legislation, constitutions, treaties, and parliamentary ...€¦ · web viewrecommendation for...

Legislation, Constitutions, Treaties, and Parliamentary Documents Requirements and Use Cases Version 1.0

Working Draft 04

17 June 2015

Technical Committee:OASIS Legal Citation Markup (LegalCiteM) TC

Chairs:John Joergensen ([email protected]), Rutgers University School of LawFabio Vitali ([email protected]), University of Bologna-CIRSFID

Editors:Monica Palmirani ([email protected]), University of Bologna-CIRSFIDMelanie Knapp ([email protected]), George Mason University Law LibraryJohn Dann ([email protected]), Chargé de direction adjoint at Ministère d'Etat - Service central de législation

Additional artifacts:This prose specification is one component of a Work Product that also includes:

XML schemas: (list file names or directory name) Other parts (list titles and/or file names)

Related work:This specification is related to:

Related specifications (hyperlink, if available)Declared XML namespace:

http://docs.oasis-open.org/legalcitem/ns/Abstract:

Summary of the technical purpose of the document.Status:

This Working Draft (WD) has been produced by one or more TC Members; it has not yet been voted on by the TC or approved as a Committee Draft (Committee Specification Draft or a Committee Note Draft). The OASIS document Approval Process begins officially with a TC vote to approve a WD as a Committee Draft. A TC may approve a Working Draft, revise it, and re-approve it any number of times as a Committee Draft.

URI patterns:Initial publication URI:http://docs.oasis-open.org/legalcitem/legislation-reqs/v1.0/csd01/legislation-reqs-v1.0-csd01.docPermanent “Latest version” URI:http://docs.oasis-open.org/legalcitem/legislation-reqs/v1.0/legislation-reqs-v1.0.doc(Managed by OASIS TC Administration; please don’t modify.)

Copyright © OASIS Open 2015. All Rights Reserved.All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as

legislation-reqs-v1.0-wd044 Working Draft 04 17 June 2015Standards Track Draft Copyright © OASIS Open 2015. All Rights Reserved. of 72

https://www.oasis-open.org/policies-guidelines/ipr

https://www.oasis-open.org/policies-guidelines/tc-process#standApprovProcess

https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft

https://www.oasis-open.org/policies-guidelines/tc-process#dWorkingDraft

mailto:[email protected]

http://www.gmu.edu/


http://www.cirsfid.unibo.it/


http://www.cirsfid.unibo.it/


http://www.newark.rutgers.edu/


https://www.oasis-open.org/committees/legalcitem/

needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Table of Contents1 Introduction......................................................................................................................................... 6

1.1 Terminology....................................................................................................................................... 61.2 Normative References....................................................................................................................... 61.3 Non-Normative References...............................................................................................................6

2 Introduction......................................................................................................................................... 72.1 Goal of the document........................................................................................................................ 72.2 Scenario............................................................................................................................................ 72.3 Objectives.......................................................................................................................................... 8

3 Type of documents.............................................................................................................................. 94 Type of citations................................................................................................................................ 10

4.1 Dynamic citations............................................................................................................................ 104.2 Static citations................................................................................................................................. 104.3 Internal and External citations.........................................................................................................104.4 Multiple citations.............................................................................................................................. 11

4.4.1 Range citations........................................................................................................................ 114.4.2 List of citations......................................................................................................................... 11

4.5 Explicit citations............................................................................................................................... 114.6 Incomplete citations......................................................................................................................... 114.7 Short title, Acronym, Abbreviation...................................................................................................114.8 Implicit citations............................................................................................................................... 124.9 Linguistic variant of the citations......................................................................................................12

5 Common End-User Requirements....................................................................................................135.1 Flexibility.......................................................................................................................................... 135.2 Usability........................................................................................................................................... 135.3 Human Readable............................................................................................................................ 145.4 Interoperability................................................................................................................................. 14

5.4.1 Multilinguism............................................................................................................................ 145.4.2 Alias......................................................................................................................................... 155.4.3 Fragment citation.....................................................................................................................155.4.4 Meta Data................................................................................................................................. 16

5.5 Legal Expert Requirements.............................................................................................................165.5.1 Versioning and Consolidation over time...................................................................................165.5.2 Variants and Translation..........................................................................................................175.5.3 Errata corrige........................................................................................................................... 185.5.4 Annulment and Retroactive Modifications................................................................................185.5.5 Sovereign................................................................................................................................. 195.5.6 Jurisdiction............................................................................................................................... 195.5.7 Document Component, Components and Annexes.................................................................20

5.6 Archival Requirements....................................................................................................................215.6.1 Open vocabulary...................................................................................................................... 215.6.2 Authenticity............................................................................................................................... 215.6.3 Provenance.............................................................................................................................. 22

5.7 Citations per document type............................................................................................................22


5.7.1 Constitution.............................................................................................................................. 225.7.2 Act............................................................................................................................................ 225.7.3 Bill............................................................................................................................................ 225.7.4 European documents...............................................................................................................225.7.5 Treaty....................................................................................................................................... 225.7.6 Code........................................................................................................................................ 235.7.7 Consolidated act......................................................................................................................235.7.8 Gazette, Journal.......................................................................................................................23

6 Existing pilot cases............................................................................................................................ 246.1 ELI................................................................................................................................................... 24

6.1.1 Luxembourg pilot case.............................................................................................................246.1.1.1 URI Schema........................................................................................................................................27The URI schema is based on how legislation is cited, with elements which do not change over time...........276.1.1.2 Use case for Constitutional Court.......................................................................................................286.1.1.3 Reference to point in time and consolidated version..........................................................................29

6.1.2 France pilot case......................................................................................................................296.1.2.1 Constitution.........................................................................................................................................296.1.2.2 Code...................................................................................................................................................306.1.2.3 Other legislative and regulatory texts..................................................................................................306.1.2.4 URI building blocks for France............................................................................................................306.1.2.5 Examples for texts..............................................................................................................................326.1.2.6 Examples for articles of texts..............................................................................................................336.1.2.7 HTML version of a consolidated CODE at a given date (not yet implemented)..................................336.1.2.8 Official Journal entries........................................................................................................................33

6.1.3 UK pilot case............................................................................................................................ 346.1.3.1 Reference to legislation in academic work or publication...................................................................346.1.3.2 URI structure reflecting UK legislation:...............................................................................................36

6.1.4 Publications Office of the European Union...............................................................................386.1.4.1 General structure of the identifiers......................................................................................................386.1.4.2 Identifying abstract legal resources (Directives and Regulations in a first stage)...............................396.1.4.3 Identifying a specific legal resource pertaining to an act....................................................................396.1.4.4 Identifying a specific linguistic version of a legal resource (a “LegalExpression”)..............................406.1.4.5 Identifying a specific format of a specific linguistic version of a legal resource..................................416.1.4.6 Incomplete identifiers for search purposes.........................................................................................41

6.1.5 European Parliament Information model..................................................................................426.1.5.1 The extended document model..........................................................................................................426.1.5.2 Another system to identify document : the session number...............................................................45

6.2 Reference in European documents.................................................................................................456.2.1 Reference to another act..........................................................................................................456.2.2 In the title of an act...................................................................................................................456.2.3 In a citation(example : COM(2015) 4 final)...............................................................................456.2.4 In a recital................................................................................................................................. 466.2.5 In the body............................................................................................................................... 46

1.1.1.1 Amending act : reference to the amended provision..........................................................................466.3 Reference to blocks inside actUS GPO...........................................................................................47

6.3.1 Types of documents and their citation......................................................................................476.3.2 Secondary legislative documents issued by the federal legislature are:..................................48


6.3.3 Use case 1: United States Constitution....................................................................................486.3.4 Cornell LII................................................................................................................................. 48

6.3.4.1 Use case 2: United States Code, 18 U.S.C. § 924.............................................................................486.3.5 GPO......................................................................................................................................... 496.3.6 Cornell LII................................................................................................................................. 49

6.3.6.1 Use case 3: Public Law, Pub. L. No. 113-1........................................................................................506.3.6.2 Use case 4: Private Law, Priv. L. No. 112-1.......................................................................................50

6.4 URN:LEX......................................................................................................................................... 506.4.1 Italian Project URN:NIR............................................................................................................50

6.4.1.1 The case of the Senate of Italy...........................................................................................................516.4.1.2 Normattiva...........................................................................................................................................516.4.1.3 High Court of Cassation......................................................................................................................51

6.4.2 LexML Brazil Project................................................................................................................516.5 Zotero for legislative resources.......................................................................................................516.6 LLL – US Code................................................................................................................................ 526.7 Akoma Ntoso (to be revised: it is an extract from the AKN Naming convention deliverable submitted in OASIS LegalDocML TC)....................................................................................................................536.8 The IRI of a Work............................................................................................................................ 53

6.8.1 The IRI for the Work as a Whole..............................................................................................536.8.2 The IRI for WorkComponents...................................................................................................546.8.3 The IRI for Work-level portion queries......................................................................................54

6.9 The IRI of an Expression................................................................................................................. 556.9.1 The IRI for the Expression as a Whole.....................................................................................556.9.2 The IRIs for ExpressionComponents.......................................................................................56

6.9.2.1 The Expression is Only Composed of One Component.....................................................................566.9.2.2 The Expression is Composed of Many Components..........................................................................56

6.9.3 Hierarchies of Components in ExpressionComponents...........................................................576.9.4 The IRIs for Virtual Expressions...............................................................................................576.9.5 The IRI for Expression-level portion queries............................................................................58

6.10 The IRI of a Manifestation.............................................................................................................586.10.1 The IRI for the Manifestation as a Whole...............................................................................586.10.2 The IRI for Manifestation-level portion naming.......................................................................596.10.3 The IRIs for ManifestationComponents..................................................................................596.10.4 The IRIs for the Components in the Akoma Ntoso Package Manifestation............................59

6.11 The IRI of an Item.......................................................................................................................... 607 Conformance..................................................................................................................................... 618 Bibliography...................................................................................................................................... 62Appendix A. Acknowledgments................................................................................................................. 63Appendix B. Example Title.........................................................................................................................64

B.1 ELI Metadata................................................................................................................................... 64B.2 Akoma Ntoso Metadata...................................................................................................................69B.3 Zotero Metadata.............................................................................................................................. 69

Appendix C. Revision History.................................................................................................................... 70


1 Introduction[All text is normative unless otherwise labeled]

1.1 TerminologyThe key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119].

1.2 Normative References[RFC2119] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels”, BCP

14, RFC 2119, March 1997. http://www.ietf.org/rfc/rfc2119.txt.[Reference] [Full reference citation]<this is an example nor real reference>

1.3 Non-Normative References[Reference] [Full reference citation]

(Remove Non-Normative References section if there are none. Remove text below and this note before submitting for publication.)

NOTE: The proper format for citation of technical work produced by an OASIS TC (whether Standards Track or Non-Standards Track) is:

[Citation Label]Work Product title (italicized). Edited by Albert Alston, Bob Ballston, and Calvin Carlson. Approval date (DD Month YYYY). OASIS Stage Identifier and Revision Number (e.g., OASIS Committee Specification Draft 01). Principal URI (version-specific URI, e.g., with stage component: somespec-v1.0-csd01.html). Latest version: (latest version URI, without stage identifiers).For example:

[OpenDoc-1.2] Open Document Format for Office Applications (OpenDocument) Version 1.2. Edited by Patrick Durusau and Michael Brauer. 19 January 2011. OASIS Committee Specification Draft 07. http://docs.oasis-open.org/office/v1.2/csd07/OpenDocument-v1.2-csd07.html. Latest version: http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html.

<this is an example nor real reference>


http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html

http://docs.oasis-open.org/office/v1.2/csd07/OpenDocument-v1.2-csd07.html

http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#latest-version

http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#this-version

http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#revision

http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#stage

http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#workProductName

http://www.ietf.org/rfc/rfc2119.txt

2 Introduction2.1 Goal of the documentThis document is the summary of the outcomes of the LegalCiteM – Legislation, Treaty, Constitution (LLTC) sub committee of the main LegalCiteM OASIS Technical Committee. This sub committee has the goal to analyze different normative references concerning legislation, treaties, constitutions in order to define the fundamental elements which would then enable to represent in a unique manner legal resources on the Web. Using these elements for referencing or representing legal citations inside of the legal texts would be of great benefit to all. The LLTC collects use cases among different legal traditions, countries, languages, standards and it summarizes the main requirements in the domain for favoring the work of the technical specifications definition in the Technical sub committee.The pilot cases collected are the following: ELI from France, Luxembourg, Office of Publications of the European Union, United Kingdom; URN:LEX from Brazil and Italy; Akoma Ntoso from different countries; GPO (USA); Cornell University LII annotation; LEGISLATIVE LOOKUP & LINKING (LLL); Library of Congress annotation.

2.2 ScenarioAll countries are based on the rule of law. Legal system and government tradition, rule of procedure in the legislative system and all of them have publication regulation for permitting the public access these sources. The public access to the legal sources is an essential democratic principle for permitting citizens to take knowledge of their rights and obligations. It is also prodromic to participate in the governance of a country.The legislative citation is part of this national legal culture and for this reason it is important to have in mind a flexible mechanism that is able to be close to the national legislative system.Most of the deliberative bodies or publication institutions have extensive Web sites (government gazette, official gazette, official journal, official newspaper, official diary or any other authorial publication instrument), for editing and publishing legislation documents to the general public and businesses.Also, the process of cooperation at the international level has increased the need to identify and exchange legislation documents especially if they are authentic, official and delivered by empowered authorities. This need is partially met by the digitalization of legislation documents and the widespread use of the Internet. However, the use of legal documents is greatly limited by the differences that exist in the various legal systems and in the way in which relevant documenters are organized and classified or stored in technical systems. It is even further hampered by the amount of legal data available.Citation and exchange of legislation documents across borders and across different systems, and in particular data relating to international, regional (e.g. Pan-African Parliament, Mercosur), European or national legislation would be very useful to all. In order to facilitate the further development of interlinked legal data and to serve legal professionals and citizens, we are missing some of the most basic building blocks for interoperability in order to share, cite and link legal data. Benefiting from the emerging architecture of the semantic web and Linked Open Data, this solution would allow a greater and faster exchange of data by enabling an automatic and efficient exchange of information. It would also allow humans and machines to have an improved access to Governments’ legislation, allowing easy referencing, understanding the meaning of the information processed, downloading, analyzing, re-using and interconnecting different information and sources across domains. Constructing common building blocks for naming and citing legislation documents, with additional structured metadata, that are sufficiently standardized and flexible and that respect each countries unique legislative and legal tradition, would be feasible. It should also take in consideration that this should be a cost-effective implementation on top of existing IT solutions or databases, and it should be designed to work seamlessly on top of existing systems.


2.3 ObjectivesThe Legal normative citation topic involves three main aspects strictly connected :

1. identifier: the univocal, but not necessarily unique, name of the legal resource, persistent, meaningful, easy for the end-user to use, connected with the main semantic metadata of the legal resource in order to qualify the legal text and to understand the provenance;

