Copyright © 2025
Effective policymaking relies heavily on monitoring, as assessing the impact of legislation and policies is crucial to determining whether specific objectives have been met. However, lack of coordination when setting reporting requirements can lead to legal interoperability barriers that then lead to inefficient policy measures, and to duplicated and overlapping requests, data duplication, and unclear data location.
To address this challenge, the European Commission announced in its Communication on the Long-term competitiveness of the EU (16 March 2023) that it would "make a fresh push to rationalize and simplify reporting requirements for companies and administrations." The Commission aims to introduce initial proposals for the green, digital, and economic thematic areas by autumn 2024, with the goal of reducing administrative burdens by 25% without compromising related policy objectives.
In support of this initiative, the European Commission has identified streamlining regulatory reporting as a key area for reducing administrative burden. By providing policy officers with a detailed understanding of existing legal frameworks and enabling them to leverage these frameworks, the Commission seeks to eliminate redundancies and harmonize reporting requirements, ultimately reducing the complexity and burden associated with regulatory reporting.
This application profile has the status SEMIC Working Draft published at 2025-01-15.
Information about the process and the decisions involved in the creation of this specification are consultable at the Changelog.
Copyright © 2024 European Union. All material in this repository is published under the license EUPL 1.2, unless explicitly otherwise mentioned
An Application Profile is a specification that reuses terms from one or more base standards, adding more specificity by identifying mandatory, recommended and optional elements to be used for a particular application, as well as recommendations for controlled vocabularies to be used.
An Annex to an Application Profile is a specification that precises the use of some aspects of the Application Profile for a specific context.
This specification uses the following prefixes to shorten the URIs for readibility.
Prefix | Namespace IRI |
---|---|
dct | http://purl.org/dc/terms/ |
eli | http://data.europa.eu/eli/ontology# |
rdf | http://www.w3.org/1999/02/22-rdf-syntax-ns# |
rdfs | http://www.w3.org/2000/01/rdf-schema# |
rrmv | http://data.europa.eu/2qy/rrmv# |
skos | http://www.w3.org/2004/02/skos/core# |
time | http://www.w3.org/2006/time# |
xsd | http://www.w3.org/2001/XMLSchema# |
An overview of RRMV is shown by the UML diagram below. The UML diagram illustrates the specification described in this document. For readability purposes the representation has been condensed as follows:
This document describes the usage of the following main entities for a correct usage of the Application Profile:
|
Action |
Action Result |
Agent Role |
Requirement |
Temporal Entity Specification |
The main entities are supported by:
|
Agent |
Agent Category |
Agent Type |
Annotation |
Concept |
Duration Temporal Entity Specification |
Expression |
Frequency |
Instant Temportal Entity Specification |
Interval Temporal Entity Specification |
Legal Expression |
Literal |
Manifestation |
Resource |
Result Type |
Role |
Role Type |
Status |
Temporal Function |
Work |
And supported by these datatypes:
| langString | xsd:anyURI | xsd:boolean | xsd:duration | xsd:string |
The main entities are those that form the core of the Application Profile. The properties and their associated constraints that apply in the context of this profile are listed in a tabular form. Each row corresponds to one property.
As this is the toplevel application profile for this usage context the reuse of the terms is indicated by their URIs.
If an URI is used from another vocabulary than the namespace 2qy
it means that the information is inherited as expressed in
the data specification in which that URI is defined.
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
at time | Temporal Entity Specification | 0..* | An Action valid within a time interval. | |
has agent role | Agent Role | 0..* | The involvement of an agent in a role within this action. | The involvement of the agent may be time dependent. |
has next | Action | 0..* | A succeeding action | A requirement may formulate a repetitive sequence of actions. This property chains the actions together. |
has result | Action Result | 0..* | A result of an action. | |
has status | Status | 0..* | A status of this Action. |
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
has title | langString | 0..* | Title of the action result | |
has type | Result Type | 0..* | A kind of result |
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
changes | Requirement | 0..* | Indicates that this work or expression legally changes another. This encompasses the notions of amendment, replacement, repeal, or other types of change. This may be a direct change (textual or non-textual amendment) or a consequential or indirect change. | This relation cannot reuse the eli URI as it would force the class to be an eli:Expression TBD issue 43 |
has topic | Concept | 0..* | The topic of the requirement | |
has URI | xsd:anyURI | 0..* | associates a rrmv:Requirement with a unique identifier, denoted by a Uniform Resource Identifier (URI), which serves as a reference to the portion (or portions) of the text from where the Requirement is expressed and modelled. | Multiple values indicate that the union of the content of these URIs should be considered for the complete understanding of the Requirement. This property can be repeated, as different portions of the act may encode different aspects of the Requirement, for instance, the addressees may be in one article, while the temporal aspects may be in another. |
is part of | Work | 0..1 | TBD | |
part of | Expression | 0..1 | A related resource in which the described resource is physically or logically included. | TBD definition in FRBROO is circular: F8 is the inverse of F8i and in F8i is the inverse of F8. Kept for now the DCT definition. |
produces | Action | 0..* | The action that is produced by a requirement. | |
related to | Requirement | 0..* | Indicates a somehow related other document, not necessarily a legal resource. | TBD Issue 43: using this property make a Requirement an instance of an eli:Expression or eli:LegalResource |
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
after | Temporal Entity Specification | 0..* | Indicates that one temporal entity specification occurs following another one. | |
before | Temporal Entity Specification | 0..* | Indicates that one temporal entity specification precedes another one. | |
ends | Temporal Entity Specification | 0..* | Establishes that one temporal entity specification marks the conclusion of another one. | |
external event | xsd:boolean | 0..* | Indicates whether a temporal entity specification depends on events outside the regulatory framework's direct control. | |
has frequency | Frequency | 0..* | (TBD) The frequency in which the requirement is to be executed in case of repetitive mandate. | |
has function | Temporal Function | 0..* | The function the temporal infomation plays | For instance as deadline, moment of entering into force, etc. |
in | Temporal Entity Specification | 0..* | Establishes that one temporal entity specification occurs entirely within the boundaries of another temporal entity specification. | |
is unspecified | xsd:boolean | 0..* | Indicates whether a temporal aspect exists but is undefined. | TBD: definition to be improved |
meets | Temporal Entity Specification | 0..* | Indicates that one temporal entity specification directly adjoins another one without overlap, where one ends exactly when the other begins. | |
overlaps | Temporal Entity Specification | 0..* | Indicates that two temporal entities specifications share a common portion of time without either completely containing the other. | |
starts | Temporal Entity Specification | 0..* | Establishes that one temporal entity specification marks the beginning of another one. |
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
has type | Agent Type | 0..* | A kind of agent |
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
has body | Literal | 0..* | The object of the relationship is a resource that is a body of the Annotation. | TBD: card, ranges, improved definition |
has target | Resource | 0..* | The relationship between an Annotation and its Target. | TBD: need for supproperty? range? Definition is meaningless |
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
preferred label | Literal | 1..n | A preferred label of the concept. | This property can be repeated for parallel language versions of the label. |
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
has duration | xsd:duration | 0..1 | Links a duration specification to its duration value, quantifying the time periods |
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
has end | Instant Temportal Entity Specification | 0..* | Connects an interval to its concluding instant. | |
has start | Instant Temportal Entity Specification | 0..* | Connects an interval to its starting instant. |
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
cites | Legal Expression | 0..* | Citation in the text of the legislation. This may be at the legal resource or legal expression level, as required by the implementation context. This includes verbatim citation and citations in referrals. | |
embodies | Manifestation | 0..* | Relates a manifestation to the expression that it embodies. Inverse of "is_embodied_by". | |
is part of | Legal Expression | 0..* | Indicates a work in which this one is physically included. Covers the case of text included in an Official Journal, or an article included in a text. |
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
is embodied by | Legal Expression | 0..* | Relates an expression to a manifestation of that expression. |
Property | Range | Card | Definition | Usage |
---|---|---|---|---|
is realized by | Legal Expression | 0..* | Relates an expression to a work realised through that expression. Inverse of "is_realized_by". | |
is realized by | Legal Expression | 0..* | Relates an expression to a work realised through that expression. Inverse of "is_realized_by". |
Class | Definition | The datatype of language-tagged string values. | An anyURI represents an Internationalized Resource Identifier Reference (IRI). | A boolean represents the values of two-valued logic. | Duration represents a duration of time. The ·value space· of duration is a six-dimensional space where the coordinates designate the Gregorian year, month, day, hour, minute, and second components defined in § 5.5.3.2 of [[ISO8601]], respectively. | The string datatype represents character strings in XML. |
---|
skos:Concept
always indicate the usage of some controlled vocabulary.
In addition, the following controlled vocabularies MUST be used for the properties listed in the table below.
The MUST be used interpretation means that the range value space of the property is closed under the controlled vocabulary.
Validation systems SHOULD produce errors.
Property URI | Used for Class | Vocabulary name | Vocabulary URI | Usage note |
---|---|---|---|---|
rrmv:hasType | Action Result | Action Result Type | This controlled vocabulary is under construction. | |
rrmv:hasType | Role | Role Type | This controlled vocabulary is under construction. | |
rrmv:hasType | Agent | Agent Type | This controlled vocabulary is under construction. | |
rrmv:hasstatus | Action | Status | This controlled vocabulary is under construction. |
The EU Vocabularies contains a codelist for frequencies. It should be considered if this codelist is not better suited to address the usecase of the class Frequency.
Considered instances are ReportInProgress, report, actionResult, plan, standard.
Considered instances are bearer, addressee, addresser, proposer, implementor.
Considered instances are company, individual, association, publicAdminisitration, agency.
Considered instances are completed, implemented, suspended, activated, postponed, reiterated, duplicated, deleted.
Considered entitities are deadline, validity.
The example uses the ELI as unique reference for the legal document:
http://data.europa.eu/eli/reg/2016/1011/oj
.
Question to be raised is whether implementations should always use this one? Or other like the CELEX are allowed?
The fact that a legal document has many identifiers may raise implementation questions.
It is unclear if this needs to be discussed in the context of RRMV.
A Request is an interpretation of the legislation with the objective to track reporting obligations. As such it has a strong connection with the legislation, but it is not the THE legislation. If it would be the same then one should reflect on why the existing ELI machine readible annotations are not sufficient to track and followup reporting obligations. In the following we assume that this reflection has happened and that the conclusion was they are different entities with a different lifecylce, yet strongly connected.
Given the above context, it is assumed that requests are managed in systems outside the legislation. It is not needed to annotate the legation with a RRMV interpretation to be formally adopted. Therefore the structure of the identifier of Request is not determined by RRMV. For the sake of readibility the examples assume that the URI is the identifier of the Request (a Linked Data implementation).
Class | Class IRI | Property Type | Property | Property IRI |
---|---|---|---|---|
Action | http://data.europa.eu/2qy/rrmv#Action |
at time | http://data.europa.eu/2qy/rrmv#atTime |
|
Action | http://data.europa.eu/2qy/rrmv#Action |
has agent role | http://data.europa.eu/2qy/rrmv#hasAgentRole |
|
Action | http://data.europa.eu/2qy/rrmv#Action |
has next | http://data.europa.eu/2qy/rrmv#hasNext |
|
Action | http://data.europa.eu/2qy/rrmv#Action |
has result | http://data.europa.eu/2qy/rrmv#hasResult |
|
Action | http://data.europa.eu/2qy/rrmv#Action |
has status | http://data.europa.eu/2qy/rrmv#hasStatus |
|
Action Result | http://data.europa.eu/2qy/rrmv#ActionResult |
has title | http://purl.org/dc/terms/title |
|
Action Result | http://data.europa.eu/2qy/rrmv#ActionResult |
has type | http://data.europa.eu/2qy/rrmv#hasType |
|
Agent | http://data.europa.eu/2qy/rrmv#Agent |
has type | http://data.europa.eu/2qy/rrmv#hasType |
|
Agent Category | http://data.europa.eu/2qy/rrmv#AgentCategory |
|||
Agent Role | http://data.europa.eu/2qy/rrmv#AgentRole |
at time | http://data.europa.eu/2qy/rrmv#atTime |
|
Agent Role | http://data.europa.eu/2qy/rrmv#AgentRole |
for agent | http://data.europa.eu/2qy/rrmv#forAgent |
|
Agent Role | http://data.europa.eu/2qy/rrmv#AgentRole |
with role | http://data.europa.eu/2qy/rrmv#withRole |
|
Agent Type | http://data.europa.eu/2qy/rrmv#AgentType |
|||
Annotation | http://www.w3.org/ns/oa#Annotation |
has body | http://www.w3.org/ns/oa#hasBody |
|
Annotation | http://www.w3.org/ns/oa#Annotation |
has target | http://www.w3.org/ns/oa#hasTarget |
|
Concept | http://www.w3.org/2004/02/skos/core#Concept |
preferred label | http://www.w3.org/2004/02/skos/core#prefLabel |
|
Duration Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#DurationSpec |
has duration | http://data.europa.eu/2qy/rrmv#hasDuration |
|
Expression | http://data.europa.eu/eli/ontology#Expression |
|||
Frequency | http://data.europa.eu/2qy/rrmv#Frequency |
has unit | http://data.europa.eu/2qy/rrmv#hasUnit |
|
Frequency | http://data.europa.eu/2qy/rrmv#Frequency |
value | http://data.europa.eu/2qy/rrmv#value |
|
Instant Temportal Entity Specification | http://data.europa.eu/2qy/rrmv#InstantSpec |
|||
Interval Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#IntervalSpec |
has end | http://data.europa.eu/2qy/rrmv#hasEnd |
|
Interval Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#IntervalSpec |
has start | http://data.europa.eu/2qy/rrmv#hasStart |
|
Legal Expression | http://data.europa.eu/eli/ontology#LegalExpression |
cites | http://data.europa.eu/eli/ontology#cites |
|
Legal Expression | http://data.europa.eu/eli/ontology#LegalExpression |
embodies | http://data.europa.eu/eli/ontology#embodies |
|
Legal Expression | http://data.europa.eu/eli/ontology#LegalExpression |
is part of | http://data.europa.eu/eli/ontology#is_part_of |
|
Literal | http://www.w3.org/2000/01/rdf-schema#Literal |
|||
Manifestation | http://data.europa.eu/eli/ontology#Manifestation |
is embodied by | http://data.europa.eu/eli/ontology#is_embodied_by |
|
Requirement | http://data.europa.eu/2qy/rrmv#Requirement |
changes | http://data.europa.eu/2qy/rrmv#changes |
|
Requirement | http://data.europa.eu/2qy/rrmv#Requirement |
has topic | http://data.europa.eu/2qy/rrmv#hasTopic |
|
Requirement | http://data.europa.eu/2qy/rrmv#Requirement |
has URI | http://data.europa.eu/2qy/rrmv#hasURI |
|
Requirement | http://data.europa.eu/2qy/rrmv#Requirement |
is part of | http://data.europa.eu/2qy/rrmv#isPartOf |
|
Requirement | http://data.europa.eu/2qy/rrmv#Requirement |
part of | https://www.iflastandards.info/fr/frbr/frbroo#R8i |
|
Requirement | http://data.europa.eu/2qy/rrmv#Requirement |
produces | http://data.europa.eu/2qy/rrmv#produces |
|
Requirement | http://data.europa.eu/2qy/rrmv#Requirement |
related to | http://data.europa.eu/2qy/rrmv#related_to |
|
Resource | http://www.w3.org/2000/01/rdf-schema#Resource |
|||
Result Type | http://data.europa.eu/2qy/rrmv#ResultType |
|||
Role | http://data.europa.eu/2qy/rrmv#Role |
has type | http://data.europa.eu/2qy/rrmv#hasType |
|
Role Type | http://data.europa.eu/2qy/rrmv#RoleType |
|||
Status | http://data.europa.eu/2qy/rrmv#Status |
|||
Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#TemporalEntitySpec |
after | http://data.europa.eu/2qy/rrmv#after |
|
Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#TemporalEntitySpec |
before | http://data.europa.eu/2qy/rrmv#before |
|
Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#TemporalEntitySpec |
ends | http://data.europa.eu/2qy/rrmv#ends |
|
Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#TemporalEntitySpec |
external event | http://data.europa.eu/2qy/rrmv#externalEvent |
|
Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#TemporalEntitySpec |
has frequency | http://data.europa.eu/2qy/rrmv#hasFrequency |
|
Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#TemporalEntitySpec |
has function | http://data.europa.eu/2qy/rrmv#hasFunction |
|
Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#TemporalEntitySpec |
in | http://data.europa.eu/2qy/rrmv#in |
|
Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#TemporalEntitySpec |
is unspecified | http://data.europa.eu/2qy/rrmv#isUnspecified |
|
Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#TemporalEntitySpec |
meets | http://data.europa.eu/2qy/rrmv#meets |
|
Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#TemporalEntitySpec |
overlaps | http://data.europa.eu/2qy/rrmv#overlaps |
|
Temporal Entity Specification | http://data.europa.eu/2qy/rrmv#TemporalEntitySpec |
starts | http://data.europa.eu/2qy/rrmv#starts |
|
Temporal Function | http://data.europa.eu/2qy/rrmv#TemporalFunction |
|||
Work | http://data.europa.eu/eli/ontology#Work |
is realized by | http://data.europa.eu/eli/ontology#is_realized_by |
|
Work | http://data.europa.eu/eli/ontology#Work |
is realized by | http://data.europa.eu/eli/ontology#is_realized_by |