@prefix : . @prefix schema: . @prefix rdfs: . @prefix rdf: . @prefix owl: . @prefix skos: . @prefix xsd: . @prefix prov: . @prefix dbr: . @prefix ce: . @prefix karp: . @prefix rip: . @prefix lsm: . # ============================================================ # ONTOLOGY # ============================================================ : a owl:Ontology ; schema:name "Seale's Law Vocabulary Erosion Ontology"@en ; schema:description "Lightweight ontology modeling Tony Seale's 'Seale's Law' thesis (word precision decays as commercial value rises), its prescribed two-phase semantic-foundation framework, and a set of corroborating cases drawn from four independently authored companion documents that each show a different technology term undergoing the identical dilution the thesis predicts."@en ; schema:identifier "https://www.linkedin.com/posts/tonyseale_every-technology-wave-eats-its-own-vocabulary-share-7485764156680343553-_B5Z/"^^xsd:anyURI ; rdfs:label "Seale's Law Vocabulary Erosion Ontology"@en ; rdfs:comment "Local TBox for this document; distinct from the :analysis CreativeWork it describes."@en . :SemanticFoundationPractice a rdfs:Class ; rdfs:label "Semantic Foundation Practice"@en ; rdfs:comment "One of the four ordered, imperative practices the post prescribes for building an AI-ready semantic foundation."@en ; rdfs:isDefinedBy : . :addressesPhase a rdf:Property ; rdfs:label "addresses phase"@en ; rdfs:comment "The phase (Internal Coherence or Interoperability) a given practice belongs to."@en ; rdfs:domain :SemanticFoundationPractice ; rdfs:range xsd:string ; rdfs:isDefinedBy : . :SealesLawCorroboration a rdfs:Class ; rdfs:label "Seale's Law Corroboration"@en ; rdfs:comment "A case, drawn from an independently authored companion document in this corpus, in which a specific technology term is shown undergoing the dilution Seale's Law predicts, alongside that document's own corrective mechanism."@en ; rdfs:isDefinedBy : . :dilutedTerm a rdf:Property ; rdfs:label "diluted term"@en ; rdfs:comment "The specific technology term the corroborating document shows losing precision as it gains commercial/marketing value."@en ; rdfs:domain :SealesLawCorroboration ; rdfs:range xsd:string ; rdfs:isDefinedBy : . :correctiveMechanism a rdf:Property ; rdfs:label "corrective mechanism"@en ; rdfs:comment "The open-standards-based mechanism the corroborating document proposes to restore precision to the diluted term."@en ; rdfs:domain :SealesLawCorroboration ; rdfs:range xsd:string ; rdfs:isDefinedBy : . # ============================================================ # MAIN COLLECTION DOCUMENT # ============================================================ :collection a schema:CreativeWork ; schema:name "Seale's Law: Vocabulary Erosion, Meshed With a Four-Document Corroboration Set"@en ; schema:abstract "Tony Seale's LinkedIn post proposes Seale's Law: word precision is inversely proportional to commercial value as a marketing term, and 'semantics' is now the word undergoing it. This collection reproduces the post and its comment thread verbatim, then meshes the thesis against four independently authored companion documents, each of which shows a different AI-era term (context, ontology, System of Intelligence, trust boundary) undergoing the identical dilution — and each of which independently prescribes the same corrective: open-standards Linked Data infrastructure."@en ; schema:hasPart :faqSection, :glossarySection, :howtoSection, :thesisSection, :argumentSection, :meshSection, :referenceLinksSection, : ; schema:author ; schema:accountablePerson ; prov:wasGeneratedBy , . :faqSection schema:isPartOf :collection . :glossarySection schema:isPartOf :collection . :howtoSection schema:isPartOf :collection . :thesisSection schema:isPartOf :collection . :argumentSection schema:isPartOf :collection . :meshSection schema:isPartOf :collection . :referenceLinksSection schema:isPartOf :collection . : schema:isPartOf :collection . a schema:SoftwareApplication ; schema:name "kg-generator skill"@en ; schema:url ; schema:description "Generates RDF Knowledge Graphs from web content using curated prompt templates."@en . a schema:SoftwareApplication ; schema:name "rdf-infographic-skill"@en ; schema:url ; schema:description "Generates interactive HTML infographics and Markdown companions from RDF Knowledge Graphs."@en . # ============================================================ # PEOPLE # ============================================================ a schema:Person ; schema:name "Tony Seale"@en ; schema:url ; schema:identifier "https://uk.linkedin.com/in/tonyseale"^^xsd:anyURI . a schema:Person ; schema:name "Kingsley Uyi Idehen"@en ; schema:url ; schema:identifier "https://www.linkedin.com/in/kidehen"^^xsd:anyURI . a schema:Person ; schema:name "Arnaldo Sepulveda"@en ; schema:url ; schema:identifier "https://ca.linkedin.com/in/arnaldosepulveda"^^xsd:anyURI . a schema:Person ; schema:name "Oliver Cronk"@en ; schema:url ; schema:identifier "https://uk.linkedin.com/in/cronky"^^xsd:anyURI . a schema:Person ; schema:name "Michael Bucknell"@en ; schema:url ; schema:identifier "https://au.linkedin.com/in/mickbucknell"^^xsd:anyURI . a schema:Person ; schema:name "Andrea Splendiani"@en ; schema:url ; schema:identifier "https://ch.linkedin.com/in/andreasplendiani"^^xsd:anyURI . a schema:Person ; schema:name "Stéphane Mader"@en ; schema:url ; schema:identifier "https://fr.linkedin.com/in/stephane-mader"^^xsd:anyURI . a schema:Person ; schema:name "Andi Willmott"@en ; schema:url ; schema:identifier "https://uk.linkedin.com/in/andi-willmott-330457"^^xsd:anyURI . a schema:Person ; schema:name "Gregory Halliday"@en ; schema:url . a schema:Person ; schema:name "Jérôme CHIBOUT"@en ; schema:url . a schema:Organization ; schema:name "Architect Tomorrow"@en ; schema:url . # ============================================================ # THE POST # ============================================================ :post a schema:SocialMediaPosting ; schema:headline "Every technology wave eats its own vocabulary"@en ; schema:author ; schema:datePublished "2026-08-07"^^xsd:date ; schema:url ; schema:text """Every technology wave eats its own vocabulary. Words start sharp. Then the market discovers them. “Cloud.” “Platform.” “Transformation.” “AI.” At first, each points at something real. Then it becomes useful in a sales deck. Then it becomes useful in every sales deck. The word survives. The meaning does not. So here is Seale's Law: ⚡ The precision of a word's meaning is inversely proportional to its commercial value as a marketing term ⚡ It is a joke - but only just. The painful irony is that this is now happening to semantics. For years, those of us working with ontologies and knowledge graphs have made a fairly unfashionable argument: meaning matters. Context matters. Data is not ready for machines simply because it has been loaded into a warehouse, lakehouse, dashboard or API. When concepts remain implicit, identities are inconsistent and business meaning is trapped inside departmental dialects, the system may appear integrated. It is not. AI has made that impossible to ignore. LLMs have exposed a truth that many analytics programmes could postpone: enterprise data is not connected enough, described clearly enough or governed around meaning well enough for intelligent systems to use it safely. AI does not simply need more data. It needs data with identity, relationships, context and explicit business meaning. That is good news. It is also dangerous. 🔵 “Semantics” is about to become a beautiful container for vague promises. The word will be attached to products, features, copilots, roadmaps and platforms. Some of it will be real. Much of it will be rebranding. Organisations moving quickly will be sold noise at precisely the moment they need clarity. The message is simpler than the market will make it. 🔵 Every organisation has a data integration problem. To solve it for AI, you must connect your data and organise that connected data through an ontology: an explicit model of the things your organisation cares about, what they mean and how they relate. That is phase one: internal coherence. 🔵 Phase two is arriving fast: interoperability. No organisation operates alone. Supply chains, regulators, partners, customers, research networks and financial systems all cross organisational boundaries. If AI is going to work across those boundaries, meaning has to travel too. That requires open standards. Not proprietary semantic theatre. Not another silo with “ontology” printed on the brochure. Open standards for identity, connectivity and shared models of meaning. Semantics is having its moment. Our task is to protect the substance before the market hollows out the word. Your AI strategy is only as strong as your semantic foundation. Connect the data. Model the meaning. Use open standards. Prepare for interoperability. And if Seale's Law is right, do it before we need a new word for the thing that finally made the old one profitable. 🔗 Building your semantic foundation? Let's talk: https://lnkd.in/ezHU2amU"""@en ; schema:interactionStatistic :postLikes, :postComments ; schema:isPartOf :collection . :collection schema:about :post . :postLikes a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount 93 . :postComments a schema:InteractionCounter ; schema:interactionType schema:CommentAction ; schema:userInteractionCount 8 . # ============================================================ # COMMENT THREAD (7 of 8 comments visible without sign-in; sequential order) # ============================================================ :comment1 a schema:Comment ; schema:author ; schema:parentItem :post ; schema:position 1 ; schema:text """Exactly. Prompt engineering is not a security boundary. The boundary is the platform: identity, policy, retrieval scope, tool authorization, observability, and audit. The interesting question is not whether an LLM can be attacked, because it can. The question is whether the surrounding system can detect drift, constrain authority, prove provenance, and fail closed when the operating conditions change. That's the problem I'm working on with governed agentic systems."""@en ; schema:interactionStatistic :comment1Likes . :comment1Likes a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount 1 . :comment2 a schema:Comment ; schema:author ; schema:parentItem :post ; schema:position 2 ; schema:text """Yep! Prepare for interoperability at Internet and Web scale as follows: - **Connect the data** — use hyperlinks as identifiers. - **Model the meaning** — describe things using machine-computable sentences built from terms in shared and/or homegrown ontologies. - **Use open standards** — use standards such as RDF for machine-computable statements and ontology construction. Basically, good old **Linked Data principles** manifesting a **Semantic Web** — a natural complement to the natural-language processing capabilities that Large Language Models (a.k.a. Langulators) have recently added to computing's UI/UX stack. No more silos. Silos are extremely stubborn and often well disguised by marketing communications that blur or appropriate terminology as a survival strategy. Adopt Linked Data principles and you get the magic of the Web at an even more powerful level: data, information, and knowledge providing a critical context layer that AI agents can access, interpret, reuse, and share by reference. There's no better foundation for this on the planet. ** posted deliberately using markdown! ** #Ontology #ContextLayer #SemanticLayer #SemanticWeb #LinkedData"""@en ; rdfs:comment "Kingsley Idehen's comment restates the post's own three-part imperative (Connect the data / Model the meaning / Use open standards) explicitly as Linked Data principles manifesting a Semantic Web, names the specific mechanism (hyperlinks as identifiers, RDF, shared/homegrown ontologies) the post leaves implicit, and adds the observation — echoed independently across all four meshed companion documents — that marketing communications 'blur or appropriate terminology as a survival strategy,' i.e. Seale's Law describing silo behavior itself."@en ; schema:about dbr:Linked_data, dbr:Semantic_Web, dbr:Resource_Description_Framework ; schema:interactionStatistic :comment2Likes . :comment2Likes a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount 2 . :comment3 a schema:Comment ; schema:author ; schema:parentItem :post ; schema:position 3 ; schema:text "We have an episode of Architect Tomorrow coming that is aligned to what you are saying here - talking about how ontology is falling into the marketing bucket. Aiming to publish it next month."@en ; schema:mentions ; schema:interactionStatistic :comment3Likes . :comment3Likes a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount 1 . :comment4 a schema:Comment ; schema:author ; schema:parentItem :post ; schema:position 4 ; schema:text "Love this image Tony Seale"@en ; schema:mentions ; schema:interactionStatistic :comment4Likes . :comment4Likes a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount 1 . :comment5 a schema:Comment ; schema:author ; schema:parentItem :post ; schema:position 5 ; schema:text """Totally agree, but any advise on how to \"protect the meaning\"? We already see \"ontologies\" mentioned everywhere, without people even thinking at the idea of connecting data..."""@en ; rdfs:comment "Andrea Splendiani's objection is itself a live, real-time instance of Seale's Law acting on the word 'ontology': the term is already in wide circulation detached from its substance (connecting data), independently corroborated by the :ontologiesBackCorroboration case in this collection's mesh section."@en ; schema:interactionStatistic :comment5Likes . :comment5Likes a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount 1 . :comment6 a schema:Comment ; schema:author ; schema:parentItem :post ; schema:position 6 ; schema:text "Gregory Halliday Jérôme CHIBOUT"@en ; schema:mentions , . :comment7 a schema:Comment ; schema:author ; schema:parentItem :post ; schema:position 7 ; schema:text """Totally agree. What happens when a controlled vocabulary contents start to mean differing things to differing teams due to overuse, reuse or reinterpretation. Remember when 'lean working' had one meaning - not now…🙄"""@en ; schema:interactionStatistic :comment7Likes . :comment7Likes a schema:InteractionCounter ; schema:interactionType schema:LikeAction ; schema:userInteractionCount 1 . :post schema:comment :comment1, :comment2, :comment3, :comment4, :comment5, :comment6, :comment7 . :kidehenPerspectiveSection a schema:CreativeWork ; schema:name "Kingsley Idehen's Perspective on the Seale's Law Thread"@en ; schema:about :comment2 ; schema:hasPart :comment2 ; schema:isPartOf :collection ; rdfs:comment "Distinct callout: of the eight commenters, Kingsley Idehen (:comment2) is the one who names the concrete mechanism the post leaves abstract — hyperlinks as identifiers, RDF, shared/homegrown ontologies, Linked Data principles, Semantic Web — and is also the accountable person for this collection's curation and its mesh with four of his own previously published companion documents."@en . :comment2 schema:isPartOf :kidehenPerspectiveSection . # ============================================================ # THESIS SECTION # ============================================================ :thesisSection a schema:CreativeWork ; schema:name "Thesis: Seale's Law"@en ; schema:text "Word precision decays as commercial value rises; 'semantics' is now the word undergoing that decay, at precisely the moment AI systems need genuine semantic foundations — connected data, explicit ontologies, and open standards — rather than marketing theatre wearing the word's clothing."@en ; schema:mainEntity :sealesLaw ; schema:hasPart :phaseOneInternalCoherence, :phaseTwoInteroperability . :sealesLaw a schema:CreativeWork ; schema:name "Seale's Law"@en ; schema:text "The precision of a word's meaning is inversely proportional to its commercial value as a marketing term."@en ; schema:creator ; schema:isPartOf :thesisSection . :vocabularyErosionPattern a schema:DefinedTerm ; schema:name "Vocabulary Erosion"@en ; schema:description "The pattern Seale's Law formalizes: a technology term ('Cloud', 'Platform', 'Transformation', 'AI', and now 'semantics') points at something real, becomes useful in a sales deck, then survives as a word while its meaning does not."@en ; schema:isPartOf :glossarySection . :phaseOneInternalCoherence a :SemanticFoundationPractice ; schema:position 1 ; schema:name "Phase One: Internal Coherence"@en ; schema:description "Connect an organisation's data and organise that connected data through an explicit ontology — a model of the things the organisation cares about, what they mean, and how they relate."@en ; :addressesPhase "Internal Coherence"@en ; schema:isPartOf :thesisSection . :phaseTwoInteroperability a :SemanticFoundationPractice ; schema:position 2 ; schema:name "Phase Two: Interoperability"@en ; schema:description "Because no organisation operates alone — supply chains, regulators, partners, customers, research networks and financial systems all cross organisational boundaries — meaning must travel across those boundaries too, which requires open standards rather than proprietary semantic theatre."@en ; :addressesPhase "Interoperability"@en ; schema:isPartOf :thesisSection . # ============================================================ # ARGUMENT SECTION (analytical restructuring, not verbatim repeat) # ============================================================ :argumentSection a schema:ItemList ; schema:name "The Post's Argument, Restructured"@en ; schema:itemListElement :vocabularyErosionObservation, :sealesLaw, :semanticsUndergoingDilution, :aiNeedsGenuineSemantics, :phaseOneInternalCoherence, :phaseTwoInteroperability, :protectSubstanceImperative . :vocabularyErosionObservation a schema:CreativeWork ; schema:position 1 ; schema:name "Observation"@en ; schema:text "Every technology wave eats its own vocabulary — 'Cloud', 'Platform', 'Transformation', 'AI' each pointed at something real before becoming sales-deck filler; the word survives, the meaning does not."@en ; schema:isPartOf :argumentSection . :semanticsUndergoingDilution a schema:CreativeWork ; schema:position 3 ; schema:name "Current Instance"@en ; schema:text "'Semantics' is now undergoing the identical process: it will be attached to products, features, copilots, roadmaps and platforms — some real, much of it rebranding — precisely when organisations most need clarity."@en ; schema:isPartOf :argumentSection . :aiNeedsGenuineSemantics a schema:CreativeWork ; schema:position 4 ; schema:name "The Stakes"@en ; schema:text "LLMs have exposed that enterprise data is not connected, described, or governed around meaning well enough for intelligent systems to use safely — AI needs data with identity, relationships, context and explicit business meaning, not just more data."@en ; schema:isPartOf :argumentSection . :protectSubstanceImperative a schema:CreativeWork ; schema:position 7 ; schema:name "Closing Imperative"@en ; schema:text "Semantics is having its moment; the task is to protect the substance before the market hollows out the word — do it before a new word is needed for the thing that finally made the old one profitable."@en ; schema:isPartOf :argumentSection . # ============================================================ # MESH SECTION — four corroborating companion documents # ============================================================ :meshSection a schema:CreativeWork ; schema:name "Corroboration: Four Independent Documents, Four Diluted Terms, One Corrective"@en ; schema:text "Each of these four documents was authored independently of Tony Seale's post, about a different named term, yet each traces the exact pattern Seale's Law predicts: a real technical concept, adopted commercially, hollowed into marketing language — and each document's own corrective is the same one Seale prescribes and Kingsley Idehen names in the thread: open standards, Linked Data, explicit ontology."@en ; schema:hasPart :contextEngineCorroboration, :ontologiesBackCorroboration, :karpCorroboration, :reverseParadoxCorroboration ; schema:author ; schema:accountablePerson ; prov:wasGeneratedBy . :contextEngineCorroboration a :SealesLawCorroboration ; schema:position 1 ; schema:name "Case 1 — \"Context\" as a Proprietary Container"@en ; :dilutedTerm "Context / Context Engine"@en ; :correctiveMechanism "Six loosely-coupled, standards-addressable infrastructure layers — Identity, Identification, Authentication, Authorization, Data Spaces, and Ontology — rather than one vendor's proprietary compounding loop."@en ; schema:citation ; schema:about ce:ontologyLayer, ce:identityLayer, ce:pluggableContextQuality, ce:deterministicReasoning ; rdfs:seeAlso ; schema:isPartOf :meshSection . :ontologiesBackCorroboration a :SealesLawCorroboration ; schema:position 2 ; schema:name "Case 2 — \"Ontology\" Mentioned Everywhere, Connected to Nothing"@en ; :dilutedTerm "Ontology"@en ; :correctiveMechanism "Ontologies re-adopted as genuine, queryable, dereferenceable logical guardrails for agent loops — the neurosymbolic-AI convergence of LLM language fluency with RDFS/OWL structure — rather than a brochure word."@en ; schema:citation ; schema:about lsm:thinAgents, lsm:loopEngineering, dbr:Neurosymbolic_AI ; rdfs:seeAlso ; schema:isPartOf :meshSection ; rdfs:comment "This document itself opens by noting AI engineers are rediscovering ontologies as guardrails — Andrea Splendiani's comment on the Seale post ('we already see ontologies mentioned everywhere, without people even thinking at the idea of connecting data') is the same warning stated as a live objection under the post it is meshed with here."@en . :karpCorroboration a :SealesLawCorroboration ; schema:position 3 ; schema:name "Case 3 — Vendor-Owned Ontologies Recreate the Lock-In They Claim to Solve"@en ; :dilutedTerm "System of Intelligence / Ontology (vendor-branded)"@en ; :correctiveMechanism "An enterprise-owned Knowledge Graph built on Linked Data principles and HTTP, queryable via SPARQL by any model — instead of a closed, proprietary graph (Palantir Ontology, Databricks Unity Catalog) recreating the walled-garden dynamic one layer down the stack."@en ; schema:citation ; schema:about karp:systemOfIntelligence, karp:dataCommunism, karp:critique2OntologyLockIn, karp:critique3LinkedDataAlternative ; rdfs:seeAlso ; schema:isPartOf :meshSection . :reverseParadoxCorroboration a :SealesLawCorroboration ; schema:position 4 ; schema:name "Case 4 — A \"Trust Boundary\" That Still Needs a Representational Substrate"@en ; :dilutedTerm "Trust Boundary"@en ; :correctiveMechanism "The five-pillar trust boundary (Control, Capability, Choice, Cost, Compound) framed as needing new legal instruments is, per the critical perspective, already achievable today via loose coupling over HTTP, an enterprise knowledge graph, and attribute-based access control — no new word or new law required, only the open standards Seale's post prescribes."@en ; schema:citation ; schema:about rip:reverseInformationParadox, rip:trustBoundary, rip:intelligenceExhaust, rip:controlPillar, rip:capabilityPillar, rip:choicePillar, rip:costPillar, rip:compoundPillar ; rdfs:seeAlso ; schema:isPartOf :meshSection . # ============================================================ # REFERENCE LINKS # ============================================================ :referenceLinksSection a schema:ItemList ; schema:name "Reference Links"@en ; schema:itemListElement :refPost, :refContextEngine, :refOntologiesBack, :refKarp, :refReverseParadox, :refSealeProfile, :refBuildingFoundationLink . :refPost a schema:CreativeWork ; schema:position 1 ; schema:name "Original LinkedIn post"@en ; schema:url ; schema:isPartOf :referenceLinksSection . :refContextEngine a schema:CreativeWork ; schema:position 2 ; schema:name "Context Engine vs. Context Infrastructure"@en ; schema:url ; schema:isPartOf :referenceLinksSection . :refOntologiesBack a schema:CreativeWork ; schema:position 3 ; schema:name "Ontologies Are So Back — Meshed With the agent-rdf-memory Corpus"@en ; schema:url ; schema:isPartOf :referenceLinksSection . :refKarp a schema:CreativeWork ; schema:position 4 ; schema:name "Alex Karp, Frontier Models and the Real Fight for Enterprise AI"@en ; schema:url ; schema:isPartOf :referenceLinksSection . :refReverseParadox a schema:CreativeWork ; schema:position 5 ; schema:name "The Reverse Information Paradox"@en ; schema:url ; schema:isPartOf :referenceLinksSection . :refSealeProfile a schema:CreativeWork ; schema:position 6 ; schema:name "Tony Seale — LinkedIn profile"@en ; schema:url ; schema:isPartOf :referenceLinksSection . :refBuildingFoundationLink a schema:CreativeWork ; schema:position 7 ; schema:name "\"Building your semantic foundation? Let's talk.\" (post's own CTA link)"@en ; schema:url ; schema:isPartOf :referenceLinksSection . # ============================================================ # FAQ # ============================================================ :faqSection a schema:FAQPage ; schema:mainEntity :q1, :q2, :q3, :q4, :q5, :q6, :q7, :q8, :q9, :q10, :q11, :q12, :q13, :q14, :q15 . :q1 a schema:Question ; schema:isPartOf :faqSection ; schema:name "What is Seale's Law?"@en ; schema:acceptedAnswer :a1 . :a1 a schema:Answer ; schema:text "Tony Seale's formulation: 'The precision of a word's meaning is inversely proportional to its commercial value as a marketing term.' As a term becomes profitable to say in a sales deck, its precise meaning erodes even as the word itself keeps circulating."@en . :q2 a schema:Question ; schema:isPartOf :faqSection ; schema:name "What does 'every technology wave eats its own vocabulary' mean?"@en ; schema:acceptedAnswer :a2 . :a2 a schema:Answer ; schema:text "Terms like 'Cloud', 'Platform', 'Transformation' and 'AI' each started by pointing at something real, then became useful in every sales deck; the word survived while the precise meaning did not."@en . :q3 a schema:Question ; schema:isPartOf :faqSection ; schema:name "What is happening to the word 'semantics' specifically?"@en ; schema:acceptedAnswer :a3 . :a3 a schema:Answer ; schema:text "It is about to become 'a beautiful container for vague promises' — attached to products, features, copilots, roadmaps and platforms, some real and much of it rebranding, right as organisations need clarity most."@en . :q4 a schema:Question ; schema:isPartOf :faqSection ; schema:name "What two-phase framework does the post prescribe?"@en ; schema:acceptedAnswer :a4 . :a4 a schema:Answer ; schema:text "Phase One is internal coherence: connect your data and organise it through an explicit ontology. Phase Two is interoperability: because no organisation operates alone, meaning must travel across organisational boundaries too, which requires open standards."@en . :q5 a schema:Question ; schema:isPartOf :faqSection ; schema:name "What is Phase One, 'internal coherence'?"@en ; schema:acceptedAnswer :a5 . :a5 a schema:Answer ; schema:text "Connecting an organisation's data and organising that connected data through an ontology — an explicit model of the things the organisation cares about, what they mean, and how they relate."@en . :q6 a schema:Question ; schema:isPartOf :faqSection ; schema:name "What is Phase Two, 'interoperability'?"@en ; schema:acceptedAnswer :a6 . :a6 a schema:Answer ; schema:text "Because supply chains, regulators, partners, customers, research networks and financial systems all cross organisational boundaries, AI working across those boundaries requires meaning to travel too — via open standards, not proprietary semantic theatre."@en . :q7 a schema:Question ; schema:isPartOf :faqSection ; schema:name "What did Kingsley Idehen say in response to the post?"@en ; schema:acceptedAnswer :a7 . :a7 a schema:Answer ; schema:text "He restated the post's three-part imperative concretely: connect the data using hyperlinks as identifiers, model the meaning using shared/homegrown ontologies, and use open standards such as RDF — Linked Data principles manifesting a Semantic Web, a natural complement to LLMs' natural-language capabilities."@en . :q8 a schema:Question ; schema:isPartOf :faqSection ; schema:name "What objection did Andrea Splendiani raise?"@en ; schema:acceptedAnswer :a8 . :a8 a schema:Answer ; schema:text "She asked how to 'protect the meaning' in practice, noting that 'ontologies' is already mentioned everywhere without people connecting it to the actual idea of connecting data — a live instance of the same dilution Seale's Law predicts, happening to 'ontology' itself."@en . :q9 a schema:Question ; schema:isPartOf :faqSection ; schema:name "How does the Context Engine vs. Context Infrastructure article corroborate Seale's Law?"@en ; schema:acceptedAnswer :a9 . :a9 a schema:Answer ; schema:text "Sierra's 'Context Engine' brands customer context as a proprietary, vendor-owned moat; the critical-perspective response shows the same compounding value is achievable via six loosely-coupled, standards-addressable layers (identity, authentication, authorization, data spaces, ontology) instead — the diluted term is 'context', the corrective is open infrastructure."@en . :q10 a schema:Question ; schema:isPartOf :faqSection ; schema:name "How does the 'Ontologies Are So Back' mesh article corroborate Seale's Law?"@en ; schema:acceptedAnswer :a10 . :a10 a schema:Answer ; schema:text "It documents AI engineers rediscovering ontologies as guardrails for agentic systems from four independent voices — the exact word ('ontology') Andrea Splendiani flags as already overused in this thread, being restored to substance via neurosymbolic AI and dereferenceable, queryable graphs."@en . :q11 a schema:Question ; schema:isPartOf :faqSection ; schema:name "How does the Karp / Enterprise AI Control-Point article corroborate Seale's Law?"@en ; schema:acceptedAnswer :a11 . :a11 a schema:Answer ; schema:text "Vendor-owned 'System of Intelligence' ontologies (Palantir Ontology, Databricks Unity Catalog) recreate the lock-in they claim to solve — the diluted term is 'ontology' rebranded as a proprietary control point; the corrective is an enterprise-owned Knowledge Graph on Linked Data principles, queryable via SPARQL by any model."@en . :q12 a schema:Question ; schema:isPartOf :faqSection ; schema:name "How does the Reverse Information Paradox article corroborate Seale's Law?"@en ; schema:acceptedAnswer :a12 . :a12 a schema:Answer ; schema:text "Its 'trust boundary' is framed as needing a new legal instrument, patents' functional equivalent; the critical perspective shows the same boundary is already achievable today via open standards — HTTP loose coupling, an enterprise knowledge graph, and attribute-based access control — no new word or law required."@en . :q13 a schema:Question ; schema:isPartOf :faqSection ; schema:name "Why do vendor-owned ontologies also fall under Seale's Law?"@en ; schema:acceptedAnswer :a13 . :a13 a schema:Answer ; schema:text "Because a closed, proprietary graph 'printed on the brochure' as an ontology is exactly the 'proprietary semantic theatre' the post warns against — the word 'ontology' retains commercial value as a feature name while losing the openness that gave the underlying concept its original precision."@en . :q14 a schema:Question ; schema:isPartOf :faqSection ; schema:name "What open standards does the post (and the meshed corpus) recommend?"@en ; schema:acceptedAnswer :a14 . :a14 a schema:Answer ; schema:text "RDF and RDFS/OWL for machine-computable statements and ontology construction, HTTP-addressable hyperlinks as identifiers, and SPARQL for querying — Linked Data principles manifesting a Semantic Web, per Kingsley Idehen's comment and all four meshed companion documents."@en . :q15 a schema:Question ; schema:isPartOf :faqSection ; schema:name "What is the practical takeaway of the post?"@en ; schema:acceptedAnswer :a15 . :a15 a schema:Answer ; schema:text "Connect the data, model the meaning, use open standards, prepare for interoperability — and do it before the market hollows out 'semantics' the way it already hollowed out 'Cloud', 'Platform', 'Transformation' and 'AI'."@en . # ============================================================ # GLOSSARY # ============================================================ :glossarySection a schema:DefinedTermSet ; schema:hasDefinedTerm :sealesLawTerm, :vocabularyErosionPattern, :semanticCoherenceTerm, :internalCoherenceTerm, :interoperabilityTerm, , dbr:Linked_data, dbr:Semantic_Web, dbr:Resource_Description_Framework, ce:ontologyLayer, karp:systemOfIntelligence, rip:trustBoundary, dbr:Neurosymbolic_AI . :sealesLawTerm a schema:DefinedTerm ; owl:sameAs :sealesLaw ; schema:name "Seale's Law"@en ; schema:description "Tony Seale's coined principle: a word's meaning-precision is inversely proportional to its commercial value as a marketing term."@en ; schema:isPartOf :glossarySection . :semanticCoherenceTerm a schema:DefinedTerm ; schema:name "Semantic Coherence"@en ; schema:description "The state in which an organisation's concepts are explicit, identities are consistent, and business meaning is not trapped inside departmental dialects."@en ; schema:isPartOf :glossarySection . :internalCoherenceTerm a schema:DefinedTerm ; owl:sameAs :phaseOneInternalCoherence ; schema:name "Internal Coherence (Phase One)"@en ; schema:description "Connecting an organisation's data and organising it through an explicit ontology."@en ; schema:isPartOf :glossarySection . :interoperabilityTerm a schema:DefinedTerm ; owl:sameAs :phaseTwoInteroperability ; schema:name "Interoperability (Phase Two)"@en ; schema:description "The requirement that meaning travel across organisational boundaries via open standards, since no organisation operates alone."@en ; schema:isPartOf :glossarySection . schema:isPartOf :glossarySection ; rdfs:comment "An explicit model of the things an organisation cares about, what they mean, and how they relate — reused here from DBpedia as the term Seale's post and all four meshed documents treat as central."@en . dbr:Linked_data schema:isPartOf :glossarySection ; rdfs:comment "Using hyperlinks as identifiers to connect data across organisational and system boundaries — Kingsley Idehen's named mechanism for Phase One."@en . dbr:Semantic_Web schema:isPartOf :glossarySection ; rdfs:comment "The open, standards-based vision Linked Data principles manifest; named directly in Kingsley Idehen's comment on this post."@en . dbr:Resource_Description_Framework schema:isPartOf :glossarySection ; rdfs:comment "The open standard for machine-computable statements and ontology construction that Kingsley Idehen's comment names as the concrete Phase Two mechanism."@en . ce:ontologyLayer schema:isPartOf :glossarySection ; rdfs:comment "Reused from the Context Engine vs. Context Infrastructure companion document: the layer enabling deterministic reasoning via RDFS/OWL, one of the six loosely-coupled infrastructure layers proposed as the antidote to a proprietary 'Context Engine'."@en . karp:systemOfIntelligence schema:isPartOf :glossarySection ; rdfs:comment "Reused from the Karp/theCUBE companion document: the governed layer of business rules, policies, processes and tacit knowledge that vendor-branded ontologies claim, and often fail, to hold openly."@en . rip:trustBoundary schema:isPartOf :glossarySection ; rdfs:comment "Reused from the Reverse Information Paradox companion document: a hard boundary across which nothing crosses without consent — argued achievable today via the same open standards Seale's post prescribes."@en . dbr:Neurosymbolic_AI schema:isPartOf :glossarySection ; rdfs:comment "Reused from the Ontologies Are So Back mesh companion document: the fusion of probabilistic LLM agents with symbolic ontology systems that restores substance to the word 'ontology'."@en . # ============================================================ # HOWTO — the post's own four imperative steps # ============================================================ :howtoSection a schema:HowTo ; schema:name "How to Build a Semantic Foundation Before the Word Is Hollowed Out"@en ; schema:step :step1, :step2, :step3, :step4 . :step1 a schema:HowToStep ; schema:position 1 ; schema:isPartOf :howtoSection ; schema:name "Connect the data"@en ; schema:text "Use hyperlinks as identifiers to connect data across systems and departments, per Kingsley Idehen's comment — the concrete first move of Phase One."@en . :step2 a schema:HowToStep ; schema:position 2 ; schema:isPartOf :howtoSection ; schema:name "Model the meaning"@en ; schema:text "Organise the connected data through an explicit ontology — a model of the things the organisation cares about, what they mean, and how they relate — using shared and/or homegrown ontologies expressed as machine-computable sentences."@en . :step3 a schema:HowToStep ; schema:position 3 ; schema:isPartOf :howtoSection ; schema:name "Use open standards"@en ; schema:text "Adopt open standards such as RDF for machine-computable statements and ontology construction, instead of proprietary semantic theatre or another silo with 'ontology' printed on the brochure."@en . :step4 a schema:HowToStep ; schema:position 4 ; schema:isPartOf :howtoSection ; schema:name "Prepare for interoperability"@en ; schema:text "Because supply chains, regulators, partners, customers, research networks and financial systems all cross organisational boundaries, ensure meaning can travel across those boundaries too — Phase Two, arriving fast."@en .