2. reference: the machine-readable representation of the textual citation of a legal source able to retrieve the legal source over time;

3. metadata: the metadata set that can qualify the legal source. Metadata can enrich the reference by helping the dereferencing or the retrieval of specific legal sources.

A good construction of the identifier permits to use a correct reference model for detecting the normative source cited in the text, also when it evolve over time or it is expressed in different linguistic variants. The reference is able to create the correct input for the dereferencing mechanism managed by different application levels (e.g., resolver, metadata database, etc.).The objectives of this document is to identify the main neutral requirements that an identifier of legislative sources should have in order to facilitate the building of the appropriate reference starting from a textual citation and the nature of the legal document.

An example of identifier is:

Primary URI

Alias

An example of reference is:

Citation in the text

Reference

An example of metadata is:

Document

metadata


3 Type of documentsThe LegalCiteM "Legislation, Constitutions, Treaties and Parliamentary" documents subcommittee collected some use cases coming from different legal systems and related to different types of document (e.g. act, constitution, bill, treaty, etc.).

The types of document in charge of this sub-committee are: constitution: constitutive legal document of a legal system; Treaties establishing the European Union act: legislative document approved by the proper authority. This category includes all the type of

primary law: legislative decree, urgent decree, president regulation, federated state acts, regional act, etc.; bill: legislative document in draft version and under discussion in the deliberative assembly (e.g. parliament, assembly, congress, etc.);

European law documents: directive, regulation, decision, recommendation; treaty: international or regional treaty; code: codified collection of acts e.g. U.S. Code, including Positive Law and Private Law or Civil Code

of Italy; consolidated act: updated version of an act e.g. Classified Compilation of Federal Legislation; amendment: document that propose modifications to a bill; collection of amendments: list of the amendments; legislative resolution given the position of the Parliament relative to a bill. Can contain a list of

amendments; resolutions of joint resolution of the European parliament; consolidated amendments: entire bill proposed as an amendment; gazette: collection of acts, bills, etc. published in Official Gazette or Journal, Statutes at Large, etc..


4 Type of citationsIn the legislation document we find different kind of citation or normative references that need to be managed by the naming convention of citation standard.

4.1 Dynamic citationsThe major part of the normative references is dynamic and follows the link according to the evolution of the law over time. We need to manage easily this requirement in order to point out exactly to the updated version of legislative document.

Article 3 of Directive 2011/24/EU (EU directive)

Section 1161(1) of the Companies Act 2006 (UK)

Those citations are updated according to the evolving of the legal system and the navigation produces the browsing to the last updated version of the legal resource.

4.2 Static citationsA static citation is when a cross-reference links to a specific version (in time) or variant (e.g., language) of a specific legislative document. E.g. the cross-references that are in the preamble. The citation of a specific table of drugs.

In European legislation, “a static reference refers to a specific text as it stands on a specific date, by stating the title of the act and the source, and specifying, where appropriate, an amending act”.1 In European legislation, references to non-Community acts are, in principle, static.“A reference is dynamic if the provision cited is always understood to be the provision as amended”2.

4.3 Internal and External citations

For EU context, an internal reference refers to another provision of the same act. External references refer to another act, either a Union act or an act from another source. The annexes, schedule, extracts are refered as internal citation.

Schedule 2 to the principal Act

1 Joint Practical guide (online), 16.11.2 Joint Practical guide, éd . 2013legislation-reqs-v1.0-wd044 Working Draft 04 17 June 2015Standards Track Draft Copyright © OASIS Open 2015. All Rights Reserved. of 72

4.4 Multiple citationsLegislative and in general legal document includes sometime multiple citations in order to minimize the general parts.

4.4.1 Range citationsParagraphs 1-32, Art. 14

4.4.2 List of citationsList of citation is a

points (a), (e), (o) and (p) of Article 6(1)

4.5 Explicit citations

OJ L 255, 30.9.2005, p. 22

4.6 Incomplete citationsIt is a citation that is missing some information that doesn’t permit to understand in a precise manner the exact destination.

4.7 Short title, Acronym, Abbreviation Sometime we have a citation explicit but incomplete of some parameters for detecting from the text the exact information for detecting the resource. This is often happen when we use abbreviation, short title or conventions:

Consumer Rights Act 2015

UK example that corresponds to the 2015 CHAPTER 15 URI: http://www.legislation.gov.uk/ukpga/2015/15/section/1/enacted

{shortTitle}{year}

Patient Protection and Affordable Care Act (PPACA)

commonly called the Affordable Care Act (ACA)

{title}{acronym}

colloquially "ObamaCare”


http://www.legislation.gov.uk/ukpga/2015/15/section/1/enacted

{shortCut}

Penal Code

Italian Case

{title}

4.8 Implicit citationsThe citation is implicit and not completed of all the information even if it is precise. We don’t know exactly the name but the semantic is understandable.

Schedule 2 to the principal Act

All the articles in contrast with the present law.

4.9 Linguistic variant of the citationsIn some legal systems, like the European Law, Switzerland or South Africa legal systems, it is relevant to manage also the references in different languages, all equally legally validThis means

- variations in the characters set (for example, Greek language);- translation of the metadata used in citation (for example title or type of act);- transposition in the linguistic system of numbering (e.g., α instead of a);

The reference is always expressed in the language of the document that contains it except if it reference a specific language version.


5 Common End-User Requirements5.1 Flexibility DefinitionIn line with the principle of proportionality and the principle of decentralization, each country and company should continue to operate its own national legal information system, e.g. Parliamentary documents, Official Journals and Legal Gazettes or legal databases in the way they prefer.

We should therefore construct carefully a system to cite and identify legislation in order to respect the legal and constitutional differences between countries. The trade-off for this flexibility is that implementing such a solution requires a degree of judgment, thought and experience and that we agree and accept that there will be some differences in the solutions found by different countries or entities.

Example

narrative use case codification

5.2 Usability DefinitionThe creation of identifier for legal source should be usable and for achieving this goal we should take in consideration the following criteria:

Build for humans and computer readable URIs (recommend http URIs)

Start designing with data and not with pages

- document your URI schema

- use information that don’t change over time to build URIs

Identify your first order objects and make them addressable

Use user-friendly, readable, reliable and hackable URIs;

- ask yourself how the users cite your legislation

- put forward the social considerations and not the technical function of the URI

Keep URIs simple and add additional information in the metadata

The publishers should have complete freedom to create their own identifiers with a set of building blocks out of a common toolbox.

URI should not only have a technical consideration, but also a social consideration. Identifiers for our legislation should be user-friendly and popular in its terms of use.

Any additional information you may want to add could be added to the metadata which you will receive when you dereference the identifier. For this, one essential requirement is that you have an HTTP URI.


In essence, it is important that the URI is flexible and user-friendly with well-defined consistent metadata. Finding the minimum level of agreement on the basis of common building blocks, will enhance interoperability, and therefore would feasible and could be implemented by many.

Example


5.3 Human Readable Definition

Depending on the legal environment, users identify or cite legislation differently, some use the type (Law, constitution etc.), others include date references (date of signature, date of publication, date of consolidated act etc.), other use common names for a given act of legislation.For the identification and citation of legislation, simple general blocks should be used.Out of these blocks a simple unique identifier could be constructed which is recognizable, readable and understandable by both humans and computers, and which is compatible with existing technological standards. In addition, a common set of standardized metadata elements to describe legislation in compliance with a recommended ontology could be presented in order to guarantee interoperability.

5.4 Interoperability Definition

The URI/IRI elaborated by the LegalCiteM TC should permit to navigate among different national document collections also composed by heterogeneous type of documents. Interconnection between different legal resources despite the origin, jurisdiction, legal tradition, versioning, language variant, is an important requirement for saving the possibility to point out the authentic source of the information. .

ExampleOne possible example of scenario is a publisher that intends to use this URI/IRI mechanism for legal books and so to connect a variety of legislative references coming from different Official on-line Gazettes or Official Journals. The LegalCiteM should provide a common and easy mechanism for citing heterogeneous legal resources using a common standard.

5.4.1 Multilinguism Definition

The URI/IRI elaborated by the LegalCiteM TC should permit to reference a specific linguistic variant. It should also permit reference without specifying a language (default language depend on the context).The URI/IRI elaborated by the LegalCiteM TC should permit to reference to a multilingual document.

Example



syntax example

5.4.2 Alias Definition

The legislative document can have alias or abbreviation or acronim. Alias feature permits to nominate the same document in multiple manner. The important requirement is that also the alias is unique.

Example


syntax example

5.4.3 Fragment citation Definition

A fragment inside of a Legal resource is a logically sub-part of the document. The most cited fragments are the partitions or provisions inside of the normative block of the legal document (e.g. article, section, chapter, title, etc.). However it is important also to refer to preface, preamble, component inside preamble (citation, recital), ,, footnotes, conclusions, signatures, etc. It is not infrequent to see some reference to the page and line (e.g., judgments, bills, publication citations).LegalciteM should provide an easy and intuitive mechanism for referring to the fragment part inside of the document, taking in care also the technical problem of the use of # inside of HTTP protocol. The # is used inside of the HTTP protocol for referring to the internal part of the HTML file. Any data after the # is not manageable server-side. The # should be avoided, referencing an article with URIs would be very useful and also open to any future technical evolution .It is also needed to reference not normalized block (for example, blocks of annex).

Example

5.4.4 Meta Data Definitionlegislation-reqs-v1.0-wd044 Working Draft 04 17 June 2015Standards Track Draft Copyright © OASIS Open 2015. All Rights Reserved. of 72

Xxx

The attribution of metadata established in the framework of a shared syntax will set the basis to promote interchange and enhance interoperability between legal information systems. By identifying the metadata describing the essential characteristics of a resource, publishers will be able to reuse relevant information processed by others for their own needs, without having to put into place additional information systems.Therefore, while legal publishers are free to use their own metadata schema, they are encouraged to follow and use common metadata standards with shared but extensible authority tables which permit to meet specific requirements. The metadata schema proposed here is intended to be used in combination with customized metadata schemas.For the data exchange to become more efficient, metadata elements may be serialized in compliance with the W3C recommendation ‘RDFa in XHTML: Syntax and Processing’. (Maybe the technical sub-group could say why RDFa is better … one reason is already the multi-lingual …).It should be stated that consistent metadata is very important.

Example


syntax example

5.5 Legal Expert Requirements

5.5.1 Versioning and Consolidation over time Definition

The URI/IRI naming convention should manage properly the temporal evolution of the legal source over time. The versioning management is not only a technical issue. Especially in legal domain the time is an artifact used by the legislator for modeling normative statements (e.g. obligations, rights, exceptions, derogations, etc.) and for this reason it is not infrequent to have temporal legal events that produce effect in the past and in the future. This requirement includes the following situations:

consolidation of the legislation according to different event of modifications (e.g. updated version of the Tax Act);

codification or recast3 of the legislation according to a reordering of a specific domain (e.g. Code of Transport);

3 In European legislation, codification is « the procedure whereby the acts to be codified are repealed and replaced by a single act containing no substantive change to those acts. … A recast is a new legal act which incorporates in a single text both the amendments it makes to the previous act and the provisions of that previous act which remain unchanged, the new legal act replacing and repealing the previous act. The new legal act therefore amounts to a codification of the pre-existing basic act and all its amendments, but at the same time it provides for changes to the law, which are not possible in the case of a codification.” (COM(2001) 645)legislation-reqs-v1.0-wd044 Working Draft 04 17 June 2015Standards Track Draft Copyright © OASIS Open 2015. All Rights Reserved. of 72

compilation of the legislation for producing a coordinated product (e.g. U.S. Code in positive law titles, Switzerland Code);

classification of the legislation for producing an editorial product (e.g. U.S. Code in non-positive law titles [1]).For the documents in drafting stage, the reference to a version use a version number. But the system need also to reference the “last version”.

Example


syntax example

5.5.2 Variants and Translation Definition

The URI/IRI naming convention should reference a legal source that is available in different languages. The reference of a multilingual legal source can be done without specifying a specific language. In this case, the language information is given by the context. The reference can also be done to a specific linguistic variant (for example for the amendment that is language dependent). For the fragment citation, the URI/IRI elaborated by the LegalCiteM TC should take into account the fact that the normative blocks is language dependent.The URI/IRI naming convention should take into account the fact that for some legal tradition (like in European tradition), each language has the same legal importance and that there is no concept of original/translation.

Example


NB. For the European institutions, the language versions are specified using the ISO codes 639-1 alpha-2 code).

syntax example

5.5.3 Errata corrigeDefinition

Some errors may occur during the publication process in any step of the law-making workflow. This event can happen during the bill phase or in the act publication. The errors that are made during the publication process are so called "errata corrige" and they don't affect the law-making process at all. Usually they are minor typos or clerical errors. The authority in charge of the publication usually provide a new communication document where it is amended the error. The "errata corrige" enters into force since the beginning of the original document, for this reason


http://www.loc.gov/standards/iso639-2/php/code_list.php

often the name of the "errata corrige" is the same of the original legal resource. LegalCiteM should manage the URI also of those special document that is strictly connected with the original resource.

ExampleEu Parliament: For document in drafting stage, the management of the errata is done by publishing a new consolidated version of the document and change his identification by adding an erratum number. Note that the erratum is language dependent: one language can have an erratum and not the other languages variant.

