Scope of Universal Wallet Interop Spec work item

[NTonani]

I wanted to start a conversation around the scope of this work item / repository. As I understand it now, and especially given our recent name change, this work item is for standardizing an interface + data models that provide for protocol interoperability and data portability among wallet vendors/implementors, plus proving through experimental implementations and test suites. I see tremendous utility in that alone, not the least of which is promoting portability to prevent vendor lock-in and data silos, and providing a more interconnected ecosystem.

I also see value in extending this work item beyond above - to what extend I'd love for us to discuss. A couple reasons why:

1. Interoperability does not just suggest protocol interop (I.e. exchange credentials with a user using a different wallet). It also suggests interoperability of data, creating a 1-n wallet-application relationship. In this light, it's important we address the additional layer of complexity that comes from this separation. This seems aligned with (https://github.com/w3c-ccg/universal-wallet-interop-spec/issues/17), though an extension of it.
2. It may be in the best interest of the community, including coowners, to provide an implementation alongside this that extends beyond the spec and provides something usable by applications. Some recent work in creating a builder pattern for enabling pluggable functionality (https://github.com/w3c-ccg/universal-wallet-interop-spec/pull/20), for example, seems aligned with the sentiment (though I understand it does not suggest a fully usable reference impl - and I am open to it all).

I know that the original proposal was to keep spec here and potentially move an implementation elsewhere (https://lists.w3.org/Archives/Public/public-credentials/2020Jun/0158.html), but it seems we may coolocate them for now!

Would love thoughts.

[OR13]

I intend to keep the "sample implementation" co-located until we have consensus to move it.

Is this issue essentially a wrapper around #17 and #20 ?

I am having some trouble parsing the question from this as written.

[NTonani]

@OR13 This was more an attempt at getting us to (at least informally) extend the use of this repo to explore and collaborate on wallet needs beyond spec. While gleaning scope of the work item from repo activity, I found a few examples that I felt were already in that light.

I'm hoping to have a conversation of what this work item (perhaps more concretely, this repo) should and shouldn't be for 😄

[OR13]

@NTonani I am very open to adding additional modules to this repo, as is needed to support the work item. since its already structured as a mono repo, this is trivial todo, however the general idea is to document what is needed in a spec in addition to providing code / supporting software.

when you say "beyond spec", I am not sure what you mean?

So far the repo contains:

• wallet interop spec
• javascript wallet implementations that support the spec
• react / material ui that support the javascript implementation

There has been discussion about splitting the spec into a data model and interface spec, I'm very open to this.

What specific changes would you like to see, or are there things you would like to see removed from this repo?