ELI - European Legislation Identifier
Passed by the Sectoral Commission for e-government 24/02/2022
The European area of freedom, security and justice requires the knowledge of European law, but also mutual knowledge of the legal systems of other Member States. For this reason, in the year 2012, the European Union adopted an interoperability initiative specifically focused on legislative information by means of the Council Conclusions (2012/C 325/02) inviting Member States to adopt a standard for the identification and description of legislative rules called the "European Legislation Identifier".
Although there is much legal information available on the Internet, the accessibility and interoperability are limited by the differences in the national legal systems as well as by the existing differences in the technical systems used to store and present the legislation in the national websites.
In this context, the European Legislation Identifier (ELI) aims to facilitate the access, exchange and interconnection of the information published in the European, national and global information systems, in order to enable the setting of a genuine network of legal information, available as open data and reusable.
The European Legislative Identifier is used for:
The advantages of the ELI system are multiple:
The ELI's system is structured in three cornerstones:
ELI offers a way to univocally identify, name and access national and European legislation, readable both by people and computer systems and compatible with current technological standards.
While a structured URI can already identify acts using a set of defined components, the attribution of additional 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, Member States will be able to reuse relevant information processed by others for their own needs, without having to put into place additional information systems.
An ontology represents a formal description of a set of concepts and the relations in a given domain. By describing the properties of legislation and the relations between the different concepts, a shared understanding is made possible so ambiguities between terms can be avoided. Being a formal specification, it is directly machine-processable.
Therefore, while Member States are free to use their own metadata schema, they are encouraged to follow and use ELI metadata standards with shared but extensible authority tables, which permit to meet specific requirements. ELI metadata schema is intended to be used in combination with customized metadata schemas.
ELI allows a wider and faster data exchange: when the metadata are integrated in the corresponding webpages of the different official gazette or legal information systems, the information can be exchanged efficiently and automatically thanks to the benefits of the emerging semantic network architecture, that makes it possible for the information to be processed directly both by computers and by people.
For the data exchange to become more efficient, ELI metadata elements may be classified in compliance with the W3C Recommendation "RDFa in XHTML: Syntax and Processing'. Member States may add other classification formats apart from RDFa.
Since 2012, ELI system has been adopted by a series of European countries (Austria, Belgium, Denmark, Finland, France, Ireland, Italy, Luxembourg, Norway, Portugal, United Kingdom) and by the Publications Office of the EU, with different intensity according to the progressive approach that characterizes this identifier (only pillar 1, pillars 1 and 2 or the three pillars).
The system's success has motivated that on 6 November 2017, the Council have adopted new Conclusions about ELI[1], encouraging again the Member States and candidate states, the Lugano States and other states to adopt the identifier voluntarily and gradually.
The Spanish legal system is a complex and plural reality. It is integrated by rules corresponding to three different territorial levels (state, autonomic and local). However, despite the fact that these rules constitute a system and that they are related to each other, there are differences in the technical systems used to store and present legislation in each legal information system. This makes access to law more difficult for legal practitioners, companies and citizens and hampers the connection among legal information systems.
In fact, if a person wants to know the legislation about any matter in Spain, it is not enough to check the state or regional regulations, but it is needed to check both and, in many cases, also the European or local regulations. However, the search of legal information corresponding to different territorial levels is costly and difficult, to the extent that the State, the Autonomous Communities and the local entities databases in which the most relevant legal information is located, are not related to each other. It requires to look up several databases or, at worst, if one is interested in the different regional or local legislations, to make searches through every one of them.
Therefore, the ELI implementation in Spain is especially relevant, since, in addition to the benefits that ELI provides at the European level, there would be, internally, a significant improvement in the access to legal information and in the interoperability between the legal information systems of the different territorial levels.
ELI is a flexible system, designed to adapt to the complexity and specificity of the different regional, national and European legal systems, as well as the changes that occur in legal resources.
In the Spanish case, the implementation must take into account the plurality and diversity that characterizes the Spanish legal system, much higher than the one presented by the European countries that up to now have implemented the identifier:
Each of the territorial level with legislative and regulatory powers has its own Official Gazette:
All the official gazettes are electronically published with digital signature, as a guarantee of its authenticity and integrity; the documents published are offered in a plurality of formats (mostly pdf and html and occasionally xml and e-pub). Many Official Gazettes publish each rule as a single electronic document; others offer a pdf with the complete issue of the day, with all the rules and acts published.
As for the language, each Official Gazette is published in its corresponding official language: only in Spanish or in two languages in the case of those public administrations that have their own language[2].
Regarding the State Official Gazette (Boletín Oficial del Estado / BOE), it is published in Spanish, although, in accordance to the Royal Decree 489/1997[3], there are four supplements in co-official languages in compliance with the agreements signed with the Autonomous Communities of the Basque Country, Catalonia, Galicia and Valencia.
Some rules are officially published in two gazettes:
ELI applies to legal resources available in the official databases of Member States.
The State, the Autonomous Communities and the local bodies have their own legal information systems. Usually, these database systems are available in the website in which the corresponding official gazette is hosted and allow to retrieve the published legislation, although sometimes the time scope considered is not complete. The information is offered in pdf and html format and less frequently in xml.
It is relatively common for official databases to offer legislation corresponding to other territorial levels, even if they have not been published in the official gazette that corresponds to the managing entity (for example, autonomic databases that also offer certain state legislation).
The consolidated law databases[6] offered mainly by the State and some Autonomous Communities reuqiers a special comment, as their management is quite different:
The situation of the databases of the Official Gazettes of the Provinces, which are dependent on the Provincial Councils, is very different and sometimes it is the corresponding local body itself, that depending on its technical resources, is in charge of the online publishing of their own regulations, being rare that they offer them in a consolidated version.
The technological situation of the diverse official bodies that offer legal resources on line is very varied. Due to this, the metadata range in the different websites is unequal: not all the administrations have metadata and, if they exist, they are not uniform, either because they do not match, because they are not named equal or because they are not defined in the same way.
The ELI system offers a flexible standard for the access to and identification of legislation, which has to be adapted to the particularities of the different regional, national and international legislative systems.
Due to the plurality of the Spanish legal system, the implementation of the identifier must be carried out in a coordinated way by all public administrations, following the philosophy defined by the "National Interoperability Scheme", which takes into account the European Union recommendations.
Thus, the public administrations have taken part in the development of the technical specification within the framework of the Sectoral Commission for e-government (Comisión Sectorial de Administración Electrónica / CSAE).
According to the gradual approach that defines ELI and that has been followed by all the European countries, the implementation in Spain will take place in various phases.
In the first phase, the ELI specification was defined for the state and autonomic legislation, by the agreement of the CSAE of 13 March 2018.
The complexity of the local legislation and the different technological situations regarding the provincial official gazettes and public bodies recommended approaching the application of the identifier to the local legislation in a second phase.
Consequently, a new version of the technical specification tackling the application of ELI to all legislation, either state, autonomic or local, has been developed. A specific addendum has been included in the text approved by the CSAE in 2018, which adapts to the legal and technical particularities of the local field.
This specification aims to establish the common guidelines required by the implementation of ELI in the Spanish context, so that the identification and description of the legal resources are performed in a coordinated and coherent way by the different public administrations.
As ELI is designed to work on the basis of existing systems, each public administration can maintain its own official gazette and legislative databases as appropriate, as well as the internal management processes that meet their needs, criteria and own regulations. The specifications include only the minimum elements necessary to guarantee the interoperability of the legal information that the different Spanish public administrations offer on the Internet.
This technical specification, applicable to all national legislation, defines:
In any case, the guidelines for this technical specification have been designed in such a way that allow its development and improvement over time, through the expansion of the minimum common metadata, and its adaptation to the evolution of the ELI ontology, until the adoption of the three pillars is completed.
According to the Council conclusions of 6 November 2017, all the public administrations (state, regional or local) which apply or which are planning to adopt the identifier, must have available a webpage containing all the information about the project.
In compliance with this, since July 2018, the ELI Working Group of CSAE maintains the common webpage https://www.elidata.es/. It also offers technical resources for the identifier's application, as well as the link to the respective webpages of the different public administrations with the information about their implementation. The availability and sharing of all this information eases the coordination at the national level and provides the knowledge about previous experiences of implementation developed by other entities.
The Council Conclusions invite Member States to apply the ELI to national legislation units, giving them space to decide to which rules the identifier will apply and to do it progressively[7].
However, according to the literal meaning of the term "units of national legislation", the following legal resources will not be taken into consideration:
The State and the Autonomous Communities will apply ELI to those rules and resolutions that belong to their corresponding legislative databases[10]. With regard to international agreements, they will be identified through ELI, since once published in the State Official Gazette[11], they become part of the domestic legal system, as established in the article 96 of the Spanish Constitution, becoming, therefore, "units of national legislation".
In the case of local regulations, the application will be carried out in the terms defined in section 11.3.a) of the specification.
Although he benefits from ELI are greater the broader is the set of norms considered, it is required to focus t on that legislation most queried by citizens.
Since most of the legislation in force has been issued after the Constitution and the firsts Autonomy Statutes were approved in 1979, ELI will be applied, at least, to state and autonomic legislation published since 29/12/1978.
In the same way, as some important legislation prior to 1978 is still in force, at the state level ELI will also be applied to all legislation published before 29/12/1978 and having a consolidated version. To the extent that it is a minimum application temporary scope, both the State and the Autonomous Communities can widen it, according to their possibilities and needs.
The local entities, as stated by section 11.3b), can define the temporary scope of the rules to which ELI is applied based on their possibilities.
The ELI ontology defines a core model for describing legal resources, aimed at supporting the link with other legal resources, along with their publication and reuse.
ELI itself builds on the well-established model for "Functional requirements for bibliographic records' (FRBRoo), aligned with other current standardization initiatives in the field. FRBRoo distinguishes between the concepts of "work" (distinct intellectual or artistic creation), "expression" (the intellectual or artistic realization of a work) and the "manifestation" (the physical embodiment of an expression).
In the specific case of ELI, the following concepts can be identified:
The picture embedded below includes these three concepts, applying them to a specific resource, in this case the Council Conclusions inviting to the introduction of the ELI.
The organization of the information in multiple conceptual levels, following the FRBRoo structure allows users to:
ELI ontology accommodates different points of view of what should be considered a new legal resource, or a new legal expression of the same resource[14].
This flexibility is particularly useful in a legislative context such as the Spanish one, which is structured in several territorial levels, each of them with its corresponding official gazette, in which certain rules are subject to double publication and in which the publication can be done in several languages.
Therefore, in the implementation of ELI in Spain, two levels of legal resources will be taken into consideration for each piece of legislation:
Consequently, there must be configured always for each piece of legislation, at least, two legal resources (eli:LegalResource):
In addition, those public administrations that offer an updated text of the rule, should also configure a consolidated legal resource. In case the administration also offers the previous texts that the rule has presented, it will be necessary to configure each of these intermediate wordings as a different legal resource.
Along with this, those public administrations that have a corrected version[15] of the rules, independently from the consolidated version, should treat this corrected version as a different legal resource.
All legal resources derived from the same rule are linked with two specific properties of the ELI ontology:
In turn, the initial legal resource and the consolidated legal resources are linked with the properties eli:consolidates (to link a consolidated legal resource with the initial legal resource that it consolidates) and eli:consolidated_by (to link an initial legal resource with the consolidated legal resource corresponding to its successive versions).
Each of the legal resources would have its corresponding expression or expressions, whether published in one language or in several[18].
The legal resource and its expressions are linked through the properties of the ontology eli:realizes and its inverse eli:is_realized_by.
Finally, the expression and formats in which is offered are linked with the properties eli:embodies and eli:is_embodied_by.
Content not available in English
The structure of legal resources and its links can be consulted in detail in the examples included in the URI cases of the technical information.
The State and the Autonomous Communities must configure always an abstract legal resource. The local entities can establish an easier conceptual model, in the event that they only offer one version of the rule (either the initial one or the consolidated one) in the terms described in section 11.4.
As mentioned in point 2.2, some autonomic and state rules are published in two official gazette.
In these cases, even it is the same rule, each of the publications must be treated as an independent abstract legal resource. So there is an abstract legal resource for the first publication and other abstract legal resource for the second publication.
Thus, in the case of the most usual re-publication example, which is that of the autonomic acts[19], once the publication is made in the autonomic official gazette, an abstract legal resource will be generated, with the metadata of the publication in the quoted official gazette. It will have associated the corresponding initial legal resource and successively, in its case, the consolidated legal resources as needed. Subsequently, once the autonomic law is published in the State Official Gazette (BOE), the State will have to create the abstract legal resource corresponding to said publication and the associated resources (initial and consolidated in its case).
The two abstract legal resources that are created, as well as their corresponding initial legal resources, will be linked through the properties of the ontology eli:is_another_publication_of and eli:has_another_publication.
An example of the double publication treatment can be consulted in the URI cases of the technical information.
According to the conceptual model presented, it is not necessary to have a single ELI domain, but the State, each Autonomous Community and each of the legal entities may create their own "ELI domains".
In order to facilitate the reuse of "ELI information", it is recommended that the URI ELI is built in the following way:
For example:
The State, each of the Autonomous Communities and local entities can establish their own and independent ELI domains.
ELI uses "HTTP URIs" to specifically identify all online legal information officially published across Europe.
These URIs are formally described by machine-readable URI templates (IETF RFC 6570), using components that carry semantics both from a legal and an end-user point of view.
Each Member State will build its own, self-describing URIs using, whenever it is possible, the described components as well as taking into account their specific language requirements. These components are[20]:
| Name eli | Comments | |
|---|---|---|
| Jurisdiction | Jurisdiction | Use of DCTERMS. ISO3166: 2 alpha country codes, e.g. ‘LU’ For international organizations, the registered domain name can be used: e.g. ‘EU’ or ‘WTO’ |
| Agent | Administrative hierarchical structure, e.g. federal States, constitutional court, parliament, etc. | |
| Subagent | Administrative hierarchical substructure, e.g. the responsible ministry | |
| Reference | Year | YYYY Various interpretations allowed depending on countries’ requirements, e.g. date of signature or date of publication, etc. |
| Month | MM | |
| Day | DD | |
| Type | Nature of the act (law, decree, draft bill, etc.) Various interpretations depending on countries’ requirements |
|
| Subtype | Subcategory of an act depending on countries’ requirements (e.g. corrigendum) | |
| Domain | Can be used if acts are classified by themes, e.g. codes | |
| Natural identifier | Reference or number to distinguish an act of same nature signed or published on the same day | |
| Subdivision | Level 1 | Reference to a subdivision of an act, e.g. Article 15 |
| Level 2 | Reference to a smaller subdivision than level 1, e.g. Article 15.2 | |
| Level 3 | Reference to a smaller subdivision than level 2 | |
| Level n | Reference to a smaller subdivision | |
| Point in time | Point in time | YYYYMMDD Version of the act as valid at a given date |
| Version | Version | To distinguish between original act or consolidated version |
| Language | Language | Language codes (International Organization for Standardization (ISO 639). |
| Format | A file format, like «pdf» or «html» | Note that the Council conclusions inviting the introduction of the European Legislation does not list this component explicitly, but it is always part of the URIs to identify the eli: format level. |
All the components are optional and can be selected based on national requirements and do not have a pre-defined order.
To enable the exchange of information, the chosen URI template must be documented using the URI template mechanism, as in the following example:
/eli/{jurisdiction}/{agent}/{sub-agent}/{year}/{month}/{day}/{type}/{natural identifier}/{level 1 ...}/{point in time}/{version}/{language}{format}
According to ELI ontology, each identifier must be split into at least three levels:
The countries are free to select and organize the components of the URI template in the most appropriate way to adapt their needs, however, they must take into account a series of recommendations:
Taking into account these recommendations and the specific legal and technical considerations of the Spanish regulatory system, the URI structure for state and autonomic rules will be the following:
/eli/{jurisdiction}/{type}/{year}/{month}/{day}/ {number}/{version}/{version_date}/{language}/{format}
| Name (ELI) | Description | Format | Values | Comments |
|---|---|---|---|---|
| Jurisdiction | Jurisdicción | Limited list of alphabetic values | List of controlled values | ISO 3166 alfa 2:
|
| Type | Tipo | Limited list of alphabetic values (1 to 4 letters) | List of controlled vocabulary | The types will be identified by acronyms with a variable length |
| Year | Año | Numeric values Format YYYY |
2001, 2002… | Date of signature (yyyy/mm/dd) |
| Month | Mes | Numeric values Formast MM |
01, 02… | |
| Day | Día | Numeric values Formart DD |
01, 02… | |
| Number (natural identifier) | Número | Numeric and, occasionally, alphanumeric values | In general, the number is the official number of the legal resource | |
| Version | Versión | Limited list of alphabetic values (3 letters) | List of controlled values | Identifies if the legal resource is the initial, the consolidated or the corrected one |
| Version_date (point in time) | It indicates the date of updating. | Numeric values: YYYYMMDD | For consolidated legal resources. | |
| Language | Langua | Limited list of alphabetic values | List of controlled values | ISO 639-3 (3 letters code), with adjustments for Valencian and bilingual documents. |
| Format | Formato | Limited list of values | html, pdf, epub, xml | The format values must be comply with the typologies established by IANA |
Until now, most of the countries that have implemented ELI and the EU itself, have not incorporated the jurisdiction element in ELI, since this information already appears in the Internet domain.
However, given that both state and autonomic official gazettes can publish their own territorial level legislation and that from other territorial levels, the domain is not enough to identify if the considered legislation is state or autonomic.
As a consequence, it is necessary to use the element eli:jurisdiction in the URI template, so that the territorial scope to which the considered legal resource corresponds is reflected. The ISO3166 alpha 2 standard will be used for this purpose.
| Code | Territorial Level |
|---|---|
| es | State |
| es-an | Autonomous Community of Andalucía |
| es-ar | Autonomous Community of Aragón |
| es-as | Autonomous Community of Principado de Asturias |
| es-cn | Autonomous Community of Canarias |
| es-cb | Autonomous Community of Cantabria |
| es-cl | Community of Castilla y León |
| es-cm | Autonomous Community of Castilla-La Mancha |
| es-ct | Autonomous Community of Cataluña |
| es-ex | Autonomous Community of Extremadura |
| es-ga | Autonomous Community of Galicia |
| es-ib | Autonomous Community of Illes Balears |
| es-ri | Autonomous Community of La Rioja |
| es-md | Community of Madrid |
| es-mc | Autonomous Community of Región de Murcia |
| es-nc | Community of Foral de Navarra |
| es-pv | Autonomous Community of País Vasco |
| es-vc | Comunitat Valenciana |
| es-ce | Ciudad Autónoma de Ceuta |
| es-ml | Ciudad Autónoma de Melilla |
ISO3166 alfa 2 standard
In the ELI scheme, the element eli:type_document (legal rank) must be collected in a controlled vocabulary table, according to the peculiarities of the national systems.
Most of Member States have chosen to publish their table of types with acronyms of variable length, except France, that maintains the complete denomination.
In the Spanish case, a limited list of values will be used, including both the ranks of state and autonomic legislation[22], identified by acronyms of variable length (1 to 4 letters).
Given the existing linguistic variants for the same category, the identification by acronyms has the advantage that the resource is always named in the same way.
The values for the controlled vocabulary table eli:type_document are as follows:
(Content not available in English)
| Español | Catalán | Euskera | Gallego | Valenciano | Siglas |
|---|---|---|---|---|---|
| Constitución | Constitució | Konstituzioa | Constitución | Constitució | c |
| Reforma (constitucional) | Reforma | Erreforma | Reforma | Reforma | ref |
| Acuerdos internacionales | Acord internacional | Nazioarteko akordio | Acordo internacional | Acord internacional | ai |
| Ley Orgánica | Llei orgànica | Lege Organikoa | Lei orgánica | Llei Orgànica | lo |
| Ley | Llei | Legea | Lei | Llei | l |
| Ley Foral | Foru Legea | lf | |||
| Real Decreto-ley | Reial decret llei | Errege Lege Dekretua | Real decreto Lei | Reial Decret llei | rdl |
| Real Decreto Legislativo | Reial decret legislatiu | Legegintzako Errege Dekretua | Real decreto Lexislativo | Reial Decret Legislatiu | rdlg |
| Decreto-ley | Decret llei | Lege Dekretua | Decreto Lei | Decret llei | dl |
| Decreto-ley Foral | Foru Lege Dekretua | dlf | |||
| Decreto-Legislativo | Decret Legislatiu | Legegintzako Dekretua | Decreto Legislativo | Decret Legislatiu | dlg |
| Decreto Foral Legislativo | Legengintzako Foru Dekretua | dflg | |||
| Reglamento | Reglament | Erregelamendua | Regulamento | Reglament | reg |
| Real Decreto | Reial decret | Errege Dekretua | Real Decreto | Reial Decret | rd |
| Decreto | Decret | Dekretua | Decreto | Decret | d |
| Decreto Foral | Foru Dekretua | df | |||
| Orden | Ordre | Agindua | Orde | Orde | o |
| Orden Foral | Foru Agindua | of | |||
| Acuerdo | Acord | Akordioa | Acordo | Acord | a |
| Resolución | Resolució | Ebazpena | Resolución | Resolució | res |
| Instrucción | Instrucció | Instrukzioa | Instrucción | Instrucció | ins |
| Circular | Circular | Zirkularra | Circular | Circular | cir |
| Otros | Altres | Beste batzuk | Outros | Atres | alia |
As the types used in the State and Autonomous Communities databases are equivalent, there should be no disagreement about the type that should be attributed to a resource published in two official gazettes or disseminated in different databases. However, it could happen that a rule does not fit in any of the typologies. For these cases, it is recommended to contrast the type attributed by the administration responsible for the first publication before generating the URI corresponding to the second publication.
In any case, there would be a residual type named "alia" and intended to collect those rules that do not exactly correspond to any of the specific types.
Regarding the corrections of errors, they will be considered a subtype[23]: the URI of the corrections will be formed with the standard structure of the ELI, adding subsequently the eli:number, the element corrigendum and the date of publication (eli:date_publication) of the correction of errors in the official gazette with format AAAAMMDD.
For example:
Real Decreto 20/2017, de 20 de enero, sobre los vehículos al final de su vida útil.
eli/es/rd/2017/01/20/20/
Corrección de errores del Real Decreto 20/2017, de 20 de enero, sobre los vehículos al final de su vida útil.
eli/es/rd/2017/01/20/20/corrigendum/20170327/dof/
Controlled vocabulary tables with acronyms of variable length (1 to 4 letters)
/eli/{jurisdiction/{type}/{year}/{month}/{day}/{number}/{subtype}/{date_publication}/{version}/{language}/{format}
The date considered to build the identifier for the state and autonomic legislation is always the date of the signature, not the date of publication.
The components are used independently {year} {month} {day}, which will allow, through truncation of the URI, the recovery of all the rules corresponding to the same year, month or day.
AAAA/MM/DD Format
This element reports the official number[26] that identifies each provision within its type or within its legal typology. The inclusion of this element in the template is due to two reasons:
However, in Spain not all the rules have an official number:
The year of adoption is always included (Law 5/2010, Decree 320/2016, Order PRE/7/2017,…) in the official number of Spanish rules. Since this year is already part of the template through the element date_document, it has been decided not to include it as a part of the element eli:number in the URI template.
In the case of higher rank rules, the sequential number will be used as natural_identifier, which allows the creation of a unique URI for each legal resource.
ANDALUCÍA:
LEY 9/2016, de 27 de diciembre, de Servicios Sociales de Andalucía.
eli/es-an/l/2016/12/27/9/
ESTADO:
REAL DECRETO-LEY 2/2017, de 27 de enero, por el que se adoptan medidas urgentes para paliar los daños causados por los últimos temporales.
eli/es/rdl/2017/01/27/2/
It should be pointed out that in certain cases of lower rank rules, the official number is composed by an alphanumeric code, prefixing the number with three identifying letters of the responsible department. In these cases, the complete alphanumeric code is considered as the number. However, to simplify the URI, the slash that separates the alphabetic and numeric element will be erased and only lowercase letters will be used.
CASTILLA Y LEÓN:
ORDEN EYH/ 671/2016, de 25 de julio, por la que se dictan las normas para la elaboración de los Presupuestos Generales de la Comunidad de Castilla y León para el año 2017.
eli/es-cl/o/2016/07/25/eyh671/
CATALUÑA:
ACUERDO GOV/16/2017, de 21 de febrero, por el que se aprueba la modificación de los Estatutos de la Autoridad del Transporte Metropolitano, Consorcio para la coordinación del sistema metropolitano de transporte público del área de Barcelona, y su texto refundido.
eli/es-ct/ac/2017/02/21/gov16/
Sometimes, depending on the numeration system used by each public administration, it may happen that rules of the same rank issued on the same date, present identical numbers, which could mean that different legal resources have the same URI[27].
When the URI for the same type of legal resource is generated, and it has the same date and the same number of another legal resource that already has an URI, a suffix will be added to the official number, beginning with the letter "b" and following with the rest if this necessary "c", "d", "e"… etc. For this purpose neither the letter "a" nor the letter "ñ" will be used.
NAVARRA:
Orden Foral 8/2015, de 4 de febrero, del Consejero de Educación, por la que se aprueban las bases que van a regular el procedimiento de admisión del alumnado en centros públicos y privados concertados, para cursar enseñanzas de segundo ciclo de Educación Infantil y Educación Primaria en la Comunidad Foral de Navarra.
eli/es-nc/of/2015/02/04/8/
Orden Foral 8/2015, de 4 de febrero, de la Consejera de Salud, por la que se crea el Servicio de Medicina Interna del Complejo Hospitalario de Navarra[28].
eli/es-nc/of/2015/02/04/8(b)/
In the case of rules without an official number, either because its legislative type that does not have an associated official number, or because it is an old regulation, a fictitious number[29] will be assigned. This number will be included between brackets, in order to differentiate it from the official numbers.
ASTURIAS:
ESTADO
Resolución de 24 de febrero de 2017, de Puertos del Estado, por la que se publica la de 14 de noviembre de 2016, sobre delegación de competencias.
eli/es/res/2017/02/24/(1)/
Resolución de 24 de febrero de 2017, de Puertos del Estado, por la que se publica la de 14 de noviembre de 2016, sobre delegación de competencias.
eli/es/res/2017/02/24/(2)/
Resolución de 24 de febrero de 2017, de Puertos del Estado, por la que se publica el Acuerdo del Comité de Distribución del Fondo de Compensación Interportuario, sobre delegación de competencias.
eli/es/res/2017/02/24/(3)/
Resolución de 24 de febrero de 2017, de la Secretaría General de Pesca, por la que se publica la actualización del censo de las flotas de altura, gran altura y buques palangreros mayores y menores de 100 toneladas de registro bruto, que operan dentro de los límites geográficos de la Comisión de Pesca del Atlántico Nordeste.
eli/es/res/2017/02/24/(4)/
This element identifies if the resource corresponds to the rule's initial text, as it was published in the official gazette, or if it is the consolidated legal resource.
The element eli:version must present a controlled vocabulary table associated, which in the case of Spain, includes the following values:
Besides, it is available the value "cer" for those public administrations that have a corrected version. This value will be used only if the system offers the text of the rule including the corrections (so, it is not an initial legal resource) and offers it independently and apart from the consolidated versions (so, it can not be considered a consolidated legal resource)
This template component shows the point in time of the updating of consolidated legal resources[30], based on the criteria used by each public administration to create consolidated versions (text in force, last published text…).
The format YYYYMMDD, recommended by the EU, will be used to distinguish it from the date of signature.
The element eli:version_date has to be part of the URI only when the intermediate consolidated versions are offered by the system[31]. Nevertheless, if that is not the case, it could be useful to have this information in the system as a metadata.
By default, if there is not a point in time in the request of a consolidated legal resource, the system will show the last consolidated version because is considered more useful for the user.
AAAAMMDD Format
This component of the template identifies the different languages in which the legal resources are published.
To build up this element, the three letters code of ISO 639-3 will be used, with an adaptation for Valencian[32] and for the bilingual texts, given that some public administrations publish two linguistic versions in the same document.
| LANGUAGE | ISO 639-3 |
|---|---|
| Spanish | spa |
| Catalan | cat |
| Basque | eus |
| Galician | glg |
| Occitan | oci |
| Valencian | vci |
| Multilingual texts | mul |
| Bilingual texts | |
| Catalan+Spanish | cat-spa |
| Basque+Spanish | eus-spa |
| Galician+Spanish | glg-spa |
| Occitan+Spanish | oci-spa |
| Occitan+Catalan | oci-cat |
| Valencian+Spanish | vci-spa |
It must be remarked that this table of authorities refers only to the languages with official value in Spain. In the case of a public administration offering legal resources in other foreign languages (English, French…) the corresponding values of ISO 639-3 will apply.
ISO 639-3 with adaptations for the Valencian and for bilingual texts
The values of the URIs recommended by the EU are the ones established by the IANA. The full list can be consulted at: http://www.iana.org/assignments/media-types.
IANA
ELI admits different points of view regarding what can be considered as a legal resource. Thus, in addition to the rules, the ELI ontology provides the possibility of applying the identifier to the gazette itself, according to each Member State consideration.
Therefore, along with the URI template envisaged for the rules, it has been considered convenient to include in this technical specification a URI template model for the issues of the official gazette and the summaries (indexes).
For these purposes, two values of the controlled vocabulary table "type" will be used.
/eli/{jurisdiction }/{type}/{year}/{month}/{day}/{number}/{language}/{format}
(Content not available in English)
| Campo (ELI) | Descripción | Formato | Valores | Comentarios |
|---|---|---|---|---|
| Jurisdiction | Jurisdicción | Lista limitada de valores alfabéticos | Tabla de vocabulario controlado | ISO 3166 alfa 2:
|
| Type | Indica el tipo de recurso legal | Lista limitada de valores alfabéticos (de 1 a 4 letras) | Tabla de vocabulario controlado | La tabla de vocabulario controlado contiene dos valores específicos: «dia» para los números del diario oficial «sum» para el sumario del número correspondiente |
| Year | Año de publicación del diario | Valores numéricos Formato AAAA |
2001, 2002… | Fecha de publicación del diario (yyyy/mm/dd) |
| Month | Mes de publicación del diario | Valores numéricos Formato MM |
01, 02… | |
| Day | Día de publicación del diario | Valores numéricos Formato DD |
01, 02… | |
| Number | Número | Valores numéricos en ocasiones, alfanuméricos. | Número del diario oficial. En caso de existir suplementos o anexos, se añadirá su identificación, separada del número con un guión. | |
| Language | Idioma | Lista limitada de valores alfabéticos | Tabla de vocabulario controlado | Se propone el uso de la norma ISO 639-3 (código de 3 letras), con una adaptación para el valenciano y los textos bilingües |
| Format | Formato de publicación | Lista limitada de valores | html, pdf, epub, xml | Los valores de los formatos se deben ajustar a las tipologías establecidas por IANA. |
For example:
CATALUÑA
DOGC número 3791 de 31 de diciembre de 2002.
eli/es-ct/dia/2002/12/31/3791/cat/pdf
Anexo A del DOGC número 3791 de 31 de diciembre de 2002.
eli/es-ct/dia/2002/12/31/3791-A/cat/pdf
Sumario del DOGC número 3791 de 31 de diciembre de 2002.
eli/es-ct/sum/2002/12/31/3791/cat/pdf
Sumario del anexo A del DOGC número 3791 de 31 de diciembre de 2002.
eli/es-ct/sum/2002/12/31/3791-A/cat/pdf
Nevertheless, the application of this template depends on each administration, as it is not strictly necessary in terms of interoperability.
The web servers must be configured to resolve ELI URIs, managing the contents so that the information is displayed according to the representation that is most appropriate for the user. In practice, when searching through the URI of a legal resource, there will always be a redirection to the URI of an expression of that legal resource that is appropriate, after analysing the characteristics and preferences of the users.
When an HTTP request is made by a person or a program, the web server can reply in two ways:
If there is already a system to offer legal resources, it is not necessary to build a new one. The web server can use redirection techniques (HTTP 303) that respond with the URI of the system in production when receiving an ELI request.
URIs must be persistent over time. An improperly offered URI should not disappear and generate a broken link, instead of that, the server can redirect the correct URI or indicate the error (and, in this case, the correct URI).
The implementation of the URI template in Spain requires the standardization of the metadata used by the different public administrations to describe legislation, at least those containing the information of the components of the URI.
Therefore, in Spain Pillar 1 must be addressed together with Pillar 2, in order to establish a common minimum metadata set:
This initial definition of common metadata will be expand as progress is made in the implementation of the identifier, with the gradual approach that characterizes the ELI. The goal is to approach the definition of the metadata schema and the incorporation of additional metadata that ease greater interoperability, as well as those that define the legal relations among rules.
However, the administrations do not have to replace their current metadata schemes. The ELI metadata can be used in combination with customized metadata schemes and the mapping of the elements used in their own scheme with those of the ELI ontology can be done.
The set of minimum common metadata is as follows:
(Content not available in English)
| Name | Domain | Range | Definition | Observaciones |
|---|---|---|---|---|
| METADATOS FORMAN PARTE PLANTILLA URI NORMATIVA ESTATAL Y AUTONÓMICA | ||||
| eli:jurisdiction | LegalResource | eli:AdministrativeArea, containing the list of administrative territorial units defined in http://publications.europa.eu/mdr/authority/atu | The jurisdiction from which the legal resource originates. The place identifier can be taken from the Administrative Territorial Unit table published of the EU Publications Office at http://publications.europa.eu/mdr/authority/atu. Member States don't have to recreate their own list of values. |
Definida conforme ISO3166 alfa 2 (apartado 7.1) |
| eli:type_document | LegalResource | eli:ResourceType, corresponding to a local concept scheme. | 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 |
Elemento obligatorio según la ontología ELI. Tabla de vocabulario controlado (apartado 7.2) |
| eli:date_document | LegalResource | xsd:Date | Date of adoption or signature (of the form yyyy-mm-dd) | Genera los elementos year/month/day de la URI (apartado 7.3) |
| eli:number | LegalResource | xsd:String | An identifier or other disambiguating feature for a legal resource or legal expression. This can be the number of a legislation, the number of an article, or the issue number of an official journal. | Con carácter general, el número se corresponde con el número oficial. Si no existe, se genera un number ficticio (apartado 7.4) |
| eli:version | LegalResource | eli:Version, corresponding to a local concept scheme | A 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. | Tabla de vocabulario controlado (apartado 7.5) |
| eli:version_date | LegalResource | xsd:Date | The point-in-time at which the provided description of the legislation is valid. |
Este metadato está previsto para recursos consolidados e indica la fecha de su actualización. Se adapta a distintos criterios de interpretación (criterio de vigencia o de publicación). Es obligatorio cuando se ofrecen las versiones consolidadas intermedias. Sólo forma parte de la URI en estos casos (apartado 7.6). |
| eli:language | LegalExpression | eli:Language, corresponding to the list of languages published by EU Publications Office. | 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. |
Elemento obligatorio según la ontología de ELI. Definido conforme la ISO 639-3 con una adaptación para el valenciano así como para los textos bilingües (apartado 7.7) https://elidata.es/mdr/authority/language/ |
| eli:format | Format | Owl:Thing | The physical embodiment of a legal expression, either on paper or in any electronic format (definition adapted from RDA). For example, any electronic or physical format of the legal expression (XML, TIFF, PDF, etc.); e.g. PDF version of act 3 of 2005. (adapted from Akoma Ntoso) |
Elemento obligatorio según la ontología de ELI. |
| METADATOS CON INFORMACIÓN RELEVANTE | ||||
| eli:title | LegalExpression | xsd:String | 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. |
Elemento obligatorio según la ontología de ELI |
| eli:date_publication | LegalResource; LegalExpression | xsd:Date | 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 of legal expressions can be separately asserted, using standard Dublin Core properties. | |
| eli:publisher (eli:publisher_agent) |
LegalExpression; format | xsd:string | Publisher: An entity responsible for making the resource available (definition from Dublin Core). This property should be used when the value cannot be identified by a suitable URI; if a URI is available, the property "publisher_agent" should be used. | Resulta de interés identificar la entidad encargada de publicar el recurso, mediante la correspondiente URI, dado que en ocasiones la entidad responsable del diario oficial no es la que ofrece los textos consolidados |
| METADATOS QUE DEFINEN LAS RELACIONES ENTRE ENTIDADES | ||||
| eli:is_member_of | LegalResource | LegalResource | Indicates that this resource is conceptually included in another one. Typically the successive temporal versions of a given legislation are conceptually members of a single « abstract » resource. For the notion of physical inclusion, use eli:is_part_of. | Enlaza un recurso legal con el recurso legal abstracto al que corresponde |
| eli:has_member | LegalResource | LegalResource | Indicates that this resource conceptually includes another one. For the notion of physical inclusion, use eli:has_part. | Enlaza el recurso legal abstracto con los recursos legales que derivan de él. |
| eli:is_another_publication_of | LegalResource | LegalResource | Indicates that this resource is a new publication, in a different official journal, of another resource already published elsewhere, and cannot be considered to be the same resource (owl:sameAs cannot be used to avoid potential duplication of certain metadata, like the date of publication, or the publisher). Note that this is different from the exceptionnal cases of "republication", where the same resource is actually republished in the same official journal a few days after its initial publication, in case of errors. |
Enlaza una norma publicada en un diario oficial con una publicación anterior en otro diario |
| eli:has_another_publication | LegalResource | LegalResource | Inverse of "is_another_publication_of". | Enlaza una norma publicada en un diario oficial con una publicación posterior en otro diario |
| eli:realizes | LegalExpression | LegalResource | Relates a legal expression to the legal resource realised through that expression. (definition adapted from RDA). Inverse of "is_realized_by". | Elemento obligatorio según la ontología de ELI.Enlaza la expresión con el recurso legal |
| eli:is_realized_by | LegalResource | LegalExpression | Relates 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". | Enlaza un recurso legal con sus expresiones. Aunque no es un elemento obligatorio, se considera conveniente incorporar este metadato para establecer las relaciones de manera bidireccional |
| eli:embodies | Format | LegalExpression | Relates a physical format to the legal expression embodied in that format (definition adapted from RDA). Inverse of "is_embodied_by". | Elemento obligatorio según la ontología de ELI.Enlaza el formato con la expresión |
| eli:is_embodied_by | LegalExpression | Format | Relates a legal expression to a physical format of that expression (definition adapted from RDA). Inverse of "embodies". | Para enlazar la expresión con el formato. Aunque no es elemento obligatorio, se considera conveniente incorporar este metadato para establecer las relaciones de manera bidireccional |
| eli:consolidates | LegalResource | LegalResource | Indicates that this consolidated legal resource or expression (which is usually the product of an editorial process that revises the legislation) takes into account another one. This property should be used multiple times to refer to both the original version or the previous consolidated version, and to the legislations making the change. | Para enlazar el recurso legal consolidado con el inicialmente publicado |
| eli:consolidated_by | LegalResource | LegalResource | Inverse of "consolidates". Indicates that this legal resource or expression is taken into account in consolidated text (which is usually the product of an editorial process that revises the legislation). | Para enlazar el recurso legal inicialmente publicado con el recurso legal consolidado |
| eli:corrects | LegalResource or LegalExpression | LegalResource or LegalExpression or Format | Indicates that this resource introduces textual modifications (like correction of spelling mistakes) with no legal change in another resource, expression or format; typically corrigenda in EU legislation. For modifications that have a legal impact, use eli:amends. | Para enlazar las correcciones con el recurso legal correspondiente |
| eli:corrected_by | LegalResource or LegalExpression or Format | LegalResource or LegalExpression | Inverse of "corrects". Indicates a resource that introduces textual modifications (like correction of spelling mistakes) with no legal change in this resource, expression or format; typically corrigenda in EU legislation. For modifications that have a legal impact, use eli:amended_by. | Para enlazar el recurso legal con sus correcciones |
The technical specification has designed a flexible implementation system, adapted to the variety and diversity which characterizes the Spanish legislation in its different territorial levels.
Nevertheless, regarding local legislation, some specific legal and technical requirement should be taken into account, which imply the need of adapting the adopted solutions for the state and autonomic rules:
The rules of local entities should be published in the corresponding official gazzete of the Province (Boletín Oficial de la Provincia / BOP), and this publication defines its entry into force
There are 43 official gazettes of the province, since in the case Autonomous Communities formed by a single province, the publication of local rules takes place in a specific section dedicated in the autonomic official gazettes[36].
All the official gazettes are published in electronic edition. Some of them offer besides the pdf format, the html or xml format also.
So far, the official gazettes of the Province have been focused mainly on offering a service of official and authentic publication, with the access to published issues of the gazette through calendars systems. This technique is usually completed with simple search engines, based on different searching criteria such as text, date and sometimes subject words. However, it is common that search engines only retrieve information from a recent date o, in most cases related to the moment in which these gazettes became electronic publications.
Most gazettes lack of structured metadata which describe the published contents. Thus, it is normal that rules are not distinguished (the "legislation", the object of the ELI project) from other types of contents of their information systems. Besides, very few official gazettes of the province label the documents with the identification of the local entity that issues the legislation.
Additionally, many official gazettes are only published as a pdf document, with no other specific pdf or html page for each published provision or announcement. Consequently, rules have not a singular entity in the information systems of these official gazettes of the province. And it makes it incompatible with the model of ELI, which is based on the individualization of each resource that needs to be identified uniquely.
In this technological context, the implementation of ELI by most official gazettes of the province should be tackled in a more ambitious documentation and technological updating project of the publication and database systems.
The technological situation is different in the case of Autonomous Communities formed by a single province, whose gazettes have more evolved systems. They have already applied or are in the process of applying ELI to autonomic legislation.
Regarding the additional rendering of legal services -such as the legal analysis of published rules or the development of consolidated texts- these activities are carried out by the local entity more than by the corresponding official gazette, because of the high legal specialization they involve.
In any case, thanks to ELI there will be a greater interoperability which will allow that the consolidated texts offered by the local entities will be linked from the official gazette of the province. It will give an easier access to law for the citizens.
Local entities, at least the local councils of greater size and all the provincial councils, offer legal information in their websites. Also, in some specific cases, the provincial council provides information about the current regulation of the entities within its scope. The information is often hosted in the respective transparency website.
In practice, these online information services of local entities seem to be the main source of legal information for citizens and for legal practitioners, instead of the territorial official gazettes.
In any case, the heterogeneity of local entities and the changeable situation in their technological projects determine that their legislative information systems are different, when they are available:
As the official gazettes of the province, the different range of maturities in these local information systems constrain the possibilities of applying ELI. However, since the amount of rules in local information systems is limited, the implementation of the identifier is easier for them than in the official gazettes of the provinces, which publish a larger number of rules every year.
It has to be added that some local entities have an informative gazette[37]. In relation to legislation, that is the scope of ELI project, legislation is published in these informative gazette only for informative purposes , so they are quite similar to the legal information services that local entities offer to the citizens.
Finally, it should be remarked that in general terms, there are not significant relations between the official gazettes of the province and local information systems.
The aim of this Addendum is to adapt the guidelines of implementation to the characteristics of the local legislation, so the interoperability of legal information offered online by the different Spanish public administrations is guaranteed.
In this sense, the variable technological situation of the official gazettes of the province and the legal information systems of local entities do not allow to draw up a uniform goal for implementing ELI to local legislation. For this reason, as opposed to what is planned for state and autonomic legislation, the Addendum sets out a model of asymmetric implementation, in which each official gazette of the province and each local administration can apply the identifier at its own pace and with the intensity allowed by its resources. It is true that most benefits of the ELI are obtained when the three pillars are implemented, but it is also possible to improve significantly the interoperability through a gradual approach.
With these goals, this Addendum:
Some provincial and local entities gazettes have well developed legal information systems, so they are able to apply the European standard easily and to take advantage of the possibilities available in terms of interoperability, transparency and new services development. However, for other local administrations, ELI implementation is not possible at the moment, because they should improve simultaneously in their information systems.
Nevertheless a defined and steady specification have advantages for those entities also:
All in all, the Addendum of the specification is an instrument for local administrations to apply ELI, at its own pace.
Despite this, in order to improve interoperability, the application of ELI has to be done in a coordinated way with the implementation developed not only by the State and the Autonomous Communities, but also by the rest of local entities. The goal of this coordination is not synchronizing the application of ELI by the official gazettes of the province and by the different local entities of their scope, but to avoid incompatibilities between the properties attributed to the same legal resource, which in the end will make interoperability impossible.
In fact, a) the heterogeneity of local rules, b) the fact that information systems in which these rules are offered depend on different public administrations -the official gazette of the province and the local entity issuing the rule-, and c) the asymmetry of the model of implementation, make necessary an additional effort of coordination. One of the principles around which ELI is built is that every resource has its corresponding unique identifier and the metadata values that define its legal properties are the same, no matter the information system which is offering them.
Therefore, the coordination requires that when a local entity is going to apply ELI, it should analyse before if the official gazette of the province which publishes its legislation is also applying it and in which way. And vice versa, if local entities have begun to implement ELI before the official gazette of the province, the latter should study how the application by the local entities of its territorial scope is being developed.
To this effect, the publication of updated and complete information about the way each local administration applies ELI (either an official gazette of the province, a provincial government or a local government) constitutes a mus,t so that coordination in the implementation of the project and, therefore, interoperability of legal information can be assured.
Besides, the Council conclusions of November 2017 on the European Legislation Identifier establish that all administrations that apply the identifier or have planned its application, must have a website with all the information about the project.
As it has been pointed out above, the webpage https://www.elidata.es/, apart from informing about the ELI project to the citizenship, offers technical resources for the application of the identifier and gathers updated information about the implementations carried out by the State and the Autonomous Communities, through the link to their respective ELI webpages.
In order to ensure coordination in the local scope, it is necessary that those local entities that apply or plan to apply ELI, inform the webpage elidata.es about their corresponding webpages, as the State and the Autonomous Communities have been doing until now.
In this way, the common website elidata.es will facilitate that the official gazettes of the province and the local entities within their scope can find the required information so that their respective implementations are compatible[38]. Likewise, the availability of this information will allow that any public administration takes advantage of previous implementation experiences already developed by others, anticipating risks and avoiding mistakes, with the consequent time and resources savings.
ELI is applied to "legal resources", that is, to legislation and not to administrative acts.
Thus, in the local scope, ELI will apply only to those documents with these two conditions:
Local legislation presents a rich typology: apart from the Ordenanzas and the Reglamentos as the most representative categories, other decisions of local entities could also have regulatory nature, such as town planning or instrumental entities' statutes.
Despite the fact that ELI benefits are greater the larger the set of rules applying ELI is, according to the gradual character of the identifier it is not necessary to extend it to all local rules, at least at the beginning. Each entity can decide to which categories applies ELI: either only to Ordenanzas, or to both Ordenanzas and Reglamentos, or if it is expanded to other regulatory categories that are eventually arranged.
For instance, even if the implementation is only limited to Ordenanzas, it would suppose an important progress in terms of accessibility to local legal information, since Ordenanzas is the type of rule more significant to citizens and companies.
In any case, it is essential that each local administration informs about the specific types of rules to which the identifier is applied through its webpage with information about the ELI project.
Additionally, it should be remarked that the issuing procedure of local rules, in particular Ordenanzas and Reglamentos, includes the publication of a text provisionally approved and afterwards another publication for the final text. For the purpose of ELI application, only the final texts will be considered.
Regarding the time frame of the legislation to which ELI is assigned, it is possible to apply a gradualness aproach likwise.
The ideal objective would be to apply the identifier with a time criterion equivalent to the one used for state and autonomic legislation[39], and implement it for all the local legislation published after 29th December 1978. At the other side, the minimum objective would be to apply the identifier to the new resources that are being published after a fixed date.
Between one and another possibilities, all types of intermediate solutions could fit. Thus, regarding retrospective application, less ambitious options can be valid, such as the effective date of the Constitution of 1978. For instance, in the case of the official gazette of the province, other possibilities could be taken into account, such as the start date of the official electronic publication, which is when the available information is likely to be easier to structure.
It is equally feasible that this temporal approach combines with criteria related to normative scope: for example, a local entity could apply ELI to all Ordenanzas passed since 1978 (or only to Ordenanzas that are currently in force) and for the rest of the rules, apply ELI only to those published in the future.
Any of these options of implementation could be valid. It should be outlined again that it is important that each local administration publish and keep updated the information about the time frame to be considered in its corresponding webpage with information about the ELI project.
The model defined in section 5.2 is based on the existence of two levels of legal resources: the first level corresponds to the rule considered in an abstract way (abstract legal resource) and the second level is derived from the previous one and corresponds with the different versions that a rule can have, being either the initially published one or the consolidated (updated) versions[41].
However, in the local scope, the outlook is more diverse:
Those local entities that offer both the initial and the consolidated versions or that have planned to offer them, should implement necessarily the model of section 5.2, configuring a legal abstract resource so that the initial and the consolidated versions of the rule are grouped around it by using the ELI properties "eli:is_member_of"[42] and "eli:has_member"[43].
Consequently, if the legal information system has the initial and consolidated version, at least three legal resources should be configured for each one (eli:LegalResource):
Equally, the initial and the consolidated legal resources are related to each other with the properties eli:consolidates (in order to relate the consolidated legal resource with the initial resource it consolidates) and eli:consolidated_by (in order to relate the initial legal resources with the consolidated legal resources that corresponds to its consecutive updates).
(Content not available in English)
Those local entities offering a unique version of the rule (either the initial or the consolidated one) can configure a single legal resource:
(Content not available in English)
Anyway, independently of the fact that the model used by the entity has a legal resource or not, the initial and/or consolidated legal resource should have at least a legal expression (if it is published only in one language) or those that are appropriate in case of being published in different languages[44].
The resources is related to its expressions by means of the properties of the ontology eli:realizes and its opposite eli:is_realized_by.
Each expression has to be shown in one or several formats (pdf, html, xml…). The expression and the different formats in which the resource is offered are related by means of the properties eli:embodies and eli:is_embodied_by.
The specification focuses on the cases with double publication in the state and the autonomic gazettes[45]. This double publication model could also be applied when there is a local informative gazettel, with the purpose of relating such publication with that of the Official Gazette of the Province. However, doing it this way, it would be necessary to be specially cautious with regard to eli:date_publication metadata.
As it is shown in the next section, in the case of local rules, this element is part of the URI and it should correspond always to the date of publication in the official gazette of the province in order to avoid the creation of different URIs for the same resource. Thus, the date of publication in the local informative gazette should be handled as metadata of the local information system itself and not as the eli:date_publication metadata.
The structure and the components of the local rules URI are the same as the ones for state and autonomic legislation.
Nevertheless, two special features should be taken into account:
/eli/{jurisdiction}/{type}/{year}/{month}/{day}/{number}/{version}/{version_date}/{language}/{format}
| ELI name | Description | Format | Values | Comments |
|---|---|---|---|---|
| Jurisdiction | Jurisdicción | Limited list of alphabetic values | List of controlled vocabulary | ISO 3166 alfa 2+ registration number in the Registry of local entities |
| Type | Tipo de norma | Limited list of alphabetic values (1 to 4 letters) | List of controlled vocabulary | The types will be identified by acronyms with a variable length |
| Year | Año | Numeric values Format AAAA | 2001, 2002… | Date of publication in the BOP (yyyy/mm/dd) |
| Month | Mes | Numeric values Format MM | 01, 02… | |
| Day | Día | Numeric values Format DD | 01, 02… | |
| Number (natural identifier) | Número | Numeric and, occasionally, alphanumeric values | The number to be used is a fictitious identifier, unless the entities give an official number to the legal resource and it appears in the BOP | |
| Version | Versión | Limited list of alphabetic values (3 letters) | List of controlled vocabulary | It identifies if the legal resource is the initial, the consolidated or the corrected one |
| Version_date (point in time) | It indicates the date of updating. | Numeric values. Format: AAAAMMDD | For consolidated legal resources | |
| Language | Language | Limited list of alphabetic values | List of controlled vocabulary | ISO 639-3 (3 letters code), with adjustments for Valencian and bilingual documents. |
| Format | Format of publication | Limited list of values | html, pdf, epub, xml… | The format values must be comply with the typologies established by IANA |
This element identifies the territorial level of the considered legal resource. In the case of state and autonomic legislation, the ISO3166 alfa2 standard is used.
Regarding local entities, the ISO3166 alfa2 only has a classification for the provinces, so it is not useful to define the jurisdiction of all local entity in accordance with uniform guidelines.
Therefore, the system for all kinds of local entities, including the provinces, combines the ISO3166 alfa2 standard and the registration number in the "Registry of Local Entities".
The registration number in the above mentioned Registry is unique and constant in time and is freely accessible in the electronic site of the Department responsible for Public Administrations[48].
The registration number has the structure "01XXYYYY", in which:
For example,
The controlled vocabulary tables, combined with the ISO3166 alfa 2 rule and the registration number, are available and updated in the common website https://www.elidata.es/mdr/authority/jurisdiction/2/.
ISO3166 alfa2- rule registration number in the Registry of local entities
In the ELI schema, the element eli:type_document should be collected in a list of controlled vocabulary.
Just as for state and autonomic legislation, a limited list of values identified by means of acronyms of variable length (1 to 4 letters) will be used.
A simplified table has been preferred, focused on the more relevant regulatory categories, leaving only eventually the residual type named Otros ("alia") for regulatory nature decisions, such as bandos or those not corresponding to any of the types of the controlled vocabulary table.
Anyway, the table should not be interpreted in the sense that all categories must be included in the implementation. Each entity can decide to which types of rules applies the identifier, according to section 11.3.
(Content not available in English)
A las derogaciones, modificaciones y suspensiones de estos tipos normativos debe asignárseles el eli:type correspondiente al documento objeto de aprobación, derogación, modificación o suspensión: por ejemplo, los acuerdos del Pleno aprobando, derogando, modificando o suspendiendo uno de estos tipos llevarán el type correspondiente al documento aprobado, derogado, modificado o suspendido |
||||||
| Español | Catalán | Euskera | Gallego | Valenciano | Observaciones | Valor |
|---|---|---|---|---|---|---|
| Ordenanza | Ordenança | Ordenantza | Ordenanza | Ordenança | Téngase en cuenta que este tipo también incluye las ordenanzas fiscales. | odnz |
| Reglamento | Reglament | Erregelamendua | Reguamento | Reglament | Téngase en cuenta que este tipo también incluye los reglamentos orgánicos. | reg |
| Instrumento urbanístico | Instrument urbanístic | Hirigintza-plangintzako tresna | Instrumento urbanístico | Instrument urbanístic | Téngase en cuenta que este tipo incluye cualquier norma de planeamiento territorial o urbanístico, con independencia de su denominación concreta. Las ordenanzas en materia urbanística llevarán el tipo "ordenanza". |
iurb |
| Presupuestos | Pressuposts / pressupostos | Aurrekontuak | Orzamentos | Pressupostos | pre | |
| Estatutos | Estatuts | Estatutuak | Estatutos | Estatuts | est | |
| Otros | Altres | Beste batzuk | Outros | Altres | Solo puede atribuirse a aquellas disposiciones de naturaleza reglamentaria que no tengan encaje en las categorías anteriores, así como a sus modificaciones, derogaciones y suspensiones. | alia |
Local entities should use exclusively the table of controlled vocabulary of the local legislation types. Under no circumstances should they use the specific "type" of the state and autonomic legislation[49]. There are only two common categories in both tables of controlled vocabulary, "reglamento" and "otros", which are the only ones that can appear under state, autonomic and local jurisdiction.
It should be noted that these are the types of legal resources for ELI, but each entity can maintain in its own system or database a richer and more complete typology, and make the corresponding mapping with the eli:type table.
With the purpose of assuring interoperability, the assignment of the type_document should be carried out according to the legal nature of the rule and not to the variable methods in which the provincial official gazette has been published. In this sense, the same type of legal resource, for example a bylaw, can appear published in different ways, such as:
All these cases fit in the same eli:type_document: "ordenanza", in spite of the fact that each provincial official gazette can continue the publication in the same way as the present ones.
Nevertheless, it could happen that a rule could be difficult to fit in any of the typologies. For these cases in order to avoid the creation of incompatible URIs, it is recommended to contrast the type attributed by the administration that has implemented the ELI in the first place (either the BOP or the local entity) before creating the corresponding URI.
Some examples of allocation of types:
(Content not available in English)
| Recurso legal | eli: type_documet | Valor |
|---|---|---|
| Aprobación definitiva de la derogación del anexo de la ordenanza municipal reguladora de la tasa por aprovechamiento del dominio público | Ordenanza | odnz |
| Aprobación definitiva del Reglamento orgánico y de funcionamiento del Ayuntamiento | Reglamento | reg |
| Texto refundido de las normas urbanísticas del Plan de ordenación urbana | Instrumento urbanístico | iurb |
| Aprobación definitiva del proyecto de urbanización de la parcela 159 del polígono 1 de la localidad de… | Instrumento urbanístico | iurb |
| Aprobación definitiva de la modificación puntual de ordenación detallada del Plan Especial de Protección del centro histórico | Instrumento urbanístico | iurb |
| Aprobación definitiva de los presupuestos correspondiente a 2020 | Presupuestos | pre |
| Modificación de los Estatutos de las Escuelas Infantiles | Estatutos | est |
| Edicto aprobación bases reguladoras y convocatoria de ayudas con destino a minimizar el impacto económico sobre PYMES derivado del… | Otros | alia |
| Norma de la Diputación provincial de asistencia económica | Otros | alia |
| Resolución de Alcaldía regulando los horarios de carga y descarga | Otros | alia |
| Pliego de cláusulas administrativas para la selección de personas demandantes de una vivienda en régimen de alquiler social… | Otros | alia |
| Acuerdo de la Comisión de Gobierno del Ayuntamiento de… sobre normativa de uso de los puntos verdes | Otros | alia |
| Decreto relativo a la aprobación de actuaciones administrativas automatizadas y de creación de sello electrónico de órgano | Otros | alia |
With regard to the correction of errors, they will be considered a subtype, in the same terms as it has been stated for state and autonomic legislation.
The URI of the corrections will be formed with the structure of the URI of the abstract legal resource corresponding to the corrected rule, adding after the eli:number, the element corrigendum and the date of publication (eli:date_publication) of the correction of errors in the provincial official gazette, with format AAAAMMDD, in order to distinguish it from date of publication of the rule which has been corrected.
/eli/{jurisdiction}/{type}/{year}/{month}/{day}/{number}/{corrigendum}/{date_publication}/{dof}/language/format
For example:
Rectificación error en anuncio publicado en BOP de 27 de diciembre de 2019 sobre la modificación de la ordenanza reguladora de la tasa por suministro de agua, alcantarillado y depuración del Ayuntamiento de Manzanares (BOP de 4 de junio de 2020)
eli/es-cm- 01130533/odnz/2019/12/27/(1)/corrigendum/20200604/dof/
The correction of errors only occur regarding the initial version of the legal resources. The consolidated resources cannot have the subtype of correction of errors.
Controlled vocabulary table with acronyms of variable length (1 to 4 letters)
/eli/{jurisdiction/{type}/{year}/{month}/{day}/{number}/{corrigendum}/{date_publication}/{dof}/{language}/{format}
One of the particularities of the URI template for the ELI for local legislation is that the date to be considered for the URI formation is the date of official publication of the text (the final text) in the official gazette of the province[50] and not the adoption or signature date[51].
The reason for this difference is that the adoption date is subject to legal interpretation, since the final text of some types of local rules is implicitly approved. In case the adoption date is used, it could easily lead to the attribution of incompatible URIs for the same legal resource.
The components are used independently {year} {month} {day}, and it will allow, through truncation of the URI, the recovery of all the rules of the same "type" published the same year, month or day.
AAAA/MM/DD format
This element informs about the official number that identifies each provision within its normative type.
The introduction of this element in the template is essential, since occasionally, the elements "type" and "date_publication" are not enough to identify the legal resources univocally. Different rules of the same type and adopted by the same entity can be published on the same day.
Almost all the local rules do not have an official number that is the number which is mentioned in the title of the publication in the official gazette of the province, with an identifying purpose and responding to formalised, normalised and consistent attribution criteria.
In this sense, those numberings that some provincial gazette assign to the provisions at the moment of their publication and only for the gazette organization purposes and internal control (as the publication order number, the marginals , the electronic verification code (CVE) and others) are not considered official numbers.
The official numbering range of the local rules is complicated since, sometimes, the information systems of the local entities present numberings (for instance, of taxing Ordenanzas) that are not included in the title published in the official gazettes of the province.
The lack of evenness in the numbering of the same rule can cause a great volume of inconsistencies in the URIs, so, as it has been pointed out, only the numbering appearing in the title of the publication in the official gazette of the province can be considered as eli:number. If the local entity has its own numbering which is not mentioned in the publication of the BOP, it can be included in the eli:id_local metadata, but it will never be used as eli:number neither for the creation of the URIs nor for the creation of ELI metadata.
When the rule has an official number, the criteria established in section 7.4 of the specification are the ones to follow for the attribution of the eli:number.
In case there is not official number[52], which the situation that will happen in most cases, the URIs of the ELI should have always the element eli:number. Therefore, in these cases, a fictitious number will be generated.
This fictitious number will be included between brackets in order to differentiate it from the official numbers.
The allocation of fictitious identifiers in case of having different rules of the same type published on the same day turns out difficult, due to the asymmetry in the application of ELI by the different public administrations which can offer the same legal resource (official gazette and local entity issuing the provision).
Thus, in case that different rules of the same local entity are published in the official gazette of the province on the same day, the attribution of the fictitious number will be normally done by the official gazette of the province and the information system of the local entity independently. Moreover, it is likely that this set will not be simultaneous but in different moments.
As it has been mentioned before, the ELI model and the proper philosophy of any URI (Uniform Resource Identifier) requires the same URI for each piece of legislation, independently of the information system which offers it.
With the purpose of facilitating the coordination and avoiding the creation of incompatible URIs, the attribution criterion of the fictitious number could be the order of appearance of the rules in the official gazette. So, the rule which is published in the first place (which is "before" in the official gazette of the province index) would have the fictitious number (1) and so on.
In these cases of different rules issued by the same entity, which are of the same type and published on the same date, it is recommended that the administration which applys the ELI in the second place verifies the fictitious number attributed by the administration which created the URI first..
It should also be mentioned that on the occasion of the ELI project, the local entities could assess the interest of setting an official number to the rules, at least to the more relevant typologies. This attribution could be made similarly to how the higher rank normative types are numbered in the State and the Autonomous Communities: sequential number/year (either in a unique serie for all normative typologies or in independent series according to the type).
This element identifies if the resource corresponds to the rule's initial text, as it was published in the official gazette, or if it is the consolidated legal resource.
The element eli:version must present a controlled vocabulary table associated, which in the case of Spain, includes the following values:
Besides, it is available the value "cer" for those public administrations that have a corrected version. This value will be used only if the system offers the text of the rule including the corrections (so, it is not an initial legal resource) and offers it independently and apart from the consolidated versions (so, it can not be considered a consolidated legal resource).
This template component shows the point in time of the updating of consolidated legal resources[54], based on the criteria used by each public administration to create consolidated versions (text in force, last published text…).
The format YYYYMMDD, recommended by the EU, will be used to distinguish it from the date of signature.
The element eli:version_date has to be part of the URI only when the intermediate consolidated versions are offered by the system[55]. Nevertheless, if that is not the case, it could be useful to have this information in the system as a metadata.
By default, if there is not a point in time in the request of a consolidated legal resource, the system will show the last consolidated version because is considered more useful for the user..
Format AAAAMMDD
This component of the template identifies the different languages in which the considered legal resource is published.
To form this element, as it has been planned for state and autonomic legislatoin, the three letter codes of ISO 639-3 will be used, with an adaptation for Valencian and for bilingual texts, since some administrations publish two linguistic expressions in the same document.
| Language | 639-3 |
|---|---|
| Spanish | spa |
| Catalan | cat |
| Basque | eus |
| Galician | glg |
| Occitan | oci |
| Valencian | vci |
| Multilingual texts | mul |
| Bilingual texts | |
| Catalan+Spanish | cat-spa |
| Basque+ Spanish | eus-spa |
| Galician+ Spanish | glg-spa |
| Occitan+ Spanish | oci-spa |
| Occitan+Catalan | oci-cat |
| Valencian+ Spanish | vci-spa |
It should be noted that this table authorities refers only to the languages with official value in Spain. In case that an administration offers legal resources in other foreign languages (English, French…) the corresponding values of the ISO 639-3 will be applied.
ISO639-3 with adaptations for Valencian and for bilingual texts
The values of the URI recommended by the EU are the ones established by IANA. The complete list can be consulted in: http://www.iana.org/assignments/media-types.
IANA
Some examples of URIs are as follows.
Ordenanza municipal reguladora del servicio de estacionamiento limitado en superficie del Ayuntamiento de Vitoria (publicada en el "Boletín Oficial del Territorio Histórico de Álava" de 28 de agosto de 2009)
Abstract legal resource:
Initial legal resource:
Initital legal resource expressions:
Consolidated legal resource:
Consolidated legal resource expressions:
ELI admits different points of view with regard to what can be considered a legal resource. So, apart from the rules, it is possible to apply the identifier to the issues of the official gazette.
The core of ELI are the rules, since identifying and describing them in the same way is the condition for the interoperability and the improvement of access to legal information for citizens.
However, even if the aim of the project is not to assign an URI to the official gazettes of the provinces, it has been considered useful to include in this Addendum a model of URI template specific for the issues of the provincial gazettes and for the summaries or indexes, so that those gazettes with a technological situation not adequate for the application of ELI, could take part in the project by the application of the identifier to the official gazette itself[56].
The URI-ELI template for the provincial official gazettes is the same planned for state and autonomic official gazettes.
For these purposes, two values of the controlled vocabulary table "type" will be used:
/eli/{jurisdiction}/{type}/{year}/{month}/{day}/{number}/{language}/{format}
(Content not available in English)
| ELI name | Descripción | Formato | Valores | Comentarios |
|---|---|---|---|---|
| Jurisdiction | Jurisdicción | Lista limitada de valores alfabéticos | Tabla de vocabulario controlado | ISO 3166 alfa 2+ número de inscripción de la provincia en el Registro de EELL |
| Type | Indica el tipo de recurso legal | Lista limitada de valores alfabéticos (de 1 a 4 letras) | Tabla de vocabulario controlado | La tabla de vocabulario controlado contiene dos valores específicos:
|
| Year | Año de publicación del diario | Valores numéricos Formato AAAA |
2001, 2002… | Fecha de publicación del diario (yyyy/mm/dd) |
| Month | Mes de publicación del diario | Valores numéricos Formato MM |
01, 02… | |
| Day | Día de publicación del diario | Valores numéricos Formato DD |
01, 02… | |
| Number | Número | Valores numéricos En ocasiones alfanuméricos |
Número del diario oficial. En caso de existir suplementos o anexos, se añadirá su identificación, separada del número con un guión. | |
| Language | Idioma | Lista limitada de valores alfabéticos | Tabla de vocabulario controlado | ISO 639-3 (código de 3 letras), con una adaptación para el valenciano y para los textos bilingües |
| Format | Formato de publicación | Lista limitada de valores | html, pdf, epub, xml… | Los valores de los formatos se deben ajustar a las tipologías establecidas por IANA |
For example:
"Boletín Oficial de la Provincia de Cádiz" number 208 of 30 October 2020
eli/es-an-02110000/dia/2020/10/30/208/spa
Summary of the "Boletín Oficial de la Provincia de Cádiz" number 208 of 30 October 2020
eli/es-an-02110000/sum/2020/10/30/208/spa
The introduction of the URI template in Spain requires the standardization of the metadata used by the different administrations to describe legislation, at least those containing the information of the URI components.
Therefore, Pillar 1 should tackled together with Pillar 2, in order to establish a list of minimum common set of metadata to be shared with the rest of local entities and with the state and autonomic administrations.
The set of common metadata for local normative includes the following ones:
However, the administrations do not need to replace their current metadata model. The ELI metadata can be used combined with customized metadata models and the mapping of the elements used in their own model with those of the ELI ontology can be done.
Even if the list of common metadata is parallel to the state and autonomic legislation, some peculiarities about their dynamics when they are applied to local rules should be added:
(Content not available in English)
| Name | Domain | Range | Definition | Observaciones |
|---|---|---|---|---|
| METADATOS QUE FORMAN PARTE PLANTILLA URI NORMATIVA LOCAL | ||||
| eli:jurisdiction | LegalResource | eli:AdministrativeArea, containing the list of administrative territorial units defined in http://publications.europa.eu/mdr/auth ority/atu | The jurisdiction from which the legal resource originates. | Definida conforme a ISO 3166 alfa 2+ número de inscripción en el Registro de EELL (apartado 11.5 a) https://www.elidata.es/mdr/authority/jurisdiction/2/ |
| eli:type_document | LegalResource | eli:ResourceType, corresponding to a local concept scheme | 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. |
Elemento obligatorio según la ontología ELI. Tabla de vocabulario controlado (apartado 11.5 b) https://www.elidata.es/mdr/authority/resource-type/2/ |
| eli:date_publication | LegalResource; Legalexpression | xsd:Date | 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 of legal expressions can be separately asserted, using standard Dublin Core properties. | Corresponde a la fecha de publicación en el BOP. Genera los elementos year/month/day de la URI (apartado 11.5 c). |
| eli:number | LegalResource | xsd:String | An identifier or other disambiguating feature for a legal resource or legal expression. This can be the number of a legislation, the number of an article, or the issue number of an official journal. | Generación de número ficticio, salvo que la entidad local emisora numere oficialmente y el número aparezca en la publicación en el BOP. El valor del número ficticio debe figurar entre paréntesis (apartado 11.5 d). |
| eli:version | LegalResource | eli:Version, corresponding to a local concept scheme | A 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. | Tabla de vocabulario controlado (Apartado 11.5 e). https://www.elidata.es/mdr/authority/version/ |
| eli:version_date | LegalResource | xsd:Date | The point-in-time at which the provided description of the legislation is valid. | Este metadato está previsto para recursos consolidados e indica la fecha de su actualización. Se adapta a distintos criterios de interpretación (criterio de vigencia o de publicación). Es obligatorio cuando se ofrecen las versiones consolidadas intermedias. Sólo forma parte de la URI en estos casos. (apartado 11.5 f). |
| eli:language | LegalExpression | eli:Language, corresponding to the list of languages published by EU Publications Office | 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. |
Elemento obligatorio según la ontología ELI. Definido conforme la ISO 639-3 con una adaptación para el valenciano así como para los textos bilingües (apartado 11.5 g) https://www.elidata.es/mdr/authority/language/ |
| eli:format | Format | Owl:Thing | 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. |
Elemento obligatorio según la ontología ELI. |
| METADATOS CON INFORMACIÓN RELEVANTE | ||||
| eli:title | LegalExpression | xsd:String | 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. |
Elemento obligatorio según la ontología ELI. |
| eli:date_document | LegalResource; | xsd:Date | Date of adoption or signature (of the form yyyy-mm-dd). | La que corresponde al texto definitivo, ya se trate de fecha de aprobación/toma de conocimiento por el órgano colegiado o la fecha de firma por la autoridad competente. |
| eli:publisher (eli:publisher_agent) | LegalExpression; Format | xsd:string | Publisher: An entity responsible for making the resource available (definition from Dublin Core). This property should be used when the value cannot be identified by a suitable URI; if a URI is available, the property "publisher_agent" should be used. | Resulta de interés identificar la entidad encargada de ofrecer el recurso, mediante la correspondiente URI, dado que puede ser el BOP o la entidad local responsable del recurso. |
| METADATOS QUE DEFINEN LAS RELACIONES ENTRE ENTIDADES | ||||
| eli:is_member_of | LegalResource | LegalResource | Indicates that this resource is conceptually included in another one. Typically the successive temporal versions of a given legislation are conceptually members of a single «abstract» resource. For the notion of physical inclusion, use eli:is_part_of. | Enlaza un recurso legal con el recurso legal abstracto al que corresponde. |
| eli:has_member | LegalResource | LegalResource | Indicates that this resource conceptually includes another one. For the notion of physical inclusion, use eli:has_part. | Enlaza el recurso legal abstracto con los recursos legales que derivan de él. |
| eli:is_realized_by | LegalResource | LegalExpression | Relates 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". | Enlaza un recurso legal con sus expresiones. Aunque no es un elemento obligatorio, se considera conveniente incorporar este metadato para establecer las relaciones de manera bidireccional. |
| eli:realizes | Legal Expression | Legal Resource | Relates a legal expression to the legal resource realised through that expression (definition adapted from RDA). Inverse of "is_realized_by". | Elemento obligatorio según la ontología ELI. Enlaza la expresión con el recurso legal. |
| eli:is_embodied_by | LegalExpression | Format | Relates a legal expression to a physical format of that expression (definition adapted from RDA). Inverse of "embodies". | Para enlazar la expresión con el formato. Aunque no es elemento obligatorio, se considera conveniente incorporar este metadato para establecer las relaciones de manera bidireccional. |
| eli:embodies | Format | LegalExpression | Relates a physical format to the legal expression embodied in that format (definition adapted from RDA). Inverse of "is_embodied_by". | Elemento obligatorio según la ontología ELI. Enlaza el formato con la expresión. |
| eli:consolidates | LegalResource | LegalResource | Indicates that this consolidated legal resource or expression (which is usually the product of an editorial process that revises the legislation) takes into account another one. This property should be used multiple times to refer to both the original version or the previous consolidated version, and to the legislations making the change. | Para enlazar el recurso legal consolidado con el inicialmente publicado. |
| eli:consolidated_by | LegalResource | LegalResource | Inverse of "consolidates". Indicates that this legal resource or expression is taken into account in a consolidated text (which is usually the product of an editorial process that revises the legislation). | Para enlazar el recurso legal inicialmente publicado con el recurso legal consolidado. |
| eli:corrects | LegalResource or LegalExpression | LegalResource or LegalExpression or Format | Indicates that this resource introduces textual modifications (like correction of spelling mistakes) with no legal change in another resource, expression or format; typically corrigenda in EU legislation. For modifications that have a legal impact, use eli:amends. | Para enlazar las correcciones con el recurso legal correspondiente. |
| eli:corrected_by | LegalResource or LegalExpression or Format | LegalResource or LegalExpression | Inverse of "corrects". Indicates a resource that introduces textual modifications (like correction of spelling mistakes) with no legal change in this resource, expression or format; typically corrigenda in EU legislation. For modifications that have a legal impact, use eli:amended_by. | Para enlazar el recurso legal con sus correcciones. |
| eli:is_another_publication_of | Legal resource | Legal resource | Indicates that this resource is a new publication, in a different official journal, of another resource already published elsewhere and cannot be considered to be the same resource (owl:sameAs cannot be used to avoid potential duplication of certain metadata, like the date of publication or the publisher). Note that this is different from the exceptionnal cases of "republication", where the same legal resource is actually republished in the same official journal a few days after its initial publication, in case of error. |
Se utiliza en el caso de que la entidad desee relacionar la publicación efectuada por el boletín de información municipal con la efectuada por el boletín oficial de la provincia. No se utiliza en las versiones consolidadas. |
| eli:has_another_publication | Legal resource | Legal resource | Inverse of "is _another_publication_of". | Se utiliza en el caso de que la entidad desee relacionar la publicación efectuada por el boletín oficial de la provincia con la efectuada por el boletín de información municipal. No se utiliza en las versiones consolidadas. |
in the BOP of 3 January 2021 a single rule of a same type has been published
in the BOP of 4 March 2021 several rules, but all with different type, have been published
in the BOP de 30 July 2020 several rules of the same type have been published
in the BOP of 27 December 2020 several rules of different type have been published