Main Page: Difference between revisions
| Line 63: | Line 63: | ||
To reach the communities goal of '''true interoperability''' every semantic definition which has its origin (mandatory property origin = 'internal') in the Semantic Hub is published unter [https://creativecommons.org/publicdomain/zero/1.0/deed.en Creative Commons CC0 1.0 Universal]. | To reach the communities goal of '''true interoperability''' every semantic definition which has its origin (mandatory property origin = 'internal') in the Semantic Hub is published unter [https://creativecommons.org/publicdomain/zero/1.0/deed.en Creative Commons CC0 1.0 Universal]. | ||
Definitions with an external origin (mandatory property origin = 'external') might be subject to other licenses that must be adhered to. Definition items with external origin must be linked to a StandardizationBody item, which provides more information about the body taking care of the definition. This includes also information about the | Definitions with an external origin (mandatory property origin = 'external') might be subject to other licenses that must be adhered to. Definition items with external origin must be linked to a StandardizationBody item, which provides more information about the body taking care of the definition. This includes also information about the licenses (License item) that determine the usage rights for the semantic definitions from this standardization body. The StandardizationBody item is referenced via the property "publishedBy" from the Definition item. | ||
In order to make the possible usage of semantic definitions from the Semantic Hub directly transparent the License item can be linked to the Definition item as well by the property "subjectToLicense". | |||
Revision as of 11:33, 26 December 2025
Welcome to the central hub for industrial semantic definitions!
Key facts
- Access to a growing number of industrial semantic definitions, resolved under the URL semantic-hub.io/semanticId
- Free of charge to use under the open license DL-DE Zero 2.0 ("Datenlizenz Deutschland")
- Maintained by a growing community that likes the vision of a central hub like we: https://semantic-hub-community.coapp.io/
- Trusted partner for standardisation organizations that want to publish their definitions on a central hub
- already xxx definitions ingested
Purpose
The hub was initiated as Wikibase to solve the problem of scattered dictionaries and APIs that make it hard to find the information behind semantic definitions instantly. Semantic definitions are the meta data (e.g., unit of measure) for concepts (e.g., temperature) that form the vocabular that is strongly needed for:
- an efficient data mapping, consistency checking and interface design
- interoperability of technical systems and the Asset Administration Shell
- common vocabulary and language in data spaces, like Factory-X, Catena-X or Dataspace4Everybody
User groups and their possibilities
| What are you looking for? | Your next step... |
|---|---|
| You are looking for a semantic definition? | Just start your search in the search field above. |
| You would like to publish a larger set of semantic definitions (e.g., as standardization body)? | Get in touch with us, to prepare the ingestion of data sets into our wikibase via support@semantic-hub.io. |
| You would like to publish your own semantic definition? | Just create your first semantic definition. We recommend to register before. |
| You are interested in semantic referencing in general and would like to propose improvements and new features? | Join our open community on https://semantic-hub-community.coapp.io/ |
| You would like to access semantic definitions via API for your applications or you would like to use extended AI-based search functionalities? | Join our open community on https://semantic-hub-community.coapp.io and chose a membership plan. |
Simple and clear rules
Identifier semanticID
Identifier (the semanticID) of semantic definitions have to be unique, e.g., URI/IRI, IRDI or URN. In this wikibase there are two kinds of items that have to have a semanticID, the Definition item with a non-versionized semanticID and the Version item with a versionized semanticID.
When ingesting data sets from existing semantic definition repositories the existing semanticID will be taken over normally. In cases where the semantic definitions are equal an item can have more that one semanticID assigned.
Creation of new semanticID
When creating a semantic definition initially in the Semantic Hub and there is no source repository / semanticID existing yet, we recommend to create your semanticID with this format:
- Definition item: https://semanticid.io/{Username}/{LocalIdentifier} or https://semanticid.io/{Username}/{LocalGroupIdentifier}/{LocalIdentifier}
- Version item: https://semanticid.io/{Username}/{LocalIdentifier}/{Version} or https://semanticid.io/{Username}/{LocalGroupIdentifier}/{LocalIdentifier}/{Version}
The version should be a counted ascending from 1.
Example: https://semanticid.io/admin/temperature (non-versionized) or https://semanticid.io/admin/temperature/1 (versionized)
Publishing of semantic definition versions
change to issuer item instead of issuerID page
A version has to be always identical with the source of the definition if there is one. In this case no version is allowed to be created that is not already existing. It is in the responsibility of the whole community to maintain the Semantic Hub in this regard.
License terms
To reach the communities goal of true interoperability every semantic definition which has its origin (mandatory property origin = 'internal') in the Semantic Hub is published unter Creative Commons CC0 1.0 Universal.
Definitions with an external origin (mandatory property origin = 'external') might be subject to other licenses that must be adhered to. Definition items with external origin must be linked to a StandardizationBody item, which provides more information about the body taking care of the definition. This includes also information about the licenses (License item) that determine the usage rights for the semantic definitions from this standardization body. The StandardizationBody item is referenced via the property "publishedBy" from the Definition item.
In order to make the possible usage of semantic definitions from the Semantic Hub directly transparent the License item can be linked to the Definition item as well by the property "subjectToLicense".
