Skip to content

Base credential schema still pins deprecated StatusList2021Entry #153

Description

@MoltyCel

schemas/delegation-credential.json:235 pins credentialStatus.type to const: "StatusList2021Entry", while the two Card-profile schemas already carry the successor: schemas/card-delegation-credential.json:148 pins const: "BitstringStatusListEntry", and schemas/kya-os-card.schema.json:182 defines a BitstringStatusListEntry $def describing it as "the StatusList2021Entry successor". SPEC.md:826 states the same direction: W3C Bitstring Status List v1.0 as "the successor to the deprecated StatusList2021".

The base credential schema was left behind by that migration. A base-profile credential issued with a BitstringStatusListEntry status entry — the form the spec mandates — fails schema validation, and one that passes validation carries the deprecated type.

Proposal: move schemas/delegation-credential.json to BitstringStatusListEntry, matching the Card schemas, and keep StatusList2021Entry accepted for a deprecation window if existing credentials need it. If the base profile is meant to stay on StatusList2021, the spec text needs to say so instead.

Reported by @IzuruToys in decentralized-identity/trusted-ai-agents#42, in the context of a delegation with no revocation mechanism at all — credentialStatus is absent from the schema's top-level required list: decentralized-identity/trusted-ai-agents#42 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions