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
  • The main objective of the DFC standard is to allow different platforms to easily read and write data from each other, in an authenticated way and using existing standards.General principles
  • Decisions and choices history
  • About the DFC Prototype

Was this helpful?

Technical specifications

PreviousTechnical ontologyNextProtocols specifications

Last updated 10 months ago

Was this helpful?

The main objective of the DFC standard is to allow different platforms to easily read and write data from each other, in an authenticated way and using existing standards.General principles

Here you will find the core of this book, focusing on how to build the DFC standard.

We divided this chapter into 4 parts:

  • where we will list the existing protocols we are using to build our semantic model, the core of our interoperability engine.

  • where we will explain why we are not building a centralized referential but rather promoting platforms intermediation.

  • where we will discuss the use of OpenID protocol as our authentication layer.

  • where we will finally resume all these information into a nice schema.

Decisions and choices history

As we are documenting most of design decisions and choices, you can find them in the appendixes:

  • .

About the DFC Prototype

In order to give an example of the standard implementation, and especially the intermediation logic behind our interoperability model, we have developed the that you will discover more in the next chapter.

Protocols specifications
Decentralized identifier matching reference system
Authentication strategy
Architecture representations
Appendix 1 - General decisions
Appendix 2 - Technical decisions
DFC Prototype