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
  • Platform
  • User
  • Prototype
  • link
  • linkSimple
  • my-data

Was this helpful?

  1. Technical specifications

Specifics API

DFC Protocol is defined here but one specific API is requiered on Platform . In addition DFC server provides some sepecific API.

PreviousDecentralized identifier matching reference systemNextAuthentication strategy

Last updated 10 months ago

Was this helpful?

Platform

User

Platform have to provide an url to obtain data about user thanks to OIDC Authentification. All users data must be return by the API and platform have to take OIDC Token into account to identify and authentify user. Those data contains sufficient data to get all other data linked to user as product, offers and all class defined in .

This API have to implement (LDP, OIDC,Ontologies...). API is designed for this use.

Platform have to contact DFC to add this url to be inclued in the Consortium.

Prototype

link

Main usage of DFC server is to provide identifier reconciliation of platforms included in consortium. A non LDP API provides this feature to platform : "What are identifiers (uri) of data in others platforme from my uri".

https://server/link/myPlatformDataUri

Result of this API use whith pivot.

{
    @id : myPlatformDataUri,
    host : {
        @id : myPlatformUri,
        label : my platform
    }
    pivot : {
        @id : pivotUri,
        represents : [
            {
                @id : otherPlatformDataUri1,
                host : {
                    @id : otherPlatformUri1,
                    label : other platform 1
                }
            },
            {
                @id : otherPlatformDataUri2,
                host : {
                    @id : otherPlatformUri2,
                    label : other platform 2
                }
            }
        ]
    }
}

linkSimple

This more compact and more Simple API compute link API to standard sameAs predicates.

https://server/linkSimple/myPlatformDataUri
{
    @id : myPlatformDataUri,
    owl:sameAs : [
        otherPlatformDataUri1,
        otherPlatformDataUri2
    ]
}

my-data

Return prototype data of a platform data. owl:sameAs added to platform provided data

https://server/my-data/myPlatformDataUri
{
	@id": myPlatformDataUri,
	predicate : value
	owl:sameAs: [
	        otherPlatformDataUri1,
	        otherPlatformDataUri2
	]
Business Ontology
technical specification
Example
Technical Ontology