- From: Andrei Ciortea <andrei.ciortea@inria.fr>
- Date: Mon, 7 Jul 2025 20:58:05 +0200
- To: Joshua Cornejo <josh@marketdata.md>
- Cc: public-webagents <public-webagents@w3.org>
- Message-Id: <C69A5226-69FA-4BFF-BEA7-623CB146CD01@inria.fr>
Hi Joshua, Certainly an interesting point — and seems relevant for the interoperability report as well. We should move this to a Github issue. We can also add this scenario (and events more broadly) on the agenda of one of our regular meetings. It would be interesting to dive deeper. Best, Andrei -- Andrei Ciortea Assistant Professor School of Computer Science University of St.Gallen, Switzerland https://interactions.ics.unisg.ch/ External Collaborator Wimmics Inria, Université Côte d’Azur, CNRS, I3S, France https://wimmics.inria.fr/ > On 27 Jun 2025, at 17:37, Joshua Cornejo <josh@marketdata.md> wrote: > > Hi guys, > > Maybe relevant or an area where someone is doing some research. > > A couple of weeks ago in my work around rights management I came across the need for events in a particular way, for example: “You have permission to run when <event>”. As I started working on a scaffolding, I’ve realised there is a lot of work around the complexities of events, above the description in RFC5545, amongst others: > > Public events and only authorised agents can ‘somehow’ create … > Private events > Malleable/Fungible (“modifiable”) events > > Any pointers or anyone interested – much appreciated. > ___________________________________ > Joshua Cornejo > marketdata <https://www.marketdata.md/> > smart authorisation management for the AI-era
Received on Monday, 7 July 2025 18:58:22 UTC