DFC standard specifications
DFC Use Cases
DFC Use Cases
  • Introduction
  • Sources and licences
  • Contact and partners
  • Semantic specifications
    • Business ontology
    • Product ontology
    • Technical ontology
  • Technical specifications
    • Protocols specifications
    • Decentralized identifier matching reference system
    • Specifics API
    • Authentication strategy
    • Architecture representations
  • Prototype specifications
  • 🚧Solid client protocol
  • 🚧Connector
    • Model specifications
    • Semantizer specifications
    • Connector specifications
  • Use Cases
    • Enterprise Use Cases
    • Product Use Cases
      • Product Transformations
      • CSA Use Cases
    • Orders
    • Order Use Cases
      • Wholesale Order Processing
    • Glossary of terms
  • Appendixes
    • Appendix 1. General decisions
      • Federation vs Syndication
      • Stateless or stateful?
      • Service granularity
      • Directionality
      • Identification and authentication
      • Centralized or decentralized data storage
      • Metadata repository
    • Appendix 2. Technical decisions
      • Libraries to develop in semantic
      • Transition strategy fron current to ideal
      • Service standard
      • Serialization
      • Transport layer
      • Multi- or single-resource requests?
      • Right delegation between platforms and DFC
      • Data validity and inferences
    • Appendix 3. Practical Examples
      • Version 1.9
      • Version 1.8.2
      • version 1.7.4
      • version 1.7.3
      • version 1.7.1
      • version 1.7
      • version 1.6.2
      • version 1.6.1
      • version 1.6
      • version 1.5.1
      • version 1.5
      • version 1.3
      • version 1.2
  • Contributing
    • Procedures
      • Updates to the ontology
        • Patch releases procedure
        • Minor releases procedure
        • Major releases procedure
      • Taxonomy enrichment
        • Taxonomy updates
    • Platform Notifcations
  • Platform Register
    • Platform Register
Powered by GitBook
On this page
  • Why semantic?
  • Ontologies
  • Access to code source

Was this helpful?

Semantic specifications

PreviousContact and partnersNextBusiness ontology

Last updated 10 months ago

Was this helpful?

Before diving into the technical aspect of the standard, we will focus a bit on the semantic aspect of it as it will help to get a better overview of the core objects and their interactions.

Why semantic?

The DFC Consortium chose to build the standard using semantic standards. In terms of interoperability, this approach makes total sense and allows us to use robust technologies to complete our objectives. It is an important decision, it will help us to improve the standard in the future, and also to give us more possibility in interoperability automation.

You can find more information about this choice in this .

Ontologies

Semantic specifications are expressed with files called onotologies. It is using Web Ontology Language (), based on other standards such as XML and RDF.

We are actually using 3 main files (and a fourth one to synthesise the three):

  • Full ontology published on

Access to code source

These ontologies are publicly available and you can find the source files on:

  • which is used in order to maintain and share the source files.

  • which is a well known library helping our standard to be discovered by other people using and reusing semantic ontologies.

appendix
OWL
Product ontology
Business ontology
Technical ontology
LOV
Github
Linked Open Vocabularies