Normative version inconsistency for SD-JWT VC in 1.0 final

Whilst working on the implementation, one of my colleagues noted an inconsistence In the normative references section of the spec for SD-JWT VC.

It points to draft 10 in the normative references, but then in section 13.4 it points to version 9. To make matters worse, that last section mentions to always use the version listed in that section in case the respective draft would be updated and breaking changes would be introduced.

So that section basically says to use draft 9, whilst the formal normative references section mentions draft 10. Section 13.4 is a bit vague anyway. It tries to convey something that it should only be the case if breaking changes are introduced. But it is not a burden to put on an implementor of this spec IMO, and simply leaves room for interpretation and thus interop problems.

Happy to make a PR, but then would need to know which one prevails. Assuming 1.0 Final is out, I guess it would become draft 9 actually and 10 for future versions of this spec. However 13.4 does not really make clear these are normative statements, so you could also say that the only normative version is 10

Compare the normative references in sections 13.4 and 16 of the OpenID4VP 1.0 specification, then confirm with maintainers which SD-JWT VC draft governs the final version. Done means the referenced versions and the wording about future breaking changes are consistent and unambiguous.