Main Page: Difference between revisions
| Line 46: | Line 46: | ||
|} | |} | ||
=== | === Instructions for the Semantic Hub === | ||
=== Data model === | |||
The data schema is enforced in the wikibase by the extension EntitySchema. An ontology about the Semantic Hub's structure is provided by [https://www.semtation.de/ Semtation] with their <s>Tool SemTalk. - Link to Ontology.</s> | |||
==== Identifier ''semanticID'' ==== | ==== Identifier ''semanticID'' ==== | ||
Revision as of 08:14, 27 December 2025
Welcome to the central hub for industrial semantic definitions maintained by an open community!
Who we are
- A open community that collects existing or publishes new industrial semantic definitions in this Semantic Hub (technically a Wikibase)
- A trusted partner for standardization bodies that want to let the community work on their definitions commonly
- Free to use (licenses might apply for external definitions only)
- The wikibase and open community plattform (https://semantic-hub-community.coapp.io/) are operated by FoP Consult GmbH from Berlin, Germany
Key Facts
- X users registered at the Semantic Hub (this Wikibase)
- XXX semantic definitions from external repositories ingested
- XXX semantic definitions publihed with their origin in the Semantic Hub
- X members joined the additional community plattform https://semantic-hub-community.coapp.io/
Purpose
The Semantic 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, Dataspace4Everybody, Asset Data eXchange Hub
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. |
Instructions for the Semantic Hub
Data model
The data schema is enforced in the wikibase by the extension EntitySchema. An ontology about the Semantic Hub's structure is provided by Semtation with their Tool SemTalk. - Link to Ontology.
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. In cases where the 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 (origing = 'internal') you have to create your own unique semanticID.
You can use this format if you do not have an alternative at hand:
- 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
In oder to publish a regular semantic definition (a version with a certain state of the definition) a Version item hast to be created.
For internal definitions (origin = 'internal') a Version item can be created at any time to freeze the state of a definition as official version.
For external definitions (origin = 'external') a version has to be always identical with the original definition, published by an external standardization body. In this case no version is allowed to be created that is not already existing at the origin. 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 (origin = 'internal') in the Semantic Hub is published unter Creative Commons CC0 1.0 Universal.
Definitions with an external origin (origin = 'external') might be subject to other licenses that must be adhered to. Definition items with external origin must be linked to an ExternalRepository item, which is linked to an StandardizationBody item that provides more information about the body taking care of the definitions in the external repository. This ExternalRepository item should be linked to a License item that provides information about the usage rights for the semantic definitions granted from the standardization body behind the ExternalRepository.
Data Access
https://www.wikidata.org/wiki/Wikidata:Data_access
- Search in the Wikibase
- Search by Special:GoBySemanticId
- Linked Data Interface (URI): semantic-hub.io/?p=semanticId; semanticId musst be percent-encoded (https://en.wikipedia.org/wiki/Percent-encoding)
- Standard interfaces (Wikibase Rest API / SPARQL) - requires free community plan
- Special interfaces (AAS CD-Repository / GraphQL) - requires advanced community plan
