These issues are related to the use of @resp and @ana across all Syriaca data.
General revision:
We will revised our use of @resp to better conform to the TEI guidelines:
To reduce the ambiguity of a resp pointing directly to a person or organization, we recommend that resp be used to point not to an agent ([person](https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-person.html) or [org](https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-org.html)) but to a [respStmt](https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-respStmt.html), [author](https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-author.html), [editor](https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-editor.html) or similar element which clarifies the exact role played by the agent. Pointing to multiple [respStmt](https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-respStmt.html)s allows the encoder to specify clearly each of the roles played in part of a TEI file (creating, transcribing, encoding, editing, proofing etc.).
As a schema change, the contents of @resp should only allow pointers to xml:ids from respStmts (that begin with "#resp").
We will number the respStmts in the following way:
xml:id="resp[\d+]-[\d+]"
where the first set of digits is the numeric portion of the record URI and the second set of digits is the sequentially assigned unique number for the respStmt
An example would be
xml:id="resp78-1" for the first respStmt in record 78.xml
Here is a full example
<respStmt xml:id="resp81-1">
<resp>Editing, data entry, and reconciling by</resp>
<name ref="http://syriaca.org/documentation/editors.xml#ngibson">Nathan P. Gibson</name>
</respStmt>
This update will need to be made a global data change across all data in conjunction with the sub issues below.
A question for discussion is if we should use the typographic symbols that will create the Editorial Comment notes directly in the xml:id (see issue #351).
Related to this change we will also use @ana to mark certain kinds of data similarly to how we previously used @resp.
These issues are related to the use of @resp and @ana across all Syriaca data.
General revision:
We will revised our use of @resp to better conform to the TEI guidelines:
As a schema change, the contents of @resp should only allow pointers to xml:ids from respStmts (that begin with "#resp").
We will number the respStmts in the following way:
xml:id="resp[\d+]-[\d+]"
where the first set of digits is the numeric portion of the record URI and the second set of digits is the sequentially assigned unique number for the respStmt
An example would be
xml:id="resp78-1" for the first respStmt in record 78.xml
Here is a full example
This update will need to be made a global data change across all data in conjunction with the sub issues below.
A question for discussion is if we should use the typographic symbols that will create the Editorial Comment notes directly in the xml:id (see issue #351).
Related to this change we will also use @ana to mark certain kinds of data similarly to how we previously used @resp.