This document describes the Reference Architecture and Technical Specifications of the DOME Marketplace system.
This document is divided into the following sections:
DOME General Overview - describes the overall structure of the project, including different roles of users, the overall technical approach and the user journeys.
DOME Trust and IAM Framework - provides a description of the decentralised Trust and Identity and Access Management (IAM) framework which are implemented in DOME.
DOME Marketplace Persistence Layer - provides a description of the DOME Persistence Layer, focusing on the specific goals and priorities associated with its implementation, including the Shared Catalog and the Transactions Layer.
DOME marketplace features - provides a description of the DOME marketplace, including the design of the processes involved in a federated procurement scenario and high-level architecture of the various subsystems delivering such features.
DOME APIs - provides a description of the APIs used in DOME used by providers or federated marketplaces to integrate with the DOME ecosystem.
Appendix I: example of onboarding of organisations in DOME - provides examples with detailed technical descriptions of some user journeys in DOME..
Appendix II: JAdES signatures of Verifiable Credentials - provides a description of the approach to digital signatures of Verifiable Credentials in DOME, to achieve high legal certainty and alignment with the EU eIDAS (and upcoming eIDAS2) regulatory framework..
Appendix III: remote Digital Signature Service (rDSS) - provides a description of the approach to remote/cloud digital signatures, enabling the use of advanced and qualified signatures for Verifiable Credentials and other types of documents, increasing legal certainty and making Verifiable Credentials equivalent to handwritten signed documents.
Following is a list of valuable links to relevant documents and resources:
-
EU Digital Identity Wallet Architecture and Reference Framework
-
DID ETSI Legal person Semantic Identifier Method Specification (did:elsi)
Just create a pull request with your changes to the documents in the src directory. Those are written in Pandoc Markdown format and converted to Github GFM (GitHub Flavored Markdown) format in the docs directory, which is where the user reads the documentation.
The script to convert the documents from src to docs is publish.py. It should be run to update the docs directory.