@prefix : . @prefix schema: . @prefix rdf: . @prefix rdfs: . @prefix xsd: . @prefix skos: . @prefix owl: . @prefix prov: . ############################################################ # Lightweight Ontology ############################################################ : a owl:Ontology ; rdfs:label "Box vs Network Data Architecture Ontology"@en ; rdfs:comment "A lightweight ontology for modeling the architectural shift from box-shaped BI/data warehouses to network-shaped knowledge graphs for AI, based on Tony Seale's LinkedIn analysis and community discussion."@en ; schema:name "Box vs Network Data Architecture Ontology"@en ; schema:description "A lightweight ontology for modeling the architectural shift from box-shaped BI/data warehouses to network-shaped knowledge graphs for AI."@en ; schema:identifier "https://www.linkedin.com/posts/tonyseale_every-c-suite-is-arriving-at-the-same-uncomfortable-share-7465730567645315073-O_VW/" . :ArchitectureConcept a rdfs:Class ; rdfs:label "Architecture Concept"@en ; rdfs:comment "A key concept in enterprise data architecture — the structural principles that determine whether data infrastructure serves or obstructs AI."@en ; rdfs:isDefinedBy : . :DataArchitectureVertical a rdfs:Class ; rdfs:label "Data Architecture Vertical"@en ; rdfs:comment "A market segment in the enterprise data infrastructure space impacted by the shift from box-shaped to network-shaped architectures."@en ; rdfs:isDefinedBy : . :hasArchitecturalImplication a rdf:Property ; rdfs:label "has architectural implication"@en ; rdfs:comment "The architectural or strategic implication of this concept for enterprise data infrastructure."@en ; rdfs:domain :ArchitectureConcept ; rdfs:range xsd:string ; rdfs:isDefinedBy : . ############################################################ # Main Analysis CreativeWork ############################################################ :analysis a schema:SocialMediaPosting ; schema:name "Every C-suite is arriving at the same uncomfortable realisation right now"@en ; schema:headline "The box served the last era well. It is just the wrong shape for this one."@en ; schema:abstract "Tony Seale argues that enterprise data infrastructure — warehouses, lakehouses, dashboards — was built for a box-shaped world of rows, columns, and aggregation. AI needs a network: relationships that cross domain boundaries, knowledge graphs where structure IS knowledge, and an ontological core that must be owned, not outsourced. Kingsley Uyi Idehen extends this with the 'webby graph' — hyperlink-named entities and relationships enabling scalable data access by reference across intranets, extranets, and the Internet."@en ; schema:articleBody "The post presents four theses: (1) Bad context in → bad decisions out — fractured enterprise data leads AI to the wrong answer. (2) BI was built for a box, intelligence needs a network — agents follow chains of meaning across boundaries the warehouse kept apart. (3) Learning happens in networks — neural networks imagine, data networks ground. (4) The lessons must live somewhere that is yours — structure IS knowledge, don't outsource your moat. The 36-comment discussion includes Kingsley Uyi Idehen's webby graph extension, Marc A.'s relational defense, Christopher Gaither's operational truth layer, and Jon Cooke's unified semantic KB proposal."@en ; schema:url "https://www.linkedin.com/posts/tonyseale_every-c-suite-is-arriving-at-the-same-uncomfortable-share-7465730567645315073-O_VW/" ; schema:datePublished "2026-05-29"^^xsd:date ; schema:inLanguage "en" ; schema:author ; schema:comment :commentKingsley, :commentTonyFollowUp, :commentJonCooke, :commentMarcA, :commentChristopherGaither, :commentBarbaraMatthews, :commentPaulOudeLuttighuis, :commentAliAzzam, :commentBoLora, :commentIFields ; schema:about :boxVsNetworkThesis, :neuralSymbolicLoop, :webbyGraphThesis, :structureIsKnowledge, :dataIntegrationElephant, :knowledgeGraphMarket, :semanticDataInfrastructureMarket ; schema:hasPart :faqSection, :glossarySection, :howtoSection, :conceptsSection, :commentsSection, :industryVerticalsSection, : ; schema:interactionStatistic [ a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount 240 ] ; prov:wasGeneratedBy . ############################################################ # People ############################################################ a schema:Person ; schema:name "Tony Seale"@en ; schema:givenName "Tony"@en ; schema:familyName "Seale"@en ; schema:url "https://www.linkedin.com/in/tonyseale" ; schema:identifier "https://www.linkedin.com/in/tonyseale" ; schema:description "Knowledge graph practitioner and thought leader. Author of the ontology-as-code thesis. Advocates for network-shaped data architectures over box-shaped warehouses as the foundation for enterprise AI."@en . a schema:Person ; schema:name "Kingsley Uyi Idehen"@en ; schema:url "https://www.linkedin.com/in/kidehen" ; schema:identifier "https://www.linkedin.com/in/kidehen" ; schema:jobTitle "Founder & CEO"@en ; schema:worksFor ; schema:description "Founder & CEO of OpenLink Software, Virtuoso creator, Semantic Web pioneer. Extended Seale's network thesis with the webby graph concept — hyperlink-named entities enabling scalable data access by reference."@en ; owl:sameAs , . a schema:Person ; schema:url "https://www.linkedin.com/in/jon-cooke-096bb0" ; schema:identifier "https://www.linkedin.com/in/jon-cooke-096bb0" ; schema:name "Jon Cooke"@en ; schema:givenName "Jon"@en ; schema:familyName "Cooke"@en ; schema:description "Commenter on the post. Argues the neural network and knowledge graph should be unified as a single semantic knowledge base, coupled with reasoning and generative AI — not separate systems."@en . a schema:Person ; schema:url "https://www.linkedin.com/in/makbar" ; schema:identifier "https://www.linkedin.com/in/makbar" ; schema:name "Marc A."@en ; schema:description "Commenter on the post. Defends relational databases' ability to model networks via foreign keys, join tables, and recursive queries. Argues the real issue is optimization for reporting vs. traversal — not database shape. The governed model of meaning matters more than the storage format."@en . a schema:Person ; schema:url "https://www.linkedin.com/in/doc03" ; schema:identifier "https://www.linkedin.com/in/doc03" ; schema:name "Christopher Gaither"@en ; schema:givenName "Christopher"@en ; schema:familyName "Gaither"@en ; schema:affiliation :mimirLabs ; schema:jobTitle "Founder"@en ; schema:description "Founder at Mimir Labs. Argues a knowledge graph needs a governed operating layer beneath it — canonical operational semantics, deterministic state, and governed events that preserve meaning as the business runs, not just document it afterward."@en . a schema:Person ; schema:url "https://www.linkedin.com/in/barbaracmatthews" ; schema:identifier "https://www.linkedin.com/in/barbaracmatthews" ; schema:name "Barbara C. Matthews"@en ; schema:givenName "Barbara"@en ; schema:familyName "Matthews"@en ; schema:description "Commenter on the post. Describes patented automated text labeling technology that outputs CSV, JSON, and Parquet simultaneously, with an expert-led ontology layer for compute efficiency — knowledge graphs as the next level beyond structured data normalization."@en . a schema:Person ; schema:url "https://www.linkedin.com/in/pauloudeluttighuis" ; schema:identifier "https://www.linkedin.com/in/pauloudeluttighuis" ; schema:name "Paul Oude Luttighuis"@en ; schema:givenName "Paul"@en ; schema:familyName "Oude Luttighuis"@en ; schema:description "Commenter on the post. Presents the contrarian view: neither boxes nor networks enable intelligence. Intelligence requires 'tissue' — an entirely different structural paradigm, out of reach of any automation. Intelligence constitutes function without ever becoming it."@en . a schema:Person ; schema:url "https://www.linkedin.com/in/ali-azzam-1b1988139" ; schema:identifier "https://www.linkedin.com/in/ali-azzam-1b1988139" ; schema:name "Ali Azzam"@en ; schema:givenName "Ali"@en ; schema:familyName "Azzam"@en ; schema:description "Commenter on the post. Observes that AI is exposing pre-existing data disconnection problems rather than creating entirely new ones — the integration debt predates AI; AI just made it impossible to keep deferring."@en . a schema:Person ; schema:url "https://www.linkedin.com/in/bolora" ; schema:identifier "https://www.linkedin.com/in/bolora" ; schema:name "Bo Lora"@en ; schema:givenName "Bo"@en ; schema:familyName "Lora"@en ; schema:description "Commenter on the post. Notes the connection to data catalogs and data meshes, pointing out AWS rebranded their implementation as the 'Semantic Hub' — the convergence of data mesh patterns with semantic layer thinking."@en . :iFields a schema:Person ; schema:name "I. Fields"@en ; schema:description "Commenter on the post. Reinforces the box-vs-network framing: warehouses answer known questions efficiently, but agents need paths — customer to contract to risk to policy. This makes lineage and semantic links first-class infrastructure, not metadata afterthoughts."@en . ############################################################ # Comments ############################################################ :commentKingsley a schema:Comment ; schema:text "\"This is the elephant in every enterprise: the data integration problem we have been postponing for twenty years. AI did not create it. AI just made it impossible to keep ignoring.\" Yep! \"BI was built for a box. Intelligence needs a network.\" My slight tweak regarding networks: Intelligence needs a graph deployed in webby form. Networks comprise relationships between entities of the same type; graphs do not have that limitation. As usual, the \"webby\" part comes from naming entities and relationships using hyperlinks, which enables scalable data access by reference across intranets, extranets, and the Internet. Whenever this becomes the norm, the following will become far less challenging in the age of AI Agents and Agent Skills: 1. Identity — via standardized identifiers (ideally hyperlinks) 2. Identification — via profile documents comprising entity relationships that symbolically represent credentials 3. Authentication — via existing protocols that verify credentials in profile documents 4. Authorization — via fine-grained, attribute-based access controls functioning as symbolic representations of policy 5. Data spaces — where create, read, update, and delete operations constrained by 1–4 occur"@en ; schema:description "Extends the network thesis with the webby graph: hyperlink-named entities and relationships turn data integration from an ETL/copy problem into a web-architecture/reference problem. Maps the implications across Identity, Identification, Authentication, Authorization, and Data Spaces."@en ; schema:author ; schema:isPartOf :commentsSection . :commentTonyFollowUp a schema:Comment ; schema:text "For further reading - I've been making this same argument for a long time. The shape was always going to be a network: 2022 - Networks: An Organic Structure, 2023 - Is Data Integration the Elephant in the Room?, 2024 - A Network of Networks, 2025 - The Neural-Symbolic Loop, Two Years On, and now it's gone mainstream - Ontology Is Having Its Moment. I called the elephant back in early 2023. The data integration problem isn't new - AI just turned it from a someday problem into a right-now one."@en ; schema:description "Traces the evolution of the box-vs-network argument through his published work from 2022 to 2026."@en ; schema:author ; schema:isPartOf :commentsSection . :commentJonCooke a schema:Comment ; schema:text "Totally agree with this Tony Seale - the one thing I would add is the neural network (AI) model doesn't have to be generative part ie one can have the graph and the neural network being the same thing as the semantic knowledge base, then coupled with a reasoning / generative AI models for the rest"@en ; schema:description "Proposes unifying the knowledge graph and neural network into a single semantic knowledge base rather than treating them as separate systems."@en ; schema:author ; schema:isPartOf :commentsSection . :commentMarcA a schema:Comment ; schema:text "I agree with the direction, but I would separate the metaphor from the implementation. Rows and columns can absolutely represent networks. Relational databases have modeled relationships for decades through foreign keys, join tables, association tables, recursive queries, and edge-like structures. The real issue is not that tables cannot hold a network. It is that most enterprise data models were optimized for reporting and aggregation, not for traversing meaning, provenance, context, and business relationships across domains. AI does not need a graph because \"networks\" are fashionable. It needs connected, trustworthy context because business reality is relational: customers, contracts, products, incidents, policies, risks, and decisions all affect each other. A knowledge graph can be a very good way to expose that semantic layer. But the important asset is the governed model of meaning, not the database shape itself."@en ; schema:description "Defends relational databases' ability to model networks. The real issue is optimization for reporting vs. traversal — the governed model of meaning matters more than database shape."@en ; schema:author ; schema:isPartOf :commentsSection . :commentChristopherGaither a schema:Comment ; schema:text "Strong framing. I agree that AI needs more than box-shaped BI. Agents need relationships, context, and meaning. But I'd push one layer deeper: a network is only as useful as the operational truth that feeds it. If the source systems preserve conflicting definitions, ambiguous states, unclear ownership, missing exception context, and fragmented event history, the graph may simply become a more expressive map of the same drift. The data network cannot just describe enterprise reality after the fact. It needs a governed operating layer that preserves meaning as the business runs. That's the layer we're focused on at Mimir Labs: canonical operational semantics, deterministic state, and governed events before intelligence starts reasoning over the network."@en ; schema:description "Pushes deeper: a network needs operational truth beneath it — canonical semantics and governed events that preserve meaning in real time, not just describe it afterward."@en ; schema:author ; schema:isPartOf :commentsSection . :commentBarbaraMatthews a schema:Comment ; schema:text "Very well said. Our patented automated text labeling tech solves for this so that data enters a storage framework in .csv, .json, AND .parquet in order to accelerate customer access to actionable intelligence from the beginning. The expert-led ontology further increases compute efficiency. KGs take it to the next level."@en ; schema:description "Describes a complementary approach: automated text labeling with multi-format output, enhanced by expert-led ontology and knowledge graphs."@en ; schema:author ; schema:isPartOf :commentsSection . :commentPaulOudeLuttighuis a schema:Comment ; schema:text "Neither boxes nor networks enable intelligence. The only difference being that the non-sense is encapsulated in the first case, and distributed in the second. Intelligence requires tissue. And that's an entirely different structure, out of reach of any automation. Intelligence is not (inter)operable. Intelligence doesn't function. It constitutes function, but without ever becoming it. Ever."@en ; schema:description "Presents the contrarian view: intelligence requires 'tissue' — a structural paradigm beyond both boxes and networks, beyond automation's reach."@en ; schema:author ; schema:isPartOf :commentsSection . :commentAliAzzam a schema:Comment ; schema:text "AI is exposing problems companies already had with disconnected data rather than creating entirely new ones"@en ; schema:description "Observes that AI reveals pre-existing integration debt rather than creating new problems."@en ; schema:author ; schema:isPartOf :commentsSection . :commentBoLora a schema:Comment ; schema:text "Tony you for got my favorite, data catalogs and data meshes which AWS just rebranded as the \"Semantic Hub\""@en ; schema:description "Connects the thesis to data catalogs and data meshes, noting AWS's 'Semantic Hub' rebranding."@en ; schema:author ; schema:isPartOf :commentsSection . :commentIFields a schema:Comment ; schema:text "I like the box vs network framing. Warehouses are great at answering known questions, but agents need paths, not just rows — customer to contract to risk to policy. That makes lineage and semantic links first-class infrastructure, not metadata nice-to-haves."@en ; schema:description "Reinforces the framing: agents need traversal paths, making lineage and semantic links first-class infrastructure."@en ; schema:author :iFields ; schema:isPartOf :commentsSection . ############################################################ # Architecture Concepts ############################################################ :boxVsNetworkThesis a :ArchitectureConcept ; schema:name "Box vs Network Architecture"@en ; schema:description "BI was built for a box: rows, columns, tables, optimized for aggregating the past into a report. AI needs a network: agents follow chains of meaning across products, customers, risks, processes, and policies — crossing boundaries the warehouse kept apart. The analytics stack is box-shaped; intelligence is network-shaped."@en ; :hasArchitecturalImplication "Enterprise data infrastructure must shift from aggregation-optimized rectangles to traversal-optimized relationship networks — the warehouse is the wrong shape for AI agents"@en ; schema:isPartOf :conceptsSection . :neuralSymbolicLoop a :ArchitectureConcept ; schema:name "Neural-Symbolic Loop"@en ; schema:description "The deepest pattern: neural networks (the creative, generative half that imagines) paired with data networks (the grounded, factual half that knows what is actually true). Everyone has the first half — frontier models are commodities. Almost nobody has built the second half: a connected model of their own reality, solid enough for intelligence to stand on."@en ; :hasArchitecturalImplication "Competitive advantage shifts from model access to data network quality — the neural network imagines, but the data network grounds"@en ; schema:isPartOf :conceptsSection . :webbyGraphThesis a :ArchitectureConcept ; schema:name "Webby Graph Architecture"@en ; schema:description "Kingsley Uyi Idehen's extension: intelligence needs a graph deployed in webby form. Networks comprise relationships between entities of the same type; graphs do not have that limitation. The 'webby' part comes from naming entities and relationships using hyperlinks, enabling scalable data access by reference across intranets, extranets, and the Internet. This simplifies Identity (standardized hyperlink identifiers), Identification (profile documents), Authentication (protocols), Authorization (fine-grained ACLs), and Data Spaces (CRUD constrained by 1-4)."@en ; :hasArchitecturalImplication "Hyperlink-based entity naming transforms data integration from an ETL problem into a web architecture problem — data access by reference, not by copy"@en ; schema:isPartOf :conceptsSection . :structureIsKnowledge a :ArchitectureConcept ; schema:name "Structure IS Knowledge"@en ; schema:description "In a network, the structure itself is the knowledge. Every relationship a business learns — what a good customer looks like, why a deal failed — is a new edge in the graph. Accumulated conceptual abstractions form the ontological core of the organization. This is the most valuable asset to be built this decade, and it must be owned, not outsourced to a third party."@en ; :hasArchitecturalImplication "The ontological core is a proprietary asset — outsourcing model-of-meaning to a vendor outsources your competitive moat. The intelligence can be rented; the structure must be owned"@en ; schema:isPartOf :conceptsSection . :dataIntegrationElephant a :ArchitectureConcept ; schema:name "The Twenty-Year Data Integration Elephant"@en ; schema:description "The data integration problem enterprises have been postponing for twenty years. Pre-AI, success looked like getting 1% of data into a warehouse. AI made this impossible to keep ignoring — bad context in produces bad decisions out, regardless of model quality. Point the best model at fractured, siloed, contradictory enterprise data and it will reason flawlessly to the wrong answer."@en ; :hasArchitecturalImplication "AI does not create the data integration problem — it makes the cost of ignoring it existential. 1% data coverage was an acceptable pre-AI baseline; it is now a business liability"@en ; schema:isPartOf :conceptsSection . ############################################################ # Industry Verticals ############################################################ :knowledgeGraphMarket a :DataArchitectureVertical ; schema:name "Knowledge Graph Infrastructure Market"@en ; schema:description "The market for graph-based data infrastructure that models enterprise meaning as traversable relationship networks — including RDF triplestores, labeled property graphs, semantic data fabrics, and webby graph platforms."@en ; schema:naics "541511" ; schema:identifier "https://www.census.gov/naics/?input=541511&year=2022&details=541511" ; schema:isPartOf :industryVerticalsSection . :semanticDataInfrastructureMarket a :DataArchitectureVertical ; schema:name "Semantic Data Infrastructure Market"@en ; schema:description "The market for platforms that combine neural and symbolic AI with governed enterprise data — spanning ontology management, semantic layers, data catalogs, and operational truth systems that preserve meaning as the business runs."@en ; schema:naics "541512" ; schema:identifier "https://www.census.gov/naics/?input=541512&year=2022&details=541512" ; schema:isPartOf :industryVerticalsSection . :mimirLabs a schema:Organization ; schema:name "Mimir Labs"@en ; schema:description "Company focused on canonical operational semantics — a governed operating layer that preserves meaning as the business runs, providing deterministic state and governed events before intelligence starts reasoning over the network."@en . ############################################################ # Entity Group Sections ############################################################ :conceptsSection a schema:ArticleSection ; schema:name "Key Architecture Concepts"@en ; schema:description "Five theses from Tony Seale's post and the community discussion: Box vs Network, the Neural-Symbolic Loop, the Webby Graph, Structure IS Knowledge, and the Data Integration Elephant."@en ; schema:hasPart :boxVsNetworkThesis, :neuralSymbolicLoop, :webbyGraphThesis, :structureIsKnowledge, :dataIntegrationElephant ; schema:isPartOf :analysis . :commentsSection a schema:ArticleSection ; schema:name "Community Discussion (10 Comments)"@en ; schema:description "Comments from the 36-comment discussion, featuring Kingsley Uyi Idehen's webby graph extension, Jon Cooke's unified semantic KB proposal, Marc A.'s relational defense, and Christopher Gaither's operational truth layer."@en ; schema:hasPart :commentKingsley, :commentTonyFollowUp, :commentJonCooke, :commentMarcA, :commentChristopherGaither, :commentBarbaraMatthews, :commentPaulOudeLuttighuis, :commentAliAzzam, :commentBoLora, :commentIFields ; schema:isPartOf :analysis . :industryVerticalsSection a schema:ArticleSection ; schema:name "Industry Verticals"@en ; schema:description "Market segments impacted by the shift from box-shaped to network-shaped enterprise data architectures."@en ; schema:hasPart :knowledgeGraphMarket, :semanticDataInfrastructureMarket ; schema:isPartOf :analysis . ############################################################ # Glossary — 10 Terms ############################################################ :glossarySection a schema:DefinedTermSet, skos:ConceptScheme ; schema:name "Data Architecture Glossary"@en ; schema:description "Key terminology from Tony Seale's box-vs-network analysis and the community discussion."@en ; schema:hasDefinedTerm :termKnowledgeGraph, :termOntologicalCore, :termNeuralSymbolicLoop, :termWebbyGraph, :termDataWarehouse, :termSemanticLayer, :termDataIntegration, :termGraphDatabase, :termHyperlinkIdentifier, :termOperationalTruth ; schema:isPartOf :analysis . :termKnowledgeGraph a schema:DefinedTerm, skos:Concept ; schema:name "Knowledge Graph"@en ; schema:description "A network-shaped data structure where entities and their relationships form a traversable graph. Unlike box-shaped warehouses optimized for aggregation, knowledge graphs enable agents to follow chains of meaning across domain boundaries."@en ; schema:termCode "knowledge-graph"@en ; schema:isPartOf :glossarySection . :termOntologicalCore a schema:DefinedTerm, skos:Concept ; schema:name "Ontological Core"@en ; schema:description "The accumulated conceptual abstractions that form an organization's model of meaning — every relationship learned, every pattern discovered, encoded as edges in the graph. The most valuable enterprise asset of the AI era, and one that must be owned, not outsourced."@en ; schema:termCode "ontological-core"@en ; schema:isPartOf :glossarySection . :termNeuralSymbolicLoop a schema:DefinedTerm, skos:Concept ; schema:name "Neural-Symbolic Loop"@en ; schema:description "The dual architecture where neural networks (generative, creative) imagine possibilities while data networks (symbolic, grounded) anchor those possibilities to factual reality. The neural network imagines; the data network grounds."@en ; schema:termCode "neural-symbolic-loop"@en ; schema:isPartOf :glossarySection . :termWebbyGraph a schema:DefinedTerm, skos:Concept ; schema:name "Webby Graph"@en ; schema:description "Kingsley Uyi Idehen's term for a knowledge graph where entities and relationships are named using hyperlinks (URIs/IRIs), enabling scalable data access by reference across intranets, extranets, and the Internet — turning data integration from an ETL problem into a web architecture problem."@en ; schema:termCode "webby-graph"@en ; schema:isPartOf :glossarySection . :termDataWarehouse a schema:DefinedTerm, skos:Concept ; schema:name "Data Warehouse (Box Architecture)"@en ; schema:description "A box-shaped data architecture optimized for aggregating the past into reports — rows, columns, and tables designed for BI queries. Effective for its era but the wrong shape for AI agents that follow chains of meaning across domain boundaries."@en ; schema:termCode "data-warehouse"@en ; schema:isPartOf :glossarySection . :termSemanticLayer a schema:DefinedTerm, skos:Concept ; schema:name "Semantic Layer"@en ; schema:description "An abstraction layer that maps business meaning onto underlying data infrastructure — providing a governed model of what data means rather than just where it is stored. Enables agents to reason over relationships rather than querying rows."@en ; schema:termCode "semantic-layer"@en ; schema:isPartOf :glossarySection . :termDataIntegration a schema:DefinedTerm, skos:Concept ; schema:name "Data Integration"@en ; schema:description "The twenty-year-old problem of connecting fractured, siloed, contradictory enterprise data sources into a coherent whole. Pre-AI, 1% coverage was acceptable. AI makes incomplete integration an existential business risk — bad context in produces bad decisions out."@en ; schema:termCode "data-integration"@en ; schema:isPartOf :glossarySection . :termGraphDatabase a schema:DefinedTerm, skos:Concept ; schema:name "Graph Database"@en ; schema:description "A database that stores data as nodes and edges (entities and relationships) rather than rows and columns. Enables traversal queries that follow chains of meaning — the kind of query AI agents need — rather than aggregation queries optimized for BI reporting."@en ; schema:termCode "graph-database"@en ; schema:isPartOf :glossarySection . :termHyperlinkIdentifier a schema:DefinedTerm, skos:Concept ; schema:name "Hyperlink Identifier"@en ; schema:description "A URI/IRI used as a name for an entity or relationship, enabling data access by reference rather than by copy. Foundation of the webby graph — turns identity, authentication, and authorization into web-architecture problems with existing protocol solutions."@en ; schema:termCode "hyperlink-identifier"@en ; schema:isPartOf :glossarySection . :termOperationalTruth a schema:DefinedTerm, skos:Concept ; schema:name "Operational Truth"@en ; schema:description "Christopher Gaither's concept from Mimir Labs: canonical operational semantics, deterministic state, and governed events that preserve meaning as the business runs — a governed operating layer that must exist before intelligence starts reasoning over the network."@en ; schema:termCode "operational-truth"@en ; schema:isPartOf :glossarySection . ############################################################ # FAQ — 12 Questions ############################################################ :faqSection a schema:FAQPage ; schema:name "Frequently Asked Questions"@en ; schema:description "Common questions about the box-to-network architectural shift for enterprise AI."@en ; schema:mainEntity :q1, :q2, :q3, :q4, :q5, :q6, :q7, :q8, :q9, :q10, :q11, :q12 ; schema:isPartOf :analysis . :q1 a schema:Question ; schema:name "Why are data warehouses the wrong shape for AI?"@en ; schema:text "Why are data warehouses the wrong shape for AI?"@en ; schema:acceptedAnswer :a1 ; schema:isPartOf :faqSection . :a1 a schema:Answer ; schema:text "Warehouses are optimized for aggregating the past into reports — rows, columns, and tables designed for BI queries. AI agents don't ask for reports; they follow chains of meaning across products, customers, risks, and policies — crossing boundaries the warehouse was designed to keep apart. A box cannot hold a chain."@en ; schema:isPartOf :faqSection . :q2 a schema:Question ; schema:name "What does 'the structure IS the knowledge' mean?"@en ; schema:text "What does 'the structure IS the knowledge' mean?"@en ; schema:acceptedAnswer :a2 ; schema:isPartOf :faqSection . :a2 a schema:Answer ; schema:text "In a knowledge graph, every relationship a business learns — what a good customer looks like, why a deal failed — becomes a new edge in the graph. The accumulated connections form the ontological core of the organization. This structure encodes institutional knowledge that cannot be captured in rows and columns alone. It is the most valuable enterprise asset of the AI era."@en ; schema:isPartOf :faqSection . :q3 a schema:Question ; schema:name "What is the neural-symbolic loop?"@en ; schema:text "What is the neural-symbolic loop?"@en ; schema:acceptedAnswer :a3 ; schema:isPartOf :faqSection . :a3 a schema:Answer ; schema:text "The neural-symbolic loop pairs two complementary capabilities: neural networks (LLMs, generative AI) that imagine possibilities, and data networks (knowledge graphs, semantic models) that ground those possibilities in factual reality. Everyone has the neural half — frontier models are commodities. The competitive advantage comes from the symbolic half: a connected model of your own reality that intelligence can stand on."@en ; schema:isPartOf :faqSection . :q4 a schema:Question ; schema:name "What is a 'webby graph'?"@en ; schema:text "What is a 'webby graph'?"@en ; schema:acceptedAnswer :a4 ; schema:isPartOf :faqSection . :a4 a schema:Answer ; schema:text "Kingsley Uyi Idehen's term for a knowledge graph where entities and relationships are named using hyperlinks (URIs). Unlike networks that only connect entities of the same type, graphs have no such limitation. The 'webby' part enables scalable data access by reference across intranets, extranets, and the Internet — turning data integration from an ETL/copy problem into a web architecture/reference problem."@en ; schema:isPartOf :faqSection . :q5 a schema:Question ; schema:name "Why must the ontological core be owned, not outsourced?"@en ; schema:text "Why must the ontological core be owned, not outsourced?"@en ; schema:acceptedAnswer :a5 ; schema:isPartOf :faqSection . :a5 a schema:Answer ; schema:text "Because the model of your meaning IS your competitive moat. Every relationship your business learns is proprietary intelligence. If a third party holds the model of your meaning, you've outsourced the one asset that differentiates you. The intelligence (LLM) can be rented — frontier models are commodities available to everyone. The structure (your knowledge graph) has to be owned."@en ; schema:isPartOf :faqSection . :q6 a schema:Question ; schema:name "Can relational databases model networks?"@en ; schema:text "Can relational databases model networks?"@en ; schema:acceptedAnswer :a6 ; schema:isPartOf :faqSection . :a6 a schema:Answer ; schema:text "Technically yes — relational databases have modeled relationships for decades through foreign keys, join tables, and recursive queries. But as Marc A. noted in the discussion, the real issue is that most enterprise data models were optimized for reporting and aggregation, not for traversing meaning, provenance, and context. The important asset is the governed model of meaning, not the database shape."@en ; schema:isPartOf :faqSection . :q7 a schema:Question ; schema:name "How does AI expose the data integration problem?"@en ; schema:text "How does AI expose the data integration problem?"@en ; schema:acceptedAnswer :a7 ; schema:isPartOf :faqSection . :a7 a schema:Answer ; schema:text "Pre-AI, getting 1% of your data estate into a warehouse was considered success. AI makes this impossible to keep ignoring because fractured, siloed, contradictory data produces wrong answers regardless of model quality. The best model on the market, pointed at bad context, will reason flawlessly to the wrong conclusion. AI didn't create the data integration problem — it made the cost of ignoring it existential."@en ; schema:isPartOf :faqSection . :q8 a schema:Question ; schema:name "What is the relationship between ontologies and knowledge graphs?"@en ; schema:text "What is the relationship between ontologies and knowledge graphs?"@en ; schema:acceptedAnswer :a8 ; schema:isPartOf :faqSection . :a8 a schema:Answer ; schema:text "An ontology defines the conceptual abstractions — the categories, properties, and rules that structure meaning. A knowledge graph instantiates those abstractions with actual data — real entities and relationships. Together they form the ontological core: the ontology provides the schema of meaning, the graph provides the connected facts. Seale argues this accumulated core is the most valuable enterprise asset of the decade."@en ; schema:isPartOf :faqSection . :q9 a schema:Question ; schema:name "What role do hyperlinks play in data architecture?"@en ; schema:text "What role do hyperlinks play in data architecture?"@en ; schema:acceptedAnswer :a9 ; schema:isPartOf :faqSection . :a9 a schema:Answer ; schema:text "Hyperlinks (URIs) serve as standardized, globally unique identifiers for entities and relationships. When entities are named with hyperlinks, data access becomes access-by-reference rather than access-by-copy — the same architectural pattern that made the World Wide Web scalable. This simplifies identity, authentication, authorization, and data space management because these become web-architecture problems with existing protocol solutions."@en ; schema:isPartOf :faqSection . :q10 a schema:Question ; schema:name "What is operational truth and why does it matter?"@en ; schema:text "What is operational truth and why does it matter?"@en ; schema:acceptedAnswer :a10 ; schema:isPartOf :faqSection . :a10 a schema:Answer ; schema:text "Christopher Gaither's concept: canonical operational semantics that preserve meaning as the business runs. A knowledge graph that only describes reality after the fact is insufficient — the network needs a governed operating layer that captures deterministic state and governed events in real time, before intelligence starts reasoning. Without operational truth, the graph becomes a more expressive map of the same drift."@en ; schema:isPartOf :faqSection . :q11 a schema:Question ; schema:name "Why is BI built for a box but AI needs a network?"@en ; schema:text "Why is BI built for a box but AI needs a network?"@en ; schema:acceptedAnswer :a11 ; schema:isPartOf :faqSection . :a11 a schema:Answer ; schema:text "BI answers known questions about the past: 'What were Q3 sales by region?' This is an aggregation problem that fits neatly into rows, columns, and tables. AI agents ask open-ended questions about relationships: 'What relates to what?' They follow chains of meaning across products, customers, risks, and policies — crossing boundaries that the warehouse kept apart. A box cannot hold a chain. Intelligence is network-shaped."@en ; schema:isPartOf :faqSection . :q12 a schema:Question ; schema:name "How should enterprises prepare their data for AI?"@en ; schema:text "How should enterprises prepare their data for AI?"@en ; schema:acceptedAnswer :a12 ; schema:isPartOf :faqSection . :a12 a schema:Answer ; schema:text "Four steps: (1) Connect the data across silos — the 1%-in-a-warehouse baseline is now a liability. (2) Model the meaning — build the ontological core that encodes what your data means in relationship to everything else. (3) Keep it yours — own your model of meaning, don't outsource it to a vendor's proprietary schema. (4) Make it webby — use hyperlink-based identifiers so data is accessible by reference across systems, turning integration from an ETL problem into a web architecture problem."@en ; schema:isPartOf :faqSection . ############################################################ # HowTo — 7 Steps ############################################################ :howtoSection a schema:HowTo ; schema:name "How to Shift from Box-Shaped to Network-Shaped Data Architecture"@en ; schema:description "A seven-step guide based on Tony Seale's analysis and community discussion."@en ; schema:step :step1, :step2, :step3, :step4, :step5, :step6, :step7 ; schema:isPartOf :analysis . :step1 a schema:HowToStep ; schema:position 1 ; schema:name "Acknowledge the data integration elephant"@en ; schema:text "Confront the twenty-year backlog. Pre-AI, 1% data coverage was acceptable. Point the best model at fractured data and it will reason to the wrong answer. Bad context in = bad decisions out. Make data integration a board-level priority — not an IT backlog item."@en ; schema:isPartOf :howtoSection . :step2 a schema:HowToStep ; schema:position 2 ; schema:name "Model meaning as a graph, not a warehouse"@en ; schema:text "Move beyond rows and columns. Build a knowledge graph where entities and their relationships form a traversable network. Agents need paths — customer to contract to risk to policy — not just aggregated reports. The structure IS the knowledge."@en ; schema:isPartOf :howtoSection . :step3 a schema:HowToStep ; schema:position 3 ; schema:name "Build the ontological core"@en ; schema:text "Accumulate conceptual abstractions as edges in the graph. Every relationship learned — what a good customer looks like, why a deal failed — becomes part of the ontological core. This is proprietary intelligence. Treat it as the most valuable asset you'll build this decade."@en ; schema:isPartOf :howtoSection . :step4 a schema:HowToStep ; schema:position 4 ; schema:name "Own your model of meaning"@en ; schema:text "Do not hand your ontological core to a third party. The intelligence (LLM) can be rented — frontier models are commodities. The structure must be owned. If a vendor holds the model of your meaning, you have outsourced your moat."@en ; schema:isPartOf :howtoSection . :step5 a schema:HowToStep ; schema:position 5 ; schema:name "Make it webby — use hyperlink identifiers"@en ; schema:text "Name entities and relationships using hyperlinks (URIs). This enables data access by reference across intranets, extranets, and the Internet. Turns identity, authentication, and authorization into web-architecture problems with existing protocol solutions."@en ; schema:isPartOf :howtoSection . :step6 a schema:HowToStep ; schema:position 6 ; schema:name "Deploy the neural-symbolic loop"@en ; schema:text "Pair neural networks (generative AI) with your data network (knowledge graph). The neural network imagines; the data network grounds. Both halves are necessary — the model without the graph hallucinates; the graph without the model cannot reason."@en ; schema:isPartOf :howtoSection . :step7 a schema:HowToStep ; schema:position 7 ; schema:name "Layer operational truth beneath the network"@en ; schema:text "A graph that only describes reality after the fact is insufficient. Build a governed operating layer that captures canonical operational semantics in real time. The data network must preserve meaning as the business runs — not just document it afterward."@en ; schema:isPartOf :howtoSection . ############################################################ # Country ############################################################ :unitedStates a schema:Country ; schema:name "United States"@en ; schema:identifier "US" ; owl:sameAs , . ############################################################ # Skill Provenance ############################################################ a schema:SoftwareApplication ; schema:name "kg-generator skill"@en ; schema:url "https://github.com/OpenLinkSoftware/ai-agent-skills/tree/main/kg-generator" ; schema:description "AI agent skill that generates comprehensive RDF-Turtle Knowledge Graphs from web content using curated prompt templates, schema.org vocabulary, and lightweight ontology design."@en .