Exemple: <dataSpec> (datatype specification)
These search results reproduce every example of the use of <dataSpec> 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 <dataSpec> 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
<dataSpec> (en)
<dataSpec ident="teidata.pointer">
<desc versionDate="2013-01-19"
xml:lang="en">defines the range of
attribute values used to provide a single URI, absolute or relative,
pointing to some other resource, either within the current document
or elsewhere.</desc>
<content>
<dataRef name="anyURI"/>
</content>
</dataSpec>
<desc versionDate="2013-01-19"
xml:lang="en">defines the range of
attribute values used to provide a single URI, absolute or relative,
pointing to some other resource, either within the current document
or elsewhere.</desc>
<content>
<dataRef name="anyURI"/>
</content>
</dataSpec>
<dataRef> (en)
<dataSpec ident="data.integerExample">
<desc>datatype used for attributes taking an integer value between 0 and 99</desc>
<content>
<dataRef name="nonNegativeInteger"
restriction="[0-9][0-9]?"/>
</content>
</dataSpec>
<desc>datatype used for attributes taking an integer value between 0 and 99</desc>
<content>
<dataRef name="nonNegativeInteger"
restriction="[0-9][0-9]?"/>
</content>
</dataSpec>
<dataFacet> (en)
<dataSpec ident="data.integerExample">
<desc>datatype used for attributes taking an integer value between 0 and 99</desc>
<content>
<dataRef name="nonNegativeInteger">
<dataFacet name="maxInclusive"
value="99"/>
<dataFacet name="minInclusive" value="0"/>
</dataRef>
</content>
</dataSpec>
<desc>datatype used for attributes taking an integer value between 0 and 99</desc>
<content>
<dataRef name="nonNegativeInteger">
<dataFacet name="maxInclusive"
value="99"/>
<dataFacet name="minInclusive" value="0"/>
</dataRef>
</content>
</dataSpec>
3 Elements Available in All TEI Documents
<desc> (en)
<dataSpec module="tei"
ident="teidata.point" validUntil="2050-02-25">
<desc type="deprecationInfo"
versionDate="2018-09-14" xml:lang="en">Several standards bodies, including NIST in the USA,
strongly recommend against ending the representation of a number
with a decimal point. So instead of <q>3.</q> use either <q>3</q>
or <q>3.0</q>.</desc>
<!-- ... -->
</dataSpec>
ident="teidata.point" validUntil="2050-02-25">
<desc type="deprecationInfo"
versionDate="2018-09-14" xml:lang="en">Several standards bodies, including NIST in the USA,
strongly recommend against ending the representation of a number
with a decimal point. So instead of <q>3.</q> use either <q>3</q>
or <q>3.0</q>.</desc>
<!-- ... -->
</dataSpec>
<desc> (en)
<dataSpec module="tei"
ident="teidata.point">
<desc versionDate="2010-10-17"
xml:lang="en">defines the data type used to express a point in cartesian space.</desc>
<content>
<dataRef name="token"
restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
<!-- ... -->
</dataSpec>
ident="teidata.point">
<desc versionDate="2010-10-17"
xml:lang="en">defines the data type used to express a point in cartesian space.</desc>
<content>
<dataRef name="token"
restriction="(-?[0-9]+(\.[0-9]+)?,-?[0-9]+(\.[0-9]+)?)"/>
</content>
<!-- ... -->
</dataSpec>