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
  • Platform Notifications for DFC Standard Changes
  • Platform Register
  • Notification of Changes

Was this helpful?

  1. Contributing

Platform Notifcations

PreviousTaxonomy updatesNextPlatform Register

Last updated 7 months ago

Was this helpful?

Platform Notifications for DFC Standard Changes

The DFC strives to ensure no-one using our standard is unduly impacted by changes as we enrich and develop the standard. We will undertake the following measures to ensure this:

  1. We will utilise deprecated flags & sameAS, where possible, to ensure any changes are non-breaking.

  2. We will follow semantic versioning, so any breaking changes should constitute a major version change.

  3. We will support 2 major versions with any urgent patch/fixpack changes.

  4. We will maintain an open register of platforms utilising the standard who will be informed of all changes and consulted on Major changes.

  5. We will notify of all changes via our .

Platform Register

Platforms implementing the DFC standard are encouraged to actively participate in our ongoing community-driven development process, register on our and join our .

We maintain a register of platforms that are implementing our standard in our . You can add your details to this file via a PR or .

Notification of Changes

All registered platforms will be notified, via the details in the Platforms Register, of all changes according to the schedules agreed in the relevant change processes:

Patch/Fixpack Version Releases
DFC-Releases mailing list
Slack workspace
regular calls
Standard Repository
open an issue in the Standard Repository
Major Version Releases
Minor Version Releases