<egXML> [http://www.tei-c.org/ns/Examples]

<egXML> (example of XML) contains a single well-formed XML fragment demonstrating the use of some XML element or attribute, in which the egXML element itself functions as the root element. [22.1.1 Phrase Level Terms]
Namespacehttp://www.tei-c.org/ns/Examples
Moduletagdocs — Documentation Elements
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.source (@source)
validindicates the intended validity of the example with respect to a schema.
Status Optional
Datatype

<rng:ref name="data.enumerated"/>
data.enumerated
Legal values are:
true
the example is intended to be fully valid, assuming that its root element, or a provided root element, could have been used as a possible root element in the schema concerned. [Default]
feasible
the example could be transformed into a valid document by inserting any number of valid attributes and child elements anywhere within it; or it is valid against a version of the schema concerned in which the provision of character data, list, element, or attribute values has been made optional.
false
the example is not intended to be valid, and contains deliberate errors.
Member of
Contained by
May containANY
Declaration

<rng:element name="egXML">
 <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.source.attributes"/>
 <rng:optional>
  <rng:attribute name="valid"
   a:defaultValue="true">

   <rng:choice>
    <rng:value>true</rng:value>
    <rng:value>feasible</rng:value>
    <rng:value>false</rng:value>
   </rng:choice>
  </rng:attribute>
 </rng:optional>
 <rng:zeroOrMore>
  <rng:group>
   <rng:choice>
    <rng:text/>
    <rng:ref name="macro.anyXML"/>
   </rng:choice>
  </rng:group>
 </rng:zeroOrMore>
</rng:element>
element egXML
{
   att.global.attributes,
   att.global.linking.attributes,
   att.global.analytic.attributes,
   att.global.facs.attributes,
   att.global.change.attributes,
   att.source.attributes,
   attribute valid { "true" | "feasible" | "false" }?,
   text | macro.anyXML*
}
Example
<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 in the TEI namespace can be used for recording how parts of the example was rendered.</item>       </list> </div> </egXML>   
Example
             <egXML xmlns="http://www.tei-c.org/ns/Examples" valid="feasible">        <text>        <front><!-- front matter for the whole group --></front>        <group>        <text>        <!-- first text -->        </text>        <text>        <!-- second text -->        </text>        </group>       </text>       <!-- This example is not valid TEI, but could be made so by       adding missing components -->     
Example
      <egXML xmlns="http://www.tei-c.org/ns/Examples" valid="false">          <para xml:lang="en">Doubloons are a pirate's best friend</para>       </egXML>       <!-- This example is not TEI at all -->     
Note

In the source of the TEI Guidelines, this element declares itself and its content as belonging to the namespace http://www.tei-c.org/ns/Examples. This enables the content of the element to be validated independently against the TEI scheme. Where this element is used outside this context, a different namespace or none at all may be preferable. The content must however be a well-formed XML fragment or document: where this is not the case, the more general eg element should be used in preference. In a TEI context use of the rend attribute in the TEI namespace, as opposed to the TEI Examples namespace, enables recording of rendition information.