DFC standard specifications
DFC standard specifications
DFC standard specifications
  • 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
    • Order states
  • Prototype specifications
  • 🚧Solid client protocol
  • 🚧Connector
    • Model specifications
    • Semantizer specifications
    • Connector specifications
  • 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
      • Ontology releases process
      • Taxonomy enrichment
        • Taxonomy updates
    • Platform Notifcations
  • Platform Register
    • Platform Register
Powered by GitBook
On this page
  • Get Data linked to Connected Users
  • Get examples from all format versions

Was this helpful?

  1. Appendixes

Appendix 3. Practical Examples

PreviousData validity and inferencesNextVersion 1.9

Last updated 4 years ago

Was this helpful?

Get Data linked to Connected Users

  • No specification for url syntax

  • Requests have to fill Authorization Header with JWT OIDC Token obtained thanks to login.lescommuns.org application.

  • Basic authentification

    • Server has to validate token thanks to signature and parse token to obtain preferred_username.

    • This preferred_username can be linked to the Platform User. To link OIDC User and Platform User, platforms can add OIDC authentification feature.

  • Outdated Token

    • If token is outdated, platforms can refuse request.

    • If platforms have to request another (DFC or Other) and receive outaded input token, Platforms can remember refresh token (when OIDC authentication features execution) and ask new access with a specific request.

Get examples from all format versions

As we developed the DFC Standard aside the DFC Prototype, we had to tweak the data format with the standard evolution.

version 1.5
version 1.3
version 1.2