search

openwallet-foundation / digital-wallet-and-agent-overviews-sig

The objective of this SIG is to develop and maintain the Digital Wallets and Agents Overview. The overview should provide transparency of the characteristics of wallets and agents in order to allow for an objective comparison and effective decision making on which wallet or agent is applicable for your use case.
https://openwallet-foundation.github.io/digital-wallet-and-agent-overviews-sig/
Apache License 2.0
16 stars 30 forks source link

update fwos and add unmio #126

Open jorgefl0 opened 1 week ago

cre8 commented 1 week ago

Hi @jorgefl0 can you explain why you added Paradym as a dependency? They have listed their agent already as a solution. The definition of a dependency is more the dependency of an SDK, not on what services an agent relies on.

It also seems that unimo is more like a product that is using agent and wallets, but is not a normal agent by the specification since all the agent part is coming from Paradym. So I would more see Unimo like a case study, showing where paradym is used.

jorgefl0 commented 1 week ago

Good day @cre8 ,

I listed Paradym for transparency in the submission. Paradym as a solution enables a software developer to provision cloud agent infrastructure via RESTful API. Does this not meet the "definition" of a dependency? We actually maintain a separate open-source component Paradym Connector as well, part of the farmworker-wallet-os project .

I'm not sure I understand the distinctions you are trying to make. There are already examples of listings that implement other dependencies. Some are annotated accordingly and others are not. Presumably this is because the "dependencies" tracking was added recently?

BC Gov, Holdr+ for example implement Bifold which in turn implements Credo. Similarly, Hologram implements Credo.

Looking at this from a SBOM perspective, it will be interesting to see the complete dependency graph develop over time for the items in this listing. Credo for example implements other relevant SDKs outside of the dependencies formerly annotated. Notable examples are:

Regarding Unmio, Unmio is a low-code solution offering that can be adapted or "white-labeled" to specific business contexts. www.unmio.com is an implementation of this offering but we hope in time there will be more. Perhaps I can change the urlWebsite to the marketplace listing?

cre8 commented 1 week ago

Hi @jorgefl0

Yeah, dependency was added like one month ago so most of the entries are not referencing it correctly. The main goal of the dependencies is the reference to SDKs, that can be used by others. It is not the goal to reference all packages from e.g. the package.json, but to highlight relevant projects for attention. You are right that credo is not a direct dependency, but a dependency of bifold. It would make the overview quite complicated and only highlight bifold as the direct reference. Maybe there is an update required for the logic. I didn't have time to scan all project to add the dependencies by myself, so hopefully the providers or anyone else will do this in the future.

The wallet and agent entries should be apps/products with the primary focus on digital identities and credentials. There are however solutions like unmio where digital identities are part of the product. By adding this, it would be an overview of all products that have digital identities integrated, but not offering it for other products. I would like to bring this questions to the next meeting to discuss this with other people and then come back to you.