Daniel Hardman: I can't get onto SIP. sip:ccg@96.89.14.196 doesn't connect for me in linphone, and US phone: +1.540.274.1034 x6306 (the number given in github page instructions) makes me the only participant in the call. ✪
Daniel Hardman: How is everybody else dialing in? ✪
... Then MyData in Helsinki, more info at the link
Joe Andrieu: Two things: the deadline for the RWoT discount is this friday. ✪
Manu Sporny: Markus_sabadello did a fantastic job getting the spec published. the chairs need to call for approval of the community group to hand over the spec to the working group. ✪
... asking for objections to making this the community group final report.
... you put the URL markus_sabadello provided, but only after the 7 day vote.
Manu Sporny: To distill: chairs ask for a 7 day review, then publish, then ask everyone to make IPR commitments. ✪
... that enables the DIDWG to pick it up and move forward.
Joe Andrieu: Do we need help from staff to publish to a W3C domain name? I can follow up ✪
Dan Burnett: If someone made a contribution, but don't agree. It doesn't mean the WG can't use the document, but the group may need to remove the content that hasn't been agreed to ✪
... that's why it is so important to make thies IPR commitment
Markus Sabadello: People can continue to raise PRs and Issues, they will be carried over to the WG ✪
Dan Burnett: To clarify on GitHub issues, the WG will make a decision about how it wants to proceed. We will (strongly) encourage the WG to copy all existing issues to the new WG. ✪
Kim Hamilton Duffy: No need to scribe, because the presentation has the contents ✪
... this has been discussed many places, but not here yet. So this is an informational session.
... please add yourself to the queue if I mess up :)
Kim Hamilton Duffy: Slide 3: we will invite experts to give deep dives on each method ✪
Kim Hamilton Duffy: Slide 6, the medium post is a really good starting point ✪
Kim Hamilton Duffy: Slide 7 - sometimes it is unclear what is meant by the terminology e.g., storage, wallets, protocols ✪
Kim Hamilton Duffy: Slide 8 has secure data hubs added in ✪
... the callout markers are not intended to have anything to do with positioning in the venn diagram
Manu Sporny: I really like this additive approach. I'm wondering if there is a progression where we'll see Solid Pods added in. ✪
Kim Hamilton Duffy: I would be interested in that informally. ✪
Dmitri Zagidulin: I'd certainly be interested in helping fit Solid Pods into that venn diagram ✪
... Solid profiles have a lot of interesting characteristics. Similar to DIDs
... pods are meant for self sovereign dat storage. picking apart the terminology will be important
Christopher Allen: I wanted to add. there are a number of other parties who may want to contribute their stacks. IPFS Agorics, the solid folk. a few others from the DWeb camp ✪
... these three in the slides may be just the beginning.
Kim Hamilton Duffy: We have a few folk, they have experience in these various other things. ✪
Jonathan Holt: Aries agents - are there other agents? ✪
Kim Hamilton Duffy: I've only encountered that in the informal sense ✪
Adrian Gropper: Quick comment. it would be nice in this overview to introduce aspects of privacy or privacy engineering across the different aspects ✪
Manu Sporny: Agents is such a broad thing, a lot of things could fall underneath. the credential-handler-api is it an agent? It is dumb, but can be used as a conduit for credential exchange ✪
... I'm also concerned we're going to run out of time
Kim Hamilton Duffy: I want to set up a straw man: identity hubs/secure data hubs are both storage level ✪
... we need to tease apart the goals and responsibilities of both.
Daniel Buchner: I was originally on the queue to say at microsoft, we are working on an enterprise agent to hold keys ✪
... on the hubs/agents slide. Hubs does describe actions.
... we recognized that task-based flows follow the same paradigm. It generalizes the process so you don't need a bunch of protocols for different events.
Joe Andrieu: I want to throw holochain into the mix, how does it fit in this conversation? ✪
... also, we haven't sent out the email for review of the final did spec.
Manu Sporny: One of the things we may be missing is the use cases that led to the current designs. for example, ✪
... secure data hubs is I have a wallet with things I feel are mine. the spec came from the desire to prevent a digital storage provider from being able to snoop
... also portability, I don't want to be locked into my data provider
... the third thing: what is the minimal set of features other communities could use to build on top of
... secure data hubs are agnostic to authorization mechanisms so they can be used by many different organizations.
Dave Longley: I think "strawman 2" is probably pretty close ... secure data hubs are more fundamental and only focused on storage that is encrypted/decrypted client-side ... vs. identity hubs seem to do more and have more relaxed characteristics but need a storage backend ... and agents clearly have different responsibilities ✪
Kim Hamilton Duffy: I can answer that kezike -- no there is no dedicated presentation for each, but we do give a brief overview in groups ✪
... the secure/encrypted search is important because otherwise the server will be able to peek inside your data. avoiding surveillance capitalism
Kim Hamilton Duffy: Sorry kezike, did that answer your question? I wanted to give Daniel a chance to respond ✪
Daniel Buchner: When we talk about low level things. hubs allow search tags that are not encrypted because when we look at methods for doing this are really expensive. ✪
... is it really possible for this to scale?
Manu Sporny: We spent a lot of time making sure the design is compute-efficient. we can go into that in more detail in the future. ✪
Daniel Buchner: So you're pushing indexes from the client to the server that are hash keyed? ✪
Kim Hamilton Duffy: That can be a follow up session ✪
Manu Sporny: Daniel, effectively,yes... with some handwaving :) ✪
Kim Hamilton Duffy: I have a lot of questions about how that happens ✪
Ryan Grant: I'd like to understand the encryption/search design better as well. ✪
Daniel Buchner: Just trying to figure this out, because we looked at multiple ways to do this, and all sort of break when you take it out of cottage industry/hobbyist realm ✪
Daniel Buchner: We think we have something that works at the enterprise level :) [scribe assist by Manu Sporny] ✪
Manu Sporny: But would love feedback on it, happy to share our solution in this group. ✪