The 'application/tei+xml' mediatype

Text Encoding and Interchange (TEI) is an international and interdisciplinary standard that is widely used by libraries, museums, publishers, and individual scholars to represent all kinds of textual material for online research and teaching. This document defines the 'application/tei+xml' media type in accordance with in order enable generic processing of such documents on the Internet using eXtensible Markup Language (XML) technologies.

TEI files are XML documents or fragments having the root element (as defined in ) in a TEI namespace. TEI namespace names are defined as an Universal Resource Identifier (URI) in accordance with and begins with http://www.tei-c.org/ns/ followed by the version number of the namespace. The current namespace is http://www.tei-c.org/ns/1.0 The most common root element names for TEI documents are <TEI> <teiCorpus> The teiCorpus documents give the possibility to bundle multiple documents into a single file. Examples: A document having <TEI> root element

... ... ]]> A document having <teiCorpus> root element

... ... ... ... second document ... ... third document ... ]]> TEI and teiCorpus files are often given the extensions .tei and .teiCorpus, respectively. There is a third type of file, which often is given the suffix .odd. ODD (‘One Document Does it All’) is a TEI XML document which include schema fragments, prose documentation, and reference documentation. It is used for the definition and documentation of XML based languages, and primarily for the TEI Guidelines. In other words, ODD files does not differ from other TEI file in syntax, only in function.

Documents having the media type 'application/tei+xml', use the fragment identifier notation as specified in for the media type 'application/xml'.

An XML resource does not in itself compromise data security. When being available on a network simply through the dereferencing of an Internationalized Resource Identifier (IRI) or an URI, care must be taken to properly interpret the data to prevent unintended access. Hence the security issues of , section 7, apply. In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in RFC 3023 , section 10. In general, security issues related to the use of XML in IETF protocols are treated in RFC 3470, section 7. We will not try to duplicate this material, but review some aspects that are important for document centric XML as applied to text encoding.

Any application accepting submitted or retrieving TEI XML for processing has to be aware of risks connected with injection of harmful scripts and executable XML. XML inclusion and the use of external entities, are vulnerable to various forms of spoofing but can also reveal aspects of a service in a way that may compromise its security. Any vulnerability of these kinds are, however, application specific. The TEI namespaces do not contain such elements.

TEI documents often arise in digitization of cultural heritage materials. Texts made accessible in TEI format may be unrestricted in the sense that their distribution may be unlimited by Digital Rights Management or Intellectual Property Rights constraints. However, TEI documents are heterogeneous. Some parts of a document may be unrestricted, whereas other, such as editorial text and annotations may be subject to DRM restrictions. The TEI format provides means for highly granular attribution, down to the content of individual XML elements. Software agents participating in the exchange or processing TEI may be required to honour markup of this kind. Even when there are no IPR constraints, intellectual property attribution alone requires that document users are able to tell the difference between content from different sources.

Historical archival records are often encoded in TEI and legal document may be binding centuries after they were written. Digitization and encoding of legal texts may require technologies for assuring authenticity, such as cryptographic check sums and electronic signatures. Similarly, historical documents may in part or in their entirety be confidential. This may be required by law or by the terms and conditions such as in the case of donated or deposited text from private sources. A text archive may need content filtering or cryptographic technologies to meet such requirements.

MIME media type name: application MIME subtype name: tei+xml Required parameters: None Optional parameters: charset the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in RFC 3023 . Encoding considerations: Identical to those for 'application/xml'. See RFC 3023 , Section 3.2. Security considerations: See Security considerations in this specification. Interoperability considerations: TEI documents are often given the extension '.xml', which is not uncommon for other XML document formats. Published specification: This media type registration is for TEI documents as described in here. TEI syntax is defined in a schema. Applications which use this media type: There are currently no known applications using the media type 'application/tei+xml'. Additional information: Magic number(s): There is no single initial octet sequence that is always present in TEI documents. file extension(s): Common extensions are '.tei', '.teiCorpus' and '.odd'. See Recognizing TEI files in this specification. Macintosh File Type Code(s) TEXT Object Identifier(s) or OID(s) Not applicable