|
|
| (5 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| − | ==TEI conformance== | + | [[category:scratchpad]] |
| | + | ==TEI conformance ideas== |
| | | | |
| − | [ NOTE: This page is purely for discussion purposes. | + | [ NOTE: This page is '''NOT''' the current or proposed policy of the TEI Consortium!!!! |
| − | It does not reflect the policy of the TEI Consortium]
| + | It contains some strawman proposals for the TEI Guidelines conformance |
| | + | chapter, for the TEI Technical Council to debate. ] |
| | | | |
| − | TEI-Conformant documents can be of any one of five different '''degrees''' of interchangability. These are as follow. There is a universal exception for any modification, that the TEI namespace may not be omitted or changed,
| |
| − | and the <TEI>, <teiHeader>, and <text> elements may not be removed.
| |
| | | | |
| − | # The document conforms to the tei_all schema, or any valid subset of that (ie with fewer elements, tighter datatyping etc); with the exception that the TEI namespace may not be omitted or changed, the <TEI> element may not be removed, and the <teiHeader> element may not be removed.
| + | '''THE REST OF THIS PAGE HAS BEEN DELETED SINCE THESE ISSUES HAVE SINCE BEEN DEBATED ON THE COUNCIL LIST AND RESULTED IN THE REWRITTEN CHAPTER NOW PART OF TEI P5.''' |
| − | ## The definition of elements may be suppressed, so deleting the associated elements from the modified schema.
| |
| − | ## The name (generic identifier) associated with an element may be changed, while preserving the semantics of the element. Note, however, that the new name may not clash with the default name of any element defined in these Guidelines.
| |
| − | ## An <equiv> element in the ODD should be used to specify the TEI name for such renamed elements.
| |
| − | ## Those parts of the content model of an element which are specified by classes may be extended by adding members to the classes.
| |
| − | ## Further attributes, together with their names and types, may be specified for an individual element and existing attributes for an individual element may be renamed. Note that the new names may not clash with names of existing attributes for the element.
| |
| − | ## Further attributes, together with their names and types, may be specified for the elements in a particular class and those inheriting characteristics from that class.
| |
| − | ## Any derivation from the tei_all schema must be expressed in an accompanying ODD specification
| |
| − | # The document conforms to a schema which adds new elements to the TEI but provides an ODD specification which uses the <equiv> mechanism which explains how to map these to unchanged TEI
| |
| − | # The document conforms to a schema which extends the TEI element set by manipulation of the TEI class system, or extends the content model model of TEI elements to allow elements from other namespaces
| |
| − | # The document conforms to a schema which is based on the TEI but has changed the content model for elements so that normal TEI documents would no longer conform
| |
| − | # The document uses the TEI elements in the TEI namespace, but embeds them within another schema
| |
| − | | |
| − | Documents which use TEI names for elements but do not use the TEI namespace are regarded only as '''TEI-like'''.
| |
| − | | |
| − | In addition to the conformance type, a document may claim AACR
| |
| − | compatibility if the elements <TEI> or <teiCorpus>, <teiHeader> and
| |
| − | the child elements <title>, <sourceStmt> and <publicationStmt> in the
| |
| − | header are retained with those names in the schema.
| |
