all/any: Relying Party Registration Metadata Error Response

[Daniel Fett]

In Section 6.4, current wording is:

---

• did_methods_not_supported

  • The Self-Issued OP does not support all of the DID methods included in did_methods_supported parameter.

• subject_identifier_types_not_supported

  • The Self-Issued OP does not support all of the subject identifier types included in subject_identifier_types_supported parameter.

• credential_formats_not_supported

  • The Self-Issued OP does not support all of the credential formats included in credential_formats_supported parameter.

---

I don’t understand the quantifier used here ('all'). Shouldn’t this be ‘any’? For a successful negotiation, only one match is needed.

Also, in the same list:

---

• value_not_supported

  • The Self-Issued OP does not support more than one of the RP Registration Metadata values defined in Section 4.3. When not supported metadata values are DID methods, subject identifier types, or credential formats, more specific error message must be used.

---

That should be “one or more”, I guess?

‌

[Kristina Yasuda]

Issue discussed during 2021-10-14 SIOP call. Agreed to reflect language suggested in this issue (all → any; more than one → one or more)

[Kristina Yasuda]

addressed in PR #61