@prefix rdf: . @base . @prefix : . @prefix owl: . @prefix prov: . @prefix rdfs: . @prefix schema: . @prefix xsd: . a schema:Dataset ; rdfs:label "Northwind showcase graph"@en ; schema:name "Northwind showcase graph"@en . a schema:WebPage ; rdfs:label "The firm that keeps what it learns — HTML collection"@en ; schema:about :analysis ; schema:associatedMedia <> ; schema:description "The reader-facing representation of the associated RDF-Turtle collection."@en ; schema:name "The firm that keeps what it learns — HTML collection"@en . <> a schema:CreativeWork ; rdfs:label "Databricks and OpenLink — RDF-Turtle collection"@en ; schema:about :analysis ; schema:accountablePerson ; schema:associatedMedia ; schema:author ; schema:dateCreated "2026-10-27T16:55:47+00:00"^^xsd:dateTime ; schema:dateModified "2026-10-27T16:55:47+00:00"^^xsd:dateTime ; schema:description "A source-grounded collection separating article claims, documented capabilities, and proposed architectural synthesis."@en ; schema:name "Databricks and OpenLink — RDF-Turtle collection"@en ; prov:wasGeneratedBy :generation . a schema:Organization ; rdfs:label "a16z news"@en ; schema:description "Publisher of the source article; the article describes a16z’s investment relationship with Databricks."@en ; schema:name "a16z news"@en . :benchmark a schema:Claim ; rdfs:label "A bounded vendor benchmark"@en ; schema:author ; schema:citation ; schema:description "Databricks reports 84.5% first-attempt correctness for Genie on 28 enterprise data-analysis questions, versus 52.4% for its strongest anonymized general-purpose coding-agent comparison. This is an internal June 2026 result—not a Virtuoso comparison or a universal accuracy rate."@en ; schema:genre "Evidence qualification"@en ; schema:isPartOf :evidence-boundaries ; schema:name "A bounded vendor benchmark"@en ; schema:position 1 ; schema:text "Databricks reports 84.5% first-attempt correctness for Genie on 28 enterprise data-analysis questions, versus 52.4% for its strongest anonymized general-purpose coding-agent comparison. This is an internal June 2026 result—not a Virtuoso comparison or a universal accuracy rate."@en . :capability-proposal a schema:Claim ; rdfs:label "Follow the data-access path"@en ; schema:alternateName "Follow the data-access path"@en ; schema:author ; schema:citation , , , ; schema:description "The existing showcases expose concrete queries over Databricks, PostgreSQL, SQL Server, and native Virtuoso data. Follow the query text and linked records to inspect the data-access path, then use task-specific cases to evaluate the agent workflow built around it."@en ; schema:genre "Evidence qualification"@en ; schema:isPartOf :evidence-boundaries ; schema:name "Follow the data-access path"@en ; schema:position 3 ; schema:text "The existing showcases expose concrete queries over Databricks, PostgreSQL, SQL Server, and native Virtuoso data. Follow the query text and linked records to inspect the data-access path, then use task-specific cases to evaluate the agent workflow built around it."@en . :case-context a schema:Claim ; rdfs:label "Retrieve the relevant contract"@en ; schema:author ; schema:citation , , , ; schema:description "For a request to explain an invoice exception, classify the intent and retrieve the governing definition, source-priority rule, approved procedure, and relevant prior cases. Select context by its task relationship rather than loading the entire memory corpus."@en ; schema:genre "Illustrative workflow"@en ; schema:isPartOf :memory-in-use ; schema:name "Retrieve the relevant contract"@en ; schema:position 1 ; schema:text "For a request to explain an invoice exception, classify the intent and retrieve the governing definition, source-priority rule, approved procedure, and relevant prior cases. Select context by its task relationship rather than loading the entire memory corpus."@en . :case-evidence a schema:Claim ; rdfs:label "Query evidence under the caller’s rights"@en ; schema:author ; schema:citation , , , ; schema:description "OPAL can invoke declared SQL or SPARQL Protocol and RDF Query Language (SPARQL) tools over permitted data. Virtuoso can join an attached invoice view with stored customer and policy descriptions. The memory rule guides the request; source and runtime authorization govern the query."@en ; schema:genre "Illustrative workflow"@en ; schema:isPartOf :memory-in-use ; schema:name "Query evidence under the caller’s rights"@en ; schema:position 2 ; schema:text "OPAL can invoke declared SQL or SPARQL Protocol and RDF Query Language (SPARQL) tools over permitted data. Virtuoso can join an attached invoice view with stored customer and policy descriptions. The memory rule guides the request; source and runtime authorization govern the query."@en . :case-learning a schema:Claim ; rdfs:label "Retain the correction and its scope"@en ; schema:author ; schema:citation , , , ; schema:description "Record the cited facts, policy version, proposed action, reviewer correction, and observed outcome with named identifiers. A later agent can retrieve the applicable lesson. Retention, access, and review policies determine what belongs in shared memory."@en ; schema:genre "Illustrative workflow"@en ; schema:isPartOf :memory-in-use ; schema:name "Retain the correction and its scope"@en ; schema:position 4 ; schema:text "Record the cited facts, policy version, proposed action, reviewer correction, and observed outcome with named identifiers. A later agent can retrieve the applicable lesson. Retention, access, and review policies determine what belongs in shared memory."@en . :case-review a schema:Claim ; rdfs:label "Separate a proposal from an authorized action"@en ; schema:author ; schema:citation , , , ; schema:description "Return the evidence and proposed resolution to the responsible person when the workflow requires approval. An agent’s remembered preference does not authorize a credit note, payment, or change to the financial record."@en ; schema:genre "Illustrative workflow"@en ; schema:isPartOf :memory-in-use ; schema:name "Separate a proposal from an authorized action"@en ; schema:position 3 ; schema:text "Return the evidence and proposed resolution to the responsible person when the workflow requires approval. An agent’s remembered preference does not authorize a credit note, payment, or change to the financial record."@en . :competitive-overlap a schema:Claim ; rdfs:label "The competitive overlap"@en ; schema:author ; schema:citation , , ; schema:description "Both routes address natural-language work over enterprise context. Evaluate the assembled experience: semantic coverage, permitted actions, retained evidence, evaluation quality, and the effort required to maintain them. A feature inventory alone cannot decide which fits."@en ; schema:genre "Architectural synthesis"@en ; schema:isPartOf :coopetitive-mesh ; schema:name "The competitive overlap"@en ; schema:position 1 ; schema:text "Both routes address natural-language work over enterprise context. Evaluate the assembled experience: semantic coverage, permitted actions, retained evidence, evaluation quality, and the effort required to maintain them. A feature inventory alone cannot decide which fits."@en . :complementary-route a schema:Claim ; rdfs:label "The complementary route"@en ; schema:author ; schema:citation , , , , , ; schema:description "Keep suitable workloads in Databricks. The existing bakehouse showcase demonstrates relational attachment and an RDF View in Virtuoso. OPAL can use declared query tools over this semantic layer; add the organization’s memory, action policies, and evaluation cases around that data-access path."@en ; schema:genre "Architectural synthesis"@en ; schema:isPartOf :coopetitive-mesh ; schema:name "The complementary route"@en ; schema:position 2 ; schema:text "Keep suitable workloads in Databricks. The existing bakehouse showcase demonstrates relational attachment and an RDF View in Virtuoso. OPAL can use declared query tools over this semantic layer; add the organization’s memory, action policies, and evaluation cases around that data-access path."@en . :connected-state a schema:Claim ; rdfs:label "Access existing operational state"@en ; schema:about ; schema:author ; schema:citation , ; schema:description "UDA supplies standards-based drivers and bridges. Virtuoso can attach reachable relational tables and query them alongside local data; a warehouse migration is not a prerequisite for every semantic use case."@en ; schema:genre "Documented capability and synthesis"@en ; schema:isPartOf :openlink-architecture ; schema:name "Access existing operational state"@en ; schema:position 1 ; schema:text "UDA supplies standards-based drivers and bridges. Virtuoso can attach reachable relational tables and query them alongside local data; a warehouse migration is not a prerequisite for every semantic use case."@en . :coordination-economics a schema:Claim ; rdfs:label "Lower coordination costs can change firm boundaries"@en ; schema:author , ; schema:citation ; schema:description "Drawing on Ronald Coase and Herbert Simon, the article argues that shared records can reduce coordination costs inside and outside a firm. The result need not be uniformly larger or smaller companies; a wider range of organizations can become feasible."@en ; schema:genre "Article argument"@en ; schema:isPartOf :source-thesis ; schema:name "Lower coordination costs can change firm boundaries"@en ; schema:position 5 ; schema:text "Drawing on Ronald Coase and Herbert Simon, the article argues that shared records can reduce coordination costs inside and outside a firm. The result need not be uniformly larger or smaller companies; a wider range of organizations can become feasible."@en . :evolution-agents a schema:Claim ; rdfs:label "Agents — turn shared context into work"@en ; schema:author , ; schema:citation ; schema:description "Genie and Agent Bricks sit above the data foundation. The article’s System of Record for Agents adds meaning, authority, and evaluation to shared state."@en ; schema:genre "Article argument"@en ; schema:isPartOf :from-spark-to-agents ; schema:name "Agents — turn shared context into work"@en ; schema:position 4 ; schema:text "Genie and Agent Bricks sit above the data foundation. The article’s System of Record for Agents adds meaning, authority, and evaluation to shared state."@en . :evolution-lakebase a schema:Claim ; rdfs:label "Lakebase — operational databases for agent work"@en ; schema:author , ; schema:citation ; schema:description "The article connects the Neon acquisition and Lakebase with separating compute from storage and making isolated database branches practical for experimentation."@en ; schema:genre "Article argument"@en ; schema:isPartOf :from-spark-to-agents ; schema:name "Lakebase — operational databases for agent work"@en ; schema:position 3 ; schema:text "The article connects the Neon acquisition and Lakebase with separating compute from storage and making isolated database branches practical for experimentation."@en . :evolution-lakehouse a schema:Claim ; rdfs:label "Lakehouse — a shared analytical foundation"@en ; schema:author , ; schema:citation ; schema:description "Table layers over lake files bring reliability, schema management, and version history to storage used by analytical and machine-learning workloads."@en ; schema:genre "Article argument"@en ; schema:isPartOf :from-spark-to-agents ; schema:name "Lakehouse — a shared analytical foundation"@en ; schema:position 2 ; schema:text "Table layers over lake files bring reliability, schema management, and version history to storage used by analytical and machine-learning workloads."@en . :evolution-spark a schema:Claim ; rdfs:label "Spark — iterative computation"@en ; schema:author , ; schema:citation ; schema:description "The source starts with Spark’s reuse of data in memory between computational rounds, addressing the disk-heavy iteration pattern of early Hadoop workloads."@en ; schema:genre "Article argument"@en ; schema:isPartOf :from-spark-to-agents ; schema:name "Spark — iterative computation"@en ; schema:position 1 ; schema:text "The source starts with Spark’s reuse of data in memory between computational rounds, addressing the disk-heavy iteration pattern of early Hadoop workloads."@en . :harness a schema:Claim ; rdfs:label "Use OPAL as the agent harness"@en ; schema:about ; schema:author ; schema:citation , ; schema:description "The OPAL module gives Virtuoso a natural-language agent interface and tool integration. It supports Model Context Protocol (MCP), Agent-to-Agent (A2A), and OpenAPI interfaces, while models and data spaces remain loosely coupled."@en ; schema:genre "Documented capability and synthesis"@en ; schema:isPartOf :openlink-architecture ; schema:name "Use OPAL as the agent harness"@en ; schema:position 3 ; schema:text "The OPAL module gives Virtuoso a natural-language agent interface and tool integration. It supports Model Context Protocol (MCP), Agent-to-Agent (A2A), and OpenAPI interfaces, while models and data spaces remain loosely coupled."@en . :institutional-context a schema:Claim ; rdfs:label "Read the investment context"@en ; schema:author , ; schema:citation ; schema:description "This is a favorable thesis written from an investor’s perspective: the article describes a16z’s financing relationship with Databricks. Company growth figures, autonomy forecasts, and organizational effects remain attributed claims."@en ; schema:genre "Article argument"@en ; schema:isPartOf :source-thesis ; schema:name "Read the investment context"@en ; schema:position 4 ; schema:text "This is a favorable thesis written from an investor’s perspective: the article describes a16z’s financing relationship with Databricks. Company growth figures, autonomy forecasts, and organizational effects remain attributed claims."@en . :judgment a schema:Claim ; rdfs:label "Execution becomes cheaper; judgment still matters"@en ; schema:author , ; schema:citation ; schema:description "The authors expect more workers to specify outcomes, delegate execution, and judge results. Their account retains human attention for people development, ethical judgment, and unfamiliar situations."@en ; schema:genre "Article argument"@en ; schema:isPartOf :source-thesis ; schema:name "Execution becomes cheaper; judgment still matters"@en ; schema:position 2 ; schema:text "The authors expect more workers to specify outcomes, delegate execution, and judge results. Their account retains human attention for people development, ethical judgment, and unfamiliar situations."@en . :market-claims a schema:Claim ; rdfs:label "Market figures are article claims"@en ; schema:author ; schema:citation ; schema:description "The article uses revenue run rates, agent activity volumes, and company valuation to illustrate commercial momentum. The runnable showcases let readers examine the architectural data-access capabilities directly."@en ; schema:genre "Evidence qualification"@en ; schema:isPartOf :evidence-boundaries ; schema:name "Market figures are article claims"@en ; schema:position 2 ; schema:text "The article uses revenue run rates, agent activity volumes, and company valuation to illustrate commercial momentum. The runnable showcases let readers examine the architectural data-access capabilities directly."@en . :non-equivalence a schema:Claim ; rdfs:label "Keep the useful differences visible"@en ; schema:author ; schema:citation , , , ; schema:description "Genie’s authority-ranked context is not automatically equivalent to RDF and Web Ontology Language (OWL) entailment. Named graphs are not database branches. Portability of context is not automatic portability of executable workflows. These distinctions keep the integration design testable."@en ; schema:genre "Architectural synthesis"@en ; schema:isPartOf :coopetitive-mesh ; schema:name "Keep the useful differences visible"@en ; schema:position 4 ; schema:text "Genie’s authority-ranked context is not automatically equivalent to RDF and Web Ontology Language (OWL) entailment. Named graphs are not database branches. Portability of context is not automatic portability of executable workflows. These distinctions keep the integration design testable."@en . :operational-memory a schema:Claim ; rdfs:label "Bind the agent to retrievable memory"@en ; schema:about ; schema:author ; schema:citation ; schema:description "Configure a Virtuoso instance as the store for agent-rdf-memory and bind the agent through AGENTS.md. Intent selection retrieves the relevant preferences, how-tos, and session context. Files remain an explicit fallback when endpoint retrieval is unavailable or incomplete."@en ; schema:genre "Documented capability and synthesis"@en ; schema:isPartOf :openlink-architecture ; schema:name "Bind the agent to retrievable memory"@en ; schema:position 4 ; schema:text "Configure a Virtuoso instance as the store for agent-rdf-memory and bind the agent through AGENTS.md. Intent selection retrieves the relevant preferences, how-tos, and session context. Files remain an explicit fallback when endpoint retrieval is unavailable or incomplete."@en . :policy-boundary a schema:Claim ; rdfs:label "Preserve the policy boundary"@en ; schema:author ; schema:citation , , ; schema:description "Database credentials and source permissions must govern the attached data. Review which columns and relationships mappings expose, and enforce the resulting graph/service permissions in Virtuoso. A permission rule in memory must not be mistaken for an enforcement point."@en ; schema:genre "Architectural synthesis"@en ; schema:isPartOf :coopetitive-mesh ; schema:name "Preserve the policy boundary"@en ; schema:position 3 ; schema:text "Database credentials and source permissions must govern the attached data. Review which columns and relationships mappings expose, and enforce the resulting graph/service permissions in Virtuoso. A permission rule in memory must not be mistaken for an enforcement point."@en . :position-coexistence-databricks a schema:Claim ; rdfs:label "Databricks — Where can they cooperate?"@en ; schema:about ; schema:author ; schema:category :dimension-coexistence ; schema:citation , , ; schema:description "Databricks SQL exposes an authenticated Java Database Connectivity (JDBC) connection that a compatible client can use."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-coexistence ; schema:name "Databricks — Where can they cooperate?"@en ; schema:text "Databricks SQL exposes an authenticated Java Database Connectivity (JDBC) connection that a compatible client can use."@en . :position-coexistence-virtuoso a schema:Claim ; rdfs:label "Virtuoso with modules + UDA — Where can they cooperate?"@en ; schema:about ; schema:author ; schema:category :dimension-coexistence ; schema:citation , , , , ; schema:description "The live showcase attaches Databricks bakehouse tables, exposes an RDF View, and provides SQL, SPARQL inside SQL (SPASQL), and SPARQL examples over the same business data. UDA drivers and bridges supply applicable connectivity paths across the wider portfolio."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-coexistence ; schema:name "Virtuoso with modules + UDA — Where can they cooperate?"@en ; schema:text "The live showcase attaches Databricks bakehouse tables, exposes an RDF View, and provides SQL, SPARQL inside SQL (SPASQL), and SPARQL examples over the same business data. UDA drivers and bridges supply applicable connectivity paths across the wider portfolio."@en . :position-evaluation-databricks a schema:Claim ; rdfs:label "Databricks — Did it work?"@en ; schema:about ; schema:author ; schema:category :dimension-evaluation ; schema:citation , , , ; schema:description "The article describes task-specific exams, feedback, and Agent Bricks optimization. Databricks’ reported Genie benchmark has a bounded internal test suite."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-evaluation ; schema:name "Databricks — Did it work?"@en ; schema:text "The article describes task-specific exams, feedback, and Agent Bricks optimization. Databricks’ reported Genie benchmark has a bounded internal test suite."@en . :position-evaluation-virtuoso a schema:Claim ; rdfs:label "Virtuoso with modules + UDA — Did it work?"@en ; schema:about ; schema:author ; schema:category :dimension-evaluation ; schema:citation , , , ; schema:description "OPAL sessions and RDF provenance can preserve actions, evidence, outcomes, and corrections. A task-specific evaluation process must be designed; storage alone supplies no accuracy guarantee."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-evaluation ; schema:name "Virtuoso with modules + UDA — Did it work?"@en ; schema:text "OPAL sessions and RDF provenance can preserve actions, evidence, outcomes, and corrections. A task-specific evaluation process must be designed; storage alone supplies no accuracy guarantee."@en . :position-interface-databricks a schema:Claim ; rdfs:label "Databricks — How do people act?"@en ; schema:about ; schema:author ; schema:category :dimension-interface ; schema:citation , , , ; schema:description "Genie offers natural-language access, shareable agents, external knowledge connectors, and Model Context Protocol (MCP) integration; developers can build more customized agents through Agent Bricks."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-interface ; schema:name "Databricks — How do people act?"@en ; schema:text "Genie offers natural-language access, shareable agents, external knowledge connectors, and Model Context Protocol (MCP) integration; developers can build more customized agents through Agent Bricks."@en . :position-interface-virtuoso a schema:Claim ; rdfs:label "Virtuoso with modules + UDA — How do people act?"@en ; schema:about ; schema:author ; schema:category :dimension-interface ; schema:citation , , , ; schema:description "Virtuoso with OPAL provides natural-language interaction with data spaces and declared tools. Agent memory retrieves relevant context rather than requiring every rule in each prompt."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-interface ; schema:name "Virtuoso with modules + UDA — How do people act?"@en ; schema:text "Virtuoso with OPAL provides natural-language interaction with data spaces and declared tools. Agent memory retrieves relevant context rather than requiring every rule in each prompt."@en . :position-isolation-databricks a schema:Claim ; rdfs:label "Databricks — How is experimentation isolated?"@en ; schema:about ; schema:author ; schema:category :dimension-isolation ; schema:citation , ; schema:description "Lakebase documents database branches that isolate development and test changes."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-isolation ; schema:name "Databricks — How is experimentation isolated?"@en ; schema:text "Lakebase documents database branches that isolate development and test changes."@en . :position-isolation-virtuoso a schema:Claim ; rdfs:label "Virtuoso with modules + UDA — How is experimentation isolated?"@en ; schema:about ; schema:author ; schema:category :dimension-isolation ; schema:citation , ; schema:description "RDF named graphs partition semantic content; they are not a claim of Lakebase-style database branching. Use configured transactions, copies, or separate environments for isolated writes."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-isolation ; schema:name "Virtuoso with modules + UDA — How is experimentation isolated?"@en ; schema:text "RDF named graphs partition semantic content; they are not a claim of Lakebase-style database branching. Use configured transactions, copies, or separate environments for isolated writes."@en . :position-meaning-databricks a schema:Claim ; rdfs:label "Databricks — What does it mean?"@en ; schema:about ; schema:author ; schema:category :dimension-meaning ; schema:citation , , ; schema:description "Genie Ontology combines curated semantics with inferred snippets and authority scoring; it respects source permissions. The inspected documentation labels it Public Preview."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-meaning ; schema:name "Databricks — What does it mean?"@en ; schema:text "Genie Ontology combines curated semantics with inferred snippets and authority scoring; it respects source permissions. The inspected documentation labels it Public Preview."@en . :position-meaning-virtuoso a schema:Claim ; rdfs:label "Virtuoso with modules + UDA — What does it mean?"@en ; schema:about ; schema:author ; schema:category :dimension-meaning ; schema:citation , , ; schema:description "Virtuoso uses explicit RDF identities, ontologies, Linked Data Views, and configured inference. agent-rdf-memory makes selected operational definitions and rules queryable."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-meaning ; schema:name "Virtuoso with modules + UDA — What does it mean?"@en ; schema:text "Virtuoso uses explicit RDF identities, ontologies, Linked Data Views, and configured inference. agent-rdf-memory makes selected operational definitions and rules queryable."@en . :position-permission-databricks a schema:Claim ; rdfs:label "Databricks — What is allowed?"@en ; schema:about ; schema:author ; schema:category :dimension-permission ; schema:citation , , ; schema:description "Unity Gateway centralizes AI service governance, including access and cost controls. Unity Catalog permissions constrain the context available to Genie."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-permission ; schema:name "Databricks — What is allowed?"@en ; schema:text "Unity Gateway centralizes AI service governance, including access and cost controls. Unity Catalog permissions constrain the context available to Genie."@en . :position-permission-virtuoso a schema:Claim ; rdfs:label "Virtuoso with modules + UDA — What is allowed?"@en ; schema:about ; schema:author ; schema:category :dimension-permission ; schema:citation , , ; schema:description "Configured Virtuoso Authentication Layer (VAL) policies and data-source permissions enforce access. OPAL calls operate within those rights; memory instructions describe intended behavior."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-permission ; schema:name "Virtuoso with modules + UDA — What is allowed?"@en ; schema:text "Configured Virtuoso Authentication Layer (VAL) policies and data-source permissions enforce access. OPAL calls operate within those rights; memory instructions describe intended behavior."@en . :position-portability-databricks a schema:Claim ; rdfs:label "Databricks — What survives a model change?"@en ; schema:about ; schema:author ; schema:category :dimension-portability ; schema:citation , , , ; schema:description "The article argues that firm-owned definitions, permissions, and evaluated experience should survive model replacement; open foundations support this ambition."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-portability ; schema:name "Databricks — What survives a model change?"@en ; schema:text "The article argues that firm-owned definitions, permissions, and evaluated experience should survive model replacement; open foundations support this ambition."@en . :position-portability-virtuoso a schema:Claim ; rdfs:label "Virtuoso with modules + UDA — What survives a model change?"@en ; schema:about ; schema:author ; schema:category :dimension-portability ; schema:citation , , , ; schema:description "RDF memory, explicit identifiers, declarative queries, and standard interfaces can preserve context across agents and models. An exported graph still needs a compatible runtime and access policies."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-portability ; schema:name "Virtuoso with modules + UDA — What survives a model change?"@en ; schema:text "RDF memory, explicit identifiers, declarative queries, and standard interfaces can preserve context across agents and models. An exported graph still needs a compatible runtime and access policies."@en . :position-state-databricks a schema:Claim ; rdfs:label "Databricks — What is true?"@en ; schema:about ; schema:author ; schema:category :dimension-state ; schema:citation , , , ; schema:description "Lakehouse and Lakebase are the article’s foundation for analytical and transactional state. Lakebase adds branch-based development and testing."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-state ; schema:name "Databricks — What is true?"@en ; schema:text "Lakehouse and Lakebase are the article’s foundation for analytical and transactional state. Lakebase adds branch-based development and testing."@en . :position-state-virtuoso a schema:Claim ; rdfs:label "Virtuoso with modules + UDA — What is true?"@en ; schema:about ; schema:author ; schema:category :dimension-state ; schema:citation , , , ; schema:description "Virtuoso combines local Structured Query Language (SQL) and Resource Description Framework (RDF) data with attached relational sources. UDA supplies applicable drivers and bridges; source systems can retain their operational role."@en ; schema:genre "Analytical mapping"@en ; schema:isPartOf :dimension-state ; schema:name "Virtuoso with modules + UDA — What is true?"@en ; schema:text "Virtuoso combines local Structured Query Language (SQL) and Resource Description Framework (RDF) data with attached relational sources. UDA supplies applicable drivers and bridges; source systems can retain their operational role."@en . :query-claims a schema:SoftwareSourceCode ; rdfs:label "Query 1 — Trace claims to their sources"@en ; schema:codeSampleType "Query recipe"@en ; schema:description "A SPARQL recipe for exploring this collection’s claims and relationships."@en ; schema:isPartOf :analysis ; schema:name "Query 1 — Trace claims to their sources"@en ; schema:position 1 ; schema:potentialAction :run-claims ; schema:programmingLanguage "SPARQL"@en ; schema:target ; schema:text """PREFIX rdf: PREFIX schema: SELECT ?claimIri ?claim ?status ?sourceIri WHERE { GRAPH { ?claimIri rdf:type schema:Claim ; schema:name ?claim ; schema:genre ?status ; schema:citation ?sourceIri . } } ORDER BY ?status ?claim"""@en . :query-comparison a schema:SoftwareSourceCode ; rdfs:label "Query 2 — Compare the four questions and other dimensions"@en ; schema:codeSampleType "Query recipe"@en ; schema:description "A SPARQL recipe for exploring this collection’s claims and relationships."@en ; schema:isPartOf :analysis ; schema:name "Query 2 — Compare the four questions and other dimensions"@en ; schema:position 2 ; schema:potentialAction :run-comparison ; schema:programmingLanguage "SPARQL"@en ; schema:target ; schema:text """PREFIX schema: SELECT ?dimensionIri ?dimension ?offeringIri ?offering ?position WHERE { GRAPH { schema:hasPart ?dimensionIri . ?dimensionIri schema:name ?dimension ; schema:position ?order . ?cell schema:category ?dimensionIri ; schema:about ?offeringIri ; schema:text ?position . ?offeringIri schema:name ?offering . } } ORDER BY ?order ?offering"""@en . :query-modules a schema:SoftwareSourceCode ; rdfs:label "Query 3 — Inspect the Virtuoso module relationship"@en ; schema:codeSampleType "Query recipe"@en ; schema:description "A SPARQL recipe for exploring this collection’s claims and relationships."@en ; schema:isPartOf :analysis ; schema:name "Query 3 — Inspect the Virtuoso module relationship"@en ; schema:position 3 ; schema:potentialAction :run-modules ; schema:programmingLanguage "SPARQL"@en ; schema:target ; schema:text """PREFIX schema: SELECT ?moduleIri ?module ?description WHERE { GRAPH { schema:hasPart ?moduleIri . ?moduleIri schema:name ?module ; schema:description ?description . } } ORDER BY ?module"""@en . :query-workflow a schema:SoftwareSourceCode ; rdfs:label "Query 4 — Read the proposed workflow in order"@en ; schema:codeSampleType "Query recipe"@en ; schema:description "A SPARQL recipe for exploring this collection’s claims and relationships."@en ; schema:isPartOf :analysis ; schema:name "Query 4 — Read the proposed workflow in order"@en ; schema:position 4 ; schema:potentialAction :run-workflow ; schema:programmingLanguage "SPARQL"@en ; schema:target ; schema:text """PREFIX schema: SELECT ?stepIri ?order ?step ?instruction WHERE { GRAPH { schema:step ?stepIri . ?stepIri schema:position ?order ; schema:name ?step ; schema:text ?instruction . } } ORDER BY ?order"""@en . :run-claims a schema:SearchAction ; rdfs:label "Run Query 1 — Trace claims to their sources"@en ; schema:name "Run Query 1 — Trace claims to their sources"@en ; schema:target . :run-comparison a schema:SearchAction ; rdfs:label "Run Query 2 — Compare the four questions and other dimensions"@en ; schema:name "Run Query 2 — Compare the four questions and other dimensions"@en ; schema:target . :run-modules a schema:SearchAction ; rdfs:label "Run Query 3 — Inspect the Virtuoso module relationship"@en ; schema:name "Run Query 3 — Inspect the Virtuoso module relationship"@en ; schema:target . :run-workflow a schema:SearchAction ; rdfs:label "Run Query 4 — Read the proposed workflow in order"@en ; schema:name "Run Query 4 — Read the proposed workflow in order"@en ; schema:target . :shared-meaning a schema:Claim ; rdfs:label "Give records shared names and meaning"@en ; schema:about ; schema:author ; schema:citation , ; schema:description "Virtuoso’s Linked Data Views give rows hyperlinks that work as cross-platform super-keys. Generated source ontologies can be aligned with shared vocabularies, enabling a semantic layer across any Open Database Connectivity (ODBC)- or JDBC-accessible database management system (DBMS)."@en ; schema:genre "Documented capability and synthesis"@en ; schema:isPartOf :openlink-architecture ; schema:name "Give records shared names and meaning"@en ; schema:position 2 ; schema:text "Virtuoso’s Linked Data Views give rows hyperlinks that work as cross-platform super-keys. Generated source ontologies can be aligned with shared vocabularies, enabling a semantic layer across any Open Database Connectivity (ODBC)- or JDBC-accessible database management system (DBMS)."@en . :shared-record a schema:Claim ; rdfs:label "Shared state can support distributed action"@en ; schema:author , ; schema:citation ; schema:description "A common record can let people and agents coordinate without sending every question through a hierarchy. The article distinguishes changing information flow from eliminating the human org chart."@en ; schema:genre "Article argument"@en ; schema:isPartOf :source-thesis ; schema:name "Shared state can support distributed action"@en ; schema:position 1 ; schema:text "A common record can let people and agents coordinate without sending every question through a hierarchy. The article distinguishes changing information flow from eliminating the human org chart."@en . :showcase-databricks a schema:Claim ; rdfs:label "Databricks: three interfaces, one business question"@en ; schema:about ; schema:author ; schema:citation , ; schema:description "Analyze revenue by city over the attached bakehouse tables. SQL joins the source tables, SPASQL wraps a query over their RDF View, and SPARQL follows transaction-to-franchise links. These examples make the cooperative data-access path concrete."@en ; schema:genre "Existing live showcase"@en ; schema:isPartOf :live-showcases ; schema:name "Databricks: three interfaces, one business question"@en ; schema:position 1 ; schema:potentialAction :open-db-sparql-revenue-by-city, :open-db-spasql-revenue-by-city, :open-db-sql-revenue-by-city ; schema:subjectOf :showcase-db-sparql-revenue-by-city, :showcase-db-spasql-revenue-by-city, :showcase-db-sql-revenue-by-city ; schema:text "Analyze revenue by city over the attached bakehouse tables. SQL joins the source tables, SPASQL wraps a query over their RDF View, and SPARQL follows transaction-to-franchise links. These examples make the cooperative data-access path concrete."@en . :showcase-federation a schema:Claim ; rdfs:label "SQL federation and graph analytics"@en ; schema:about ; schema:author ; schema:citation , ; schema:description "Join SQL Server customers, MySQL orders, and native Virtuoso products through one SQL statement. The Northwind graph example shows the complementary route: aggregate sales by following links among order lines, products, and categories."@en ; schema:genre "Existing live showcase"@en ; schema:isPartOf :live-showcases ; schema:name "SQL federation and graph analytics"@en ; schema:position 4 ; schema:potentialAction :open-nw-sparql-category-sales, :open-ss-sql-federated-join ; schema:subjectOf :showcase-nw-sparql-category-sales, :showcase-ss-sql-federated-join ; schema:text "Join SQL Server customers, MySQL orders, and native Virtuoso products through one SQL statement. The Northwind graph example shows the complementary route: aggregate sales by following links among order lines, products, and categories."@en . :showcase-ontology a schema:Claim ; rdfs:label "One vocabulary across different sources"@en ; schema:about ; schema:author ; schema:citation ; schema:description "Ask for people using the shared Friend of a Friend (FOAF) vocabulary. The query follows generated classes to foaf:Person and returns employees from CSV files and native Virtuoso SQL tables in one result."@en ; schema:genre "Existing live showcase"@en ; schema:isPartOf :live-showcases ; schema:name "One vocabulary across different sources"@en ; schema:position 3 ; schema:potentialAction :open-onto-cross-source-people ; schema:subjectOf :showcase-onto-cross-source-people ; schema:text "Ask for people using the shared Friend of a Friend (FOAF) vocabulary. The query follows generated classes to foaf:Person and returns employees from CSV files and native Virtuoso SQL tables in one result."@en . :showcase-postgres a schema:Claim ; rdfs:label "PostgreSQL: from records to entities"@en ; schema:about ; schema:author ; schema:citation , ; schema:description "Read PostgreSQL clients through SQL, then inspect the generated entity types through SPASQL or SPARQL. Record hyperlinks and ontology terms let the same operational data participate in a wider semantic layer."@en ; schema:genre "Existing live showcase"@en ; schema:isPartOf :live-showcases ; schema:name "PostgreSQL: from records to entities"@en ; schema:position 2 ; schema:potentialAction :open-pg-sparql-entity-types, :open-pg-spasql-entity-types, :open-pg-sql-clients ; schema:subjectOf :showcase-pg-sparql-entity-types, :showcase-pg-spasql-entity-types, :showcase-pg-sql-clients ; schema:text "Read PostgreSQL clients through SQL, then inspect the generated entity types through SPASQL or SPARQL. Record hyperlinks and ontology terms let the same operational data participate in a wider semantic layer."@en . :sovereignty a schema:Claim ; rdfs:label "Learning should survive the next model"@en ; schema:author , ; schema:citation ; schema:description "The article’s strongest portability test is whether a replacement model can inherit the firm’s definitions, permissions, evaluated cases, and exceptions. The proposed moat is a learning loop that improves decisions."@en ; schema:genre "Article argument"@en ; schema:isPartOf :source-thesis ; schema:name "Learning should survive the next model"@en ; schema:position 3 ; schema:text "The article’s strongest portability test is whether a replacement model can inherit the firm’s definitions, permissions, evaluated cases, and exceptions. The proposed moat is a learning loop that improves decisions."@en . :sovereignty-test a schema:Claim ; rdfs:label "Test sovereignty by replacement"@en ; schema:author ; schema:citation , ; schema:description "Export the definitions, context, cases, and evidence, then repeat a bounded task with a replacement model. Check whether source authority, access decisions, and evaluated outcomes remain intelligible. The result measures the assembled system rather than a portability slogan."@en ; schema:genre "Evidence qualification"@en ; schema:isPartOf :evidence-boundaries ; schema:name "Test sovereignty by replacement"@en ; schema:position 4 ; schema:text "Export the definitions, context, cases, and evidence, then repeat a bounded task with a replacement model. Check whether source authority, access decisions, and evaluated outcomes remain intelligible. The result measures the assembled system rather than a portability slogan."@en . :this-collection a schema:Claim ; rdfs:label "Retain a runnable procedure"@en ; schema:about ; schema:author ; schema:citation ; schema:description "Retain the selected query, its target graph or data source, the governing business definition, and the evaluation case in memory. A later agent can retrieve that procedure and repeat it with the same tools while applying the caller’s current access rights."@en ; schema:genre "Workflow design"@en ; schema:isPartOf :memory-in-use ; schema:name "Retain a runnable procedure"@en ; schema:position 5 ; schema:text "Retain the selected query, its target graph or data source, the governing business definition, and the evaluation case in memory. A later agent can retrieve that procedure and repeat it with the same tools while applying the caller’s current access rights."@en . a schema:SoftwareApplication ; rdfs:label "Genie One"@en ; schema:alternateName "Genie"@en ; schema:citation ; schema:description "Databricks’ business-user interface within the Genie family of natural-language data and agent experiences; mapped functionally to the OPAL harness."@en ; schema:isPartOf ; schema:name "Genie One"@en ; schema:url . a schema:Dataset ; rdfs:label "Databricks showcase graph"@en ; schema:name "Databricks showcase graph"@en . a schema:Dataset ; rdfs:label "Postgres showcase graph"@en ; schema:name "Postgres showcase graph"@en . a schema:SoftwareApplication ; rdfs:label "rdf-infographic-skill"@en ; schema:name "rdf-infographic-skill"@en ; prov:actedOnBehalfOf . a schema:SoftwareApplication ; rdfs:label "OpenLink AI Layer (OPAL)"@en ; schema:applicationCategory "Virtuoso module"@en ; schema:citation ; schema:description "AI harness module installed into Virtuoso via a Virtuoso Application Distribution (VAD) package; loosely couples models, tools, agents, and data spaces."@en ; schema:isPartOf ; schema:name "OpenLink AI Layer (OPAL)"@en . a schema:SoftwareApplication ; rdfs:label "Universal Data Access (UDA)"@en ; schema:citation ; schema:description "OpenLink’s connectivity portfolio; complements Virtuoso by providing drivers and bridges to reachable data sources."@en ; schema:name "Universal Data Access (UDA)"@en ; schema:provider . :answer-1 a schema:Answer ; rdfs:label "Answer: What is the central coopetitive thesis?"@en ; schema:author ; schema:citation , , ; schema:isPartOf :question-1 ; schema:name "Answer: What is the central coopetitive thesis?"@en ; schema:text "Databricks and OpenLink compete over the working context of enterprise agents. They can also cooperate: Databricks can retain suitable data workloads while Virtuoso adds cross-source semantics, OPAL supplies the agent harness, and agent-rdf-memory carries retrievable operational context."@en . :answer-10 a schema:Answer ; rdfs:label "Answer: How does agent-rdf-memory make a query workflow repeatable?"@en ; schema:author ; schema:citation , , ; schema:isPartOf :question-10 ; schema:name "Answer: How does agent-rdf-memory make a query workflow repeatable?"@en ; schema:text "It preserves the relevant business definition, selected query, source identifiers, operating procedure, and evaluated corrections. Intent-based retrieval supplies that context to a later agent, while the query service applies the caller’s current permissions."@en . :answer-11 a schema:Answer ; rdfs:label "Answer: What should survive a model change?"@en ; schema:author ; schema:citation , , ; schema:isPartOf :question-11 ; schema:name "Answer: What should survive a model change?"@en ; schema:text "The firm should retain definitions, source authority, permissions, evaluated cases, relevant corrections, and evidence. A new model still needs a compatible harness and authorized tools; an export of context does not by itself reproduce every application behavior."@en . :answer-12 a schema:Answer ; rdfs:label "Answer: What would establish that the integration works?"@en ; schema:author ; schema:citation , , ; schema:isPartOf :question-12 ; schema:name "Answer: What would establish that the integration works?"@en ; schema:text "Connect the chosen sources, verify identity and permissions on the actual execution path, run representative tasks, inspect citations and actions, and repeat after replacing the model. Record the outcomes rather than inferring success from component documentation."@en . :answer-2 a schema:Answer ; rdfs:label "Answer: Is OPAL the same thing as Genie?"@en ; schema:author ; schema:citation , , , ; schema:isPartOf :question-2 ; schema:name "Answer: Is OPAL the same thing as Genie?"@en ; schema:text "OPAL and Genie overlap in natural-language agent interaction, but this is a functional mapping, not product identity. OPAL is a Virtuoso AI harness module that loosely couples models and data spaces; Genie is Databricks’ family of data-aware AI experiences."@en . :answer-3 a schema:Answer ; rdfs:label "Answer: Are OPAL and agent-rdf-memory separate platforms beside Virtuoso?"@en ; schema:author ; schema:citation , , , ; schema:isPartOf :question-3 ; schema:name "Answer: Are OPAL and agent-rdf-memory separate platforms beside Virtuoso?"@en ; schema:text "In this portfolio model, both are Virtuoso modules. OPAL is installed as a VAD package. agent-rdf-memory uses a configured Virtuoso instance as its store, with AGENTS.md as the operational binding for the agent."@en . :answer-4 a schema:Answer ; rdfs:label "Answer: What does UDA contribute?"@en ; schema:author ; schema:citation , , , , ; schema:isPartOf :question-4 ; schema:name "Answer: What does UDA contribute?"@en ; schema:text "Universal Data Access supplies drivers and bridges that connect applications and servers to supported database interfaces. It complements Virtuoso’s attachment and Linked Data Views; the appropriate connectivity path depends on the source, driver, and deployment."@en . :answer-5 a schema:Answer ; rdfs:label "Answer: Must all enterprise data move into one database?"@en ; schema:author ; schema:citation , , , ; schema:isPartOf :question-5 ; schema:name "Answer: Must all enterprise data move into one database?"@en ; schema:text "The proposed OpenLink route can query attached relational sources alongside stored RDF, allowing source systems to retain their role. Data access still requires configured connections, source permissions, and a considered mapping of the exposed columns and relationships."@en . :answer-6 a schema:Answer ; rdfs:label "Answer: Does an RDF memory rule enforce access permissions?"@en ; schema:author ; schema:citation , , , ; schema:isPartOf :question-6 ; schema:name "Answer: Does an RDF memory rule enforce access permissions?"@en ; schema:text "No. A remembered instruction can guide the agent, but authorization must be enforced by the data source, configured Virtuoso/VAL policies, and the tool or application runtime. The collection keeps behavioral memory distinct from enforcement."@en . :answer-7 a schema:Answer ; rdfs:label "Answer: Is Genie Ontology equivalent to RDF reasoning?"@en ; schema:author ; schema:citation , , , , ; schema:isPartOf :question-7 ; schema:name "Answer: Is Genie Ontology equivalent to RDF reasoning?"@en ; schema:text "The documentation describes a context layer with curated semantics, inferred snippets, authority scoring, and source permissions. That does not establish equivalence with RDF/OWL entailment or with the operational-memory contract used here."@en . :answer-8 a schema:Answer ; rdfs:label "Answer: Does the benchmark prove that one portfolio is better?"@en ; schema:author ; schema:citation , , , ; schema:isPartOf :question-8 ; schema:name "Answer: Does the benchmark prove that one portfolio is better?"@en ; schema:text "No. Databricks’ reported result is an internal, bounded comparison with anonymized coding agents. It does not compare with Virtuoso, OPAL, or agent-rdf-memory. A meaningful choice needs task-specific evaluation of the assembled system."@en . :answer-9 a schema:Answer ; rdfs:label "Answer: Can a named graph replace a Lakebase branch?"@en ; schema:author ; schema:citation , , , , ; schema:isPartOf :question-9 ; schema:name "Answer: Can a named graph replace a Lakebase branch?"@en ; schema:text "No. A named graph identifies and partitions RDF content. Lakebase database branches address isolated development and test state. Use an appropriate transaction or environment strategy when an agent needs isolated writes."@en . :curationAgent a prov:SoftwareAgent ; rdfs:label "GPT-6 in Codex"@en ; schema:description "AI agent that produced this collection using the operator’s RDF memory protocol."@en ; schema:name "GPT-6 in Codex"@en ; prov:actedOnBehalfOf . :generation a prov:Activity ; rdfs:label "Collection generation"@en ; schema:description "RDF-first, script-assisted curation from the inspected article, official product documentation, and public agent-rdf-memory specifications."@en ; schema:name "Collection generation"@en ; prov:used , , , , , , , , , , , , , , , , , ; prov:wasAssociatedWith , , :curationAgent . :open-db-sparql-revenue-by-city a schema:ViewAction ; rdfs:label "Open Revenue by city"@en ; schema:name "Open Revenue by city"@en ; schema:target . :open-db-spasql-revenue-by-city a schema:ViewAction ; rdfs:label "Open Revenue by city, SPARQL inside SQL"@en ; schema:name "Open Revenue by city, SPARQL inside SQL"@en ; schema:target . :open-db-sql-revenue-by-city a schema:ViewAction ; rdfs:label "Open Revenue by city, in SQL"@en ; schema:name "Open Revenue by city, in SQL"@en ; schema:target . :open-nw-sparql-category-sales a schema:ViewAction ; rdfs:label "Open Sales by category"@en ; schema:name "Open Sales by category"@en ; schema:target . :open-onto-cross-source-people a schema:ViewAction ; rdfs:label "Open One shared class, two different sources"@en ; schema:name "Open One shared class, two different sources"@en ; schema:target . :open-pg-sparql-entity-types a schema:ViewAction ; rdfs:label "Open Entity types in the PostgreSQL view"@en ; schema:name "Open Entity types in the PostgreSQL view"@en ; schema:target . :open-pg-spasql-entity-types a schema:ViewAction ; rdfs:label "Open Entity types, SPARQL inside SQL"@en ; schema:name "Open Entity types, SPARQL inside SQL"@en ; schema:target . :open-pg-sql-clients a schema:ViewAction ; rdfs:label "Open PostgreSQL clients, queried in place"@en ; schema:name "Open PostgreSQL clients, queried in place"@en ; schema:target . :open-ss-sql-federated-join a schema:ViewAction ; rdfs:label "Open Federated join: SQL Server + MySQL + Virtuoso"@en ; schema:name "Open Federated join: SQL Server + MySQL + Virtuoso"@en ; schema:target . :showcase-db-sparql-revenue-by-city a schema:SoftwareSourceCode ; rdfs:label "Revenue by city"@en ; schema:about ; schema:citation , ; schema:codeSampleType "Live showcase query"@en ; schema:description "The post's query, scoped to the RDF View's graph on demo.openlinksw.com. Transactions reach their city by following the franchise link, not a foreign-key column."@en ; schema:isPartOf :analysis ; schema:name "Revenue by city"@en ; schema:position 103 ; schema:potentialAction :open-db-sparql-revenue-by-city ; schema:programmingLanguage "SPARQL"@en ; schema:target ; schema:text """PREFIX : SELECT ?city (COUNT(DISTINCT ?transaction) AS ?orders) (SUM(?totalPrice) AS ?revenue) FROM WHERE { ?transaction a :Transaction ; :franchise ?franchise ; :totalPrice ?totalPrice . ?franchise :city ?city . } GROUP BY ?city ORDER BY DESC(?revenue) LIMIT 10"""@en . :showcase-db-spasql-revenue-by-city a schema:SoftwareSourceCode ; rdfs:label "Revenue by city, SPARQL inside SQL"@en ; schema:about ; schema:citation , ; schema:codeSampleType "Live showcase query"@en ; schema:conditionsOfAccess "Open the example in Virtuoso Data Spaces, then use the signed-in Query Builder."@en ; schema:description "The Databricks RDF View, aggregated in SPARQL and handed back to SQL as rows."@en ; schema:isPartOf :analysis ; schema:name "Revenue by city, SPARQL inside SQL"@en ; schema:position 102 ; schema:potentialAction :open-db-spasql-revenue-by-city ; schema:programmingLanguage "SPASQL"@en ; schema:target ; schema:text """SELECT city, orders, revenue FROM ( SPARQL PREFIX : SELECT ?city (COUNT(DISTINCT ?transaction) AS ?orders) (SUM(?totalPrice) AS ?revenue) FROM WHERE { ?transaction a :Transaction ; :franchise ?franchise ; :totalPrice ?totalPrice . ?franchise :city ?city . } GROUP BY ?city ORDER BY DESC(?revenue) LIMIT 10 ) AS x"""@en . :showcase-db-sql-revenue-by-city a schema:SoftwareSourceCode ; rdfs:label "Revenue by city, in SQL"@en ; schema:citation , ; schema:codeSampleType "Live showcase query"@en ; schema:conditionsOfAccess "Open the example in Virtuoso Data Spaces, then use the signed-in Query Builder."@en ; schema:description "A join and an aggregate over two attached Databricks tables. The SPARQL card \"Revenue by city\" below returns the same numbers through the RDF View."@en ; schema:isPartOf :analysis ; schema:name "Revenue by city, in SQL"@en ; schema:position 101 ; schema:potentialAction :open-db-sql-revenue-by-city ; schema:programmingLanguage "SQL"@en ; schema:target ; schema:text """SELECT TOP 10 f.city, COUNT(*) AS orders, SUM(t.totalPrice) AS revenue FROM databricks.bakehouse.sales_transactions t JOIN databricks.bakehouse.sales_franchises f ON t.franchiseID = f.franchiseID GROUP BY f.city ORDER BY 3 DESC"""@en . :showcase-nw-sparql-category-sales a schema:SoftwareSourceCode ; rdfs:label "Sales by category"@en ; schema:about ; schema:citation ; schema:codeSampleType "Live showcase query"@en ; schema:description "Joins order lines to products to categories by following links, not foreign-key columns."@en ; schema:isPartOf :analysis ; schema:name "Sales by category"@en ; schema:position 109 ; schema:potentialAction :open-nw-sparql-category-sales ; schema:programmingLanguage "SPARQL"@en ; schema:target ; schema:text """PREFIX nw: SELECT ?categoryName (ROUND(SUM(?q * ?p * (1 - ?d))) AS ?totalSales) (SUM(?q) AS ?units) FROM WHERE { ?od a nw:Order_Details ; nw:quantity ?q ; nw:unitprice ?p ; nw:discount ?d ; nw:has_products ?product . ?product nw:has_categories ?cat . ?cat nw:categoryname ?categoryName . } GROUP BY ?categoryName ORDER BY DESC(?totalSales)"""@en . :showcase-onto-cross-source-people a schema:SoftwareSourceCode ; rdfs:label "One shared class, two different sources"@en ; schema:citation ; schema:codeSampleType "Live showcase query"@en ; schema:description "People from CSV files and from Virtuoso SQL tables in one answer: the query follows each generated class up to foaf:Person."@en ; schema:isPartOf :analysis ; schema:name "One shared class, two different sources"@en ; schema:position 107 ; schema:potentialAction :open-onto-cross-source-people ; schema:programmingLanguage "SPARQL"@en ; schema:target ; schema:text """PREFIX foaf: SELECT ?source ?generatedClass (COUNT(DISTINCT ?person) AS ?people) (SAMPLE(?person) AS ?example) WHERE { ?generatedClass rdfs:subClassOf foaf:Person . { GRAPH { ?person a ?generatedClass } BIND("CSV files" AS ?source) } UNION { GRAPH { ?person a ?generatedClass } BIND("Virtuoso SQL tables (Demo.demo)" AS ?source) } } GROUP BY ?source ?generatedClass ORDER BY ?source"""@en . :showcase-pg-sparql-entity-types a schema:SoftwareSourceCode ; rdfs:label "Entity types in the PostgreSQL view"@en ; schema:about ; schema:citation , ; schema:codeSampleType "Live showcase query"@en ; schema:description "16 entity types according to the post: clients, sales, shipments, suppliers and more."@en ; schema:isPartOf :analysis ; schema:name "Entity types in the PostgreSQL view"@en ; schema:position 106 ; schema:potentialAction :open-pg-sparql-entity-types ; schema:programmingLanguage "SPARQL"@en ; schema:target ; schema:text """SELECT ?type (COUNT(?s) AS ?n) FROM WHERE { ?s a ?type } GROUP BY ?type ORDER BY DESC(?n)"""@en . :showcase-pg-spasql-entity-types a schema:SoftwareSourceCode ; rdfs:label "Entity types, SPARQL inside SQL"@en ; schema:about ; schema:citation , ; schema:codeSampleType "Live showcase query"@en ; schema:conditionsOfAccess "Open the example in Virtuoso Data Spaces, then use the signed-in Query Builder."@en ; schema:description "The PostgreSQL RDF View profiled by type and returned to SQL as rows."@en ; schema:isPartOf :analysis ; schema:name "Entity types, SPARQL inside SQL"@en ; schema:position 105 ; schema:potentialAction :open-pg-spasql-entity-types ; schema:programmingLanguage "SPASQL"@en ; schema:target ; schema:text """SELECT type, n FROM ( SPARQL SELECT ?type (COUNT(?s) AS ?n) FROM WHERE { ?s a ?type } GROUP BY ?type ORDER BY DESC(?n) ) AS x"""@en . :showcase-pg-sql-clients a schema:SoftwareSourceCode ; rdfs:label "PostgreSQL clients, queried in place"@en ; schema:citation , ; schema:codeSampleType "Live showcase query"@en ; schema:conditionsOfAccess "Open the example in Virtuoso Data Spaces, then use the signed-in Query Builder."@en ; schema:description "The attached PostgreSQL table, read through Virtuoso over XMLA without moving the data."@en ; schema:isPartOf :analysis ; schema:name "PostgreSQL clients, queried in place"@en ; schema:position 104 ; schema:potentialAction :open-pg-sql-clients ; schema:programmingLanguage "SQL"@en ; schema:target ; schema:text "SELECT TOP 10 clientid, clientname, clientgender, clientcountryid FROM \"postgres\".\"postgres_jdbc_mt\".\"clients\""@en . :showcase-ss-sql-federated-join a schema:SoftwareSourceCode ; rdfs:label "Federated join: SQL Server + MySQL + Virtuoso"@en ; schema:citation , ; schema:codeSampleType "Live showcase query"@en ; schema:conditionsOfAccess "Open the example in Virtuoso Data Spaces, then use the signed-in Query Builder."@en ; schema:description "From the Decisive Knowledge post: customers in SQL Server, orders in MySQL and employees in Virtuoso, joined in one SQL statement. The button opens it with the demo account preset; the post's original link is beside it."@en ; schema:isPartOf :analysis ; schema:name "Federated join: SQL Server + MySQL + Virtuoso"@en ; schema:position 108 ; schema:potentialAction :open-ss-sql-federated-join ; schema:programmingLanguage "SQL"@en ; schema:target ; schema:text """SELECT A.CustomerID, A.CompanyName, B.OrderID, C.EmployeeID, C.LastName, C.FirstName FROM "sqlserver"."northwind"."customers" A NATURAL JOIN "mysql5"."northwind"."orders" B NATURAL JOIN "Demo"."demo"."employees" C"""@en . :step-align-meaning a schema:HowToStep ; rdfs:label "Publish shared business meaning"@en ; schema:author ; schema:citation , , ; schema:description "Generate Linked Data Views and their source ontology, assign stable row hyperlinks, and align relevant classes and properties with shared vocabularies. Preserve the source of each definition and its version."@en ; schema:isPartOf :workflow ; schema:name "Publish shared business meaning"@en ; schema:position 3 ; schema:text "Generate Linked Data Views and their source ontology, assign stable row hyperlinks, and align relevant classes and properties with shared vocabularies. Preserve the source of each definition and its version."@en . :step-configure-harness a schema:HowToStep ; rdfs:label "Install the harness and bind memory"@en ; schema:author ; schema:citation , , ; schema:description "Install OPAL as a Virtuoso VAD module. Configure the Virtuoso store for agent-rdf-memory and bind the agent through AGENTS.md. Register the allowed tools and the task’s context-retrieval policy."@en ; schema:isPartOf :workflow ; schema:name "Install the harness and bind memory"@en ; schema:position 4 ; schema:text "Install OPAL as a Virtuoso VAD module. Configure the Virtuoso store for agent-rdf-memory and bind the agent through AGENTS.md. Register the allowed tools and the task’s context-retrieval policy."@en . :step-connect-state a schema:HowToStep ; rdfs:label "Connect approved data"@en ; schema:author ; schema:citation , , ; schema:description "Configure authenticated data-source access. Use UDA drivers or bridges where applicable; attach approved tables or views to Virtuoso. If Databricks is included, verify the selected JDBC path and its source permissions."@en ; schema:isPartOf :workflow ; schema:name "Connect approved data"@en ; schema:position 2 ; schema:text "Configure authenticated data-source access. Use UDA drivers or bridges where applicable; attach approved tables or views to Virtuoso. If Databricks is included, verify the selected JDBC path and its source permissions."@en . :step-define-scope a schema:HowToStep ; rdfs:label "Choose one bounded decision"@en ; schema:author ; schema:citation , , ; schema:description "Specify the task, accountable owner, permitted actions, source systems, review threshold, and observable success criteria before connecting an agent."@en ; schema:isPartOf :workflow ; schema:name "Choose one bounded decision"@en ; schema:position 1 ; schema:text "Specify the task, accountable owner, permitted actions, source systems, review threshold, and observable success criteria before connecting an agent."@en . :step-enforce a schema:HowToStep ; rdfs:label "Enforce access at the runtime boundary"@en ; schema:author ; schema:citation , , ; schema:description "Configure source permissions and Virtuoso/VAL access rules for the required services and graphs. Check both allowed and denied cases. Keep action approval requirements explicit in the workflow."@en ; schema:isPartOf :workflow ; schema:name "Enforce access at the runtime boundary"@en ; schema:position 5 ; schema:text "Configure source permissions and Virtuoso/VAL access rules for the required services and graphs. Check both allowed and denied cases. Keep action approval requirements explicit in the workflow."@en . :step-evaluate a schema:HowToStep ; rdfs:label "Evaluate with representative cases"@en ; schema:author ; schema:citation , , ; schema:description "Run a bounded set of ordinary, conflicting, and exceptional cases. Inspect evidence citations and proposed actions as well as final answers. Retain reviewer corrections and outcomes using the organization’s retention rules."@en ; schema:isPartOf :workflow ; schema:name "Evaluate with representative cases"@en ; schema:position 6 ; schema:text "Run a bounded set of ordinary, conflicting, and exceptional cases. Inspect evidence citations and proposed actions as well as final answers. Retain reviewer corrections and outcomes using the organization’s retention rules."@en . :step-replace a schema:HowToStep ; rdfs:label "Replace the model and repeat"@en ; schema:author ; schema:citation , , ; schema:description "Use the same definitions, evaluation cases, and authorized tools with another model. Compare outcomes and preserved context, then refine the procedure from the observed differences."@en ; schema:isPartOf :workflow ; schema:name "Replace the model and repeat"@en ; schema:position 7 ; schema:text "Use the same definitions, evaluation cases, and authorized tools with another model. Compare outcomes and preserved context, then refine the procedure from the observed differences."@en . a schema:DefinedTerm ; rdfs:label "Ontology alignment"@en ; schema:citation , ; schema:description "Explicit relationships between source classes or properties and shared vocabulary terms, enabling common interpretation across data sources."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Ontology alignment"@en ; schema:position 9 ; owl:sameAs . a schema:Organization ; rdfs:label "OpenLink Software"@en ; schema:name "OpenLink Software"@en ; owl:sameAs . a schema:DefinedTerm ; rdfs:label "AI harness"@en ; schema:citation , ; schema:description "The surrounding interfaces, tools, context retrieval, execution controls, and feedback mechanisms that make a model usable for a task."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "AI harness"@en ; schema:position 5 . a schema:SoftwareApplication ; rdfs:label "agent-rdf-memory"@en ; schema:applicationCategory "Virtuoso module"@en ; schema:citation ; schema:description "Virtuoso-backed RDF memory module with AGENTS.md operational binding; carries preferences, context-routing rules, how-tos, and session context."@en ; schema:isPartOf ; schema:name "agent-rdf-memory"@en . :coopetitive-meshup a schema:DefinedTerm ; rdfs:label "Coopetitive meshup"@en ; schema:citation , , , ; schema:description "A semantically connected analysis that identifies both competitive overlap and complementary integration opportunities."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Coopetitive meshup"@en ; schema:position 13 . :cross-platform-super-key a schema:DefinedTerm ; rdfs:label "Cross-platform super-key"@en ; schema:citation , ; schema:description "A record’s hyperlink used as a stable identifier beyond its originating database, allowing relationships across data sources."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Cross-platform super-key"@en ; schema:position 7 . :durable-learning-loop a schema:DefinedTerm ; rdfs:label "Durable learning loop"@en ; schema:citation , ; schema:description "A repeatable process that connects context, authorized action, evaluated outcomes, and retained corrections across model changes."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Durable learning loop"@en ; schema:position 14 . :evaluated-case a schema:DefinedTerm ; rdfs:label "Evaluated case"@en ; schema:citation , , ; schema:description "A retained task example with evidence, expected behavior, observed results, and any reviewer correction, usable in future evaluation."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Evaluated case"@en ; schema:position 11 . :genie-ontology a schema:DefinedTerm ; rdfs:label "Genie Ontology"@en ; schema:citation , ; schema:description "Databricks’ unified business context layer combining curated semantics and inferred snippets, ranked for authority and constrained by source permissions."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Genie Ontology"@en ; schema:position 4 . :lakebase a schema:DefinedTerm ; rdfs:label "Lakebase"@en ; schema:citation , ; schema:description "Databricks’ operational database offering, based on PostgreSQL technology, with branch-based development and testing."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Lakebase"@en ; schema:position 3 . :lakehouse a schema:DefinedTerm ; rdfs:label "Lakehouse"@en ; schema:citation ; schema:description "The analytical architecture the article describes as combining flexible lake storage with warehouse-style reliability and query workloads."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Lakehouse"@en ; schema:position 2 . :linked-data-view a schema:DefinedTerm ; rdfs:label "Linked Data View"@en ; schema:citation , ; schema:description "A mapping that exposes relational data as RDF for SPARQL access without requiring a separately regenerated physical copy of every mapped triple."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Linked Data View"@en ; schema:position 8 . :operational-memory-contract a schema:DefinedTerm ; rdfs:label "Operational memory contract"@en ; schema:citation , ; schema:description "Queryable instructions and retrieval rules that bind an agent’s work to the operator’s preferences and relevant prior context."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Operational memory contract"@en ; schema:position 6 . :question-1 a schema:Question ; rdfs:label "What is the central coopetitive thesis?"@en ; schema:acceptedAnswer :answer-1 ; schema:author ; schema:citation , , ; schema:hasPart :answer-1 ; schema:isPartOf :faq ; schema:name "What is the central coopetitive thesis?"@en ; schema:position 1 . :question-10 a schema:Question ; rdfs:label "How does agent-rdf-memory make a query workflow repeatable?"@en ; schema:acceptedAnswer :answer-10 ; schema:author ; schema:citation , , ; schema:hasPart :answer-10 ; schema:isPartOf :faq ; schema:name "How does agent-rdf-memory make a query workflow repeatable?"@en ; schema:position 10 . :question-11 a schema:Question ; rdfs:label "What should survive a model change?"@en ; schema:acceptedAnswer :answer-11 ; schema:author ; schema:citation , , ; schema:hasPart :answer-11 ; schema:isPartOf :faq ; schema:name "What should survive a model change?"@en ; schema:position 11 . :question-12 a schema:Question ; rdfs:label "What would establish that the integration works?"@en ; schema:acceptedAnswer :answer-12 ; schema:author ; schema:citation , , ; schema:hasPart :answer-12 ; schema:isPartOf :faq ; schema:name "What would establish that the integration works?"@en ; schema:position 12 . :question-2 a schema:Question ; rdfs:label "Is OPAL the same thing as Genie?"@en ; schema:acceptedAnswer :answer-2 ; schema:author ; schema:citation , , , ; schema:hasPart :answer-2 ; schema:isPartOf :faq ; schema:name "Is OPAL the same thing as Genie?"@en ; schema:position 2 . :question-3 a schema:Question ; rdfs:label "Are OPAL and agent-rdf-memory separate platforms beside Virtuoso?"@en ; schema:acceptedAnswer :answer-3 ; schema:author ; schema:citation , , , ; schema:hasPart :answer-3 ; schema:isPartOf :faq ; schema:name "Are OPAL and agent-rdf-memory separate platforms beside Virtuoso?"@en ; schema:position 3 . :question-4 a schema:Question ; rdfs:label "What does UDA contribute?"@en ; schema:acceptedAnswer :answer-4 ; schema:author ; schema:citation , , , , ; schema:hasPart :answer-4 ; schema:isPartOf :faq ; schema:name "What does UDA contribute?"@en ; schema:position 4 . :question-5 a schema:Question ; rdfs:label "Must all enterprise data move into one database?"@en ; schema:acceptedAnswer :answer-5 ; schema:author ; schema:citation , , , ; schema:hasPart :answer-5 ; schema:isPartOf :faq ; schema:name "Must all enterprise data move into one database?"@en ; schema:position 5 . :question-6 a schema:Question ; rdfs:label "Does an RDF memory rule enforce access permissions?"@en ; schema:acceptedAnswer :answer-6 ; schema:author ; schema:citation , , , ; schema:hasPart :answer-6 ; schema:isPartOf :faq ; schema:name "Does an RDF memory rule enforce access permissions?"@en ; schema:position 6 . :question-7 a schema:Question ; rdfs:label "Is Genie Ontology equivalent to RDF reasoning?"@en ; schema:acceptedAnswer :answer-7 ; schema:author ; schema:citation , , , , ; schema:hasPart :answer-7 ; schema:isPartOf :faq ; schema:name "Is Genie Ontology equivalent to RDF reasoning?"@en ; schema:position 7 . :question-8 a schema:Question ; rdfs:label "Does the benchmark prove that one portfolio is better?"@en ; schema:acceptedAnswer :answer-8 ; schema:author ; schema:citation , , , ; schema:hasPart :answer-8 ; schema:isPartOf :faq ; schema:name "Does the benchmark prove that one portfolio is better?"@en ; schema:position 8 . :question-9 a schema:Question ; rdfs:label "Can a named graph replace a Lakebase branch?"@en ; schema:acceptedAnswer :answer-9 ; schema:author ; schema:citation , , , , ; schema:hasPart :answer-9 ; schema:isPartOf :faq ; schema:name "Can a named graph replace a Lakebase branch?"@en ; schema:position 9 . :runtime-authorization a schema:DefinedTerm ; rdfs:label "Runtime authorization"@en ; schema:citation , ; schema:description "The access decision applied by a running service, tool, or data source, distinct from an instruction describing intended agent behavior."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Runtime authorization"@en ; schema:position 10 . :sovereign-firm a schema:DefinedTerm ; rdfs:label "Sovereign firm"@en ; schema:citation ; schema:description "In the article’s framing, a firm able to change AI providers while retaining the knowledge and evaluated experience on which its operations depend."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "Sovereign firm"@en ; schema:position 12 . :system-of-record-for-agents a schema:DefinedTerm ; rdfs:label "System of Record for Agents (SORA)"@en ; schema:citation ; schema:description "The article’s name for the firm’s shared foundation of state, meaning, authority, and evaluation that supports agent work."@en ; schema:inDefinedTermSet :glossary ; schema:isPartOf :glossary ; schema:name "System of Record for Agents (SORA)"@en ; schema:position 1 . a schema:WebAPI ; rdfs:label "demo.openlinksw.com SPARQL endpoint"@en ; schema:description "Public SPARQL access to the showcase graphs and relational RDF Views."@en ; schema:name "demo.openlinksw.com SPARQL endpoint"@en . a schema:WebAPI ; rdfs:label "URIBurner SPARQL endpoint"@en ; schema:description "SPARQL service for querying RDF knowledge graphs."@en ; schema:name "URIBurner SPARQL endpoint"@en . a schema:WebAPI ; rdfs:label "demo.openlinksw.com XMLA service"@en ; schema:description "SQL and SPASQL access used by the showcase Query Builder."@en ; schema:name "demo.openlinksw.com XMLA service"@en . a schema:CreativeWork ; rdfs:label "Unity Gateway release notes"@en ; schema:description "Official documentation of centralized AI access, cost, and service governance; capabilities have staged release and feature-specific status."@en ; schema:name "Unity Gateway release notes"@en ; schema:url . a schema:Person ; rdfs:label "Kingsley Uyi Idehen"@en ; schema:name "Kingsley Uyi Idehen"@en ; owl:sameAs . :coopetitive-mesh a schema:CreativeWork ; rdfs:label "Compete on experience; cooperate through interfaces"@en ; schema:author ; schema:description "The two approaches compete for the agent’s trusted working context. They can also form a composed architecture when the enterprise wants Databricks workloads and cross-system semantic context together."@en ; schema:hasPart :competitive-overlap, :complementary-route, :non-equivalence, :policy-boundary ; schema:isPartOf :analysis ; schema:itemListOrder schema:ItemListUnordered ; schema:name "Compete on experience; cooperate through interfaces"@en ; schema:position 6 . :dimension-coexistence a schema:CreativeWork ; rdfs:label "Where can they cooperate?"@en ; schema:description "A proposed integration boundary"@en ; schema:hasPart :position-coexistence-databricks, :position-coexistence-virtuoso ; schema:isPartOf :four-questions ; schema:name "Where can they cooperate?"@en ; schema:position 8 . :dimension-evaluation a schema:CreativeWork ; rdfs:label "Did it work?"@en ; schema:description "Evaluation and retained outcomes"@en ; schema:hasPart :position-evaluation-databricks, :position-evaluation-virtuoso ; schema:isPartOf :four-questions ; schema:name "Did it work?"@en ; schema:position 4 . :dimension-interface a schema:CreativeWork ; rdfs:label "How do people act?"@en ; schema:description "Natural language and tool use"@en ; schema:hasPart :position-interface-databricks, :position-interface-virtuoso ; schema:isPartOf :four-questions ; schema:name "How do people act?"@en ; schema:position 5 . :dimension-isolation a schema:CreativeWork ; rdfs:label "How is experimentation isolated?"@en ; schema:description "Database isolation versus semantic scope"@en ; schema:hasPart :position-isolation-databricks, :position-isolation-virtuoso ; schema:isPartOf :four-questions ; schema:name "How is experimentation isolated?"@en ; schema:position 7 . :dimension-meaning a schema:CreativeWork ; rdfs:label "What does it mean?"@en ; schema:description "Business meaning and authority"@en ; schema:hasPart :position-meaning-databricks, :position-meaning-virtuoso ; schema:isPartOf :four-questions ; schema:name "What does it mean?"@en ; schema:position 2 . :dimension-permission a schema:CreativeWork ; rdfs:label "What is allowed?"@en ; schema:description "Identity and runtime authorization"@en ; schema:hasPart :position-permission-databricks, :position-permission-virtuoso ; schema:isPartOf :four-questions ; schema:name "What is allowed?"@en ; schema:position 3 . :dimension-portability a schema:CreativeWork ; rdfs:label "What survives a model change?"@en ; schema:description "Portable knowledge and operational binding"@en ; schema:hasPart :position-portability-databricks, :position-portability-virtuoso ; schema:isPartOf :four-questions ; schema:name "What survives a model change?"@en ; schema:position 6 . :dimension-state a schema:CreativeWork ; rdfs:label "What is true?"@en ; schema:description "Operational and analytical state"@en ; schema:hasPart :position-state-databricks, :position-state-virtuoso ; schema:isPartOf :four-questions ; schema:name "What is true?"@en ; schema:position 1 . :evidence-boundaries a schema:CreativeWork ; rdfs:label "Read the evidence at its actual scale"@en ; schema:author ; schema:description "The article’s organizational thesis, product documentation, and our integration proposal answer different kinds of questions. Keep each conclusion attached to the evidence that supports it."@en ; schema:hasPart :benchmark, :capability-proposal, :market-claims, :sovereignty-test ; schema:isPartOf :analysis ; schema:itemListOrder schema:ItemListUnordered ; schema:name "Read the evidence at its actual scale"@en ; schema:position 8 . :from-spark-to-agents a schema:CreativeWork ; rdfs:label "From Spark to agents"@en ; schema:author ; schema:description "The article presents four successive technology curves as the foundation for a new operating model. This is its architectural history, summarized without using revenue or activity figures as technical proof."@en ; schema:hasPart :evolution-agents, :evolution-lakebase, :evolution-lakehouse, :evolution-spark ; schema:isPartOf :analysis ; schema:name "From Spark to agents"@en ; schema:position 2 . :live-showcases a schema:CreativeWork ; rdfs:label "See the data work across interfaces"@en ; schema:author ; schema:description "Explore existing showcases on demo.openlinksw.com: the same enterprise records can serve SQL tools, graph queries, and an agent harness. SPASQL places a SPARQL query inside SQL so its results behave like an ordinary derived table."@en ; schema:hasPart :showcase-databricks, :showcase-federation, :showcase-ontology, :showcase-postgres ; schema:isPartOf :analysis ; schema:itemListOrder schema:ItemListUnordered ; schema:name "See the data work across interfaces"@en ; schema:position 4 . :openlink-architecture a schema:CreativeWork ; rdfs:label "OpenLink Architecture"@en ; schema:author ; schema:description "Virtuoso supplies the data substrate. Its modules add an AI harness and queryable operational memory; UDA complements them with connectivity. This mapping is our synthesis of the documented capabilities."@en ; schema:hasPart :connected-state, :harness, :operational-memory, :shared-meaning ; schema:isPartOf :analysis ; schema:itemListOrder schema:ItemListUnordered ; schema:name "OpenLink Architecture"@en ; schema:position 3 . a schema:CreativeWork ; rdfs:label "Customer Sales Performance Dashboard — SPASQL"@en ; schema:description "Existing OpenLink weblog showcase of sales analysis over a SQL Server RDF View."@en ; schema:name "Customer Sales Performance Dashboard — SPASQL"@en ; schema:url . a schema:CreativeWork ; rdfs:label "OPAL installation and usage guide"@en ; schema:description "Official OpenLink guide describing OPAL as a Virtuoso add-on installed with VAD packages."@en ; schema:name "OPAL installation and usage guide"@en ; schema:url . :memory-in-use a schema:CreativeWork ; rdfs:label "Agent-rdf-memory in use"@en ; schema:author ; schema:description "A bounded invoice-exception review loop connects retrieved business definitions, authorized queries, human review, and reusable corrections."@en ; schema:hasPart :case-context, :case-evidence, :case-learning, :case-review, :this-collection ; schema:isPartOf :analysis ; schema:itemListOrder schema:ItemListUnordered ; schema:name "Agent-rdf-memory in use"@en ; schema:position 7 . :source-thesis a schema:CreativeWork ; rdfs:label "What the article contributes"@en ; schema:author ; schema:description "The article links the data architecture of an enterprise with the shape of work and management. These are the authors’ arguments, rather than established organizational forecasts."@en ; schema:hasPart :coordination-economics, :institutional-context, :judgment, :shared-record, :sovereignty ; schema:isPartOf :analysis ; schema:itemListOrder schema:ItemListUnordered ; schema:name "What the article contributes"@en ; schema:position 1 . a schema:CreativeWork ; rdfs:label "PostgreSQL records as Linked Data"@en ; schema:description "Existing OpenLink weblog showcase explaining record hyperlinks, generated classes, and relationships over PostgreSQL."@en ; schema:name "PostgreSQL records as Linked Data"@en ; schema:url . :workflow a schema:HowTo ; rdfs:label "Build a bounded, portable learning loop"@en ; schema:description "A proposed implementation sequence for the coopetitive architecture; adapt it to the organization’s policies and installed components."@en ; schema:hasPart :step-align-meaning, :step-configure-harness, :step-connect-state, :step-define-scope, :step-enforce, :step-evaluate, :step-replace ; schema:isPartOf :analysis ; schema:name "Build a bounded, portable learning loop"@en ; schema:step :step-align-meaning, :step-configure-harness, :step-connect-state, :step-define-scope, :step-enforce, :step-evaluate, :step-replace . a schema:CreativeWork ; rdfs:label "Genie One product overview"@en ; schema:description "Official product description covering natural-language interaction, external knowledge connectors, MCP, and governed actions."@en ; schema:name "Genie One product overview"@en ; schema:url . a schema:CreativeWork ; rdfs:label "Databricks JDBC connection configuration"@en ; schema:description "Official configuration documentation for authenticated connections to Databricks compute and SQL warehouses."@en ; schema:name "Databricks JDBC connection configuration"@en ; schema:url . a schema:CreativeWork ; rdfs:label "Databricks → Virtual Knowledge Graph with Virtuoso"@en ; schema:description "Existing URIBurner weblog showcase of the Databricks bakehouse virtual knowledge graph."@en ; schema:name "Databricks → Virtual Knowledge Graph with Virtuoso"@en ; schema:url . :four-questions a schema:CreativeWork ; rdfs:label "Four questions, two architectural routes"@en ; schema:author ; schema:description "The following comparison is a capability map, without winner scores or implied feature equivalence. OPAL and agent-rdf-memory are included within the Virtuoso position."@en ; schema:hasPart :dimension-coexistence, :dimension-evaluation, :dimension-interface, :dimension-isolation, :dimension-meaning, :dimension-permission, :dimension-portability, :dimension-state ; schema:isPartOf :analysis ; schema:itemListOrder schema:ItemListUnordered ; schema:name "Four questions, two architectural routes"@en ; schema:position 5 . a schema:Person ; rdfs:label "Ben Horowitz"@en ; schema:name "Ben Horowitz"@en . a schema:Person ; rdfs:label "Michael McGuiness"@en ; schema:name "Michael McGuiness"@en . a schema:SoftwareApplication ; rdfs:label "Databricks platform"@en ; schema:applicationCategory "Integrated data and AI platform"@en ; schema:citation ; schema:description "The integrated Databricks data and AI platform discussed by the article; distinct from the Databricks company."@en ; schema:hasPart ; schema:name "Databricks platform"@en ; schema:url . a schema:CreativeWork ; rdfs:label "Lakebase branches"@en ; schema:description "Official documentation of isolated database branches for development and testing."@en ; schema:name "Lakebase branches"@en ; schema:url . a schema:CreativeWork ; rdfs:label "Universal Data Access drivers"@en ; schema:description "Official description of ODBC, JDBC, ADO.NET, and OLE DB connectivity and connection-level security features."@en ; schema:name "Universal Data Access drivers"@en ; schema:url . a schema:CreativeWork ; rdfs:label "Genie One, Genie Agents, and Genie Ontology"@en ; schema:description "Databricks launch announcement dated June 16, 2026, including an internal 28-question benchmark and its comparison scope."@en ; schema:name "Genie One, Genie Agents, and Genie Ontology"@en ; schema:url . a schema:CreativeWork ; rdfs:label "Genie Ontology documentation"@en ; schema:description "Official documentation: curated and inferred context, authority scoring, source permissions, and Public Preview status; inspected October 27, 2026."@en ; schema:name "Genie Ontology documentation"@en ; schema:url . :faq a schema:FAQPage ; rdfs:label "Frequently asked questions"@en ; schema:hasPart :question-1, :question-10, :question-11, :question-12, :question-2, :question-3, :question-4, :question-5, :question-6, :question-7, :question-8, :question-9 ; schema:isPartOf :analysis ; schema:mainEntity :question-1, :question-10, :question-11, :question-12, :question-2, :question-3, :question-4, :question-5, :question-6, :question-7, :question-8, :question-9 ; schema:name "Frequently asked questions"@en . a schema:CreativeWork ; rdfs:label "Virtuoso Authentication Layer rules"@en ; schema:description "Official documentation of RDF-based access-control rules and groups; enforcement is supplied by the configured runtime."@en ; schema:name "Virtuoso Authentication Layer rules"@en ; schema:url . a schema:SoftwareApplication ; rdfs:label "Virtuoso"@en ; schema:applicationCategory "Multi-model data server + OPAL and agent-rdf-memory modules"@en ; schema:citation ; schema:description "Multi-model database and data virtualization server, extended here with OPAL and agent-rdf-memory modules."@en ; schema:hasPart , ; schema:name "Virtuoso"@en ; schema:provider ; schema:url ; owl:sameAs . a schema:CreativeWork, schema:WebApplication ; rdfs:label "Virtuoso Data Spaces"@en ; schema:citation ; schema:description "Existing application containing the runnable showcases and their query text."@en, "Existing live application, found through the URIBurner weblog, with SQL, SPASQL, SPARQL, ontology, and agent showcases."@en ; schema:name "Virtuoso Data Spaces"@en ; schema:provider ; schema:url . a schema:CreativeWork ; rdfs:label "Generating Linked Data Views"@en ; schema:description "Official Virtuoso documentation covering attachment of ODBC/JDBC-accessible tables, ontology generation, and Linked Data publication."@en ; schema:name "Generating Linked Data Views"@en ; schema:url . a schema:CreativeWork ; rdfs:label "Linked Data Views over relational sources"@en ; schema:description "Official documentation of SPARQL-to-SQL translation and queries combining virtual relational graphs with stored RDF."@en ; schema:name "Linked Data Views over relational sources"@en ; schema:url . :analysis a schema:Article ; rdfs:label "The firm that keeps what it learns"@en ; schema:about , , , , :coopetitive-meshup, :cross-platform-super-key, :durable-learning-loop, :evaluated-case, :genie-ontology, :lakebase, :lakehouse, :linked-data-view, :operational-memory-contract, :runtime-authorization, :sovereign-firm, :system-of-record-for-agents, ; schema:abstract "The article makes the firm’s shared record central to autonomous work. This meshup asks how that record can remain useful across databases, agents, and models. Databricks offers an integrated data-and-agent environment. Virtuoso, with its OpenLink AI Layer (OPAL) and agent-rdf-memory modules, complemented by Universal Data Access (UDA), offers a loosely coupled route. Their overlap creates competition, while standard interfaces create room for cooperation. Durable advantage depends on preserving business meaning, permissions, evidence, and evaluated decisions."@en ; schema:accountablePerson ; schema:author ; schema:citation , , , , , , , , , , , , , , , , , ; schema:dateCreated "2026-10-27T16:55:47+00:00"^^xsd:dateTime ; schema:description "A coopetitive meshup of Databricks and OpenLink’s portfolio: shared business meaning, governed action, and memory that survives a model change."@en ; schema:hasPart :coopetitive-mesh, :evidence-boundaries, :faq, :four-questions, :from-spark-to-agents, :glossary, :live-showcases, :memory-in-use, :openlink-architecture, :query-claims, :query-comparison, :query-modules, :query-workflow, :showcase-db-sparql-revenue-by-city, :showcase-db-spasql-revenue-by-city, :showcase-db-sql-revenue-by-city, :showcase-nw-sparql-category-sales, :showcase-onto-cross-source-people, :showcase-pg-sparql-entity-types, :showcase-pg-spasql-entity-types, :showcase-pg-sql-clients, :showcase-ss-sql-federated-join, :source-thesis, :workflow ; schema:isBasedOn ; schema:name "The firm that keeps what it learns"@en ; prov:wasGeneratedBy , , :curationAgent, :generation . :glossary a schema:DefinedTermSet ; rdfs:label "Core technical glossary"@en ; schema:description "Contextual definitions for the article and this meshup."@en ; schema:hasDefinedTerm , , :coopetitive-meshup, :cross-platform-super-key, :durable-learning-loop, :evaluated-case, :genie-ontology, :lakebase, :lakehouse, :linked-data-view, :operational-memory-contract, :runtime-authorization, :sovereign-firm, :system-of-record-for-agents ; schema:hasPart , , :coopetitive-meshup, :cross-platform-super-key, :durable-learning-loop, :evaluated-case, :genie-ontology, :lakebase, :lakehouse, :linked-data-view, :operational-memory-contract, :runtime-authorization, :sovereign-firm, :system-of-record-for-agents ; schema:isPartOf :analysis ; schema:name "Core technical glossary"@en . a schema:CreativeWork ; rdfs:label "OpenLink AI Layer"@en ; schema:description "Official OPAL product description: agents and skills loosely coupled with models, data spaces, APIs, and declarative query services."@en ; schema:name "OpenLink AI Layer"@en ; schema:url . a schema:CreativeWork ; rdfs:label "Agent RDF Memory protocol"@en ; schema:description "Public specification of the RDF behavioral contract, intent-routed retrieval, optional private overlay, and endpoint/file fallback."@en ; schema:name "Agent RDF Memory protocol"@en ; schema:url . a schema:BlogPosting ; rdfs:label "Databricks & the Future of the Firm"@en ; schema:author , ; schema:datePublished "2026-10-27T14:02:28.268000+00:00"^^xsd:dateTime ; schema:description "How agents and new database technology will change the shape of the firm—and what we do at work all day"@en ; schema:name "Databricks & the Future of the Firm"@en ; schema:publisher ; schema:url . a schema:SoftwareApplication ; rdfs:label "kg-generator"@en ; schema:name "kg-generator"@en ; prov:actedOnBehalfOf .