Legal Obligation Metadata Ontology (LOMO)

Released 2026-01-16

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 (bearer, 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.

Ontology Class Diagram

Class
Abstract Class
SKOS Concept
Inheritance
Association

Entities

Action

IRI: http://data.europa.eu/lomo#Action

Definition:
An event that must, may, or may not be performed by one or more agents, as prescribed by a prescriptive rule.
See also
  • Inspired by RRMV Action and LegalRuleML Rule.
is subClass of
Property Range Definition

Action Result

IRI: http://data.europa.eu/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
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 .
is subClass of

Action Result Type

IRI: http://data.europa.eu/lomo#ActionResultType

Definition:
A category or type of action results rather than a specific identified result instance.
Usage Note
Use ActionResultType to represent classes of outputs from actions.
Example
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
is subClass of

Action Result or Action Result Type

IRI: http://data.europa.eu/lomo#ActionResultOrType

Definition:
Abstract superclass for ActionResult (specific result instances), ActionResultType (categories of results). Used as a flexible range for properties linking to results.
is subClass of
Property Range Definition

Agent

IRI: http://data.europa.eu/lomo#Agent

Definition:
A specific, identifiable legal subject (natural person, legal person, or organization) that participates in an action.
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
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 .
See also
  • Inspired by RRMV Agent and ELI-LO Agent definitions.
is subClass of

Agent Role

IRI: http://data.europa.eu/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: bearer, addressee, addresser, beneficiary). An action may have multiple agent roles. Use Agent for specific entities and AgentType for categories.
Example
# Using a specific Agent ex:AgentRole_Commission_Bearer rdf:type lomo:AgentRole ; lomo:forAgent ex:Commission ; lomo:withRole lomo:bearer ; rdfs:comment "The Commission bears this obligation"@en . # Using an AgentType (category) ex:AgentRole_MS_Addresser rdf:type lomo:AgentRole ; lomo:forAgent ex:MemberStates ; lomo:withRole lomo:addresser ; rdfs:comment "Member States (as a category) send notification"@en .
is subClass of
Property Range Definition

Agent Type

IRI: http://data.europa.eu/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
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 .
is subClass of

Agent or Agent Type

IRI: http://data.europa.eu/lomo#AgentOrType

Definition:
Abstract superclass for Agent (specific entities), AgentType (categories of entities). Used as the range for forAgent property in AgentRole.
is subClass of

Constitutive Rule

IRI: http://data.europa.eu/lomo#ConstitutiveRule

Definition:
A legal provision that creates, defines, or constitutes institutional facts, 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
Example 1: 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" Example 2: Explicit Definition - Category with Criteria (Fourth Company Law Directive 78/660/EEC, Art. 11) 'Small companies within the meaning of Article 27 shall be companies which on their balance sheet dates do not exceed the limits of at least two of the three following criteria: balance sheet total: 1 000 000 ECU, net turnover: 2 000 000 ECU, average number of employees during the financial year: 50' Example 3: Scope Provision - Positive Applicability (Markets in Financial Instruments Directive - MiFID II, Art. 1(1)) 'This Directive applies to investment firms, credit institutions when providing investment services and/or performing investment activities, and regulated markets' Example 4: 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' Example 5: Status Constitution - Legal Personality (Regulation (EU) 2016/794 - Europol Regulation, Art. 3) 'Europol shall be a body of the Union. It shall have legal personality' Example 6: Organ Establishment (GDPR Art. 68(1)) 'The European Data Protection Board ('Board') is hereby established as a body of the Union' Example 7: Composition Definition (Regulation (EU) No 910/2014 - eIDAS, Art. 17(4)) 'The Cooperation Group shall be composed of representatives of Member States, the Commission and the supervisory body or supervisory bodies, where they exist' Example 8: Power/Competence Attribution (Treaty on the Functioning of the European Union - TFEU, Art. 258) 'If the Commission considers that a Member State has failed to fulfil an obligation under the Treaties, it may bring the matter before the Court of Justice of the European Union' Note: While 'may bring' might seem prescriptive (permission), this provision primarily constitutes the Commission's institutional power/competence in infringement procedures. Example 9: 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' Example 10: Qualification/Classification (Regulation (EC) No 178/2002 - General Food Law, Art. 3(1)) 'For the purposes of this Regulation, 'food' (or 'foodstuff') means any substance or product, whether processed, partially processed or unprocessed, intended to be, or reasonably expected to be ingested by humans' Example 11: 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' Example 12: 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.
  • Based on Searle's theory of constitutive rules. Represents provisions that establish institutional facts without prescribing actions. Parent class of Definition.
is subClass of

Definition

IRI: http://data.europa.eu/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' - Definiens: reference to IAS/IFRS definition - No explicit referent class (inherited from the referenced standard) Use isSemanticDefinition property to distinguish: true for semantic, false for syntactic.
Example
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:hasReferent ex:PublicInterestEntity1 , ex:PublicInterestEntity2 ; lomo:isSemanticDefinition "true"^^xsd:boolean ; lomo:establishedInResource <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 ; lomo:hasDefiniens "has the same meaning as in IAS 24 (Related Party Disclosures)"@en ; lomo:isSemanticDefinition "false"^^xsd:boolean ; 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:hasReferent ex:SmallUndertaking1, ex:SmallUndertaking2 ; lomo:isSemanticDefinition "true"^^xsd:boolean ; lomo:establishedInResource <https://eur-lex.europa.eu/eli/dir/2013/34/oj/art_2/point_2> .
is subClass of
Property Range Definition

Deontic Modality

IRI: http://data.europa.eu/lomo#DeonticModality

Definition:
The deontic character of a prescriptive rule: obligation, permission, prohibition, or right. Deontic modalities apply to actions and prescribe behaviour. NOTE: Constitutive rules are NOT deontic modalities - they describe facts and definitions rather than prescribing actions.
is subClass of

Digital Dimension

IRI: http://data.europa.eu/lomo#DigitalDimension

Definition:
A category for classifying prescriptive rules by their digital dimension: Data, Digital Public Service, or Digital Solutions. Based on the LFDS (Legislative Financial and Digital Statement) Assessment Methodology.
is subClass of

Frequency

IRI: http://data.europa.eu/lomo#Frequency

Definition:
The rate at which a temporal specification recurs or repeats over a specified period of time.
Usage Note
Use Frequency to model recurring obligations such as annual reporting, quarterly filings, or periodic inspections. A Frequency instance specifies the repetition interval using frequencyValue and frequencyUnit properties.
Example
ex:Frequency_Annual rdf:type lomo:Frequency ; rdfs:label "Annually"@en ; lomo:frequencyValue 1 ; lomo:frequencyUnit "year" .
See also
is subClass of
Property Range Definition

Legal Condition

IRI: http://data.europa.eu/lomo#LegalCondition

Definition:
A condition that must be satisfied for a requirement to apply or an action to be triggered.
Usage Note
Legal conditions represent the triggering circumstances or prerequisites for requirements and actions. Common patterns include: 1. TRIGGERING CONDITIONS: Events that activate an obligation or permission Example: 'changes in the types of undertakings in their national law that may affect the accuracy of Annex I or Annex II' 2. QUALIFYING CONDITIONS: Criteria that must be met for a provision to apply Example: 'undertakings other than small undertakings' - limits scope of MS flexibility 3. SEQUENTIAL/TEMPORAL CONDITIONS: Requirements that depend on prior actions Example: 'In such a case' (after notification) - Commission power triggered by MS notification 4. COMPOUND CONDITIONS: Multiple conditions combined (conjunction/disjunction) Example: 'provided that... AND the disclosure requirement is contained in...' Link conditions to requirements via hasCondition property. Capture the exact legal text in legalText property.
Example
ex:Condition_ChangesAffectingAnnexes rdf:type lomo:LegalCondition ; rdfs:label "Changes Affecting Accuracy of Annex I or II"@en ; lomo:legalText "changes in the types of undertakings in their national law that may affect the accuracy of Annex I or Annex II"@en ; rdfs:comment "The obligation is triggered only when national law changes potentially affect the accuracy of the annexes."@en .
is subClass of

Legal Rule

IRI: http://data.europa.eu/lomo#LegalRule

Definition:
Any identifiable fragment of a legal resource (e.g., article, paragraph, point, recital). Serves as the superclass for all discrete legal text fragments that can be classified by their semantic function: prescriptive (PrescriptiveRule) or constitutive (ConstitutiveRule).
Usage Note
LegalRule is the LOMO-native root class for describing rules defined in legal resources. The connection to Mapping to eli:Work is provided via the range of the property lomo:establishedInResource. All legal rules are classified by their normative function: prescriptive rules (PrescriptiveRule), constitutive facts (ConstitutiveRule). In case of uncertainty concerning their classification into one or the other category, use the generic LegalRule class.
is subClass of

Prescriptive Rule

IRI: http://data.europa.eu/lomo#PrescriptiveRule

Definition:
A prescriptive legal norm 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 constitutive rules that establish facts, definitions, or institutional realities without prescribing actions, use ConstitutiveRule instead.
Usage Note
PrescriptiveRule is the core class for modeling PRESCRIPTIVE legal provisions that mandate, permit, or prohibit actions. This class aligns with ELI-LO's LegalNorm concept. Each requirement should specify: 1. hasDeonticModality: The type of normative effect (Obligation, Permission, Prohibition, Right) - NOTE: ConstitutiveRule is NOT a deontic modality 2. hasRequirementType: The functional category (Substantive, Procedural, Implementation, Penalty, etc.) 3. legalText: The verbatim text from the legal source 4. establishedInResource: Reference to the legal source subdivision Optional properties include: produces (for action-producing requirements), hasCondition (for conditional requirements), usesDefinition (for requirements making use of terms). IMPORTANT: For provisions that establish facts, definitions, or institutional realities without prescribing behaviour, use ConstitutiveRule or Definition instead. Deontic modalities (obligation, permission, prohibition) apply to ACTIONS, not to factual statements or definitions.
Example
# 1) Fisheries regulation — data requirements (Article 4(1)) <http://data.europa.eu/lrmo/lfds-fisheries#Requirement_Art4_Par1> rdf:type lomo:PrescriptiveRule ; lomo:hasDeonticModality lomo:Obligation ; lomo:hasRequirementType <http://publications.europa.eu/resource/authority/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:establishedInResource <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 lomo:Obligation ; lomo:hasRequirementType <http://publications.europa.eu/resource/authority/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:establishedInResource <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 lomo:Obligation ; lomo:hasRequirementType <http://publications.europa.eu/resource/authority/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:establishedInResource <https://data.europa.eu/eli/dl/proc/2025/96/cod/doc/com/COM_2025_179/FINAL/art_10/par_2> .
See also
  • Aligned with ELI-LO LegalNorm for prescriptive rules. Now restricted to provisions with deontic modalities (obligation, permission, prohibition, right). For constitutive facts and definitions, see ConstitutiveRule and Definition.
is subClass of
Property Range Definition

Requirement Type

IRI: http://data.europa.eu/lomo#RequirementType

Definition:
The functional or substantive category of a prescriptive rule.
is subClass of

Result Category

IRI: http://data.europa.eu/lomo#ResultCategory

Definition:
The category or type of result produced by an action (e.g., report, certificate, decision, standard).
Usage Note
Create domain-specific ResultCategory instances for different types of outputs. Common types include: reports, notifications, certificates, delegated acts, financial statements, etc. ResultCategory instances should be reusable across multiple ActionResult instances.
Example
ex:AnnualFinancialStatements rdf:type lomo:ResultCategory ; rdfs:label "Annual Financial Statements"@en ; rdfs:comment "Complete financial statements comprising balance sheet, profit and loss account, and notes"@en . ex:Notification rdf:type lomo:ResultCategory ; rdfs:label "Notification"@en .
is subClass of

Role Type

IRI: http://data.europa.eu/lomo#RoleType

Definition:
The type or category of role played by an agent in an action (e.g., bearer, addressee, addresser, beneficiary).
is subClass of

Temporal Function

IRI: http://data.europa.eu/lomo#TemporalFunction

Definition:
The role that a temporal specification plays (e.g., deadline, validity period, starting point).
is subClass of

Temporal Specification

IRI: http://data.europa.eu/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. Use hasInstant, hasInterval, hasDurationSpec to categorize the type. Link temporal specifications via temporal relations (before, after, etc.). Specify function via hasFunction (deadline, validity, startingPoint) when used in prescriptive rules or actions.
See also
  • Inspired by RRMV TemporalEntitySpec and ELI-LO TemporalSpecification.
is subClass of
Property Range Definition

Object Properties

after

IRI: http://data.europa.eu/lomo#after

Definition:
Indicates that one temporal specification occurs after another.

at time

IRI: http://data.europa.eu/lomo#atTime

Definition:
Specifies the temporal constraints between two entities
Usage Note
Can be used on both Action instances (to specify when an action must/may occur) and on PrescriptiveRule instances (to specify when the requirement is applicable or triggers). Domain is intentionally unspecified to allow flexibility.
Example
ex:Action_InformCommission lomo:atTime ex:TemporalSpec_ReasonablePeriod .
has range
Temporal Specification

before

IRI: http://data.europa.eu/lomo#before

Definition:
Indicates that one temporal specification occurs before another.

defines

IRI: http://data.europa.eu/lomo#defines

Definition:
Links a definition to the concept, term, or agent it defines.
has domain
Definition

established in resource

IRI: http://data.europa.eu/lomo#establishedInResource

Definition:
Links any Legal Rule (PrescriptiveRule, ConstitutiveRule, Definition, or Action) to the specific subdivision of a legal resource where it is established.
Usage Note
This property applies to all classes under Legal Rule (PrescriptiveRule, ConstitutiveRule, Definition) as well as Action. It provides provenance by linking to the source legal text subdivision; mappings to the CDM fragment class are provided here.

finished by

IRI: http://data.europa.eu/lomo#finishedBy

Definition:
Indicates that one temporal specification has its end point at the same moment as another (inverse of finishes).

finishes

IRI: http://data.europa.eu/lomo#finishes

Definition:
Indicates that one temporal specification ends at the same moment as another.

for agent

IRI: http://data.europa.eu/lomo#forAgent

Definition:
Specifies the agent or agent type who plays a particular role. Can reference either a specific Agent (named entity) or an AgentType (category of entities).
has domain
Agent Role
has range
Agent or Agent Type

has agent role

IRI: http://data.europa.eu/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: bearer (who performs/bears obligation), addressee (recipient of communication), addresser (sender), beneficiary (who benefits). An action may have multiple agent roles for different participants.
Example
ex:Action_InformCommission lomo:hasAgentRole ex:AgentRole_MS_Informer , ex:AgentRole_Commission_Informed . ex:AgentRole_MS_Informer lomo:forAgent ex:MemberStates ; lomo:withRole lomo:addresser . ex:AgentRole_Commission_Informed lomo:forAgent ex:Commission ; lomo:withRole lomo:addressee .
has domain
Action
has range
Agent Role

has category

IRI: http://data.europa.eu/lomo#hasCategory

Definition:
Links a requirement or action to a digital dimension category from the Digital Dimensions scheme.
See also
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
ex:Requirement_Art4_DataRequirements lomo:hasCategory lomo:Data , lomo:DigitalPublicService . ex:Requirement_Art5_ObservationData lomo:hasCategory lomo:Observation .
has domain
Prescriptive Rule
has range
Digital Dimension

has condition

IRI: http://data.europa.eu/lomo#hasCondition

Definition:
Relates a requirement or action to a condition that must be satisfied for it to apply or be triggered.
Usage Note
Conditions specify WHEN requirements apply or WHEN actions are triggered. Domain is intentionally unspecified to allow use on both: - PrescriptiveRule: specifies when the requirement applies (e.g., 'obligation triggered when changes occur') - Action: specifies preconditions for the action (e.g., 'action only after notification received') A requirement/action may have MULTIPLE conditions: - Conjunctive (AND): all conditions must be met - Disjunctive (OR): any condition triggers Four condition types: 1. TRIGGERING: Events that activate obligation/permission ('when changes occur...') 2. QUALIFYING: Limits scope of application ('undertakings other than small undertakings') 3. SEQUENTIAL: Depends on prior actions ('In such a case' - after notification) 4. COMPOUND: Multiple conditions combined ('provided that X AND Y') The legalText property on the LegalCondition should capture the exact wording from the legal source.
Example
# Linking requirement to condition ex:Requirement_Art1_Par2_InformCommission lomo:hasCondition ex:Condition_ChangesAffectingAnnexes . # The condition itself ex:Condition_ChangesAffectingAnnexes rdf:type lomo:LegalCondition ; rdfs:label "Changes Affecting Accuracy of Annex I or II"@en ; lomo:legalText "changes in the types of undertakings in their national law that may affect the accuracy of Annex I or Annex II"@en ; rdfs:comment "The obligation is triggered only when national law changes potentially affect the annexes."@en .
has range
Legal Condition

has deontic modality

IRI: http://data.europa.eu/lomo#hasDeonticModality

Definition:
Relates a prescriptive rule to its deontic character (obligation, permission, prohibition, or right). NOTE: This property does NOT apply to ConstitutiveRule or Definition instances, as constitutive rules describe facts rather than prescribe actions.
has domain
Prescriptive Rule
has range
Deontic Modality

has duration specification

IRI: http://data.europa.eu/lomo#hasDurationSpec

Definition:
Links to a temporal specification representing a length of time.
Usage Note
Use this to indicate that something refers to or is based on a duration (length of time without fixed start/end).
has range
Temporal Specification

has end

IRI: http://data.europa.eu/lomo#hasEnd

Definition:
Specifies the ending point of a temporal specification (typically an interval).
Usage Note
Links an interval temporal specification to another temporal specification representing its end point.
has range
Temporal Specification

has frequency

IRI: http://data.europa.eu/lomo#hasFrequency

Definition:
Specifies the frequency at which a temporal specification repeats.
See also
Usage Note
Use this property on TemporalSpecification instances to specify periodic intervals. Actions inherit frequency through their :atTime relationship to temporal specifications. For example, an action that must be performed annually has an :atTime link to a TemporalSpecification with :hasFrequency pointing to a Frequency instance.
Example
# Correct pattern: Frequency through temporal specification ex:Action_SubmitStatistics lomo:atTime ex:TemporalSpec_AnnualDeadline . ex:TemporalSpec_AnnualDeadline lomo:hasFrequency ex:Frequency_Annual . ex:Frequency_Annual rdf:type lomo:Frequency ; lomo:frequencyValue 1 ; lomo:frequencyUnit "year" .
has domain
Temporal Specification
has range
Frequency

has function

IRI: http://data.europa.eu/lomo#hasFunction

Definition:
Specifies the function of a temporal specification (e.g., deadline, validity, starting point).
has domain
Temporal Specification
has range
Temporal Function

has instant

IRI: http://data.europa.eu/lomo#hasInstant

Definition:
Links to a temporal specification representing a specific point in time.
Usage Note
Use this to indicate that something refers to or is based on a specific instant (point in time).
has range
Temporal Specification

has interval

IRI: http://data.europa.eu/lomo#hasInterval

Definition:
Links to a temporal specification representing a period with start and end points.
Usage Note
Use this to indicate that something refers to or is based on an interval (time period).
has range
Temporal Specification

has next

IRI: http://data.europa.eu/lomo#hasNext

Definition:
Indicates that one action is followed by another action in a sequence.
Example
ex:Action_SubmitDraft lomo:hasNext ex:Action_PublishFinal
has domain
Action
has range
Action

has referent class

IRI: http://data.europa.eu/lomo#hasReferentClass

Definition:
Points to the class of non-symbolic referents to which the definiens descriptively refers. This property establishes the semantic (not merely syntactic) definitional relation by connecting the definition to actual entities, properties, or phenomena in the world. The relation between definiens and referent class is non-symmetrical.
has domain
Definition
has range
http://www.w3.org/2002/07/owl#Class

has requirement type

IRI: http://data.europa.eu/lomo#hasRequirementType

Definition:
Relates a prescriptive rule to its functional or substantive category (e.g., substantive, procedural, implementation and oversight, penalty). A requirement may have multiple types if it serves multiple functions.
Example
Preferred external concept IRIs (examples): - http://publications.europa.eu/resource/authority/administrative-obligation/c_80214a02 (Reporting) - http://publications.europa.eu/resource/authority/administrative-obligation/c_39b9f824 (Notification)
has domain
Prescriptive Rule

has result

IRI: http://data.europa.eu/lomo#hasResult

Definition:
Links an action to the result(s) it produces, which can be specific ActionResult instances or ActionResultType categories.
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). Since dcat:Dataset is a subclass of ActionResult, this property can directly link actions to datasets for data-related outputs.
Example
ex:Action_PrepareFinancialStatements lomo:hasResult ex:Result_FinancialStatements_2024 . ex:Action_Audit lomo:hasResult ex:AuditReportType .
has domain
Action
has range
Action Result or Action Result Type

