Re: [akomantoso-xml] RE: Akoma Ntoso as a working /in-progress document

legaldocml message

Subject: Re: [akomantoso-xml] RE: Akoma Ntoso as a working /in-progress document

From: monica.palmirani <monica.palmirani@unibo.it>

To: <akomantoso-xml@googlegroups.com>, "legaldocml@lists.oasis-open.org" <legaldocml@lists.oasis-open.org>

Date: Wed, 5 Dec 2012 09:34:50 +0100

Dear Grant,

first of all thanks for your very pertinent questions (as usual! :-) for facing the topic "incompleteness of the Akoma markup".

Some comments below in the text for the today TC meeting. Some files in attachment as proof-of-concept that it is feasible to mange the incompleteness markup in Akoma. However in this email I intend to propose some improvements to the schema.

Before to read the text below, some nomenclature is necessary.
In my previous email I meant to define a sort of taxonomy of incompleteness:
- uncompleted --> the information are not known now but in the future it is possible to know especially because we are in drafting phase
- unknown --> the information exists but we don't know
- undefined --> the information is not defined in the original document, it doesn't exist in some legal tradition (e.g. speech anonymous without by attribute, or no numbering in publication)
- ignored --> the information exists but we are not interested to markup it

We can discuss on the terminology, but the semantic meaning of incompleteness is really precious for interoperability, transparency and trustiness of the metadata assertions.

Cheers,
Monica

Il 05/12/2012 02:28, Grant Vergottini ha scritto:

From my viewpoint, the there are perhaps a cascade of cases - each one following the other through the drafting process:

1) The initial state of a document being created. Is it possible to have a document that is valid according to the schema, which has yet to contain any information?

