This document defines the 'application/tei+xml' media type for markup languages defined in accordance with the Text Encoding and Interchange guidelines
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”
This Internet-Draft will expire on October 10, 2010.
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
2. Registration of MIME type 'application/tei+xml'
3. Recognizing TEI files
4. Fragment identifier
5. Security considerations
6. IANA Considerations
7. Normative References
§ Authors' Addresses
The 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. [TEI] (, “TEI Guidelines,” .)
In order to increase the possibilities for generic XML processing this document defines the 'application/tei+xml' media type in accordance with [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).
MIME media type name: application
MIME subtype name: tei+xml
Required parameters: None
Optional parameters: charset
Identical with charset in [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.)
By virtue of TEI XML content being XML, it has the same considerations when sent as 'application/tei+xml' as does XML in general. See RFC 3023 [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.), Section 3.2.
TEI elements may refer to arbitrary URIs. Hence the security issues of [RFC3986] (Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.), section 7, apply. See also Security considerations (Security considerations)
Interoperability considerations: None.
This media type registration is for TEI documents as described in the TEI Guidelines[TEI] (, “TEI Guidelines,” .).
Applications which use this media type:
There are currently no applications using the media type 'application/tei+xml'. It will be an entirely new type which is registered in order to allow for the deployment of TEI on the World Wide Web as a first class XML application.
There is no single initial octet sequence that is always present in TEI documents.
TEI documents have most often the extension '.xml'. Other common extensions are '.tei', '.teiCorpus' and '.odd'.
Macintosh File Type Code(s)
Object Identifier(s) or OID(s)
TEI files are XML documents or fragments having the root element in a TEI namespace, i.e., a namespace URI starting with http://www.tei-c.org/ns/. This URI is followed by a version number, corresponding to the major release of the TEI schema. The current namespace is http://www.tei-c.org/ns/1.0
In general, a [TEI] (, “TEI Guidelines,” .) file usually contains either of the strings
near the beginning.
Frequently, the actual XML content of TEI files will contain <TEI somewhere early on.
More specialized types of documents may start with a lower case tei as in <teiCorpus.
Documents having the media type 'application/tei+xml', use the fragment identifier notation in the same way as does 'application/xml'. This is specified in [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.) or its successors.
An XML resource identifier does not in itself compromise data security. When converted to IRIs or URIs and used to provide access to network resources, care must be taken to properly interpret the data to prevent unintended access.
Any application accepting submitted or retrieves TEI XML for processing has to be aware of risks connected with injection of harmful scripts and executable XML. Even common XML inclusion or the use of external entities, could potentially be used to reveal aspects of a service that may compromise its security. Any vulnerability of these kinds are, however, application specific. The TEI namespaces do not contain such elements.
Registration of MIME type 'application/tei+xml' (Registration of MIME type 'application/tei+xml')
|[RFC3023]||Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” RFC 3023, January 2001 (TXT).|
|[RFC3986]||Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” STD 66, RFC 3986, January 2005 (TXT, HTML, XML).|
|TEI Consortium and INRIA|
|The Royal Library, Copenhagen|
|1016 København K|