Industrial Data Space Core Vocabulary

IRI:
http://industrialdataspace.org/2016/10/idsv/core#
Date:
20/12/2016
Current version:
1.1.0
Authors:
Christian Mader
Christoph Lange-Bever
Jaroslav Pullmann
Niklas Petersen
Steffen Lohmann
Publisher:
Fraunhofer FIT
Fraunhofer IAIS/EIS
Other visualisation:
Industrial Data Space Vocabulary Server
Source:
IDS Vocabulary BitBucket Repository

Abstract

The Industrial Data Space Core Vocabulary (IDSV) provides classes and properties for describing datasets and services that are accessible on the Industrial Data Space (IDS). It does not provide a formal, complete definition of all necessary dimensions for describing datasets, but rather sets out a consistent means by which dataset and service descriptions can be provided on the IDS. That way, it is possible for a potential user of IDS to find and retrieve datasets and services, as well as to judge their suitability for a particular purpose. This document describes the structure and usage of the Industrial Data Space (IDS) Core Vocabulary for describing datasets (IDSV). It provides an overview on the main classes and properties that should be used within the IDS context in order to publish datasets and services. The namespace for IDSV is http://industrialdataspace.org/2016/10/idsv/core#. Parts of this document have been created automatically from the vocabular source using LODE.

Table of Content

  1. Introduction
  2. Vocabulary Overview
  3. Usage Example
  4. Future Work
  5. Classes
  6. Object Properties
  7. Data Properties
  8. Named Individuals
  9. Annotation Properties
  10. Namespace Declarations

Vocabulary Overview

The following vocabulary relates and links to a number of existing vocabularies that have been identified as suitable for the requirements within the IDS context. The design goal was to leverage the expressivity of vocabularies that are currently in use so that we can build on their functionality. A graphical overview on the vocabulary's structure is given in Figure 1. It illustrates the relevant classes and their alignment to existing vocabularies. Furthermore, it shows the properties that relate the classes to one another. To improve readability, we only depict the most relevant properties in the figure; all other properties relevant for describing the IDS datasets can be found in the sections below. There are two namespaces, ids_top and ids_std which are intended to hold thesauri on dataset and service topical coverage as well as existing standards a dataset or service complies to. These are not part of the IDS Core Vocabulary as they are currently under development and will be provided at a later point in time.

Fig. 1 Data model showing the core classes and their relations.

The figure below illustrates the vocabulary on a more detailed level, including more general classes and properties.

Fig. 2 Detailed data model showing a more complete set of relations and properties.

Usage Example

There are two general ways of distributing data in IDS, either as a single downloadable data set archive (PublishedDataset) or as a parametrized, dynamic service-based provision (DataService), which are covered in the following section Describing an Exemplary Dataset and Describing an Exemplary Service.

Describing an Exemplary Dataset

To illustrate usage of the IDSV, we show its application for a fictional scenario: The energy supplier "NRW-Energie" has collected a large dataset that contains information on the energy consumption of private households in the German province North Rhine-Westphalia. The datasets are quarterly generated and should be provided for download to the Federal Environment Ministry at the price of 10000€. The data must be deleted 30 days after download.

Keep in mind that this is a constructed example for the purpose of giving an idea on a subset of the functionality the IDSV can cover. It does not fully cover any kind of information needed for the publication of datasets but merely acts as a starting point for IDS participants so that they can craft IDS-compliant metadata descriptions. It is planned that user interfaces will be available in productive IDS environments which assist participants in creating the metadata described below in a guided and semi-automated way.

We assume that the energy supplier holds all data in an RDBMS in a secured company-internal intranet. The quarterly report is automatically generated and provided as a CSV file. When publishing it to the IDS, the energy supplier is responsible for defining a unique identifier for the dataset. This may be a URN (like "urn:ids:custom:nrw-energie:ds:consumtionQ1:meta") or a URL (such as "http://nrw-energie.de/datasets/consumptionQ1/meta"). The exact scheme for addressing this information has not been decided yet. Therefore, in this example we refer to the dataset metadata description as nrwe:consumptionQ1.

Express Data Origin and Basic Metadata

Dataset providers like NRW-Energie in our example want to state that (i) the contribution they made is a dataset intended for publication at the IDS, (ii) the title (i.e. publicly visible name) of the dataset, (iii) the fact that the dataset was created by NRW-Energie, and (iv) there is a person that can answer questions on the dataset. This information can be represented as follows:

nrwe:consumptionQ1 a idsv:PublishedDataset;
  idsv:title "Power consumption of households Q3 2016"@en;
  idsv:createdBy <https://www.nrw-energie.de/en.html>;
  idsv:contact <https://www.nrw-energie.de/help/quarterlyreports.html>.

The resources stated for the creator and contact person must be URLs. Following the Linked Data principles, these URLs should be dereferencable and lead to additional information, such as name and telephone numbers of the contact person. In the example above, we have illustrated how to link Websites (i.e. information expressed using the HTML language), but in future we encourage to also use the IDSV for expressing this information in RDF. With the properties proposed above, this can already be done currently. However, we will provide updates and extensions of the IDSV that define on a more detailed level the properties that should be used for expressing participant information (like creators and contact persons).

Expressing Dataset Coverage and Content

Partners on the IDS such as the energy supplier in our example want to describe their datasets as accurately as possible so that it can be found efficiently (i.e. high precision and recall) when issuing queries at the broker. Therefore, the IDSV provides facilities to describe a dataset's content in a standardized way. The energy data has both a temporal coverage (i.e., the data covers the first quarter of 2015) as well as a spatial coverage (i.e., the collected data originates from households in the province North Rhine-Westphalia). We explain how to express this information in the examples in the following sections.

Temporal Coverage

The temporal coverage of a dataset can be stated by the property idsv:coversTemporal which allows for reusing the elements of the Time Ontology should be used. If a dataset, for example, covers an interval specified by a start and end date (like the quarterly period in the example), this can be expressed as follows:

nrwe:consumptionQ1 idsv:coversTemporal [
  a time:Interval;
  time:hasBeginning [
    a time:Instance;
    time:inXSDDateTime "2015-01-01T00:00:00-1:00"^^xsd:dateTime
  ];
  time:hasEnd [
    a time:Instance;
    time:inXSDDateTime "2015-03-31T24:00:00-1:00"^^xsd:dateTime
  ]
].

Spatial Coverage

In a similar way, spatial coverage of a dataset can be described. Two properties are available. idsv:coversSpatialLocation can be used for covering exact spacial locations that can be referred to by a name, such as "Germany". The other property, idsv:coversSpatialGeometry is intended to express custom spatial regions like areas of temporary blackouts of electrical power. In our energy-supplier example, we want to state the fact that the dataset covers information of the province "North Rhine-Westphalia", which can be expressed as a single statement:

nrwe:consumptionQ1 idsv:coversSpatialLocation <http://sws.geonames.org/2861876/about.rdf>.

The URL http://sws.geonames.org/2861876/about.rdf refers to the RDF representation from the GeoNames service, which we encourage to use for the idsv:coversSpatialLocation property.

For expressing spatial geometries (i.e., areas with custom boundaries), the property idsv:coversSpatialGeometry is intended. It uses the ISA Location Core and the NeoGeo vocabularies. Currently, geometries are just a collection of geo coordinates that make up a polygon indicating the area of interest, like

nrwe:consumptionQ1 idsv:coversSpatialGeometry [
  a ngeo:Polygon;
  ngeo:interior [
		a ngeo:LinearRing ;
    ngeo:posList (
      [ wgs84_pos:lat "-29"; wgs84_pos:long "16" ]
      [ wgs84_pos:lat "-28"; wgs84_pos:long "33" ]
      [ wgs84_pos:lat "-34"; wgs84_pos:long "27" ]
      [ wgs84_pos:lat "-35"; wgs84_pos:long "19" ]
      [ wgs84_pos:lat "-29"; wgs84_pos:long "16" ]
    )
  ] ;
].

Note that despite our running energy supplier example does not need to state information about spatial geometries, we include the example here as an additional method to, e.g., state areas within the province that are not covered by the dataset.

Data Format

The energy supplier also needs to state that the dataset is available in text format as comma separated values (CSV). This can be done in the following way:

nrwe:consumptionQ1 idsv:mediaType <http://www.iana.org/assignments/media-types/text/csv>.

Note that, as shown above, the property idsv:mediaType refers to a resource as defined by IANA. If a format is not provided by IANA, it is possible to indicate it as a string using the idsv:format property like this:
    nrwe:consumptionQ1 idsv:format [rdfs:label "customFormat"].

Expressing Legal Information and Access Control

For attaching legal information such as terms of use of a dataset, in the provided example the energy supplier has the requirement to state that (i) retrieving the dataset costs 10000€ and (ii) only the Federal Environment Ministry is entitled to retrieve the dataset. In order to describe such kind of usage information, the IDSV supports the attachment of ODRL-based policies to datasets. This is done by using the property idsv:policy is used. For exploring the full expressivity of ODRL, please refer to the ODRL ontology documentation page. Keep in mind that multiple policies containing various permissions and prohibitions may be attached to a single dataset so that it is possible to cover a large number of possible usage scenarios.

Expressing the Price of a Dataset

The following RDF snippet shows how to attach a policy to the dataset in our example, that grants the permission to read the dataset with the duty to pay exactly 10000€.

