How to read a principle

Every principle page has the same structure. The table below shows where each part comes from in the RDF master file. The properties are described in the Data model.

Part of the page

What it tells you

RDF property

Title

Short name of the principle.

dct:title

Statement

The rule itself, in one or two sentences.

elap:statement

Rationale

Why the principle matters and the benefits of applying it.

elap:rationale

Implications

What organisations have to do - at business and technical level - to apply it.

elap:implications

Category

Stage of the digital public service life it applies to.

elap:category

Interoperability layers

EIF layers (legal, organisational, semantic, technical) the principle affects.

dcat:theme

Governance model

Public administration governance model the principle belongs to.

elap:paGovernance

Influence on DPS lifecycle / attributes

Whether applying the principle is an obligation or a desire.

elap:influenceInDPSLifecycle, elap:influenceInDPSAttribute

Scope

Business domain the principle applies to.

eira:scope

Related EIRA elements

EIRA content areas and Architecture Building Blocks the principle is related to.

elap:relatedContent, elap:associatedABB

Source

Reference(s) the principle is based on, with a note on why it is relevant.

dct:source, elap:aboutSource

The values used in the metadata are explained in the Glossary.