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

Was this helpful?

  1. Contributing
  2. Procedures
  3. Taxonomy enrichment

Taxonomy updates

PreviousTaxonomy enrichmentNextPlatform Notifcations

Last updated 10 months ago

Was this helpful?

The procedure for releasing updates to the taxon files is detailed below:

  1. Initial changes are submitted to .

  2. Changes are approved & merged by a project administrator.

  3. Updated JSON-LD and RDF files are generated by export from vocBench (ensuring both Graph "http://www.w3.org/2004/02/skos/core" and the "Include Inferred" option are checked).

  4. Updated files are pushed to the , on the nextTaxon branch.

  5. Reviews are completed and the updated files are merged into the main branch.

  6. Following the appropriate flow (determined by whether it's a Patch, Minor, or Major Release).

  7. A new release is generated and updated JSON-LD and RDF files are published to the latest release folder for the contexts to read.

🚧
vocBench
github repository