Good day folks, thanks for the US folks that took their morning for the 3-day holiday weekend
", "time": "2023-02-20T16:00:45Z"}, {"author": "Hannes Tschofenig", "text": "Audio failed. Restarting
", "time": "2023-02-20T16:01:44Z"}, {"author": "Henk Birkholz", "text": "Sry, l8t, hotel wifi
", "time": "2023-02-20T16:05:32Z"}, {"author": "Steve Lasker", "text": "+1
\nIt's a great forcing function.
+1 Neal. That's exactly what SCITT does. Dick's use is valid but is an application ON TOP OF SCITT
", "time": "2023-02-20T16:19:33Z"}, {"author": "Steve Lasker", "text": "+1
\nSCITT is a means to gate/store and serve content that leads to decisions based on content from verifiable identities. Different consumers may choose different entities they choose to trust, based on their target environment.
Some how my Mute button is not working
", "time": "2023-02-20T16:20:46Z"}, {"author": "Yogesh Deshpande", "text": "I am back again
", "time": "2023-02-20T16:21:43Z"}, {"author": "Yogesh Deshpande", "text": "and seem to work now!
", "time": "2023-02-20T16:21:50Z"}, {"author": "Jon Geater", "text": "\"Common facts, uncommon conclusions.\" - Trustworthiness depends on the risk that the consumer is exposed to and will be different from cater to caller. Our present task is to create the fundamental building blocks for exchanging/storing/retrieving those facts, attributed to known parties, with certain longevity and anti-forgery properties.
", "time": "2023-02-20T16:22:07Z"}, {"author": "Jon Geater", "text": "We must avoid trying to bite off more than that or we'll never make progress
", "time": "2023-02-20T16:22:36Z"}, {"author": "Steve Lasker", "text": "+1 I beleive we're building secure, verifiable pipes of information. SBOMs, VEX, statements today. Some new type of documents will source tomorrow. Can you trust the content of the document, based don't the relationship of the identifier.
", "time": "2023-02-20T16:23:35Z"}, {"author": "Cedric Fournet", "text": "The \"basic relying party policy\" should be of the form \"I want a recent statement about X from A registered in SCITT ledger B. Others may issue statements about X, and other SCITT ledgers may or may not register them, which matters in more advanced scenarios but the basic policy should be good useful enough for many relying parties.
", "time": "2023-02-20T16:37:52Z"}, {"author": "Raymond Lutz", "text": "@Bob Martin, I like your suggestion and I hope you can write it up a bit more so I can study it.
", "time": "2023-02-20T16:40:29Z"}, {"author": "Raymond Lutz", "text": "Yes, @Jon Geater, I agree with the simple model that can't necessarily make a final \"trustable\" conclusion.
", "time": "2023-02-20T16:42:04Z"}, {"author": "Raymond Lutz", "text": "That is, the conclusion can be based on the evidence in the registry, but it will take an evaluation layer to do it.
", "time": "2023-02-20T16:42:41Z"}, {"author": "Neal McBurnett", "text": "Very nice, Jon: self-driving cars with AI have \"lots of moving parts\"
", "time": "2023-02-20T16:43:12Z"}, {"author": "Cedric Fournet", "text": "Dick, I believe the generic trust statement would be of the form \"Registry R recorded that A said that X is trustworthy\". The statement must mention both R and A, and simple relying parties should used statically-configured values for R and for A. \"X is trustworthy\" is too hard to decide on its own.
", "time": "2023-02-20T16:55:34Z"}, {"author": "Raymond Lutz", "text": "The issue of visibility of an internal registry and how it can eventually placed in public-facing registry is an important capability that I am not sure we have addressed sufficiently in the user case.
", "time": "2023-02-20T16:56:52Z"}, {"author": "Raymond Lutz", "text": "-- use case.
", "time": "2023-02-20T16:57:11Z"}]