has result category

IRI: http://data.europa.eu/lomo#hasResultCategory

Definition:
Specifies the category of a result.
has domain
Action Result or Action Result Type
has range
Result Category

has start

IRI: http://data.europa.eu/lomo#hasStart

Definition:
Specifies the starting point of a temporal specification (typically an interval).
Usage Note
Links an interval temporal specification to another temporal specification representing its start point.
has range
Temporal Specification

immediately after

IRI: http://data.europa.eu/lomo#immediatelyAfter

Definition:
Indicates that one temporal specification begins immediately when another ends.

immediately before

IRI: http://data.europa.eu/lomo#immediatelyBefore

Definition:
Indicates that one temporal specification ends immediately when another begins.

in

IRI: http://data.europa.eu/lomo#in

Definition:
Indicates that one temporal specification occurs entirely within the boundaries of another.

involves process

IRI: http://data.europa.eu/lomo#involvesProcess

Definition:
Links a requirement or action to the high-level process(es) it involves or contributes to.
Usage Note
Used to classify requirements by the high-level processes they relate to (e.g., 'Data Collection', 'Data Transmission', 'Data Reuse', 'Data Processing', 'Data Quality Verification'). Multiple processes can be assigned.
Example
ex:Requirement_Art4 lomo:involvesProcess ex:Process_DataCollection , ex:Process_DataTransmission .
has range
http://www.w3.org/2004/02/skos/core#Concept

