Example: <gi> (element name)
These search results reproduce every example of the use of <gi> in the Guidelines, including all localised and translated versions. In some cases, the examples have been drawn from discussion of other elements in the Guidelines and illustrating the use of <gi> is not the main focus of the passage in question. In other cases, examples may be direct translations of each other, and hence identical from the perspective of their encoding.
- 2 The TEI Header
- 3 Elements Available in All TEI Documents
- 13 Names, Dates, People, and Places
- 16 Linking, Segmentation, and Alignment
- 21 Certainty, Precision, and Responsibility
22 Documentation Elements
<p>The <gi>gi</gi> element is used to tag element
names when they appear in the text; the <gi>tag</gi> element however is used to show how a tag as
such might appear. So one might talk of an occurrence of the <gi>blort</gi> element which had been
tagged <tag>blort type='runcible'</tag>. The <att>type</att> attribute may take any name token as
value; the default value is <val>spqr</val>, in memory of its creator.</p>
names when they appear in the text; the <gi>tag</gi> element however is used to show how a tag as
such might appear. So one might talk of an occurrence of the <gi>blort</gi> element which had been
tagged <tag>blort type='runcible'</tag>. The <att>type</att> attribute may take any name token as
value; the default value is <val>spqr</val>, in memory of its creator.</p>
22.1.2 Element and Attribute Descriptions
<div>
<head>Element and Attribute Descriptions</head>
<p>Within the body of a document using this module, the … the brief prose descriptions these provide for elements and attributes.
<specList>
<specDesc key="specList"/>
<specDesc key="specDesc" atts="atts"/>
</specList>
</p>
<p>TEI practice recommends that a <gi>specList</gi> listing the elements under … </p>
<!-- ... -->
</div>
<head>Element and Attribute Descriptions</head>
<p>Within the body of a document using this module, the … the brief prose descriptions these provide for elements and attributes.
<specList>
<specDesc key="specList"/>
<specDesc key="specDesc" atts="atts"/>
</specList>
</p>
<p>TEI practice recommends that a <gi>specList</gi> listing the elements under … </p>
<!-- ... -->
</div>
<p>The
<gi>term</gi> element is declared using the following syntax:
<eg><![CDATA[<!ELEMENT term (%phrase.content;)>]]</eg>
</p>
<gi>term</gi> element is declared using the following syntax:
<eg><![CDATA[<!ELEMENT term (%phrase.content;)>]]</eg>
</p>
<eg> (fr)
<p>L'élément <gi>term</gi> est déclaré en utilisant la syntaxe suivante :
<eg><![CDATA[<!ELEMENT term (%phrase.content;)>]]</eg>
</p>
<eg><![CDATA[<!ELEMENT term (%phrase.content;)>]]</eg>
</p>
<eg> (zh-TW)
<egXML xmlns="http://www.tei-c.org/ns/Examples"><div>
<head>A slide about <gi>egXML</gi>
</head>
<list>
<item>
<gi>egXML</gi> can be used to give XML examples in the TEI
Examples namespace</item>
<item>Attributes values for <att>valid</att>:
<list rend="collapsed">
<item>
<val rend="green">true</val>: intended to be fully
valid</item>
<item>
<val rend="amber">feasible</val>: valid if missing nodes
provided</item>
<item>
<val rend="red">false</val>: not intended to be valid</item>
</list>
</item>
<item>The <att>rend</att> attribute can be
used for recording how parts of the example were rendered.</item>
</list>
</div>
</egXML>
<head>A slide about <gi>egXML</gi>
</head>
<list>
<item>
<gi>egXML</gi> can be used to give XML examples in the TEI
Examples namespace</item>
<item>Attributes values for <att>valid</att>:
<list rend="collapsed">
<item>
<val rend="green">true</val>: intended to be fully
valid</item>
<item>
<val rend="amber">feasible</val>: valid if missing nodes
provided</item>
<item>
<val rend="red">false</val>: not intended to be valid</item>
</list>
</item>
<item>The <att>rend</att> attribute can be
used for recording how parts of the example were rendered.</item>
</list>
</div>
</egXML>
<div>
<head>A slide about <gi>egXML</gi>
</head>
<list>
<item>
<gi>egXML</gi> can be used to give XML examples in the TEI
Examples namespace</item>
<item>Attributes values for <att>valid</att>:
<list rend="collapsed">
<item>
<val rend="green">true</val>: intended to be fully
valid</item>
<item>
<val rend="amber">feasible</val>: valid if missing nodes
provided</item>
<item>
<val rend="red">false</val>: not intended to be valid</item>
</list>
</item>
<item>The <att>rend</att> attribute can be
used for recording how parts of the example were rendered.</item>
</list>
</div>
<head>A slide about <gi>egXML</gi>
</head>
<list>
<item>
<gi>egXML</gi> can be used to give XML examples in the TEI
Examples namespace</item>
<item>Attributes values for <att>valid</att>:
<list rend="collapsed">
<item>
<val rend="green">true</val>: intended to be fully
valid</item>
<item>
<val rend="amber">feasible</val>: valid if missing nodes
provided</item>
<item>
<val rend="red">false</val>: not intended to be valid</item>
</list>
</item>
<item>The <att>rend</att> attribute can be
used for recording how parts of the example were rendered.</item>
</list>
</div>
<p>The <gi>xhtml:li</gi> element is roughly analogous to the <gi>item</gi> element, as is the
<gi scheme="DBK">listItem</gi> element.</p>
<gi scheme="DBK">listItem</gi> element.</p>
<gi> (fr)
<p>L'élément <gi>xhtml:li</gi> est grosso modo analogue à l'élément <gi>item</gi>, comme
l'est l'élément <gi scheme="DBK">listItem</gi>.</p>
l'est l'élément <gi scheme="DBK">listItem</gi>.</p>
<gi> (zh-TW)
<gi> (de)
<p>The <gi>xhtml:li</gi> element is roughly analogous to the <gi>item</gi> element, as is the
<gi scheme="DBK">listItem</gi> element.</p>
<gi scheme="DBK">listItem</gi> element.</p>
<classSpec module="tei" type="model"
ident="model.segLike">
<desc>groups elements used for arbitrary segmentation.</desc>
<classes>
<memberOf key="model.phrase"/>
</classes>
<remarks>
<p>The principles on which segmentation is carried out, and
any special codes or attribute values used, should be defined explicitly
in the <gi>segmentation</gi> element of the <gi>encodingDesc</gi> within
the associated TEI header.</p>
</remarks>
</classSpec>
ident="model.segLike">
<desc>groups elements used for arbitrary segmentation.</desc>
<classes>
<memberOf key="model.phrase"/>
</classes>
<remarks>
<p>The principles on which segmentation is carried out, and
any special codes or attribute values used, should be defined explicitly
in the <gi>segmentation</gi> element of the <gi>encodingDesc</gi> within
the associated TEI header.</p>
</remarks>
</classSpec>
<classSpec> (fr)
<classSpec module="tei" type="model"
ident="model.segLike">
<desc>regroupe des éléments utilisés pour des segmentations arbitraires.</desc>
<classes>
<memberOf key="model.phrase"/>
</classes>
<remarks>
<p>Les principes selon lesquels la segmentation est effectuée, et tous les codes
spéciaux ou toutes les valeurs d'attribut utilisées, devraient être définis
explicitement dans l'élément<gi>segmentation</gi> de l'élément<gi>encodingDesc</gi>
dans l'en-tête TEI associé.</p>
</remarks>
</classSpec>
ident="model.segLike">
<desc>regroupe des éléments utilisés pour des segmentations arbitraires.</desc>
<classes>
<memberOf key="model.phrase"/>
</classes>
<remarks>
<p>Les principes selon lesquels la segmentation est effectuée, et tous les codes
spéciaux ou toutes les valeurs d'attribut utilisées, devraient être définis
explicitement dans l'élément<gi>segmentation</gi> de l'élément<gi>encodingDesc</gi>
dans l'en-tête TEI associé.</p>
</remarks>
</classSpec>
<classSpec> (zh-TW)
<classSpec module="tei" type="model"
ident="model.segLike">
<desc>匯集用於隨機分割的元素</desc>
<classes>
<memberOf key="model.phrase"/>
</classes>
<remarks>
<p>The principles on which segmentation is carried out, and any special codes or attribute
values used, should be defined explicitly in the <gi>segmentation</gi> element of the
<gi>encodingDesc</gi> within the associated TEI header.</p>
</remarks>
</classSpec>
ident="model.segLike">
<desc>匯集用於隨機分割的元素</desc>
<classes>
<memberOf key="model.phrase"/>
</classes>
<remarks>
<p>The principles on which segmentation is carried out, and any special codes or attribute
values used, should be defined explicitly in the <gi>segmentation</gi> element of the
<gi>encodingDesc</gi> within the associated TEI header.</p>
</remarks>
</classSpec>
22.4.1 Description of Components
<elementSpec module="core" ident="foreign">
<!--... -->
<remarks>
<p>This element is intended for use only where no other element is available to mark the phrase
or words concerned. The global <att>xml:lang</att> attribute should be used in preference to
this element where it is intended to mark the language of the whole of some text element.</p>
<p>The <gi>distinct</gi> element may be used to identify phrases belonging to sublanguages or
registers not generally regarded as true languages.</p>
</remarks>
<!--... -->
</elementSpec>
<!--... -->
<remarks>
<p>This element is intended for use only where no other element is available to mark the phrase
or words concerned. The global <att>xml:lang</att> attribute should be used in preference to
this element where it is intended to mark the language of the whole of some text element.</p>
<p>The <gi>distinct</gi> element may be used to identify phrases belonging to sublanguages or
registers not generally regarded as true languages.</p>
</remarks>
<!--... -->
</elementSpec>
<exemplum xml:lang="en">
<p>The <gi>name</gi> element can be used for both personal names and place names:</p>
<eg xml:space="preserve"><![CDATA[ <q>My dear <name type="person">Mr. Bennet</name>,</q> said his lady to him one day, <q>have you heard that <name type="place">Netherfield Park</name> is let at last?</q>]]></eg>
<p>As shown above, the <att>type</att> attribute may be used to distinguish the one from the
other.</p>
</exemplum>
<p>The <gi>name</gi> element can be used for both personal names and place names:</p>
<eg xml:space="preserve"><![CDATA[ <q>My dear <name type="person">Mr. Bennet</name>,</q> said his lady to him one day, <q>have you heard that <name type="place">Netherfield Park</name> is let at last?</q>]]></eg>
<p>As shown above, the <att>type</att> attribute may be used to distinguish the one from the
other.</p>
</exemplum>
<exemplum> (fr)
<exemplum>
<p>L'élément<gi>name</gi> est employé à la fois pour les noms propres de personne et de
lieu : </p>
<eg xml:space="preserve"> <q> <name type="person">Mrs. Parker</name>, connaît un épicier bulgare, nommé, <name type="person">Popochef Rosenfeld</name>qui vient d'arriver de <name type="place" >Constantinople</name>. C'est un grand spécialiste en yaourts.</q> </eg>
<p>Comme il est indiqué ci-dessus, l'attribut<att>type</att> peut être utilisé pour
distinguer un élément de l'autre.</p>
</exemplum>
<p>L'élément<gi>name</gi> est employé à la fois pour les noms propres de personne et de
lieu : </p>
<eg xml:space="preserve"> <q> <name type="person">Mrs. Parker</name>, connaît un épicier bulgare, nommé, <name type="person">Popochef Rosenfeld</name>qui vient d'arriver de <name type="place" >Constantinople</name>. C'est un grand spécialiste en yaourts.</q> </eg>
<p>Comme il est indiqué ci-dessus, l'attribut<att>type</att> peut être utilisé pour
distinguer un élément de l'autre.</p>
</exemplum>
<exemplum> (zh-TW)
<exemplum>
<p>
<gi>名稱</gi>元素可以同時用於人名以及地名：</p>
<eg xml:space="preserve"><![CDATA[ <q>我親愛的 <name type="person">班耐特</name>先生，</q> 有一天太太對他說， <q>你聽到<name type="place">尼得斐莊園</name> 終於租出去了嗎？</q>]]></eg>
<p>如上所示，<att>屬性值</att> 可用來分辨人名或地名。</p>
</exemplum>
<p>
<gi>名稱</gi>元素可以同時用於人名以及地名：</p>
<eg xml:space="preserve"><![CDATA[ <q>我親愛的 <name type="person">班耐特</name>先生，</q> 有一天太太對他說， <q>你聽到<name type="place">尼得斐莊園</name> 終於租出去了嗎？</q>]]></eg>
<p>如上所示，<att>屬性值</att> 可用來分辨人名或地名。</p>
</exemplum>
<valDesc>must point to another <gi>align</gi>
element logically preceding this one.</valDesc>
element logically preceding this one.</valDesc>
<valDesc> (fr)
<valDesc>doit pointer vers un autre élément <gi>align</gi>précédant logiquement
celui-ci.</valDesc>
celui-ci.</valDesc>
<valDesc> (zh-TW)
<valList type="closed">
<valItem ident="border">
<desc>used to signify that there is border around a page.</desc>
</valItem>
<valItem ident="border-rule">
<desc>used to signify that there is a border made of ruled lines.</desc>
</valItem>
<valItem ident="border-ornamental">
<desc>used to signify that there is an ornamental border.</desc>
</valItem>
<valItem ident="catch">
<gloss>catchword</gloss>
<desc>for catch words.</desc>
</valItem>
<valItem ident="lineNum">
<gloss>line number</gloss>
<desc>for printed line numbers (usually in poetry).</desc>
</valItem>
<valItem ident="listHead">
<gloss>list heading</gloss>
<desc>for headings of lists or similar constructs; often used in tables of contents for the
<q>page</q> heading.</desc>
</valItem>
<valItem ident="pageNum">
<gloss>page number</gloss>
<desc>for page numbers.</desc>
</valItem>
<valItem ident="pressFig">
<gloss>press figure</gloss>
<desc>for press figures. These are usually numbers, but are not sequential or regularly
printed like signatures.</desc>
</valItem>
<valItem ident="sig">
<gloss>signature</gloss>
<desc>for printed signatures.</desc>
</valItem>
<valItem ident="unknown">
<desc>for a metawork whose function you do not know.</desc>
</valItem>
<valItem ident="vol">
<gloss>volume number</gloss>
<desc>for printed volume numbers.</desc>
</valItem>
<valItem ident="other">
<desc>anything not covered by the above values.</desc>
<remarks>
<p>Used for an ornament, decorated tool line, or symbol(s) that is not officially a
delimiter (and thus there is no element on which to put <val>pre()</val> or
<val>post()</val>) but is used to fill space at the bottom of a page so that a
<gi>floatingText</gi> or similar can start at the top of the next.</p>
</remarks>
</valItem>
</valList>
<valItem ident="border">
<desc>used to signify that there is border around a page.</desc>
</valItem>
<valItem ident="border-rule">
<desc>used to signify that there is a border made of ruled lines.</desc>
</valItem>
<valItem ident="border-ornamental">
<desc>used to signify that there is an ornamental border.</desc>
</valItem>
<valItem ident="catch">
<gloss>catchword</gloss>
<desc>for catch words.</desc>
</valItem>
<valItem ident="lineNum">
<gloss>line number</gloss>
<desc>for printed line numbers (usually in poetry).</desc>
</valItem>
<valItem ident="listHead">
<gloss>list heading</gloss>
<desc>for headings of lists or similar constructs; often used in tables of contents for the
<q>page</q> heading.</desc>
</valItem>
<valItem ident="pageNum">
<gloss>page number</gloss>
<desc>for page numbers.</desc>
</valItem>
<valItem ident="pressFig">
<gloss>press figure</gloss>
<desc>for press figures. These are usually numbers, but are not sequential or regularly
printed like signatures.</desc>
</valItem>
<valItem ident="sig">
<gloss>signature</gloss>
<desc>for printed signatures.</desc>
</valItem>
<valItem ident="unknown">
<desc>for a metawork whose function you do not know.</desc>
</valItem>
<valItem ident="vol">
<gloss>volume number</gloss>
<desc>for printed volume numbers.</desc>
</valItem>
<valItem ident="other">
<desc>anything not covered by the above values.</desc>
<remarks>
<p>Used for an ornament, decorated tool line, or symbol(s) that is not officially a
delimiter (and thus there is no element on which to put <val>pre()</val> or
<val>post()</val>) but is used to fill space at the bottom of a page so that a
<gi>floatingText</gi> or similar can start at the top of the next.</p>
</remarks>
</valItem>
</valList>
2 The TEI Header
<teiHeader>
<fileDesc>
<titleStmt>
<title>Shakespeare: the first folio (1623) in electronic form</title>
<author>Shakespeare, William (1564–1616)</author>
<respStmt>
<resp>Originally prepared by</resp>
<name>Trevor Howard-Hill</name>
</respStmt>
<respStmt>
<resp>Revised and edited by</resp>
<name>Christine Avern-Carr</name>
</respStmt>
</titleStmt>
<publicationStmt>
<distributor>Oxford Text Archive</distributor>
<address>
<addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
</address>
<idno type="OTA">119</idno>
<availability>
<p>Freely available on a non-commercial basis.</p>
</availability>
<date when="1968">1968</date>
</publicationStmt>
<sourceDesc>
<bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
1968)</bibl>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>Originally prepared for use in the production of a series of old-spelling
concordances in 1968, this text was extensively checked and revised for use during the
editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>
</projectDesc>
<editorialDecl>
<correction>
<p>Turned letters are silently corrected.</p>
</correction>
<normalization>
<p>Original spelling and typography is retained, except that long s and ligatured
forms are not encoded.</p>
</normalization>
</editorialDecl>
<refsDecl xml:id="ASLREF">
<cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">
<p>A reference is created by assembling the following, in the reverse order as that
listed here: <list>
<item>the <att>n</att> value of the preceding <gi>lb</gi>
</item>
<item>a period</item>
<item>the <att>n</att> value of the ancestor <gi>div2</gi>
</item>
<item>a space</item>
<item>the <att>n</att> value of the parent <gi>div1</gi>
</item>
</list>
</p>
</cRefPattern>
</refsDecl>
</encodingDesc>
<revisionDesc>
<list>
<item>
<date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>
<item>
<date when="1989-03-01">1 Mar 89</date> LB made new file</item>
</list>
</revisionDesc>
</teiHeader>
<fileDesc>
<titleStmt>
<title>Shakespeare: the first folio (1623) in electronic form</title>
<author>Shakespeare, William (1564–1616)</author>
<respStmt>
<resp>Originally prepared by</resp>
<name>Trevor Howard-Hill</name>
</respStmt>
<respStmt>
<resp>Revised and edited by</resp>
<name>Christine Avern-Carr</name>
</respStmt>
</titleStmt>
<publicationStmt>
<distributor>Oxford Text Archive</distributor>
<address>
<addrLine>13 Banbury Road, Oxford OX2 6NN, UK</addrLine>
</address>
<idno type="OTA">119</idno>
<availability>
<p>Freely available on a non-commercial basis.</p>
</availability>
<date when="1968">1968</date>
</publicationStmt>
<sourceDesc>
<bibl>The first folio of Shakespeare, prepared by Charlton Hinman (The Norton Facsimile,
1968)</bibl>
</sourceDesc>
</fileDesc>
<encodingDesc>
<projectDesc>
<p>Originally prepared for use in the production of a series of old-spelling
concordances in 1968, this text was extensively checked and revised for use during the
editing of the new Oxford Shakespeare (Wells and Taylor, 1989).</p>
</projectDesc>
<editorialDecl>
<correction>
<p>Turned letters are silently corrected.</p>
</correction>
<normalization>
<p>Original spelling and typography is retained, except that long s and ligatured
forms are not encoded.</p>
</normalization>
</editorialDecl>
<refsDecl xml:id="ASLREF">
<cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
replacementPattern="#xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">
<p>A reference is created by assembling the following, in the reverse order as that
listed here: <list>
<item>the <att>n</att> value of the preceding <gi>lb</gi>
</item>
<item>a period</item>
<item>the <att>n</att> value of the ancestor <gi>div2</gi>
</item>
<item>a space</item>
<item>the <att>n</att> value of the parent <gi>div1</gi>
</item>
</list>
</p>
</cRefPattern>
</refsDecl>
</encodingDesc>
<revisionDesc>
<list>
<item>
<date when="1989-04-12">12 Apr 89</date> Last checked by CAC</item>
<item>
<date when="1989-03-01">1 Mar 89</date> LB made new file</item>
</list>
</revisionDesc>
</teiHeader>
2.3.3 The Editorial Practices Declaration
<editorialDecl>
<segmentation>
<p>
<gi>s</gi> elements mark orthographic sentences and
are numbered sequentially
within their parent <gi>div</gi> element
</p>
</segmentation>
<interpretation>
<p>The part of speech analysis applied throughout section 4 was
added by hand and has not been checked.</p>
</interpretation>
<correction>
<p>Errors in transcription controlled by using the
WordPerfect spelling checker.</p>
</correction>
<normalization source="http://szotar.sztaki.hu/webster/">
<p>All words converted to Modern American spelling following
Websters 9th Collegiate dictionary.</p>
</normalization>
<quotation marks="all">
<p>All opening quotation marks represented by entity reference
<ident type="ge">odq</ident>; all closing quotation marks
represented by entity reference <ident type="ge">cdq</ident>.</p>
</quotation>
</editorialDecl>
<segmentation>
<p>
<gi>s</gi> elements mark orthographic sentences and
are numbered sequentially
within their parent <gi>div</gi> element
</p>
</segmentation>
<interpretation>
<p>The part of speech analysis applied throughout section 4 was
added by hand and has not been checked.</p>
</interpretation>
<correction>
<p>Errors in transcription controlled by using the
WordPerfect spelling checker.</p>
</correction>
<normalization source="http://szotar.sztaki.hu/webster/">
<p>All words converted to Modern American spelling following
Websters 9th Collegiate dictionary.</p>
</normalization>
<quotation marks="all">
<p>All opening quotation marks represented by entity reference
<ident type="ge">odq</ident>; all closing quotation marks
represented by entity reference <ident type="ge">cdq</ident>.</p>
</quotation>
</editorialDecl>
<editorialDecl>
<normalization method="markup">
<p>Where both upper- and lower-case i, j, u, v, and vv have been normalized, to modern
20th century typographical practice, the <gi>choice</gi> element has been used to
enclose <gi>orig</gi> and <gi>reg</gi> elements giving the original and new values
respectively. ... </p>
</normalization>
<normalization method="silent">
<p>Spacing between words and following punctuation has been regularized to zero spaces;
spacing between words has been regularized to one space.</p>
</normalization>
<normalization source="http://www.dict.sztaki.hu/webster">
<p>Spelling converted throughout to Modern American usage, based on Websters 9th
Collegiate dictionary.</p>
</normalization>
</editorialDecl>
<normalization method="markup">
<p>Where both upper- and lower-case i, j, u, v, and vv have been normalized, to modern
20th century typographical practice, the <gi>choice</gi> element has been used to
enclose <gi>orig</gi> and <gi>reg</gi> elements giving the original and new values
respectively. ... </p>
</normalization>
<normalization method="silent">
<p>Spacing between words and following punctuation has been regularized to zero spaces;
spacing between words has been regularized to one space.</p>
</normalization>
<normalization source="http://www.dict.sztaki.hu/webster">
<p>Spelling converted throughout to Modern American usage, based on Websters 9th
Collegiate dictionary.</p>
</normalization>
</editorialDecl>
<normalization> (fr)
<editorialDecl>
<normalization method="markup">
<p>Là où les majuscules et les minuscules i, j, u, v et vv ont été normalisées selon la
pratique typographique moderne, l'élément<gi> choice</gi> a été employé en association
avec <gi>orig</gi> et <gi>reg</gi>pour fournir à la fois les formes originales et les
formes nouvelles , respectivement ... </p>
</normalization>
<normalization method="silent">
<p> L'espace entre chaque mot a été régularisé à un espace. Un signe de ponctuation
simple est suivi d'un espace, un signe de ponctuation double est précédé et suivi d'un
espace.</p>
</normalization>
<normalization source="http://www.academie-francaise.fr/langue/orthographe/plan.html">
<p>Normalisation effectuée selon le Rapport Du Conseil Supérieur De La Langue Française
publié dans les documents administratifs du Journal officiel du 6 décembre 1990</p>
</normalization>
</editorialDecl>
<normalization method="markup">
<p>Là où les majuscules et les minuscules i, j, u, v et vv ont été normalisées selon la
pratique typographique moderne, l'élément<gi> choice</gi> a été employé en association
avec <gi>orig</gi> et <gi>reg</gi>pour fournir à la fois les formes originales et les
formes nouvelles , respectivement ... </p>
</normalization>
<normalization method="silent">
<p> L'espace entre chaque mot a été régularisé à un espace. Un signe de ponctuation
simple est suivi d'un espace, un signe de ponctuation double est précédé et suivi d'un
espace.</p>
</normalization>
<normalization source="http://www.academie-francaise.fr/langue/orthographe/plan.html">
<p>Normalisation effectuée selon le Rapport Du Conseil Supérieur De La Langue Française
publié dans les documents administratifs du Journal officiel du 6 décembre 1990</p>
</normalization>
</editorialDecl>
<normalization> (zh-TW)
<editorialDecl>
<normalization method="markup">
<p>當大寫與小寫的 i, j, u, v, 以及vv已經標準化，符合二十世紀現代印刷術，<gi>choice</gi>元素就用來包含 <gi>orig</gi> 還有
<gi>reg</gi> 兩個元素，並賦予新的意義。… </p>
</normalization>
<normalization method="silent">
<p>字與字後的標點符號之間規定沒有空格；字與字間規定留一個空格。</p>
</normalization>
<normalization source="http://www.dict.sztaki.hu/webster">
<p>拼字源於Websters 9th Collegiate字典的現代美語用法</p>
</normalization>
</editorialDecl>
<normalization method="markup">
<p>當大寫與小寫的 i, j, u, v, 以及vv已經標準化，符合二十世紀現代印刷術，<gi>choice</gi>元素就用來包含 <gi>orig</gi> 還有
<gi>reg</gi> 兩個元素，並賦予新的意義。… </p>
</normalization>
<normalization method="silent">
<p>字與字後的標點符號之間規定沒有空格；字與字間規定留一個空格。</p>
</normalization>
<normalization source="http://www.dict.sztaki.hu/webster">
<p>拼字源於Websters 9th Collegiate字典的現代美語用法</p>
</normalization>
</editorialDecl>
<quotation marks="none">
<p>No quotation marks have been retained. Instead, the <att>rend</att> attribute on the
<gi>q</gi> element is used to specify what kinds of quotation mark was used, according
to the following list: <list type="gloss">
<label>dq</label>
<item>double quotes, open and close</item>
<label>sq</label>
<item>single quotes, open and close</item>
<label>dash</label>
<item>long dash open, no close</item>
<label>dg</label>
<item>double guillemets, open and close</item>
</list>
</p>
</quotation>
<p>No quotation marks have been retained. Instead, the <att>rend</att> attribute on the
<gi>q</gi> element is used to specify what kinds of quotation mark was used, according
to the following list: <list type="gloss">
<label>dq</label>
<item>double quotes, open and close</item>
<label>sq</label>
<item>single quotes, open and close</item>
<label>dash</label>
<item>long dash open, no close</item>
<label>dg</label>
<item>double guillemets, open and close</item>
</list>
</p>
</quotation>
<quotation> (fr)
<quotation marks="none">
<p>Aucun guillemet n'a été conservé. Au lieu de cela, on a utilisé l'attribut
<att>rend</att> pour l'élément <gi>q</gi> afin de spécifier quel type de guillemet a été
utilisé, selon la liste suivante : <list type="gloss">
<label>ga</label>
<item>guillemet allemand</item>
<label>gd</label>
<item>guillemet anglais ou guillemet dactylographique </item>
<label>gf</label>
<item>guillemet français</item>
</list>
</p>
</quotation>
<p>Aucun guillemet n'a été conservé. Au lieu de cela, on a utilisé l'attribut
<att>rend</att> pour l'élément <gi>q</gi> afin de spécifier quel type de guillemet a été
utilisé, selon la liste suivante : <list type="gloss">
<label>ga</label>
<item>guillemet allemand</item>
<label>gd</label>
<item>guillemet anglais ou guillemet dactylographique </item>
<label>gf</label>
<item>guillemet français</item>
</list>
</p>
</quotation>
<quotation> (zh-TW)
<quotation marks="none">
<p>不保留引號，改用元素<gi>q</gi>內的屬性<att>rend</att> 來區分引號的種類，種類如下：<list type="gloss">
<label>dq</label>
<item>雙引號，前後各一</item>
<label>sq</label>
<item>單引號，前後各一</item>
<label>dash</label>
<item>破折號，僅前面一個</item>
<label>dg</label>
<item>雙箭號，前後各一</item>
</list>
</p>
</quotation>
<p>不保留引號，改用元素<gi>q</gi>內的屬性<att>rend</att> 來區分引號的種類，種類如下：<list type="gloss">
<label>dq</label>
<item>雙引號，前後各一</item>
<label>sq</label>
<item>單引號，前後各一</item>
<label>dash</label>
<item>破折號，僅前面一個</item>
<label>dg</label>
<item>雙箭號，前後各一</item>
</list>
</p>
</quotation>
<segmentation>
<p>
<gi>s</gi> elements mark orthographic sentences and are numbered sequentially within
their parent <gi>div</gi> element </p>
</segmentation>
<p>
<gi>s</gi> elements mark orthographic sentences and are numbered sequentially within
their parent <gi>div</gi> element </p>
</segmentation>
<p>
<gi>seg</gi> elements are used to mark functional constituents of various types within each
<gi>s</gi>; the typology used is defined by a <gi>taxonomy</gi> element in the corpus
header <gi>classDecl</gi>
</p>
<gi>seg</gi> elements are used to mark functional constituents of various types within each
<gi>s</gi>; the typology used is defined by a <gi>taxonomy</gi> element in the corpus
header <gi>classDecl</gi>
</p>
<punctuation marks="all"
placement="internal">
<p>All punctuation marks in the source text have been retained and represented using the
appropriate Unicode code point. In cases where a punctuation mark and nearby markup convey
the same information (for example, a sentence ends with a question mark and is also tagged
as <gi>s</gi>) the punctuation mark is captured as content within the element.</p>
</punctuation>
placement="internal">
<p>All punctuation marks in the source text have been retained and represented using the
appropriate Unicode code point. In cases where a punctuation mark and nearby markup convey
the same information (for example, a sentence ends with a question mark and is also tagged
as <gi>s</gi>) the punctuation mark is captured as content within the element.</p>
</punctuation>
<refsDecl>
<p>The <att>n</att> attribute of each text in this corpus carries a
unique identifying code for the whole text. The title of the text is
held as the content of the first <gi>head</gi> element within each
text. The <att>n</att> attribute on each <gi>div1</gi> and
<gi>div2</gi> contains the canonical reference for each such
division, in the form 'XX.yyy', where XX is the book number in Roman
numerals, and yyy the section number in arabic. Line breaks are
marked by empty <gi>lb</gi> elements, each of which includes the
through line number in Casaubon's edition as the value of its
<gi>n</gi> attribute.</p>
<p>The through line number and the text identifier uniquely identify
any line. A canonical reference may be made up by concatenating the
<gi>n</gi> values from the <gi>text</gi>, <gi>div1</gi>, or
<gi>div2</gi> and calculating the line number within each part.</p>
</refsDecl>
<p>The <att>n</att> attribute of each text in this corpus carries a
unique identifying code for the whole text. The title of the text is
held as the content of the first <gi>head</gi> element within each
text. The <att>n</att> attribute on each <gi>div1</gi> and
<gi>div2</gi> contains the canonical reference for each such
division, in the form 'XX.yyy', where XX is the book number in Roman
numerals, and yyy the section number in arabic. Line breaks are
marked by empty <gi>lb</gi> elements, each of which includes the
through line number in Casaubon's edition as the value of its
<gi>n</gi> attribute.</p>
<p>The through line number and the text identifier uniquely identify
any line. A canonical reference may be made up by concatenating the
<gi>n</gi> values from the <gi>text</gi>, <gi>div1</gi>, or
<gi>div2</gi> and calculating the line number within each part.</p>
</refsDecl>
<refsDecl> (fr)
<refsDecl xml:id="fr_ASLREF">
<cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
replacementPattern="#fr_xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">
<p>Une référence a été créée en assemblant les éléments suivants dans l'ordre inverse de
la liste qui suit : <list>
<item>la valeur <att>n</att> du précédent <gi>lb</gi>
</item>
<item>une période</item>
<item>la valeur <att>n</att> de l'ancêtre <gi>div2</gi>
</item>
<item>un espace</item>
<item>la valeur<att>n</att> du parent <gi>div1</gi>
</item>
</list>
</p>
</cRefPattern>
</refsDecl>
<cRefPattern matchPattern="(\S+) ([^.]+)\.(.*)"
replacementPattern="#fr_xpath(//div1[@n='$1']/div2/[@n='$2']//lb[@n='$3'])">
<p>Une référence a été créée en assemblant les éléments suivants dans l'ordre inverse de
la liste qui suit : <list>
<item>la valeur <att>n</att> du précédent <gi>lb</gi>
</item>
<item>une période</item>
<item>la valeur <att>n</att> de l'ancêtre <gi>div2</gi>
</item>
<item>un espace</item>
<item>la valeur<att>n</att> du parent <gi>div1</gi>
</item>
</list>
</p>
</cRefPattern>
</refsDecl>
<refsDecl> (zh-TW)
<refsDecl>
<p>參照是將位於最高層級的<gi>div</gi>元素的屬性<att>n</att>值串聯起來，
其後跟著空格和續接的下一層級<gi>div</gi>，接著冒點，
然後是續接的下一(最低) 層級的<gi>div</gi>所組成。</p>
</refsDecl>
<p>參照是將位於最高層級的<gi>div</gi>元素的屬性<att>n</att>值串聯起來，
其後跟著空格和續接的下一層級<gi>div</gi>，接著冒點，
然後是續接的下一(最低) 層級的<gi>div</gi>所組成。</p>
</refsDecl>
<refsDecl>
<p>References are made up by concatenating the value for the
<att>n</att> attribute on the highest level <gi>div</gi>
element, followed by a space, followed by the sequential
number of the next level <gi>div</gi> followed by a colon
followed by the sequential number of the next (and lowest)
level <gi>div</gi>.</p>
</refsDecl>
<p>References are made up by concatenating the value for the
<att>n</att> attribute on the highest level <gi>div</gi>
element, followed by a space, followed by the sequential
number of the next level <gi>div</gi> followed by a colon
followed by the sequential number of the next (and lowest)
level <gi>div</gi>.</p>
</refsDecl>
<prefixDef ident="ref"
matchPattern="([a-z]+)"
replacementPattern="../../references/references.xml#$1">
<p> In the context of this project, private URIs with
the prefix "ref" point to <gi>div</gi> elements in
the project's global references.xml file.
</p>
</prefixDef>
matchPattern="([a-z]+)"
replacementPattern="../../references/references.xml#$1">
<p> In the context of this project, private URIs with
the prefix "ref" point to <gi>div</gi> elements in
the project's global references.xml file.
</p>
</prefixDef>
<listPrefixDef>
<prefixDef ident="psn"
matchPattern="([A-Z]+)"
replacementPattern="personography.xml#$1">
<p> Private URIs using the <code>psn</code>
prefix are pointers to <gi>person</gi>
elements in the personography.xml file.
For example, <code>psn:MDH</code>
dereferences to <code>personography.xml#MDH</code>.
</p>
</prefixDef>
<prefixDef ident="bibl"
matchPattern="([a-z]+[a-z0-9]*)"
replacementPattern="http://www.example.com/getBibl.xql?id=$1">
<p> Private URIs using the <code>bibl</code> prefix can be
expanded to form URIs which retrieve the relevant
bibliographical reference from www.example.com.
</p>
</prefixDef>
</listPrefixDef>
<prefixDef ident="psn"
matchPattern="([A-Z]+)"
replacementPattern="personography.xml#$1">
<p> Private URIs using the <code>psn</code>
prefix are pointers to <gi>person</gi>
elements in the personography.xml file.
For example, <code>psn:MDH</code>
dereferences to <code>personography.xml#MDH</code>.
</p>
</prefixDef>
<prefixDef ident="bibl"
matchPattern="([a-z]+[a-z0-9]*)"
replacementPattern="http://www.example.com/getBibl.xql?id=$1">
<p> Private URIs using the <code>bibl</code> prefix can be
expanded to form URIs which retrieve the relevant
bibliographical reference from www.example.com.
</p>
</prefixDef>
</listPrefixDef>
<!-- ... --><revisionDesc>
<change n="RCS:1.39" when="2007-08-08"
who="#jwernimo.lrv">Changed <val>drama.verse</val>
<gi>lg</gi>s to <gi>p</gi>s. <note>we have opened a discussion about the need for a new
value for <att>type</att> of <gi>lg</gi>, <val>drama.free.verse</val>, in order to address
the verse of Behn which is not in regular iambic pentameter. For the time being these
instances are marked with a comment note until we are able to fully consider the best way
to encode these instances.</note>
</change>
<change n="RCS:1.33" when="2007-06-28"
who="#pcaton.xzc">Added <att>key</att> and <att>reg</att>
to <gi>name</gi>s.</change>
<change n="RCS:1.31" when="2006-12-04"
who="#wgui.ner">Completed renovation. Validated.</change>
</revisionDesc>
2.7 Minimal and Recommended Headers
<teiHeader>
<fileDesc>
<titleStmt>
<title>Common sense, a machine-readable transcript</title>
<author>Paine, Thomas (1737-1809)</author>
<respStmt>
<resp>compiled by</resp>
<name>Jon K Adams</name>
</respStmt>
</titleStmt>
<editionStmt>
<edition>
<date>1986</date>
</edition>
</editionStmt>
<publicationStmt>
<distributor>Oxford Text Archive.</distributor>
<address>
<addrLine>Oxford University Computing Services,</addrLine>
<addrLine>13 Banbury Road,</addrLine>
<addrLine>Oxford OX2 6RB,</addrLine>
<addrLine>UK</addrLine>
</address>
</publicationStmt>
<notesStmt>
<note>Brief notes on the text are in a
supplementary file.</note>
</notesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<editor>Foner, Philip S.</editor>
<title>The collected writings of Thomas Paine</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Citadel Press</publisher>
<date>1945</date>
</imprint>
</monogr>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<samplingDecl>
<p>Editorial notes in the Foner edition have not
been reproduced. </p>
<p>Blank lines and multiple blank spaces, including paragraph
indents, have not been preserved. </p>
</samplingDecl>
<editorialDecl>
<correction status="high"
method="silent">
<p>The following errors
in the Foner edition have been corrected:
<list>
<item>p. 13 l. 7 cotemporaries contemporaries</item>
<item>p. 28 l. 26 [comma] [period]</item>
<item>p. 84 l. 4 kin kind</item>
<item>p. 95 l. 1 stuggle struggle</item>
<item>p. 101 l. 4 certainy certainty</item>
<item>p. 167 l. 6 than that</item>
<item>p. 209 l. 24 publshed published</item>
</list>
</p>
</correction>
<normalization>
<p>No normalization beyond that performed
by Foner, if any. </p>
</normalization>
<quotation marks="all">
<p>All double quotation marks
rendered with ", all single quotation marks with
apostrophe. </p>
</quotation>
<hyphenation eol="none">
<p>Hyphenated words that appear at the
end of the line in the Foner edition have been reformed.</p>
</hyphenation>
<stdVals>
<p>The values of <att>when-iso</att> on the <gi>time</gi>
element always end in the format <val>HH:MM</val> or
<val>HH</val>; i.e., seconds, fractions thereof, and time
zone designators are not present.</p>
</stdVals>
<interpretation>
<p>Compound proper names are marked. </p>
<p>Dates are marked. </p>
<p>Italics are recorded without interpretation. </p>
</interpretation>
</editorialDecl>
<classDecl>
<taxonomy xml:id="lcsh">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
<taxonomy xml:id="lc">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<creation>
<date>1774</date>
</creation>
<langUsage>
<language ident="en" usage="100">English.</language>
</langUsage>
<textClass>
<keywords scheme="#lcsh">
<term>Political science</term>
<term>United States -- Politics and government —
Revolution, 1775-1783</term>
</keywords>
<classCode scheme="#lc">JC 177</classCode>
</textClass>
</profileDesc>
<revisionDesc>
<change when="1996-01-22" who="#MSM"> finished proofreading </change>
<change when="1995-10-30" who="#LB"> finished proofreading </change>
<change notBefore="1995-07-04" who="#RG"> finished data entry at end of term </change>
<change notAfter="1995-01-01" who="#RG"> began data entry before New Year 1995 </change>
</revisionDesc>
</teiHeader>
<fileDesc>
<titleStmt>
<title>Common sense, a machine-readable transcript</title>
<author>Paine, Thomas (1737-1809)</author>
<respStmt>
<resp>compiled by</resp>
<name>Jon K Adams</name>
</respStmt>
</titleStmt>
<editionStmt>
<edition>
<date>1986</date>
</edition>
</editionStmt>
<publicationStmt>
<distributor>Oxford Text Archive.</distributor>
<address>
<addrLine>Oxford University Computing Services,</addrLine>
<addrLine>13 Banbury Road,</addrLine>
<addrLine>Oxford OX2 6RB,</addrLine>
<addrLine>UK</addrLine>
</address>
</publicationStmt>
<notesStmt>
<note>Brief notes on the text are in a
supplementary file.</note>
</notesStmt>
<sourceDesc>
<biblStruct>
<monogr>
<editor>Foner, Philip S.</editor>
<title>The collected writings of Thomas Paine</title>
<imprint>
<pubPlace>New York</pubPlace>
<publisher>Citadel Press</publisher>
<date>1945</date>
</imprint>
</monogr>
</biblStruct>
</sourceDesc>
</fileDesc>
<encodingDesc>
<samplingDecl>
<p>Editorial notes in the Foner edition have not
been reproduced. </p>
<p>Blank lines and multiple blank spaces, including paragraph
indents, have not been preserved. </p>
</samplingDecl>
<editorialDecl>
<correction status="high"
method="silent">
<p>The following errors
in the Foner edition have been corrected:
<list>
<item>p. 13 l. 7 cotemporaries contemporaries</item>
<item>p. 28 l. 26 [comma] [period]</item>
<item>p. 84 l. 4 kin kind</item>
<item>p. 95 l. 1 stuggle struggle</item>
<item>p. 101 l. 4 certainy certainty</item>
<item>p. 167 l. 6 than that</item>
<item>p. 209 l. 24 publshed published</item>
</list>
</p>
</correction>
<normalization>
<p>No normalization beyond that performed
by Foner, if any. </p>
</normalization>
<quotation marks="all">
<p>All double quotation marks
rendered with ", all single quotation marks with
apostrophe. </p>
</quotation>
<hyphenation eol="none">
<p>Hyphenated words that appear at the
end of the line in the Foner edition have been reformed.</p>
</hyphenation>
<stdVals>
<p>The values of <att>when-iso</att> on the <gi>time</gi>
element always end in the format <val>HH:MM</val> or
<val>HH</val>; i.e., seconds, fractions thereof, and time
zone designators are not present.</p>
</stdVals>
<interpretation>
<p>Compound proper names are marked. </p>
<p>Dates are marked. </p>
<p>Italics are recorded without interpretation. </p>
</interpretation>
</editorialDecl>
<classDecl>
<taxonomy xml:id="lcsh">
<bibl>Library of Congress Subject Headings</bibl>
</taxonomy>
<taxonomy xml:id="lc">
<bibl>Library of Congress Classification</bibl>
</taxonomy>
</classDecl>
</encodingDesc>
<profileDesc>
<creation>
<date>1774</date>
</creation>
<langUsage>
<language ident="en" usage="100">English.</language>
</langUsage>
<textClass>
<keywords scheme="#lcsh">
<term>Political science</term>
<term>United States -- Politics and government —
Revolution, 1775-1783</term>
</keywords>
<classCode scheme="#lc">JC 177</classCode>
</textClass>
</profileDesc>
<revisionDesc>
<change when="1996-01-22" who="#MSM"> finished proofreading </change>
<change when="1995-10-30" who="#LB"> finished proofreading </change>
<change notBefore="1995-07-04" who="#RG"> finished data entry at end of term </change>
<change notAfter="1995-01-01" who="#RG"> began data entry before New Year 1995 </change>
</revisionDesc>
</teiHeader>
3 Elements Available in All TEI Documents
3.11.4 Declaring Reference Systems
<encodingDesc>
<refsDecl>
<cRefPattern matchPattern="([^ ]+) ([0-9]+)\.([0-9]+)\.([0-9]+)"
replacementPattern="#xpath(//div1[@n='$1']/div2[@n='$2']/div3[@n='$3']/l[@n='$4']">
<p>A canonical reference is assembled with
<list>
<item>the name of the <label>work</label>: the
<att>n</att> of a <gi>div1</gi>,</item>
<item>a space,</item>
<item>the number of the <label>book</label>: the
<att>n</att> of a child <gi>div2</gi>,</item>
<item>a full stop</item>
<item>the number of the <label>poem</label>: the
<att>n</att> of a child <gi>div3</gi>,</item>
<item>the line number: the <att>n</att> value of a
child <gi>l</gi>
</item>
</list>
</p>
</cRefPattern>
<cRefPattern matchPattern="([^ ]+) ([0-9]+)\.([0-9]+)"
replacementPattern="#xpath(//div1[@n='$1']/div2[@n='$2']/div3[@n='$3']">
<p>Same as above, but without the last component (full
stop followed by the <gi>l</gi>'s <att>n</att>.</p>
</cRefPattern>
<cRefPattern matchPattern="([^ ]+) ([0-9]+)"
replacementPattern="#xpath(//div1[@n='$1']/div2[@n='$2']">
<p>Same as above, but without the poem component (full
stop followed by the <gi>div3</gi>'s <att>n</att>.</p>
</cRefPattern>
</refsDecl>
</encodingDesc>
<refsDecl>
<cRefPattern matchPattern="([^ ]+) ([0-9]+)\.([0-9]+)\.([0-9]+)"
replacementPattern="#xpath(//div1[@n='$1']/div2[@n='$2']/div3[@n='$3']/l[@n='$4']">
<p>A canonical reference is assembled with
<list>
<item>the name of the <label>work</label>: the
<att>n</att> of a <gi>div1</gi>,</item>
<item>a space,</item>
<item>the number of the <label>book</label>: the
<att>n</att> of a child <gi>div2</gi>,</item>
<item>a full stop</item>
<item>the number of the <label>poem</label>: the
<att>n</att> of a child <gi>div3</gi>,</item>
<item>the line number: the <att>n</att> value of a
child <gi>l</gi>
</item>
</list>
</p>
</cRefPattern>
<cRefPattern matchPattern="([^ ]+) ([0-9]+)\.([0-9]+)"
replacementPattern="#xpath(//div1[@n='$1']/div2[@n='$2']/div3[@n='$3']">
<p>Same as above, but without the last component (full
stop followed by the <gi>l</gi>'s <att>n</att>.</p>
</cRefPattern>
<cRefPattern matchPattern="([^ ]+) ([0-9]+)"
replacementPattern="#xpath(//div1[@n='$1']/div2[@n='$2']">
<p>Same as above, but without the poem component (full
stop followed by the <gi>div3</gi>'s <att>n</att>.</p>
</cRefPattern>
</refsDecl>
</encodingDesc>
13 Names, Dates, People, and Places
<event from="2019-09-16" to="2019-09-20"
xml:id="tei2019graz">
<eventName type="full">TEI 2019: What is text, really? TEI and beyond</eventName>
<eventName type="short">TEI 2019</eventName>
<note> The abstract leading to the <gi>eventName</gi> element is available at <ref target="https://gams.uni-graz.at/o:tei2019.141">https://gams.uni-graz.at/o:tei2019.141</ref>.
Other related documents are available through <ref target="https://gams.uni-graz.at/tei2019">https://gams.uni-graz.at/tei2019</ref>, as well as in the
<ref target="https://zenodo.org/communities/tei2019">TEI 2019 Zenodo community</ref>.
</note>
<listPerson type="LocalOrganisers">
<person>
<persName>
<surname>Raunig</surname>
<forename>Elisabeth</forename>
</persName>
</person>
<person>
<persName>
<surname>Scholger</surname>
<forename>Martina</forename>
</persName>
</person>
<person>
<persName>
<surname>Scholger</surname>
<forename>Walter</forename>
</persName>
</person>
<person>
<persName>
<surname>Steiner</surname>
<forename>Elisabeth</forename>
</persName>
</person>
<person>
<persName>
<surname>Vogeler</surname>
<forename>Georg</forename>
</persName>
</person>
</listPerson>
<place xml:lang="de">
<placeName>Universität Graz</placeName>
<location>
<address>
<addrLine>ReSoWi Gebäude</addrLine>
<addrLine>Universitätsstratheße 15</addrLine>
<postCode>8010</postCode>
<settlement>Graz</settlement>
<country>Österreich</country>
</address>
<geo>15.451651587656 47.078215112534</geo>
</location>
</place>
<listRelation>
<relation active="#tei2019graz"
passive="#AnnualTEIConference" type="CRM" name="P31_is_instance_of"
ref="https://www.wikidata.org/wiki/Property:P31"/>
</listRelation>
</event>
xml:id="tei2019graz">
<eventName type="full">TEI 2019: What is text, really? TEI and beyond</eventName>
<eventName type="short">TEI 2019</eventName>
<note> The abstract leading to the <gi>eventName</gi> element is available at <ref target="https://gams.uni-graz.at/o:tei2019.141">https://gams.uni-graz.at/o:tei2019.141</ref>.
Other related documents are available through <ref target="https://gams.uni-graz.at/tei2019">https://gams.uni-graz.at/tei2019</ref>, as well as in the
<ref target="https://zenodo.org/communities/tei2019">TEI 2019 Zenodo community</ref>.
</note>
<listPerson type="LocalOrganisers">
<person>
<persName>
<surname>Raunig</surname>
<forename>Elisabeth</forename>
</persName>
</person>
<person>
<persName>
<surname>Scholger</surname>
<forename>Martina</forename>
</persName>
</person>
<person>
<persName>
<surname>Scholger</surname>
<forename>Walter</forename>
</persName>
</person>
<person>
<persName>
<surname>Steiner</surname>
<forename>Elisabeth</forename>
</persName>
</person>
<person>
<persName>
<surname>Vogeler</surname>
<forename>Georg</forename>
</persName>
</person>
</listPerson>
<place xml:lang="de">
<placeName>Universität Graz</placeName>
<location>
<address>
<addrLine>ReSoWi Gebäude</addrLine>
<addrLine>Universitätsstratheße 15</addrLine>
<postCode>8010</postCode>
<settlement>Graz</settlement>
<country>Österreich</country>
</address>
<geo>15.451651587656 47.078215112534</geo>
</location>
</place>
<listRelation>
<relation active="#tei2019graz"
passive="#AnnualTEIConference" type="CRM" name="P31_is_instance_of"
ref="https://www.wikidata.org/wiki/Property:P31"/>
</listRelation>
</event>
16 Linking, Segmentation, and Alignment
16.2.3 Using Abbreviated Pointers
<listPrefixDef>
<prefixDef ident="psn"
matchPattern="([a-z]+)"
replacementPattern="../../references/people/personography.xml#$1">
<p> In the context of this project, private URIs with the prefix
"psn" point to <gi>person</gi> elements in the project's
personography.xml file.
</p>
</prefixDef>
</listPrefixDef>
<prefixDef ident="psn"
matchPattern="([a-z]+)"
replacementPattern="../../references/people/personography.xml#$1">
<p> In the context of this project, private URIs with the prefix
"psn" point to <gi>person</gi> elements in the project's
personography.xml file.
</p>
</prefixDef>
</listPrefixDef>
21 Certainty, Precision, and Responsibility
<!-- 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="delivery" xml: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>