Re: Agentic Linked Data -- attempt 2

Extending on your use cases, agents could also be personal assistants (access to the individual calendar, diary, phone?) / personal trainers (access to the exercise routine, step counter, calorie counters, grocery shopping?). I could see these coming with different levels of “sophistication” for a membership (even a “business/personal” agent that sits on top of your entire personal and business diary, just like a human PA does today).

IMHO it would be useful to separate the terminology of “personal health” (heart rate history, sports routines) from “medical history” (drug prescriptions). 

My first project (in the very early 90’s) was a multiyear research project for a health information system (HIMS), one of the first requirements from the doctors was that “all medical history should be immutable and traceable”, similar to the black box of a plane.

Agents accessing fine-grained unencrypted medical history should be probably amongst the narrowest and in a "special category of interest”.

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

> On 30 Dec 2024, at 11:04, Matt Taylor <matt@mattj-taylor.co.uk> wrote:
> 
> I’m new to the group (Hi!) and I agree that the use cases need to be crisp and governance strong.
> I’d like to throw my tuppence in 😊.
>  
> Restricting unwanted use of personal data is a goal and not opening it up through an Agentic framework must be a priority.
> Keeping a robust and secure platform and then having a [managed] agentic service layer on top (as a separate product) is my suggestion.
> I can only think of 3 use cases where agentic access to data would be optimal : Personal security (agentic panic button??), Personal health (prescribed drug / health info where a person is incapacitated) and data access after bereavement.
> All 3 should (and will) be heavily regulated.
>  
> I’d love to be included in the discussion / any investigative group that spins off from this thread.
>  
> Matt
> Consultant in ethical use of technology and data.
>  
>  
> From: Sindhu Raju <sindhu2@me.com <mailto:sindhu2@me.com>> 
> Sent: 30 December 2024 10:27
> To: Joshua Cornejo <josh@marketdata.md <mailto:josh@marketdata.md>>
> Cc: public-solid <public-solid@w3.org <mailto:public-solid@w3.org>>; Melvin Carvalho <melvincarvalho@gmail.com <mailto:melvincarvalho@gmail.com>>; Eric Jahn <eric@alexandriaconsulting.com <mailto:eric@alexandriaconsulting.com>>; Aad Versteden <aad.versteden@gmail.com <mailto:aad.versteden@gmail.com>>
> Subject: Re: Agentic Linked Data -- attempt 2
>  
> Hello,
>  
> I would also be interested in this discussion. I am working on a project in regards to personal data management. 
>  
> I think it would be helpful to delineate where AI agents may be helpful and or a hinderance via consumer use cases.
>  
> Thanks,
> Sindhu Raju
>  
>  
>  
> 
> 
> On Dec 30, 2024, at 12:05 AM, Joshua Cornejo <josh@marketdata.md <mailto:josh@marketdata.md>> wrote:
>  
> Interesting coincidence that someone posted this on LinkedIn and appeared on my timeline.
>  
> I like the quote “Agents should be skeptical of assertions that they read on the Semantic Web until they have checked the sources of information.”.
>  
> Maybe the vision is that authorisation (can the agent read the data) coexists with validation (is the data legitimate).
>  
> <preview.png>
> Scientific American_ Feature Article_ The Semantic Web_ May 2001 <https://www-sop.inria.fr/acacia/cours/essi2006/Scientific%20American_%20Feature%20Article_%20The%20Semantic%20Web_%20May%202001.pdf>
> PDF Document · 158 KB <https://www-sop.inria.fr/acacia/cours/essi2006/Scientific%20American_%20Feature%20Article_%20The%20Semantic%20Web_%20May%202001.pdf>
>  
> _________________________
> Joshua Cornejo
> marketdata <https://www.marketdata.md/>
> smart authorisation management for the AI-era
> 
> 
> On 29 Dec 2024, at 22:04, Aad Versteden <aad.versteden@gmail.com <mailto:aad.versteden@gmail.com>> wrote:
>  
> Hi all,
> 
> 
> An exciting and necessary extension indeed.
> 
> I would also like to follow this too, perhaps from a short distance
> assuming time doesn't permit.  Agentic Linked Data fits closely to how
> we use Linked Data within semantic.works [1][2] so we can share what
> we've learned over time.  Microservices act as Agents manipulating data
> in semantic.works and we manage to share many microservices across
> applications.  Everything we do is based on SPARQL so some differences
> with Solid do exist.  We integrate Artificial Intelligence [3] in the
> same way as microservices which handle login, registration or sending
> out emails[4].
> 
> When we squint our eyes we shouldn't notice too much of a difference in
> an Agent being a if-this-then-that construct, a Deep Neural Network, an
> OWL reasoner, an LLM, or a human.  This should be a natural and
> hopefully straightforward extension to Solid.
> 
> A FOAF Agent based approach would also lend itself to support backend
> processes on Solid Pods.  We found this to be one of the bigger
> technical challenges to apply Solid Pods more in our business setting
> and it was one of the key technical challenges for Solid Shop[5].
> 
> All in all, this may become a minor guideline or extension opening up
> many possibilities.
> 
> 
> Exciting work ahead,
> 
> Aad
> 
> 
> [1] https://github.com/mu-semtech
> [2] https://semantic.works/
> [3] https://github.com/semantic-ai/translation-nl-en-service
> [4] https://github.com/lblod/berichtencentrum-deliver-email-service
> [5] https://github.com/redpencilio/app-solid-shop
> 
> --
> 
> Aad Versteden
> Technical Futurist
> CEO
> 
> Proudly building the #WebWeWant at redpencil.io <http://redpencil.io/>
> 
> GitHub: @madnificent
> Mastodon: @madnificent@mastodon.social
> Mail: aad.versteden@redpencil.io <mailto:aad.versteden@redpencil.io>
> Web: https://redpencil.io <https://redpencil.io/>
> Tel: +32476513848