<div dir="ltr">Well i'd like to talk about the
No PE / WICG understands the queries (I will help with this)<div>But i was told today it is out of scope so i bailed out assuming that i needed to go somewhere else!</div><div>I wish you guys would make up your mind - </div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span style="background-color:rgb(242,242,242);color:rgba(0,0,0,0.9);font-family:-apple-system,system-ui,system-ui,"Segoe UI",Roboto,"Helvetica Neue","Fira Sans",Ubuntu,Oxygen,"Oxygen Sans",Cantarell,"Droid Sans","Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Lucida Grande",Helvetica,Arial,sans-serif;font-size:14px;white-space:pre-wrap">Be the change you want to see in the world </span>..tom</div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 12, 2024 at 3:16 PM Orie Steele via Openid-specs-digital-credentials-protocols <<a href="mailto:openid-specs-digital-credentials-protocols@lists.openid.net">openid-specs-digital-credentials-protocols@lists.openid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello,<br><br>I'd like to repeat my proposal from today' call on this list for discussion.<br>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.<br><br>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".<br><br>If that's true, I think it's a waste of time to discuss profiling of PE further.<br><br>Interoperability has been demonstrated, implementations exist, implementer feedback has been gathered.<br><br>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.<br><br>I don't feel the effort spent to further restrict PE is a good use of working group call time.<br><br>Instead I propose the following:<br><br>Assign a URN to OIDC4VP draft 20 with PE JSON Schema unmodified, something like:<br><br>"urn:ietf:params:oauth:oidc:vp:pe:v1" request for it to be registered, and make it clear that it is frozen effectively immediately.<br><br>"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.<br><br>"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" : <br><br><a href="https://docs.google.com/document/d/1A10PZ_DviMJeyy2mDFt2QLcXUbT4O2dc_BizNXAD2PQ/edit#heading=h.txx2wxvypaci" target="_blank">https://docs.google.com/document/d/1A10PZ_DviMJeyy2mDFt2QLcXUbT4O2dc_BizNXAD2PQ/edit#heading=h.txx2wxvypaci</a><br><br>... let me know when the call for this ^ will be so I can attend.<br><br>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.<br><br>Regards,<br><br>OS<br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><span><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;padding:10pt 0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(32,18,77);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap">ORIE STEELE</span><span style="font-size:10pt;font-family:Arial;color:rgb(32,18,77);background-color:transparent;font-weight:700;vertical-align:baseline;white-space:pre-wrap"><br></span><span style="font-size:10pt;font-family:Arial;color:rgb(32,18,77);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">Chief Technology Officer</span><span style="font-size:10pt;font-family:Arial;color:rgb(32,18,77);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><br></span><span style="font-size:8pt;font-family:Arial;color:rgb(32,18,77);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">www.transmute.industries</span></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;padding:0pt 0pt 10pt"><a href="https://transmute.industries" target="_blank"><img width="96" height="22" src="https://ci3.googleusercontent.com/mail-sig/AIorK4xqtkj5psM1dDeDes_mjSsF3ylbEa5EMEQmnz3602cucAIhjLaHod-eVJq0E28BwrivrNSBMBc"></a><br></p></span></div></div></div></div></div></div></div>
-- <br>
Openid-specs-digital-credentials-protocols mailing list<br>
<a href="mailto:Openid-specs-digital-credentials-protocols@lists.openid.net" target="_blank">Openid-specs-digital-credentials-protocols@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols" rel="noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols</a><br>
</blockquote></div>