OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

legaldocml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Request for MIME media type Application/Standards Tree - akn+xml - documentation


Dear all, 

this is the first proposal for registration of the Akoma Ntoso media type we sent and the answer we received. 



> According to the IESG-designated expert, until a stable reference is available, this type can be registered only in the provisional registry at http://www.iana.org/assignments/provisional-standard-media-types. This registry records only the type's name, organization, and contact. 
> 
> Should we proceed with provisional registration, listing you as the contact? 
> 
> See the inline comments below for the expert's suggestions for a future application.  
> 
> 
> ===
> 
>> Name : Fabio Vitali
> 
>> Email : fabio.vitali@unibo.it
> 
>> 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 of
>> the application/xml media type as specified in [RFC 3023] and
>> successors.
> 
>> Encoding considerations: Identical to those for 'application/xml'. See
>> RFC 3023, Section 3.2.
> 
> The references throughout this registration to RFC 3023 need to be updated
> to RFC 7303.
> 
>> Security 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.
> 
> 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.)
> 
>> Interoperability 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.
> 
> 
>> Published specification :
>> The Akoma Ntoso specifications are an upcoming output of the LegalDocML
>> Technical Committee of OASIS. Specification of the Akoma Ntoso schema is
>> available in draft form at http://www.akomantoso.org, and will be made
>> available on the OASIS web site during the normal approval process.
> 
> There needs to be a stable document to reference here for a standards tree
> type.
> 
>> Applications 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'.
> 
>> Restrictions on usage :
>> None
> 
>> Provisional registration? (standards tree only) :
>> We kindly request provisional registration for application/akn+xml
> 
> 
>> Additional 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 media-types@iana.org, id: http://www.ietf.org/mail-archive/web/media-types/current/msg00587.html , that received no comments.
> 
>> Person to contact for further information :
> 
>> 1. Name : Fabio Vitali or Monica Palmirani
>> 2. Email : fabio.vitali@unibo.it or monica.palmirani@unibo.it
> 
>> Intended usage : Common
>> Common
> 
>> Author/Change controller : The OASIS Legal XML Member Section has change
>> control over these specifications.
> 



--

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/






--

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/






[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]