Re: [legaldocml] Table of content for deliveries 1 and 2

[Fabio Vitali <fabio@CS.UniBO.IT>]

Dear Tom, 

> Fabio:
> I'm sure we'll end up talking about this on the call, but I'm curious:  in which of deliverables 0 or 1 will we address the influence of different legislative process on the design of the model?  One of the things I am most curious about -- and apologize for not having addressed more fully -- is the fact that American legislative process (at the Federal level, at least ) is IMHO less amenable to FRBR-ish assumptions.....
> 
> t.


a very quick and most probably wrong answer: 

The justification for the adoption or modification or rejection of a technical feature belongs to the discussion of that technical feature, and not in a chapter on its own. 

That is to say: in the section about the design issue of delivery 1 we will need to discuss FRBR. At that point we will examine how FRBR fits the legislative processes of individual countries. My idea is that once we decide that we need to modify FRBR to deal with US Federal legislation, we plainly and directly modify it without introducing in a different section the explanation of how the individual differences in legislative systems impacted on the language. 

Ciao

Fabio




Il giorno 12/apr/2012, alle ore 17.40, Thomas R. Bruce ha scritto:

> On 4/12/12 6:33 AM, Fabio Vitali wrote:
>> Dear all,
>> 
>> as discussed in the last TC meeting, the deliverables for this TC will be six (numbered 0 to 5):, as follows:
>> 
>> 0) language primer: a layman introduction to all the issues relevant to the language (Non Normative)
>> 1) language vocabulary: an introduction to the themes, the design issues and the objectives of the language followed by the systematic discussion of the characteristics of each element of the language (Normative)
>> 2) language schema: the formal structure (in XSD and/or RelaxNG) of the XML vocabulary of the language (Normative)
>> 3) naming convention: the structure and components of the URI used in the language (Normative)
>> 4) pilot cases: a list of good experiences and best practices of applying the language to real life situations
>> 5) user manual: instructional material for producers of documents, explaining the steps and the aspects of the actual production of documents using the language.
>> 
>> We are now meant to discuss the Table of Content of these delivery documents.
>> 
>> 
> Fabio:
> I'm sure we'll end up talking about this on the call, but I'm curious:  in which of deliverables 0 or 1 will we address the influence of different legislative process on the design of the model?  One of the things I am most curious about -- and apologize for not having addressed more fully -- is the fact that American legislative process (at the Federal level, at least ) is IMHO less amenable to FRBR-ish assumptions.....
> 
> t.
> 
> -- 
> +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
> Thomas R. Bruce @trbruce
> Director, Legal Information Institute
> Cornell Law School
> http://www.law.cornell.edu/ @liicornell
> +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legaldocml-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: legaldocml-help@lists.oasis-open.org
> 



--

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/