Re: Agentic Linked Data -- attempt 2

Hi Melvin,

I would be interested.

A lot of the work I’ve done in the authorisation architecture with ODRL has been driven by both “agents” (as potential delegates) and embedding security (e.g. different pieces of information generate the same embedding, and now you need to segregate/obfuscate for the linked paths).

A piece of advice is to define what "Agent " means, in OIDC user accounts are assigned to humans and machine accounts (service accounts) are assigned to machines, following slightly different protocols. 

From what I see in the examples of “agents” have mixed both with a machine used for connection to a service provider (API keys = service accounts) whilst the “personas” within the implementation of an agent try to emulate humans. I haven’t done much thinking about it - but “smells” wrong.

Regards,
_________________________
Joshua Cornejo
marketdata <https://www.marketdata.md/>
smart authorisation management for the AI-era

> On 28 Dec 2024, at 11:11, Melvin Carvalho <melvincarvalho@gmail.com> wrote:
> 
> Hi All,
> 
> When I started this group, it was with the idea that Solid = Social Linked Data. Solid's foundation on WebID ties it to the concept of "Agent," based on FOAF's Agent class (parent of FOAF Person).
> 
> With "agentic AI" really taking off right now, I wonder—would anyone be interested in exploring "Agentic Linked Data"? It feels like a natural direction.
> 
> Best,
> 
> Melvin
>