is composed of

IRI: http://data.europa.eu/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
ex:FinancialStatementsType lomo:isComposedOf ex:BalanceSheetType , ex:ProfitLossAccountType , ex:NotesType .
has domain
Action Result or Action Result Type
has range
Action Result or Action Result Type

is manifested in

IRI: http://data.europa.eu/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 a result instance or a result type to the dataset that contains or represents it (e.g., report dataset, published dataset). Prefer datasets represented as dcat:Dataset.
Example
ex:Result_AnnualReport2025_Interoperability lomo:isManifestedIn ex:Dataset_InteroperabilityReport2025
has domain
Action Result or Action Result Type
has range
http://www.w3.org/ns/dcat#Dataset

manifests

IRI: http://data.europa.eu/lomo#manifests

Definition:
Inverse of :isManifestedIn; relates a dcat:Dataset to the ActionResult(s) it manifests.
Example
ex:Dataset_InteroperabilityReport2025 lomo:manifests ex:Result_AnnualReport2025_Interoperability
has domain
http://www.w3.org/ns/dcat#Dataset
has range
Action Result or Action Result Type

meets

IRI: http://data.europa.eu/lomo#meets

Definition:
Indicates that one temporal specification ends exactly when another begins, without any gap or overlap.

overlaps

IRI: http://data.europa.eu/lomo#overlaps

Definition:
Indicates that two temporal entities specifications share a common portion of time without either completely containing the other.

precedes

IRI: http://data.europa.eu/lomo#precedes

Definition:
Indicates that one action must occur before another action.
has domain
Action
has range
Action

produces

IRI: http://data.europa.eu/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 and Definition instances do NOT produce actions - they constitute facts or define terms.
Example
ex:Requirement_Art1_Par2_InformCommission lomo:produces ex:Action_InformCommissionOfChanges .
has domain
Prescriptive Rule
has range
Action

references

IRI: http://data.europa.eu/lomo#references

Definition:
Relates a prescriptive rule to a digital resource (dataset, standard, software, service) that is referenced, cited, or pointed to by the requirement.
See also
Usage Note
Use this property to link requirements to the digital resources they mention, cite, or relate to. This is semantically distinct from 'requires' (dependency) - 'references' indicates a citation or relationship without implying that the requirement cannot exist without the resource. 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
Example
# 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 .
has domain
Prescriptive Rule
has range
http://www.w3.org/ns/dcat#Resource

started by

IRI: http://data.europa.eu/lomo#startedBy

Definition:
Indicates that one temporal specification has its beginning point at the same moment as another (inverse of starts).

starts

IRI: http://data.europa.eu/lomo#starts

