<respons>

<respons> (responsabilidad) Identifica la responsabilidad individual/es de algún aspecto del marcaje de un elemento/s particular. 21.3 Attribution of Responsibility
Módulo certainty — 21 Certainty, Precision, and Responsibility
Además de los atributos globales
target proporciona el identificador/es del elemeto/s por el cual un aspecto de la responsabilidad está siendo asignado.
Estado Obligatorios cuando se aplican
Tipo de datos 1–∞ apariciones de  

<rng:ref name="data.pointer"/>
data.pointer
separado por espacio en blanco
Valores 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.
Estado Opcional
Tipo de datos 

<rng:text/>
text
Valores The pattern should be expressed using the pattern syntax defined in Kay (ed.) (2007).
locus indica el aspecto específico del marcaje por el cual la responsabilidad está siendo asignada
Estado Necesario
Tipo de datos 1–∞ apariciones de  

<rng:ref name="data.enumerated"/>
data.enumerated
separado por espacio en blanco
Los valores admitidos son:
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 (parte responsable) indentifica el individuo o grupo responsable del aspecto indicado en un texto electrónico.
Estado Necesario
Tipo de datos 

<rng:ref name="data.pointer"/>
data.pointer
Valores 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
Usado por
model.global.meta
Puede contener
core: desc gloss
tagdocs: altIdent equiv
Declaración 

<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*
}
Ejemplo
<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>