Current page last modified at: 07-Dec-2017 11:39:31

ATTX Ontology

Table of Contents

Ontology/Data Model - ATTXOnto

The full ontology description and examples are available at:

The ontology/data model has the purpose of describing how and when the data flows within the platform, types of transformations (and associated workflows), the provenance information (agent and associated processes performed) and other meta data.

A general use case is represented in Figure 1 where we can depict several parts:

  • ETL processes associated with the specific steps and workflows - see ETL Workflow for more details and UVProvovenance API which generates such specific information;
  • Provenance Data Graph - which depicts provenance information specific to each workflow, data set etc.;
  • Working Data Graph - contains both inferred and explicit relationships between domain data;
  • Dissemination Data Graph - Data Graph distributed via the APIs.

Figure 1. Ontology Use Cases Flow

Figure 1. Ontology Use Cases Flow

ATTX Graph Namespaces

Base namespaces and/or named graphs convention:

  • - ontology and associated classes
  • - to be used as a base for data
  • - for provenance data
  • - for clusted data ids
  •{workflowID}/work - for working data
    •{workflowID}/infra - for infrastructure
    •{workflowID}/{workflowID}/work/pub - for publication
  • - service whatever comes after the id should resolve the id

The Graph Manager API generates working datasets by following the{generatedID} where the generatedID is a result of hash algorithm. To be pointed out that the is the recommended base for the working datasets.

Example of provenance header in TURTLE format:

@prefix attx: <> .
@prefix attxonto: <> .
@prefix dc: <> .
@prefix dcterms: <> .
@prefix prov: <> .
@prefix pwo: <> .
@prefix rdf: <> .
@prefix rdfs: <> .
@prefix schema: <> .
@prefix sd: <> .
@prefix xml: <> .
@prefix xsd: <> .

ATT Data Model

The Data Model is focused on data interoperability of catalogues and research materials find-ability (e.g. research papers and other types of documents). And as its label states it is a "Application Profile for Research Data Catalogues" or has the purpose to aid in building such an application profile. The main focus seems to be however on the DCTerms vocabulary with concepts such as: FileFormat, LinguisticSystem, LicenseDocument, Location, MediaType, PeriodOfTime, RightsStatement.

The ATT Ontology also builds on the PROV-O with concepts such as Activity, Entity and FOAF (Agent, Project, Document - interesting there is no use of PROV-O Agent - given that between them is the property prov:wasAssociatedWith, however considering the precise definition of a foaf:Agent rather than the broader prov:Agent it justifies the choice. At the same time the use of schema:SoftwareApplication could be introduced and SKOS: Concept, ConceptScheme and DCAT: CatalogRecord, Catalog, Dataset, Distribution. At the same time other utilised concepts are:

On another note the ATT Data Model intertwines Shape Constraints SHACL with constructs such as:

        a                   sh:Shape ;
        rdfs:comment        "A value that allows the contents of a file to be authenticated. This class allows the results of a variety of checksum and cryptographic message digest algorithms to be represented."@en , "Arvo joka mahdollistaa jakelun sisällön tarkistamisen"@fi ;
        rdfs:isDefinedBy    <> ;
        rdfs:label          "Checksum"@en , "Tarkistussumma"@fi ;
        dcterms:created     "2016-05-17T13:26:21"^^xsd:dateTime ;
        dcterms:identifier  "urn:uuid:7950884d-3a5e-4498-be71-1e82cbf6e1dc" ;
        dcterms:modified    "2016-10-24T12:02:53.317+03:00"^^xsd:dateTime ;
        owl:versionInfo     "Unstable" ;
        sh:property         <urn:uuid:9baa0ec8-f994-443d-9793-595ebe498e18> , <urn:uuid:0d4bcc55-523f-4d08-a37c-0fdb8923d630> ;
        sh:scopeClass       <> .


Reference ontologies:

Other models:

results matching ""

    No results matching ""