types_values in DCQL should refer to expanded form

[awoie]

Currently, the DCQL query param for W3C VCs to specify the type value uses types_values which is ambiguous.

The following examples refer to different type values:

{
  "@context": "https://example.com/person/1",
  "@type": "Person"
}

{
  "@context": "https://example.com/other/1",
  "@type": "Person"
}

How to solve this:

Say that types_values have to refer to the expanded form of the type values, e.g., https://example.com/person/1#Person, https://example.com/other/1#Person.

[c2bo]

Good catch - needs to be fixed imho and the expanded type form seems like a good idea that makes matching robust.

[TimoGlastra]

We did the same for PEX v1, i think this makes sense yes