Data model

Conceptual model (T-Box) of ELAP. ELAP is published as a dcat:Catalog whose members are architecture principles, modelled as a specialisation of dcat:Resource.

Ontology

http://data.europa.eu/2sa/elap/ontology

Version

1.0.0

Last modified

19 November 2026

The library is a dcat:Catalog that lists its principles with elap:principle. Each principle is an elap:Principle, a specialisation of dcat:Resource. It reuses dct:title, eira:scope, dct:source (a dct:BibliographicResource with its own dct:title) and dcat:theme (interoperability layer) and adds the ELAP properties below. Classification values are concepts of the ELAP code lists (see Glossary).

Classes

elap:Principle

A qualitative statement of intent that should be met by the architecture of a digital public service, catalogued in ELAP with its statement, rationale and implications.

Subclass of: dcat:Resource

Note: Specialises dcat:Resource following the DCAT 3 extension pattern for catalogues of resources other than datasets and data services. Principles are individuals (A-Box), not classes.

Change from 3.1.0: In ELAP 3.1.0 principles were also typed owl:Class (punning). They are individuals only.

Properties

Property

Definition

Domain → range

Change from 3.1.0

elap:principle

An architecture principle listed in the library. Specific sub-property of dcat:resource, as DCAT 3 recommends when available.

dcat:Catalog → elap:Principle

New

elap:statement (single value)

A brief statement that helps to detect and identify the purpose of the principle.

elap:Principle → rdf:langString

Replaces the first of the three dct:description values used in ELAP 3.1.0.

elap:rationale (single value)

Text describing the business benefits of adhering to the principle.

elap:Principle → rdf:langString

Replaces the second of the three dct:description values used in ELAP 3.1.0.

elap:implications (single value)

Text describing the requirements for both business and technical aspects of applying the principle.

elap:Principle → rdf:langString

Replaces the third of the three dct:description values used in ELAP 3.1.0.

elap:category (single value)

Digital public service category of the principle (governance, implementation or strategy), conforming to ITIL.

elap:Principle → skos:Concept

Replaces elap:Category (literal value) used in ELAP 3.1.0.

elap:paGovernance (single value)

Public administration governance paradigm the principle relates to: New Public Management, New Public Governance, New Weberian State, or Common to all.

elap:Principle → skos:Concept

Value type changed from literal (ELAP 3.1.0) to skos:Concept.

elap:influenceInDPSLifecycle (single value)

Whether the principle is an obligation (legal requirement) or a desire across the whole life-cycle of the digital public service.

elap:Principle → skos:Concept

Value type changed from literal (ELAP 3.1.0) to skos:Concept.

elap:influenceInDPSAttribute (single value)

Whether the principle is an obligation, a desire, or not applicable for specific attributes or features of the implemented digital public service.

elap:Principle → skos:Concept

Value type changed from literal (ELAP 3.1.0) to skos:Concept.

elap:relatedContent

Interoperability content area (per interoperability layer, governance or functional) the principle relates to.

elap:Principle → skos:Concept

Replaces dct:relation values that were literals (”… Content”) in ELAP 3.1.0.

elap:associatedABB

EIRA Architecture Building Block associated with the principle, identified by its EIRA PURI. No range is asserted: EIRA ABBs are classes in the EIRA ontology, so the link is an OWL 2 punning reference to the ABB IRI.

elap:Principle → —

Replaces dct:relation values that were EIRA IRIs in ELAP 3.1.0.

elap:aboutSource

References, examples or descriptions clarifying how the source supports the principle. Kept on the principle, not on the source: the same source is cited by several principles with different explanations.

elap:Principle → rdf:langString

Replaces rdfs:comment as used in ELAP 3.1.0.