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: Bug fix: New release of Akoma Ntoso 3.0 (23 July 2013 - OASIS CSD05)


Hello again. 

In order to comply with the OASIS procedure on submission of candidate CSDs, please find attached, again, the CSD05 of Akoma Ntoso (23 July 2013) with only ONE minor bug fix (namely, the addition of the core attributes to the toc element), as evidenced on last Tuesday's teleconf. Everything else is exactly as the distribution of the 23rd of July. 

Ciao

Fabio

--

Hello.

Please find attached the new release of Akoma Ntoso, dated 23 July 2013. This is the fifth draft release for what is meant to become version 3.0 of Akoma Ntoso. If you missed the fourth, do not worry: it has been distributed only to the OASIS TC and is completely replaced by this one. I hope I haven't forgotten anything of what was decided. 

Ciao

Fabio

--

Differences between release 23/7/2013 (CSD05 AN 3.0) and 18/2/2013 (CSD03 AN 3.0)
---------------------------------------------------------------------------------
Please note that this is release CSD05 AN 3.0, and that CSD04 AN 3.0 was an unofficial intermediate release dated 18/7/2013 that was never distributed outside the OASIS TC, and its modifications are completely contained and described here.
This release contains a number of modifications proposed, discussed and approved by the OASIS TC between February and July 2013, and promoted by Monica Palmirani, Grant Vergottini and Veronique Parisse for the specific needs of Uruguayan bills, Swiss legislation, US and Hong Kong codes, and European Parliament’s legislation. In detail:
* The spelling judgment instead of judgement has been applied consistently throughout the schema as suggested by native English speakers and approved by the TC.
* The pattern popup has been renamed subFlow, and all types, groups and attribute groups containing the word popup have been renamed accordingly. Also the generic element popup is now named subFlow.
* Three new hcontainers have been added: rule, subRule and proviso.
* Element coverPage can now contain longTitle.
* A new inline element decoration has been added to mark the editorial suggestion by the legislator that are meant to decorate and explain the most recent publication of a legislative fragment, such as adding the word “new” on the side of an newly inserted article or section.
* A new judgment section has been added called argument, to specify the argument used by the judge to evaluate a case.
* Attribute list dateTime has been removed (containing both a date and a time attributes) and replaced by a extended data type for the date attribute, allowing either a simple date value (with the usual syntax YYYY-MM-DD) or a dateTime value YYYY-MM-DDThh:mm:ss(zzzz), where zzzzzz is either the letter “Z” (referring to UTC) or a six letter sequence composed of a plus or minus sign followed by a five-letter time offset with regard to UTC (e.g., CET would be -01:00, and EST would be +05:00). Absence of a time zone specification is only allowed when the time zone can be determined without ambiguity (e.g., in national documents for countries spanning a single time zone). Multiple representations of the same point in time according to different time zones must be marked up only ONCE with a disambiguating date attribute with any choice of time zone. All elements that used to have both date and time attributes (e.g, docDate, date, publication, eventRef, step, etc.) now only have the extended date attribute.
* The part component of a document structure can now be placed both at the end of the document type (i.e., just before the end tag of </bill> or </act> or, as before, at the end of the Akoma Ntoso structure (i.e., just before the end tag of </akomaNtoso>). This allows a greater flexibility in dividing longer documents in smaller fragments and placing the fragments either within the document flow or just outside of it.
* The type collectionStructure (used by complex documents) can now contain preambles.
* The hcontainer subdivision, has been added to the list of usable hcontainers, as it was left out erroneously.
* Element toc is back to being a block-level element without headings or introductions, but the need to have them has been taken care of by the new element blockContainer, which is a kore general solution to a problem that toc shared with other elements, such as conclusions.
* A new block-level element has been added, blockContainer, meant to side blockList in the expression of complex structures at the block level. This allows to specify headed and autonomous sections within a block level context, such as element content, conclusion or prefaceSection.
* Type subFlowStructure (formerly popupStructure, used by subFlow elements such as quotedStructure and extractStructure, now allow more elements, in particular all document types (e.g., bill, act, etc.) and table elements tr, th, and td.
* Element FRBRname in FRBRWork properties can now be repeated as many times as needed to specify different well-known names with which the work is known.
* Type valueType, used by many metadata elements especially is the FRBR block, can now use the refersTo and showAs attribute.
* Modifier attributes exclusion and incomplete can now be added both to whole analysis elements, as before, as well as to individual members of the analysis element such as source, destination, etc.
* A new element, renumberingInfo, has been added in temporalData to manage the tracking of multiple renumberings in structure (e.g. for bills). Since id only contains the very first id for the element, and evolvingId contains the id the structure would have in the current version of the document, renumberingInfo provides a way to record all the intermediate evolving ids the structure has had in the historical evolution of the document. In particular, each renumberingInfo element must specify the original id of the structure being described (i.e., the never-changing id attribute), the evolved Id (i.e., the evolving id the structure has in that specific time interval), and the start and end temporalInfo specifications for the time interval in which the evolving Id was current.


--

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 20130723.zip
Description: Zip archive



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