Discussion item for

[Fabio Vitali <fvitali@gmail.com>]

Dear all, 

please find a text for the request of the assignation of a MIME type to Akoma Ntoso documents. 

Ciao

Fabio


--

Fabio Vitali                            Tiger got to hunt, bird got to fly,
Dept. of Computer Science        Man got to sit and wonder "Why, why, why?'
Univ. of Bologna  ITALY               Tiger got to sleep, bird got to land,
phone:  +39 051 2094872              Man got to tell himself he understand.
e-mail: fabio@cs.unibo.it         Kurt Vonnegut (1922-2007), "Cat's cradle"
http://vitali.web.cs.unibo.it/




Internet Engineering Task Force (IETF)                         F. Vitali
Request for Comments: XXXX                         University of Bologna
Category: Informational                                     M. Palmirani
ISSN: XXXXXX                                       University of Bologna
                                                             August 2014

                  The 'application/akn+xml' Media Type

Abstract

   This document defines the 'application/akn+xml' media type for 
   documents defined in accordance with the OASIS LegalDocML markup 
   language Akoma Ntoso.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6129.

Copyright Notice

   Copyright (c) 2014 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
   2.  Recognizing Akoma Ntoso Files . . . . . . . . . . . . . . . . . 2
   3.  Fragment Identifier . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
     4.1.  Harmful Content . . . . . . . . . . . . . . . . . . . . . . 4
     4.2.  Intellectual Property Rights  . . . . . . . . . . . . . . . 4
     4.3.  Authenticity and confidentiality  . . . . . . . . . . . . . 5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
     5.1.  Registration of MIME Type 'application/akn+xml' . . . . . . 5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 7

1.  Introduction

   Akoma Ntoso is an international and standard that is widely used by libraries, museums,
   publishers, and individual scholars to represent all kinds of textual
   material for online research and teaching [AKN].

   This document defines the 'application/akn+xml' media type in
   accordance with [RFC3023] in order to enable generic processing of
   such documents on the Internet using eXtensible Markup Language (XML)
   [W3C.REC-xml-20081126] technologies.

2.  Recognizing Akoma Ntoso Files

   Akoma Ntoso files are XML documents or fragments having the root element (as
   defined in [W3C.REC-xml-20081126]) in an Akoma Ntoso namespace.  Akoma Ntoso namespace
   names are defined as a Universal Resource Identifier (URI) [RFC3986]
   in accordance with [W3C.REC-xml-names-20091208] and begins with
   XXX or XXX followed by the version number of the
   namespace.  The current namespace is XXX

   The root element name for Akoma Ntoso documents is

Example: A document having root element ... ... Akoma Ntoso files are often given the extensions .akn. 3. Fragment Identifier Documents having the media type 'application/akn+xml' use the fragment identifier notation as specified in [RFC3023] for the media type 'application/xml'. 4. Security Considerations 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) [RFC3987] or a URI, care must be taken to properly interpret the data to prevent unintended access. Hence the security issues of [RFC3986], Section 7, apply. In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in RFC 3023 [RFC3023], Section 10. In general, security issues related to the use of XML in IETF protocols are treated in RFC 3470 [RFC3470], 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. 4.1. Harmful Content Any application accepting submitted or retrieving Akoma Ntoso XML for processing has to be aware of risks connected with injection of harmful scripts and executable XML. XML inclusion [W3C.REC-xinclude-20061115] and the use of external entities are vulnerable to various forms of spoofing, and 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 Akoma Ntoso namespaces do not contain such elements. 4.2. Intellectual Property Rights Akoma Ntoso documents often arise in digitization of legal documents and legislative documents. Texts made accessible in Akoma Ntoso format may be unrestricted in the sense that their distribution may be unlimited by Digital Rights Management [DRM] or Intellectual Property Rights [IPR] constraints. However, Akoma Ntoso documents are heterogeneous. Some parts of a document may be unrestricted, whereas others, such as editorial text and annotations, may be subject to DRM restrictions. The Akoma Ntoso format provides means for highly granular attribution, down to the content of individual XML elements. Software agents participating in the exchange or processing Akoma Ntoso may be required to honour markup of this kind. Even when there are no IPR constraints, intellectual property attribution alone requires that document users be able to tell the difference between content from different sources. 4.3. Authenticity and confidentiality Legal and legislative documents may be binding centuries after they were written. Digitization and encoding of such texts may require technologies for assuring authenticity, such as cryptographic checksums and electronic signatures. Similarly, such 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. 5. IANA Considerations 5.1. Registration of MIME Type 'application/akn+xml' MIME media type name: application MIME subtype name: akn+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 [RFC3023]. Encoding considerations: Identical to those for 'application/xml'. See RFC 3023 [RFC3023], Section 3.2. Security considerations: See Security Considerations (Section 4) in this specification. Interoperability considerations: Akoma Ntoso documents are often given the extension '.xml', which is not uncommon for other XML document formats. Published specification: This media type registration is for Akoma Ntoso documents [AKN] as described here. Akoma Ntoso syntax is defined in a schema [AKNschema]. Applications which use this media type: There are currently no known applications using the media type 'application/akn+xml'. Additional information: Magic number(s): There is no single initial octet sequence that is always present in Akoma Ntoso documents. file extension(s): Common extension is '.akn'. See Recognizing Akoma Ntoso files (Section 2) in this specification. Macintosh File Type Code(s) TEXT Object Identifier(s) or OID(s) Not applicable 6. References 6.1. Normative References [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001. [RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols", BCP 70, RFC 3470, January 2003. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource Identifiers (IRIs)", RFC 3987, January 2005. [AKN] XXX [AKNschema] XXX [W3C.REC-xml-20081126] Paoli, J., Yergeau, F., Sperberg-McQueen, C., Maler, E., and T. Bray, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", World Wide Web Consortium Recommendation REC- xml-20081126, November 2008, . [W3C.REC-xml-names-20091208] Bray, T., Hollander, D., Layman, A., Tobin, R., and H. Thompson, "Namespaces in XML 1.0 (Third Edition)", World Wide Web Consortium Recommendation REC-xml-names-20091208, December 2009, . 6.2. Informative References [DRM] "Digital rights management", . [IPR] "Intellectual property", . [W3C.REC-xinclude-20061115] Marsh, J., Orchard, D., and D. Veillard, "XML Inclusions (XInclude) Version 1.0 (Second Edition)", World Wide Web Consortium Recommendation REC-xinclude-20061115, November 2006, . Authors' Addresses Fabio Vitali XXX EMail: XXX URI: XXX Monica Palmirani XXX EMail: XXX URI: XXX