Building. European Legislation Identifier. Pillars. Thomas Francart ELI Taskforce

Transcription

1 Building European Legislation Identifier Pillars Thomas Francart ELI Taskforce «Access to and reuse of EU Legal Information» Brussels 21 march 2016

2 1. Identifiers Identify Browse legislation legislation 2. Metadata Describe Link legislation legislation 3. Content structure? Not in scope of ELI!

3 Design ELI URIs Create ELI metadata Publish ELI metadata

4 URIs are «barcodes» for every piece of data on the web

5 URL URI Identify something on the web Identify, on the web, anything (from the real world) Fabien Gandon :

6 ELI proposes URI components that can be selected and arranged in any order to define your own URI structure.

7 Guidelines to Design ELI URIs

8 Guideline #1 Stay close to how legislation is cited the 2001 Directive means Directive 2001/83/EC of the European Parliament and of the Council on the Community code relating to medicinal products for human use; (*) LOV nr 925 af 18/09/ (*) :

9 Guideline #2 Use components stable over time «Cool URIs don t change» Typically avoid names of ministries in the URI

10 Guideline #3 Define user behavior to browse the ELI hierarchy User behavior /eli/dir/2001 Lists all the directives of 2001 /eli/dir/2001/83 Get Directive 2001/83/EC in its current state : latest consolidated version, plus modifiers not yet consolidated /eli/dir/2001/83/corrigendum /eli/dir/2001/83/ Get the corrigenda of Directive 2001/83/EC Get Directive 2001/83/EC as it was at the requested date

11 Guideline #4 Address layers of the ELI description A specific legislation, independently of one of its «version» or language A specific (temporal) version of this legislation, independently of its language A specific linguistic variant of this version of the legislation A specific file format for given language of given version of this legislation Directive 80/181/CEE OJ version or consolidated version An english translation Signed PDF vs. HTML

12 1 Legal Resource in its original OJ version 23 Legal Expressions 3 Formats for each expressions

13 (Abstract) LegalResource Has multiple versions in LegalResource Can be expressed in various LegalExpression Can be published in various Format Each conceptual level is identified with a URI using extra components. Is expressed in concrete files

14 Why are ELI URIs foundations for ELI metadata?

15 Subject Verb Complement <ELI URI> <Metadata> <Value> /eli/dir/1980 /181/oj eli:date_pu blication ELI Metadata are expressed on ELI URI in the form of triples.

16 ELI metadata model ~ 35 fields (+ inverse properties) Generic description of legislation A publishing model to share not to replace internal metadata schemas (if any)

17 Describe legal texts (Luxembourg) Finance, Tax is_about Parliament Ministry of Finance passed_by responsibility_of uri:.../loi/2014/21/19/n11 type_document: Law title: Pondération de l'indice des prix à la consommation date_document: 25/10/2014 date_publication: 30/10/2014 in_force: yes publisher: Bureau de la Législation du Luxembourg published_in Official Journal A 255/2014 relevant_for Luxembourg

18 Different levels of description LegalResource Can be expressed in various LegalExpression Can be published in various Format Each level of abstraction will be associated with specific metadata.

19 ELI Metadata : links Based on / basis for Secondary legislation to primary legislation Changes / changed by Amendment, replacement Cites / cited by In the text of the legislation Consolidated / consolidated by Consolidated version to previous consolidated version or base act, plus legislation making the change Transposes / transposed by (implements / implemented by) From national legislation to EU directives (transposes : formal link, implements : more generic, for consolidated versions)

20 Link legal texts (Luxembourg) Project idparlement:60720 related_to cites Law /loi/1988/12/13/n1 Reglementation /rgd/2015/07/24/n3 basis_for Law /loi/2014/21/19/n11 SEQ:A cites cited_by Directive 1991/0440 Law /loi/2015/07/30/n1 changes changes Law /loi/2010/12/17/n2 changes Law /loi/2009/05/05/n8 changed_by Law../loi/1860/12/04/n1 Creating a graph of legislation. Law /loi/2015/05/31/n1

21 Guidelines to Create ELI metadata

22 Guideline #1 Map your description metadata to ELI Map Xpath inside XML, or database columns Map what you have, some fields will be «not applicable» ELI Property date_document date_publication first_date_entry_in_force date_no_longer_in_force related_to changes changed_by Italy Corresponds to the date of the legal act (data atto) Corresponds to the date of the Official Gazzette that contains the legal act It maps to the "iniziovigenza" date. It maps to the "finevig" date. Not applicable emendamenti, errata corrige, avvisi di rettifica Not applicable

23 Guideline #2 Publish the 4 mandatory fields Type of document : eli:type_document Title : eli:title Language : eli:language File format : eli:format

24 Guideline #3 Define necessary controlled lists (use SKOS) type of document keywords administrative areas agents (ministries, publishers, etc.)

25 How can ELI metadata be published into web pages?

26 What you see as a human

27 What the HTML code looks like <div id="content"> <h2 class="title"> <span about=" /jo/texte/fr" property="eli:title" typeof="eli:legalexpression"> LOI n du 2 décembre 2015 portant diverses dispositions d'adaptation au droit de l'union européenne dans le domaine de la prévention des risques </span> </h2>... <strong>loi n du <span property="eli:date_document" datatype="xsd:date" content=" ">2 décembre 2015</span> portant... </strong>... </div> RDFa syntax allows to embed semantic markup in an HTML web page with extra attributes.

28 What the machine sees Applications can parse RDFa markup and turn it into (RDF) structured data.

29 Guidelines to Publish ELI metadata

30 Guideline #1 Use RDFa to add semantic markup to existing webpages. Either inline <strong>loi n du <span property="eli:date_document" datatype="xsd:date" content=" ">2 décembre 2015</span> portant...

31 Guideline #2 or in a header <head> <meta about=" typeof="eli:legalresource"/> <meta about=" property="eli:id_local" content="31969r2596" /> <meta about=" property="eli:type_document" resource=" <meta about=" property="eli:passed_by" resource=" <meta about=" property="eli:is_about" resource=" </head>

32 Take away

33 ELI URIs = Technical identifiers + User browsing in legislation

34 ELI Metadata = Clear levels of abstraction + Generic legislation description

35 ELI Publishing = Low impact on publishing workflow + No visual impact in webpages

36 ELI is an easy first step for building a web of legal data. Once deployed it can be improved iteratively.

37 Thank you! Questions?