Main Page: Difference between revisions

From semantic-hub.io
 
(63 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''Welcome to the central hub for industrial semantic definitions maintained by an open community!'''
'''Welcome to the central hub for industrial semantic definitions maintained by an open community!'''
'''Semantic Hub = Meta Dictionary for industrial semantic definitions/concept descriptions'''


[[Special:GoBySemanticId]]
[[Special:GoBySemanticId]]
Line 5: Line 7:
=== Who we are ===
=== Who we are ===


* A open community that collects existing or publishes new industrial semantic definitions in this Semantic Hub (technically a Wikibase)
* An 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
* 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)
* Free to use (licenses might apply for external definitions only)
* The open community is managed by FoP Consult GmbH from Berlin, Germany
* The wikibase and open community plattform (https://semantic-hub-community.coapp.io/) are operated by FoP Consult GmbH from Berlin, Germany


=== Key Facts ===
=== Key Facts ===
* X users registered at the Semantic Hub (this Wikibase)
* X users registered at the Semantic Hub (this Wikibase)
* XXX semantic definitions from external repositories ingested
* XXX semantic definitions from external repositories ingested
* XXX semantic definitions publihed with their origin in the Semantic Hub
* XXX semantic definitions published with their origin in the Semantic Hub
* X members joined the additional community plattform https://semantic-hub-community.coapp.io/
* X members joined the additional community plattform https://semantic-hub-community.coapp.io/


Line 22: Line 23:
* an efficient data mapping, consistency checking and interface design
* an efficient data mapping, consistency checking and interface design
* interoperability of technical systems and the Asset Administration Shell
* interoperability of technical systems and the Asset Administration Shell
* common vocabulary and language in data spaces, like Factory-X, Catena-X or Dataspace4Everybody
* common vocabulary and language in data spaces, like [https://factory-x.org/de/ Factory-X], [https://catena-x.net/ Catena-X], [https://www.iese.fraunhofer.de/en/department/digital-twin-engineering/aas-dataspace-for-everybody.html Dataspace4Everybody], [https://adx-hub.com/ Asset Data eXchange Hub]


=== User groups and their possibilities ===
=== User groups and their possibilities ===
Line 32: Line 33:
|You are looking for a semantic definition?  
|You are looking for a semantic definition?  
|Just start your search in the search field above.
|Just start your search in the search field above.
In addition the SPARQL-Endpoint is available here: query@semantic-hub.io
|-
|-
|You would like to publish a larger set of semantic definitions (e.g., as standardization body)?
|You would like to create your own definitions and to contribute to the Semantic Hub by creating content?
|Get in touch with us, to prepare the ingestion of data sets into our wikibase via support@semantic-hub.io.
|Just register at the Semantic Hub above and start.
|-
|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?
|You would like to get support and interact with the vivid Semantic Hub community?
|Join our open community on https://semantic-hub-community.coapp.io/
|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/ https://semantic-hub-community.coapp.io] and chose a membership plan.
|}
|}


=== Rules for the Semantic Hub ===
=== Our Partner ===
 
==== Open Community Platform ====
[https://www.linkedin.com/company/open-innovationscommunity/posts/?feedView=all OPEN Community | LinkedIn]
 
[https://www.semtation.de/ Semtation]
 
=== Instructions for the Semantic Hub ===
 
==== Youtube Channel ====
The Youtube-Channel provides short video clips that are the easiest way to get introduced to the Semantic Hub.
 
==== Meta model ====
The meta model and ontology of the Semantic Hub is visualized here: https://datahub.semtalk.com/
 
Curated by the community, this meta model serves as a best-practice framework. It defines the preferred structures and elements to ensure a consistent Wikibase and interoperability at the end.


==== Identifier ''semanticID'' ====
In addition meta model elements that are candidated to become part of the best-practice framework are listed here: [[Data model]]
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.
Outlook: The meta model can be validated in future by the Wikibase extension EntitySchema.
 
==== Semantic Definitions ====
The Semantic Hub differentiates between two origins of (semantic) Definitions. Definitions with ''origin of definition''=''external'' are external definitions that have been published from a certain standardization body. Definitions with ''origin of definition''=''internal'' are internal definitions created and maintained by the Semantic Hub community.
 
External definitions will be ingested by the maintainer of the Wikibase or the users thorougly. It is the goal to augment these external definitions by the community. In order to know which information are part of the original standard the [[wikidata:Help:Qualifiers|qualifier]] "[[Property:P24|standardized]]" with value "yes" has to be used.
 
Internal community definitions are assumed to be taken later from standardization bodies in order to standardize them officially with an own semanticId.
 
==== Identifier ''semanticId'' ====
Identifier (the ''semanticId'') of semantic definitions have to be unique, e.g., URI/IRI, IRDI or URN. In this wikibase a ''semanticId'' can be assigned to items and properties. Every ''semanticId'' can be assigned only once.
 
When ingesting data sets from existing semantic definition repositories the existing ''semanticId'' will be taken over. In cases where exactly same definitions (duplicates) have different ''semanticId's'' more than one ''semanticId'' can be assigned. [[wikidata:Help:Ranking|Ranks]] should be used in the case of multiple semanticId's.  


==== Creation of new semanticID ====
==== Creation of new semanticID ====
When creating a semantic definition initially in the Semantic Hub (origing = 'internal') you have to create your own unique semanticID.
When creating a semantic definition initially in the Semantic Hub (''origin of definition''=''internal'') you have to create your own unique semanticId.


You can use this format if you do not have an alternative at hand:
You can use this format if you do not have an alternative at hand:


* Definition item: <nowiki>https://semanticid.io/{Username}/{LocalIdentifier}</nowiki> or <nowiki>https://semanticid.io/{Username}/{LocalGroupIdentifier}/{LocalIdentifier}</nowiki>
* <nowiki>https://semanticid.io/{item</nowiki>/property identif<nowiki/>ier}/{label} or <nowiki>https://semanticid.io/{item/property</nowiki> identifier}/{group name}/{label}
* Version item: <nowiki>https://semanticid.io/{Username}/{LocalIdentifier}/{Version}</nowiki> or <nowiki>https://semanticid.io/{Username}/{LocalGroupIdentifier}/{LocalIdentifier}/{Version}</nowiki>
Community definitions are by its nature always "under development" and thus can't be a standard. The qualifier "standardized" won't be used for internal definitions. Also versionizing makes no sense in the case of internal definitions.
The version should be a counted ascending from 1.


Example: <nowiki>https://semanticid.io/admin/temperature</nowiki> (non-versionized) or <nowiki>https://semanticid.io/admin/temperature/1</nowiki> (versionized)
The group name is an optional grouping name, e.g., 'building' expressing that the definition has a connection to buildings.


==== Publishing of semantic definition versions ====
SemanticId.io is a livelong neutral domain name, reserved by FoP Consult GmbH, that won't be resolved to a real website.
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.
Example: <nowiki>https://semanticid.io/5/temperature</nowiki>


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 with origin=internal in the Semantic Hub is published unter [https://creativecommons.org/publicdomain/zero/1.0/deed.en Creative Commons CC0 1.0 Universal].  


==== License terms ====
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.
To reach the communities goal of '''true interoperability''' every semantic definition which has its origin (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 (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.
The maintainer of the Wikibase take care of the license terms when ingesting data sets. This means that in some case only the semanticId will be ingested.


=== Data Access ===
==== Data Access ====
https://www.wikidata.org/wiki/Wikidata:Data_access
https://www.wikidata.org/wiki/Wikidata:Data_access


Line 82: Line 102:
* Search by [[Special:GoBySemanticId]]
* 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)
* 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
* SPARQL: query.semantic-hub.io
* Special interfaces (AAS CD-Repository / GraphQL) - requires advanced community plan
* Wikibase Action/Rest API
* Special interfaces (e.g., AAS CD-Repository) are planned
 
==== Data Mapping ====
note: there should be a page leading to ressources for data mapping or how it is modeled in the Wikibase.
 
==== Naming Conventions (Metamodel) ====
Items - Upper CamelCase
 
Properties - Lower CamelCase
 
to be completed...
 
=== Additional content ===
[[File:Screenshot 1.png|left|thumb|600x600px]]
 
 
 
 
 
 
 
 
 
 
 
[[File:Screenshot 2.png|left|thumb|600x600px]]
 
 
 
 
 
 
 
 
 
 
 
[[File:Screenshot 3.png|left|thumb|600x600px]]
 
 
 
 
 
 
 
 
 
 
[[File:Screenshot 4.png|left|thumb|600x600px]]

Latest revision as of 07:38, 8 March 2026

Welcome to the central hub for industrial semantic definitions maintained by an open community!

Semantic Hub = Meta Dictionary for industrial semantic definitions/concept descriptions

Special:GoBySemanticId

Who we are

  • An 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 published 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:

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.

In addition the SPARQL-Endpoint is available here: query@semantic-hub.io

You would like to create your own definitions and to contribute to the Semantic Hub by creating content? Just register at the Semantic Hub above and start.
You would like to get support and interact with the vivid Semantic Hub community? Join our open community on https://semantic-hub-community.coapp.io/ .

Our Partner

Open Community Platform

OPEN Community | LinkedIn

Semtation

Instructions for the Semantic Hub

Youtube Channel

The Youtube-Channel provides short video clips that are the easiest way to get introduced to the Semantic Hub.

Meta model

The meta model and ontology of the Semantic Hub is visualized here: https://datahub.semtalk.com/

Curated by the community, this meta model serves as a best-practice framework. It defines the preferred structures and elements to ensure a consistent Wikibase and interoperability at the end.

In addition meta model elements that are candidated to become part of the best-practice framework are listed here: Data model

Outlook: The meta model can be validated in future by the Wikibase extension EntitySchema.

Semantic Definitions

The Semantic Hub differentiates between two origins of (semantic) Definitions. Definitions with origin of definition=external are external definitions that have been published from a certain standardization body. Definitions with origin of definition=internal are internal definitions created and maintained by the Semantic Hub community.

External definitions will be ingested by the maintainer of the Wikibase or the users thorougly. It is the goal to augment these external definitions by the community. In order to know which information are part of the original standard the qualifier "standardized" with value "yes" has to be used.

Internal community definitions are assumed to be taken later from standardization bodies in order to standardize them officially with an own semanticId.

Identifier semanticId

Identifier (the semanticId) of semantic definitions have to be unique, e.g., URI/IRI, IRDI or URN. In this wikibase a semanticId can be assigned to items and properties. Every semanticId can be assigned only once.

When ingesting data sets from existing semantic definition repositories the existing semanticId will be taken over. In cases where exactly same definitions (duplicates) have different semanticId's more than one semanticId can be assigned. Ranks should be used in the case of multiple semanticId's.

Creation of new semanticID

When creating a semantic definition initially in the Semantic Hub (origin of definition=internal) you have to create your own unique semanticId.

You can use this format if you do not have an alternative at hand:

  • https://semanticid.io/{item/property identifier}/{label} or https://semanticid.io/{item/property identifier}/{group name}/{label}

Community definitions are by its nature always "under development" and thus can't be a standard. The qualifier "standardized" won't be used for internal definitions. Also versionizing makes no sense in the case of internal definitions.

The group name is an optional grouping name, e.g., 'building' expressing that the definition has a connection to buildings.

SemanticId.io is a livelong neutral domain name, reserved by FoP Consult GmbH, that won't be resolved to a real website.

Example: https://semanticid.io/5/temperature

License terms

To reach the communities goal of true interoperability every semantic definition with 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.

The maintainer of the Wikibase take care of the license terms when ingesting data sets. This means that in some case only the semanticId will be ingested.

Data Access

https://www.wikidata.org/wiki/Wikidata:Data_access

Data Mapping

note: there should be a page leading to ressources for data mapping or how it is modeled in the Wikibase.

Naming Conventions (Metamodel)

Items - Upper CamelCase

Properties - Lower CamelCase

to be completed...

Additional content