- From: Sebastian Samaruga <ssamarug@gmail.com>
- Date: Fri, 10 Oct 2025 22:38:37 -0300
- To: Kingsley Idehen <kidehen@openlinksw.com>
- Cc: public-lod <public-lod@w3.org>, W3C Semantic Web IG <semantic-web@w3.org>, ontolog-forum <ontolog-forum@googlegroups.com>, W3C AIKR CG <public-aikr@w3.org>
- Message-ID: <CAOLUXBueqvuf+V_-Mn7VYPbT_AWabjBBWTcC35bt5Ba4Zqb2jw@mail.gmail.com>
Another App for LLMs, REST (and RDF, why not?). Semantic Hypermedia Addressing: Given Hypermedia Resources Content Types (REST): .. Text .. Images .. Audio .. Video .. Tabular .. Hierarchical .. Graph (Am I missing something?) Imagine the possibility of not only annotate resources of those types with metadata and links (in the appropriate axes and occurrences context) but having those annotations and links being generated by inference and activation being that metadata and links in turn meaningful annotated with their meaning given its occurrence context in any given axis or relationship role (dimension). RESTful principles could apply rendering annotations and links as resources also, with their annotations and links, making them discoverable and browsable / query-able. Naming conventions for standard addressable resources could make browsing and returning results (for a query or prompt, for example) a machine-understandable task. Also, the task of constructing resources hyperlinked or embedding other resources in a content context (a report or dashboard, for example) or the frontend for a given resource driven (REST) resource contexts interactions will be a matter of discovery of the right resources and link resources. Given the appropriate resources, link resources and addressing, encoding a prompt / query for a link, in a given context (maybe embedded within the prompt / query) would be a matter of resource interaction, being the capabilities of what can be prompted / queried for available to the client for further exploration. Generated resources, in their corresponding Content Types, should also address and be further addressable in and by other resources, enabling incremental knowledge composition by means of preserving generated assets in a resources interaction contexts history. Examples: "Given this book, make an index with all the occurrences of this character and also provide links to the moments of those occurrences in the book's picture. Tell me which actor represented that character role". Best regards, Sebastián. On Wed, Oct 8, 2025, 8:35 PM Sebastian Samaruga <ssamarug@gmail.com> wrote: > A "generic client" sounds for me as a "generic client" for any kind of > database. It lacks what is meant for an application ("killer" or not) like > its domain's use cases and its behaviors and flows rendered meaningfully in > an user interface (or API). Browsers allowed us to do that, not without > significant effort, by declaratively stating the "meaning" and "behaviors" > of components rendered on each "applications" pages (flows). > > IMHO, what we need is a framework that, for any integrated / linked source > of (semantic) data, renders for us useful applications, translating what is > expressed in simple statements source data into a "representation" which > allows to interact with that underlying data in a contextualized use-case > driven fashion. All this by only "feeding" the "browser" with the data and > schemes to be aligned inferring the rest by aggregation, alignment and > activation means of these source data / schemes. > > All this leveraging Semantic inference, heuristics (FCA: Formal Concept > Analysis), Domain Driven Development, DCI (Data, Contexts and Interactions) > design patterns and, of course, GenAI / LLMs. > > Sorry for the self-ad, but this is what I've been working on for a long > time: > https://sebxama.blogspot.com/2025/10/semantic-web-genai-enabled-eai.html > > Regards, > Sebastián. > > > On Mon, Sep 29, 2025, 1:52 PM Kingsley Idehen <kidehen@openlinksw..com> > wrote: > >> Hi Everyone, >> >> It’s been a while! >> >> Something important is happening right now, thanks to the emergence of >> LLMs as the long-awaited generic RDF client (the so-called “killer app”). >> We all know how Mosaic → Mozilla/Netscape made HTML and HTTP globally >> usable by end-users and developers alike. Well, the very same thing is >> finally happening with RDF—albeit some 20+ years later than expected. >> >> Here’s a post I recently published on LinkedIn about this critical >> development: >> >> >> https://www.linkedin.com/pulse/large-language-models-llms-powerful-generic-rdf-clients-idehen-xwhfe >> >> -- >> Regards, >> >> Kingsley Idehen >> Founder & CEO >> OpenLink Software >> Home Page: http://www.openlinksw.com >> Community Support: https://community.openlinksw.com >> >> Social Media: >> LinkedIn: http://www.linkedin.com/in/kidehen >> Twitter : https://twitter.com/kidehen >> >>
Received on Saturday, 11 October 2025 01:39:32 UTC