[{"author": "Filip Skokan", "text": "

good afternoon

", "time": "2022-11-09T13:01:23Z"}, {"author": "Robin Wilton", "text": "

Good point from the mic line.

", "time": "2022-11-09T13:14:35Z"}, {"author": "Aaron Parecki", "text": "

\"relying parties gonna rely\" :joy:

", "time": "2022-11-09T13:14:38Z"}, {"author": "Robin Wilton", "text": "

;^)

", "time": "2022-11-09T13:14:45Z"}, {"author": "Aaron Parecki", "text": "

don't know if you heard the room Robin but there was a very audible chuckle

", "time": "2022-11-09T13:15:02Z"}, {"author": "Robin Wilton", "text": "

I didn't - good to know ;^D

", "time": "2022-11-09T13:15:14Z"}, {"author": "Robin Wilton", "text": "

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 ;^)

", "time": "2022-11-09T13:15:52Z"}, {"author": "Robin Wilton", "text": "

Which is not to say we shouldn't explore the issue.

", "time": "2022-11-09T13:16:07Z"}, {"author": "Aaron Parecki", "text": "

+1, especially in an interoperable way. I'm sure people are already doing some variation of this independently

", "time": "2022-11-09T13:16:20Z"}, {"author": "Robin Wilton", "text": "

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...

", "time": "2022-11-09T13:17:37Z"}, {"author": "Robin Wilton", "text": "

But syntactic interop of combined claims is a worthy objective.

", "time": "2022-11-09T13:18:24Z"}, {"author": "George Fletcher", "text": "

+1 for this being really important work

", "time": "2022-11-09T13:48:42Z"}, {"author": "George Fletcher", "text": "

UX Design Patterns make sense to me

", "time": "2022-11-09T13:50:03Z"}, {"author": "Robin Wilton", "text": "

+1; it makes sense not 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 does depend on (i.e. third parties and user agents).

", "time": "2022-11-09T13:52:04Z"}, {"author": "Robin Wilton", "text": "

.

", "time": "2022-11-09T13:52:08Z"}, {"author": "Robin Wilton", "text": "

Was Justing perhaps thinking of SOUPS?

", "time": "2022-11-09T13:52:27Z"}, {"author": "Robin Wilton", "text": "

*Justin

", "time": "2022-11-09T13:52:31Z"}, {"author": "Kristina Yasuda", "text": "

Agrees with John

", "time": "2022-11-09T13:54:49Z"}, {"author": "Robin Wilton", "text": "

+1 John; a layer of abstraction between the presented client_ID and the corresponding database index is a crucial design point.

", "time": "2022-11-09T14:25:58Z"}, {"author": "Robin Wilton", "text": "

Thanks everyone - good session

", "time": "2022-11-09T14:34:03Z"}]