[Openid-specs-digital-credentials-protocols] OIDC4VP v3

[Tom Jones]

Well i'd like to talk about the   No PE / WICG understands the queries (I
will help with this)
But i was told today it is out of scope so i bailed out assuming that i
needed to go somewhere else!
I wish you guys would make up your mind -

Be the change you want to see in the world ..tom


On Tue, Mar 12, 2024 at 3:16 PM Orie Steele via
Openid-specs-digital-credentials-protocols <
openid-specs-digital-credentials-protocols at lists.openid.net> wrote:

> Hello,
>
> I'd like to repeat my proposal from today' call on this list for
> discussion.
> I'd appreciate it if Kristina could share the link to the proposal she
> presented, regarding what I am calling "PEv2", a profile of PEv1
> incorporating lessons learned, and published by OIDF instead of DIF, if I
> understand correctly.
>
> It was asserted on the call today that both ISO mDoc and OAUTH JWT VC
> work with "PEv1" as defined in "OpenID for Verifiable Presentations - draft
> 20".
>
> If that's true, I think it's a waste of time to discuss profiling of PE
> further.
>
> Interoperability has been demonstrated, implementations exist, implementer
> feedback has been gathered.
>
> Further restricting PE based on that feedback will continue to improve
> interoperability for PE based flows, but we can all see the writing on the
> wall.
>
> I don't feel the effort spent to further restrict PE is a good use of
> working group call time.
>
> Instead I propose the following:
>
> Assign a URN to OIDC4VP draft 20 with PE JSON Schema unmodified, something
> like:
>
> "urn:ietf:params:oauth:oidc:vp:pe:v1"  request for it to be registered,
> and make it clear that it is frozen effectively immediately.
>
> "urn:ietf:params:oauth:oidc:vp:pe:v2"  request for it to be registered,
> create a separate document to track "using PE moving forward", and let
> people who want to contribute to that document, contribute to it... let me
> know when this is, so I can avoid joining it... I have limited time to
> contribute, and I would like to dedicate my time to replacing PE with
> something else, not patching it until it is unrecognizable.
>
> "urn:ietf:params:oauth:oidc:vp:w3c:v1"  request for it to be registered,
> create a separate document to track "designing a format specific query
> language", to be coordinated with WICG, that's basically what this document
> is supposed to become, even though the first part of the document is
> focused on "urn:ietf:params:oauth:oidc:vp:pe:v1" :
>
>
> https://docs.google.com/document/d/1A10PZ_DviMJeyy2mDFt2QLcXUbT4O2dc_BizNXAD2PQ/edit#heading=h.txx2wxvypaci
>
> ... let me know when the call for this ^ will be so I can attend.
>
> TLDR; Please separate the discussion of PEv1 (work completed), PEv2 (good
> luck) and No PE / WICG understands the queries (I will help with this), so
> that we don't see them mixed into every working group call related to
> OpenID 4 VP.
>
> Regards,
>
> OS
>
> --
>
>
> ORIE STEELE
> Chief Technology Officer
> www.transmute.industries
>
> <https://transmute.industries>
> --
> Openid-specs-digital-credentials-protocols mailing list
> Openid-specs-digital-credentials-protocols at lists.openid.net
>
> https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20240312/a2ac242a/attachment.html>