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: Re: [legaldocml] New release of Akoma Ntoso 3.0 (10 September 2015 - OASIS WD15)


Dear all, 

after long discussions in Ravenna last week, here you can find a few reflections I had on the issues raised. 

1) Interstitial between amendments in amendmentList: 
----------------------------------------------------
> 	• I have some problems to see the interstitial only as an independant component or attachment.  
> Inside the European Parliament, the interstitial is used for example to put the text with the number of the amendment inside the amendmentList.  In this context, when interstitial is used, it must be in connection with the real component or attachment (that is, the corresponding amendment).

Rather than using interstitial between amendments, since CSD09 we have the possibility of using num and heading within components. The following is a valid Akoma Ntoso document: 

<akomaNtoso xmlns="http://docs.oasis-open.org/legaldocml/ns/akn/3.0/WD15";>
	<amendmentList name="AmendmentList">
		<meta> ... </meta>
		<collectionBody>
			<component eId="component_1">
				<num>1</num>
				<heading>First amendment</heading>
				<amendment name="Something"> ... </amendment>
			</component>
			<component eId="component_2">
				<num>2</num>
				<heading>Second amendment</heading>
				<amendment name="Something else"> ... </amendment>
			</component>
		</collectionBody>
	</amendmentList>
</akomaNtoso>

2) Repetition in identification and publication
-----------------------------------------------
> 	• I see that, in the metadata part, the only sections that are not repeteable are the <identification> and the <publication>.
> Is it a reaon for this ?  Both elements have the attribute "source" which seems to mean that it can be multiple, as there can have multiple source.

As I said, I am very convinced that we should NOT allow repeatability for identification elements, as they are the place where the specific manifestation describes itself, and it makes no sense for a manifestation to have multiple definitions of itself by different authors. I'm even saying that the actor identified by the source attribute of the <identification> element should be interpreted as the main creator of the whole Manifestation, and any other actor that appears somewhere as the source of other metadata parts should be considered as guests of the main author of the Manifestation. 

As for repeatability of the <publication> I have less strong objections. I'll leave to you to decide whether we should allow it. 

3) inlinequote attribute in <quoted*> elements
----------------------------------------------

It will be added. 

4) xml:lang in <notes> and <componentBody>
------------------------------------------

It will be added. 

5) Space between <num> and <heading>
------------------------------------

I am dead set AGAINST a new element for this. Grant said that he is fine with an officially recommended solution in the documentation. This is my solution, and I agree at putting it somewhere in the documentation. 

When a divider (e.g. a space or a return) needs to be reliably inserted between two elements in a container, such as, for instance, between <num> and <heading>, then the following are BAD approaches: 

a) insert an empty element 
   <num>10.</num> 
   <heading class="ignoreMe">&#160;</heading>
   <heading>The real heading</heading>
b) Put the divider character at the beginning of the second element
   <num>10.</num>
   <heading>&#160;The real heading</heading>
c) Put the divider character at the end of the first element
   <num>10.&#160;</num>
   <heading>The real heading</heading>

The best solution is to handle it as a classic presentation characterization of the two elements with a specific CSS style. In particular, if the space needs to be handled as text (e.g. redlined) then using the margin or the padding would not provide a reasonable solution. It is better to use the "content" property of the ::after CSS pseudo-class of the first element, as follows: 

d) <num>10.</num>
   <heading>The real heading</heading>

and, in the CSS style: 

num::after { 
    content: "&#160;";
}

Exceptions to this (e.g., one single num, heading pair that is NOT separated by a space) should be handled by a specially created CSS class, as for instance in the following: 

e) <num class="noSpace">11.</num>
   <heading>The real heading</heading>

and, in the CSS style: 

num::after { 
    content: "&#160;";
}
 
num.noSpace::after { 
    content: "" !important;
}

Ciao

Fabio

--

On 11/set/2015, at 08:54, "PARISSE, Véronique" <V.PARISSE@aubay.lu> wrote:

> Hello,
> 
> I have two additional remarks: 
> 
> 	• I see that, in the metadata part, the only sections that are not repeteable are the <identification> and the <publication>.
> Is it a reaon for this ?  Both elements have the attribute "source" which seems to mean that it can be multiple, as there can have multiple source.
> 	• I have some problems to see the interstitial only as an independant component or attachment.  
> Inside the European Parliament, the interstitial is used for example to put the text with the number of the amendment inside the amendmentList.  In this context, when interstitial is used, it must be in connection with the real component or attachment (that is, the corresponding amendment).
> Kind regards
> 
> Véronique Parisse
> 
> 
> Véronique Parisse
> AUBAY Luxembourg
> Orco House
> 38, Parc d’activités - L-8308 Capellen 
> Standard : +352 2992501
> Fax : +352 299251
> www.aubay.com
> De : legaldocml@lists.oasis-open.org [legaldocml@lists.oasis-open.org] de la part de Fabio Vitali [fvitali@gmail.com]
> Envoyé : jeudi 10 septembre 2015 18:36
> À : legaldocml@lists.oasis-open.org
> Cc : Angelo Di Iorio; akomantoso-xml@googlegroups.com; Luca Cervone
> Objet : [legaldocml] New release of Akoma Ntoso 3.0 (10 September 2015 - OASIS WD15)
> 
> Hello.
> 
> Please find attached the new release of Akoma Ntoso, dated 10 September 2015. This is another draft release for what is meant to become version 3.0 of Akoma Ntoso. 
> 
> Ciao
> 
> Fabio
> 
> --
> 
> Differences between release 10/09/2015 (WD15 AN 3.0) and 22/07/2015 (WD14 AN 3.0)
> ---------------------------------------------------------------------------------
> This release contains a few modifications that were suggested by Jim Mangiafico, Monica Palmirani, Veronique Parisse, Grant Vergottini, and other individuals during the Arlington (VA) summer school in July 2015.
> * A new hcontainer called level has been added.
> * An intermediate container (similar to heading and subheading), called crossheading, has been added inside the hierarchy of hcontainers,
> * The spelling of value “uncostitutionality” of attribute type of forceMods elements has been changed to a more correct “unconstitutionality”.
> * The content model of the portion element now allows more elements including coverPage, preface, preamble, recitals, citations, longTitle, and formula.
> * A new optional attribute has been added to elements eol and eop, called breakWith. This is meant to specify the exact character used as hyphen when breaking a word at the end of a line or page. Also, the spelling of attribute breakat of the same elements is now breakAt, which is consistent with the camelCase approach of Akoma Ntoso.
> * A new section of the analysis section of the metadata has been added, called otherReferences. Here one can specify a number of otherRef elements, that are meant to specify implicit references associated to fragments of the document (identified through a source element).
> 
> --
> 
> Fabio Vitali                                          The sage and the fool
> Dept. of Informatics                                     go to their graves
> Univ. of Bologna  ITALY                               alike in this respect:
> phone:  +39 051 2094872                  both believe the sage to be a fool.
> e-mail: fabio@cs.unibo.it                  Where, then, may wisdom be found?
> http://vitali.web.cs.unibo.it/   Qi, "Neither Yes nor No", The codeless code
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


--

Fabio Vitali                                          The sage and the fool
Dept. of Informatics                                     go to their graves
Univ. of Bologna  ITALY                               alike in this respect:
phone:  +39 051 2094872                  both believe the sage to be a fool.
e-mail: fabio@cs.unibo.it                  Where, then, may wisdom be found?
http://vitali.web.cs.unibo.it/   Qi, "Neither Yes nor No", The codeless code



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