Definition of schema and profiling scope

[bitbucket-import-issues]

Originally submitted by mhainework (Mark Haine) on 2025-08-06

The eKYC & IDA WG is doing work around the schema and profiling of some specific identity related data.

There is a need to be clear about the extent of that work.

---

Bitbucket status: new

Bitbucket origin: issue 1475

[bitbucket-import-issues]

Originally submitted by mhainework (Mark Haine) on 2025-08-13

relating to charter of new identity schema WG

[bitbucket-import-issues]

Originally submitted by mhainework (Mark Haine) on 2025-08-20

Initial draft of my thoughts:

‌

Schema Profiling

For each country, industry vertical and or use cases there would seem to be different levels of identity assurance metadata needed.
In cases where the OID4IDA Schema is used, and to aid implementers and the possible interoperability goals between contexts, it would seem to make sense to describe the profiles used in each context in a similar fashion and perhaps make them available for re-use or modification.

Data Value registration

There are various elements of the OpenID4IDA Schema definition that would benefit from having well governed lists of values and values that are registered for various contexts

• registries of object types

  • schemes - maybe
  • assurance levels - yes - international?
  • policies -
  • scheme_procedures - yes - scheme
  • gpg45 confidence levels - yes - UK guidance
  • assurance types - yes - international?
  • assurance classifications - yes - but mapped to GPG45? so scheme level?
  • evidence_classification - yes - but mapped to GPG45? so scheme level?
  • evidence_sub_classification - yes - scheme
  • evidence type - OID4IDA
  • check_method - yes - need to update from OID4IDA Wiki to proper registry
  • document type - yes - international?
  • attachment type - yes - international?
  • (electronic) record type - yes - international?
  • authoritative source type - yes - international?

‌