Definition:
Indicates that one temporal specification begins at the same moment as another.

uses definition

IRI: http://data.europa.eu/lomo#usesDefinition

Definition:
Indicates that a requirement, action, agent, result, or digital resource relies upon or references a particular definition for its interpretation or application.
Usage Note
Use this property to link entities that DEPEND ON or REFERENCE existing definitions for their meaning or application. 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; :usesDefinition should be used to reference existing Definition instances. Key notes: - Definitions are modeled as :Definition instances (subclass of :ConstitutiveRule). - :usesDefinition → Any entity RELIES ON/REFERENCES an existing Definition. Note: Prescriptive rules (PrescriptiveRule) can use :usesDefinition to reference the definitions they depend on. Applicable domains (intentionally unspecified for flexibility): 1. PrescriptiveRule: Links prescriptive requirements to definitions they rely upon for interpretation 2. ConstitutiveRule: Links constitutive rules to definitions they reference 3. Action: Links actions to definitions that scope or qualify the action 4. Agent/AgentType: Links agents to definitions that define their category or status 5. ActionResult: Links results to definitions that specify output characteristics or formats 6. dcat:Dataset: Links datasets to definitions that specify data content or scope 7. dcterms:Standard: Links standards to definitions of terms they implement 8. cpsv:PublicService: Links services to definitions of entities they serve or processes they implement Common patterns: - Substantive requirements using defined terms (e.g., 'public-interest entities shall...') - Size-based exemptions referencing size category definitions - Cross-references to definitions in other articles or external standards - Actions that apply only to defined categories of entities - Datasets whose content is scoped by legal definitions - Standards that implement legally defined concepts - Services targeting legally defined categories of users A single entity may use MULTIPLE definitions when its interpretation depends on several defined terms.
Example
# Requirement using multiple definitions for interpretation ex:Requirement_Art17_Par1 rdf:type lomo:PrescriptiveRule ; lomo:hasDeonticModality lomo:Obligation ; lomo:hasRequirementType <http://publications.europa.eu/resource/authority/administrative-obligation> ; lomo:legalText "Public-interest entities shall include in the management report a corporate governance statement..."@en ; lomo:usesDefinition ex:Def_PublicInterestEntity , ex:Def_ManagementReport ; rdfs:comment "This requirement uses the definitions of 'public-interest entity' and 'management report' to determine its scope and application."@en . # Action scoped by a definition ex:Action_PrepareConsolidatedStatements lomo:usesDefinition ex:Def_ParentUndertaking ; rdfs:comment "The action of preparing consolidated statements applies based on the definition of parent undertaking."@en . # AgentType linked to its defining criteria ex:SmallUndertakings rdf:type lomo:AgentType ; lomo:usesDefinition ex:Def_SmallUndertakings ; rdfs:comment "This agent type is defined by the criteria in the Small Undertakings definition."@en . # ActionResult using definitions for output specification ex:Result_ConsolidatedFinancialStatements rdf:type lomo:ActionResult ; rdfs:label "Consolidated Financial Statements"@en ; lomo:usesDefinition ex:Def_GroupUndertaking , ex:Def_SubsidiaryUndertaking ; rdfs:comment "The consolidated statements must include entities meeting these definitions."@en . # Dataset scoped by legal definitions ex:Dataset_PIE_DisclosureData rdf:type dcat:Dataset ; dcterms:title "Public Interest Entity Disclosure Dataset"@en ; lomo:usesDefinition ex:Def_PublicInterestEntity , ex:Def_MaterialInformation ; rdfs:comment "Dataset contains disclosures from entities meeting the PIE definition, with materiality determined by the Material Information definition."@en . # Standard implementing defined concepts ex:Standard_SME_AccountingRules rdf:type dcterms:Standard ; dcterms:title "SME Accounting Standard"@en ; lomo:usesDefinition ex:Def_SmallUndertakings , ex:Def_MediumUndertakings ; rdfs:comment "This standard applies to undertakings meeting the small or medium size definitions."@en . # Public service targeting defined entity categories ex:Service_PIE_AuditOversight rdf:type cpsv:PublicService ; dcterms:title "Public Interest Entity Audit Oversight Service"@en ; lomo:usesDefinition ex:Def_PublicInterestEntity , ex:Def_StatutoryAudit ; rdfs:comment "This oversight service applies to statutory audits of public-interest entities as defined in the Directive."@en .
has range
Definition

with role

IRI: http://data.europa.eu/lomo#withRole

Definition:
Specifies the type of role played by an agent.
has domain
Agent Role
has range
Role Type

Datatype Properties

durationdp

IRI: http://data.europa.eu/lomo#duration

Definition:
A duration value expressed using xsd:duration.
has range
http://www.w3.org/2001/XMLSchema#duration

frequencydp

IRI: http://data.europa.eu/lomo#frequency

Definition:
A frequency indication as an xsd:duration expressing the elapsed time between occurrences.
has range
http://www.w3.org/2001/XMLSchema#duration

frequency unitdp

IRI: http://data.europa.eu/lomo#frequencyUnit

Definition:
The time unit for the frequency (e.g., 'year', 'month', 'quarter', 'day').
has domain
Frequency
has range
http://www.w3.org/2001/XMLSchema#string

frequency valuedp

IRI: http://data.europa.eu/lomo#frequencyValue

Definition:
The numeric value of the frequency (e.g., 1 for annual, 2 for biennial, 4 for quarterly).
has domain
Frequency
has range
http://www.w3.org/2001/XMLSchema#integer

has annotationdp

IRI: http://data.europa.eu/lomo#hasAnnotation

Definition:
A human-readable annotation or note explaining an element.
has range
http://www.w3.org/1999/02/22-rdf-syntax-ns#langString

has capabilitydp

IRI: http://data.europa.eu/lomo#hasCapability

Definition:
Describes a technical function or capability that a digital solution (software) provides.
has domain
http://purl.org/dc/terms/Software
has range
http://www.w3.org/1999/02/22-rdf-syntax-ns#langString

has definiendumdp

IRI: http://data.europa.eu/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 domain
Definition
has range
http://www.w3.org/1999/02/22-rdf-syntax-ns#langString

has definiensdp

IRI: http://data.europa.eu/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 domain
Definition
has range
http://www.w3.org/1999/02/22-rdf-syntax-ns#langString

has purposedp

IRI: http://data.europa.eu/lomo#hasPurpose

Definition:
Describes the objective, mission, or intended outcome of a public service or public action.
has domain
http://purl.org/vocab/cpsv#PublicService
has range
http://www.w3.org/1999/02/22-rdf-syntax-ns#langString

has referent descriptiondp

IRI: http://data.europa.eu/lomo#hasReferentDescription

Definition:
A textual description of the class of non-symbolic referents when a formal owl:Class is not available or appropriate. Used to capture the extensional meaning of the definition.
has domain
Definition
has range
http://www.w3.org/1999/02/22-rdf-syntax-ns#langString

instantdp

IRI: http://data.europa.eu/lomo#instant

Definition:
A specific date or datetime value for a point in time.
has range
http://www.w3.org/2001/XMLSchema#dateTime

is semantic definitiondp

IRI: http://data.europa.eu/lomo#isSemanticDefinition

Definition:
Boolean flag indicating whether this is a semantic (triadic) definition that includes reference to a class of non-symbolic referents (true), or a purely syntactic (dyadic) definition that only relates symbols (false).
has domain
Definition
has range
http://www.w3.org/2001/XMLSchema#boolean

is unspecifieddp

IRI: http://data.europa.eu/lomo#isUnspecified

Definition:
Boolean flag indicating whether the temporal entity is undefined or depends on external factors.
has range
http://www.w3.org/2001/XMLSchema#boolean

legal textdp

IRI: http://data.europa.eu/lomo#legalText

Definition:
The verbatim text from the legal source.
has range
http://www.w3.org/1999/02/22-rdf-syntax-ns#langString

repetitionsdp

IRI: http://data.europa.eu/lomo#repetitions

Definition:
A fixed number of repetitions for a recurring temporal specification.
has range
http://www.w3.org/2001/XMLSchema#integer

temporal labeldp

IRI: http://data.europa.eu/lomo#temporalLabel

Definition:
The name or label of an event or period referenced in the temporal specification.
has range
http://www.w3.org/1999/02/22-rdf-syntax-ns#langString

term labeldp

IRI: http://data.europa.eu/lomo#termLabel

Definition:
The exact label of a defined term as it appears in the legal text.
has domain
Definition
has range
http://www.w3.org/1999/02/22-rdf-syntax-ns#langString

trigger descriptiondp

IRI: http://data.europa.eu/lomo#triggerDescription

Definition:
A textual description of the event that triggers the start of an action or the application of a requirement.
has range
http://www.w3.org/1999/02/22-rdf-syntax-ns#langString

Controlled Vocabularies

This section is non-normative.

The usage of controlled vocabularies in LOMO conforms to the best practices set by the Publications Office. In the context of this specification, classes mapped on the URI skos:Concept always indicate the usage of some controlled vocabulary.

In addition, the following controlled vocabularies MUST be used for the properties listed below. In this document, "MUST be used" means that the value space of the property is closed to terms from the specified controlled vocabulary; validation systems SHOULD report errors when values fall outside that space.

The controlled vocabularies are defined as part of the LOMO ontology and enforced through SHACL validation shapes (see lrmo-shapes.ttl).

Controlled Vocabulary Usage Table

Controlled Vocabulary Scheme Used for Property Used for Class Codes are instances of Usage Note
Deontic Modality Scheme
Deontic Modality Controlled Vocabulary 		has deontic modality Deontic Modality
Digital Dimensions Scheme
Digital Dimensions Controlled Vocabulary 		has category Digital Dimension
Result Category Scheme
Result Category Controlled Vocabulary 		http://www.w3.org/2004/02/skos/core#hasTopConcept Result Category Scheme Result Category
Role Type Scheme
Role Type Controlled Vocabulary 		http://www.w3.org/2004/02/skos/core#hasTopConcept Role Type Scheme Role Type
Temporal Function Scheme
Temporal Function Controlled Vocabulary 		http://www.w3.org/2004/02/skos/core#hasTopConcept Temporal Function Scheme Temporal Function

Concepts

Obligation

IRI: http://data.europa.eu/lomo#Obligation

Type: http://data.europa.eu/lomo#DeonticModality

Definition:

A requirement that mandates an action must be performed.
Usage Note
Use for provisions that impose a duty to act. Linguistic indicators include: 'shall', 'must', 'is required to', 'has the obligation to'. The bearer of the obligation must perform the prescribed action.
Example
"Member States shall inform the Commission within a reasonable period of time..." - obligation on MS to notify Commission of changes.

Permission

IRI: http://data.europa.eu/lomo#Permission

Type: http://data.europa.eu/lomo#DeonticModality

Definition:

A requirement that allows an action may be performed.
Usage Note
Use for provisions that grant authority or discretion to act. Linguistic indicators include: 'may', 'shall be empowered to', 'is permitted to', 'is authorized to'. The agent has discretion whether to perform the action. Note: 'shall be empowered' grants permission/authority, NOT an obligation.
Example
"The Commission shall be empowered to adapt, by means of delegated acts..." - permission granting authority to Commission (not obligation to act).

