You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there is a mismatch between the type used in the spec and the types allowed in the schema.
The spec has non-normative examples with the type BitstringStatusList (see Example 2)
Non of the examples has a context, specifically defined for the BitstringStatusList. The closest is the one for Status List 2021.
As you can see, the schema does not have the type BitstringStatusList, causing JSON-LD validation error. Is there another schema that is supposed to be used together with the BitstringStatusList? If not, either the spec or the schema must be changed to ensure that the JSON-LD can be validated.
Thanks.
Hakan
The text was updated successfully, but these errors were encountered:
msporny
added
the
before-CR
This issue needs to be resolved before the Candidate Recommendation phase.
label
Dec 27, 2023
Yes, agreed. The VCWG renamed the specification to BitstringStatusList, so we will need to update all of the examples and schemas to match. This will be done over the next several weeks.
Hello,
there is a mismatch between the type used in the spec and the types allowed in the schema.
The spec has non-normative examples with the type
BitstringStatusList
(see Example 2)Non of the examples has a context, specifically defined for the BitstringStatusList. The closest is the one for Status List 2021.
As you can see, the schema does not have the type
BitstringStatusList
, causing JSON-LD validation error. Is there another schema that is supposed to be used together with the BitstringStatusList? If not, either the spec or the schema must be changed to ensure that the JSON-LD can be validated.Thanks.
Hakan
The text was updated successfully, but these errors were encountered: