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
  • UML profile
  • Stereotypes
  • Interfaces
  • Classes

Was this helpful?

  1. Connector

Model specifications

Our UML model is the source we use to generate the source code of our connector in various programming languages thanks to "model to text transformation" (M2T).

We have defined a UML model to use the DFC ontology within an application.

UML profile

Stereotypes

Stereotype
Range
Description

property

Property

Marks a class variable. Attributes: getter, setter. The two attributes both target an operation of the model. The getter attribute should point to the operation responsible to get the value of the class variable. The setter attribute should point to the operation responsible to set the value of the class variable.

propertyMultiple

Property

Marks a model property used to define a class variable that is a collection. Attributes: getter, setter, adder, remover. The getter and setter are inherited from the property stereotype. The adder attribute should point to the operation responsible to add a value to the class variable. The remover attribute should point to the operation responsible to remove a value of the class variable.

constructor

Operation

Marks a constructor method.

initializer

Parameter

Marks a parameter used to initialize the value of a class variable. This stereotype should be applied on constructor parameters. Attributes: property. The property attribute should point to the class variable the parameter will initialize.

initializerParent

Parameter

Marks a parameter used to initialize the value of a parent class variable. This stereotype should be applied on constructor parameters. Attributes: property. The property attribute should point to the class variable the parameter will initialize.

getter

Operation

Marks an operation used to get the value of a class variable.

setter

Operation

Marks an operation used to set the value of a class variable.

adder

Operation

Marks an operation used to add a value to a class variable.

remover

Operation

Marks an operation used to remove a value from a class variable.

semantic

Element

Marks an element mapped to a term of an ontology. Attributes: map. The map attribute should contain the URI of the mapped ontology term.

blankNode

Class , Interface

Marks a class or interface as a blank node.

skosBroader

Property

Marks. Attributes: map. The map attribute should contain the URI of the mapped SKOS term.

Interfaces

To be written.

Classes

To be written.

PreviousConnectorNextSemantizer specifications

Last updated 10 months ago

Was this helpful?

🚧