Italy: the errata is a particular kind of document that is published separately in the Gazette and it needs an URI. In Italy the errata (http://www.normattiva.it/atto/caricaDettaglioAtto?atto.dataPubblicazioneGazzetta=1993-10-09&atto.codiceRedazionale=093A5697&atto.articolo.numero=1&atto.articolo.tipoArticolo=0)It is possible also to have a “Avviso di ratifica” that is a material modification by the executive ministery (http://www.normattiva.it/atto/caricaDettaglioAtto?atto.dataPubblicazioneGazzetta=1993-10-09&atto.codiceRedazionale=093A5696&atto.articolo.numero=1&atto.articolo.tipoArticolo=0)


For a proposal of legal document by the European Commission, the initial version of the document has a COM number + stage (“final” indicating that the document is adopted by the European Commission). Then each erratum has an identification built with the COM number + stage“ + a sequential number.Ex: “COM(2013) 654 final” is the initial version. An erratum for the portuguese version will be identified as “COM(2013) 654 final/2”, the other linguistic version remaining with identifier “COM(2013) 654 final”

syntax example

5.5.4 Annulment and Retroactive ModificationsDefinition

In some legal tradition the High Court or the Constitutional Court can modify the legislative act or to repeal totally or partially the normative text because it is illegal. The effect of this decision is ex-tunc or better since the beginning of the origin of the document. This phenomena produces retroactive effects and consequently the temporal versions of the original document is forked in two timelines: one without the decision and the second taking into account the High Court/Constitutional Court decision. In some legal tradition this kind of decision is erga omnes (valid for all the persons) like in Italy, France, etc. In other legal tradition this kind of decision is limited to the case like in Mexico. LegalCiteM should provide URI mechanism for expressing this situation where a legal resource has different valid versions contextually.

Example



http://www.normattiva.it/atto/caricaDettaglioAtto?atto.dataPubblicazioneGazzetta=1993-10-09&atto.codiceRedazionale=093A5697&atto.articolo.numero=1&atto.articolo.tipoArticolo=0



syntax example

5.5.5 SovereignDefinition

Sovereign is the governing legal body issuing the document. A sovereign may be a national government, supranational or international organization, or sub-national government. [Do we name the sovereign in general terms, as I did, or get more specific such as Parliament of the United Kingdom, UN Security Council, etc.?]

ExampleItaly, United States, European Union, United Nations, New York City In EU law, the legal document can be issuing by 1. the Commission or 2. the Council or 3. The Council and the European Parliament jointly.


syntax example

5.5.6 JurisdictionDefinition

Jurisdiction is the geographical or subject-matter area to which the document applies. A "decision" is binding on those to whom it is addressed (e.g. an EU country or an individual company) and is directly applicable.

ExampleAn EU law that applies only in some member states.

codification

syntax example

5.5.7 Document Component, Components and AnnexesDefinition

Legal resources sometime are composed by different autonomous works that have legal value also individually (e.g. international treaty, multilateral agreement, etc.). It is important to define the relationship among different legal resources when the compositions of some of them constitutes a new legal resource (e.g. a folder of a bill is composed by different independent works: the


executive summary, the bill itself, the declarations of some party, amendments, etc.). For this reason we can have at least four different object that we can define with

Example

narrative use case1. European legislation – drafting act

The European Commission document containing a new drafting act (called a COM document) is composed of an explanatory text called “Explanatory memorandum”, following by the proposal of a new act (with annexes and/or attached act), following by, optionally, a “financial statement”. These two components are not part of the act.

In EU law, “The annex to an act generally contains rules or technical data which, for practical reasons, do not appear in the enacting terms . The enacting terms must always indicate clearly, by means of a reference (for example, ‘listed in the Annex’, ‘in Annex I’, ‘set out in the Annex’), the link between its provisions and the annex.4”

“In contrast, there may be attached (not ‘annexed’) to an act other legal acts pre-existing it which are generally approved by it. Examples of acts which may be set out in this way are rules of subordinate bodies and international agreements. Such attached acts, in particular international agreements, may themselves have annexes. Such acts are not preceded by the word ‘ANNEX’.5”

When adopted by the Commission, the document is identified with a COM number with a “final” stage. To reference to the act drafted included in the COM document, people can refer to the COM number.

codification

syntax example

5.6 Archival Requirements

5.6.1 Open vocabulary Definition

xxx

Example


syntax example

4 Interinstitutionnal style guide5 Joint practical guidelegislation-reqs-v1.0-wd044 Working Draft 04 17 June 2015Standards Track Draft Copyright © OASIS Open 2015. All Rights Reserved. of 72

5.6.2 Authenticity

Definition

Authenticity refers to a document with a security system in place to ensure that it is unaltered from the original, indicating trustworthiness and reliability.

Example

The United States GPO uses a Public Key Infrastructure system to certify that the information has remained in the intended chain of custody with no alterations to the original, intended information. The system displays a visible Seal of Authenticity to users to verify authenticity. SYNTAX EXAMPLE

syntax example

Official

DefinitionOfficial refers to the published source designated by the sovereign as the source for the information. Official is contrasted with unofficial. An unofficial source has not been designated as the published source by the sovereign. In case of differences between an official and unofficial source, the official source would control.

Example

The United States has designated the United States Code as the official source for the codified federal laws of the United States. [cite?] Commerical publishers also produce versions of the United States Code. Two examples are the United States Code Annotated and the United States Code Service. While these unofficial versions are meant to contain the same text of the laws as the United States Code, they are not published by direction of the sovereign, and in the case of a difference between the United States Code and either unofficial source, the official United States Code would control.

syntax example

5.6.3 Provenance Definition

The provenance is fundamental for communicating the authoritativeness of the legal resource.

Example



5.7 Citations per document type

5.7.1 Constitution

5.7.2 Act

5.7.3 Bill

Consolidated Fund HC Bill (2008-09) [5] title | HC Bill | (session) | [number] OR title | HL Bill | (session) | number

5.7.4 European documentsDecision

Directive

Regulation

Communication

5.7.5 Treaty Consolidated Version of the Treaty on European Union [2010] OJ C83/13

5.7.6 Code

5.7.7 Consolidated act

5.7.8 Gazette, Journal


6 Existing pilot cases

6.1 ELI

6.1.1 Luxembourg pilot casePublisher: Government - Official JournalMark-up is done manually and the URI links are added to the XML structured data.

References or citations to other acts are mainly mentioned by “Type” and “Date”.e.g.: http://eli.legilux.public.lu/eli/etat/leg/loi/2014/04/02/n3/jo/references

Loi du 2 avril 2014 portant 1. modification - du Code de la consommation, - de la loi modifiée du 14 août 2000 relative au commerce électronique, - de la loi modifiée du 30 mai 2005 relative aux dispositions spécifiques de protection de la personne à l'égard du traitement des données à caractère personnel dans le secteur des communications électroniques et portant modification des articles 88-2 et 88-4 du Code d'instruction criminelle, - de la loi modifiée du 8 avril 2011 portant introduction d'un Code de la consommation; 2. abrogation de la loi modifiée du 16 juillet 1987 concernant le colportage, la vente ambulante, l'étalage de marchandises et la sollicitation de commandes.(Mém. A - 64 du 22 avril 2014, p. 660)

Modifie:Loi du 08 avril 2011 (Mém. A-69 du 12 avril 2011, p.1120)

Loi du 30 mai 2005 (Mém. A-73 du 07 juin 2005, p.1168)

Loi du 14 août 2000 (Mém. A-96 du 08 septembre 2000, p.2176)

Citant:Loi du 02 septembre 2011 (Mém. A-198 du 22 septembre 2011, p.3602)

Loi du 24 mai 2011 (Mém. A-108 du 26 mai 2011, p.1694)

Loi du 29 avril 2009 (Mém. A-88 du 30 avril 2009, p.1028)


Loi du 18 décembre 2006 (Mém. A-223 du 21 décembre 2006, p.3802)

Loi du 17 mai 2004 (Mém. A-76 du 26 mai 2004, p.1112)



Loi du 16 avril 2003 (Mém. A-61 du 08 mai 2003, p.1026)

Loi du 30 juillet 2002 (Mém. A-90 du 12 août 2002, p.1830)

Loi du 18 décembre 1998 (Mém. A-4 du 26 janvier 1999, p.70)

Loi du 27 juillet 1997 (Mém. A-65 du 03 septembre 1997, p.2048)

Loi du 14 juin 1994 (Mém. A-58 du 06 juillet 1994, p.1092)

Loi du 09 août 1993 (Mém. A-66 du 24 août 1993, p.1181)


Loi du 25 août 1983 (Mém. A-70 du 01 septembre 1983, p.1494)

Abroge:Loi du 16 juillet 1987 (Mém. A-61 du 31 juillet 1987, p.1175)


Sometimes the short title is also added in citations.Exemple: « Loi du 29 mars 2013 relative à l'organisation du casier judiciaire et aux échanges d'informations extraites du casier judiciaire entre les états membres de l'union européenne et modifiant »Law of 29 March 2013 concerning (in French: “relative”) the organization of …

The URI structure only takes into account non modifying elements, like Type, Dates In this case the URI would be http://eli.legilux.public.lu/eli/etat/leg/loi/2013/03/29/n10 Elements of the URI structure explained with an example:

http://eli.legilux.public.lu/eli/etat/leg/loi/2011/04/08/n2

Details for building the URI from different building blocks “metadata”

Loi http://eli.legilux.public.lu/eli/etat/leg/loi/

2011 http://eli.legilux.public.lu/eli/etat/leg/loi/2011/

Avril http://eli.legilux.public.lu/eli/etat/leg/loi/2011/04/

8 http://eli.legilux.public.lu/eli/etat/leg/loi/2011/04/08/

n2 To have a unique ID at the end to make the URI unique, in the case of Luxembourg we decided to use the sequence of publishing.

Of course we could also have added another number from the database e.g. 123456 or something else, but for user-friendliness we have chosen to keep it simple to remember.

Below you have the original Text from the introduction text in the law:

Texte modifié dernièrement par:

Loi du 27 avril 2015 déterminant le régime des sanctions applicables en cas de violation des dispositions du règlement (UE) n° 181/2011 du Parlement européen et du Conseil du 16 février 2011 concernant les droits des passagers dans le transport par autobus et autocar et modifiant le règlement (CE) n° 2006/2004, et modifiant1) les articles L. 311-5 et L. 311-6 du Code de la consommation,2) l'article 7bis de la loi modifiée du 29 juin 2004 sur les transports publics.

Version publiée


http://eli.legilux.public.lu/eli/etat/leg/loi/2011/04/08/n2

Loi du 8 avril 2011 portant introduction d'un Code de la consommation.

Nous Henri, Grand-Duc de Luxembourg, Duc de Nassau,

Notre Conseil d'Etat entendu;

De l'assentiment de la Chambre des Députés;

Vu la décision de la Chambre des Députés du 5 avril 2011 et celle du Conseil d'Etat du 8 avril 2011 portant qu'il n'y a pas lieu à second vote;

Avons ordonné et ordonnons:

Art. 1er.

Les dispositions annexées à la présente loi constituent le Code de la consommation.

Art. 2.

Sont abrogés:

– la loi modifiée du 25 août 1983 relative à la protection juridique du consommateur;

– la loi modifiée du 9 août 1993 réglementant le crédit à la consommation;

– la loi modifiée du 14 juin 1994 portant réglementation des conditions d'exercice des activités relatives à l'organisation et à la vente de voyages ou de séjours et portant transposition de la directive du 13 juin 1990 concernant les voyages, vacances et circuits à forfait;

– la loi modifiée du 18 décembre 1998 relative aux contrats portant sur l'acquisition d'un droit d'utilisation à temps partiel de biens immobiliers;

– les articles 52bis à 59 de la loi modifiée du 14 août 2000 relative au commerce électronique;

– la loi modifiée du 16 avril 2003 concernant la protection des consommateurs en matière de contrats à distance;

– la loi modifiée du 19 décembre 2003 fixant les conditions d'agrément des organisations habilitées à intenter des actions en cessation;

– la loi modifiée du 21 avril 2004 relative à la garantie de conformité;

– les alinéas 6 à 10 de l'article 2 de la loi modifiée du 17 mai 2004 relative à la concurrence;

– la loi modifiée du 18 décembre 2006 sur les services financiers à distance;

– la loi du 23 avril 2008 relative à la recherche et à la sanction des violations des droits des consommateurs;

– la loi du 29 avril 2009 relative aux pratiques commerciales déloyales.

Art. 3.…….

Modification• du Code de la consommation,• de la loi modifiée du 14 août 2000

relative au commerce électronique,

This law modifies :Different CodesThe law of August 14 2000 regarding

electronic commerceEtc.

Remarks:


• de la loi modifiée du 30 mai 2005 relative aux dispositions spécifiques de protection la personne à l'égard du traitement des données à caractère personnel dans le secteur des communications électroniques et portant modification des articles 88-2 et 88-4 du Code d'213instruction criminelle,

• de la loi modifiée du 8 avril 2011 portant introduction d'un Code de la consommation;

Does not mention what exactly is modified

abrogation de la loi modifiée du 16 juillet 1987 concernant le colportage, la vente ambulante, l'étalage de marchandises et la sollicitation de commandes.

Repeals law and all the modifiers of 16 July 1987 act

Nous Henri, Grand-Duc de Luxembourg, Duc de Nassau Signed by Grand Duc Henri

De l'assentiment de la Chambre des Députés With the assent of the Parliament: no exact reference to a document

Vu la décision de la Chambre des Députés du 11 mars 2014 et celle du Conseil d'Etat du 25 mars 2014 portant qu'il n'y a pas lieu au second vote

Reference to consent of Parliament and “Conseil d’Etat”– only date is mentioned no reference to an exact document


«Art. L. 211-7. (1) Lorsque du fait du choix des parties le droit d’un pays tiers est applicable au contrat, le ……suivantes:–la directive 1999/44/CE du Parlement européen et du Conseil du 25 mai 1999 sur certains aspects de la vente et des garanties des biens de consommation;

Lorsque le droit applicable au contrat est celui d’un pays tiers, le règlement (CE) n°593/2008 s’applique afin de déterminer si le consommateur continue de bénéficier de la protection garantie par la directive 2011/83/UE du Parlement européen et du Conseil du 25 octobre 2011 relative aux droits des consommateurs, modifiant la directive 93/13/CEE du Conseil et la directive 1999/44/CE du Parlement européen et du Conseil et abrogeant la directive 85/577/CEE du Conseil et la directive 97/7/CE du Parlement européen et du Conseil.»

Cites EU Directives and Regulations

Remarks :No indication to which version in

time.

6.1.1.1 URI Schema

The URI schema is based on how legislation is cited, with elements which do not change over time.

URI structure: http://eli.legilux.public.lu/eli/etat/leg/{type}/{year}/{month}/{day}/{id}

Legilux.public.lu Luxembourg official Journal website


Public in Luxembourg we have for all official Government internet sites in the URL the Word “public”

lu for Luxembourg

eli to show that it is a European Legislation Identifier

leg or adm “LEG” for Legislation “ADM” for administrate circulars for example

Type Nature of the act (law, decree, draft bill, etc.)

Year / Month / day Date of signature of the act (not date of Publication)

Id Unique identifier


http://eli.legilux.public.lu/eli/etat/leg/{type}/{year}/{month}/{day}/{id}

http://eli.legilux.public.lu/eli/etat/leg/{type}/{year}

For example :http://eli.legilux.public.lu/eli/etat/leg/loi/2013

Result would give all the laws of 2013

http://eli.legilux.public.lu/eli/etat/leg/{type}/{year}/{month}

For example :http://eli.legilux.public.lu/eli/etat/leg/loi/2013/03

Result would give all the laws of March 2013

http://eli.legilux.public.lu/eli/etat/leg/{type}/{year}/{month}/{day}

For example :http://eli.legilux.public.lu/eli/etat/leg/loi/2013/03/29

Result would give all the laws of 29 March 2013

http://eli.legilux.public.lu/eli/etat/leg/{year}

For example :http://eli.legilux.public.lu/eli/etat/leg/2013

Result would give all kind of acts for 2013

6.1.1.2 Use case for Constitutional Courthttp://eli.legilux.public.lu/eli/etat/leg/acc/2013/07/12/n1


http://eli.legilux.public.lu/eli/etat/leg/2013

http://eli.legilux.public.lu/eli/etat/leg/loi/2013/03/29

http://eli.legilux.public.lu/eli/etat/leg/loi/2013/03

http://eli.legilux.public.lu/eli/etat/leg/loi/2013

