<respons>

<respons> (responsibility) identifies the individual(s) responsible for some aspect of the content or markup of particular element(s). [21.3 Attribution of Responsibility]
Modulecertainty — Certainty, Precision, and Responsibility
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.scoping (@target, @match) att.responsibility (@cert, @resp) (att.source (@source))
locusindicates the specific aspect of the encoding (markup or content) 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)
Member of
Contained by
analysis: cl interp m phr s span w
figures: cell figure table
linking: ab join seg
nets: graph
spoken: u writing
tagdocs: eg valDesc
textcrit: app lem rdg wit witDetail
verse: metSym rhyme
May contain
Declaration

<rng:element name="respons">
 <rng:ref name="att.global.attributes"/>
 <rng:ref name="att.global.linking.attributes"/>
 <rng:ref name="att.global.analytic.attributes"/>
 <rng:ref name="att.global.facs.attributes"/>
 <rng:ref name="att.global.change.attributes"/>
 <rng:ref name="att.scoping.attributes"/>
 <rng:ref name="att.responsibility.attributes"/>
 <rng:ref name="att.source.attributes"/>
 <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:zeroOrMore>
  <rng:choice>
   <rng:ref name="model.descLike"/>
   <rng:ref name="model.certLike"/>
  </rng:choice>
 </rng:zeroOrMore>
</rng:element>
element respons
{
   att.global.attributes,
   att.global.linking.attributes,
   att.global.analytic.attributes,
   att.global.facs.attributes,
   att.global.change.attributes,
   att.scoping.attributes,
   att.responsibility.attributes,
   att.source.attributes,
   attribute locus
   {
      list { ( "name" | "start" | "end" | "location" | "value" )+ }
   },
   ( model.descLike | model.certLike )*
}
Example
<respons target="#p1locus="name locationresp="#encoder1"/>
<respons
  target="#p2"
  match="@rend"
  locus="value"
  resp="#encoder2"/>

<list type="encoders">
 <item xml:id="encoder1"/>
 <item xml:id="encoder2"/>
</list>
Example

In this (partially fictional) example the entire document was transcribed and encoded by a single encoder, except for one passage which was transcribed and encoded by the proofreader.


<!-- in the <teiHeader>: --><respStmt xml:id="enc01">
 <name>C. Colin Backslash</name>
 <resp>transcription</resp>
 <resp>encoding</resp>
</respStmt>
<respStmt xml:id="prf01">
 <name>Erin Spelling</name>
 <resp>proofreading</resp>
</respStmt>
<!-- in the <text>: -->
<p>Θερινὴ τροπή
<lb/>
 <foreign xml:lang="hebxml:id="mp0a8"> ת
 <supplied reason="undefined">קו</supplied>
  <unclear>פ</unclear>
   ת תמוז
 </foreign>
</p>
<!-- elsewhere: -->
<respons target="#mp0a8locus="name valueresp="#prf01"/>
Example

In this (partially fictional) example an initial encoder (‘across.dta’) encoded most of the document; a later encoder (‘rcapolung.ewo’) encoded a particular passage; and a third encoder (‘sbauman.emt’) fixed some of that encoding.


<!-- in the <teiHeader>: --><respStmt xml:id="enc03">
 <persName ref="../contextual/persons.xml#across.dta"/>
 <resp>encoding</resp>
</respStmt>
<!-- in the <text>: -->
<spGrp rend="braced(atonce1)xml:id="sgrp05">
 <sp who="#mo">
  <speaker rend="align(left)slant(italic)">
   <persName>Mor</persName>.</speaker>
  <p rend="break(no)">So, so, so!</p>
 </sp>
 <sp who="#hg">
  <speaker rend="align(left)slant(italic)">
   <persName>Mr. H</persName>.</speaker>
  <p rend="break(no)">What, without my Leave!</p>
 </sp>
 <sp who="#la">
  <speaker rend="align(left)slant(italic)">
   <persName>Lady D</persName>.</speaker>
  <p rend="break(no)">Amazing!</p>
 </sp>
</spGrp>
<stage rend="align(right)slant(italic)type="deliveryxml:id="atonce1">All together.</stage>
<!-- anywhere: -->
<respons
  target="sgrp05"
  locus="name"
  resp="../contextual/persons.xml#rcapolung.ewo">

 <desc>Ashley did not know what to do with this; I have decided it
   best fits as a braced <gi>spGrp</gi>
 </desc>
</respons>
<respons
  target="sgrp05"
  match=".//@rend"
  locus="value"
  resp="../contextual/persons.xml#sbauman.emt">

 <desc>fixed <att>rend</att> attributes</desc>
</respons>
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.