Page History

...

• Common Data Models: A data model defines the structure and relationships of data elements, providing a framework for how identity information is represented and exchanged. Using standardised attributes, such as those defined by the W3C Verifiable Credentials Data Model, OpenID4VC etc, ensures a “date of birth” or a "person identifier" are consistently structured and interpreted across systems.
• Ontology Alignment: Agreeing on the meaning of terms, such as what constitutes a “verified identity” or a “trusted issuer,” to avoid miscommunication.
• Interoperable Formats: Supporting formats like JSON-LD for credentials to ensure data can be read and processed by different identity wallets.
• Schemas for understanding credentials: Schemas define the specific structure and required attributes for credentials, such as those used in ELM, OpenBadge, EMREX, ELMO, but also different isolated schemas at the national level. These schemas must be interoperable to allow credentials issued in one system to be understood and verified in another. For example, a schema for a digital diploma must specify fields like issuer, recipient, and issuance date in a standardised way.
• Profiles: Profiles are sets of specifications or configurations that define how standards and protocols are implemented to achieve interoperability.
  • A transport interoperability protocol, such as HAIP (High Assurance Interop Profile) or something more lightweight like DIIP (Decentralised Identity Interop Profile), ensures consistent communication between systems.
  • Trust profiles, such as the OpenID for Research and Education (OpenID4RE) Project or  the OpenID Federation for Wallets architecture, establish rules for trust relationships.
  • National profiles, like those bases on ELM, may further specify local requirements for credentials formats and verification processes.

...