Prohibition

IRI: http://data.europa.eu/lomo#Prohibition

Type: http://data.europa.eu/lomo#DeonticModality

Definition:

A requirement that forbids an action from being performed.
Usage Note
Use for provisions that prevent or forbid actions. Linguistic indicators include: 'shall not', 'must not', 'is prohibited from', 'may not'. The agent is forbidden from performing the specified action.
Example
"Distribution costs shall not be included" - prohibition on including certain costs in production cost calculation.

Right

IRI: http://data.europa.eu/lomo#Right

Type: http://data.europa.eu/lomo#DeonticModality

Definition:

A legal entitlement that empowers an agent to demand a certain performance or to refrain from interference.
Usage Note
Use for provisions that establish legal entitlements or claims. Unlike permissions (which allow action), rights create corresponding duties in others. Linguistic indicators include: 'has the right to', 'is entitled to', 'without prejudice to their rights'.
Example
"...without prejudice to their rights as shareholders" - preserves shareholder rights while defining financial holding undertakings.

Data

IRI: http://data.europa.eu/lomo#Data

Type: http://data.europa.eu/lomo#DigitalDimension

Definition:

Category for requirements related to data collection, transmission, storage, quality, and reuse. Includes requirements about datasets, data formats, data standards, and data governance.
Usage Note
Use this category for requirements that: - Mandate collection or transmission of specific data - Specify data quality standards or validation rules - Define data formats, structures, or schemas - Establish data sharing or reuse obligations - Set data retention or archiving requirements - Reference specific datasets or data types

Digital Public Service

IRI: http://data.europa.eu/lomo#DigitalPublicService

Type: http://data.europa.eu/lomo#DigitalDimension

Definition:

Category for requirements related to digital public services, including statistical services, information dissemination, citizen-facing portals, and administrative e-services.
Usage Note
Use this category for requirements that: - Establish or mandate digital public services - Define service levels or availability requirements - Specify public access to information or data - Require provision of online administrative services - Mandate interoperability between public services - Define user rights or service guarantees

Digital Solutions

IRI: http://data.europa.eu/lomo#DigitalSolutions

Type: http://data.europa.eu/lomo#DigitalDimension

Definition:

Category for requirements related to digital infrastructure, software systems, technical platforms, and IT solutions that support the implementation of legal obligations.
Usage Note
Use this category for requirements that: - Mandate specific software systems or platforms - Define technical infrastructure requirements - Specify system interoperability standards - Require use of particular technologies or tools - Establish technical security or reliability standards - Reference databases, registers, or information systems

Observation

IRI: http://data.europa.eu/lomo#Observation

Type: http://data.europa.eu/lomo#DigitalDimension

Definition:

Category for requirements that establish specific data values, measurements, rates, thresholds, or other discrete data points that must be recorded, transmitted, or processed by digital systems. Aligned with qb:Observation from the W3C RDF Data Cube Vocabulary / SDMX.
Usage Note
Use this category for requirements that: - Define specific rates, percentages, or thresholds (e.g., duty rates, tax rates, limits) - Establish reference values that systems must use for calculations - Mandate recording of discrete measurements or observations - Specify coded values (e.g., TARIC codes, classification codes) - Define authoritative data points that must be exchanged between systems This is a subconcept of Data, specifically for discrete, well-defined data points rather than broader data management or dataset requirements. Alignment: This concept corresponds to qb:Observation in the W3C RDF Data Cube Vocabulary (http://purl.org/linked-data/cube#Observation), which is the RDF representation of SDMX statistical observations.
See also

certificate

IRI: http://data.europa.eu/lomo#certificate

Type: http://data.europa.eu/lomo#ResultCategory

Definition:

A result category representing an official document certifying a particular fact.

report

IRI: http://data.europa.eu/lomo#report

Type: http://data.europa.eu/lomo#ResultCategory

Definition:

A result category representing a structured document containing information.

addressee

IRI: http://data.europa.eu/lomo#addressee

Type: http://data.europa.eu/lomo#RoleType

Definition:

The agent to whom a request or communication is directed.

addresser

IRI: http://data.europa.eu/lomo#addresser

Type: http://data.europa.eu/lomo#RoleType

Definition:

The agent who sends a request or communication.

bearer

IRI: http://data.europa.eu/lomo#bearer

Type: http://data.europa.eu/lomo#RoleType

Definition:

The agent who carries the responsibility or obligation.

beneficiary

IRI: http://data.europa.eu/lomo#beneficiary

Type: http://data.europa.eu/lomo#RoleType

Definition:

The agent who benefits from an action.

deadline

IRI: http://data.europa.eu/lomo#deadline

Type: http://data.europa.eu/lomo#TemporalFunction

Definition:

A temporal function indicating the latest time by which an action must be completed.

starting point

IRI: http://data.europa.eu/lomo#startingPoint

Type: http://data.europa.eu/lomo#TemporalFunction

Definition:

A temporal function indicating when an action may or must begin.

validity

IRI: http://data.europa.eu/lomo#validity

Type: http://data.europa.eu/lomo#TemporalFunction

Definition:

A temporal function indicating the period during which a requirement is effective.