[Openid-specs-ab] OpenID Federation Wallet Architectures Draft

[Kristina Yasuda]

Hi all,

Can you please explain how your updated draft addresses any of Joseph's
comments?
https://lists.openid.net/pipermail/openid-specs-ab/2024-August/010370.html

With all respect, but just adding a scope section that it is a profile of
an OpenID Federation does not make it less of a profile of OpenID4VC
specs, without removing any of the sections that have been pointed out as
problematic.

Best,
Kristina

On Mon, Aug 19, 2024 at 5:56 AM Michael Jones via Openid-specs-ab <
openid-specs-ab at lists.openid.net> wrote:

> The authors hereby contribute a second draft of the OpenID Federation
> Wallet Architectures 1.0 specification to the OpenID Connect working
> group.  An HTML rendering of the specification is attached for archival
> purposes.  The source is available at
> https://github.com/peppelinux/federation-wallet and the HTML can also be
> viewed at https://peppelinux.github.io/federation-wallet/main.html.
>
>
>
> Changes relative to the initial contribution are summarized in the history
> entry
> <https://peppelinux.github.io/federation-wallet/main.html#name-document-history>,
> which says:
>
>    - Created Scope section describing the purpose of the document and
>    collaboration with other working groups.
>    - Moved metadata tables and examples to an informative appendix on
>    possible usage.
>    - Fixed #10:
>    Renamed openid_wallet_relying_party to openid_credential_verifier.
>
>
>
> Both the first two points were suggested by Nat as an appropriate way to
> respond to feedback from Joseph and others and to clarify the authors’
> intent to work closely with the DCP working group to define any new
> metadata parameters that would be useful in the OpenID4VC specifications
> there.
>
>
>
> The last point aligned the terminology more closely with that used in the
> OpenID4VC specs.  Other than the identifier change, no normative changes
> were made relative to the initial contribution, other than the removal of
> the normative metadata definitions.
>
>
>
>                                                                 -- Mike
>
>
>
> *From:* Openid-specs-ab <openid-specs-ab-bounces at lists.openid.net> *On
> Behalf Of *Giuseppe De Marco via Openid-specs-ab
> *Sent:* Monday, July 29, 2024 2:30 PM
> *To:* Artifact Binding/Connect Working Group <
> openid-specs-ab at lists.openid.net>
> *Cc:* Giuseppe De Marco <demarcog83 at gmail.com>; andrea.demaria07 at gmail.com;
> Roland Hedberg <kustrask at gmail.com>; Michael Jones
> <mike at self-issued.consulting>
> *Subject:* [Openid-specs-ab] OpenID Federation Wallet Architectures Draft
>
>
>
> Dear OpenID Connect working group,
>
> The authors hereby contribute the attached OpenID Federation Wallet
> Architectures specification to the working group.  It defines OpenID
> Federation entity types for digital wallet architectures.
>
> The specification contents are attached in HTML format.
>
> Additionally, for the convenience of working group members, the
> specification source can be viewed at
> https://github.com/peppelinux/federation-wallet and the rendered HTML can
> be viewed at https://peppelinux.github.io/federation-wallet/main.html.
>
> Best wishes,
>
> Giuseppe
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-ab
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20240819/ad61068c/attachment.html>