*** Yes it is possible to extract some sub-schemas from Akoma Ntoso (like the current tool does http://generator.akomantoso.org/) for any consistent fragment of the schema: preface, preamble, body, conclusions, meta. I will include this item in the agenda of today.

This document could be a form of a template.

*** The templates are managed by the tools (editors). We have produced in our web editor different templates according to the specifications of the end-users. http://sinatra.cirsfid.unibo.it/wawe/
It is possible to create some examples of templates in the LegalDocML documentations, but they are so close to each legal traditions and to the end-user pilot cases that it is risky to include them in OASIS Specs. This is an option to evaluate together. I will include this item in the agenda of today.

Is a template a valid Akoma Ntoso document? (This is close to Monica's second case)

*** Yes, if the template respect the main blocks of Akoma Ntoso and if we decide to create, additionally to the existing sub-schemas, other sub-schemas oriented to the main blocks of Akoma, it is possible.

2) Is it possible to have an incomplete document, partially drafted, that is still a valid document. Sometimes it takes a long time to draft legislation and it must be possible to save, analyze, and pre-publish documents that are yet to be completed .(This is also close to Monica's second case)

*** Yes, as I said before it is not a matter to modify the prescriptiveness of Akoma Ntoso (that is so loose) but it is a matter to produce sub-schema for blocks (preface, meta, etc.) AND to define a set of values (e.g. "undefined") to include in the list of enumerated elements like @contains, @status.

Some practical proposals:

a. @status is an attribute for any part of the "body". It is very useful for said the status of the fragment of text. Now we have different status (omissis, editorial, edited, ignore, etc.) -->
Proposal: add new values like
"uncompleted" (in the future it is possible to know)
"unknown" (it is not possible to know now and in the future)
"undefined"
"ignored"

or similar

 <xsd:simpleType name="statusType">
 <xsd:annotation>
 <xsd:documentation>
 <type>Simple</type>
 <name>statusType</name>
 <comment>This is the list of allowed values for the status attribute</comment>
 </xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:enumeration value="omissis"/>
 <xsd:enumeration value="repealed"/>
 <xsd:enumeration value="suspended"/>
 <xsd:enumeration value="editorial"/>
 <xsd:enumeration value="ignore"/>
 <xsd:enumeration value="translated"/>
 <xsd:enumeration value="edited"/>
 <xsd:enumeration value="verbatim"/>
 </xsd:restriction>
 </xsd:simpleType>

b. @contains is an attribute of the root for specifying the type of the document
Now we have these values. draftVersion
<xsd:restriction base="xsd:string">
 <xsd:enumeration value="originalVersion"/>
 <xsd:enumeration value="singleVersion"/>
 <xsd:enumeration value="multipleVersions"/>
</xsd:restriction>
Proposal: to add new valuse like:
"draftVersion" --> in future it is transformed in originalVersion, singleVersion, multipleVersions
"incompleteVersion" --> it is not mandatory to have a transformation in a complete document.

c. the metadata has @refersTo attribute. It is possible since now to use it for defining the status of the metadata "undefined" (I have used the following example for the use case of the Chancellery of Switzerland)

<publication date="9999-01-01" name="internal" showAs="undefined" number="undefined" refersTo="#undefined"/>

However some part of the schema like FRBR doesn't permit to use refersTo.
Proposal: to add a new attribute for any metadata similar to attribute @status
example
<identification source="#somebody" status="draft">
 <FRBRWork>

d. when the people suspend to markup, it is possible to wrap the not-yet-marked part of the text like this.
<content status="uncompleted">
 The professional rights of both members of BNAT and IAGRAT are
 assured as outlined in the Conditions and Scheme of Service for
 teachers. In the event, where a member of the Service has a problem,
 he approaches the association to which he belongs and that
 association handles the problem with BES in the light of the
 Conditions of Service.
 In the area of professional development, BNAT organizes in-service
 training for its members.
 Mr. Speaker, BNAT joins the ‘FORUM’ comprising the Judicial Service
 Staff Association of BUNGENI (JUSSAB), the Registered Nurses
 Association (BRNA) and the Civil Servants Association (CSA) for the
 negotiation of salaries for all teachers.

3) Some aspects of an Akoma Ntoso document, such as the metadata section, rely on heavy analysis of a drafted document. Is the intent that this analysis will take place throughout the editing session or can it be postponed to a discrete time either before or after the document is saved or even finalized. If it is possible to postpone analysis to a discrete time, is it still possible to have a valid document even without the analysis having taken place? How strict should Akoma Ntoso be in ensuring that all the steps have been completed? Or does this check belong with the software and not with the schema?

*** Yes it is always possible to postpone the metadata markup apart FRBR session.
Another approach is to insert the main "block" of metadata during the drafting activity with some "status", as I am suggesting in the previous paragraph, just as a reminder.
Please find in attachment a debate example without metadata or better where are mandatory (FRBR, by, etc.) with the status "uncompleted".
For the bill it is easer because the mandatory elements are really few: FRBR and body! I have attached an example where the only part marked up is the body. Note that <mod> is possible without <analysis> just for permitting an incremental approach in the markup.

4) Some aspects of the document may not initially be known and might not even be known until the bill is adopted. For example, the effective date of a piece of legislation perhaps won't be known until such time as the legislation is adopted. When this is the case, and a date is speculative, proposed, or unknown, how should this information be represented in Akoma Ntoso? Is it represented by an "unknown" date or is it omitted until it is known? (I believe this is Monica's first case)

*** It is in your hand the decision which approach to use, both are possible.
Now it is possible to adopt this
 <FRBRdate date="9999-01-01" name="publication"/>
In future I would like to have:
 <FRBRdate date="9999-01-01" name="publication" status="uncompleted"/>
Now it is possible this:
 <publication date="9999-01-01" name="internal" showAs="uncompleted" number="uncompleted" refersTo="#undefined"/>
In future I would like to have:
 <publication date="9999-01-01" name="internal" showAs="uncompleted" number="uncompleted" status="uncompleted"/>

