Only second? What happened? 😅

Ah maar Kenneth is de max! Jaloers!

Last but not least, Gertjan De Mulder shows how to query Verifiable Credentials via SPARQL in OID4VP flows. RDF graphs enable selective, privacy-preserving presentations.
🔗 ceur-ws.org/Vol-4085/pap...
#ISWC2025

Wout Slabbinck and Beatriz Esteves present LOAMA — a low-code ODRL tool for access management. Visual policy editing for non-technical users & semantic integration.
🔗 ceur-ws.org/Vol-4085/pap...
#ISWC2025

Ieben Smessaert and Julián Rojas will demo SPARQL time functions — treating partial & floating dates as intervals for better temporal queries. Implemented in Comunica.
🔗 smessie.github.io/Article-ISWC...
#ISWC2025

Julián Rojas presents our #Trustflows model: combining CQRS + Event Sourcing with Linked Data to decouple reads/writes and add trust contexts. Validated in the PACSOI health use case.
🔗 ceur-ws.org/Vol-4085/pap...
#ISWC2025

Julián Rojas, Arthur Vercruysse and Ieben Smessaert lead the RDF-Connect tutorial — building provenance-aware, multilingual streaming pipelines. Let’s create a weather KG for Nara 🇯🇵!
🔗 rdf-connect.github.io/Tutorial-ISW...
#ISWC2025

Jonni Hanski and Ruben Taelman explore automated client-side federation for Wikidata after its graph split. Shows when automation can replace manual SERVICE clauses.

🔗 www.rubensworks.net/raw/publicat...
#ISWC2025

Ruben Taelman also leads a tutorial on RDF & SPARQL 1.2 — a hands-on intro to the first spec update in a decade! Covers motivations, RDF-star, triple-terms & reification.
🔗 www.w3.org/Talks/2025/i...
#ISWC2025

Ruben Eschauzier and Ruben Taelman present “Revisiting Link Prioritization…”:evaluating link prioritization in #Solid environments. Defines the R3 metric, tests in Comunica, finds no gain over FIFO.
🔗 rubeneschauzier.github.io/r3-metric-da...
#ISWC2025

The NextTrain Pebble app provides a countdown to your train you intended to catch in Belgium and the NL. UX-wise it is fabulous. I maintain the API behind it that has been online since 2010 and still is. So much looking fwd to using NextTrain again!

I don’t think both ways of seeing named graphs are in conflict: you either choose what you do in your store, but I also see ways in which they can co-exist in 1 store if that’s what you want to do.

They are still named, just with local identifiers that cannot conflict with any other external source

Thanks for recommending it! Happy to open the discussion on blank node graphs, I brought my arguments in favor ;)

In the attached image, I’m using named graphs on the one hand as a contextual assertion, but also to bundle triples together as an RDF Message. For the latter, I believe we should have another syntactic feature (cfr. NDJSON or Jelly frames).

Wikidata, Wikimedia Commons, OpenStreetMap, UniProt, PubChem, DBLP, public transit schedules, our world in data, Europeana, data.europa.eu (the meta dataset), national statistics, ...