Mandate DCQL instead of PE; all DCQL features are mandatory

[c2bo]

Closes #140.

I guess the biggest discussion point currently missing would be the mandatory DCQL features (also closes #142).

(also adds missing document history if you are wondering about that part)

[tlodderstedt]

WG Call 9.1.25

• Consensus to make DCQL as it is specified MTI in HAIP and simplify the text to make it MTI on the overall level (which means to remove DCQL related text in the mdoc and sd-jwt sections)

[c2bo]

WG Call 9.1.25

• Consensus to make DCQL as it is specified MTI in HAIP and simplify the text to make it MTI on the overall level (which means to remove DCQL related text in the mdoc and sd-jwt sections)

If we agree in #142, that initially there is no profiling of DCQL required, then I think the PR is fine as is and I would just additionally remove the text referencing #142 for sd-jwt and DC API.

[Sakurann]

re-requesting reviews since on top of DCQL being mandatory, all DCQL features are made mandatory

[babisRoutis]

re-requesting reviews since on top of DCQL being mandatory, all DCQL features are made mandatory

Is there any text (in this PR) related to "all DCQL features are made mandatory" or the reference to OpenId4VP implies this?
If the mandatory features are implied, perhaps there is some uncertainty, given that DCQL is still evolving.

PS: BTW, I am not suggesting that HAIP should list the mandatory features.

[Sakurann]

@babisRoutis I think that by not saying which features are mandatory, that means that all are mandatory, but i think i agree we can make that clearer, though I don't know what text can best say that...

[babisRoutis]

@babisRoutis I think that by not saying which features are mandatory, that means that all are mandatory, but i think i agree we can make that clearer, though I don't know what text can best say that...

Given that

• OpenId4VP, which defines DCQL doesn't provide "names" for each feature and doesn't make a distinction between mandatory/optional features
• DCQL developedment was/is driven by a well-defined set of use-cases

I don't think that there is a good reason to explicitly define features to HAIP.

PR looks good as it is now (except the title 😄 )