nrwe:consumptionQ1 idsv:policy [
  a odrl:Offer;
  odrl:permission [
    a odrl:Permission ;
    odrl:action odrl:read ;
    odrl:duty [
      a odrl:Duty ;
      odrl:action odrl:pay ;
      odrl:constraint [
        a odrl:Constraint ;
        odrl:payAmount 10000.00 ;
        odrl:operator odrl:eq ;
        odrl:unit dbpedia:Euro
      ];
    ];
  ];
].

Expressing Whitelist-based User Permissions for a Dataset

Policies can also be used to state what users should be able to perform what actions on a dataset. In our example, the Federal Environment Ministry (identified by the URL http://www.bmub.bund.de/en/) should be granted read access to the dataset:

nrwe:consumptionQ1 idsv:policy [
  a odrl:Offer ;
  odrl:permission [
    a odrl:Permission ;
    odrl:action odrl:read ;
    odrl:assignee <http://www.bmub.bund.de/en/> ;
  ] ;
].

Keep in mind that the policy described above is only a method of stating access information. There needs to be an implementation that interprets and enforces the policy, which should be deployed close to the data, i.e., at the connector. Furthermore, odrl:assignee links to a URL for identification of the communication partner. This means that policy creator and dataset accessor need to have a common understanding on the URL describing their identity. The exact way on how to reach this understanding is not within the scope of this documentation.

Expressing an Expiry Date of a Dataset

The energy supplier in our example wants the dataset downloader (Federal Environment Ministry) to delete the dataset after a period of 30 days. The snippet below shows how to attach a policy to the example dataset that expresses these constraints.

nrwe:consumptionQ1 idsv:policy [
  a odrl:Offer;
  odrl:permission [
    a odrl:Permission ;
    odrl:action odrl:read ;
    odrl:assignee <http://www.bmub.bund.de/en/> ;
    odrl:duty [
      a odrl:Duty ;
      odrl:action odrl:delete ;
      odrl:constraint [
        a odrl:Constraint ;
        odrl:operator odrl:eq ;
        odrl:dateTime "P30D"^^xsd:dateTime
      ];
    ];
  ];
].
As in the previous example which showed how to grant read permissions, the metadata provided in the example above is intended to be interpreted by machines to, e.g., drive search and retrieval interfaces and/or enforce the actual policy by physically deleting the files in the assignee's environment.

Describing an Exemplary Service

In addition to describing a dataset that is provided "as a whole" for access and download on the IDS, the IDS vocabulary also provides means to describe data services. This description covers the service's functionality and what parameters it takes as input and output. This standardized description improves service lookup and invocation on the IDS because it leverages the power of controlled vocabularies: using linked data techniques, it is possible to bind additional semantics (i.e. meaning) to service descriptions and parameters. This technology enables the establishment of common understanding on a service's capabilities even between different industry branches.

To illustrate service description using the IDS Core Vocabulary, let's consider the following example. A company offers to its customers a service that allows them to check if certain products are currently on stock. The company produces steel in various grades of quality, so the service requires as input the quality grade, an amount and the unit in which the amount is measured (e.g., kg or pound). Therefore, the company creates a service description using resources in their namespace szag. Services that are intended to provide data should be of type DataSource and have attached a DataService which may support multiple operations. These operations have a set of input and output parameters. Each parameter SHOULD be described by a name and link to a URL (using the property semanticType) which provides additional semantic information of the parameter's type (like, e.g., a quality definition, or spatial location). In addition, "basic" datatypes can be asserted to a parameters, such as double or string, by using the dataType properties pointing to types defined in XML schema.

szag:Stock
	a idsv:DataSource ;
	idsv:service szag:stockQueryService.

szag:stockQueryService
    a idsv:DataService ;
	idsv:operation szag:getStock .

szag:getStock
	a idsv:RetrieveDataOperation ;
	idsv:label "Bestandsauskunft"@de ;
	idsv:description "Beispiel für diese Operation in Java: double getBestand(URI steelQualityType, double amount, URI unit)";
	idsv:input szag:steelQualityTypeParameter ;
	idsv:input szag:amountParameter ;
	idsv:input szag:unitParameter ;
	idsv:output szag:amountParameter.

szag:steelQualityTypeParameter
	a idsv:Parameter ;
	idsv:label "Stahlgüte"@de ;
	idsv:name "steelQualityType" ;
	idsv:semanticType en10025:SteelGrade ;
	idsv:dataType xsd:anyURI.

szag:amountParameter
	a idsv:Parameter ;
	idsv:label "Menge"@de ;
	idsv:name "amount" ;
	idsv:semanticType qudt:MassUnit ;
	idsv:dataType xsd:double.

szag:unitParameter
	a idsv:Parameter ;
	idsv:label "Einheit"@de ;
	idsv:name "unit" ;
	idsv:semanticType qudt:Unit ;
	idsv:dataType xsd:anyURI.

In this example, a service szag:Stock is defined as a data source. It supports an operation for retrieving data called getStock which requires three parameters: steelQualityType, amount, and unit. The parameter steelQualityType defines the steel grade quality by a referencing to its definition in the EN10025 standard, which is available on the Web using the URL en10025:SteelGrade. The amount parameter is to be used to specify the actually requested amount, such as 500. The parameter unit references the definition of the unit of measurement, such as pounds or kilograms, which is again available in an open vocabulary on the Web (qudt:Unit).

Figure 3 illustrates how the service description provided above can help to establish a common understanding on a service's parameters, their meaning and how they related to one another. It also shows how a controlled vocabulary describing units that is linked by the service description may help to convert between units passed as input parameters. For example, the parameter Grade links to the resource en10025:SteelGrade which is described in a steel grade vocabulary that is available on the web. The resource which is an URL can be resolved and provide additional information (e.g., how a steel grade is defined, what standards and description methods exist). In a similary way also the instances that are passed as Grade parameters are URLs that link to this controlled vocabulary. Each instance, e.g., bs4360:40B or en10025:S235JR is also represented in the vocabulary (if not it can be added) alongside with information on how these grades relate to each other (this is an example of such a vocabulary compiled from data already available on the Web). In the example at hand, they are related by the property owl:sameAs which indicates that they are identical. Therefore the steel grade vocabulary acts as a semantic mapping table of various steel grades, enabling (i) customers to call the service with the steel grades they are used to and (ii) service providers to maintain or contribute to a steel grade mapping vocabulary they can easily use to prepare queries to their internal backend systems.

Fig. 3 Linking service descriptions to controlled vocabularies for improved semantics.

Figure 4 describes the relation of an IDS participan's service description and the IDS vocabulary as formalized in the code snipped above. A client can be granted access to read a provider's service description (1), which enables the client to get an understanding on the service's objectives and how to invoke it (2) so that an actual data transfer (3,4) can happen.

Fig. 4 Describing a customer service using the IDS Core Vocabulary.

Future Work

Our immediate next steps in the development if the IDSV will be:

Classes

Connectorc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#Connector

Industrial Dataspace Connector for hosting data services.

has super-classes
Contributionc
is in domain of
providedContributionop
is in range of
providedByop

Contributionc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#Contribution

An item created by an IDS participant which is intended to be accessed by others

has super-classes
entityc
has sub-classes
Connectorc
is in domain of
contactop, createdAtdp, createdByop, curatorop, descriptiondp, lastModifiedAtdp, licenseop, policyop, providedAtdp, publishedByop, technicalContactop, titledp, updateFrequencyop, versiondp

DataEndpointc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#DataEndpoint

An entity that can be used in a data flow within a connector or between connectors.

has sub-classes
DataSinkc, DataSourcec
is in domain of
interfaceop, providedByop, serviceop
is in range of
providedContributionop, receiverop, senderop

DataServicec back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#DataService

Particular type of service operating on data, in contrast to e.g. controlling a device or interacting with a process. A DataService will usually expose a set of related operations to be applied on a homogenous, uniform data set. It should not have preconditions or side-effects.

is in domain of
operationop
is in range of
serviceop

Datasetc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#Dataset

Dataset on the Industrial Dataspace. May be a data offering, a subset of a dataset that is in the state of being transfered or an aggregation of multiple other datasets.

has super-classes
datasetc
has sub-classes
PublishedDatasetc, TransferedDatasetc
is in domain of
formatop, mediaTypeop, structureop

DataSinkc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#DataSink

A service that consumes data.

has super-classes
DataEndpointc

DataSourcec back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#DataSource

An active or passive service that offers data.

has super-classes
DataEndpointc
has sub-classes
PublishedDatasetc

InvolvedActorc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#InvolvedActor

A person that is involved in the Industrial Data Space on a more general way like, e.g., providing support for a dataset

has sub-classes
Participantc
is in range of
contactop, publishedByop, technicalContactop
is also defined as
named individual

Operationc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#Operation

has sub-classes
RetrieveDataOperationc
is in domain of
faultop, outputop
is in range of
operationop

Parameterc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#Parameter

Formal parameter of a functional unit (operation, template etc.)

is in domain of
dataTypeop, label, nameop, semanticTypeop, structureReferencedp, subParameterop
is in range of
faultop, inputop, outputop, subParameterop

Participantc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#Participant

A person or company using the Industrial Data Space

has super-classes
InvolvedActorc
organizationc
is in domain of
emailop, emailop, nameop, primarySiteop
is in range of
createdByop, curatorop

Protocol Bindingc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#ProtocolBinding

is in range of
interfaceop

PublishedDatasetc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#PublishedDataset

Data to be published and consumed using the IDS

has super-classes
DataSourcec
Datasetc
is in domain of
accessURLop, byteSizedp, conformsToop, coversSpatialGeometryop, coversSpatialLocationop, coversTemporalop, coversTopicop, creationMethodop, downloadURLop, keywordop, languageop, qualityAnnotationop, qualityMeasurementop

RetrieveDataOperationc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#RetrieveDataOperation

has super-classes
Operationc

Templatec back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#Template

Structured string literal containing distinguished placeholders to be replaced by runtime arguments, see for example URI Templates (RFC 6570).

TransferedDatasetc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#TransferedDataset

The class of resources that describe a dataset transfered by an IDS communication in a protocol frame.

has super-classes
Datasetc
is in domain of
authTokenop, customPropertyop, digestop, receiverop, senderop

TransferPropertyc back to ToC or Class ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#TransferProperty

General property for additional description of security aspects of a data transfer.

is in range of
customPropertyop

Object Properties

accessURLop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#accessURL

A landing page, feed, SPARQL endpoint or other type of resource that gives access to the dataset. MUST be asserted to resources of type PublishedDataset.

has domain
PublishedDatasetc
has range
resourcec
is also defined as
annotation property

authTokenop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#authToken

An authorization token like JSON Web Token.

has domain
TransferedDatasetc
is also defined as
data property

conformsToop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#conformsTo

The standard the dataset conforms to. SHOULD link to the IDS Standards taxonomy. SHOULD be asserted to resources of type PublishedDataset.

has domain
PublishedDatasetc
has range
standardc

contactop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#contact

Entity that is competent to answer general service requests about the contribution. SHOULD be asserted to resources of type Contribution.

has domain
Contributionc
has range
InvolvedActorc
is also defined as
annotation property

coversSpatialGeometryop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#coversSpatialGeometry

Spatial area covered by the dataset, expressed as a geometry shape. MAY be asserted to resources of type PublishedDataset.

has domain
PublishedDatasetc
has range
geometryc
is also defined as
annotation property

coversSpatialLocationop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#coversSpatialLocation

Spatial location covered by the dataset. MAY be asserted to resources of type PublishedDataset.

has domain
PublishedDatasetc
has range
locationc
is also defined as
annotation property

coversTemporalop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#coversTemporal

Temporal period or instance covered by the dataset. MAY be asserted to resources of type PublishedDataset.

has domain
PublishedDatasetc
has range
temporal entityc
is also defined as
annotation property

coversTopicop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#coversTopic

The topic covered by the dataset. SHOULD link to the IDS Topics taxonomy. SHOULD be asserted to resources of type PublishedDataset.

has domain
PublishedDatasetc
has range
topicc
is also defined as
annotation property

createdByop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#createdBy

Entity primarily responsible for making the resource. MUST be asserted to resources of type Contribution.

has domain
Contributionc
has range
Participantc
is also defined as
annotation property

creationMethodop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#creationMethod

Algorithm or mapping that describes how the dataset is created from a source representation.

has domain
PublishedDatasetc
is also defined as
data property

curatorop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#curatedBy

Entity responsible for curation of the contribution. MAY be asserted to resources of type Contribution.

has domain
Contributionc
has range
Participantc

customPropertyop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#customProperty

The digest of the dataset being transfered.

dataTypeop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#dataType

Links a parameter to a datatype IRI.

has domain
Parameterc

digestop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#digest

The digest of the dataset being transfered.

has domain
TransferedDatasetc
is also defined as
data property

downloadURLop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#downloadURL

The URI for downloading the dataset as a whole. SHOULD be asserted to resources of type PublishedDataset.

has domain
PublishedDatasetc
has range
resourcec
is also defined as
annotation property

emailop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#email

Email address for contacting the participant on a general level. MUST be asserted to resources of type Participant.

has domain
Participantc
has range
thingc
is also defined as
annotation property

emailop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#homepage

General official homepage of the participant. MUST be asserted to resources of type Participant.

has domain
Participantc
has range
documentc
is also defined as
annotation property

faultop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#fault

has domain
Operationc
has range
Parameterc

formatop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#format

The file format of the dataset. idsv:mediaType SHOULD be used if the type of the distribution is defined by IANA. SHOULD be asserted to resources of type Dataset.

has domain
Datasetc
has range
media type or extentc
is also defined as
annotation property

inputop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#input

References an input parameter without specifying its cardinality.

has domain
Operationc or Templatec
has range
Parameterc

interfaceop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#interface

has domain
DataEndpointc
has range
Protocol Bindingc

keywordop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#keyword

A keyword describing the dataset's content. Can be a free-text term. SHOULD be asserted to resources of type PublishedDataset.

languageop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#language

Indicates the language used in the dataset. SHOULD be asserted to resources of type PublishedDataset.

has domain
PublishedDatasetc
has range
linguistic systemc
is also defined as
annotation property

licenseop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#license

Link to a license document resource. SHOULD be asserted to resources of type Contribution.

has domain
Contributionc
has range
license documentc
is also defined as
annotation property

mediaTypeop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#mediaType

The media type of the dataset, as defined by IANA. SHOULD be asserted to resources of type Dataset.

has domain
Datasetc
has range
media type or extentc
is also defined as
annotation property

nameop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#name

Name of the company participating in the IDS. MUST be asserted to resources of type Participant.

operationop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#operation

has domain
DataServicec
has range
Operationc

outputop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#output

has domain
Operationc
has range
Parameterc

policyop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#policy

An ODRL policy covering intellectual property and access rights. MAY be asserted to resources of type Contribution.

has domain
Contributionc
has range
policyc

primarySiteop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#primarySite

Indicates a primary site for the Organization, this is the default means by which an Organization can be contacted and is not necessarily the formal headquarters. SHOULD be asserted to resources of type Participant.

has domain
Participantc
has range
addressc
is also defined as
annotation property

providedByop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#providedBy

The connector that publishes the service. MUST be asserted to resources of type DataEndpoint if they are configured into a connector.

has domain
DataEndpointc
has range
Connectorc
is inverse of
providedContributionop

providedContributionop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#provides

The endpoint that is published by the connector. If such are present, they MUST be asserted to resources of type Connector.

has domain
Connectorc
has range
DataEndpointc
is inverse of
providedByop

publishedByop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#publishedBy

Publisher providing access to the contribution. MAY be asserted to resources of type Contribution.

has domain
Contributionc
has range
InvolvedActorc
is also defined as
annotation property

qualityAnnotationop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#qualityAnnotation

Statements, i.e., ratings, certificate on the contribution's quality. MAY be asserted to resources of type Contribution.

has domain
PublishedDatasetc
has range
quality annotationc
is also defined as
annotation property

qualityMeasurementop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#qualityMeasurement

Measurement of a data quality observation. MAY be asserted to resources of type Contribution.

has domain
PublishedDatasetc
has range
quality measurementc
is also defined as
annotation property

receiverop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#receiver

The receiver of the message.

has domain
TransferedDatasetc
has range
DataEndpointc

semanticTypeop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#semanticType

Links a parameter to a type IRI to express its semantics.

has domain
Parameterc

senderop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#sender

The sender of the message.

has domain
TransferedDatasetc
has range
DataEndpointc

serviceop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#service

has domain
DataEndpointc
has range
DataServicec

structureop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#structure

Links to resources that express how the data can be interpreted, like validating expressions, or mappings. MAY be asserted to resources of type Dataset.

has domain
Datasetc

subParameterop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#subParameter

Auxiliary predicate to expose relevant parts of a structured top-level parameter (XML, JSON).

has domain
Parameterc
has range
Parameterc

technicalContactop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#technicalContact

Entity that is competent to process technical requests about the contribution. SHOULD be asserted to resources of type Contribution.

has domain
Contributionc
has range
InvolvedActorc
is also defined as
annotation property

updateFrequencyop back to ToC or Object Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#updateFrequency

The frequency the contribution is updated, e.g., for actualisation, revision or maintenance. MAY be asserted to resources of type Contribution.

has domain
Contributionc
has range
frequencyc

Data Properties

authTokenop back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#authToken

An authorization token like JSON Web Token.

has range
string
is also defined as
object property

byteSizedp back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#byteSize

The size of the dataset in bytes when accessed by idsv:downloadURL. SHOULD be asserted to resources of type PublishedDataset.

has domain
PublishedDatasetc
has range
literal

createdAtdp back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#createdAt

Date of creation of the contribution. SHOULD be asserted to resources of type Contribution.

has domain
Contributionc
has range
date time
is also defined as
annotation property

creationMethodop back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#creationMethod

Algorithm or mapping that describes how the dataset is created from a source representation.

has range
string
is also defined as
object property

descriptiondp back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#description

Freetext description of the contribution. MAY be asserted to resources of type Contribution.

has domain
Contributionc
has range
literal
is also defined as
annotation property

digestop back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#digest

The digest of the dataset being transfered.

has range
base64 binary
is also defined as
object property

keywordop back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#keyword

A keyword describing the dataset's content. Can be a free-text term. SHOULD be asserted to resources of type PublishedDataset.

has range
literal
is also defined as
annotation property, object property

lastModifiedAtdp back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#lastModifiedAt

Date of last modification. SHOULD be asserted to resources of type Contribution.

has domain
Contributionc
has range
date time
is also defined as
annotation property

nameop back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#name

Name of the company participating in the IDS. MUST be asserted to resources of type Participant.

has range
literal
is also defined as
annotation property, object property

providedAtdp back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#providedAt

Date of submission of the contribution. SHOULD be asserted to resources of type Contribution.

has domain
Contributionc
has range
date time
is also defined as
annotation property

structureReferencedp back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#structureReference

Generic reference (path expression) into a structured parameter value

has domain
Parameterc
has range
string

titledp back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#title

Name of the contribution. MUST be asserted to resources of type Contribution.

has domain
Contributionc
has range
literal
is also defined as
annotation property

versiondp back to ToC or Data Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#version

Version identifier of the contribution. SHOULD be asserted to resources of type Contribution.

has domain
Contributionc
has range
string
is also defined as
annotation property

Named Individuals

InvolvedActorni back to ToC or Named Individual ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#InvolvedActor

belongs to
kindc
is also defined as
class

Annotation Properties

access u r lap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/dcat#accessURL

has sub-properties
accessURLap

accessURLap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#accessURL

A landing page, feed, SPARQL endpoint or other type of resource that gives access to the dataset. MUST be asserted to resources of type PublishedDataset.

has super-properties
access u r lap
is also defined as
object property

contactap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#contact

Entity that is competent to answer general service requests about the contribution. SHOULD be asserted to resources of type Contribution.

has super-properties
contact pointap
is also defined as
object property

contact pointap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/dcat#contactPoint

has sub-properties
contactap, technicalContactap

coversSpatialGeometryap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#coversSpatialGeometry

Spatial area covered by the dataset, expressed as a geometry shape. MAY be asserted to resources of type PublishedDataset.

has super-properties
geometryap
is also defined as
object property

coversSpatialLocationap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#coversSpatialLocation

Spatial location covered by the dataset. MAY be asserted to resources of type PublishedDataset.

has super-properties
spatialap
is also defined as
object property

coversTemporalap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#coversTemporal

Temporal period or instance covered by the dataset. MAY be asserted to resources of type PublishedDataset.

has super-properties
temporalap
is also defined as
object property

coversTopicap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#coversTopic

The topic covered by the dataset. SHOULD link to the IDS Topics taxonomy. SHOULD be asserted to resources of type PublishedDataset.

has super-properties
themeap
is also defined as
object property

createdAtap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#createdAt

Date of creation of the contribution. SHOULD be asserted to resources of type Contribution.

has super-properties
date submittedap
is also defined as
data property

createdByap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#createdBy

Entity primarily responsible for making the resource. MUST be asserted to resources of type Contribution.

has super-properties
creatorap
is also defined as
object property

creatorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/creator

has sub-properties
createdByap

date submittedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/dateSubmitted

has sub-properties
createdAtap, providedAtap

descriptionap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#description

Freetext description of the contribution. MAY be asserted to resources of type Contribution.

has super-properties
descriptionap
is also defined as
data property

descriptionap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/description

has sub-properties
descriptionap

download u r lap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/dcat#downloadURL

has sub-properties
downloadURLap

downloadURLap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#downloadURL

The URI for downloading the dataset as a whole. SHOULD be asserted to resources of type PublishedDataset.

has super-properties
download u r lap
is also defined as
object property

emailap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#email

Email address for contacting the participant on a general level. MUST be asserted to resources of type Participant.

has super-properties
mboxap
is also defined as
object property

emailap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#homepage

General official homepage of the participant. MUST be asserted to resources of type Participant.

has super-properties
homepageap
is also defined as
object property

formatap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#format

The file format of the dataset. idsv:mediaType SHOULD be used if the type of the distribution is defined by IANA. SHOULD be asserted to resources of type Dataset.

has super-properties
formatap
is also defined as
object property

formatap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/format

has sub-properties
formatap

geometryap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/locn#geometry

has sub-properties
coversSpatialGeometryap

has primary siteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/org#hasPrimarySite

has sub-properties
primarySiteap

has quality annotationap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/dqv#hasQualityAnnotation

has sub-properties
qualityAnnotationap

has quality measurementap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/dqv#hasQualityMeasurement

has sub-properties
qualityMeasurementap

has versionap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/hasVersion

has sub-properties
versionap

homepageap back to ToC or Annotation Property ToC

IRI: http://xmlns.com/foaf/0.1/homepage

has sub-properties
emailap

jsonStructureReferenceap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#jsonStructureReference

JSON Pointer reference to a node within enclosing complex JSON parameter.

has super-properties
structureReference

keywordap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#keyword

A keyword describing the dataset's content. Can be a free-text term. SHOULD be asserted to resources of type PublishedDataset.

has super-properties
keywordap
is also defined as
object property, data property

keywordap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/dcat#keyword

has sub-properties
keywordap

labelap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#label

Human-readable label describing a parameter.

has super-properties
label
has domain
Parameterc

languageap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#language

Indicates the language used in the dataset. SHOULD be asserted to resources of type PublishedDataset.

has super-properties
languageap
is also defined as
object property

languageap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/language

has sub-properties
languageap

lastModifiedAtap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#lastModifiedAt

Date of last modification. SHOULD be asserted to resources of type Contribution.

has super-properties
modifiedap
is also defined as
data property

licenseap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#license

Link to a license document resource. SHOULD be asserted to resources of type Contribution.

has super-properties
licenseap
is also defined as
object property

licenseap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/license

has sub-properties
licenseap

mboxap back to ToC or Annotation Property ToC

IRI: http://xmlns.com/foaf/0.1/mbox

has sub-properties
emailap

media typeap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/dcat#mediaType

has sub-properties
mediaTypeap

mediaTypeap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#mediaType

The media type of the dataset, as defined by IANA. SHOULD be asserted to resources of type Dataset.

has super-properties
media typeap
is also defined as
object property

modifiedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/modified

has sub-properties
lastModifiedAtap

nameap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#name

Name of the company participating in the IDS. MUST be asserted to resources of type Participant.

has super-properties
notationap
nameap
is also defined as
object property, data property

nameap back to ToC or Annotation Property ToC

IRI: http://xmlns.com/foaf/0.1/name

has sub-properties
nameap

notationap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#notation

has sub-properties
nameap

primarySiteap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#primarySite

Indicates a primary site for the Organization, this is the default means by which an Organization can be contacted and is not necessarily the formal headquarters. SHOULD be asserted to resources of type Participant.

has super-properties
has primary siteap
is also defined as
object property

providedAtap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#providedAt

Date of submission of the contribution. SHOULD be asserted to resources of type Contribution.

has super-properties
date submittedap
is also defined as
data property

publishedByap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#publishedBy

Publisher providing access to the contribution. MAY be asserted to resources of type Contribution.

has super-properties
publisherap
is also defined as
object property

publisherap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/publisher

has sub-properties
publishedByap

qualityAnnotationap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#qualityAnnotation

Statements, i.e., ratings, certificate on the contribution's quality. MAY be asserted to resources of type Contribution.

has super-properties
has quality annotationap
is also defined as
object property

qualityMeasurementap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#qualityMeasurement

Measurement of a data quality observation. MAY be asserted to resources of type Contribution.

has super-properties
has quality measurementap
is also defined as
object property

rdfStructureReferenceap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#rdfStructureReference

SPARQL 1.1. Property Path reference to a node within enclosing complex RDF parameter.

has super-properties
structureReference

spatialap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/spatial

has sub-properties
coversSpatialLocationap

technicalContactap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#technicalContact

Entity that is competent to process technical requests about the contribution. SHOULD be asserted to resources of type Contribution.

has super-properties
contact pointap
is also defined as
object property

temporalap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/temporal

has sub-properties
coversTemporalap

themeap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/dcat#theme

has sub-properties
coversTopicap

titleap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#title

Name of the contribution. MUST be asserted to resources of type Contribution.

has super-properties
titleap
is also defined as
data property

titleap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/title

has sub-properties
titleap

versionap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#version

Version identifier of the contribution. SHOULD be asserted to resources of type Contribution.

has super-properties
has versionap
is also defined as
data property

xmlStructureReferenceap back to ToC or Annotation Property ToC

IRI: http://industrialdataspace.org/2016/10/idsv/core#xmlStructureReference

XML Path (XPath) reference to an element or attribute node within enclosing complex XML parameter.

has super-properties
structureReference

Namespace Declarations back to ToC

default namespace
http://industrialdataspace.org/2016/10/idsv/core#
2
http://www.w3.org/ns/odrl/2/
core
http://industrialdataspace.org/2016/10/idsv/core#
dcat
http://www.w3.org/ns/dcat#
dqv
http://www.w3.org/ns/dqv#
foaf
http://xmlns.com/foaf/0.1/
html
https://tools.ietf.org/html/
locn
http://www.w3.org/ns/locn#
ns
http://www.w3.org/2006/vcard/ns#
org
http://www.w3.org/ns/org#
owl
http://www.w3.org/2002/07/owl#
prov
http://www.w3.org/ns/prov#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
skos
http://www.w3.org/2004/02/skos/core#
standards
http://industrialdataspace.org/2016/10/idsv/standards#
terms
http://purl.org/dc/terms/
time
http://www.w3.org/2006/time#
topics
http://industrialdataspace.org/2016/10/idsv/topics#
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.