
11:36
Can you reshare the agenda link please?

11:51
https://wiki.trustoverip.org/display/HOME/2023-01-18+TSPTF+Meeting+Notes

12:01
Thx Phil!

13:54
https://trustoverip.org/get-involved/membership/

23:54
Hi! No microphone here right now.Veikko Eeva, I'm a co-fonder in Lumoin. We're working in built environment related issues, such as deconstruction, renovation, construction and slowly and surely towards project financing in general. Also working on DID & VC library in .NET (public repo in GH a bit lagging, but should update soonish).

23:58
No, I’m Alex from Roots ID

25:31
https://wiki.trustoverip.org/display/HOME/Trust+Spanning+Protocol+Task+Force

28:54
https://trustoverip.org/blog/2023/01/05/the-toip-trust-spanning-protocol/

29:00
https://trustoverip.org/our-work/evolution-of-the-toip-stack/

30:01
https://trustoverip.org/permalink/Design-Principles-for-the-ToIP-Stack-V1.0-2022-11-17.pdf

30:19
https://trustoverip.org/our-work/technical-architecture/

36:10
Good to see the 3-party Issuer-Holder-Verifier model take lesser role …"just one kind of trust path" :-)

37:30
Is DIDComm Layer 2 or Layer 3? ...me thinks Layer 2

37:47
Exactly Michael. This was a great collaborative realisation & decision while we worked on the Tech Architecture. We had 100+ slides pertaining viewpoints from multiple contributors.

38:11
DIDComm is layer 2.

38:20
Yes! :-)

39:02
Michael, I see you have your hand up, you’re next

42:25
It also totally lines up with Paster Hardman and the Great Unit Church movement as well ;-) :-)

42:36
...Great Unity Church

42:57
pls provide link to the '100+' slides

43:42
https://docs.google.com/presentation/d/14YPhH66yfOetrSfuycuFOgQqxzGZ0b7H22EZDhilphU/edit#slide=id.p

43:54
Sorry, only 95, misspoke ;)

44:03
:-) thanks!

48:37
Again, the link to blog post is https://trustoverip.org/blog/2023/01/05/the-toip-trust-spanning-protocol/

50:03
so DWN layer 2 would be HTTPS?

50:42
the core “co-protocols” are Layer 2, Layer 3 would be the specialized - we have a diagram somewhere that starts to explain that too

51:25
@Michael you can create applications level protocols ex: https://gist.github.com/csuwildcat/2ac6ebf4c581c5df143c32fa4911850e

51:46
DWNs are directly from the Secure Data Storage box in Layer 1 ...DWNs are not Layer 2

51:53
Have to disagree that a DWN is only a “storage protocol.” The DWN spec includes a message-based protocol, semantic data discovery, etc.

52:09
@Michael - I suggest talking that discussion to the TAS GitHub

52:51
@Frank - agreed - there are multiple-layers to DWN. I think the 4-layer model helps split that out and tell a story about what is where.

53:03
it is permissioned crytpographic data... which is what all applications come down to not just a filesystem type of replication

54:13
Suggest: Trust Spanning - minimal layer that does not preclude support for a variety of higher level protocols that build on a common base, minimal layer

54:24
+1

54:32
RE: @Michael you can create applications level protocolsThe DWN storage protocol may be "application level" protocols that they are still storage level procotols. They are only for manipulating storage in DWNs.

55:21
...and for raising storage events

56:21
Restating...The DWN storage protocol may be used to create "application level" protocols that they are still storage level protocols - none the less. They are only for manipulating storage in DWNs ...and supporting storage-level events.

56:46
The whole thesis of a DWN ( according to the spec ) is a “data storage and message relay node”. The message layer is defined here: https://identity.foundation/decentralized-web-node/spec/#messages . I agree with Frank that it’s more than a storage protocol.

57:14
https://trustoverip.org/our-work/technical-architecture/

57:45
Maybe "storage centric protocol" is a better term for DWNs ...it can't and shouldn't be equated with being on the same level as DIDComm

58:25
If there is anyone else that you think should be in this Task Force. Please invite them to attend the meeting next week. We want all the voices heard and participating.

59:52
Does anyone have a link to the recording of Daniel’s talk from January 9th?

01:00:22
Thank you Mathieu

01:00:23
https://us02web.zoom.us/rec/play/LM4MOfsMsPly-6ObW3iMWiuAIBv9VfXPW10xO1sYQOi6jQHH62ie2oG3_wFGp0bMAF40B60An8-o4qhs.pJbo3ECAOAylzDht?continueMode=true&_x_zm_rtaid=cukn9LNKTEaY2slcGfXf8w.1673535685856.559fd03f01e2b81cb0fdd43ef2b2f617&_x_zm_rhtaid=14

01:00:31
Join the ToIP All Members Meeting in one hour where the HXWG will be discussing their white paper. Read about it in this BLOG - https://trustoverip.org/blog/2023/01/17/why-the-digital-identity-juggernaut-needs-safety-belts/

01:01:05
Michael, perhaps “storage synchronization protocol” would fit for DWN?

01:01:06
Yes, please do come to the All-Member Meeting

01:01:41
Here's my diagram

01:01:42
https://hyperonomy.com/2023/01/18/web-7-0-didcomm-arm-vs-tbd-web5-dwp-stack/

01:01:42
+1 to complementary efforts in ToIP, DIF, KERI, HL, etc. working together more closely.

01:01:56
👏

01:02:23
If you prefer video than reading the Technology Architecture, this is one of the talks I gave: https://youtu.be/PpIiYoe96qk

01:02:39
Perhaps, "storage centric" is the key ...your terminology supports that. Definitely Layer 1

01:04:46
Here's the narrative: https://youtu.be/1XnPWmpkGro?t=630s

01:05:19
If the Trust Spanning Protocol is a conduit from bottom and top layers, doesn't it make sense to map out those needs?

01:05:32
Keep being awesome folks

01:05:38
thanks everyone

01:05:44
thanks