Arrêt de la Cour constitutionnelle12 juillet 2013Dans l’affaire n° 00100 du registre ayant pour objet une demande de décision préjudicielle conformément à l’article 6 de la loi du 27 juillet 1997 portant organisation de la Cour Constitutionnelle, introduite par le Conseil supérieur de la sécurité sociale suivant arrêt du 8 février 2013, (n° 2013/0006), parvenue au greffe de la Cour constitutionnelle le 20 février 2013 dans le cadre d’un litige opposant…..:1) L’article 29 point 2 de la loi modifiée du 30 juin 1976 portant 1. création d’un fonds pour l’emploi;…… 2) L’article 29 point 2 de la loi modifiée du 30 juin 1976 portant 1. création d’un fonds pour l’emploi; 2.

Sometimes one can find a reference to an article of a legal act:“L'article 29 point 2 de la loi modifiée du 30 juin 1976 portant 1

Reference to an article, but points to the initial law.

No indication to which point in time for the article is to be considered.

All references are made to the act as published, not to any point in time when the original act was modified.

6.1.1.3 Reference to point in time and consolidated versionIn Luxembourg it is not possible, for the moment, to refer, technical wise, to a point in time of a given act. The below draft URI structure is ready but not implemented. http://eli.legilux.public.lu/eli/etat/leg/{type}/{year}/{month}/{day}/{Sub-Level}/{id}/{version}{Point in Time}/{Language}

Version To distinguish between original act or consolidated version


http://eli.legilux.public.lu/eli/etat/leg/loi/1976/06/30/n1/jo

Point in Time YYYYMMDD Version of the act as valid at a given date

Sub Level e.g. Art section etc. Reference to a subdivision of an act, e.g. Article 15

Language To differ different official expressions of the same act Use of DCTERMS.ISO3166: 3 alpha

Example: http://eli.legilux.public.lu/eli/etat/leg/rgd/2009/12/10/n1/consolide/will be redirected to the latest consolidated version e.g. 2 January 2013 http://eli.legilux.public.lu/eli/etat/leg/rgd/2009/12/10/n1/consolide/20130102

6.1.2 France pilot casePublisher: DILA (Direction de l’Information Légale et Administrative) - Official Journal

6.1.2.1 Constitution

Constitution articles are mentioned by “Article number.” Example: “Article 4 de la Constitution de la cinquième République française”

6.1.2.2 Code

Provisions of the Code are mentioned by “Code name” and “Article number”Example: “Code de l'action sociale et des familles - Article L111-1” legislation-reqs-v1.0-wd044 Working Draft 04 17 June 2015Standards Track Draft Copyright © OASIS Open 2015. All Rights Reserved. of 72

http://eli.legilux.public.lu/eli/etat/leg/rgd/2009/12/10/n1/consolide/20130102

http://eli.legilux.public.lu/eli/etat/leg/rgd/2009/12/10/n1/consolide/20130102

6.1.2.3 Other legislative and regulatory texts

Laws, ordonnances, and decrees are mentioned by “Type”, “Natural identifier”, “Date”, and “Title”.Example: “LOI n° 2014-1655 du 29 décembre 2014 de finances rectificative pour 2014 (rectificatif)”

Most of other types of texts like “arretes” are mentioned by “Type”, “Date”, and “Title”.Example: “Circulaire du 9 janvier 2015 relative à la prolongation de la mise en berne des drapeaux sur les bâtiments et édifices publics”

6.1.2.4 URI building blocks for France

Constitution articles and Code article won’t have an ELI URI. For the moment, ELI will be implemented only for the other legislative and regulatory texts that where published since 1/1/2002 in Official Journal.

Using common building blocks, the following schema has been retained for France:/eli/{type}/{year}/{month}/{day}/{natural identifier}/{version}/{level}/{point in time}/fr/{format}

There is also a shortcut for the HTML version of a text:/eli/{type}/{year}/{month}/{day}/{natural identifier}/{version}/texte/{point in time}

The natural identifier takes two possibilities to ensure backwards compatibility. Yyyy-Number of law in the specified year + “R” + Rectification numberORNOR (12 alphanumeric characters)

Example 1: http://www.legifrance.gouv.fr/eli/loi/2014/12/29/2014-1655R1/jo/texteExample 2: http://www.legifrance.gouv.fr/eli/loi/2014/12/29/FCPX1425969Z/jo/texte

Both examples give access to the html version in the French language, equivalent to: http://www.legifrance.gouv.fr/eli/loi/2014/12/29/FCPX1425969Z/jo/texte/fr/html

Building blocks of the URI:

name Format value comments

Type Letters

loi, arrete, circulaire, decret, ordonnance, rapport…

No limitative list of values


http://www.legifrance.gouv.fr/eli/loi/2014/12/29/FCPX1425969Z/jo/texte/fr/html

http://www.legifrance.gouv.fr/eli/loi/2014/12/29/FCPX1425969Z/jo/texte

http://www.legifrance.gouv.fr/eli/loi/2014/12/29/2014-1655R1/jo/texte


Year Yyyy Always 4 digits

Month Mm No padding with 0

Day Dd No padding with 0

Natural identifier

2 possibilities :

yyyy-Number of law in the specified year + “R” + Rectification number (if there is a rectification, max=3 rectifications )

NOR (12 alphanumeric characters)

Before 2000, use 2 digits for yyyy

NOR is an unique alias that exists (since 1987) to ensure backward compatibility with previous systems

Point in time yyyymmdd

Version of the text at a given date.

This parameter is optional. When omitted, the latest in force version is returned.

Version 2 letters jo, lc

“jo” means the original version of the legislative text

“lc” means the consolidated version of the legislative text

Level Letters texte, article_

Texte gives the entire textArticle_ followed by the name of the article gives access to one article of the text

Language 2 letters fr Only one official language



Format Letters

pdf, rtf, html (rdf will be implemented later)

6.1.2.5 Examples for texts

6.1.2.5.1 HTML version of a non-consolidated lawText as cited: Loi n° 2014-1170 du 13 octobre 2014 d'avenir pour l'agriculture, l'alimentation et la forêt (rectificatif){type} {year} {month} {day} {natural identifier} {version } {level} {point in time} {format}loi 2014 10 13 AGRX1324417Z jo texte

or 2014-1170R1URIs:http://www.legifrance.gouv.fr/eli/loi/2014/10/13/AGRX1324417Z/jo/texte http://www.legifrance.gouv.fr/eli/loi/2014/10/13/2014-1170R1/jo/texte

6.1.2.5.2 PDF version of a non-consolidated law

Text as cited: LOI n° 2014-1655 du 29 décembre 2014 de finances rectificative pour 2014 (rectificatif)

{type} {year} {month} {day} {natural identifier} {version } {level} {point in time} {format}loi 2014 12 29 FCPX1425969Z jo texte pdf

or 2014-1655R1

URIs:http://www.legifrance.gouv.fr/eli/loi/2014/12/29/FCPX1425969Z/jo/texte/fr/pdfAlias:http://www.legifrance.gouv.fr/eli/loi/2014/12/29/2014-1655R1/jo/texte/fr/pdf

6.1.2.5.3 HTML version of a consolidated law at a given date (hypothetical, not yet implemented)

Text as cited (it doesn’t exist): Décret n° 2014-9998 du 31 décembre 2014 portant diverses mesures réglementaires de transposition de la directive 2012/999/CE relative à la chasse aux grands fauves (NOR : ABC01234567Q, fictitious)

{type} {year} {month} {day} {natural identifier} {version } {level} {point in time} {format}


http://www.legifrance.gouv.fr/eli/loi/2014/10/13/2014-1170R1/jo/texte

decret 2014 12 31 2014-9998 lc texte 20150101Or ABC01234567Q

URIs:http://www.legifrance.gouv.fr/eli/decret/2014/12/31/2014-9998/lc/texte/20150101Alias:http://www.legifrance.gouv.fr/eli/decret/2014/12/31/ABC01234567Q/lc/texte/20150101

6.1.2.6 Examples for articles of texts

Article 1 de la loi n° 2014-1170 du 13 octobre 2014 d'avenir pour l'agriculture, l'alimentation et la forêtArticle as cited: Article 1er de la loi n° 2014-1170 du 13 octobre 2014 d'avenir pour l'agriculture, l'alimentation et la forêt

{type} {year} {month} {day} {natural identifier} {version } {level} {point in time} {format}loi 2014 10 13 AGRX1324417L jo article_

or 2014-1170

URIs: http://www.legifrance.gouv.fr/eli/loi/2014/10/13/AGRX1324417L/jo/article_1Alias:http://www.legifrance.gouv.fr/eli/loi/2014/10/13/2014-1170/jo/article_1

6.1.2.7 HTML version of a consolidated CODE at a given date (not yet implemented)

Shall we add this use case, even though France has not implemented it yet ? It is interesting because it is a Code.

6.1.2.8 Official Journal entries

Each Official Journal, since 1/1/2002, has its own URI ELI, based on the date of publication of it.There is a unique form of URI to access to the HTML version of the summary of an Official Journal, published in this period:

/eli/{type}/{year}/{month}/{day}

Name Format value CommentsType 2 letters jo Only one valueYear yyyy Always 4 digitsMonth mm No padding with 0


http://www.legifrance.gouv.fr/eli/decret/2014/12/31/ABC01234567Q/lc/texte/20150101

Day dd No padding with 0

Example: http://www.legifrance.gouv.fr/eli/jo/2015/1/21 gives access to the JO published on the 21st January 2015.

6.1.3 UK pilot case

Sources:http://www.legislation.gov.uk/help#referLegislation http://www.legislation.gov.uk/developer/uris http://www.legislation.gov.uk/pdfs/GuideToRevisedLegislation_Oct_2013.pdf http://en.wikipedia.org/wiki/Citation_of_United_Kingdom_legislation

6.1.3.1 Reference to legislation in academic work or publication

The way in which legislation should be referred to in academic work and publications depends on the referencing style adopted by the academic institution or publishing house in question. For example, many universities use style guides based on the Harvard Referencing Style. The particular style requirements of each institution or publisher may differ, however, and you should always check with your faculty or publisher how they expect you to refer to legislation in your work. Bearing this in mind, you may find the following information useful: Title, year and number

The formats described here reflect generally accepted practice among legislators and legal practitioners.

