Main Page: Difference between revisions

From semantic-hub.io
Line 78: Line 78:
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.
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 similar definitions 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 for exactly the same external definitions.
When ingesting data sets from existing semantic definition repositories the existing ''semanticId'' will be taken over. In cases where similar definitions 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 for exactly the same external definition (in case of duplicates).


==== Creation of new semanticID ====
==== Creation of new semanticID ====

Revision as of 22:52, 26 February 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.
You would like to publish a larger set of semantic definitions (e.g., as standardization body)? Please join our open community on https://semantic-hub-community.coapp.io and announce a Data Set Request here.
You would like to edit the Wikibase (Semantic Hub)? Join our open community on https://semantic-hub-community.coapp.io and you will get an invitation link to the Wikibase (Semantic Hub) after a short check from our administrators.
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 / SPARQL 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.

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/

In addition meta model elements are listed here: Data model

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

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 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 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 similar definitions have different semanticId's more than one semanticId can be assigned. Ranks should be used in the case of multiple semanticId's for exactly the same external definition (in case of duplicates).

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 internat 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 kind=community in the Semantic Hub is published unter Creative Commons CC0 1.0 Universal.

Definitions with an external origin (kind=standardized) 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

  • 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)
  • SPARQL: query.semantic-hub.io
  • Wikibase Rest API - requires free community plan
  • Special interfaces (AAS CD-Repository / GraphQL) - requires advanced community plan

Data Mapping

note: there should be a page leading to ressources for data mapping

Naming Conventions (Metamodel)

Items - Upper CamelCase

Properties - Lower CamelCase

to be completed...

Additional content