Example: <val> (value)

These search results reproduce every example of the use of <val> 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 <val> 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.

22 Documentation Elements


22.1.1 Phrase Level Terms

<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>

<egXML>

<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 in the TEI namespace can be
       used for recording how parts of the example was 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 in the TEI namespace can be
       used for recording how parts of the example was rendered.</item>
  </list>
</div>

<val>

<val>unknown</val>

<val>

<val>inconnu</val>

<val>

<val>未知</val>

<attDef>

<attDef usage="recident="type">
 <desc>specifies a name conventionally used for this level of subdivision, e.g.
 <val>act</val>, <val>volume</val>, <val>book</val>, <val>section</val>, <val>canto</val>,
   etc.</desc>
 <datatype>
  <rng:text/>
 </datatype>
</attDef>

<attDef>

<attDef usage="recident="type">
 <desc>spécifie un nom conventionnellement utilisé pour ce niveau de divisions , par ex.
 <val>acte</val>, <val>volume</val>, <val>livre</val>, <val>section</val>,
 <val>chant</val>, etc.</desc>
 <datatype>
  <rng:text/>
 </datatype>
</attDef>

<attDef>

<attDef usage="recident="type">
 <desc>具體指定慣例上使用的分部名稱,例如:
 <val></val>, <val></val>, <val></val>, <val></val>, <val>篇章</val>,
   等。</desc>
 <datatype>
  <rng:text/>
 </datatype>
</attDef>

2 The TEI Header


2.5 The Revision Description


<!-- ... --><revisionDesc>
 <change n="RCS:1.39when="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.33when="2007-06-28"
  who="#pcaton.xzc">
Added <att>key</att> and <att>reg</att>
   to <gi>name</gi>s.</change>
 <change n="RCS:1.31when="2006-12-04"
  who="#wgui.ner">
Completed renovation. Validated.</change>
</revisionDesc>

2.6 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="enusage="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-22who="#MSM"> finished proofreading </change>
  <change when="1995-10-30who="#LB"> finished proofreading </change>
  <change notBefore="1995-07-04who="#RG"> finished data entry at end of term </change>
  <change notAfter="1995-01-01who="#RG"> began data entry before New Year 1995 </change>
 </revisionDesc>
</teiHeader>

16 Linking, Segmentation, and Alignment


16.2.5.2 Complete and Partial URI Examples

<refsDecl xml:id="USC">
 <cRefPattern matchPattern="([0-9][0-9])\s*U\.?S\.?C\.?\s*[Cc](h(\.|ap(ter|\.)?)?)?\s*([1-9][0-9]*)"
  replacementPattern="http://uscode.house.gov/download/pls/$1C$5.txt">

  <p>Matches most standard references to particular
     chapters of the United States Code, e.g.
  <val>11USCC7</val>, <val>17 U.S.C. Chapter 3</val>, or
  <val>14 USC Ch. 5</val>. Note that a leading zero is
     required for the title (must be two digits), but is not
     permitted for the chapter number.</p>
 </cRefPattern>
 <cRefPattern matchPattern="([0-9][0-9])\s*U\.?S\.?C\.?\s*[Pp](re(lim(inary)?)?)?\s*[Mm](at(erial)?)?"
  replacementPattern="http://uscode.house.gov/download/pls/$1T.txt">

  <p>Matches references to the preliminary material for a
     given title, e.g. <val>11USCP</val>, <val>17 U.S.C.
       Prelim Mat</val>, or <val>14 USC pm</val>.</p>
 </cRefPattern>
 <cRefPattern matchPattern="([0-9][0-9])\s*U\.?S\.?C\.?\s*[Aa](ppend(ix)?)?"
  replacementPattern="http://uscode.house.gov/download/pls/$1A.txt">

  <p>Matches references to the appendix of a given tile,
     e.g. <val>05USCA</val>, <val>11 U.S.C. Appendix</val>,
     or <val>18 USC Append</val>.</p>
 </cRefPattern>
</refsDecl>
<!-- ... -->
<p>The example in section 10 is taken
from <ref cRef="17 USC Ch 1">Subject Matter and Scope of
   Copyright</ref>.</p>