Monica's fourth case is a special case to me - I think. I usually refer to these as "operational conditions" which are sometimes very hard to automate. There are many ways in which an event in time could be specified to occur. The simple case is the "operational date" specified as a fixed date which is easy to automate. But what do you do when the event occurs based on conditions which cannot easily be automated? For example, legislation that comes into effect only if other legislation is also passed, repealed, or amended. How are these conditions characterized in Akoma Ntoso? While this problem is relatively rare, it does occur frequently enough to deserve accommodation in Akoma Ntoso.

*** Akoma Ntoso already includes a particular block in the <analysis> where to specify the conditions:

<ch:forceEqualTo href="/ch/act/2000-03-24/ru20012394/main"/>

</condition>

</forceMod>

The <condition> block is matter of any single public administration/customer/entity.
For more detailed modelling features about rules/conditions/implications we can use LegalRuleML embedded inside.

The treaty cases are so frequent in EU legal tradition that we can't ignore. For some end-user (like UN oopsh) it is the core business. Moreover several legal traditions includes these conditions. See the Switzerland case for examples (art. 7, par. 2) http://www.admin.ch/ch/i/as/2000/1915.pdf (there is also in France http://www.admin.ch/ch/f/as/2000/1915.pdf and in German http://www.admin.ch/ch/d/as/2000/1915.pdf)
"Entra in vigore contemporaneamente alla legge federale del 24 marzo 20002 concernente
l’istituzione e l’adeguamento di basi legali per il trattamento di dati personali."
So this scenario is really an important case to mange.

Regards,
-Grant

On Mon, Dec 3, 2012 at 11:18 PM, monica.palmirani <monica.palmirani@unibo.it> wrote:

Dear Ashok, dear Grant,

in preparation of the TC meeting of tomorrow please find these few comments.

Thanks for opening this discussion on the incomplete document. It is a very important topic.

There are four cases, from my point of view, when a document is incomplete and so invalid to the XML validation:

- situation where the document is incomplete because some information are not available due to the legislative work-flow. It is the case of the bill where (e.g.) the time of enter into force of the document is not yet defined. In this case we need some attribute (status="undefined" date="9999-99-99") or some default values (eg. <num status="undefined">undefined</num>) for those parts that need to be treated in these cases.
The status of incompleteness is in the major of cases destined to be resolved when the document completes its legislative work-flow (e.g. it becomes act). In this case the status of incompleteness is mostly temporary.

- situation where the document is incomplete because the people is working on it in different steps. In this case we don't take care so much to the validation. However it is possible to produce some sub-schemas, one for each main part of Akoma Ntoso (e.g. preface, preamble, body, etc.), in order to permit the validation of each macro-block. It is the case when the markup task is divided between different offices of the same body. It is a feature quite interesting for the editors based on XML engine. In this case the status of incompleteness is definitely temporary.

- situation where the document is incomplete of some metadata without any other evolution. In this case the incompleteness is permanent but in Akoma Ntoso there aren't parts mandatory except for the <meta><identification> block and <body>. So you can resolve this situation using @refersTo combined with or <omissis>.

