Akoma Ntoso MIME Type Version 1.0

Akoma Ntoso MIME Type Version 1.0

Working Draft 01

19 March 2015

Technical Committee:

OASIS LegalDocumentML (LegalDocML) TC

Chairs:

Fabio Vitali (),University of Bologna-CIRSFID

Monica Palmirani (),University of Bologna-CIRSFID

Editors:

Fabio Vitali (), University of Bologna-CIRSFID

Monica Palmirani (), University of Bologna-CIRSFID

Additional artifacts:

This prose specification is one component of a Work Product that also includes:

XML schemas:(list file names or directory name)
Other parts (list titles and/or file names)

Related work:

This specification is related to:

Related specifications (hyperlink, if available)

Declared XML namespace:

Abstract:

Summary of the technical purpose of the document.

Status:

This Working Draft (WD) has been produced by one or more TC Members; it has not yet been voted on by the TC or approved as a Committee Draft (Committee Specification Draft or a Committee Note Draft). The OASIS document Approval Process begins officially with a TC vote to approve a WD as a Committee Draft. A TC may approve a Working Draft, revise it, and re-approve it any number of times as a Committee Draft.

URI patterns:

Initial publication URI:

Permanent “Latest version” URI:

(Managed by OASIS TC Administration; please don’t modify.)

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Table of Contents

1Introduction

1.1 Terminology

1.2 Normative References

1.3 Non-Normative References

2Section Title

2.1 Level 2 section title

2.1.1 Level 3 section title

2.1.1.1 Level 4 section title is usually deepest for Table of Contents

3# Conformance

Appendix A. Acknowledgments

Appendix B. Example Title

B.1 Subsidiary section

B.1.1 Sub-subsidiary section

B.1.1.1 Sub-sub-subsidiary section

Appendix C. Revision History

akn-mime-v1.0-wd01Working Draft 0119 March2015

1Introduction

[All text is normative unless otherwise labeled]

1.1Terminology

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119].

1.2Normative References

[RFC2119]Bradner, S.,“Key words for use in RFCs to Indicate Requirement Levels”, BCP 14, RFC 2119, March 1997.

[Reference] [Full reference citation]

1.3Non-Normative References

[Reference] [Full reference citation]

(Remove Non-Normative References section if there are none. Remove text below and this note before submitting for publication.)

NOTE: The proper format for citation of technical work produced by an OASIS TC (whether Standards Track or Non-Standards Track) is:

[Citation Label]

Work Product title (italicized). Edited by Albert Alston, Bob Ballston, and Calvin Carlson. Approval date (DD Month YYYY). OASIS Stage Identifier and Revision Number (e.g., OASIS Committee Specification Draft 01). Principal URI (version-specific URI, e.g., with stage component: somespec-v1.0-csd01.html). Latest version: (latest version URI, without stage identifiers).

For example:

[OpenDoc-1.2]Open Document Format for Office Applications (OpenDocument) Version 1.2. Edited by Patrick Durusau and Michael Brauer. 19 January 2011. OASIS Committee Specification Draft 07. Latest version:

2Section Title

Name : Fabio Vitali

Email :

MIME media type name : Application

MIME subtype name : Standards Tree - akn+xml

Required parameters : None

Optional parameters :

charset

with identical semantics to the charset parameter ofthe application/xml media type as specified in [RFC 3023] andsuccessors.

Encoding considerations: Identical to those for 'application/xml'. SeeRFC 7303, Section 3.2.

2.1Security considerations

Since this media type uses the "+xml" convention, it shares the security considerations described in Section 10 of RFC 3023 [RFC3023], Akoma Ntoso documents may contain arbitrary URIs. Hence the security issues of [RFC3986], Section 7, apply.

Akoma Ntoso agents MUST adopt secure transmission channels such as SSL/TLS, and MAY adopt in addition further tools such as XML encryption on the private parts of the content.

RC:

This is useful information but not sufficient. In discussing the security

considerations for a media type it is necessary to cover at least these points:

(1) State whether or not the media type contains active or executable

content. If the media type does contain executable content explain

what measures have been taken to insure that it can be executed

safely, e.g. a sandbox, safe operation set, signed content, etc.

(2) State whether or not the information contained in the media type

needs privacy or integrity services.

(3) If the answer to (2) is yes, elaborate on any privacy or integrity

services the media type itself provides, or if it doesn't provide such

services, explain how they should be provided externally, e.g., through

the use of SSL/TLS.

Having perused the schema for this type, it appears to me that it does not

directly incorporate executable content, but that such content could be present

in "presentation", or "proprietary" elements due to their extensibility. If

this is correct it needs to be noted.

As for privacy and integrity, it strikes me that there will be cases where

this media type needs both, and if so (or if not) that also needs to be noted.

It may also be appropriate to give guidance as to how that would be done (e.g.,

XML signatures, SSL/TLS, etc.)

2.2Interoperability considerations

This specification describes processing semantics that dictate behavior that must be followed when dealing with, among other things, unrecognized elements. Since Akoma Ntoso is designed to be extensible in specific elements, "application/akn+xml" processors MAY expect that content received is well-formed XML, but processors SHOULD NOT assume that the content is valid Akoma Ntoso or expect to recognize all of the elements and attributes in the document.

2.3Published specification

The Akoma Ntoso specifications are an upcoming output of the LegalDocMLTechnical Committee of OASIS. Specification of the Akoma Ntoso schema isavailable in draft form at and will be madeavailable on the OASIS web site during the normal approval process.

RC: There needs to be a stable document to reference here for a standards tree

type.

2.4Applications which use this media

Akoma Ntoso documents are created, accepted and managed by a number of tools in use by parliaments that are active in the legal XML domain. These include document management systems, legal drafting tools, URI resolvers and format converters.

The necessity of this media types arises with those institutions that have another XML data format for their legal documents, and that want to add support for Akoma Ntoso, since by examining the request they need to be able to determine the XML vocabulary to use for the response.

Fragment identifier considerations : Documents having the media type 'application/akn+xml' use a fragment identifier notation totally consistent with what is specified in [RFC3023] for the media type 'application/xml'.

2.5Restrictions on usage

None

2.6Provisional registration

We kindly request provisional registration for application/akn+xml

2.7Additional information

1. Deprecated alias names for this type : None

2. Magic number(s) : There is no single initial octet sequence that is always

3. File extension(s) : Akoma Ntoso documents are most often identified with the ext

4. Macintosh file type code : TEXT

5. Object Identifiers: None

Preliminary Community Review was obtained in August 2014, with a mail to , id: , that received no comments.

Person to contact for further information :

1. Name : Fabio Vitali or Monica Palmirani

2. Email : or

Intended usage : Common

Common

Author/Change controller : The OASIS Legal XML Member Section has change control over these specifications.

3# Conformance

The last numbered section in the specification must be the Conformance section. Conformance Statements/Clauses go here. [Remove # marker]

Appendix A.Acknowledgments

The following individuals have participated in the creation of this specification and are gratefully acknowledged:

Participants:

[Participant Name, Affiliation | Individual Member]

Appendix B.Example Title

text

B.1Subsidiary section

text

B.1.1Sub-subsidiary section

Text

B.1.1.1Sub-sub-subsidiary section

text

B.1.1.1.1Sub-sub-sub-subsidiary section

text

Appendix C.Revision History

Revision / Date / Editor / Changes Made
[01] / [19/03/2015] / [Monica Palmirani] / [First version]

akn-mime-v1.0-wd01Working Draft 0119 March2015