Difference between revisions of "TEI for ISO"
(New page: = Using the TEI for Editing ISO documents = == Basic principles == Most of the necessary documentation for using the giudelines in specific contexts can be found under: [http://www.tei-c...) |
m (→Basic principles: another typo) |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
== Basic principles == | == Basic principles == | ||
| − | Most of the necessary documentation for using the | + | Most of the necessary documentation for using the guidelines in specific contexts can be found under: [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html]. |
| + | |||
| + | Looking between the lines at [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html#STPE], one can also get advice as to how to integrate a TEI component within a third party DTD or schema. | ||
| + | |||
| + | |||
| + | === Terms and definition === | ||
| + | |||
| + | The term and definition section should be represented as a list of items: | ||
| + | |||
| + | <div n="3" type="termsAndDefinitions"> | ||
| + | <head>Terms and definitions</head> | ||
| + | <list type="termlist"> | ||
| + | <item/> | ||
| + | </list> | ||
| + | </div> | ||
| + | |||
| + | Each item should have the following structure: | ||
| + | <item xml:id="stateOfTheArt" n="3.13"> | ||
| + | <term>state of the art</term> | ||
| + | <gloss>developed stage of technical capability at a given time as regards | ||
| + | products, processes and services, based on the relevant consolidated | ||
| + | findings of science, technology and experience</gloss> | ||
| + | <ref>ISO/IEC Guide 2:2004, definition 1.4</ref> | ||
| + | </item> | ||
| + | |||
| + | |||
| + | Abbreviation should be represented by means of an <abbr> following the corresponding <term> | ||
| + | Additional terms for the same concepts should be represented as <term>'s following the main entry. | ||
== Using TEI modules in ISO specification (and others...) == | == Using TEI modules in ISO specification (and others...) == | ||
| Line 18: | Line 45: | ||
<moduleRef key="iso-fs"/> | <moduleRef key="iso-fs"/> | ||
</schemaSpec> | </schemaSpec> | ||
| + | |||
| + | |||
| + | == Using Vesta to compile ISO document == | ||
| + | |||
| + | |||
| + | === Bugs and feature requests === | ||
| + | |||
| + | * figures in docx outputs do not appear | ||
| + | * xml tags within egXML do not appear in the HTML output | ||
| + | * generating anchors | ||
== Linking to ISO cat == | == Linking to ISO cat == | ||
| + | |||
| + | List of references to data categories as [http://www.isocat.org/ ISOCat] entries at the end of an ISO standards are represented along a pattern close to that of terminological entries: | ||
| + | |||
| + | <item xml:id="DCn" dcr:datcat="http://www.isocat.org/datcat/ISO-DC-n"> | ||
| + | <term>abbreviation</term> | ||
| + | <gloss>Designation formed by omitting words or letters from a longer form | ||
| + | and refering to the same concept.</gloss> | ||
| + | </item> | ||
| + | |||
| + | The dcr prefix should be associated with the name space: http://www.isocat.org/ns/dcr | ||
| + | |||
| + | Work is ongoing to provide a TEI export to ISOCat that would allow one to embed a DCS (Data Category Selection) expressed as a list of items automatically. | ||
| + | |||
| + | http://www.isocat.org/12620/schemas/DCIF.html | ||
| + | |||
| + | http://www.isocat.org/rest/help.html#dcs | ||
Latest revision as of 03:18, 25 November 2013
Contents
Using the TEI for Editing ISO documents
Basic principles
Most of the necessary documentation for using the guidelines in specific contexts can be found under: [1].
Looking between the lines at [2], one can also get advice as to how to integrate a TEI component within a third party DTD or schema.
Terms and definition
The term and definition section should be represented as a list of items:
<head>Terms and definitions</head>
<list type="termlist">
<item/>
</list>
Each item should have the following structure:
<item xml:id="stateOfTheArt" n="3.13">
<term>state of the art</term>
<gloss>developed stage of technical capability at a given time as regards
products, processes and services, based on the relevant consolidated
findings of science, technology and experience</gloss>
<ref>ISO/IEC Guide 2:2004, definition 1.4</ref>
</item>
Abbreviation should be represented by means of an following the corresponding <term>
Additional terms for the same concepts should be represented as <term>'s following the main entry.
Using TEI modules in ISO specification (and others...)
Feature structures
The relaxNg schema for representing feature structures is available under [3].
This can be generated directly by means of the following ODD declaration:
<schemaSpec ident="testjustfs" start="">
<moduleRef key="tei"/>
<moduleRef key="iso-fs"/>
</schemaSpec>
Using Vesta to compile ISO document
Bugs and feature requests
- figures in docx outputs do not appear
- xml tags within egXML do not appear in the HTML output
- generating anchors
Linking to ISO cat
List of references to data categories as ISOCat entries at the end of an ISO standards are represented along a pattern close to that of terminological entries:
<item xml:id="DCn" dcr:datcat="http://www.isocat.org/datcat/ISO-DC-n"> <term>abbreviation</term> <gloss>Designation formed by omitting words or letters from a longer form and refering to the same concept.</gloss> </item>
The dcr prefix should be associated with the name space: http://www.isocat.org/ns/dcr
Work is ongoing to provide a TEI export to ISOCat that would allow one to embed a DCS (Data Category Selection) expressed as a list of items automatically.
