How to include suggestions for free text in the ODD schema?

[nathangibson]

Hi @wsalesky , there are some places in the manuscript descriptions where we would like to use free text (e.g., in handNote) but have some suggestions of common statements that might be inserted there. We'd like to have a multi-select option to insert these into a text box but allow them to be manually edited. We envision them being simple p elements (maybe including a label?), e.g., <p><label>ductus: connectivity</label>The ductus has a connected style.</p>

What is a reasonable way to indicate these suggestions in the ODD so that they could be programatically included in the XForms?

I think of 3 possibilities:

1. As multiple p elements within exemplum/egXML, where your XSLT would look for @type='prose-template' and give the option of inserting any of the items in egXML

<exemplum type="prose-template" subtype="script-ductus">
    <egXML xmlns="http://www.tei-c.org/ns/Examples">
        <p><label>ductus: connectivity</label>The ductus has a connected style.</p>
        <p><label>ductus: abusive ligatures</label>The ductus has abusive ligatures.</p>
    </egXML>
</exemplum>

2. As a valList[@type='open'] with each valItem/@ident indicating the text to be inserted, but the downside is I don't think the suggestion could contain any child elements whatsoever:

<valList type="open" >
                        <valItem ident="ductus: connectivity: The ductus has a connected style."/>
                        <valItem ident="ductus: abusive ligatures: The ductus has abusive ligatures."/>
</valList>

3. As a content model in the content element, but this seems overly complex.

cc: @mMoliere

[wsalesky]

@nathangibson I think the first option would be the best.

[nathangibson]

Thanks @wsalesky
@mMoliere So we could implement option 1 above.

[mMoliere]

@nathangibson Option 1 should be easy to implement from a technical side. Now, we need to come up with attribute-values and prose text. As far as I see there is no such case in the test schema we are now designing for the XForms, right? Shall we discuss it further via Zoom in the coming days, or should we wait for Ronny to return?

[nathangibson]

@mMoliere our current schema for XForms only covers msContents. But there were several items I think the things we talked about wanting to implement as templated text in handDesc or similar. So we don't need to discuss or do anything further in the schema yet. This is just figuring out how it should work when we get there.

[wsalesky]

@nathangibson @mMoliere Are there any examples of this in the schema?