BP02B - Manage vocabularies
To help understand the content of this document, readers should familiarize themselves with the key definitions and actors.
Overview
To help understand the content of this document, readers should familiarize themselves with the key definitions and actors.
Vocabulary Management is part of BP02 – Set-up and configuration of data space Governance Authority process. It outlines the management of vocabularies within a data space, enabling semantic interoperability of data structures across domains and data providers. Vocabulary management governs the lifecycle of vocabularies native to the data space, while also enabling the registration and use of external vocabularies.
Actors
The following actors are involved:
- Governance Authority
Assumptions
The following assumptions are made:
- Vocabularies are managed by the Governance Authority and centrally stored in the Vocabulary Hub. The DSSC specification link: https://dssc.eu/space/BBE/178422433/Specifications+-+Data+Models#Vocabulary-hub.
- Providers can propose (e.g. via email) well-documented modifications to a vocabulary, including proposed metadata, rationale, and potential impact analysis, and suggest adjustments based on their expertise or requirements. Interactions with other data spaces (not part of this BP) can also trigger the need of vocabulary updates.
- External vocabularies - such as industry-standard or domain-specific ones, can be referenced within the data space. These vocabularies are not hosted by Simpl-Open by default but can be linked from authoritative external sources or uploaded if necessary. Simpl-Open does not have control over these external vocabularies. Any vocabulary not explicitly uploaded into Simpl-Open is considered external.
Prerequisites
The following prerequisites must be fulfilled:
- Governance Authority setup: the Governance Authority must be setup before they can manage any vocabulary (Business Process 02A).
- Governance Authority configure: the Governance Authority must be configured before they can manage any vocabulary (Business Process 02B).
Details
The following shows the detailed business process diagram and gives the step descriptions.
Trigger vocabulary management
The Governance Authority reviews existing vocabularies and decides whether to create or import a new vocabulary, introduce a new version of an existing vocabulary, or deprecate an outdated one.
BP02B.01 – Create new vocabulary
The Governance Authority creates a new vocabulary (e.g., using RDF Schema or OWL). The new vocabulary is developed according to defined syntactic and structural rules, including metadata, which ensure consistency, compatibility, and proper validation across schemas.
BP02B.02 – Validate vocabulary
The vocabulary is verified through both syntax and semantic validation. While syntax validation is fully automated, semantic validation is performed through a combination of automated checks and manual review.
BP02B.03 – Publish vocabulary
Once successfully validated, the new or updated vocabulary is published, and the previous version is immediately marked as deprecated.
BP02B.04 – Create new version of vocabulary
The Governance Authority selects an existing vocabulary and creates a new version to incorporate changes, enhancements, or stakeholder input.
BP02B.05 – Deprecate vocabulary version
A vocabulary version is deprecated when it is no longer aligned with current business needs, has been replaced by an updated version, or is no longer applicable for future use.
Deprecation can occur in two scenarios:
Version Update: When a new or updated version of a vocabulary is published, the previous version is automatically deprecated. While deprecated, it remains accessible to support legacy schemas, ensuring system continuity and backward compatibility. Access to deprecated versions is maintained either indefinitely or according to a defined sunset policy, depending on governance decisions.
Full Vocabulary Deprecation: In cases where the entire vocabulary is deemed obsolete or irrelevant to ongoing business processes, all versions of that vocabulary are deprecated. This means it is no longer recommended for use in any context, and future schema development should not reference it.
Important Note:
Deprecation does not mean deletion. Deprecated vocabularies remain available for reference and maintenance of existing implementations. However, they are no longer recommended for use in new development or integration efforts.
BP02B.06 – Send validation notification
Simpl-Open sends a report to the Governance Authority highlighting any validation issues detected in the vocabulary.
Outcomes
Vocabulary version published, updated or deprecated: A new or updated vocabulary is provided to support semantic schema validation. Over time, an older vocabulary version may be deprecated when it is replaced by a newer version.
- Report related to invalid vocabulary sent: Simpl-Open sends a report to the Governance Authority detailing any validation issues found in the vocabulary. If issues are present, the vocabulary is not published or updated.
| Business Process | Status: Proposed |
High Level Requirements
2B.1 - The Governance Authority consults vocabularies
Simpl-Open shall allow the Governance Authority to consult the existing ...
See more details2B.2 - The Governance Authority creates a new vocabulary
Simpl-Open shall allow the Governance Authority to create a ...
See more details2B.3 - The Governance Authority creates a new version of a vocabulary
Simpl-Open shall allow the Governance Authority to create a new ...
See more details2B.4 - The Governance Authority validates a new vocabulary or a new version of a vocabulary
Simpl-Open shall allow the Governance Authority to validate a new ...
See more details2B.5 - The Governance Authority publishes a new vocabulary or a new version of a vocabulary
Simpl-Open shall support the Governance authority to publish a ...
See more details2B.6 - The Governance Authority deprecates a vocabulary
Simpl-Open shall allow the Governance Authority to deprecate a ...
See more details
Please log in or sign up to comment.