[{"author": "Filip Skokan", "text": "<p>good afternoon</p>", "time": "2022-11-09T13:01:23Z"}, {"author": "Robin Wilton", "text": "<p>Good point from the mic line.</p>", "time": "2022-11-09T13:14:35Z"}, {"author": "Aaron Parecki", "text": "<p>\"relying parties gonna rely\" <span aria-label=\"joy\" class=\"emoji emoji-1f602\" role=\"img\" title=\"joy\">:joy:</span></p>", "time": "2022-11-09T13:14:38Z"}, {"author": "Robin Wilton", "text": "<p>;^)</p>", "time": "2022-11-09T13:14:45Z"}, {"author": "Aaron Parecki", "text": "<p>don't know if you heard the room Robin but there was a very audible chuckle</p>", "time": "2022-11-09T13:15:02Z"}, {"author": "Robin Wilton", "text": "<p>I didn't - good to know ;^D</p>", "time": "2022-11-09T13:15:14Z"}, {"author": "Robin Wilton", "text": "<p>FWIW I don't think we have a good handle on the technicalities of transitive trust, for claims like this; the idea that we will quickly get a handle on the technicalities of combinatiorial trust is... optimistic ;^)</p>", "time": "2022-11-09T13:15:52Z"}, {"author": "Robin Wilton", "text": "<p>Which is not to say we shouldn't explore the issue.</p>", "time": "2022-11-09T13:16:07Z"}, {"author": "Aaron Parecki", "text": "<p>+1, especially in an interoperable way. I'm sure people are already doing some variation of this independently</p>", "time": "2022-11-09T13:16:20Z"}, {"author": "Robin Wilton", "text": "<p>Right - if you can't control what combinations people construct, interoperability is quickly reduced to \"do the signatures verify?\". Semantic interop is probably a pipe dream...</p>", "time": "2022-11-09T13:17:37Z"}, {"author": "Robin Wilton", "text": "<p><em>But</em> syntactic interop of combined claims is a worthy objective.</p>", "time": "2022-11-09T13:18:24Z"}, {"author": "George Fletcher", "text": "<p>+1 for this being really important work</p>", "time": "2022-11-09T13:48:42Z"}, {"author": "George Fletcher", "text": "<p>UX Design Patterns make sense to me</p>", "time": "2022-11-09T13:50:03Z"}, {"author": "Robin Wilton", "text": "<p>+1; it makes sense <em>not</em> to design this so that trustworthiness depends on user actions - but in doing so, you have to have an assurance framework  for the entities it <em>does</em> depend on (i.e. third parties and user agents).</p>", "time": "2022-11-09T13:52:04Z"}, {"author": "Robin Wilton", "text": "<p>.</p>", "time": "2022-11-09T13:52:08Z"}, {"author": "Robin Wilton", "text": "<p>Was Justing perhaps thinking of SOUPS?</p>", "time": "2022-11-09T13:52:27Z"}, {"author": "Robin Wilton", "text": "<p>*Justin</p>", "time": "2022-11-09T13:52:31Z"}, {"author": "Kristina Yasuda", "text": "<p>Agrees with John</p>", "time": "2022-11-09T13:54:49Z"}, {"author": "Robin Wilton", "text": "<p>+1 John; a layer of abstraction between the presented client_ID and the corresponding database index is a crucial design point.</p>", "time": "2022-11-09T14:25:58Z"}, {"author": "Robin Wilton", "text": "<p>Thanks everyone  -  good session</p>", "time": "2022-11-09T14:34:03Z"}]