Abstract
A common ontology for modeling the interpretation of legal obligations, permissions, prohibitions, and related normative effects from legal sources.
The use cases and key features of LOMO are as follows:
**1 - Annotate prescriptive rules:** Annotate prescriptive legal provisions in existing legislation, including what actions are mandated/permitted/prohibited, by which agents, under what conditions, and with what temporal constraints. The goal of this use case is to systematically annotate prescriptive rules within legal texts with explicit deontic modalities (obligation, permission, prohibition, right), allowing detailed analysis of who must do what, when, and under what circumstances.
**2 - Model reporting obligations:** Identify and model reporting requirements including what should be reported (action results), by whom (addresser), to whom (addressee), when (temporal specifications), and in what form (result categories). This use case focuses on annotating data collection, transmission, and reporting obligations mandated by legislation.
**3 - Distinguish definitions from requirements:** Clearly separate constitutive provisions (definitions, scope provisions, category establishments) from prescriptive requirements to enable proper semantic interpretation. This addresses the fundamental distinction between provisions that establish "what counts as" something (constitutive rules) and provisions that mandate actions (prescriptive requirements).
**4 - Trace temporal validity and conditions:** Identify temporal specifications including deadlines, validity periods, starting points, frequencies, and conditional triggers that govern when requirements apply. This enables timeline analysis, identification of temporal conflicts, and support for compliance planning and monitoring.
**5 - Map agent roles and responsibilities:** Identify agents (natural persons, legal persons, organizations, public authorities) and their roles (addressee, addresser, beneficiary) in legal actions. Clear agent role modeling supports accountability tracking and delegation analysis.
**6 - Analyze digital service requirements:** Annotate digital dimensions of legal obligations to identify opportunities for digitalization, interoperability requirements, and application of once-only principles. This leverages LOMO's digital dimensions vocabulary to classify obligations by their potential for digital automation and data reuse.
**7 - Track changes in legal frameworks:** Identify modifications, amendments, and repeals that affect legal obligations across versions of legal acts. By maintaining version-aware annotations, LOMO supports impact assessment of legislative changes.
**8 - Link requirements to legal sources:** Establish precise references to legal sources using European Legislation Identifier (ELI) URIs at granular levels (article, paragraph, point, recital). This maintains traceability between structured obligation models and their authoritative legal sources.
**9 - Generate compliance checklists and workflows:** Transform structured requirement annotations into actionable compliance guidance, automated workflows, and implementation specifications. LOMO's structured representation can generate practical tools including requirement checklists, deadline calendars, and responsibility matrices.
**10 - Enable federated legal knowledge graphs:** Support the integration of legal obligation data across different jurisdictions, domains, and institutional contexts through standardized vocabularies and ontology alignment. By adhering to W3C standards (OWL, SKOS, SHACL) and European interoperability frameworks, LOMO enables distributed legal knowledge graphs.
Entities
Action
IRI: http://data.europa.eu/leg/lomo#Action
Definition
An event that must, may, or may not be performed by one or more agents, as prescribed by a prescriptive rule.
| Property |
Range |
Definition |
Action Result
IRI: http://data.europa.eu/leg/lomo#ActionResult
Definition
A specific, identifiable output, product, or outcome produced by performing an action.
Usage Note
Use ActionResult for specific result instances such as 'First annual report on interoperability in the Union'. For types or categories of results, use ActionResultType instead.
Example
First annual report on interoperability in the Union - 2025 - https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=COM:2025:860:FIN (a specific report instance published in 2025)"@en ;
Report on the application of Regulation (EU) 2024/1350 due by 12 June 2028 - https://eur-lex.europa.eu/eli/reg/2024/1350/oj/eng#art_15 (a specific time-bound report mandated by Article 15)"@en
Turtle Instantiation
ex:Result_AnnualReport2025_Interoperability rdf:type lomo:ActionResult ;
rdfs:label "First annual report on interoperability in the Union - 2025"@en ;
rdfs:comment "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=COM:2025:860:FIN"@en .
# Example from Regulation (EU) 2024/1350, Article 15
ex:Result_Report_2028_ApplicationOfRegulation rdf:type lomo:ActionResult ;
rdfs:label "Report on the application of the Regulation (EU) 2024/1350 due by 12 June 2028"@en ;
rdfs:comment "Report submitted by the Commission to the European Parliament and the Council on the application of the Regulation, including Article 9(2)(b), Member State contributions, and resettlement and humanitarian admission efforts."@en .
Action Result Type
IRI: http://data.europa.eu/leg/lomo#ActionResultType
Definition
A category or type of action results, representing a set of related ActionResults.
Usage Note
Use ActionResultType to represent classes or categories of action results, such as recurring reports or standardized outputs.
Example
Annual report on interoperability in the Union (a type of recurring report produced annually)
Certificate of activity (http://data.europa.eu/eli/reg/2018/848/oj/eng#art_35): a certificate provided by competent authorities to operators who have notified their activity and comply with the regulation
Label of Identification (http://data.europa.eu/eli/dir/2009/48/oj/eng#art_4): a label affixed on a toy containing identification information such as type, batch, serial or model number
Formal Expert Group (http://data.europa.eu/eli/reg/2019/516/oj/art_4): a formal expert group composed of Member State representatives and chaired by the Commission to provide advice
Turtle Instantiation
# Example 1: Annual interoperability report
ex:ResultType_AnnualInteroperabilityReport rdf:type lomo:ActionResultType ;
rdfs:label "Annual report on interoperability in the Union"@en ;
rdfs:comment "A recurring report produced annually to assess interoperability progress in the European Union"@en .
# Example 2: Certificate from Regulation (EU) 2018/848 Article 35(1)
ex:ResultType_Certificate rdf:type lomo:ActionResultType ;
rdfs:label "Certificate of activity"@en ;
rdfs:comment "A certificate provided by the competent authorities to any operator or group of operators that has notified its activity in accordance with Article 34(1) and complies with the Regulation (EU) 2018/848."@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2018/848/oj/eng#art_35> .
# Example 3: Label from Directive 2009/48 Article 4(5)
ex:ResultType_LabelOfIdentification rdf:type lomo:ActionResultType ;
rdfs:label "Label of Identification"@en ;
rdfs:comment "A label affixed on a toy containing a type, batch, serial or model number or other element allowing their identification"@en ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2009/48/oj/eng#art_4> .
# Example 4: Formal Expert Group from Regulation (EU) 2019/516 Article 4
ex:ResultType_FormalExpertGroup rdf:type lomo:ActionResultType ;
rdfs:label "Formal Expert Group"@en ;
rdfs:comment "A formal expert group, composed of representatives of all the Member States and chaired by a representative of the Commission, to advise the Commission."@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2019/516/oj/art_4> .
Action Result or Action Result Type
IRI: http://data.europa.eu/leg/lomo#ActionResultOrType
Definition
Abstract superclass for ActionResult (specific result instances), ActionResultType (categories of results). Used as a flexible range for properties linking to results.
| Property |
Range |
Definition |
Agent
IRI: http://data.europa.eu/leg/lomo#Agent
Definition
A specific, identifiable legal subject (natural person, legal person, or organization).
Usage Note
Use Agent for specific, named entities such as 'European Commission', 'Eurostat', 'Memorex Telex Japan Ltd'. For categories or types of entities, use AgentType instead. Both Agent and AgentType can be linked to actions via AgentRole.
Example
Specific, named entities: European Commission (an EU institution), Hitachi-Maxell (a specific Japanese company)
Turtle Instantiation
ex:Commission rdf:type lomo:Agent ;
rdfs:label "European Commission"@en ;
rdfs:comment "The European Commission - a specific institution"@en .
ex:HitachiMaxell rdf:type lomo:Agent ;
rdfs:label "Hitachi-Maxell"@en ;
rdfs:comment "A specific Japanese company"@en .
Agent Role
IRI: http://data.europa.eu/leg/lomo#AgentRole
Definition
The relationship between an agent (or agent type) and an action, specifying the function the agent plays in that action.
Usage Note
AgentRole connects Agents or AgentTypes to Actions with a specific function (RoleType). Each AgentRole instance specifies: forAgent (which agent or agent type) and withRole (what role type: addressee, addresser, beneficiary). An action may have multiple agent roles. Use Agent for specific entities and AgentType for categories.
Example
Member States acting as addresser (sender) in a notification action
Turtle Instantiation
# Using an AgentType (category)
ex:AgentRole_MS_Addresser rdf:type lomo:AgentRole ;
lomo:forAgent ex:MemberStates ;
lomo:withRole <http://publications.europa.eu/resource/authority/role/ADDRESSER> ;
rdfs:comment "Member States (as a category) send notification"@en .
| Property |
Range |
Definition |
Agent Type
IRI: http://data.europa.eu/leg/lomo#AgentType
Definition
A category or type of legal subjects (e.g., Member States, Undertakings, Importers) rather than a specific identified entity.
Usage Note
Use AgentType for categories of entities that share common characteristics, such as 'Member States', 'Small Undertakings', 'Customs Authorities', 'Importers'. For specific, named entities, use Agent instead.
Example
Categories of entities: Member States (EU Member States as a category), Small Undertakings (category of undertakings meeting size criteria)
Turtle Instantiation
ex:MemberStates rdf:type lomo:AgentType ;
rdfs:label "Member States"@en ;
rdfs:comment "EU Member States as a category - any Member State may bear this obligation"@en .
ex:SmallUndertakings rdf:type lomo:AgentType ;
rdfs:label "Small Undertakings"@en ;
rdfs:comment "Category of undertakings meeting size criteria"@en .
Agent or Agent Type
IRI: http://data.europa.eu/leg/lomo#AgentOrType
Definition
Abstract superclass for Agent (specific entities), AgentType (categories of entities). Used as the range for forAgent property in AgentRole.
Constitutive Rule
IRI: http://data.europa.eu/leg/lomo#ConstitutiveRule
Definition
A legal provision that creates, defines, or constitutes institutional facts, including legal concepts, statuses, powers, or relationships within a normative system. Constitutive rules establish 'what counts as' something in a legal context, creating the very possibility of certain institutional realities. Unlike prescriptive rules (PrescriptiveRule), constitutive rules do NOT impose obligations, permissions, or prohibitions - they describe what IS rather than what OUGHT TO BE.
Usage Note
Use for provisions that constitute institutional facts rather than regulate behaviour. Constitutive rules do not create obligations, permissions, or prohibitions - they establish the conditions under which something counts as a legal concept, status, or institutional entity. According to Searle (1979), 'Constitutive rules do not merely regulate, they create or define new forms of behaviour. The rules of football or chess, for example, create the very possibility of playing such games' (p. 33).
The foundational pattern (Searle, 1969; Grossi & Jones, 2013) is:
X counts as Y in context C
where X is a brute fact or antecedent condition, Y is the institutional fact or legal concept created, and C is the institutional/legal context.
Common linguistic patterns
Constitutive rules typically appear through:
- Explicit definitions: 'X means Y' or 'For the purposes of this Regulation, X means Y'
- Scope provisions: 'This Regulation applies to...' or 'This Directive shall not apply to...'
- Category constitutions: 'X shall be classified as Y' or 'The following count as Y: [enumeration]'
- Status constitutions: 'X is hereby established as Y' or 'X shall have the status of Y'
- Power attributions: 'X shall have the power to Y' or 'X has jurisdiction over Y'
- Legal effect provisions: 'X shall have the effect of Y' or 'Compliance with X satisfies requirement Y'
Distinguishing constitutive from prescriptive rules
The fundamental test is whether the provision creates an institutional reality or regulates behaviour.
Special cases
Provisions related to institutional organs represent an appropriate example to clarify the norms’ distinction. Provisions are constitutive when they establish the organ, define its composition, grant legal personality, or attribute institutional competences abstractly. They are prescriptive when they impose specific procedural obligations, require concrete actions, establish operational deadlines, or regulate specific procedures. The key question is: does the provision define what the organ institutionally IS or CAN DO (constitutive), or how it MUST/MAY ACT in specific situations (prescriptive)?
Mixed provisions may combine both elements. For example, GDPR Art. 9(1) states: 'Processing of personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs... shall be prohibited.' This provision implicitly constitutes the category of 'special categories of personal data' through enumeration, but its primary function is prescriptive – it prohibits processing.
Annotation guideline: When a provision is both prescriptive and constitutive, classify it as prescriptive, even if it also contains constitutive elements. Only provisions that exclusively define, constitute, or establish institutional facts without prescribing behaviour should be classified as constitutive.
Example
Explicit Definition - Legal Concept (GDPR Art. 4(1))
'personal data' means any information relating to an identified or identifiable natural person ('data subject'); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person
Explicit Definition - Category with criteria (Directive 2013/34/EU on the annual financial statements, consolidated financial statements and related reports of certain types of undertakings, Art. 2(2))
'“participating interest” means rights in the capital of other undertakings, whether or not represented by certificates, which, by creating a durable link with those undertakings, are intended to contribute to the activities of the undertaking which holds those rights. The holding of part of the capital of another undertaking is presumed to constitute a participating interest where it exceeds a percentage threshold fixed by the Member States which is lower than or equal to 20 %'
Scope Provision - Positive Applicability Directive 2014/65/EU on markets in financial instruments (consolidated version), Art. 1(1)
'This Directive shall apply to investment firms, market operators, and third-country firms providing investment services or performing investment activities through the establishment of a branch in the Union'
Scope Provision - Negative Exclusion (GDPR Art. 2(2)(a))
'This Regulation does not apply to the processing of personal data in the course of an activity which falls outside the scope of Union law'
Status Constitution - Legal Personality
(Regulation 2016/794/EU on the European Union Agency for Law Enforcement Cooperation (Europol) (consolidated), Art.62)
'Europol shall be an agency of the Union. It shall have legal personality'
Organ Establishment (GDPR Art.68(1))
'The European Data Protection Board (the ‘Board’) is hereby established as a body of the Union and shall have legal personality'
Composition Definition (Regulation (EU) No 910/2014 – eIDAS (consolidated version), Art.46e(2))
'The Cooperation Group shall be composed of representatives appointed by the Member States and of the Commission. The Cooperation Group shall be chaired by the Commission.'
Legal Effect Constitution (Directive 93/13/EEC - Unfair Contract Terms, Art. 6(1))
'Member States shall lay down that unfair terms used in a contract concluded with a consumer by a seller or supplier shall, as provided for under their national law, not be binding on the consumer and that the contract shall continue to bind the parties upon those terms if it is capable of continuing in existence without the unfair terms'
Qualification/Classification (Regulation (EC) No 178/2002 - General Food Law (consolidated), Art. 3(1))
'‘food law’ means the laws, regulations and administrative provisions governing food in general, and food safety in particular, whether at Community or national level; it covers any stage of production, processing and distribution of food, and also of feed produced for, or fed to, food-producing animals;'
Territorial Applicability (Rome I Regulation (EC) No 593/2008, Art. 2)
'Any law specified by this Regulation shall be applied whether or not it is the law of a Member State'
Temporal Constitution - Entry into Force (GDPR Art. 99(2))
'It shall apply from 25 May 2018'
See also
- Rawls, J. (1955). 'Two Concepts of Rules.' The Philosophical Review, 64(1), 3-32. doi:10.2307/2182230
- Austin, J.L. (1962). How to Do Things with Words (2nd ed.). Oxford University Press.
- Searle, J.R. (1969). Speech Acts: An Essay in the Philosophy of Language. Cambridge University Press.
- Searle, J.R. (1979). 'A Taxonomy of Illocutionary Acts.' In Expression and Meaning: Studies in the Theory of Speech Acts (pp. 1-29). Cambridge University Press. (1st ed. 1975)
- Conte, A.G. (1995). 'Regola costitutiva in Wittgenstein.' In Filosofia del linguaggio normativo. I (pp. 237-254). Torino. (1st ed. 1981)
- Guastini, R. (1986). 'Six Concepts of Constitutive Rule.' In T. Eckhoff, L.M. Friedman, & J. Uusitalo (Eds.), Vernunft und Erfahrung im Rechtsdenken der Gegenwart (Proceedings of the 11th World Congress of IVR, Helsinki 1983) (pp. 261-269). Rechtstheorie Beiheft 10.
- Roversi, C. (2012). Costituire: Uno Studio di Ontologia Giuridica. Giappichelli, Turin.
- Ceci, M., et al. (2015). 'Legal Patterns for Different Constitutive Rules.' In Proceedings of the International Workshop on AI Approaches to the Complexity of Legal Systems (pp. [pages]). Springer International Publishing, Cham.
- Biagioli, C., & Sartor, G. (1993). 'Regole e atti linguistici nel discorso normativo: Studi per un modello informatico-giuridico.' In Nuovi modelli formali del diritto. Il ragionamento giuridico nell'informatica e nell'intelligenza artificiale. CLUESP.
- Boella, G., & van der Torre, L. (2004). 'Regulative and Constitutive Norms in Normative Multiagent Systems.' KR, 4, 255-265.
- Grossi, D., Meyer, J.J.C., & Dignum, F. (2006). 'Classificatory Aspects of Counts-As: An Analysis in Modal Logic.' Journal of Logic and Computation, 16(5), 613-643.
- Grossi, D., & Jones, A.J.I. (2013). 'Constitutive Norms and Counts-As Conditionals.' In D. Gabbay, J. Horty, X. Parent, R. van der Meyden, & L. van der Torre (Eds.), Handbook of Deontic Logic and Normative Systems. College Publications, Milton Keynes.
- Hohfeld, W.N. (1913). 'Some Fundamental Legal Conceptions as Applied in Judicial Reasoning.' Yale Law Journal, 16-59.
Definition
IRI: http://data.europa.eu/leg/lomo#Definition
Definition
A legal definition of a term, concept, or agent role used within a legal source. Definition is a specialized kind of ConstitutiveRule that establishes the meaning of terms within a legal context. Like all constitutive rules, definitions do not prescribe actions - they constitute the semantic foundation upon which prescriptive rules operate.
Usage Note
Definitions in legal texts can be classified as semantic (triadic) or synctactic (dyadic):
Semantic definitions establish meaning through three components:
1. Definiendum (hasDefiniendum): The term being defined
2. Definiens (hasDefiniens): The defining phrase or description
3. Referent (hasReferent): The real-world entities to which the term refers
Example: 'public-interest entities' means undertakings whose securities are traded on regulated markets...
- Definiendum: 'public-interest entities'
- Definiens: the enumerated categories
- Referent: actual undertakings meeting those criteria
Synctactic definitions only relate symbols without explicit referent:
Example: 'related party' has the same meaning as in IAS/IFRS
- Definiendum: 'related party'
- No definiens
- No explicit referent (inherited from the referenced standard)
Use equivalentDefinition to link a synctactic definition to an equivalent semantic definition.
Turtle Instantiation
ex:Def_PublicInterestEntity rdf:type lomo:Definition ;
lomo:hasDefiniendum "public-interest entities"@en ;
lomo:hasDefiniens "undertakings within the scope of Article 1 which are..."@en ;
lomo:isSemanticDefinition "true"^^xsd:boolean ;
lomo:establishedIn <https://eur-lex.europa.eu/eli/dir/2013/34/oj/art_2/point_1> .
ex:Def_RelatedParty rdf:type lomo:Definition ;
lomo:hasDefiniendum "related party"@en ;
# "has the same meaning as in IAS 24 (Related Party Disclosures)"
lomo:equivalentDefinition [
a lomo:Definition ;
lomo:establishedInResource <https://www.ifrs.org/issued-standards/ias-24-related-party-disclosures/> .
]
.
ex:Def_SmallUndertakings rdf:type lomo:Definition ;
lomo:hasDefiniendum "small undertakings"@en ;
lomo:hasDefiniens "undertakings which on their balance sheet dates do not exceed the limits of at least two of the three following criteria:..."@en ;
lomo:isSemanticDefinition "true"^^xsd:boolean ;
lomo:establishedIn <https://eur-lex.europa.eu/eli/dir/2013/34/oj/art_2/point_2> .
| Property |
Range |
Definition |
Implementation and Oversight Rule
IRI: http://data.europa.eu/leg/lomo#ImplementationAndOversightRule
Definition
Legal provisions that establish the administrative, procedural, and institutional framework required for Member States, public institutions or bodies to transpose, operationalize, monitor, support or enforce substantive rules.
Usage Note
This class refers to the mechanics of governance and the policing of the law. It focuses on the obligations of authorities to establish supervisory bodies, define powers of inspection, and implement sanctioning regimes rather than the conduct of the regulated subjects.
Example
Member States shall provide for effective systems of public oversight for statutory auditors and audit entities (Accounting Directive 2013/34/EU, Art. 32 on the oversight of auditing requirements).
Member States shall bring into force the laws, regulations and administrative provisions necessary to comply with this Directive by 20 July 2015. They shall immediately inform the Commission thereof (Accounting Directive 2013/34/EU, Art. 53 on the transposition).
The power to adopt delegated acts referred to in Article XX, YY shall be conferred on the Commission for a period of five years from 17 July 2012. The Commission shall draw up a report in respect of the delegation of power not later than nine months before the end of the five-year period. (Regulation (EU) No 528/2012, Art. 83 on the exercice of the delegation)
Institutional Rule
IRI: http://data.europa.eu/leg/lomo#InstitutionalRule
Definition
A constitutive rule that establishes institutional entities, constitutes legal statuses, attributes powers or competences, or defines the composition of organs within a normative system.
Usage Note
Use for provisions whose primary function is to bring into existence an institutional entity, endow it with legal personality or status, define its composition, attribute powers or competences, or constitute the legal consequences attaching to certain facts or acts.
Institutional rules create the legal-institutional structures of the legal system. They establish bodies, roles, and capacities that exist only by virtue of legal norms, without prescribing how actors must or may behave.
Institutional rules encompass organ establishment ("is hereby established"), status constitution (legal personality), composition provisions, power attribution, and legal effect constitution.
Power attribution provisions vest entities with institutional capacity to perform legal acts — they constitute the power itself, not regulate its exercise.
Legal effect provisions attach specific institutional consequences to facts or acts — for example, a provision stating that unfair terms are not binding creates the legal consequence of invalidity.
The distinction from prescriptive rules requires careful consideration regarding competences. A provision is institutional when it constitutes what an organ is, what legal qualities it has, or what it can do as institutional capacity. It becomes prescriptive when it regulates how the organ must or may act in specific circumstances.
Example: 'X shall have the power to impose fines' is institutional; 'X shall impose a fine not exceeding 20,000,000 EUR' upon certain violations is prescriptive.
Common linguistic patterns:
- Establishment formulas: 'X is hereby established as Y'
- Status attributions: 'X shall have legal personality' or 'X shall be a body of the Union'
- Composition provisions: 'X shall be composed of'
- Power/competence attributions: 'X shall have the power to Y' or 'X may [institutional action]' (institutional capacity, not behavioural permission)
- Legal effect constitutions: 'X shall not be binding on Y' or 'X shall have the effect of Y'
Example
Legal personality — Regulation (EU) 2016/794 (Europol Regulation), Art. 1
A European Union Agency for Law Enforcement Cooperation (Europol) is hereby established with a view to supporting cooperation among law enforcement authorities in the Union.
Role definition — Regulation (EU) No 910/2014 (eIDAS), Art. 17(3)
The role of the supervisory body shall be the following: [...]
Mixed institutional content — Regulation (EU) 2024/903 (Interoperable Europe Act), Art. 15
Article 15 establishes the Board (para. 1), defines its composition (para. 2), attributes the Chair and observer-status powers (para. 4), constitutes the decision-making mechanism (para. 4), and lists the Board's tasks and competences (para. 5).
See also
- Searle, J.R. (1969). Speech Acts: An Essay in the Philosophy of Language. Cambridge University Press.
- Grossi, D., & Jones, A.J.I. (2013). 'Constitutive Norms and Counts-As Conditionals.' In Handbook of Deontic Logic and Normative Systems. College Publications.
- Hohfeld, W.N. (1913). 'Some Fundamental Legal Conceptions as Applied in Judicial Reasoning.' Yale Law Journal, 1659.
- Roversi, C. (2012). Costituire: Uno Studio di Ontologia Giuridica. Giappichelli, Turin.
- Boella, G., & van der Torre, L. (2004). 'Regulative and Constitutive Norms in Normative Multiagent Systems.' KR, 4, 255-265.
- Ceci, M., et al. (2015). 'Legal Patterns for Different Constitutive Rules.' Springer.
Legal Rule
IRI: http://data.europa.eu/leg/lomo#LegalRule
Definition
The intellectual content of a rule.
Usage Note
Use LegalRule as the base class for any legal norm extracted from a legal source.
The intellectual content of a rule is its legal interpretation: the juridical meaning attributed to a provision through legal analysis, distinct from its literal textual expression. This allows the same legal concept to be represented even when expressed differently across multiple legal instruments.
Every LegalRule must be linked to its legal source(s) via lomo:establishedIn, which points to eli:Work URIs. A single LegalRule instance may have multiple lomo:establishedIn properties pointing to different legal sources when the rule is derived from multiple provisions that together establish its meaning.
For rules with clear normative function, prefer the specialized subclasses: PrescriptiveRule or ConstitutiveRule.
Example
GDPR Article 1 on Subject-matter and objectives (<http://data.europa.eu/eli/reg/2016/679/art_1>): a scope provision that establishes the purpose and scope of the regulation
eIDAS Regulation Article 3 on Definitions (<http://data.europa.eu/eli/reg/2014/910/art_3>): a provision containing foundational definitions that structure the legal framework
Directive (EU) 2019/1024 Article 5 (<http://data.europa.eu/eli/dir/2019/1024/art_5>): a complex provision combining both definitional and procedural elements
A rule replicated across Regulation (EU) 2018/1148 and its amendment Regulation (EU) 2023/1234, requiring multiple lomo:establishedIn links
Turtle Instantiation
# Example 1: GDPR Article 1 as a LegalRule
ex:Rule_GDPR_Art1 rdf:type lomo:LegalRule ;
rdfs:label "GDPR Subject-matter and objectives"@en ;
rdfs:comment "Scope provision establishing the purpose and scope of the General Data Protection Regulation"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2016/679/art_1> .
# Example 2: Rule with multiple legal sources
ex:Rule_Replicated rdf:type lomo:LegalRule ;
rdfs:label "Replicated compliance rule"@en ;
lomo:legalText "The operator shall ensure compliance with the requirements..."@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2018/1148/art_10> ,
<http://data.europa.eu/eli/reg/2023/1234/art_8> .
# Example 3: Open Data Directive Article 5
ex:Rule_OpenData_Art5 rdf:type lomo:LegalRule ;
rdfs:label "Open Data Directive Article 5"@en ;
rdfs:comment "Complex provision combining definitional and procedural elements"@en ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2019/1024/art_5> .
# Example 4: eIDAS Definitions
ex:Rule_eIDAS_Art3 rdf:type lomo:LegalRule ;
rdfs:label "eIDAS Definitions"@en ;
rdfs:comment "Foundational definitions structuring the eIDAS legal framework"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2014/910/art_3> .
| Property |
Range |
Definition |
Prescriptive Rule
IRI: http://data.europa.eu/leg/lomo#PrescriptiveRule
Definition
A legal rule extracted from a legal source that mandates, permits, or prohibits actions. PrescriptiveRule is restricted to norms with deontic modalities (obligation, permission, prohibition, right) that prescribe behaviour. For legal rules that establish facts, definitions, or institutional realities without prescribing actions, use ConstitutiveRule instead.
Usage Note
PrescriptiveRule is the core class for modeling rules that mandate, permit, or prohibit actions.
Each :PrescriptiveRule should specify:
1. hasDeonticModality: The type of normative effect (Obligation, Permission, Prohibition, Right)
2. hasRequirementType: The functional category (Substantive, Procedural, Implementation, Penalty, etc.)
3. legalText: The verbatim text from the legal source
5. produces: The action(s) mandated, permitted, or prohibited by the rule
Optional properties include: hasCondition (for conditional requirements), usesDefinition (for requirements making use of terms).
For provisions that establish facts, definitions, or institutional realities without prescribing behaviour, use ConstitutiveRule.
Example
Fisheries regulation — data requirements (Article 4(1)): A requirement specifying detailed topics, transmission frequencies, and other data collection parameters.
Financial reporting — publication obligation (Article 30(1)): A requirement for undertakings to publish annual financial statements within 12 months after the balance sheet date.
Vehicle registration — temporary submission requirement (Article 10(2)): A requirement for submission of registration certificates when re-registering vehicles from another Member State.
Turtle Instantiation
# 1) Fisheries regulation — data requirements (Article 4(1))
<http://data.europa.eu/lrmo/lfds-fisheries#Requirement_Art4_Par1> rdf:type lomo:PrescriptiveRule ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Obligation> ;
lomo:hasRequirementType <http://publications.europa.eu/resource/dataset/administrative-obligation/c_80214a02> ;
lomo:produces <http://data.europa.eu/lrmo/lfds-fisheries#Action_Art4_DataCollection> , <http://data.europa.eu/lrmo/lfds-fisheries#Action_Art4_DataTransmission> ;
lomo:legalText "The detailed topics, transmission frequencies, reference periods and the dimensions related to sensitive species, organic production and regional breakdown on fisheries and aquaculture statistics referred to in Article 1, shall be as set out in the Annex."@en ;
lomo:establishedIn <https://data.europa.eu/eli/dl/proc/2025/96/cod/doc/com/COM_2025_425/FINAL/eng/art_4/par_1> .
# 2) Financial reporting — publication obligation (Article 30(1))
<http://data.europa.eu/lrmo/financial-reporting#Requirement_Art30_Par1_PublicationObligation> rdf:type lomo:PrescriptiveRule ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Obligation> ;
lomo:hasRequirementType <http://publications.europa.eu/resource/dataset/administrative-obligation/c_80214a02> ;
lomo:produces <http://data.europa.eu/lrmo/financial-reporting#Action_Art30_Publish> ;
lomo:legalText "Member States shall ensure that undertakings publish within a reasonable period of time, which shall not exceed 12 months after the balance sheet date, the duly approved annual financial statements and the management report, together with the opinion submitted by the statutory auditor or audit firm."@en ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2013/34/oj/art_30/par_1> .
# 3) Vehicle registration — temporary submission requirement (Article 10(2))
<http://data.europa.eu/lrmo/vehicle-registration#Requirement_Art10_Par2> rdf:type lomo:PrescriptiveRule ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Obligation> ;
lomo:hasRequirementType <http://publications.europa.eu/resource/dataset/administrative-obligation/c_39b9f824> ;
lomo:legalText "Until [date of entry into force + 4 years] the competent authorities shall require the submission of only Part I of the physical registration certificate when re-registering a vehicle previously registered in another Member State. Until that date, they may also accept the presentation of a mobile registration certificate, if any."@en ;
lomo:establishedIn <https://data.europa.eu/eli/dl/proc/2025/96/cod/doc/com/COM_2025_179/FINAL/art_10/par_2> .
| Property |
Range |
Definition |
Scope Rule
IRI: http://data.europa.eu/leg/lomo#ScopeRule
Definition
A constitutive rule that determines the material, actor-related, or territorial scope of application of a legal act or of one of its provisions, specifying what subject-matters, activities, entities, or territories fall within, or are excluded from, its regulatory reach. Scope rules constitute the boundaries of the normative space within which the substantive provisions operate, without themselves prescribing conduct.
Usage Note
Use for provisions or act-level clauses whose primary function is to delimit the scope of application of a legal instrument along its material dimension (what activities or situations are covered), actor-related dimension (which actors or entities are addressed), or territorial dimension (where the instrument applies).
These provisions are typically located in the opening articles of EU legislative acts (commonly Articles 1-3), often under headings such as 'Subject matter and scope' or 'Scope'.
Scope rules may be formulated positively (specifying what the instrument covers) or negatively (excluding certain areas, activities, or entities). Together, positive and negative scope provisions jointly constitute the regulatory perimeter of the instrument. Territorial scope provisions — including EU provisions extending regulatory effects beyond Member State borders — likewise constitute boundaries of the normative space rather than prescribing behaviour.
Scope provisions employing 'shall apply to' may resemble prescriptive language, but they do not regulate behaviour: they constitute the domain within which prescriptive and other constitutive rules operate. 'This Regulation does not apply to' does not prohibit anything — it constitutes a boundary.
Distinguishing scope rules from other constitutive rules: The central test is whether the provision determines the reach of the instrument — to what, to whom, or where it applies. Defining the concept of 'investment firm' constitutes a Definition; specifying that 'this Directive applies to investment firms' is a scope rule. If the provision determines when the instrument applies, it is a temporal applicability rule (TemporalRule).
Common linguistic patterns:
- Positive material scope: 'This Regulation/Directive applies to' or 'This Regulation covers'
- Negative exclusions: 'This Regulation does not apply to' or 'This Directive shall not apply to'
- Actor-related scope: 'This Regulation applies to providers' or 'The addressees of this Directive are'
- Territorial scope: 'shall be applied whether or not it is the law of a Member State'
Example
Subject matter — Regulation (EU) No 910/2014 (eIDAS), Art. 1
This Regulation: (a) lays down the conditions under which Member States recognize electronic identification means of natural and legal persons falling under a notified electronic identification scheme of another Member State; (b) lays down rules for trust services, in particular for electronic transactions; and (c) establishes a legal framework for electronic signatures, electronic seals, electronic time stamps, electronic documents, electronic registered delivery services and certificate services for website authentication.
Positive material and actor-related scope — eIDAS, Art. 2(1)
This Regulation applies to electronic identification schemes that have been notified by a Member State, and to trust service providers that are established in the Union.
Negative exclusion — eIDAS, Art. 2(2)
This Regulation does not apply to the provision of trust services that are used exclusively within closed systems resulting from national law or from agreements between a defined set of participants.
Territorial scope — Regulation (EC) No 593/2008 (Rome I), Art. 2
Any law specified by this Regulation shall be applied whether or not it is the law of a Member State.
See also
- Rawls, J. (1955). 'Two Concepts of Rules.' The Philosophical Review, 64(1), 3-32.
- Grossi, D., & Jones, A.J.I. (2013). 'Constitutive Norms and Counts-As Conditionals.' In Handbook of Deontic Logic and Normative Systems. College Publications.
- Guastini, R. (1986). 'Six Concepts of Constitutive Rule.' In T. Eckhoff, L.M. Friedman, & J. Uusitalo (Eds.), Vernunft und Erfahrung im Rechtsdenken der Gegenwart (Proceedings of the 11th World Congress of IVR, Helsinki 1983) (pp. 261-269). Rechtstheorie Beiheft 10.
Substantive Rule
IRI: http://data.europa.eu/leg/lomo#SubstantiveRule
Definition
Legal provisions that define the primary rights, duties, and obligations of the regulated subjects, such as individuals, businesses and public administrations, by establishing mandatory standards of conduct or essential requirements.
Usage Note
This class refers to the core prescriptive content of an act. It focuses on the mandatory actions that parties must perform to achieve policy objectives, governing the direct relationship between the state and the businesses/individuals or between private parties.
Example
Where environmental damage has occurred the operator shall, without delay, inform the competent authority of all relevant aspects of the situation and take: (a) all practicable steps to immediately control (...) the relevant contaminants (...) and (b) the necessary remedial measures, in accordance with Article 7. (Directive 2004/35/EC, Art. 6 on remedial actions)
In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the supervisory authority competent in accordance with Article 55, unless (...) (Regulation (EU) 2016/679 (GDPR) Art. 33 on Notification of a personal data breach)
Member States shall ensure that undertakings publish within a reasonable period of time, which shall not exceed 12 months after the balance sheet date, the duly approved annual financial statements and the management report, together with the opinion submitted by the statutory auditor or audit firm (...) (Directive 2013/34/EU Art. 30 on General publication requirements of financial statements)
Temporal Specification
IRI: http://data.europa.eu/leg/lomo#TemporalSpecification
Definition
A specification of temporal information, including points in time, periods, durations, and temporal relationships.
Usage Note
Use temporal characteristics (instant, duration, frequency, repetitions, temporalLabel) as direct properties. Link temporal specifications via temporal relations (before, after, etc.). Specify function via hasFunction (deadline, validity, startingPoint) when used in prescriptive rules or actions.
| Property |
Range |
Definition |
Object Properties
after
IRI: http://data.europa.eu/leg/lomo#after
Definition
Indicates that one temporal specification occurs subsequent to the end of another temporal specification.
at time
IRI: http://data.europa.eu/leg/lomo#atTime
Definition
A generic property linking any entity to a temporal specification, indicating when an event occurs, a rule applies, or an action must be performed.
Usage Note
The atTime property serves as a generic property linking any kind of entity to a temporal specification. It can be used for Rules (to specify when a requirement is applicable or triggers), Actions (to specify when an action must/may occur), Results, and other classes in need of temporal modeling. The domain is intentionally unspecified to allow flexibility across different entity types.
The actual role played by the TemporalSpecification (whether it is a deadline, a trigger, a starting point, etc.) is indicated by the hasFunction property on the TemporalSpecification itself. This allows for precise modeling of temporal constraints and events.
Example patterns:
1. Linking a PrescriptiveRule to a triggering event:
PrescriptiveRule :atTime TemporalSpecification .
TemporalSpecification :temporalLabel "label of the event"@en .
TemporalSpecification :hasFunction :trigger .
2. Linking an Action to a deadline:
Action :atTime TemporalSpecification .
TemporalSpecification :instant "2026-04-12"^^xsd:date .
TemporalSpecification :hasFunction :deadline .
Example
- In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the supervisory authority competent in accordance with Article 55, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons. Where the notification to the supervisory authority is not made within 72 hours, it shall be accompanied by reasons for the delay. - http://data.europa.eu/eli/reg/2016/679/art_33/par_1/2016-05-04
Turtle Instantiation
# "In case of a personal data breach, the controller shall..."
ex:NotifySupervisoryAuthority a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:temporalLabel "personal data breach"@en ;
lomo:hasFunction <http://data.europa.eu/leg/temporal-function/trigger> ;
]
before
IRI: http://data.europa.eu/leg/lomo#before
Definition
Indicates that one temporal specification occurs prior to the start of another temporal specification.
defines
IRI: http://data.europa.eu/leg/lomo#defines
Definition
Links a definition to the concept, term, or agent it defines.
derogates from
IRI: http://data.europa.eu/leg/lomo#derogatesFrom
Definition
Relates a legal rule to another rule from which it departs, by establishing an incompatible normative qualification with that of the latter for a defined range of cases. The derogating rule either substitutes the normative qualification of the derogated rule (substitutive derogation) or suspends its application without producing a new qualification (blocking derogation), and may do so on a mandatory or discretionary basis.
Usage Note
Use derogates when two rules, applied jointly to the same case, would yield conflicting normative qualifications, and the legal system resolves the conflict in favour of the derogating rule. Unlike specifies, derogation involves genuine deontic conflict between the two rules in at least some cases falling within their joint scope.
Key characteristics:
- The derogating rule overrides or suspends the application of the derogated rule
- There is a deontic conflict between the two rules for some cases
- The derogating rule may be more specific (substitutive derogation) or merely blocking
- The relationship is typically defined by law to indicate which rule takes precedence
Two types of derogation:
1. Substitutive derogation: The derogating rule replaces the normative qualification
2. Blocking derogation: The derogating rule suspends application without providing a new qualification
Example: A national law requires all companies to submit annual financial reports. However, micro-enterprises are exempt from this obligation. The exemption rule derogates from the general reporting requirement.
Example
Directive 2013/34/EU Article 1(2)(a) requires all undertakings to prepare financial statements, but Article 1a provides a derogation for micro-entities. The micro-entity derogation rule derogates from the general financial reporting requirement by suspending it (blocking derogation).
GDPR Article 6(1) establishes consent as a lawful basis for processing personal data. However, Article 6(1)(b) establishes performance of a contract as an alternative lawful basis that can substitute for consent in specific circumstances — a substitutive derogation.
Regulation (EU) 2019/1242 Article 4 requires CO₂ monitoring for heavy-duty vehicles, but Article 5(4) provides a derogation for vehicles of certain categories or with specific characteristics from the general monitoring obligation.
Turtle Instantiation
# Example 1: Directive 2013/34/EU - Micro-entity exemption from financial reporting
ex:Rule_Dir2013_34_Art1_GeneralObligation a lomo:PrescriptiveRule ;
rdfs:label "Directive 2013/34/EU Article 1(2)(a): General requirement for financial statements"@en ;
rdfs:comment "All undertakings shall prepare annual financial statements"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Obligation> ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2013/34/oj/art_1> .
ex:Rule_Dir2013_34_Art1a_MicroEntityDerogation a lomo:PrescriptiveRule ;
rdfs:label "Directive 2013/34/EU Article 1a: Derogation for micro-entities"@en ;
rdfs:comment "Micro-entities are exempt from the requirements of Articles 4 to 8 and 19a"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Permission> ;
lomo:derogatesFrom ex:Rule_Dir2013_34_Art1_GeneralObligation ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2013/34/oj/art_1a> .
# Example 2: GDPR - Alternative lawful basis derogating from consent requirement
ex:Rule_GDPR_Art6_1_a_Consent a lomo:PrescriptiveRule ;
rdfs:label "GDPR Article 6(1)(a): Lawful basis - Consent"@en ;
rdfs:comment "Processing shall be lawful only if and to the extent that consent has been given"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Permission> ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2016/679/art_6/par_1/point_a> .
ex:Rule_GDPR_Art6_1_b_ContractPerformance a lomo:PrescriptiveRule ;
rdfs:label "GDPR Article 6(1)(b): Lawful basis - Contract performance"@en ;
rdfs:comment "Processing is necessary for the performance of a contract to which the data subject is party"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Permission> ;
lomo:derogatesFrom ex:Rule_GDPR_Art6_1_a_Consent ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2016/679/art_6/par_1/point_b> ;
rdfs:comment "Article 6(1)(b) provides an alternative lawful basis that substitutes consent when contract performance is necessary (substitutive derogation)" .
# Example 3: CO₂ Regulation - Category-based derogation
ex:Rule_EU2019_1242_Art4_CO2Monitoring a lomo:SubstantiveRule ;
rdfs:label "Regulation (EU) 2019/1242 Article 4: CO₂ monitoring"@en ;
rdfs:comment "Manufacturers shall monitor CO₂ emissions and fuel consumption"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Obligation> ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2019/1242/art_4> .
ex:Rule_EU2019_1242_Art5_4_VehicleDerogation a lomo:PrescriptiveRule ;
rdfs:label "Regulation (EU) 2019/1242 Article 5(4): Derogation from monitoring for certain vehicles"@en ;
rdfs:comment "The monitoring requirements of Article 4 shall not apply to vehicles of certain categories or with specific characteristics"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Permission> ;
lomo:derogatesFrom ex:Rule_EU2019_1242_Art4_CO2Monitoring ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2019/1242/art_5/par_4> ;
rdfs:comment "Article 5(4) provides a blocking derogation that suspends the general monitoring obligation for specified vehicle categories" .
equivalent definition
IRI: http://data.europa.eu/leg/lomo#equivalentDefinition
Definition
A link between two definitions, to indicate that the subject definition is declared equivalent to the object definition.
Turtle Instantiation
ex:Def_RelatedParty rdf:type lomo:Definition ;
lomo:hasDefiniendum "related party"@en ;
# "has the same meaning as in IAS 24 (Related Party Disclosures)"
lomo:equivalentDefinition [
a lomo:Definition ;
lomo:establishedInResource <https://www.ifrs.org/issued-standards/ias-24-related-party-disclosures/> .
]
established in
IRI: http://data.europa.eu/leg/lomo#establishedIn
Definition
Links an entity to the source of legal information used as reference
Usage Note
This property can be used to link any entity to the resource, or the subdivision of a legal resource containing the information used as reference for the interpretation of the legal sources in LOMO
Example
The 'General safety requirement' in EU legislation is established in Article 5 of Regulation 2023/988 (http://data.europa.eu/eli/reg/2023/988/art_5/oj)
Turtle Instantiation
ex:GeneralSafetyRule a lomo:LegalRule ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2023/988/art_5/oj> .
finished by
IRI: http://data.europa.eu/leg/lomo#finishedBy
Definition
Indicates that one temporal specification has its end point at the same moment as another (inverse of finishes).
Usage Note
This property is context-independent and can be used to model temporal relationships in legal rules, actions, and other entities.
Example
A deadline for submitting a report finishes by the end of the fiscal year.
Turtle Instantiation
# Example 1: Deadline finishes by the end of a period
ex:Deadline_SubmitReport a lomo:TemporalSpecification ;
lomo:instant "2025-12-31"^^xsd:date ;
lomo:hasFunction <http://data.europa.eu/leg/temporal-function/deadline> ;
lomo:finishedBy ex:FiscalYear2025 .
ex:FiscalYear2025 a lomo:TemporalSpecification ;
lomo:instant "2025-12-31"^^xsd:date ;
rdfs:label "End of Fiscal Year 2025"@en .
# Example 2: Action finishes by the end of another action
ex:Action_SubmitReport a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:finishedBy ex:Action_ReviewReport ;
] .
ex:Action_ReviewReport a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:instant "2025-12-31"^^xsd:date ;
] .
finishes
IRI: http://data.europa.eu/leg/lomo#finishes
Definition
Indicates that one temporal specification ends at the same moment as another.
Usage Note
This property is context-independent and can be used to model temporal relationships in legal rules, actions, and other entities.
Example
A fiscal year finishes at the same moment as the deadline for submitting a report.
Turtle Instantiation
# Example 1: Fiscal year finishes at the same moment as a deadline
ex:FiscalYear2025 a lomo:TemporalSpecification ;
lomo:instant "2025-12-31"^^xsd:date ;
rdfs:label "End of Fiscal Year 2025"@en ;
lomo:finishes ex:Deadline_SubmitReport .
ex:Deadline_SubmitReport a lomo:TemporalSpecification ;
lomo:instant "2025-12-31"^^xsd:date ;
lomo:hasFunction <http://data.europa.eu/leg/temporal-function/deadline> .
# Example 2: One action finishes at the same moment as another action starts
ex:Action_ReviewReport a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:finishes ex:Action_SubmitReport ;
] .
ex:Action_SubmitReport a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:instant "2025-12-31"^^xsd:date ;
] .
for agent
IRI: http://data.europa.eu/leg/lomo#forAgent
Definition
Links an AgentRole to the specific Agent or AgentType performing that role.
Usage Note
Use this property to specify the agent or agent type associated with a particular role in an action. It can reference either a specific Agent (e.g., European Commission) or an AgentType (e.g., Member States).
Example
An AgentRole for a specific Agent (e.g., European Commission) or an AgentType (e.g., Member States).
Turtle Instantiation
# Example 1: Linking an AgentRole to a specific Agent
ex:AgentRole_Commission_Addresser rdf:type lomo:AgentRole ;
lomo:forAgent ex:Commission ;
lomo:withRole lomo:addresser .
ex:Commission rdf:type lomo:Agent ;
rdfs:label "European Commission"@en .
# Example 2: Linking an AgentRole to an AgentType
ex:AgentRole_MS_Addresser rdf:type lomo:AgentRole ;
lomo:forAgent ex:MemberStates ;
lomo:withRole lomo:addresser .
ex:MemberStates rdf:type lomo:AgentType ;
rdfs:label "Member States"@en .
has agent role
IRI: http://data.europa.eu/leg/lomo#hasAgentRole
Definition
Relates an action to an agent role specifying an agent's participation.
Usage Note
Every Action should have at least one AgentRole specifying who participates. Common role types: addressee (recipient of communication), addresser (sender), beneficiary (who benefits). An action may have multiple agent roles for different participants.
Example
Member States informing the Commission about a change in national legislation.
Turtle Instantiation
# Example 1: Action with multiple agent roles
ex:Action_InformCommission lomo:hasAgentRole ex:AgentRole_MS_Informer , ex:AgentRole_Commission_Informed .
ex:AgentRole_MS_Informer rdf:type lomo:AgentRole ;
lomo:forAgent ex:MemberStates ;
lomo:withRole lomo:addresser .
ex:AgentRole_Commission_Informed rdf:type lomo:AgentRole ;
lomo:forAgent ex:Commission ;
lomo:withRole lomo:addressee .
# Example 2: Action with a single agent role
ex:Action_PublishReport rdf:type lomo:Action ;
lomo:hasAgentRole ex:AgentRole_Commission_Publisher .
ex:AgentRole_Commission_Publisher rdf:type lomo:AgentRole ;
lomo:forAgent ex:Commission ;
lomo:withRole lomo:addresser .
has category
IRI: http://data.europa.eu/leg/lomo#hasCategory
Definition
Links a requirement or action to a digital dimension category from the Digital Dimensions scheme.
Usage Note
Used to classify requirements by digital dimensions categories (Data, Digital Public Service, Digital Solutions). Multiple categories can be assigned. Categories are defined in the DigitalDimensionsScheme.
Example
A requirement for data collection and transmission can be classified under both Data and Digital Public Service categories.
Turtle Instantiation
ex:Requirement_Art4_DataRequirements lomo:hasCategory <http://data.europa.eu/leg/digital-dimensions/Data> , <http://data.europa.eu/leg/digital-dimensions/DigitalPublicService> .
ex:Requirement_Art5_ObservationData lomo:hasCategory <http://data.europa.eu/leg/digital-dimensions/Observation> .
See also
has deontic modality
IRI: http://data.europa.eu/leg/lomo#hasDeonticModality
Definition
Relates a prescriptive rule to its deontic character (obligation, permission, prohibition, or right). MUST use values from DeonticModalityScheme.
See also
has function
IRI: http://data.europa.eu/leg/lomo#hasFunction
Definition
Specifies the function of a temporal specification.
Usage Note
Use this property to indicate the role of a temporal specification. Common functions include deadline, validity period, starting point, and trigger.
Example
Member States shall submit their national implementation reports by 31 December 2025.
Turtle Instantiation
# Example 1: Deadline for an action
ex:Action_SubmitReport a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:instant "2025-12-31"^^xsd:date ;
lomo:hasFunction <http://data.europa.eu/leg/temporal-function/deadline> ;
] .
# Example 2: Validity period for a rule
ex:Rule_TemporaryMeasure a lomo:PrescriptiveRule ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:duration "P6M"^^xsd:duration ;
lomo:hasFunction <http://data.europa.eu/leg/temporal-function/validity> ;
] .
# Example 3: Trigger for a rule
ex:Rule_DataBreachNotification a lomo:PrescriptiveRule ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:temporalLabel "personal data breach"@en ;
lomo:hasFunction <http://data.europa.eu/leg/temporal-function/trigger> ;
] .
See also
has next
IRI: http://data.europa.eu/leg/lomo#hasNext
Definition
Indicates that one action is followed by another action in a sequence.
Example
An action to submit a draft is followed by an action to publish the final version.
Turtle Instantiation
ex:Action_SubmitDraft lomo:hasNext ex:Action_PublishFinal
has previous
IRI: http://data.europa.eu/leg/lomo#hasPrevious
Definition
Indicates that one action is preceded by another action in a sequence.
Example
An action to communicate a national transposition of a Directive to the Commission is preceded by the entry into force of the corresponding national legislation.
Turtle Instantiation
ex:Action_CommunicateTransposition lomo:hasPrevious ex:Action_TransposesDirective
has requirement type
IRI: http://data.europa.eu/leg/lomo#hasRequirementType
Definition
Relates a prescriptive rule to its functional or substantive category. MUST use values from the appropriate authority tables.
Usage Note
This property links the specific PrescriptiveRule to the SKOS concept describing the functional or substantive category.
In the case of the class lomo:ImplementationAndOversightRule, values in the range of this property should be taken from the Implementation and oversight authority table.
In the case of the class lomo:SubstantiveRule, values in the range of this property should be taken from the Administrative obligation authority table.
See also
has result
IRI: http://data.europa.eu/leg/lomo#hasResult
Definition
Links an action to the result(s) it produces.
Usage Note
Connects actions to their outputs. An action may produce multiple results. Use ActionResult for specific result instances (e.g., 'Annual Report 2024') or ActionResultType for result categories (e.g., 'Financial Statements' as a type).
Example
An action to prepare financial statements produces the 2024 financial statements. An audit action produces an audit report.
Turtle Instantiation
# Example 1: Linking an action to a specific result instance
ex:Action_PrepareFinancialStatements rdf:type lomo:Action ;
lomo:hasResult ex:Result_FinancialStatements_2024 .
ex:Result_FinancialStatements_2024 rdf:type lomo:ActionResult ;
rdfs:label "Financial Statements 2024"@en .
# Example 2: Linking an action to a result type
ex:Action_Audit rdf:type lomo:Action ;
lomo:hasResult ex:AuditReportType .
ex:AuditReportType rdf:type lomo:ActionResultType ;
rdfs:label "Audit Report"@en .
# Example 3: Action producing multiple results
ex:Action_AnnualReview rdf:type lomo:Action ;
lomo:hasResult ex:Result_AnnualReport_2024 , ex:Result_FinancialSummary_2024 .
ex:Result_AnnualReport_2024 rdf:type lomo:ActionResult ;
rdfs:label "Annual Report 2024"@en .
ex:Result_FinancialSummary_2024 rdf:type lomo:ActionResult ;
rdfs:label "Financial Summary 2024"@en .
has result category
IRI: http://data.europa.eu/leg/lomo#hasResultCategory
Definition
Specifies the category of a result.
See also
in
IRI: http://data.europa.eu/leg/lomo#in
Definition
Indicates that one temporal specification occurs entirely within the boundaries of another.
involves process
IRI: http://data.europa.eu/leg/lomo#involvesProcess
Definition
Links a requirement or action to the high-level process(es) it involves or contributes to. MUST use values from the Business Capabilities or Technical Capabilities concept schemes.
Usage Note
Used to classify requirements by the high-level processes they relate to. The concept schemes concerning business and technical capabilities should be used.
Example
'The Union entity or public sector body concerned shall publish, in a machine-readable format facilitating automated translation, a report presenting the outcome of the interoperability assessment, including the items listed in the Annex, on an official website.'
http://data.europa.eu/eli/reg/2024/903/art_3/par_1/oj
This LegalRule requires Union entities or public sector bodies concerned to have the capability to publish information.
Turtle Instantiation
ex:Requirement_Art4 a lomo:LegalRule ;
lomo:establishedIn http://data.europa.eu/eli/reg/2024/903/art_3/par_1/oj ;
lomo:involvesProcess https://op.europa.eu/web/eu-vocabularies/concept/-/resource?uri=http://data.europa.eu/9bx/1&lang=en .
See also
is composed of
IRI: http://data.europa.eu/leg/lomo#isComposedOf
Definition
Indicates that a result is composed of other results or components.
Usage Note
Models hierarchical result structures. For example, Annual Financial Statements type can be composed of Balance Sheet, Profit and Loss Account, and Notes types. Specific result instances can also be composed of other specific results.
Example
Annual Financial Statements consist of three components: Balance Sheet, Profit and Loss Account, and Notes.
Turtle Instantiation
ex:FinancialStatementsType lomo:isComposedOf
ex:BalanceSheetType ,
ex:ProfitLossAccountType ,
ex:NotesType .
is defined by
IRI: http://data.europa.eu/leg/lomo#isDefinedBy
Definition
Indicates that an agent type, temporal specification, result, or digital resource has been defined in a particular definition.
Usage Note
Use this property to link entities that were defined in a definition. Definitions themselves are modeled as instances of :Definition (a subclass of :ConstitutiveRule). When a constitutive construct establishes definitions, applications may model that containment using dataset- or project-specific patterns; :isDefinedBy should be used to reference existing Definition instances.
Key notes:
- Definitions are modeled as :Definition instances (subclass of :ConstitutiveRule).
- :isDefinedBy → Any entity can BE DEFINED BY an existing Definition.
Applicable domains (intentionally unspecified for flexibility):
1. Agent/AgentType: Links agents to definitions that define their category or status
2. ActionResult: Links results to definitions that specify output characteristics or formats
3. dcat:Dataset: Links datasets to definitions that specify data content or scope
4. TemporalSpecification: Link a specific event to its definition (e.g. "personal data breach")
A single entity can be fined by ONLY ONE definition.
Turtle Instantiation
# AgentType linked to its definition
ex:SmallUndertakings a lomo:AgentType ;
lomo:isDefinedBy ex:Def_SmallUndertakings ;
rdfs:comment "This agent type is defined by the criteria in the Small Undertakings definition."@en .
ex:Def_SmallUndertakings a lomo:Definition ;
lomo:hasDefiniendum "small undertakings"@en ;
lomo:hasDefiniens "undertakings which meet 2 of 3 following criterias: ..."@en ;
.
# TemporalSpecification linked to its definition
ex:TemporalDataBreach a lomo:TemporalSpecification ;
lomo:isDefinedBy ex:Def_PersonalDataBreach ;
rdfs:comment "This agent type is defined by the criteria in the Small Undertakings definition."@en .
ex:Def_PersonalDataBreach a lomo:Definition ;
lomo:hasDefiniendum "personal data breach"@en ;
lomo:hasDefiniens "a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored or otherwise processed"@en ;
.
is derogated by
IRI: http://data.europa.eu/leg/lomo#isDerogatedBy
Definition
Inverse of derogatesFrom: indicates that a legal rule is derogated by another rule that establishes an incompatible normative qualification for a defined range of cases.
Usage Note
Use isDerogatedBy to express the same relationship from the perspective of the rule being derogated.
Example
Directive 2013/34/EU Article 1 (General requirements for financial statements) is derogated by Article 1a which exempts micro-entities from the general financial reporting obligations.
GDPR Article 6(1)(a) (Consent as lawful basis) is derogated by Article 6(1)(b) which provides an alternative lawful basis through contract performance that can substitute for consent.
Regulation (EU) 2019/1242 Article 4 (CO₂ monitoring for heavy-duty vehicles) is derogated by Article 5(4) which exempts certain vehicle categories from the general monitoring obligation.
Turtle Instantiation
# Example 1: Financial reporting obligation derogated by micro-entity exemption
ex:Rule_Dir2013_34_Art1_GeneralObligation a lomo:PrescriptiveRule ;
rdfs:label "Directive 2013/34/EU Article 1(2)(a): General requirements for financial statements"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Obligation> ;
lomo:isDerogatedBy ex:Rule_Dir2013_34_Art1a_MicroEntityDerogation ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2013/34/oj/art_1> .
ex:Rule_Dir2013_34_Art1a_MicroEntityDerogation a lomo:PrescriptiveRule ;
rdfs:label "Directive 2013/34/EU Article 1a: Derogation for micro-entities"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Permission> ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2013/34/oj/art_1a> .
# Example 2: Consent requirement derogated by alternative contract-based lawful basis
ex:Rule_GDPR_Art6_1_a_Consent a lomo:PrescriptiveRule ;
rdfs:label "GDPR Article 6(1)(a): Lawful basis - Consent"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Permission> ;
lomo:isDerogatedBy ex:Rule_GDPR_Art6_1_b_ContractPerformance ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2016/679/art_6/par_1/point_a> .
ex:Rule_GDPR_Art6_1_b_ContractPerformance a lomo:PrescriptiveRule ;
rdfs:label "GDPR Article 6(1)(b): Lawful basis - Contract performance"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Permission> ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2016/679/art_6/par_1/point_b> ;
rdfs:comment "Article 6(1)(b) substitutes consent as a lawful basis when contract performance is necessary" .
# Example 3: CO₂ monitoring obligation derogated by category exemptions
ex:Rule_EU2019_1242_Art4_CO2Monitoring a lomo:SubstantiveRule ;
rdfs:label "Regulation (EU) 2019/1242 Article 4: CO₂ monitoring"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Obligation> ;
lomo:isDerogatedBy ex:Rule_EU2019_1242_Art5_4_VehicleDerogation ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2019/1242/art_4> .
ex:Rule_EU2019_1242_Art5_4_VehicleDerogation a lomo:PrescriptiveRule ;
rdfs:label "Regulation (EU) 2019/1242 Article 5(4): Derogation from monitoring for certain vehicles"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Permission> ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2019/1242/art_5/par_4> ;
rdfs:comment "Article 5(4) provides a blocking derogation that suspends the general monitoring obligation for specified vehicle categories" .
is manifested in
IRI: http://data.europa.eu/leg/lomo#isManifestedIn
Definition
Relates an ActionResult (or ActionResultType) to the dcat:Dataset that manifests or contains the realized output.
Usage Note
Use this property to link an ActionResult or ActionResultType to the dcat:Dataset that contains or represents its real-world manifestation. This property bridges the legal definition of an ActionResult (or ActionResultType) with its concrete representation in a dataset.
Key points:
- ActionResult: Represents the legal definition or conceptual output of an action (e.g., 'Annual Report 2025 on Interoperability').
- dcat:Dataset: Represents the concrete dataset that contains or manifests the ActionResult (e.g., the actual dataset containing the report).
- Purpose: To link the legal or conceptual definition of a result to its real-world manifestation in a dataset.
This property is particularly useful when an ActionResult or ActionResultType has a corresponding dataset that represents its realization or publication.
Example
A result (Annual Report 2025 on Interoperability) is manifested in a specific dataset containing the report.
Turtle Instantiation
# Example 1: Linking an ActionResult to a dataset
ex:Result_AnnualReport2025_Interoperability rdf:type lomo:ActionResult ;
rdfs:label "Annual Report 2025 on Interoperability"@en ;
lomo:isManifestedIn ex:Dataset_InteroperabilityReport2025 .
ex:Dataset_InteroperabilityReport2025 rdf:type dcat:Dataset ;
dcterms:title "Interoperability Report 2025 Dataset"@en .
# Example 2: Linking an ActionResultType to a dataset
ex:ResultType_AnnualInteroperabilityReport rdf:type lomo:ActionResultType ;
rdfs:label "Annual Report on Interoperability"@en ;
lomo:isManifestedIn ex:Dataset_InteroperabilityReports .
ex:Dataset_InteroperabilityReports rdf:type dcat:Dataset ;
dcterms:title "Interoperability Reports Dataset"@en .
is specified by
IRI: http://data.europa.eu/leg/lomo#isSpecifiedBy
Definition
Inverse of specifies: indicates that a more general legal rule is specified by a more specific rule that determines its underdetermined content without creating conflicting normative qualifications.
Usage Note
Use isSpecifiedBy to express the same relationship from the perspective of the general rule being specified by the more specific rule.
Example
GDPR Article 5 (Principles relating to processing of personal data) is specified by Article 4(7) which defines 'controller' — a key concept upon which the principles depend.
Directive 2013/34/EU Article 4 (General requirements) is specified by Article 2(3) which defines the size thresholds for 'small undertakings' — determining which entities are subject to simplified requirements.
Regulation (EU) 2018/848 Article 3 (General obligation for organic farming) is specified by Articles 10 and 11, which detail the specific practices operators must follow for crop production and livestock production respectively.
Turtle Instantiation
# Example 1: GDPR principle specified by definition
ex:Rule_GDPR_Art5_Principles a lomo:ConstitutiveRule ;
rdfs:label "GDPR Article 5: Principles relating to processing"@en ;
lomo:isSpecifiedBy ex:Rule_GDPR_Art4_7_Controller .
ex:Rule_GDPR_Art4_7_Controller a lomo:Definition ;
rdfs:label "GDPR Article 4(7): Definition of Controller"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2016/679/art_4/par_7> .
# Example 2: General obligation specified by detailed practices
ex:Rule_OrgFarm_Art3_GeneralObligation a lomo:PrescriptiveRule ;
rdfs:label "Regulation (EU) 2018/848 Article 3: General Obligation"@en ;
lomo:isSpecifiedBy ex:Rule_OrgFarm_Art10_CropProduction ;
lomo:isSpecifiedBy ex:Rule_OrgFarm_Art11_LivestockProduction .
ex:Rule_OrgFarm_Art10_CropProduction a lomo:SubstantiveRule ;
rdfs:label "Regulation (EU) 2018/848 Article 10: Crop Production Requirements"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2018/848/art_10> .
ex:Rule_OrgFarm_Art11_LivestockProduction a lomo:SubstantiveRule ;
rdfs:label "Regulation (EU) 2018/848 Article 11: Livestock Production Requirements"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2018/848/art_11> .
ex:Rule_Dir2013_34_Art4_ReportingObligations a lomo:PrescriptiveRule ;
rdfs:label "Directive 2013/34/EU Article 4: General requirements"@en ;
lomo:isSpecifiedBy ex:Rule_Dir2013_34_Art2_3_SmallUndertakings .
ex:Rule_Dir2013_34_Art2_3_SmallUndertakings a lomo:Definition ;
rdfs:label "Directive 2013/34/EU Article 2(3): Definition of small undertakings"@en ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2013/34/oj/art_2/par_3> .
manifests
IRI: http://data.europa.eu/leg/lomo#manifests
Definition
Inverse of :isManifestedIn; relates a dcat:Dataset to the ActionResult(s) it manifests.
Usage Note
Use this property to link a dcat:Dataset to the ActionResult or ActionResultType that it manifests. This property is the inverse of :isManifestedIn and serves the same purpose but from the perspective of the dataset.
Key points:
- dcat:Dataset: Represents the concrete dataset that contains or manifests the ActionResult (e.g., the actual dataset containing the report).
- ActionResult: Represents the legal definition or conceptual output of an action (e.g., 'Annual Report 2025 on Interoperability').
- Purpose: To link the concrete dataset to the legal or conceptual definition of the result it manifests.
This property is particularly useful when a dataset represents the realization or publication of an ActionResult or ActionResultType.
Example
A dataset containing the 2025 Interoperability Report manifests the annual report result.
Turtle Instantiation
# Example 1: Linking a dataset to an ActionResult
ex:Dataset_InteroperabilityReport2025 rdf:type dcat:Dataset ;
dcterms:title "Interoperability Report 2025 Dataset"@en ;
lomo:manifests ex:Result_AnnualReport2025_Interoperability .
ex:Result_AnnualReport2025_Interoperability rdf:type lomo:ActionResult ;
rdfs:label "Annual Report 2025 on Interoperability"@en .
# Example 2: Linking a dataset to an ActionResultType
ex:Dataset_InteroperabilityReports rdf:type dcat:Dataset ;
dcterms:title "Interoperability Reports Dataset"@en ;
lomo:manifests ex:ResultType_AnnualInteroperabilityReport .
ex:ResultType_AnnualInteroperabilityReport rdf:type lomo:ActionResultType ;
rdfs:label "Annual Report on Interoperability"@en .
overlaps
IRI: http://data.europa.eu/leg/lomo#overlaps
Definition
Indicates that two temporal specifications share a common portion of time without either completely containing the other.
Usage Note
Use this property to indicate temporal overlap between two temporal specifications. This property exclusively refers to temporal overlap and does not imply any other form of overlap or relationship.
Example
Two temporal specifications overlap if they share a common period of time, such as two projects running concurrently for a period.
Turtle Instantiation
# Example 1: Two actions with overlapping temporal specifications
ex:Action_ProjectA a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:instant "2025-01-01"^^xsd:date ;
lomo:duration "P6M"^^xsd:duration ;
] .
ex:Action_ProjectB a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:instant "2025-03-01"^^xsd:date ;
lomo:duration "P6M"^^xsd:duration ;
] .
ex:TemporalSpec_ProjectA lomo:overlaps ex:TemporalSpec_ProjectB .
# Example 2: Two temporal specifications with partial overlap
ex:TemporalSpec_EventA a lomo:TemporalSpecification ;
lomo:instant "2025-01-01"^^xsd:date ;
lomo:duration "P3M"^^xsd:duration .
ex:TemporalSpec_EventB a lomo:TemporalSpecification ;
lomo:instant "2025-02-01"^^xsd:date ;
lomo:duration "P3M"^^xsd:duration .
ex:TemporalSpec_EventA lomo:overlaps ex:TemporalSpec_EventB .
produces
IRI: http://data.europa.eu/leg/lomo#produces
Definition
Relates a prescriptive rule to the action(s) it prescribes.
Usage Note
Links a PrescriptiveRule to the Action(s) that must/may/must-not be performed. A requirement may produce multiple actions. NOTE: This property applies only to PrescriptiveRule (prescriptive rules). ConstitutiveRule instances do NOT produce actions - they constitute facts or define terms.
Example
A requirement to inform the Commission produces an action to inform the Commission of changes.
Turtle Instantiation
ex:Requirement_Art1_Par2_InformCommission lomo:produces ex:Action_InformCommissionOfChanges .
references
IRI: http://data.europa.eu/leg/lomo#references
Definition
Relates a legal rule to a digital resource (dataset, standard, software, service) that is referenced, cited, or pointed to by the rule.
Usage Note
Use this property to link legal rules to the digital resources they mention, cite, or relate to.
Common patterns:
1. Requirements reference DATASETS they mandate (e.g., Article 4 references fisheries statistics datasets)
2. Requirements reference STANDARDS they invoke (e.g., Article 11 references quality standards)
3. Requirements reference SOFTWARE/SYSTEMS they utilize (e.g., Article 7 references EUROBASE)
4. Requirements reference SERVICES they provide (e.g., requirements that reference data collection activities for statistical dissemination)
The referenced resources are typically modeled as:
- dcat:Dataset for data types
- dcterms:Standard for standards and specifications
- dcterms:Software for digital solutions and systems
- cpsv:PublicService for digital public services
Turtle Instantiation
# Requirement references multiple digital resources
ex:Requirement_Art4_Par1 lomo:references
ex:Dataset_FisheriesStatistics ,
ex:Dataset_AquacultureStatistics ,
ex:Standard_AnnexRequirements ,
ex:Service_DataCollection .
# The referenced resources
ex:Dataset_FisheriesStatistics rdf:type dcat:Dataset .
ex:Standard_AnnexRequirements rdf:type dcterms:Standard .
ex:Service_DataCollection rdf:type cpsv:PublicService .
relates to
IRI: http://data.europa.eu/leg/lomo#relatesTo
Definition
Establishes a generic, non-hierarchical relationship between two legal rules that are semantically connected but where no stronger relationship (such as derogation or specificity) applies. This is a catch-all property for rule-to-rule relationships. This is a super-property of both lomo:derogatesFrom and lomo:specifies, enabling generic querying across all rule relationships.
Usage Note
Use relatesTo when two rules share context, subject matter, or are part of the same regulatory framework, but neither derogates, specializes, nor overrides the other.
Key characteristics:
- The relationship is generic and non-directional (unless specialized by derogatesFrom or specifies)
- The two rules are semantically connected but without hierarchy (at the base level)
- May be specialized into more specific relationships: derogatesFrom or specifies
- Should be accompanied by a rdfs:comment or skos:note explaining the nature of the relationship
Guidance:
- Prefer more precise sub-properties (lomo:specifies, lomo:derogatesFrom) when applicable
- Use lomo:relatesTo as a catch-all for rules that are contextually connected but lack a specific hierarchical or defeasibility relationship
- Use lomo:relatesTo for generic querying across all rule-to-rule relationships (including specificity and derogation)
- Consider documenting the nature of the relationship in comments
Property hierarchy:
- lomo:relatesTo (super-property, encompasses all rule relationships)
- lomo:derogatesFrom (sub-property: deontic conflict)
- lomo:specifies (sub-property: determines underdetermined content)
Turtle Instantiation
# Example 1: Complementary rules from the same regulatory framework (generic relation)
ex:Rule_GDPR_Art5_Principles a lomo:ConstitutiveRule ;
rdfs:label "GDPR Article 5: Principles relating to processing of personal data"@en ;
lomo:relatesTo ex:Rule_GDPR_Art6_LawfulBasis ;
skos:note "Both articles are foundational to the GDPR but neither specifies nor derogates from the other - they establish complementary requirements" ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2016/679/art_5> .
ex:Rule_GDPR_Art6_LawfulBasis a lomo:ConstitutiveRule ;
rdfs:label "GDPR Article 6: Lawfulness of processing"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2016/679/art_6> .
# Example 2: Data reporting and verification obligations from same legislative instrument
ex:Rule_FinRep_Art4_DataRequirements a lomo:PrescriptiveRule ;
rdfs:label "Financial Reporting Regulation Article 4: Data reporting requirements"@en ;
lomo:relatesTo ex:Rule_FinRep_Art5_DataVerification ;
skos:note "Both rules govern financial data quality in the same regulatory framework: Article 4 specifies what to report, Article 5 specifies how to verify; they are complementary but independent requirements" ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2019/815/art_4> .
ex:Rule_FinRep_Art5_DataVerification a lomo:PrescriptiveRule ;
rdfs:label "Financial Reporting Regulation Article 5: Data verification requirements"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2019/815/art_5> .
# Example 3: Cross-cutting obligations from environmental legislation
ex:Rule_EIA_Art5_PublicConsultation a lomo:PrescriptiveRule ;
rdfs:label "Environmental Impact Assessment Directive Article 5: Public consultation on environmental effects"@en ;
lomo:relatesTo ex:Rule_EIA_Art6_ScreeningRequirements ;
skos:note "Both articles are procedural requirements for environmental assessment but neither determines nor overrides the other - they work together in sequence" ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2014/52/art_5> .
ex:Rule_EIA_Art6_ScreeningRequirements a lomo:PrescriptiveRule ;
rdfs:label "Environmental Impact Assessment Directive Article 6: Screening for environmental effects"@en ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2014/52/art_6> .
# Example 4: Using relatesTo for generic querying across all rule types
# Query: ?rule1 lomo:relatesTo ?rule2
# Returns results for generic relations (Examples 1-3) plus all specifies and derogatesFrom relationships
specifies
IRI: http://data.europa.eu/leg/lomo#specifies
Definition
Relates a more specific legal rule to a more general rule whose underdetermined content it further determines, without producing conflicting normative qualifications. The specifying rule articulates, defines, or concretises elements that the general rule leaves open — such as concepts, procedures, thresholds, addressees, or scope — so that both rules remain jointly applicable and their conclusions compose without contradiction.
Usage Note
Use specifies when a rule elaborates the content of another rule in a way that is compatible with it: the two rules, applied together to the same case, do not yield conflicting normative qualifications. The specifying rule fills a gap of determination rather than overriding the general rule.
Key characteristics:
- The specifying rule is more specific, detailed, or particular
- Both rules remain jointly applicable without contradiction
- The specifying rule clarifies, defines, or concretises elements left open by the general rule
- No deontic conflict between the two rules
Example: GDPR Article 5 establishes principles for personal data processing. Article 4(7) defines what counts as a 'controller' for these principles. Article 4(7) specifies Article 5 by determining one of the concepts it operates on.
Example
GDPR Article 4(7) defines 'controller' as 'the natural or legal person, public authority, agency or any other body which, alone or jointly with others, determines the purposes and means of the processing of personal data.' This specifies GDPR Article 5 (principles for processing) by determining a key concept the principles operate on.
Directive 2013/34/EU Article 2(3) defines 'small undertakings' with specific size criteria (total assets, net turnover, employees). This specifies Article 4 (requirements for financial reporting) by determining which entities are subject to simplified reporting procedures.
eIDAS Regulation Article 4(27) defines 'electronic identification' as 'the process of using identification data in electronic form which uniquely represents either a natural or legal person.' This specifies the general identity requirements in Article 6 by clarifying what forms of identification satisfy the regulation.
Turtle Instantiation
# Example 1: GDPR - Concept definition specifying principles
ex:Rule_GDPR_Art4_7_Controller a lomo:Definition ;
rdfs:label "GDPR Article 4(7): Definition of Controller"@en ;
lomo:hasDefiniendum "controller"@en ;
lomo:hasDefiniens "the natural or legal person, public authority, agency or any other body which, alone or jointly with others, determines the purposes and means of the processing of personal data"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2016/679/art_4/par_7> ;
lomo:specifies ex:Rule_GDPR_Art5_Principles .
ex:Rule_GDPR_Art5_Principles a lomo:ConstitutiveRule ;
rdfs:label "GDPR Article 5: Principles relating to processing of personal data"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2016/679/art_5> .
# Example 2: Directive 2013/34/EU - Size criteria specifying reporting obligations
ex:Rule_Dir2013_34_Art2_3_SmallUndertakings a lomo:Definition ;
rdfs:label "Directive 2013/34/EU Article 2(3): Definition of small undertakings"@en ;
lomo:hasDefiniendum "small undertakings"@en ;
lomo:hasDefiniens "undertakings which on their balance sheet dates do not exceed the limits of at least two of the three following criteria: (1) total assets: EUR 4,000,000; (2) net turnover: EUR 8,000,000; (3) average number of employees during the financial year: 50"@en ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2013/34/oj/art_2/par_3> ;
lomo:specifies ex:Rule_Dir2013_34_Art4_ReportingObligations .
ex:Rule_Dir2013_34_Art4_ReportingObligations a lomo:PrescriptiveRule ;
rdfs:label "Directive 2013/34/EU Article 4: General requirements"@en ;
lomo:establishedIn <http://data.europa.eu/eli/dir/2013/34/oj/art_4> .
# Example 3: Organic Farming Regulation - Detailed practices specifying general obligation
ex:Rule_OrgFarm_Art3_GeneralObligation a lomo:PrescriptiveRule ;
rdfs:label "Regulation (EU) 2018/848 Article 3: General Obligation"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Obligation> ;
lomo:legalText "Operators producing, preparing or distributing organic products shall ensure and maintain the measures necessary to comply with this Regulation."@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2018/848/art_3> .
ex:Rule_OrgFarm_Art10_CropProduction a lomo:SubstantiveRule ;
rdfs:label "Regulation (EU) 2018/848 Article 10: Crop Production Requirements"@en ;
lomo:hasDeonticModality <http://data.europa.eu/leg/deontic-modality/Obligation> ;
lomo:specifies ex:Rule_OrgFarm_Art3_GeneralObligation ;
lomo:legalText "For crop production, operators shall use crop and soil management practices adapted to local conditions, including where appropriate conservation of natural resources and maintenance or improvement of soil fertility, through [...] appropriate crop rotations; [...]"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2018/848/art_10> ;
rdfs:comment "Article 10 specifies the general obligation in Article 3 by establishing concrete practices required for organic crop production" .
# Example 3: eIDAS - Electronic identification specifying identity requirements
ex:Rule_eIDAS_Art4_27_eID a lomo:Definition ;
rdfs:label "eIDAS Regulation Article 4(27): Definition of electronic identification"@en ;
lomo:hasDefiniendum "electronic identification"@en ;
lomo:hasDefiniens "the process of using identification data in electronic form which uniquely represents either a natural or legal person"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2014/910/art_4/par_27> ;
lomo:specifies ex:Rule_eIDAS_Art6_IdentityRequirements .
ex:Rule_eIDAS_Art6_IdentityRequirements a lomo:ConstitutiveRule ;
rdfs:label "eIDAS Regulation Article 6: General requirements for electronic identification"@en ;
lomo:establishedIn <http://data.europa.eu/eli/reg/2014/910/art_6> .
started by
IRI: http://data.europa.eu/leg/lomo#startedBy
Definition
Indicates that one temporal specification has its beginning point at the same moment as another (inverse of starts).
Usage Note
Use this property to indicate that one temporal specification has its beginning point at the same moment as another. This property is the inverse of :starts and is context-independent, suitable for modeling temporal relationships in legal rules, actions, and other entities.
Example
A reporting period is started by the beginning of a fiscal year.
Turtle Instantiation
# Example 1: Reporting period started by the beginning of a fiscal year
ex:ReportingPeriod2025 a lomo:TemporalSpecification ;
lomo:instant "2025-01-01"^^xsd:date ;
rdfs:label "Start of Reporting Period 2025"@en ;
lomo:startedBy ex:FiscalYear2025 .
ex:FiscalYear2025 a lomo:TemporalSpecification ;
lomo:instant "2025-01-01"^^xsd:date ;
rdfs:label "Start of Fiscal Year 2025"@en .
# Example 2: One action started by the beginning of another action
ex:Action_SubmitReport a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:startedBy ex:Action_ReviewReport ;
] .
ex:Action_ReviewReport a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:instant "2025-12-31"^^xsd:date ;
] .
starts
IRI: http://data.europa.eu/leg/lomo#starts
Definition
Indicates that one temporal specification begins at the same moment as another.
Usage Note
Use this property to indicate that one temporal specification begins at the same moment as another. This property is context-independent and can be used to model temporal relationships in legal rules, actions, and other entities.
Example
A fiscal year starts at the same moment as a new reporting period begins.
Turtle Instantiation
# Example 1: Fiscal year starts at the same moment as a reporting period
ex:FiscalYear2025 a lomo:TemporalSpecification ;
lomo:instant "2025-01-01"^^xsd:date ;
rdfs:label "Start of Fiscal Year 2025"@en ;
lomo:starts ex:ReportingPeriod2025 .
ex:ReportingPeriod2025 a lomo:TemporalSpecification ;
lomo:instant "2025-01-01"^^xsd:date ;
rdfs:label "Start of Reporting Period 2025"@en .
# Example 2: One action starts at the same moment as another action
ex:Action_ReviewReport a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:starts ex:Action_SubmitReport ;
] .
ex:Action_SubmitReport a lomo:Action ;
lomo:atTime [
a lomo:TemporalSpecification ;
lomo:instant "2025-12-31"^^xsd:date ;
] .
with role
IRI: http://data.europa.eu/leg/lomo#withRole
Definition
Specifies the type of role performed by an agent. MUST use values from the OP AT Role Table.
Usage Note
In the context of LOMO 1.0.0, only the following three concepts from the OP AT Role authority table are permitted as values of lomo:withRole:
- <http://publications.europa.eu/resource/authority/role/ADDRESSER> (Addresser): the agent who sends a request or communication
- <http://publications.europa.eu/resource/authority/role/ADDRESSEE> (Addressee): the agent to whom something is addressed
- <http://publications.europa.eu/resource/authority/role/BENEF> (Beneficiary): the agent who benefits from an action
These three concepts are grouped in the skos:Collection :LomoPermittedRoles defined in this ontology. This restriction is also enforced by a sh:in constraint in the LOMO SHACL shapes (shapes/lomo-shapes.ttl).
The AT Role authority table contains many additional concepts whose definitions do not fit the scope of LOMO. This restriction is intended to prevent the annotation of data with role values that may become incompatible with future versions of LOMO. The restriction will be reviewed and may be extended in LOMO 2.0.0.
See also
Datatype Properties
duration
IRI: http://data.europa.eu/leg/lomo#duration
Definition
A duration value expressed using xsd:duration.
Usage Note
Use for durations in months, years, etc. Examples: 'P6M' (6 months), 'P3Y' (3 years), 'P30D' (30 days).
Example
Before 3 years after the approval date
frequency
IRI: http://data.europa.eu/leg/lomo#frequency
Definition
A frequency indication as an xsd:duration expressing the elapsed time between occurrences.
Usage Note
Use for recurring patterns like 'every year' (P1Y), 'daily' (P1D).
Example
Every year until 2035
has capability
IRI: http://data.europa.eu/leg/lomo#hasCapability
Definition
Describes a technical function or capability that a digital solution (software) provides.
Usage Note
Use this property to describe what a digital solution CAN DO from a technical perspective. Capabilities represent the functional features or technical abilities of software systems. Multiple capabilities can be specified for a single software instance.
Key characteristics of capabilities:
- TECHNICAL FOCUS: What the software is able to perform (functions, operations)
- IMPLEMENTATION-ORIENTED: How the system delivers its functionality
- REUSABLE: The same capability may be provided by different software systems
For the PURPOSE or OBJECTIVE of a public service (policy goals, societal outcomes), use :hasPurpose instead.
Examples of software capabilities:
- 'Collect structured data from web forms'
- 'Validate data against SHACL constraints'
- 'Transform XML to RDF format'
- 'Disseminate statistics via REST API'
- 'Generate PDF reports from templates'
- 'Authenticate users via eIDAS'
Example
Software systems can have multiple capabilities: EUROBASE stores and retrieves statistical datasets, provides public web access, and exports data in various formats.
Turtle Instantiation
ex:Software_EUROBASE rdf:type dcterms:Software ;
dcterms:title "EUROBASE Statistical Database"@en ;
lomo:hasCapability "Store and retrieve statistical datasets"@en ;
lomo:hasCapability "Provide public access via web interface"@en ;
lomo:hasCapability "Export data in multiple formats (CSV, SDMX, JSON)"@en ;
dcterms:publisher ex:Agent_Eurostat .
ex:Software_DataValidation rdf:type dcterms:Software ;
dcterms:title "Statistical Data Validation System"@en ;
lomo:hasCapability "Validate incoming data against predefined rules"@en ;
lomo:hasCapability "Generate validation reports"@en ;
lomo:hasCapability "Flag anomalies for manual review"@en .
has definiendum
IRI: http://data.europa.eu/leg/lomo#hasDefiniendum
Definition
The symbol being defined (the term or phrase whose meaning is being established). In a definitional relation, the definiendum is the symbol on the left-hand side of the definition.
has definiens
IRI: http://data.europa.eu/leg/lomo#hasDefiniens
Definition
The defining symbol or phrase that establishes the meaning of the definiendum. In syntactic definitions, this is simply the symbol that is equated with the definiendum. In semantic definitions, this includes descriptive terms that reference a class of referents.
has purpose
IRI: http://data.europa.eu/leg/lomo#hasPurpose
Definition
Describes the objective, mission, or intended outcome of a public service or public action.
Usage Note
Use this property to describe WHY a public service exists and WHAT OUTCOMES it aims to achieve. Purpose statements express policy goals, societal benefits, or the mission of public actions. Multiple purposes can be specified for a single service.
Key characteristics of purposes:
- OUTCOME-ORIENTED: What the service aims to achieve for citizens, businesses, or society
- POLICY-ALIGNED: Connected to legal mandates, policy objectives, or public interest goals
- MISSION-DRIVEN: Expresses the 'why' rather than the 'how'
For technical CAPABILITIES of software systems (what they can do), use :hasCapability instead.
Distinction from capabilities:
- Capability: 'Collect data from Member States' (technical function)
- Purpose: 'Ensure availability of harmonized European fisheries statistics for policy-making' (policy goal)
Examples of public service purposes:
- 'Provide transparent access to European statistical data for citizens and researchers'
- 'Enable evidence-based policy-making through reliable fisheries statistics'
- 'Ensure compliance with EU statistical quality standards across Member States'
- 'Support sustainable fisheries management through timely data availability'
- 'Facilitate cross-border data sharing between national statistical institutes'
Example
A public service can have multiple purposes: the European Statistical Dissemination Service aims to provide transparent access to data and support evidence-based policy-making.
Turtle Instantiation
ex:Service_StatisticalDissemination rdf:type cpsv:PublicService ;
dcterms:title "European Statistical Dissemination Service"@en ;
lomo:hasPurpose "Provide transparent access to European statistical data for citizens, researchers, and policy-makers"@en ;
lomo:hasPurpose "Support evidence-based policy-making at EU and national levels"@en ;
cpsv:hasCompetentAuthority ex:Agent_Eurostat .
ex:Service_DataQualityAssurance rdf:type cpsv:PublicService ;
dcterms:title "Statistical Data Quality Assurance Service"@en ;
lomo:hasPurpose "Ensure reliability and comparability of European statistics"@en ;
lomo:hasPurpose "Build public trust in official statistics through quality verification"@en ;
cpsv:hasCompetentAuthority ex:Agent_Eurostat .
ex:Service_MemberStateDataCollection rdf:type cpsv:PublicService ;
dcterms:title "Member State Data Collection Service"@en ;
lomo:hasPurpose "Gather harmonized fisheries data from all EU Member States"@en ;
lomo:hasPurpose "Enable production of comparable European statistics"@en ;
cpsv:hasCompetentAuthority ex:Agent_Eurostat .
instant
IRI: http://data.europa.eu/leg/lomo#instant
Definition
A specific date or datetime value for a point in time.
Usage Note
Use this property to specify a point in time as a datatype value. This property is a datatype property, not a subcategory of TemporalSpecification. It can represent specific dates, times, or parts of dates/times (e.g., 'on 12/04/2026', '14:00', 'the 30th september', 'january').
Supported datatype values:
- xsd:date: Full date (e.g., '2026-04-12')
- xsd:dateTime: Date and time (e.g., '2026-04-12T14:00:00')
- xsd:gDay: Day of the month (e.g., '---30')
- xsd:gMonth: Month (e.g., '--09')
- xsd:gMonthDay: Month and day (e.g., '--09-30')
- xsd:gYear: Year (e.g., '2026')
- xsd:gYearMonth: Year and month (e.g., '2026-04')
- xsd:time: Time (e.g., '14:00:00')
Example
Member States shall transpose this directive before the 12/04/2026
legal text
IRI: http://data.europa.eu/leg/lomo#legalText
Definition
The verbatim text from the legal source.
Usage Note
Applicable to all classes under Legal Rule (PrescriptiveRule, ConstitutiveRule, Definition) as well as Action. Captures the exact wording from the legal instrument.
repetitions
IRI: http://data.europa.eu/leg/lomo#repetitions
Definition
A fixed number of repetitions for a recurring temporal specification.
Usage Note
Use for expressions like '3 times', '(every year) during 5 years'. Complements frequency to specify total repetitions.
Example
Every year during 5 years
temporal label
IRI: http://data.europa.eu/leg/lomo#temporalLabel
Definition
The name or label of an event or period referenced in the temporal specification.
Usage Note
Use for named events or periods such as 'personal data breach', 'warranty period', 'date of entry into force of the directive', 'closing of the year', 'approval date', 'submission date'.
Example
In case of a personal data breach, the controller shall...
term label
IRI: http://data.europa.eu/leg/lomo#termLabel
Definition
The exact label of a defined term as it appears in the legal text.
Example
The term 'personal data' as defined in Art 4(1) of Regulation (EU) 2016/679 (GDPR).
Turtle Instantiation
# Example: Definition of 'personal data' from GDPR Art 4(1)
ex:Def_PersonalData rdf:type lomo:Definition ;
lomo:termLabel "personal data"@en ;
lomo:hasDefiniendum "personal data"@en ;
lomo:hasDefiniens "any information relating to an identified or identifiable natural person ('data subject'); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person"@en ;
lomo:establishedIn <https://data.europa.eu/eli/reg/2016/679/art_4/par_1> .