Strengthen the Attribute model beyond string to ensure semantic robustness

Title

Strengthen the Attribute model beyond string to ensure semantic robustness

Summary

The current draft of ETSI TS 119 478 defines Attribute:value only as string.
This limits semantic precision and causes implementation risks, especially for cross-border attribute verification.

Submitted for:
Mobil Krankenkasse (statutory public body under German law)
Contact: Sascha Block, IT Architect

Problem / Background

  • The current model does not enforce datatypes or structural constraints.
  • Experience from national infrastructures (e.g., German Telematikinfrastruktur) shows that weak typing leads to validation errors and inconsistent interpretations.
  • Complex attributes (e.g., identifiers, timestamps, enums) require deterministic typing and format validation.

Proposal / Change Request

  1. Introduce typed schema definitions for each attribute:
    • Use JSON Schema as normative (MUST).
    • Support JSON-LD / CDDL as optional (SHOULD).
  2. Mandate canonical forms and value patterns (e.g. regex for identifiers).
  3. Provide conformance tests and reference instances per attribute.

Expected Benefits

  • Reduced error rates and improved interoperability.
  • Easier validation and automated governance checks.
  • Cross-border consistency and higher semantic trust.

References

  • ETSI TS 119 478 (Draft V0.0.3) – Clause 5.1 / 5.2
  • CIR (EU) 2025/1569 – Catalogue of Attributes
  • W3C DCAT-AP 3.0 / W3C VC Data Model 2.0
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information