Difference between revisions of "Conformance"

From TEIWiki
Jump to navigation Jump to search
m
(nothing links here; looks like a candidate for deletion to me)
 
(13 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==TEI conformance==
+
[[category:scratchpad]]
 +
==TEI conformance ideas==
  
A document may claim TEI conformance according to 5 levels. Each
+
[ NOTE: This page is '''NOT''' the current or proposed policy of the TEI Consortium!!!!
document should contain a link in its metadata pointing to a
+
It contains some strawman proposals for the TEI Guidelines conformance
'''TEI Conformance Statement''' (TCS) which must provide the following
+
chapter, for the TEI Technical Council to debate. ]
information
 
  
# contact information for the document owner
 
# a URL or URLs for the schema(s) to which the document claims conformance  (this is distinct from any formal link in the document itself used by validating software)
 
# a URL for the ODD specification of the schema, if it is not one of  the existing TEI exemplars
 
  
Where possible, the TCS should be a section within the metadata
+
'''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.'''
of the current document, but may also point to any publicly-available
 
web document.
 
 
 
The conformance levels are as follows:
 
 
 
# The document conforms to the tei_all schema, or any valid subset of  that (ie with fewer elements, tighter datatyping etc).
 
## 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 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 standard TEI (this allows for syntactic sugar, or translated names)
 
# the document conforms to a schema which extends the  TEI element set by manipulation of the TEI class system
 
# 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
 
 
 
In addition to the conformance level, a document will claim AACR
 
compatibility if the elements <TEI> or <teiCorpus>, <teiHeader> and
 
the child elements <title>, <sourceStmt> and <publicationStmt> in the
 
header are retained in the schema
 

Latest revision as of 13:49, 29 January 2009

TEI conformance ideas

[ NOTE: This page is NOT the current or proposed policy of the TEI Consortium!!!! It contains some strawman proposals for the TEI Guidelines conformance chapter, for the TEI Technical Council to debate. ]


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.