RE: Tim Berners-Lee: He Created the Web. Now He’s Out to Remake the Digital World.

Adrian,

Based on what I’ve learned so far having built the 2 sample apps in the Inrupt Getting Started Guide (https://twitter.com/mwherman2000/status/1349469330988101632) (aka I’m now #poddytrained 😉) and from some of their presentations, a Solid pod is a base/low level, hierarchical folder-based, secure RDF schema-based content store/container.

How these pods and folders are used appears to be quite flexible – both from a deployment perspective (mobile device, PC, local server, central server, cloud server) as well as a content storage perspective.  A Pod can serve as the backend store for a mobile wallet, cloud wallet, or as a general data store.

I haven’t figured out:

  1.  Is content stored in a Pod verifiable? …i.e. signable in a verifiable way.



  1.  How a decentralized identity model can or would plug into the Solid Pod architecture?


  1.  Can the same entity live in multiple folders within a pod and/or multiple folders in multiple pods?  What sort of replication/synchronization solutions are imagined?  …is it singe master? …or multi-master (like Groove Workspace storage model used to be https://www.youtube.com/watch?v=lOAY0fOfNNc)?





  1.  Scalability of a Pod?  Can I store billions of business documents in a pod?  Can a store the entire business process execution history associated with each of these documents? If millions of these business documents are being processed per day, that is the execution/retrieval performance/scalability of a pod?

Michael

From: Adrian Gropper <agropper@healthurl.com>
Sent: January 14, 2021 8:03 PM
To: Michael Herman (Parallelspace) <mwherman@parallelspace.net>
Cc: Heather Vescent <heathervescent@gmail.com>; W3C Credentials CG (Public List) <public-credentials@w3.org>; Dmitri Zagidulin (dzagidulin@gmail.com) <dzagidulin@gmail.com>; Sarven Capadisli (info@csarven.ca) <info@csarven.ca>
Subject: Re: Tim Berners-Lee: He Created the Web. Now He’s Out to Remake the Digital World.

Solid has fallen into the same trap as all first-generation people-centered technologies of linking storage of personal information to control of personal data. Yes, it's easier to control data about you if you also store that data but the problem is that almost nobody cares about the data you have in storage - they have their own copies of that data and their own ways of monetizing it whether you have a Solid Pod or not.

I'm looking forward to scalable people-centered technologies where personal data is controlled without having to be copied into a PDS. Proper authorization standards like GNAP introduce a separation of concerns between who has the data and who controls how it's used. If we understand the case for end-to-end encryption, why would we insist that two of our service providers must transfer data through my Pod as a way to share it?

I'm told by people who work on Solid that they could adopt authorization standards to provide independent control over what's in my Pod. Yet they haven't AFAIK. I would not trust Solid as being person-centric until they provide me with standards-based authorization for access control to what is in my Pod. Otherwise, they're just like Apple who controls access to my health record stored on my iPhone based on opaque App Store policies and proprietary app APIs.

Adrian

On Thu, Jan 14, 2021 at 9:23 PM Michael Herman (Parallelspace) <mwherman@parallelspace.net<mailto:mwherman@parallelspace.net>> wrote:
There is already 3-4 years of sources of general information on Solid (e.g. Inrupt forums, Solid CG Specifications, Technical Report, YouTube videos, etc.).

In terms of inter-CG communication/discussions, I’m interested in Inrupt/Solid’s directions in terms of its adoption of:


  1.  Decentralized Identity Models
  2.  Self-Sovereign Identity Models (a subset of the above)
  3.  Other points of potential intersection

Best regards,
Michael

From: Heather Vescent <heathervescent@gmail.com<mailto:heathervescent@gmail.com>>
Sent: January 14, 2021 9:54 AM
To: W3C Credentials CG (Public List) <public-credentials@w3.org<mailto:public-credentials@w3.org>>
Subject: Re: Tim Berners-Lee: He Created the Web. Now He’s Out to Remake the Digital World.

All,

The CCG and Solid co-chairs are discussing coordinating introductory presentations from each group to each group in order to jump start collaboration -- this will likely happen in February.

CCG members: what questions on Solid would you like answered?

More details as they happen.

Cheers,

-Heather

On Thu, Jan 14, 2021 at 1:27 AM Kishore Bhatia <kishore@affinidi.com<mailto:kishore@affinidi.com>> wrote:
Thanks for shedding some more light on this Michael and Dmitri, have been following Solid/Inrupt’s launch from community pods to ESS and very interested in convergence or parallels with Secure data storage!

Looking at Solid again in 2021 for VC compliant storage: encrypted data vault, maybe even Cloud-agents/identity-hub like components in Affinidi’s architecture, would be great to sync’up with you direct on the identity/VC relevant roadmap so far - will ping direct!

Cheers!
Kishore


On Thu, Jan 14, 2021 at 12:39 AM Dmitri Zagidulin <dzagidulin@gmail.com<mailto:dzagidulin@gmail.com>> wrote:
>  Is there anyone from the Solid project or Inrupt a member of CCG?

I'll add my name to that list as well -- I'm an active participant in the Solid project (am one of the core spec editors, implementer, etc) as well. And in general, try to bring Solid's perspective to various w3c groups I'm part of (including the Confidential Storage group).



--
Heather Vescent<http://www.heathervescent.com/>
Co-Chair, Credentials Community Group @W3C<https://www.w3.org/community/credentials/>
President, The Purple Tornado, Inc<https://thepurpletornado.com/>
Author, The Secret of Spies<https://amzn.to/2GfJpXH> (Available Oct 2020)
Author, The Cyber Attack Survival Manual<https://www.amazon.com/Cyber-Attack-Survival-Manual-Apocalypse/dp/1681886545/> (revised, Dec 2020)
Author, A Comprehensive Guide to Self Sovereign Identity<https://ssiscoop.com/>

@heathervescent<https://twitter.com/heathervescent> | Film Futures<https://vimeo.com/heathervescent> | Medium<https://medium.com/@heathervescent/> | LinkedIn<https://www.linkedin.com/in/heathervescent/> | Future of Security Updates<https://app.convertkit.com/landing_pages/325779/>