Supported standards
Concert states SIGNET's relationship to each standard precisely, in one of three tiers:
- Normative mapping — in the specification's mapping table; a conforming implementation MUST transform without loss of the mapped fields. Where noted, the mapping is machine-verified in continuous integration.
- Architectural alignment — the standard shapes the canonical model's design, or is reachable through an already-mapped layer.
- Compliance enablement — regulatory and management-system frameworks SIGNET does not implement, whose obligations the architecture helps organisations meet and evidence.
| Standard | Category | Tier |
|---|---|---|
| Peppol BIS 3.0 | Document Exchange | Normative mapping · CI-verified (Billing) |
| UBL 2.3 | Document Exchange | Normative mapping · CI-verified (Invoice) |
| EN 16931 | Document Exchange | Normative mapping · CI-verified |
| UN/CEFACT CII | Document Exchange | Architectural alignment |
| eForms | Document Exchange | Normative mapping |
| W3C VC 2.0 | Identity & Trust | Normative mapping |
| W3C DID 1.0 | Identity & Trust | Normative mapping |
| eIDAS 2.0 | Identity & Trust | Compliance enablement |
| Solid | Identity & Trust | Architectural alignment |
| OCDS | Data Standards | Normative mapping |
| eProcurement Ontology (ePO) | Data Standards | Normative mapping |
| GS1 | Data Standards | Architectural alignment |
| Model Context Protocol (MCP) | AI Protocols | Architectural alignment · forward-looking |
| Agent-to-Agent (A2A) | AI Protocols | Architectural alignment |
| ISO/IEC 27001:2022 | Security | Compliance enablement |
| NIST CSF 2.0 | Security | Compliance enablement |
| NIS2 | Security | Compliance enablement |
| GDPR | Security | Compliance enablement |