1 / 35

Law Making Environment Perspectives

ITTIG - CNR. Law Making Environment Perspectives. C. Biagioli, L. Bacci, E. Francesconi, F. Turchi ITTIG-CNR Istituto di Teoria e Tecniche dell’Informazione Giuridica A. Cappelli ISTI-CNR Istituto di Scienza e Tecnologie dell’Informazione V Legislative XML Workshop

latika
Download Presentation

Law Making Environment Perspectives

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITTIG - CNR Law Making Environment Perspectives C. Biagioli, L. Bacci, E. Francesconi, F. Turchi ITTIG-CNR Istituto di Teoria e Tecniche dell’Informazione Giuridica A. Cappelli ISTI-CNR Istituto di Scienza e Tecnologie dell’Informazione V Legislative XML Workshop Fiesole, 14 – 16 June 2006

  2. Overview • Law-Making Environment • Tools for the “Legislator” based on semantic models; • Model of Provisions and Arguments; • Software architecture of a module for Planning a new bill; • Conclusions.

  3. Legislation management:State of the Art • Upkeep of current legislation through URN and XML standards; • This guarantees: • Web accessibility of new and legacy contents; • Interoperability among applications; • Advanced search and retrieval services based on semantics; • Automatic consolidation; • The most part of tools dealing with standards for legislation are addressed to documentalists rather than to the Legislator;

  4. Purposes • Providing the Law-Maker with a set of drafting tools allowing to plan organic and well structure bills; • Strategy: • Ex-ante (Lachmayer) management of the semantics; • Benefits: • planning a new organic bill from a conceptual (semantic) point of view; • Metadata are directly inserted by the Legislator • they will be “authentic” metadata;

  5. Semantic Model • Model of Provisions and Arguments: • Amendments (Insertion, Abrogation, Substitution); • Rules (Obligation, Prohibition, Penalties, Exceptions, …); and their Arguments; • It is a standard within the “Norme in Rete” DTDs/XMLSchema;

  6. NIR-DTD document description • The NIR standards describe a legislative text under two profiles: • the formal profile: • It considers a law text as made up of divisions; • It describes the physical structure of a document; • the functional profile: • It considers a normative text as composed by elementary components called provisions (fragment of a regulation); • It is described by provisions types and their arguments; • It describes the logical structure of a document.

  7. A fragment of legislative text viewed according to the formaland the functional profile Article 7 (Notification) Functional Profile 1. A controller intending to process personal data falling within the scope of application of this Act shall have to notify the Garante thereof… Type of provision: “Obligation” Arguments: Addressee: “Controller” Action: “Notification” Counter-party: “Garante” 2. The notification shall have to be given… Formal profile Division (or Paragraph)

  8. Legislative Document within the NIR environment Article 1 (Purposes and definitions) … 2. For the purposes of this Act: a) "data bank" shall mean any set of personal data, … … Article 7 (Notification) 1. A controller intending to process personal data falling within the scope of application of this Act shall have to notify the Garante thereof … Article 42 (Amendments to laws in force ) 2. For paragraph 1 of article 4 of legislative decree no. 39 of 12 February 1993 there shall be substituted the following:“1. An Authority for information technology in the public administration…” Definition(definiendum =“data bank”, definiens= “any set of personal data…”) Obligation(addressee=“controller”, action =“notification”, counter-party=“Garante”) Substitution(norm=“urn:…”, novellando=“paragraph 1 of article 4”, novella= “#…”)

  9. Drafting Meta Drafting PlanningProvisions types Argument Keywords Provision Models Domain Keywords Editor(structure) XML Partitions Skeleton DB Provisions Editor(wording) Aggregation Queries on provisions XML Partitions Skeleton and Text XML Partitions Skeleton and Semantics metaEdit(semantic markup) Generation Automatic provisionswording XML Text (Structure and Semantics) LME: Tools for Law Makers URN, XML Standards tomorrow today

  10. xmLegesEditor today

  11. Semantic MarkUp: MetaEdit today

  12. Semantic MarkUp: MetaEdit Arguments of the chosen provision type

  13. Semantic MarkUp: MetaEdit Filling theArgument

  14. Semantic MarkUp: MetaEdit Semantic markup view

  15. MetaDrafting: LME Project • Planning; • Aggregation; • Generation. tomorrow

  16. Planning basic elements • Model of Provisions and Arguments; • Ontology of concepts and terms of the scenario to be regulated; • Definition manager; • Visual panel where provisions types and their arguments can be handle as visual objects;

  17. 1. Model of Provisions and Arguments OWL description of the provision taxonomy; Provision subClassOf <owl:Class rdf:ID=“Provision”> <owl:Class rdf:ID=“Regulative”> <rdfs:subClassOf rdf:resource="#Provision”/> <owl:Class rdf:ID=“Obligation”> <rdfs:subClassOf rdf:resource="#Regulative”/> … <owl:Class rdf:ID=“Addressee”/> <owl:Class rdf:ID=“Action”/> <owl:Class rdf:ID=“Counter-party”/> … <owl:ObjectProperty rdf:ID="hasAddressee”> <rdfs:domain rdf:resource="#Obligation”/> <rdfs:range rdf:resource="#Addressee”/> </owl:ObjectProperty> Regulative ObjectProperty Obligation hasAddressee hasCounterParty hasAction Counter-party Addressee Action

  18. 2. Ontology of concepts and terms of the scenario to be regulated • Two levels: • Ontology (classes of legal concepts); • Lexicon (terms as instantiations of legal concepts); • These terms are used to • provide values to the • provision arguments. Legal act has_hyperonym Notification has_hyponym Notice

  19. 3. Definition Manager • Specific terms of the domain of interest not contained in the vocabulary can be inserted and defined using a Definition Manager; • Also these new terms can be used to provide values to the provision arguments.

  20. 4. Visual Panel • Panel where to handle: • Provision Types as visual objects; • Provision Arguments whose values are terms from the “Definition Manager”; File Edit View Insert Options Help

  21. Provision > … Constitutives Regulatives > Amendments Obligation Procedure Penalty … Definition Manager ‘data bank’ shall mean … ‘personal data’ shall mean any information relating to natural or Legal persons… SemanticNet - Legal act - Notification - Notice Planning visual panel File Edit View Insert Options … Help Obligation Addreesee: Action: Counter-party: Notification

  22. Planning visual panel File Edit View Insert Options … Help Definition Definiendum: Data bank Definiens: … Obligation Addreesee: Controller Action: Notification Counter-party: Garante Derogation Addreesee: Action: Notification Counter-party: Procedure Addreesee: Action: Notification Counter-party: Definition Definiendum: Personal data Definiens: …

  23. Aggregation:from Provision Instances toGroups of Partitions GROUP ProvisionTypes = “Definition” INTO an Article GROUP ProvisionType = “Obligation” AND ProvisionType = “Procedure” AND ProvisionType = “Derogation” WHERE Argument = “Action” AND content = “Notification” INTO an Article

  24. Aggregation File Edit View Insert Options … Help Paragraph Paragraph Definition Definiendum: Controller Definiens: … Obligation Addreesee: Controller Action: Notification Counter-party: Garante Paragraph Definition Definiendum: Data bank Definiens: … Paragraph Procedure Addreesee: Action: Notification Counter-party: … Paragraph Article Derogation Addreesee: Action: Notification Counter-party: … Article

  25. Aggregation CriteriaFormal and Functional profiles of a “well-structured” documents • A legislative text where the functional structure fits well the chosen formal structure; Capo I Art. 1. • [DEFINITION] • [DEFINITION] • [DEFINITION] • “Well-structured” normative documents: Art. 5. Stuctural partitions • [OBLIGATION, Arguments X,Y] • [PROCEDURE, Arguments X,Y] • [DEROGATION, Arguments X,Y] contain … semantically Art. 16 correlated partitions • [PENALTY] • [PENALTY] according to several criteria;

  26. Obligation Procedure Derogation Document (Law) … Chapter Chapter Chapter Article Article Article Article … … Paragraph Paragraph Paragraph Paragraph Paragraph Semantics StructureDocument Construction Formal profile PartOf Concrete Definition Definition Functional profile

  27. <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE NIR SYSTEM 'nircompleto.dtd'> … <capo id=“cap1”> <disposizioni> <analitiche> <dsp:definizione> <dsp:definiendum>Personal data<dsp:definiendum> </dsp:definizione> … <articolo id=“art1”> </articolo> … </capo> <capo id=“cap2”> <disposizioni> <analitiche> <dsp:obbligo> <dsp:destinatario>Controller</dsp:destinatario> <dsp:azione>Notification</dsp:azione> … </dsp:definizione> … <articolo id=“art7”> </articolo> … </capo> … Law n. Chapter 1 Art. 1 1. [to be filled] 2. [to be filled] … Chapter 2 Art. 7 1. [to be filled] 2. [to be filled] 3. [to be filled] XML Skeleton Editor view Definition(Controller,…) Definition(Data bank,…) Obligation(Controller, Notification,Garante) Procedure(..,Notification, ..) Derogation(..,Notification, ..)

  28. Generation • Aims: • Supporting provision generation • Features: • Provision text generation on the basis of • The grammar of a specific provision type • The content of the arguments

  29. Grammar of each provision type • EBNF productions for each type of provisions • <ProvisionType>  <Definition> | <Competence> | <Obligation> • <Permission> | <Procedure> | <Penalty> … • 2) <Definition>  <Definition syntactical structure> • 3) <Competence>  <Competence syntactical structure> • … • … <Obligation>  <Obligation syntactical structure> • Each specific syntactical structure is related to the structure of the arguments of each provision type

  30. Benefits of “Generation” • More clear legislative texts; • It limits the ambiguity of texts; • It helps legislative drafting even for unexpert users as regards legislative technique;

  31. Generation XML Partitions Skeleton and Semantics XML Text(Structure and Semantics) Law n. Chapter 1 Art. 1 1. [to be filled] 2. [to be filled] … Chapter 2 Art. 7 1. [to be filled] 2. [to be filled] 3. [to be filled] Law n. Chapter 1 Art. 1 1. "controller" shall mean any natural or legal person 2. "data bank" shall mean any set of personal data … … Chapter 2 Art. 7 1. A controller .. shall have to notify the Garante … 2. The notification shall have to be given in advance … 3. Simplified notifications may omit certain items … Definition(Controller,…) Definition(Controller,…) Definition(Data bank,…) Definition(Data bank,…) Obligation(Controller,Notification,Garante) Obligation(Controller,Notification,Garante) Procedure(..,Notification, ..) Procedure(..,Notification, ..) Derogation(..,Notification, ..) Derogation(..,Notification, ..)

  32. Uses of the Provision Models • Drafting LawMakingEnvironment • To provide a semantic guide for planning a new bill. • Consolidation • Management of amendments; • Searching MetaSearch • To query a legal information system according to a semantic point of view;

  33. metaSearch Text Provision types Arguments Argument keywords

  34. metaSearch Retrieved provisions Related provisions Related derogations

  35. Conclusions • The LME is aimed at supporting the Law-Maker in planning a new bill from a conceptual point of view; • The classical process of drafting is reverted: • Traditional drafting • structure text content semantic markupEx Post • Meta-draftingsemantic markup structure text content • Ex Ante

More Related