<respons>

<respons> (responsibility) identifies the individual(s) responsible for some aspect of the markup of particular element(s). 21.2 Attribution of Responsibility
Modulcertainty — 21 Certainty and Responsibility
Attribute
targetgives the identifier(s) of the element(s) for which some aspect of the responsibility is being assigned.
Zustand Obligatorisch
Datentyp 1–∞ Vorkommen von 

<rng:ref name="data.pointer"/>
data.pointer
Durch Leerzeichen getrennt
Werte one or more valid identifiers, separated by whitespace.
locusindicates the specific aspect of the markup for which responsibility is being assigned.
Zustand Obligatorisch
Datentyp 1–∞ Vorkommen von 

<rng:ref name="data.enumerated"/>
data.enumerated
Durch Leerzeichen getrennt
Empfohlene Werte sind:
gi
(element name) responsibility for the claim that the element is of the type indicated by the markup
location
responsibility for the claim that the element begins and ends where indicated
startLoc
(start location) responsibility for the claim that the element begins where indicated
endLoc
(end location) responsibility for the claim that the element ends where indicated
attrName
(attribute name) responsibility for the claim that the name attribute has the value given in the markup
transcribedContent
responsibility for the transcription of the element content
suppliedContent
responsibility for the contents supplied by the encoder (corrections, expansions of abbreviations, etc.)
resp (responsible party) identifies the individual or agency responsible for the indicated aspect of the electronic text.
Zustand Obligatorisch
Datentyp 

<rng:ref name="data.pointer"/>
data.pointer
Werte a pointer to one of the identifiers declared in the document header, associated with a person asserted as responsible for some aspect of the text's creation, transcription, editing, or encoding
Verwendet von
model.global.meta
Kann enthalten
core: desc gloss
tagdocs: altIdent equiv
Deklaration

<rng:element name="respons">
<rng:ref name="att.global.attributes"/>
<rng:attribute name="target">
 <rng:list>
  <rng:oneOrMore>
   <rng:ref name="data.pointer"/>
  </rng:oneOrMore>
 </rng:list>
</rng:attribute>
<rng:attribute name="locus">
 <rng:list>
  <rng:oneOrMore>
   <rng:choice>
    <rng:value>gi</rng:value>
    <rng:value>location</rng:value>
    <rng:value>startLoc</rng:value>
    <rng:value>endLoc</rng:value>
    <rng:value>attrName</rng:value>
    <rng:value>transcribedContent</rng:value>
    <rng:value>suppliedContent</rng:value>
    <rng:data type="Name"/>
   </rng:choice>
  </rng:oneOrMore>
 </rng:list>
</rng:attribute>
<rng:attribute name="resp">
 <rng:ref name="data.pointer"/>
</rng:attribute>
<rng:zeroOrMore>
 <rng:ref name="model.glossLike"/>
</rng:zeroOrMore>
</rng:element>
element respons
{
   att.global.attributes,
   attribute target { list { data.pointer+ } },
   attribute locus
   {
      list
      {
         (
            "gi"
          | "location"
          | "startLoc"
          | "endLoc"
          | "attrName"
          | "transcribedContent"
          | "suppliedContent"
          | xsd:Name
         )+
      }
   },
   attribute resp { data.pointer },
   model.glossLike*
}
Beispiel
<respons target="#p1" locus="gi location" resp="#encoder1"/>
<respons target="#p2" locus="rend" resp="#encoder2"/>
<list type="encoders">
 <item xml:id="encoder1"/>
 <item xml:id="encoder2"/>
</list>