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 a prototype?
  • Roadmap
  • API Data Format
  • Access to source code

Was this helpful?

Prototype specifications

Why a prototype?

After the first iteration of the DFC Standard, we chose to develop a prototype in order to use this standard in a practical example. This helped (and is still helping) us a lot to improve the standard over iterations as there are always some small differences between theoritical design and experimental applications. To get quickly this feedback allows us to adjust our specifications with real cases, and this is why we also want to share these information in this book.

Roadmap

It follows, of course, our standard definition. You will find then the different milestones for past, present and future development.

What we did so far is:

  • Implement authentication with OIDC

  • Read catalogs from different API following the DFC standard

  • Link items from these different catalogs with an intuitive UI

What we are currently doing is:

  • Write data on API following the DFC standard

  • Improve internationalization

What we aim to is:

  • Synchronize catalogs between platforms, especially on logistic aspect

  • Synchronize orders between platforms

API Data Format

Access to source code

PreviousArchitecture representationsNextSolid client protocol

Last updated 10 months ago

Was this helpful?

The data frames we designed evolved during the development and you can find the different versions in .

The current recommenced format is the .

To access the code source of the DFC Prototype, we are suggesting to take a look a our Github project: .

You can also find technical information .

You can find more details at the wiki section: . It will help you to install the prototype, to use it, and to connect your application to it if you wish.

Appendix 3 - Practical Examples
version 1.5
DFC Prototype
here
https://github.com/datafoodconsortium/dfc-prototype-V3/wiki