legaldocml message

Subject: New release of Akoma Ntoso 3.0 (20 January 2013 - OASIS CSD01)

From: Fabio Vitali <fabio@cs.unibo.it>
To: legaldocml@lists.oasis-open.org, akomantoso-xml@googlegroups.com
Date: Sun, 20 Jan 2013 17:36:34 +0100

Hello.

Please find attached the new release of Akoma Ntoso, dated 20 January 2013. This is the first version of Akoma Ntoso to be submitted and approved by the OASIS LegalDocML Technical Committee. It is also the first draft release for what is meant to become version 3.0 of Akoma Ntoso. The namespace policies have been modified to reflect this change.

Ciao

Fabio

Differences between release 20/1/2013 (CSD01 AN 3.0) and 27/07/2012 (AN 2.0)
----------------------------------------------------------------------------
This release is the first to be created as a deliverable of the OASIS LegalDocML Technical Committee. It contains answers to a number of requirements by CIRSFID, by the European Parliament, by the Library of Congress of Chile, and by XCential.
The most apparent difference is in the management of namespaces, especially with regard to future releases. There are several issues with regard to namespaces. First of all, it has been proposed that very new release is associated to a different namespace. Thus, from now on, regardless of the number of differences in the release, a new namespace will be forged and associated to the release. Second, being under the cover of the OASIS LegalDocML implies adopting OASIS-style naming conventions for schemas, as detailed in http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives-v1.3.html#xml-namespaces . In particular, this means that namespaces from now on will have the form: http://docs.oasis-open.org/legaldocml/ns/akn/xxx , where xxx is one of
• Working Draft (WD)
• Committee Specification Draft (CSD)
• Committee Specification Public Review Draft (CSPRD)
• Committee Specification (CS)
• Candidate OASIS Standard (COS)
• OASIS Standard (OS)
• Approved Errata (Errata)
, followed by a sequential number. Finally, the objective of this stage of the OASIS LegalDocML TC at this stage is to deliver the 3rd version of Akoma Ntoso. Therefore, the namespace of this release will be http://docs.oasis-open.org/legaldocml/ns/akn/3.0/CSD01 .

Additional differences include:
· A new element has been included in speech sections, called speechGroup. This is meant for collecting within a single, annotated group an otherwise unmarked sequence of individual speeches, of which there is one main speech (by an appointed speaker, possibly introduced by the chair, interrupted by the audience and followed by a debate. In this case, the speechGroup element will help identify the main speaker (attribute by), the role of the main speaker (attribute as) and the addressees (attribute to) as well as the individual speech elements that the overall discussion is composed by.
· Elements recitals, citations and toc are now provided with a list of optional heading elements (such as header, subheader, num, etc.) in case the structure of the section becomes fairly complicated. This also implies that toc, previously a block element, has been upgraded to container.
· Two new elements from HTML have been added, abbr and br (an inline and a marker, respectively), with the same use and semantics as in HTML.
· Two new elements have been added to judgements, namely arguments and remedies.
· Type YesNoType data type has been removed and unified with the plain xsd:Boolean data type. Attributes that used “yes”/”no” values need now to use “true”/”false” values.
· Attribute status has been clarified and streamlined. Its values now express the justification for the difference between the actual content of the manifestation and the content of the corresponding expression. In particular, the new values for the attribute are as follows:
o removed: the content of the element is present in the markup (manifestation) but is not present in the real content of the document (expression level) because it has been definitely removed (either ex tunc, as in annullments, or ex nunc, as in abrogations).
o temporarily removed: the content of the element is present in the markup (manifestation) but is not present in the real content of the document (expression level) because it has been temporarily removed (e.g., for a temporary suspension or limitation of efficacy).
o translated: the content of the element is present in the markup (manifestation) in a different form than in the real content of the document (expression level) because it has been translated into a different language (e.g., to match the rest of the document or because of other editorial decisions).
o editorial: the content of the element is present in the markup (manifestation) but is not present in the real content of the document (expression level) because it has been inserted as an editorial process when creating the XML markup.
o edited: the content of the element is different in the markup (manifestation) than in the real content of the document (expression level) because it has been amended (e.g., to remove scurrilous or offensive remarks).
o verbatim: the content of the element is present in the markup (manifestation) is EXACTLY as it was in the real content of the document (expression level) because usual silent fixes and edits were NOT performed (e.g. to punctuation, grammatical errors or other usually non-debatable problems).
o incomplete: the content of the element or the value of a required attribute is NOT present in the markup (manifestation), although it should, because the missing data is not known at the moment, but in the future it might become known. This is especially appropriate for documents in drafting phase (e.g., the publication date of the act while drafting the bill)
o unknown: the content of the element or the value of a required attribute is NOT present in the markup (manifestation), although it should, because the author of the manifestation does not know it.
o undefined: the content of the element or the value of a required attribute is NOT present in the markup (manifestation), because the information is not defined in the original document, or it doesn't exist in some legal tradition (e.g. an anonymous speech cannot specify the attribute by, or some publications do not record the numbering of the items, etc.),
o ignored: the content of the element or the value of a required attribute is NOT present in the markup (manifestation) because the information exists but the author of the manifestation is not interested in reporting it (e.g., omitted parts of the document due to editorial reasons, etc.).

· A new element, documentRef, has been added to side pre-existing componentRef. This should clarify and streamline the use of each: componentRef is now only a manifestation-level placeholder for content that is placed in a separate file, and can be placed instead of any structural element of the body of the document. Element documentref, on the other hand, is meant as a work-level or expression-level placeholder to a whole document that is available at a different URI. It can be only placed as members of a document collection, as an attachment, or as an included document within quotedStructure and extractStructure elements.
· All containers and hcontainers can now be empty. This is meant to help in using status=”omissis” on a structure, or any other situation in which content exist but is not represented in the XML document.
· Elements formula and FRBRAlias have now a name attribute to help identify the kind of formula it is.
· Elements docDate, publication, step and eventRef now accept a dateTime, in its norm attribute, which allows the (optional) specification of a time as well as a date, if present.
· A new element time has been added. It contains a time attribute to specify a normalized specification of a time as present in the text.
· Elements quotedText, extractText, quotedStructure and extractStructure now allow a new attribute quote, which is used to specify the quote character used (if any) in the text.
· Keyword elements now accept a href attribute meant to associate the individual keyword to a specific fragment of the text, so that it is now possible to perform classification of individual fragments of the document. Keywords without the href elements will be assumed to refer to the whole document.
· Two new textual modifications have been added to the analysis section of the metadata, join and split, to identify operations that respectively create a single structure out of two adjoining ones, and that create two adjoining structures by separating one.
· Elements old and new can now be contained multiple times within the same textual modification. This allows for the same modification to affect multiple parts of a document. Additional attributes id and href allows to specify which new refers to which old part.
· Element attachments can now contain either a documentRef (as previously) or any of the document types. This allows for each manifestation to decide whether an attachment should be placed outside of the main XML flow or within it on a document by document basis.
· A specification has been added to the Akoma Ntoso naming convention with regard to virtual expressions (i.e., expressions where some of the information is unknown or unavailable). This is specified in section 8.4.4 of the Release Notes.

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/

Attachment: Release 20130120.zip
Description: Zip archive