What are the pipeline naming conventions?

The below conventions will help in building a readable Data Ingestion Pipeline.

Note that URI convention should be applied to any new project. For existing projects, any change should be considered carefully, as it can impact saved discoveries, templates, and dashboards.

General

  • No special characters
  • Snake case (lower case with underscores marking the token)

Class

  • Class Name Format = [source]_[concept]

Predicate

  • Predicates are set with a prefix
  • A colon is used between the prefix and predicate name

Prefix

  • The prefix reflects the data type (such as the concept or class)
  • A colon is used between the prefix and predicate name

Rdf-type/Class type/Resource Type

  •  If there is a public or internal convention for ontology, this convention is used (e.g., foaf, dcat…).
  • Otherwise use the format
    http://ns.[company].com/ontology/classes/[type name]

Instance URI

 In order of priority apply:

  • URI as defined on identifiers.org for described data source and object type
  • URI defined in DISQOVER.com [mandatory for URI matching]
  • URL used for instance centric information
    http://ns.[company].com/[source]/[type]/[identifier/name]

Data Source URI

  • Prevent the use of a dataset URI from the public DISQOVER. This may result in conflicts in the federated setup. Hence, it is not recommended to use the dataset URL or URI referenced on identifiers.org. Go to your DISQOVER's DATA page for the details.
  • Data Source URI Format:
    http://ns.[company].com/disqover.dataset/[name]

Canonical Type URI

  • For a mixed Canonical Type, use the Canonical Type URI as declared on the federated instance (e.g., http://ns.ontoforce.com/ontologies/integration_ontology#Gene). Go to your DISQOVER's DATA page for the details.
  • Local URIs are in lower case, with underscores marking the token
    http://ns.[company].com/disqover.ontology/canonical_type/[ct_name]

Facet URI

  • For mixed facets, use the facet URI as declared on the federated instance (e.g., http://ns.ontoforce.com/2013/facet/enzyme/ClassificationEnzyme). Go to your DISQOVER's DATA page for the details.
  • Local URIs are in lower case, with underscores marking the token. Do not use a colon. 
    http://ns.[company]..com/disqover.ontology/facet/[ct_name]/[facet_name]

Property URI

  •  For mixed properties, use the property URI as declared on the federated instance (e.g., http://ns.ontoforce.com/2013/property/enzyme/Parent). Go to your DISQOVER's DATA page for the details.
  • Local URIs are in lower case, with underscores marking the token. Do not use a colon.
    http://ns.[company]..com/disqover.ontology/property/[ct_name]/[property_name]

Typed Link URI

  • Typed Links cannot be mixed!
  • URIs are in lower case, with underscores marking the token.
    http://ns.[company]..com/disqover.ontology/typed_link/[ct_name1]_[ct_name2]/[property_name]
  • [ct_name1]_[ct_name2] are placed in alphabetical order. 

Subinstance URI

  • For mixed sub-instances use same URI as declared on the federated instance. Go to your DISQOVER's DATA page for the details.
  • Local URIs are in lower case, with underscores marking the token
    http://ns.[company]..com/disqover.ontology/subinstance/[ct_will_appear_in]/[subinstance_name]