<respons>

<respons> (responsibility) identifies the individual(s) responsible for some aspect of the markup of particular element(s). 21.3 Attribution of Responsibility
Module certainty — 21 Certainty, Precision, and Responsibility
In addition to global attributes In addition to global attributes
target gives the identifier(s) of the element(s) for which some aspect of the responsibility is being assigned.
Status Mandatory when applicable
Datatype 1–∞ occurrences of  

<rng:ref name="data.pointer"/>
data.pointer
separated by whitespace
Values 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.
Status Optional
Datatype 

<rng:text/>
text
Values The pattern should be expressed using the pattern syntax defined in Kay (ed.) (2007).
Note
The context for the pattern is the nodeset identified by the value of the target attribute. If no value is given for target, the context is the document root.
Note that the value of the target attribute may include an Xpointer expression which may include an Xpath expression (see 16.2.4 TEI XPointer Schemes). Either method may be used to identify the parts of a document responsibility for which is to be documented by this element.
locus indicates the specific aspect of the markup for which responsibility is being assigned.
Status Required
Datatype 1–∞ occurrences of  

<rng:ref name="data.enumerated"/>
data.enumerated
separated by whitespace
Legal values are:
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.
Status Required
Datatype 

<rng:ref name="data.pointer"/>
data.pointer
Values 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
Used by
model.global.meta
May contain
core: desc gloss
tagdocs: altIdent equiv
Declaration 

<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*
}
Example
<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>
Note
The respons element is designed for cases in which fine-grained information about specific aspects of the markup of a text is desirable for whatever reason. Global responsibility for certain aspects of markup is usually more simply indicated in the TEI header, using the respStmt element within the title statement, edition statement, or change log.