The Trustflows Community Charter
Mission
With this charter, the Trustflows community expresses the ambition to strengthen the position of “Datatech made in Flanders” as a quality label in Europe and beyond.
By participating in the Trustflows community, members agree to the principles and commitments below.
Principles
The solutions developed by the Trustflows community will be:
-
Interoperable: The European Interoperability Framework will guide us in fostering European (and global) interoperability on multiple levels.
-
Compliant: The governance and tooling will help to comply with relevant EU legislation.
-
Trusted by end-users: The end-user is put in the center, empowered to control their data sharing interactions.
-
Secure: Data sharing interactions will be protected using battle-tested security mechanisms to ensure confidentiality, availability, and integrity.
Commitments in Data Architectures
-
Document data model schemas. The schemas must document the meaning of their terms in reusable vocabularies.
-
Capture new interaction patterns in a use-case agnostic way so the wider community can reuse them.
-
Treat write and read models as separate concerns. What you store is rarely identical to what downstream actors need, so Trustflows demand explicit write and read projections. Alignments between vocabularies must be documented, so that the alignment between schemas can be automated.
-
Publish an implementation guide. Describe every project as a composition of interaction patterns and schemas, so other members can reproduce the product without requiring them to reuse the exact implementation.
Commitments as Community Member
-
Educate the main architects and developers in Linked Data and data governance, using or contributing to the courses highlighted in the education section.
-
Disseminate implementation guides, mappings, and interaction patterns with the Trustflows community through events and the website so the collective body of knowledge continues to grow.
-
Maintain artefacts (schemas for both write and read, mappings, event definitions) in accessible repositories and announce updates so other members can build their read models.