
Nobody writes a new browser for every website. So why does every AI agent need a custom integration for every application? From Still 2.0, a short film by AtomGraph.

The application is data.

Nobody writes a new browser for every website. So why does every AI agent need a custom integration for every application? From Still 2.0, a short film by AtomGraph.

Just adopt #rdf already 🥱
Meet the Neo4j Ontology Graph Specification, an open-source way to represent domain knowledge in a machine-readable form, so data, applications, and AI systems can work together and automate more. It builds on years of experience with ontologies: a clear, accessible format for describing entities, relationships, properties, and business meaning. What you get: consistency in knowledge graph development, simpler integration, and knowledge that’s easier to understand and use. Learn more from Jesus and Oskar: bit.ly/4fy0XvZ

Hackers are now using LLMs to continuously scan software updates, spot newly fixed bugs, and build attacks before teams can apply the fix — all without human involvement. That’s according to the latest report from the Google Threat Intelligence Group. We're helping defenders counter automated threats with Google AI Threat Defense, which combines Gemini and other frontier models to find and fix flaws before attackers can exploit them.

Listing the details of everything for sale everywhere is meant to make Amazon more useful than Reddit for people and AI agents. theverge.com/tech/1033697/am…

AI has made human carelessness easier to exploit without making computer users any wiser. Companies and governments must act decisively against these threats economist.com/leaders/2026/1…

Applications ship their own stylesheets as packages. They are compiled together with the platform's, so an application's templates run in the browser as well. atomgraph.com/blog/linkeddat…

In many web apps, the interface is built twice: server templates for the first page, front-end components for the browser. LinkedDataHub 6 renders both with the same XSLT 3.0 stylesheets, Saxon on the server and SaxonJS in the browser. There is no separate front end.

Interest in #ontology #semantic #knowledge graphs over time. From lnkd.in/p/e5Bd_fKy

📦 Software Spotlight: LinkedDataHub Describe what you want to do with linked data in everyday language. Its AI assistant turns your request into a plan you can review and choose to run. openknowledgegraphs.com/soft…

“The Semantic Web had the right vision and the wrong tools. Thirty years later, the tools have caught up.” infoworld.com/article/422915…

The full film, 3½ minutes: youtu.be/SbvNIRS9jyg The argument behind it: firstprinciplesoftheweb.org/


Wikipedia is the largest encyclopedia ever written by humans—and it is likely to hold that title for ever. (Any future rival is sure to be made with the help of AI) bit.ly/4iO1Sum Illustration: Carl Godfrey

The assistant doesn't generate code. It produces a plan of data operations, executed with the user's access rights. The resulting chart becomes a block on the page, and the conversation is saved in the document too. linkeddatahub.com/

In LinkedDataHub 6, the assistant is available on any page. Ask in plain language. Read-only requests run immediately. Here, it finds the five customers who ordered the most and presents them as text and a chart. Changes to data wait until Execute is pressed.

"The data from the ontology itself, is stored as a knowledge graph, persisted to QuipuDB, our homegrown RDF graph database [...] Data here is generated by parsing raw telemetry, logs, and incident discussions into triples (subject-predicate-object facts)." netflixtechblog.com/ontology…