The 'application/tei+xml' mediatype
draft-lundberg-app-tei-xml-01

Abstract

This document defines the 'application/tei+xml' media type for markup languages defined in accordance with the Text Encoding and Interchange guidelines

Status of this Memo

This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

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.”

The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.

This Internet-Draft will expire on September 30, 2010.

Copyright Notice

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 BSD License.

Table of Contents

1.  Introduction
2.  Registration of MIME type 'application/tei+xml'
3.  Recognizing TEI files
4.  Fragment identifier
5.  Security considerations
6.  Normative References
§  Authors' Addresses

1.  Introduction

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.)

2.  Registration of MIME type 'application/tei+xml'

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.)

Encoding considerations:

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.

Security considerations:

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.

Interoperability considerations: None.

Published specification:

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.

Additional information:

Magic number(s):

There is no single initial octet sequence that is always present in TEI documents.

file extension(s):

TEI documents have most often the extension '.xml'. Other common extensions are '.tei', '.teiCorpus' and '.odd'.

Macintosh File Type Code(s)

TEXT

Object Identifier(s) or OID(s)

Not applicable

3.  Recognizing TEI files

A [TEI] (, “TEI Guidelines,” .) file usually contains either of the strings

<tei

<TEI

near the beginning.

Examples: Older versions of the standard may start with <TEI.2, more recent ones with <TEI. More specialized types of documents may start with <teiCorpus.

4.  Fragment identifier

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.

5.  Security considerations

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.

6. Normative References

Authors' Addresses