Closed larkvi closed 6 years ago
It has only seen limited actual use:
I have transferred it over, but recommend striking it from the ODD unless a clear use case for why it would be better to do this by hand can be made.
Result of meeting was agreement on striking it from the ODD and recommending ways that generic elements could be used for individual research projects.
former definition was:
<elementSpec ident="setPhrase" prefix="cei_"
mode="add">
<desc></desc>
<classes>
<memberOf key="att.global"/>
<memberOf key="att.typed"/>
</classes>
<content>
<classRef key="model.phrase"/>
</content>
<attList>
<attDef ident="type" mode="replace">
<datatype>
<dataRef key="teidata.text"/>
</datatype>
<valList type="open">
<valItem ident="Salutem et apostolicam benedictionem">
<desc>Desc.</desc>
</valItem>
</valList>
</attDef>
</attList>
</elementSpec>
setPhrase seems like it is an example of the concordance problem--something that we used to do by hand, but now is more easily and better done by computers. In opposition to variable formulae of diplomaticParts, which still need to be controlled by hand, setPhrase should definitionally be easier to search for than to mark up, and capture more results in the process.