<respons>

<respons> (responsibility) identifies the individual(s) responsible for some aspect of the markup of particular element(s). 21.3 Attribution of Responsibility
Modul certainty — 21 Certainty, Precision, and Responsibility
Neben global gültigen Attributen
target gives the identifier(s) of the element(s) for which some aspect of the responsibility is being assigned.
Zustand Obligatorisch wenn zutreffend
Datentyp 1–∞ Vorkommen von  

<rng:ref name="data.pointer"/>
data.pointer
Durch Leerzeichen getrennt
Werte one or more valid identifiers, separated by whitespace.
pattern supplies an XSLT 2.0 pattern which may be used to select those portions of the document responsibility for which is to be specified.
Zustand Optional
Datentyp 

<rng:text/>
text
Werte The pattern should be expressed using the pattern syntax defined in Kay (ed.) (2007).
locus indicates 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
Gültige Werte:
name
responsibility is being assigned concerning the name of the element or attribute used.
start
responsibility is being assigned concerning the start of the element concerned.
end
responsibility is being assigned concerning the end of the element concerned.
location
responsibility is being assigned concerning the location of the element concerned.
value
responsibility is being assigned concerning the content (for an element) or the value (for an attribute)
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:optional>
  <rng:attribute name="target">
   <rng:list>
    <rng:oneOrMore>
     <rng:ref name="data.pointer"/>
    </rng:oneOrMore>
   </rng:list>
  </rng:attribute>
 </rng:optional>
 <rng:optional>
  <rng:attribute name="pattern">
   <rng:text/>
  </rng:attribute>
 </rng:optional>
 <rng:attribute name="locus">
  <rng:list>
   <rng:oneOrMore>
    <rng:choice>
     <rng:value>name</rng:value>
     <rng:value>start</rng:value>
     <rng:value>end</rng:value>
     <rng:value>location</rng:value>
     <rng:value>value</rng:value>
    </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 pattern { text }?,
   attribute locus
   {
      list { ( "name" | "start" | "end" | "location" | "value" )+ }
   },
   attribute resp { data.pointer },
   model.glossLike*
}
Beispiel
<respons target="#p1" locus="name location" resp="#encoder1"/>
<respons
  target="#p2"
  pattern="@rend"
  locus="value"
  resp="#encoder2"/>
<list type="encoders">
 <item xml:id="encoder1"/>
 <item xml:id="encoder2"/>
</list>