Public General Acts of the UK ParliamentThese may be cited by the short title (which includes the year) and chapter number (bracketed), e.g. Constitutional Reform Act 2005 (c. 4).Citations of pre-1963 Acts may also contain a reference to the 'regnal year' (that is, the year of the sovereign's reign) of the session of parliament in which the Act was passed, e.g. Statute of Westminster 1931 (22 and 23 Geo. 5 c. 4). This means that the Act was passed in 1931 during the session of Parliament spanning the 22nd and 23rd years of the reign of King George the Fifth.

Local Acts of the UK ParliamentThese may be cited by the short title (which includes the year) and chapter number in Roman numerals (bracketed), e.g. London Local Authorities Act 1996 (c. ix)

Acts of Earlier ParliamentsThese may be cited in exactly the same way as UK Public General Acts except that, in the case of Acts of the old Scottish or Irish parliaments, there might also be a letter 'S' or 'I' as appropriate in square brackets at the end of the citation, e.g. Writs Act 1672 (c. 16 [S])

Acts of the Scottish Parliament


These may be cited by the short title (which includes the year) and 'asp' number (bracketed), e.g. Human Tissue (Scotland) Act 2006 (asp 4).

Acts of the Northern Ireland Assembly (and other primary legislation for Northern Ireland)These may be cited by the short title (which includes the year) and chapter number (bracketed), e.g. Social Security Act (Northern Ireland) 2002 (c. 10).

Acts of the Parliament of Northern Ireland (1921 to 1972) and Measures of the Northern Ireland Assembly (1974 only) are cited in exactly the same way as Acts of the Northern Ireland Assembly.For the citation of Northern Ireland Orders in Council, see under 'Statutory Instruments' below.

Church MeasuresThese may be cited by the short title (which includes the year) and Measure number (bracketed), e.g. Clergy Discipline Measure 2003 (No. 3).

Statutory InstrumentsThese may be cited by the title (which includes the year) and Statutory Instrument (S.I.) number (bracketed), e.g. The Detergents Regulations 2005 (S.I. 2005/2469).Northern Ireland Orders in Council (which are in the form of Statutory Instruments), will be cited similarly, but with the addition of the 'N.I'series number, e.g. The Budget (Northern Ireland) Order 2005 (S.I. 2005/860) (N.I. 3.).

Scottish Statutory InstrumentsThese may be cited by the title (which includes the year) and Scottish Statutory Instrument (S.S.I.) number (bracketed), e.g. The Tuberculosis (Scotland) Order 2005 (S.S.I. 2005/434).

Statutory Rules of Northern IrelandThese may be cited by the title (which includes the year) and Statutory Rules (S.R.) number (bracketed), e.g. The Quarries Regulations (Northern Ireland) 2006 (S.R. 2006/205).

Church InstrumentsThese instruments do not have any series numbers, perhaps because there are so few of them. They are generally cited by date in the style: Instrument dated 14.12.2000 made by the Archbishops of Canterbury and York or, occasionally: Archbishops' Instrument dated 14.12.2000.

AuthorThere is no readily identifiable 'author'of an Act or Statutory Instrument in the same way as there is an author of a book or article. If there could be said to be an 'author'it would be the Crown. Check with your faculty or publisher whether this information is really needed in the reference and, if so, how they want it to be expressed.

PublisherThis information can be found on the printed Act or instrument, or in the bound volume. Except for very old legislation (before 1889), the publisher will either be His or Her Majesty's Stationery Office ('HMSO') or. since 1996 (1997 for Acts).'The Stationery Office Limited' (a private company which publishes legislation under the authority and superintendence of HMSO under contract).


Place of PublicationThe 'place of publication' is only ever given as 'UK' on printed copies of legislation. If a more particular location is really required, the place of publication can generally be taken to depend on the legislature from which the legislation originated: London (for Acts of the UK parliament and Statutory Instruments made under them); Edinburgh (for Acts of the Scottish Parliament and Scottish Statutory Instruments); Belfast (for Acts of the Northern Ireland Assembly and Statutory Rules of Northern Ireland made under them); or Cardiff (for Measures of the National Assembly for Wales or Statutory Instruments made by the Assembly).

How to cite the revised version of an ActYou would cite a revised version of an Act in exactly the same way as you would cite the Act as originally enacted (i.e., in this case, the XXX Act YYYY (c. NN)) but, by convention, you might then add "(as amended)" to indicate that you are referring to the revised version.

Other UK Citation StylesThe citation styles listed above are those generally followed however there are some variations which are also often used. - It’s common for citations to legislative documents to exclude either the title or the series number, e.g. “Superannuation Act 1972” or “1972 c. 11” rather than “Superannuation Act 1972 (c. 11)”. Sometimes the missing part of the reference is provided in an accompanying footnote (you can see an example in http://www.legislation.gov.uk/uksi/2014/1229/article/2/made ). - It’s also common for documents to include definitions of abbreviated citations that have a limited reference scope, e.g. “In this Act, “ALDA 1979” means the Alcoholic Liquor Duties Act 1979” and “the 1986 Act” means the Insolvency Act 1986” (see http://www.legislation.gov.uk/ukpga/2013/29/section/235 for some examples).- It should also be noted that most UK legislation contains a provision that specifies how it should be cited (i.e. it defines the document’s short title) e.g. see http://www.legislation.gov.uk/uksi/2014/1229/article/1/made and http://www.legislation.gov.uk/ukpga/2010/1/section/2 for examples.

6.1.3.2 URI structure reflecting UK legislation:http://www.legislation.gov.uk/developer/uris

3 levels of URIs are defined

identifier URIs; for example, "The Transport Act 1985", http://www.legislation.gov.uk/id/ukpga/1985/67

document URIs; for example, "The current version of The Transport Act 1985" (as opposed to a previous version), http://www.legislation.gov.uk/ukpga/1985/67

representation URIs; for example, "The current version of The Transport Act 1985 in XML" (as opposed to an HTML document), http://www.legislation.gov.uk/ukpga/1985/67/data.xml

We recommend that you link to identifier URIs.

When you request an identifier URI, the response will usually be a 303 See Other redirection to a document URI. When you request a document URI, you will usually get a 200 OK response and a


Content-Location header that will point to an appropriate representation URI based on the Accept headers that you use in the request.

Identifier URIs generally follow the template:http://www.legislation.gov.uk/id/{type}/{year}/{number}[/{section}]

However, legislation is often quoted without a chapter number, which can make it hard to automatically construct these URIs. If you don’t know the chapter number for a piece of legislation, you can use a search URI of the form: http://www.legislation.gov.uk/id?title={title}

If the title is recognized, this will result in a 301 Moved Permanently redirection to the canonical URI for the legislation.

For example, requesting:http://www.legislation.gov.uk/id?title=The%20Transport%20Act%201985will result in a 301 Moved Permanently redirection tohttp://www.legislation.gov.uk/id/ukpga/1985/67

On occasion, items of legislation have very similar titles, and the title search will result in multiple possibilities. In this case, the response will be a 303 Multiple Choices containing a simple XHTML document.

For example, requestinghttp://www.legislation.gov.uk/id?title=Disability%20Rights%20Commission%20Act will result in a document containing multiple results • The Disability Rights Commission Act 1999 (Commencement No.3) Order 2006• The Disability Rights Commission Act 1999 (Commencement No. 2 and Transitional Provision) Order 2000• The Disability Rights Commission Act 1999 (Commencement No. 1 and Transitional Provision) Order 1999• Disability Rights Commission Act 1999(repealed)

Interesting approach: User testing has shown that users want an updated in force version of an act. http://www.legislation.gov.uk/ukpga/2002/30/schedule/7 redirects to the latest in force versionhttp://www.legislation.gov.uk/ukpga/2002/30/schedule/7?timeline=true shows a timeline with different point in time versions http://www.legislation.gov.uk/ukpga/2002/30/schedule/7/2007-04-01 Same act with a point in time as 1 April 2007 UK example:

http://www.legislation.gov.uk/ukpga/2002/30/schedule/7

http://www.legislation.gov.uk Official site for UK legislationukpga Document type: in this case United Kingdom Public GeneralAct


2002 Year: 30 Chapter 30Schedule Subdivision … like a paragraph 7 Schedule number 7 http://www.legislation.gov.uk/ukpga/2002/30/schedule/7/2007-04-01 As in force on 1 April 2007

6.1.4 Publications Office of the European Union

Caveat : this section gives the current state of thinking about the ELI identifiers at the Publications Office of the European Union, and should not be considered definitive. Anything described here may evolve in the future.

6.1.4.1 General structure of the identifiersThe Publications Office will use URIs to refer to 4 different levels of abstraction of a legal resource (from most generic to most specific):Abstract Legal ResourceAn act, independently of one of its temporal version (e.g. without specifying if we refer to the original version as published in the OJ or to one of the consolidated version), independently of its language, and independently of the file format.Such URIs are said to be “abstract” identifiers, and can be used to make a reference to an act without specifying explicitly to which version. In other words, the abstract legal resource “contains” all the versionsof the same piece of legislation.

Legal ResourceA legal resource can represent a specific temporal version of an act, that is either: the original version as published in the OJ; or the consolidated versions of the legal resource that were in force at particular points in time.Corrigenda and modifiers amending the basic act are also legal resources, although they are not considered to be part of the “abstract legal resource” of the act they are correcting or modifying. Corrigenda and modifiers are rather linked to the specific resource they are correcting or modifying with a link of type “changes/changedBy”.

Legal ExpressionA specific linguistic version of a legal resource (an original version, a consolidated version, a corrigenda or a modifier)

FormatA specific file format of one of the specific linguistic version of a legal resource.

6.1.4.2 Identifying abstract legal resources (Directives and Regulations in a first stage)

The URI is a root uri (http://data.europa.eu/eli) followed by the type of document, year and natural number


URI template: http://data.europa.eu/eli/{typedoc}/{year}/{natural_number}Example: http://data.europa.eu/eli/dir/2011/83

Detailshttp://data.europa.eu/eli - Official address for ELIs published by the Publications Office{typedoc} - A code for the type of document which comes from the Resources types authority table (MDR). Codes are abbreviations for the English word indicating the type of document. Possible codes include, amongst others :dir (“directive”)reg (“regulation”)dec (“decision”)res (“resolution”)Full list of codes can be found at http://publications.europa.eu/mdr/authority/resource-type

{year} - The year in which the legal resource was published.{natural_number} - The sequence number in the number assigned by the Publications Office at the moment of the publication of the documents in the Official Journal (restarts at 1 each year)

Dereferencing a URI corresponding to an abstract legal resource would return its latest consolidated version, or, if such a version does not exist, the original version as published in the OJ.

Adding the suffix “/all” to the URI of an abstract legal resource (e.g. http://data.europa.eu/eli/dir/2002/96/all) would list all of the documents pertaining to the act : the original version, the consolidated versions, the corrigenda and the modifiers (including the modifiers in this list is an open question, it may be decided not to include them)

6.1.4.3 Identifying a specific legal resource pertaining to an actThere are distinct identifiers schemes to identify original versions of legal resources as published in the OJ, corrigenda to them, or their consolidated versions.

6.1.4.3.1 Identifying a legal resource as published in the OJ

The URI consists of the URI of the abstract legal resource followed by “/oj”URI template: http://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/ojExample: http://data.europa.eu/eli/dir/2011/83/oj

6.1.4.3.2 Identifying a corrigendumThe URI template described here is still under discussion and may evolve in the future.The URI consists of the URI of the abstract legal resource, followed by “/corr”, followed by the publication date of the corrigenda, followed by the corrigenda sequence number, and with a final “/oj”.URI template: http://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/corr/{pubdate}/{seqnumber}/ojExample: http://data.europa.eu/eli/dir/2002/96/corr/2008-10-25/1/oj


http://data.europa.eu/eli

6.1.4.3.3 Identifying a consolidated versionConsolidated versions of a legal resource have 2 types of ELI identifiers : a canonical identifier (unique for each consolidated version), and “aliases” identifiers allowing to access the up-to-date state of the legislation in force at a given point in time.

6.1.4.3.3.1 Canonical identifiers for consolidated versions are structured as follows:The URI consists of the URI of the abstract legal resource, followed by the date which indicates the date of entry into force of the last amendment introduced in the act, followed by the date of publication of the last actor involved in correcting or modifying this act.URI template: http://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/{date_entry_into_force}/{date_of_publication}Example: http://data.europa.eu/eli/cons_text/1997/7/2014-06-13/2011-10-25

6.1.4.3.3.2 “Point-in-time aliases“ for consolidated versions are structured as follow :

The consists of the URI of the abstract legal resource, followed by a date at which we would like to have the consolidated version of the text.URI template: http://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/{point_in_time}Example: http://data.europa.eu/eli/dir_del/2014/15/2014-09-21

6.1.4.3.4 Identifying a subdivision within a Legal Resource (typically an article)Identifiers for subdivisions within a Legal Resource will be introduced at a later stage, typically to make it possible to reference specific articles. While not definite, it is envisioned that these identifiers will be for example http://data.europa.eu/eli/dir_del/2014/12/oj/article/2 (the identifier for the legal resource, followed by « /article », followed by the article number).

6.1.4.4 Identifying a specific linguistic version of a legal resource (a “LegalExpression”)

Any of the ELI described above (for original versions, for corrigenda and for consolidated version) can be further refined to ask for a specific linguistic version of the corresponding legal resource.The URI consists of the URI of the legal resource, followed by a language codeURI template: http://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/oj/{lang}orhttp://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/corr/{pubdate}/{seqnumber}/oj/{lang}orhttp://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/{date_entry_into_force}/{date_of_publication} /{lang} (canonical version for a consolidated version)orhttp://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/{point_in_time}/{lang} (point in time version for a consolidated version)


Example: http://data.europa.eu/eli/dir/2011/83/oj/pororhttp://data.europa.eu/eli/dir/2002/96/corr/2008-10-25/1/oj/engorhttp://data.europa.eu/eli/dir_del/2014/15/2014-09-21/fra (point in time example for a consolidated version)

6.1.4.5 Identifying a specific format of a specific linguistic version of a legal resource

Any linguistic version can then be retrieved in a specific file format (XML, HTML, etc.)The URI consists of the URI of the linguistic expression, followed by a format codeURI template: http://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/oj/{lang}/{format}orhttp://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/corr/{pubdate}/{seqnumber}/oj/{lang}/{format}orhttp://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/{date_entry_into_force}/{date_of_publication} /{lang}/format (canonical version for a consolidated version)orhttp://data.europa.eu/eli/{typedoc}/{year}/{natural_number}/{point_in_time}/{lang}/{format} (point in time version for a consolidated version)

Example: http://data.europa.eu/eli/dir/2011/83/oj/por/htmlorhttp://data.europa.eu/eli/dir/2002/96/corr/2008-10-25/1/oj/eng/htmlorhttp://data.europa.eu/eli/dir_del/2014/15/2014-09-21/fra/pdf (point in time exemple for a consolidated version)

6.1.4.6 Incomplete identifiers for search purposesIt will be possible to use incomplete ELIs to list all the texts having the characteristics given in the URIs. For example: • http://data.europa.eu/eli/dir/2014 would give the list of all the directives of 2014.• http://data.europa.eu/eli/dir/2002/96/corr would give the list of all corrigenda for the given directive

It will also be possible to add query parameters to the incomplete ELIs, to give additional criteria that are not strictly speaking part of one of the ELI schemes described above. For example http://data.europa.eu /eli/dir/2014?author=com would return all the directives of 2014 for which the author is the European Commission. Distinguishing the query parameters from the incomplete ELIs would allow to use these parameters at any level of the identifiers, for example, without the {year} part : http://data.europa.eu /eli/dir?author=com would return all the directives for which the author is the European Commission.

It is also envisioned that adding “/all” after the ELI of an abstract resource (for example http://data.europa.eu/eli/dir/2002/96/all) would list all the legal resources pertaining to the act : original OJ version, corrigenda, modifiers (to be confirmed in the future), and all consolidated versions.


6.1.5 European Parliament Information model

In the European Parliament, the multilingualism is a basic feature:

all official languages (24 languages !) are equally important;

all parliamentary documents are published in all the official languages and

all Members of the European Parliament have the right to speak in the official language of their choice.

Another very important point is that, at the legal point of view each language is equivalent: there is no notion of original language and translation, each law must be considered as a multilingual document.

6.1.5.1 The extended document model

There is a need to define an information model that is generic, and is able to take into account the evolution, the translation and the format axis of the documents. This model is defined to have a common foundation for the definition of the document management rules and principles.

The model adopted by the European Parliament is proposed by the college of IRO (Information Resources Officers). It is fully implemented by the “Parliament Unique Repository for XML text production” (PURE-XML), the XML-oriented content repository for all the e-Parliament applications.

The identification of the documents and the references to them are build on this model.

6.1.5.1.1 General structure of the identifiers

The concept of “document” carries one semantic message and integrates versioning and translations.

The information model defined by the college of IRO highlights the distinction between the conceptual semantic message and the physical representations of the message:

A logical document is a meta-layer or high level, representing the semantic. It does not have content by itself (it is NOT a physical document), but is the semantic layer of the physical documents.It forms the high layer for registration and referencing the semantic content.

A physical document is a physical carrier of a structured set of semantic information, considered to be presented, delivered and stored in a complete unity. It is the physical representation of the conceptual content defined in the logical document.

The layer of physical representation is a complex layer. A hierarchy of three aspects are defined inside it: the content versioning, the translation and the format. The modification of the content is not done using corrigenda but by delivering a new version of the

document with all the change.For this reason, the top layer is the version layer which keeps all representations of a specific content version together: the conceptual semantic message (the logical layer) can evolve and each stage in the elaboration of the semantic message is the content version.

The middle layer is the language layer, representing all possible language representations of one content version.


Every language is of equal importance. So, a new version of the document can be written in an “original language” different than the previous version. Note that translations might need to be refined, or corrected, so the language layer has its own versioning (language correction).

The bottom layer is the format layer representing all representations of a specific content version in a specific language in all possible format


LanguageLayer

LogicalDocument

VersionDocument (v1.0)

PhysicalDocument1.0-FR-1.0

VersionDocument (v1. 1)


PhysicalDocument1.0 -EN -1.0

PhysicalDocument1.0 -DE -1.0

PhysicalDocument1.1-DE -1.0



PhysicalDocument2.0 -FR -1.0

PhysicalDocument2.0 -FR-2.0

LinguisticCorrection

SmallChange

Substantialchange

Version Layer


.PDF

FormatDocument1.0 -DE -2.0

.DOC


.HTML

FormatLayer

Small Change


SubstantialChange

LanguageLayer

The Extended Document Model

LogicalDocument


PhysicalDocument1.0-FR-1.0

VersionDocument (v1. 1)


PhysicalDocument1.0 -EN -1.0





PhysicalDocument2.0 -FR -1.0

PhysicalDocument2.0 -FR-2.0


SmallChange

Substantialchange

Version Layer


.PDF

FormatDocument1.0 -DE -2.0

.DOC


.HTML

FormatLayer

Small Change


SubstantialChange

6.1.5.1.2 The generic content model

The model identify 3 types of containers :

at the low level, the chunk is the smallest information unit that can be reused by applications, for example by the translation processing. It can correspond to a content like a paragraph.

The information block is a section of content, inside a document. An information block can be considered as semantic whole, understandable by itself, and is related to the business understanding. It may appear in multiple documents, not only in the document in which it is created. An information block may have its own business life. For example, amendment, legislative resolution, explanatory statement are all information blocks.

The document is a business deliverable. It can be created in the context of a specific stage of the parliamentary procedure. Draft reports, final reports, the “Amendments” document … are all documents.

6.1.5.1.3 The identification of the European Parliament documentsThe identification system has two levels:

the upper part identify the logical level and

the second part identify the physical level, and its 3 aspects : version, language and format.

6.1.5.1.3.1 The identification of the logical level (UDI, IBId)The logical identification of the document (UDI) and of the Information Block (IBId) was structured similarly:

eu.europa.europarl:din1:(AAAA)nnnnnnnnnn “eu.europa.europarl” is the naming authority

Scheme identification : “din1” is for document, “ibi1” is for information block

Year of the production

Sequential number

All the physical representations share the identification of the logical level.

6.1.5.1.3.2 The physical identificationThe physical identification is concatenate to the logical identification. It must in principle include all the elements of the complete versioning system:

Content versioning , including business-controlled major versioning and system-controlled minor versioning : The form of the physical document represents a stage in the elaboration of the semantic message of a logical document

Language identification Language correction, Language correction, including business-controlled major versioning and

system-controlled minor versioning : The form of the physical document represents a stage in the translation of the semantic message of another physical document by correction of the language representation

1.0FR1.0


Finally, the format is identified by the extension of the file name (.pdf, .doc, …)All the documents created by the European Parliament are identified with this convention.

6.1.5.2 Another system to identify document : the session numberAll documents that play a role in a plenary session receive a session number. This number identify only the logical document, not the physical one.The session number contains the following information1. a letter that identify the type of the document

A: reports, recommendations, and recommendations for second reading B: motions for resolutions and other session documents O: oral questions E: written questions C: documents from other institutions (like, for example, the proposal of the European Commission

for a new act) T: texts adopted RC: joint motions for resolution

2. a number that refers to the parliamentary term

3. a sequential number in the year

4. the year when the identifier is created.

6.2 Reference in European documents

6.2.1 Reference to another actInformation provided for referencing other acts are :

– title of the act– name of the institution(s)– date– number of the act– publication in the official journal

The use of this information depends on the location of the citation (title, preamble, body) and whether it is or not the first use of this reference.The information can be in the text or in a footnote associated to the reference.

Examples

6.2.2 In the title of an actRECOMMENDATION FOR SECOND READING on the Council position at first reading with a view to the adoption of a directive of the European Parliament and of the Council on the prevention of the use of the financial system for the purposes of money laundering or terrorist financing, amending Regulation (EU) No 648/2012 of the European Parliament and of the Council, and repealing Directive 2005/60/EC of the European Parliament and of the Council and Commission Directive 2006/70/EC

6.2.3 In a citation(example : COM(2015) 4 final)Having regard to the Treaty on the Functioning of the European Union


Having regard to Council Directive 2003/96/EC of 27 October 2003 restructuring the Community framework for the taxation of energy products and electricity6, and in particular Article 19 thereof,

---------------------------------------- OJ L 283, 31.10.2003, p. 51

6.2.4 In a recitalDirective 2001/97/EC of the European Parliament and of the Council7

--------------------------------------2 Directive 2001/97/EC of the European Parliament and of the Council of 4 December 2001 amending Council Directive 91/308/EEC on prevention of the use of the financial system for the purpose of money laundering (OJ L 344, 28.12.2001, p. 76)

6.2.5 In the bodyas defined in point (1) of Article 13 of Directive 2009/138/EC of the European Parliament and of the Council8, insofar as it carries out life assurance activities covered by that Directive;-----------------------------------------3 Directive 2009/138/EC of the European Parliament and of the Council of 25 November 2009 on the taking-up and pursuit of the business of Insurance and Reinsurance (Solvency II) (OJ L 335, 17.12.2009, p. 1).

When an act is referenced several times, only the first one has the footnote.

Example (COM(2014) 581 final): the propulsion of vehicles as defined by point (13) of Article 3 of Directive 2007/46/EC of the European Parliament and of the

Council17; …

The Commission shall be assisted by the ‘Technical Committee – Motor Vehicles’ (TCMV) established in Article 40(1) of Directive 2007/46/EC of the European Parliament and of the Council. That committee is a committee within the meaning of Regulation (EU) No 182/2011.

----------------------------17

Directive 2007/46/EC of the European Parliament and of the Council of 5 September 2007 establishing a framework for the approval of motor vehicles and their trailers, and of the systems, components and separate technical units intended for such vehicles (OJ L 263, 9.10.2007, p.1)

1.1.1.1 Amending act : reference to the amended provisionThe title of the amending act must mention the number of the act being amended and either indicate the title of the act, or specify what is to be amended.Where several provisions of the same act are to be amended, all the amendments are combined in a single article, comprising an introductory phrase with the reference to the amended act and points following the numerical order of the articles to be amended.Further to the foregoing, amendments to annexes containing technical passages are normally made in the annex to the amending act.

6

7

8


6.3 Reference to blocks inside actUS GPO

In the United States, the laws are not copyrighted—they are public property—but they have not always been easy to access due to lack of publication. The government now publishes the law more consistently online; many commercial publishers publish the law online behind paywalls; and there is a strong open access movement, too. The use cases presented here compare the same document published by two government sources: the Government Publishing Office (GPO), which uses public key infrastructure (PKI) to authenticate the documents, and the House Office of the Law Revision Counsel, which publishes the codified laws in XML format for easy access and use. Then, the same document is presented again from the Cornell LII, the U.S.A.’s leading open access legal publisher.

As is evident, the URI format used varies greatly among just these three publishers, with the Cornell LII URI being the most human-readable.

Sources:

U.S. GPO: http://www.gpo.gov/fdsys/search/home.action House Office of the Law Revision Counsel: http://uscode.house.gov/ Cornell LII: http://www.law.cornell.edu/

6.3.1 Types of documents and their citationU.S. legal documents are cited according to several citation systems. The most common in legal practice is The Bluebook: A Uniform System of Citation, Nineteenth edition, proprietary, published by the journal editors of the Harvard, Yale, Columbia, and the University of Pennsylvania Law journals. A typical citation is shown for each.The primary legislative documents issued by the federal legislature are:United States ConstitutionThe U.S. Constitution is cited without a date. It is named, and the article, section, and clause are given. In the case of an amendment or the preamble, that is stated (although by abbreviation). U.S. Const. art. I, § 9, cl. 2.U.S. Const. amend. XIV, § 2.U.S. Const. pmbl.United States Code (codified, current/in-force legislation)The Title of the U.S. Code, U.S. Code, and the section number are the basic elements in a citation. It is presumed that the current version is being cited. Better citations include the popular name of the law and the year.Necessary: 28 U.S.C. § 1291.Better: Comprehensive Environmental Response, Compensation, and Liability Act, 42 U.S.C. §§ 9601-9675 (2006).Public LawPublic laws are typically referred to by Public Law + Congressional term + sequential number. A year could be given, but is redundant because of the inclusion of the congressional session.Pub. L. No. 91-190Interestingly, however, these have historically been published in a set of books called United States Statutes at Large, and many citations to a public law will be to that set instead of directly to the public law.Pub. L. No. 91-190, 83 Stat. 852.legislation-reqs-v1.0-wd044 Working Draft 04 17 June 2015Standards Track Draft Copyright © OASIS Open 2015. All Rights Reserved. of 72

Private LawPriv. L. No. 94-75, 90 Stat. 2985 (1976)

6.3.2 Secondary legislative documents issued by the federal legislature are:BillA bill is an introduced piece of legislation which may or may not be eventually approved and issued as law. A bill is named by stating which of the two bodies (House or Senate) it originated + the congressional session + sequential number. A year may be provided, though it is redundant of the Congressional session.S. 516, 105th Cong. (1997)H.R. 422, 106th Cong. (1999)The following documents are produced during the process of a bill moving through houses, committees, and to a final vote. Typically, the congressional session and sequential number are used to identify the document.Committee ReportH.R. Rep. No. 101-524 (1990)Committee PrintThese are cited by a very long, descriptive title and a year.Legislative Debate123 Cong. Rec. 17,147 (1977)Hearing TranscriptThese are cited by a very long, descriptive title and a year.

6.3.3 Use case 1: United States ConstitutionHere, we see that only Cornell LII builds a URL that matches a user’s expectation. The House and GPO build a URL that is akin to a roadmap of finding the document on their servers. House Law Revision Counselhttp://uscode.house.gov/view.xhtml?path=/frontmatter/organiclaws/constitution&edition=prelimGPOhttp://www.gpo.gov/fdsys/browse/collection.action?collectionCode=GPO&browsePath=Constitution+of+the+United+States+of+America%3A+Analysis+and+Interpretation&isCollapsed=false&leafLevelBrowse=false&ycord=0

6.3.4 Cornell LIIhttp://www.law.cornell.edu/constitution

6.3.4.1 Use case 2: United States Code, 18 U.S.C. § 924Preliminary information provided at the top of the text in GPO version:18 U.S.C. United States Code, 2012 EditionTitle 18 - CRIMES AND CRIMINAL PROCEDUREPART I - CRIMES


CHAPTER 44 - FIREARMSSec. 924 - Penalties

6.3.5 GPOhttp://www.gpo.gov/fdsys/pkg/USCODE-2012-title18/html/USCODE-2012-title18-partI-chap44-sec924.htm http://www.gpo.gov/fdsys Official site for the GPO document repository pkg I believe this tells us that the public key infrastructure is used to ensure authenticityUSCODE The source we are using (a part of a standard citation)2012 The yearTitle 18 Title of the code (a part of a standard citation) html FRBR manifestation USCODE-2012-title18- Repeat of information already providedpartI-chap44 Subdivisions of the work that are not used by users or in a citationSec924 The relevant section number (a part of a standard citation)

A more meaningful URI to a user would be: http://www.gpo.gov/fdsys/pkg/USCODE-2012-title18-sec924.htmHousehttp://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title18-section924&num=0&edition=prelim http://uscode.house.gov/ Online source for the U.S. Code view.xhtml?req=granuleid:USC The source we are using (a part of a standard citation)prelimtitle 18 Title of the code (a part of a standard citation) Section924 The relevant section number (a part of a standard citation)&num=0&edition=prelim

6.3.6 Cornell LIIhttp://www.law.cornell.edu/uscode/text/18/924 http://www.law.cornell.edu Online source for this free version of the U.S. Code uscode The source we are using (a part of a standard citation)text18 Title of the code (a part of a standard citation) 924 The relevant section number (a part of a standard citation)

6.3.6.1 Use case 3: Public Law, Pub. L. No. 113-1This is only available from the GPO, not the House or Cornell LIIGPOhttp://www.gpo.gov/fdsys/pkg/PLAW-113publ1/pdf/PLAW-113publ1.pdf


http://www.gpo.gov/fdsys/pkg/PLAW-113publ1/html/PLAW-113publ1.htm http://www.gpo.gov/fdsys/ Official site for the GPO document repositorypkg I believe this tells us that the public key infrastructure is used to ensure authenticityPLAW Public law (a part of a standard citation) but ambiguous with Private law113 Congressional session (a part of a standard citation)Publ1 Sequential number of the public law (a part of a standard citation) pdf or html The FRBR manifestationPLAW-113publ1.pdf Repeated information

A more user-friendly citation would be: http://www.gpo.gov/fdsys/pkg/Pub-Law-113-1.pdf

6.3.6.2 Use case 4: Private Law, Priv. L. No. 112-1This is only available from the GPO, not the House or Cornell LIIGPOhttp://www.gpo.gov/fdsys/pkg/PLAW-112pvtl1/pdf/PLAW-112pvtl1.pdfhttp://www.gpo.gov/fdsys/pkg/PLAW-112pvtl1/html/PLAW-112pvtl1.htmhttp://www.gpo.gov/fdsys/ Official site for the GPO document repositorypkg I believe this tells us that the public key infrastructure is used to ensure authenticityPLAW Private law (a part of a standard citation) but ambiguous with Public law112 Congressional session (a part of a standard citation)pvtl1 Sequential number of the private law (a part of a standard citation) pdf or html The FRBR manifestationPLAW-112pvtl1.htm Repeated information

A more user-friendly citation would be: http://www.gpo.gov/fdsys/pkg/Priv-Law-112-1.htm

6.4 URN:LEXURN:LEX is a completed and very detailed standard based on URN, but it admit also an annotation HTTP. URN:LEX is compliance with FRBR model.

6.4.1 Italian Project URN:NIRNormeInRete was the first instance of URN:LEX naming convention. It was produced inside of the Government working group of NormeinRete.

<URN> ::= "urn:nir:" <NSS-nir><NSS-nir> ::= <document> ["@" <version>] *["*" <communication>]["$"

<manifestation>]

<reference> ::= <document> ["@" (<version> | "original")] ["~" <partition>] ["!" <property>]


6.4.1.1 The case of the Senate of ItalyOrder of the day: urn:nir:senato.repubblica;assemblea:ordine.giorno:2005-12-20Bill: urn:nir:senato.repubblica:disegno.legge:15.legislatura;1014http://dati.senato.it/19?testo_generico=26

6.4.1.2 Normattivaurn:nir:stato:legge:2015-04-17;43urn:nir:stato:costituzione

6.4.1.3 High Court of Cassation

6.4.2 LexML Brazil ProjectThe Senate of Brazil9 adopted LexML standard for marking up the legislative documents. LexML Brazil XML Schema is derived from the schemas of the Akoma Ntoso Project, and the URI naming convention is based on URN:LEX. Here after an example of URI for making the citations:

Text of the citation Federal Act No. 8666, of June 21, 1993.

URN urn:lex:br:federal:lei:1993-06-21;8666

URL http://www.lexml.gov.br/urn/urn:lex:br:federal:lei:1993-06-21;8666

6.5 Zotero for legislative resourcesZotero is a methodology for helping people to make correct citation and to create link with the original resource in the web.The main instrument used is RDF

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:z="http://www.zotero.org/namespaces/export#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:bib="http://purl.org/net/biblio#"> <bib:Manuscript rdf:about="#item_1"> <z:itemType>manuscript</z:itemType> <dc:subject>human rights</dc:subject> <dc:title>1948 Universal Declaration of Human Rights</dc:title> <z:type>UNGA Resolution 217A(III), adopted by the United Nations General Assembly on</z:type> <dc:date>10 December 1948</dc:date>

9 https://blog.law.cornell.edu/voxpop/tag/urnlex/legislation-reqs-v1.0-wd044 Working Draft 04 17 June 2015Standards Track Draft Copyright © OASIS Open 2015. All Rights Reserved. of 72

http://dati.senato.it/19?testo_generico=26

</bib:Manuscript></rdf:RDF>

Australian Citizenship Act<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:z="http://www.zotero.org/namespaces/export#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:bib="http://purl.org/net/biblio#"> <bib:Legislation rdf:about="#item_1"> <z:itemType>statute</z:itemType> <dc:subject>citizenship</dc:subject> <dc:title>Australian Citizenship Act</dc:title> <dcterms:abstract>Replaces Australian Citizenship Act 1948.</dcterms:abstract> <z:codeNumber>No. 20</z:codeNumber> <dc:date>2007</dc:date> <z:shortTitle>Australian Citizenship Act</z:shortTitle> </bib:Legislation></rdf:RDF>

6.6 LLL – US Code(from the slides of Grant Vergottini) ---> NEED TO STORNG REVISION

work ::= [docPart] [fractionPart] [qualification]docPart ::= [“/uslm”] “/” jurisdiction “/” category “/” docNamefractionPart ::= (“/” level)+

level ::= (bigLevel | smallLevel | specialLevel)bigLevel ::= (“st” | “ch” | “sch” | “pt” | “spt” | “d” | “sd” | “s” | “app” | “reorgPlans” | “courtRules” | “rule” ) (num* | range)smallLevel ::= (num* | range)specialLevel ::= (“notes” | “toc” | “srcc” | (“note” num*)

Pub. L. 101–650, title III, § 325(a)(2) à /uslm/us/pl/101/650/s325/a/2range ::= levelNum “…” [levelNum]

50 U.S.C. App. 451 et seq. à /uslm/us/usc/t50/app451…7 USC 8(b): “sections 7 through 7a-1” à /uslm/us/usc/t7/s7…7a-1qualification ::= “(“ ref “)”Resolves ambiguity in citations due to duplicates (often errors)


Distinguishing language used included “as amended by”, “as added by”, “as redesignated by”, or “relating to”.Other qualifications:

Effective but not operativeExamples:

28 USC § 1932 à /uslm/us/usc/t28/s132(/us/pl/104/317/s403/a/1)28 USC § 1932 à /uslm/us/usc/t28/s132(/us/pl/104/134/s101)

expression ::= “@” {version|date}version ::= “v” numberdate ::= year “-” month “-” day

Examples:28 USC § 121(2) on March 1, 2014 à /uslm/us/usc/t28/s121/2@2014-03-0128 USC § 121(2) as of today à /uslm/us/usc/t28/s121/2@28 USC § 121(2) as enacted à /uslm/us/usc/t28/s121/2@v1

Manifestation ::= “.” (“xml” | “html” | “pdf” | “txt” | “rdf”)Examples:

28 USC § 121(2) as XML à /uslm/us/usc/t28/s121/2.xml28 USC § 121(2) as HTML à /uslm/us/usc/t28/s121/2.html50 U.S.C. App. 451 et seq. as PDF à /uslm/us/usc/t50/app451….PDF

6.7 Akoma Ntoso (to be revised: it is an extract from the AKN Naming convention deliverable submitted in OASIS LegalDocML TC)

Akoma Ntoso naming convention is based on FRBR and it defines Work, Expression, Manifestation syntax for naming the legal sources and also for building query.

6.8 The IRI of a Work

6.8.1 The IRI for the Work as a WholeThe IRI for the Work consists of the following pieces:

The base URL of a naming authority with IRI-resolving capabilities (not relevant for the Naming Convention)

A detail fragment that organizes additional data in a hierarchical fashion:– Country or subdivision (a two-letter or code according to ISO 3166-1 or a four-letter code

according to ISO 3166-2). For an Akoma Ntoso XML representation, this value must correspond to the content of the element <FRBRcountry> in the metadata.

– Type of document. For an Akoma Ntoso XML representation, this value must correspond to the element immediately below the akomaNtoso root element (e.g., act, bill, or debateReport.).

– Any specification of document subtype, if appropriate. For an Akoma Ntoso XML representation, this value must correspond to the content of the element <FRBRsubtype> in the metadata.

– The emanating actor, unless implicitly deducible by the document type (e.g., acts and bills do not usually require actor, while ministerial decrees do). For an Akoma Ntoso XML representation, this value must correspond to the content of the element <FRBRauthor> in the <FRBRWork> section of the metadata.


– Original creation date (expressed in YYYY-MM-DD format or just YYYY if the year is enough for identification purposes). For an Akoma Ntoso XML representation, this value must correspond to the content of element <FRBRdate> in the <FRBRExpression> section of the metadata.

– Number or title or other disambiguating feature of the Work (when appropriate, otherwise the string nn). For an Akoma Ntoso XML representation, this value must correspond to the content of element <FRBRnumber> or <FRBRname>, respectively, in the metadata.

All components are separated by forward slashes (“/”) so as to exploit relative IRIs in references. [http://www.authority.org]/akn/dz/debaterecord/2004-12-21

Algerian parliamentary debate record, 21st December 2004. [http://www.authority.org]/akn/sl/act/2004-02-13/2

Sierra Leone enacted Legislation. Act number 2 of 2004. [http://www.authority.org]/akn/ng/bill/2003-05-14/19

Namibia Bill number 19 of 2003 [http://www.authority.org]/akn/mg/act/2003-03-12/3

Madagascar. Act 3 from 2003 [http://www.authority.org]/akn/ke/act/decree/MinistryForeignAffairs/2005-07-12/3

Kenya, Decree n. 3 of 2005 by the Ministry of Foreign Affairs

6.8.2 The IRI for WorkComponentsFor the components like the schedule, attachment and similar we have the following syntax:

1. The number part of the Work-level IRI (/nn/) is required even in unnumbered documents ("/nn/" for not numbered) and

2. The Expression fragment, if present, always has at least the language and the "@" character, and the @ character can only be used for Expression fragments, the absence of a part containing the "@" character indicates a Work-level component reference after the 4th component (the number). For an Akoma Ntoso XML representation, this value must correspond to the content of element <docTitle> of the document.

– [http://www.authority.org]/akn/kn/act/2007-01-01/1/schedule1Kenya, schedule 1 of act 1 from 2007 (WorkComponent)

Query syntax

6.8.3 The IRI for Work-level portion queriesFor querying a portion of a document at Work-level, we use a query language composed by the tilde symbol “~” following the fragment name (e.g., art_13). This syntax permits the server to manage the fragment information and so to detect the best manifestation (or all the manifestations) available AND to extract the portion requested:

[http://www.authority.org]/akn/sl/act/2004-02-13/2~art_3

6.9 The IRI of an Expression

6.9.1 The IRI for the Expression as a WholeThe IRI for the Expression as a whole consists of the following pieces:

The IRI of the corresponding Work The character “/” The human language code in which the Expression is drafted (a three-letter code according to

ISO 639-2 alpha-3). For an Akoma Ntoso XML representation, this value must correspond to the


content of the first element <FRBRlanguage> in the metadata section. According with ISO 639-2 alpha-3 “mul” means multilingual document (text with different languages), “und” means undetermined language

The “@” character (required) Zero or more comma-separated version identifiers as follows:

– If an approved act, the version date of the Expression in syntax YYYY-MM-DD. For an Akoma Ntoso XML representation, this value must correspond to the content of element <FRBRdate> in the <FRBRExpression> section of the metadata. If appropriate, the date can be integrated with a time using values for the XSD:dataTime datatype: Thh:mm:ss±hh:mm. The difference between the local time and Coordinated Universal Time (UTC) is specified using the sign + or - followed by the difference from UTC represented as hh:mm (note: the minutes part is required). See ISO 8601 Date and Time Formats and XML Schema Part 2: Datatypes (http://www.w3.org/TR/xmlschema-2/).

– If a bill, the presentation date is appropriate, or the stage in the approval process that the current draft is the result of.

– If an official version number exists, the version number preceded by "ver_"…. For an Akoma Ntoso XML representation, this value must correspond to the content of element <FRBRversionNumber>

The “!” character (required only if an optional part is added) Any content authoring information to determine the authoritativeness of the text content. This is

separate and independent of the authoring information relative to the metadata and markup, which are among the features of the Manifestation (optional). For an Akoma Ntoso XML representation, these values must correspond to the content of elements in the <FRBRExpression> section of the metadata.

Any content-specification date (as opposed to validity dates) (optional).

The absence of the version identifiers signals two different situations depending on the type of document: If the document is not versioned (e.g., the debate record of an assembly) then version identifier

need not and cannot be present. If the document is versioned (e.g., an act in force), then the lack of version identifiers refers to the

version in force at the moment of the resolution of the IRI.The original version of an Expression is referred to with an IRI with a dangling "@" character (which implies that the actual version date is the first appropriate date for that Work).

[http://www.authority.org]/akn/dz/debaterecord/2004-12-21/fraAlgerian parliamentary debate record, 21st December 2004., French version

[http://www.authority.org]/akn/sl/act/2004-02-13/2/engSierra Leone enacted Legislation. Act number 2 of 2004. English version, current version (as accessed today [according to the reader])

[http://www.authority.org]/akn/sl/act/2004-02-13/2/eng@Sierra Leone enacted Legislation. Act number 2 of 2004. English version, original version

[http://www.authority.org]/akn/sl/act/2004-02-13/2/eng@2004-07-21Sierra Leone enacted Legislation. Act number 2 of 2004. English version, as amended on July 2004

[http://www.authority.org]/ /akn/uy/bill/ejecutivo/carpeta/2005-04-04/137-2005/esp@2005-05-02T13:30:00-03:00/bill/Uruguay bill. Number 137-2005, at 2005-04-04. Spanish version, as amended on May 2nd, 2005, at 10.30 Montevideo time.

[http://www.authority.org]/akn/ng/bill/2003-05-14/19/eng@firstNamibia Bill number 19 of 2003, first stage, English version


[http://www.authority.org]/akn/mg/act/2003-03-12/3/mulMadagascar. Act 3 from 2003 in French and Malagasy. This means having a document with multilingual text.

[http://www.auth.org]/sl/act/2004-02-13/2/eng@2004-07-21!official/2004-07-25Sierra Leone enacted Legislation. Act number 2 of 2004. English version, as amended on July 2004. Official version generated on 25 July 2004.

[http://www.authority.org]/akn//eu/bill/directive/cnl/2013/eng@ver_secondProposal for an European directive of the Council – English variant, second version. .

6.9.2 The IRIs for ExpressionComponentsSome expressions have many components; some are only composed of a main document. In order to explicitly refer to individual components, it is therefore necessary to introduce a naming convention that identifies individual components, and still allows an easy connection between the component and the Expression it belongs to.There are therefore two subcases following explained.

6.9.2.1 The Expression is Only Composed of One ComponentIn this case, the IRI for the Expression as a whole and for its main component are identical plus the name “main”.

6.9.2.2 The Expression is Composed of Many ComponentsIn this case, the IRI for each ExpressionComponent consists of the following pieces:

The IRI of the corresponding Expression as a whole The character “/” Either:

– 1. A unique name for the attachment– 2. The name “main” which is reserved for the main document. It we have different main they

are numbered sequentially: main1, main2, etc.Some examples:

– [http://www.authority.org]/akn/dz/minutes/2004-12-21/fra/mainAlgerian parliamentary debate record, 21st December 2004., French version, main document

– [http://www.authority.org]/akn/sl/act/2004-02-13/2/eng/mainMain body of the Sierra Leone enacted Legislation. Act number 2 of 2004. English version, current version (as accessed today)

– [http://www.authority.org]/akn/sl/act/2004-02-13/2/eng@2004-07-21/main/schedule1Attachment “schedule01” of Sierra Leone enacted Legislation. Act number 2 of 2004. English version, as amended on July 2004

– [http://www.authority.org]/akn/ng/bill/2003-05-14/19/eng@first/main/schedule3Third attachment of Namibia Bill number 19 of 2003, first stage, English version.

6.9.3 Hierarchies of Components in ExpressionComponentsIn case of schedule, annexes, extracts we have the following rules:

If the attachment does not have further attachments, its IRI is provided as detailed in the previous section, without further addenda.

If the attachment has further attachments, the IRI, as detailed in the previous section, refers to the whole attachment, including its own attachments.

To refer to the main document of an attachment that has further attachments, a further “/main” part should be added.


To refer to any further attachment of an attachment, a further “/” followed by a unique name for the attachment must be added to the attachment itself.

Some examples:– [http://www.authority.org]/akn/sl/act/2004-02-13/2/eng@2004-07-21/main/schedule1

Whole attachment “schedule01” of the Sierra Leone enacted Legislation. Act number 2 of 2004. English version, English version, as amended on July 2004.

– [http://www.authority.org]/akn/sl/act/2004-02-13/2/eng@2004-07-21/main/schedule1/mainMain document of the attachment “schedule01” of Sierra Leone enacted Legislation. Act number 2 of 2004. English version, as amended on July 2004.

– [http://www.authority.org]/akn/sl/act/2004-02-13/2/eng@2004-07-21/main/schedule1/tableAAttachment “Table A” of the attachment “schedule01” of Sierra Leone enacted Legislation. Act number 2 of 2004. English version, as amended on July 2004.

– [http://www.authority.org]/akn/sl/act/2004-02-13/2/eng@2004-07-21/main/schedule1/attachment1/mainMain document of the attachment “attachment01” of the attachment “schedule01” of Sierra Leone enacted Legislation. Act number 2 of 2004. English version, amended on July 2004.

– [http://www.authority.org]/akn/eu/debate/2004-02-13/2/mul@/mainMain document of the European parliament debate report with multiple languages embedded.

– [http://www.authority.org]/akn//eu/bill/directive/cnl/2013/eng@ver_second/annex_1Annex 1 of the proposal for a Council directive, in the second version.

6.9.4 The IRIs for Virtual ExpressionsIn some situations, the information such as the actual enter-in-force date of the Expression or the language is not known in advance, and it is necessary to create references or mentions of documents whose IRI is now known completely (possibly, because their exact delivery date is not known yet). These are called virtual expressions (i.e., references to expressions that probably do not exist yet or ever, but can be unambiguously deduced once all relevant information is made available.)There are at least three cases where such a situation may arise:1. The information is not known by the author of the Expression (e.g., the legislator), in which case the

act of actually retrieving the correct information is in itself an act of interpretation.2. The information is not known by the editor of the Expression (e.g., the publisher of the XML version of

the document), in which case the information can theoretically be available, but is too much of a burden for the publisher to retrieve it.

3. The information is not known by the query system.

In these cases, the syntax for the IRI of the virtual Expression uses a similar syntax to the specification of the actual Expression, but the character “:” is used before each unknown value and instead of the “@” at the end of the specification of the Work-level IRI. For instance, if we need to reference the Expression of an act in force on date “1/1/2007”, we will probably need to refer to some Expression whose enter in force date was in a previous date to 1/1/2007.

– [http://www.authority.org]/akn/sl/act/2004-02-13/2/eng:2004-07-21Sierra Leone enacted Legislation. Act number 2 of 2004. English version, as amended on the closest date before July 21, 2004

– [http://www.authority.org]/akn/eu/act/2004-11-13/87/und:2015-01-10European Directive number 2004/87/EC of 2004. All the language versions, as amended on the closest date before January 10, 2015


Similarly, if we need to refer dynamically to the expressions in German of a specific act, we need to make a virtual reference whose date is left unspecified, and the language is forced to be German, as follows (deu is SO 639-2 alpha-3 code for German).

– [http://www.authority.org]/akn/ch/act/2009-05-09/432/:deuSwiss enacted Legislation. Act number 432 of 2009. Dynamic reference to any of the German versions.

6.9.5 The IRI for Expression-level portion queries For querying a portion of a document at Expression-level, we use a query language composed by the tilde symbol “~” following the fragment name (e.g., art_13) after the Expression fragment. This syntax permits the server to manage the fragment information and so to detect the best manifestation (or all the manifestations) available AND to extract the portion requested:

[http://www.authority.org]/akn/sl/act/2004-02-13/2/eng@2004-07-21~art_3

6.10 The IRI of a ManifestationCharacterizing the Manifestation is the specific process that generated an electronic document in some specific format(s). This includes specifications of the data format(s) used. Therefore, different manifestations of the same Expression generated using different data formats correspond to different manifestations and will have different IRIs.Manifestations are organized in components (the ManifestationComponents), and therefore we must identify separately the Manifestation as a whole and the individual IRIs for each ManifestationComponent. All of them are all immediately derived from the baseline, which is the IRI for the Expression.

6.10.1 The IRI for the Manifestation as a WholeThe IRI for the Manifestation as a whole consists of the following pieces:

The IRI of the corresponding Expression as a whole The character “!” (only required if any of the optional parts is added) The markup authoring information (useful to determine the authoritativeness of the markup and

metadata) (optional). For an Akoma Ntoso XML representation, this value must correspond to the content of element <FRBRauthor> in the <FRBRManifestation> section of the metadata.

Any relevant markup-specific date (optional). For an Akoma Ntoso XML representation, this value must correspond to the content of element <FRBRdate> in the <FRBRManifestation> section of the metadata.

Any additional markup-related annotation (e.g., the existence of multiple versions or of annotations.) (optional)

The character “.” (required) A unique three letter acronym of the data format in which the Manifestation is drafted. The

acronym can be “pdf” for PDF, “doc” for MS Word, or “xml” for the XML Manifestation, or “akn” for the package of all documents including XML version of the main document(s) according to the Akoma Ntoso rules (required). For an Akoma Ntoso XML representation, this value must correspond to the content of element <FRBRformat> in the <FRBRManifestation> section of the metadata.

Some examples:– [http://www.authority.org]/akn/dz/debaterecord/2004-12-21/fra/main.doc

Word version of the Algerian parliamentary debate record, 21st December 2004., French version

– [http://www.authority.org]/akn/sl/act/2004-02-13/2/eng/main.pdfPDF version of the Sierra Leone enacted Legislation. Act number 2 of 2004. English version, current version (as accessed today)


– [http://www.authority.org]/akn/sl/act/2004-02-13/2/eng@2004-07-21/main.aknPackage of all documents including XML versions of the Sierra Leone enacted Legislation. Act number 2 of 2004. English version, as amended in July 2004

– [http://www.authority.org]/akn/sl/act/2004-02-13/2/eng@2004-07-21!CIRSFID/2011-07-15/main.aknPackage of all documents including XML versions of the Sierra Leone enacted Legislation. Act number 2 of 2004. English version, as amended in July 2004. Rendered in Akoma Ntoso by CIRSFID on 15 July 2011.

6.10.2 The IRI for Manifestation-level portion namingThe syntax for naming a portion at the Manifestation level is the following:

/akn/us/act/123/en@2014-05-15~sect_13.xmlIn the case of the US Code, the chapter 3 portion of Title 9 is specified as:

/akn/us/usc/title_9/eng@2013-07-26~chp_3/main.akn

6.10.3 The IRIs for ManifestationComponentsIRI for each ManifestationComponent consists of the following pieces:

1. The IRI of the corresponding Expression as a whole2. The character “!” (only required if any of the optional parts is added)3. The markup authoring information to determine the authoritativeness of the markup and metadata

(optional)4. Any relevant markup-specific date (optional)5. Any additional markup-related annotation (e.g., the existence of multiple versions or of

annotations) (optional)6. The character “/”7. Some unique identification of the ManifestationComponent with respect either to the

Manifestation as a whole or to the ExpressionComponent the component is the Manifestation of.8. The character “.“9. A unique extension of the data format in which the Manifestation is drafted. The acronym can be

“pdf” for PDF, “doc” for MS Word, “xml” for XML documents, “tif” for image formats, etc.In the next section we will examine the format of the package and the relevant IRIs for a specific Manifestation of Akoma Ntoso documents, the XML format.

6.10.4 The IRIs for the Components in the Akoma Ntoso Package Manifestation

The Akoma Ntoso package Manifestation is a very specific Manifestation using a number of data formats (mainly XML but could include other multimedia formats as needed) with a very specific organization of parts and components. Since it makes explicit choices in terms of data formats and reciprocal references, it is important to provide clear and non-ambiguous rules as to the internal naming mechanism and its overall structure. An Akoma Ntoso package Manifestation is a package composed of one or more files organized in a flat fashion. The transportable format is a ZIP file whose extension is “.akn”. Other formats are possible and acceptable as long as they adhere to these rules.The following are alternative options for the Akoma Ntoso package:

10. If the document is just composed of text and does not refer to any multimedia fragment of any form, then the ZIP package contains a single document called “main.xml”.

11. If the document is composed of many ManifestationComponents but does not refer to any multimedia fragment of any form, then the zip package is composed of many XML files, one for each ExpressionComponent. Each ManifestationComponent is then called as its corresponding ExpressionComponent, plus the “.xml” extension. The name “main” is reserved for the main


mailto:/akn/us/act/123/en@2014-05-15~sect_13.xml

component. Numbers are never used except when they are already part of the ExpressionComponent’s name.

12. If the document contains multimedia fragments of any kind, then each individual fragment does not have a corresponding ExpressionComponent, but is just a ManifestationComponent referred to in the <img> or <object> element. All multimedia components must be stored within an inner structure (e.g., a folder) called “media”. Multimedia components can be called freely, but must use the appropriate extension to refer to their content type. Thus a logo can be called “logo.tif” or any other name, as long as the extension is correctly specifying the content type.

Reciprocal references to ManifestationComponents are necessary within a specific Manifestation. For instance, the Manifestation of the main document refers to the manifestations of its attachments via the <attachment> elements, and the schedule showing an image refers to the file of the image via the <img> element. In these cases, all references MUST be relative to the package (i.e., the Manifestation as a whole):

attachment1.xmlManifestation of the first attachment of the current document

schedule3.xmlManifestation of the third attachment of the current document

media/logo.tifManifestation of an image within the current document

References to ManifestationComponents are rarely, if ever, needed outside of the Manifestation themselves. But if needed, they will refer to the file as follows:

1. The IRI of the corresponding Expression as a whole2. The character “/”3. The relative reference to the required ManifestationComponent as specified above.

6.11 The IRI of an ItemAkoma Ntoso makes no assumption on the physical storage mechanism employed to record actual manifestations. As such, there is NO rule for IRIs of the items.


7 ConformanceThe last numbered section in the specification must be the Conformance section. Conformance Statements/Clauses go here. [Remove # marker]


8 Bibliography

http://eur-lex.europa.eu/content/pdf/techleg/joint-practical-guide-2013-en.pdfhttp://www.bournemouth.ac.uk/library/how-to/citing-refs-law.html


http://www.bournemouth.ac.uk/library/how-to/citing-refs-law.html

http://eur-lex.europa.eu/content/pdf/techleg/joint-practical-guide-2013-en.pdf

Appendix A. AcknowledgmentsThe following individuals have participated in the creation of this specification and are gratefully acknowledged:Participants:

[Participant Name, Affiliation | Individual Member][Participant Name, Affiliation | Individual Member]


Appendix B. Example TitleB.1 ELI Metadata

Properties Definitions

is_part_of

A related resource in which the described resource is physically or logically included (definition from Dublin Core). Cover the case of legal resources included in an Official Journal and the case of legal resources grouping other legal resources across time.

has_part Inverse of "is_part_of"

is_realized_byRelates a legal resource to a legal expression of this resource in the form of a "sequence of signs" (typically alpha-numeric characters in a legal context). (definition adapted from RDA). Inverse of "realizes".

realizes Relates a legal expression to the legal resource realised through that expression. (definition adapted from RDA). Inverse of "is_realized_by".

is_embodied_by Relates a legal expression to a physical format of that expression (definition adapted from RDA). Inverse of "embodies".

embodies Relates a physical format to the legal expression embodied in that format (definition adapted from RDA). Inverse of "is_embodied_by".

uri_schemaSchema describing the URI of an ELI instance. ELI uses URI template specifications (IETF RFC 6570). Schemes should be associated with member states and will be published in a registry.

id_local The unique identifier used in a local reference system to maintain backwards compatibility. Examples include CELEX at EU level, or the NOR in France

type_document

The type of a legal resource (e.g. "Directive", "Règlement grand ducal", "law", "règlement ministeriel", "draft proposition", "Parliamentary act", etc.).

Member states are encouraged to make their own list of values in the corresponding concept scheme. EU Publications Office provides a list of values for EU resource types at http://publications.europa.eu/mdr/authority/resource-type


relevant_for

Refers to a place or an area associated with the resource. This covers the notions of jurisdiction, sovereignty, applicability or administrative area. The place identifier should be based on ISO3166-2. See: https://www.iso.org/obp/ui/#search.

Member states are encouraged to make their own list of values in the corresponding concept scheme. EU Publications Office provides a list of places at http://publications.europa.eu/mdr/authority/place

The group notes the limitations of what can be said with a single property; member states can refine this notion by declaring specific sub properties.

passed_by

The authority that originally passed or made the law. The relationship between current and any former law making body should be represented in the concept scheme.

Member states are encouraged to make their own list of Agents. EU Publications Office provides a list of corporate bodies at http://publications.europa.eu/mdr/authority/corporate-body.

responsibility_of The individual, organisational unit or organisation, that has some kind of responsibility for the legislation.

is_aboutA subject for this legal resource. The use of Eurovoc (http://eurovoc.europa.eu) is encouraged to select values for this property. Member states are encouraged to align local values to Eurovoc.

date_document Date of adoption or signature (of the form yyyy-mm-dd)

date_publication

Date of publication of the official version of the legislation, in hard copy or online, depending on what the official publication is, and when it was published. Publication dates at the level on legal expressions can be separately asserted, using standard Dublin Core properties.

in_force

A value indicating whether a legal resource or a legal expression is currently in force, not in force, partially in force, etc.

Member states are encouraged to make their own list of values in the corresponding concept scheme.

first_date_entry_in_force The first date any part of the legal resource or legal expression came into force (can be seen as the start date of a dc:valid range for this resource)

date_no_longer_in_force If the date is known, it is when the legal resource or legal expression is no longer in force (can be seen as the end date of a dc:valid range for this resource)

related_to Indicates a somehow related other document, not necessarily a legal resource. Note that citation links should use the cites property.

changes

Legal resource changing (amending or replacing) another legal resource This may be a direct change (textual or non-textual amendment) or a consequential or indirect change. Note, the property is to be used to express the existence of a change relationship between two acts rather than the existence of a consolidated version of the text that shows the result of the change. For consolidation relationships, use the "consolidates" and "consolidated_by" properties.


changed_by Inverse of "changes"

basis_for Legal resource (typically constitution, treaty or enabling act) that empowers the creation of another legal resource (secondary legislation)

based_on inverse of "basis_for"

citesCitation in the text of the legislation. This may be at the legal resource or legal expression level, as required by the implementation context. This includes verbatim citation and citations in referrals.

cited_by Inverse of "cites"

consolidates

Link between a consolidated version, which is the product of an editorial process that revises the legislation to include changes made by other acts, and the original or previous consolidated version and the legislation making the change.

consolidated_by Inverse of "consolidates" coordination codification

transposes

To be used for precise statements of transposition, at act or article level, from the original version of a national implementing measure to the legal resource Directive as published in the EU Official Journal. Can be used for transposition tables, once OPEU has introduced ELI support down to the article level.

Note that this should point to the legal resource of the Directive itself, not to one of its language-specific legal expression.

transposed_by

Inverse of "transposes".

Note that this property is expressed on a legal resource, not on one of its language-specific legal expression.

implements

To be used for more general statements about the relationship between domestic and EU legislation, e.g. between consolidated versions of national implementing measures and consolidated versions of Directives.

Note that this should point to the legal resource of the Directive itself, not to one of its language-specific legal expression.

implemented_by

Inverse of "implements".

Note that this property is expressed on a legal resource, not on one of its language-specific legal expression.

language

The language of an expression.

EU Publications Office provides a list of languages at http://publications.europa.eu/mdr/authority/language. This list is large enough so that member states should not have to declare local values.

Note that, if needed, a language can also be stated on a legal resource using the Dublin Core "language" property.


title

The title, or name, of an expression.

Note that, if needed, a title can also be stated on a legal resource using the Dublin Core "title" property.

title_short Established short title of the expression (if any)

title_alternative

An alternative title of the expression (if any).

Note that, if needed, an alternative title can also be stated on a legal resource using the Dublin Core "alternative" property.

published_in

Reference to the Official Journal or other publication in which the legal resource is published, identified by a suitable mechanism. Preferably to be expressed as a URI to a given resource, in the absence of such a URI as a descriptive string.

publishesInverse of "published_in". Note this property does not link a publisher with a resource, but rather a specific Format of a resource with a specific Format of another resource, indicating that the subject Format publishes the object Format.

description An account of the resource (definition from Dublin Core), e.g. a summary.

is_exemplified_byLink to a concrete file URL.Relates a format to a single exemplar or instance of that format (definition adapted from RDA).

publisher An entity responsible for making the resource available (definition from Dublin Core)

format

The file format, physical medium, or dimensions of the resource (definition from Dublin Core).Possible URIs values should be taken from http://www.iana.org/assignments/media-types (e.g. http://www.iana.org/assignments/media-types/application/xml), and can serve as a basis for content negotiation for the server to return the appropriate file based on the client preference.

versionA version status for the resource. Member states are encouraged to make their own list of values in the Version concept scheme. Example of such values can be "Official Journal", "made", "consolidated", "proposed", "prospective", etc.

version_date A date associated with the version.

rights Information about rights held in and over the resource (definition from Dublin Core)

rightsholder A person or organization owning or managing rights over the resource (definition from Dublin Core)

licence A legal document giving official permission to do something with the resource legislation-reqs-v1.0-wd044 Working Draft 04 17 June 2015Standards Track Draft Copyright © OASIS Open 2015. All Rights Reserved. of 72

(Definition from Dublin Core)legal_value The legal value associated with a specific format of a resource. A set of values

is defined by ELI in the corresponding concept scheme. These values are : - unofficial : no particular or special standing; - official : published by an organisation with the public task of making the information available (e.g. a consolidated version of a EU directive) ; - authoritative : the publisher gives some special status to the publication (e.g. "the Queens Printer" version of an Act of Parliament, or the OJ version of a EU Directive); - definitive : the text is conclusively what the law says, (e.g. the digitally signed version of an OJ).

Member states can extend this list with local values if needed.

Annexed_of

AnnexOf

components


Components_of

B.2 Akoma Ntoso MetadataText

B.3 Zotero Metadata


Appendix C. Revision HistoryRevision Date Editor Changes Made

[01] [Rev Date] [Monica Palmirani] [Integration of all the material]

[02] [Rev Date] [Melanie Knapp] [Inclusion of some parts: France case and Luxembourg]

[03] [Rev Date] [John Dann] [Inclusion of Publications Office use case, corrections]

[04] [Rev Date] [Veonique ParisseMonica Palmirani]

[Inclusions of several parts]