- situation where the document has some parameters that are dynamic over the time and they need some integrations (e.g. conditional included inside of the normative part e.g. "1. This Convention shall enter into force on the thirtieth day following the date of the deposit of the twenty-second instrument of ratification, acceptance, approval or accession with the Secretary-General of the United Nations." http://treaties.un.org/Pages/ViewDetails.aspx?src="">). For this case we need to understand if the evolution produces a new _expression_ due to the fact that only the metadata are changed, not the text.

Yours,
Monica

Il 16/11/2012 12:11, Ashok Hariharan ha scritto:

This question is coming from the discussion in the last tc-meeting.
There was a question raised by Grant (and also I believe Veronique) on
working documents - where all the information may not be available
during some stages of markup (e.g. dateTime period information ) -
some of these are mandatory for the document to be valid. The
conclusion appeared to be that the schema has to accommodate an
unknownDateTime / unknownPeriod attribute setting for such cases ( I
lost the connection towards the end - so i am not sure if there was
further discussion on this ) . I would also think there are other
use cases of this type which we don't know about yet - what is the
recommended practice in such cases - do we leave the working document
invalid until such information is available ?

--

===================================
Associate professor of Legal Informatics
School of Law
Alma Mater Studiorum Università di Bologna
C.I.R.S.F.I.D.http://www.cirsfid.unibo.it/ Palazzo Dal Monte Gaudenzi - Via Galliera, 3
I - 40121 BOLOGNA (ITALY)
Tel +39 051 277217
Fax +39 051 260782
E-mailmonica.palmirani@unibo.it ====================================

--
You received this message because you are subscribed to the Google Groups "akomantoso-xml" group.
To post to this group, send email to akomantoso-xml@googlegroups.com.
To unsubscribe from this group, send email to akomantoso-xml+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akomantoso-xml?hl=en.

--
____________________________________________________________________
Grant Vergottini
Xcential Group, LLC.
email: grant.vergottini@xcential.com
phone: 858.361.6738

--
You received this message because you are subscribed to the Google Groups "akomantoso-xml" group.
To post to this group, send email to akomantoso-xml@googlegroups.com.
To unsubscribe from this group, send email to akomantoso-xml+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akomantoso-xml?hl=en.

-- 
===================================
Associate professor of Legal Informatics 
School of Law
Alma Mater Studiorum Università di Bologna 
C.I.R.S.F.I.D. http://www.cirsfid.unibo.it/ 
Palazzo Dal Monte Gaudenzi - Via Galliera, 3 
I - 40121 BOLOGNA (ITALY) 
Tel +39 051 277217 
Fax +39 051 260782 
E-mail  monica.palmirani@unibo.it 
====================================

<?xml version="1.0" encoding="UTF-8"?> <akomaNtoso xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://www.akomantoso.org/2.0 ./akomantoso20.xsd" xmlns="http://www.akomantoso.org/2.0";> <bill contains="originalVersion">  <meta> <identification source="#palmirani"> <FRBRWork> <FRBRthis value="/us/california/bill/2010-12-06/4/main"/> <FRBRuri value="/us/california/bill/2010-12-06/4/main"/> <FRBRdate date="2010-12-06" name="Enactment"/> <FRBRauthor href="#assembly" as="#author"/> <FRBRcountry value="us"/> </FRBRWork> <FRBRExpression> <FRBRthis value="/us/california/bill/2010-12-06/4/eng@/main"/> <FRBRuri value="/us/california/bill/2010-12-06/4/eng@"/> <FRBRdate date="2010-12-06" name="Expression"/> <FRBRauthor href="#palmirani" as="#editor"/> <FRBRlanguage language="eng"/> </FRBRExpression> <FRBRManifestation> <FRBRthis value="/us/california/bill/2010-12-06/4/eng@/main.xml"/> <FRBRuri value="/us/california/bill/2010-12-06/4/eng@/main.akn"/> <FRBRdate date="2010-12-06" name="XML-markup"/> <FRBRauthor href="#palmirani" as="#editor"/> </FRBRManifestation> </identification> </meta> <coverPage> </coverPage> <preface> </preface> <preamble> <formula> The people of the State of California do enact as follows: </formula> </preamble> <body> <section id="sec1" refersTo="#uncompleted"> <num>SECTION 1.</num> <content> <mod id="mod1"> <ref id="ref1" href="/us/california/governmentCode/main#sec11343-4">Section 11343-4 of the Government Code</ref> is <eol/>amended to read: <eol/> <quotedStructure id="mod1-qts1"> <section id="mod1-qts1-sec11343-4"> <num>11343-4.</num> <list id="mod1-qts1-sec11343-4-lst1"> <intro id="mod1-qts1-sec11343-4-lst1-into"> A regulation or an order of repeal required to be filed<eol/> with the Secretary of State shall become effective on <del id="mod1-qts1-del1">the 30th day</del> <eol/> <ins id="mod1-qts1-ins1">January 1 next following a 90-day period </ins> after the date of filing<eol/> unless: </intro> <point id="mod1-qts1-sec11343-4-lst1-pnta"> <num>(a) </num> <content> Otherwise specifically provided by the statute pursuant to<eol/> which the regulation or order of repeal was adopted, in which event<eol/> it becomes effective on the day prescribed by the statute.<eol/> </content> </point> <point id="mod1-qts1-sec11343-4-lst1-pntb"> <num>(b)</num> <content> A later date is prescribed by the state agency in a written <eol/>instrument filed with, or as part of, the regulation or order of repeal.<eol/> </content> </point> <point id="mod1-qts1-sec11343-4-lst1-pntc"> <num>(c) </num> <content> The agency makes a written request to the office <eol/>demonstrating good cause for an earlier effective date, in which <eol/>case the office may prescribe an earlier date.<eol/> </content> </point> </list> </section> </quotedStructure> </mod> </content> </section> <section id="sec2"> <num>SECTION 2.</num> <content> This act addresses the fiscal emergency declared by <eol/>the Governor by proclamation on December 6, 2010, pursuant to<eol/> <ref id="ref5" href="uri#artiv-sec10-subdivf">subdivision (f) of Section 10 of Article IV of the California </ref> <eol/>Constitution.<eol/> </content> </section> </body> </bill> </akomaNtoso>

<?xml version="1.0" encoding="UTF-8"?> <akomaNtoso xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://www.akomantoso.org/2.0 ./akomantoso20.xsd" xmlns="http://www.akomantoso.org/2.0";>  <debate contains="originalVersion">  <meta> <identification source="#somebody"> <FRBRWork> <FRBRthis value="uncompleted"/> <FRBRuri value="uncompleted"/> <FRBRdate date="9999-01-01" name="generation"/> <FRBRauthor href="#uncompleted" as="#uncompleted"/> <FRBRcountry value="ak"/> </FRBRWork> <FRBRExpression> <FRBRthis value="uncompleted"/> <FRBRuri value="/uncompleted"/> <FRBRdate date="9999-01-01" name="markup"/> <FRBRauthor href="#uncompleted" as="#editor"/> <FRBRlanguage language="eng"/> </FRBRExpression> <FRBRManifestation> <FRBRthis value="uncompleted"/> <FRBRuri value="uncompleted"/> <FRBRdate date="9999-01-01" name="publication"/> <FRBRauthor href="#uncompleted" as="#editor"/> </FRBRManifestation> </identification> <publication date="9999-01-01" name="internal" showAs="uncompleted" number="uncompleted" refersTo="#uncompleted"/>  </meta> <preface> THE <docProponent>PARLIAMENT OF THE REPUBLIC OF BUNGENI</docProponent> <docTitle>SECOND MEETING, 2011</docTitle> Friday, <docDate date="9999-01-01" refersTo="#uncompleted">10th June 2011</docDate> </preface> <debateBody> <debateSection name="uncompleted" id="dbs0"> The House met at 10.02 a.m. [MR. SPEAKER IN THE CHAIR] </debateSection> <debateSection id="sub1" name="uncompleted"> <heading>PRAYERS</heading> </debateSection> <debateSection id="dbs1" name="uncompleted">  <heading>MOTIONS </heading> <debateSection id="dbs2" name="uncompleted"> <speech by="#uncompleted"> <from>Mr. Alfa:</from> Mr. Deputy Speaker, I beg to move to the following Motion- THAT this House do grant leave to introduce a Bill for.....(30 pages of dabate) </speech> </debateSection> </debateSection> <debateSection id="dbs3" name="uncompleted">  <heading>QUORUM </heading> <debateSection id="dbs4" name="uncompleted"> <speech by="#uncompleted"> <from> Mr. Epsilon: </from> On a point of order, Mr. Speaker, Sir. We are discussing the President's Speech. The mere fact that we do not have enough hon. Members might mean that it is not a popular Speech. There is no quorum in this House and could you ensure that there is quorum and then we can continue in order to show that themPresident's Speech is popular and he is also a popular President as well? </speech> <speech by="#uncompleted"> <from>The Speaker:</from> Hon. Members, yes, I have checked and apparently the House lacks quorum at the moment. Ring the Division Bell. </speech> <summary>(The Division Bell was rung)</summary>  <speech by="#uncompleted"> <from>The Speaker:</from> Order, hon. Members! We have a quorum now. Please, proceed with the Division! </speech> </debateSection> </debateSection> <debateSection id="dbs5" name="uncompleted">  <heading>DIVISION</heading> <summary>(Question put and the House divided)</summary> <debateSection id="dbs6" name="uncompleted"> <speech by="#speaker"> <from>Mr. Speaker:</from> Order! Order! 15 minutes are now over and those who wish to vote must be in the lobbies. If you are not wihtin the lobbies, you will not allowd to vote any more </speech> <scene>(Loud consultation)</scene> <speech by="#speaker"> <from>Mr. Speaker:</from> Order! Order! The Division is now over and it is time to receive the results </speech> <summary id="sum1">(Question carried by 72 to 56 votes)</summary> </debateSection> <debateSection id="dbs7" name="uncompleted"> AYES: Mr. Alfa, Mr. Beta, Mr. Delta, etc. </debateSection> <debateSection id="dbs8" name="uncompleted"> NOES: Mr. Gamma, Mr. Epsilon, Mr. Zeta, etc. </debateSection> </debateSection>  <debateSection name="uncompleted" id="sub4"> <heading>ORAL ANSWERS TO QUESTIONS</heading> <debateSection name="uncompleted" id="sub4-sub1"> <heading>MINISTRY OF EDUCATION AND SPORTS</heading> <debateSection name="uncompleted" id="sub4-sub1-sub1"> <heading>Professional Training in the Republic of BUNGENI</heading> <question id="sub4-sub1-sub1-que1" by="#uncompleted" to="#uncompleted"> <from>Mr. Kappa</from> asked the Minister for Education and Sports the organic relations between the BUNGENI National Association of Teachers (BNAT) and the International Association of Graduate Teachers (IAGRAT) in pursuance of the professional and trade union rights of teachers in the country and trade union rights of teachers in the country, because the two are not the same. And in his Answer, he referred to professional rights of both members. Does it mean that the IAGRAT has no trade union rights as his Answer states? Because, the two are not the same. Professional rights are different from trade </question> <answer by="#uncompleted" as="#uncompleted" id="sub4-sub1-sub1-ans1"> <from>Mr. Eta</from> Mr. Speaker, BNAT was the only umbrella professional body for teachers in the country until when some graduate teachers started agitation for recognition and finally broke away and formed the National Association of Graduate Teachers (NAGRAT). Currently, there are two (2) associations serving the interest of teachers in the BES. Whereas members of IAGRAT consist of a section of graduate teachers, BNATcovers nongraduates as well as graduate teachers. The professional rights of both members of BNAT and IAGRAT are assured as outlined in the Conditions and Scheme of Service for teachers. In the event, where a member of the Service has a problem, he approaches the association to which he belongs and that association handles the problem with BES in the light of the Conditions of Service. In the area of professional development, BNAT organizes in-service training for its members. Mr. Speaker, BNAT joins the â??FORUMâ?? comprising the Judicial Service Staff Association of BUNGENI (JUSSAB), the Registered Nurses Association (BRNA) and the Civil Servants Association (CSA) for the negotiation of salaries for all teachers. </answer> </debateSection> </debateSection> </debateSection> <debateSection name="omissis" id="sub5"> <scene>(Applause)</scene> </debateSection> <adjournment id="sub6">  <heading> ADJOURNMENT</heading> The House was at <recordedTime time="9999-01-01T00:00:00">2.07 p.m. </recordedTime> till <date date="9999-01-01" refersTo="#uncompleted">11th June, 2011</date> at <recordedTime time="9999-01-01T00:00:00">10.00 a.m. </recordedTime> </adjournment> </debateBody> <conclusions> <date date="9999-01-01" refersTo="#uncompleted" >Date, 10th June, 2011</date> </conclusions> </debate> </akomaNtoso>