@base . @prefix : . @prefix source: . @prefix schema: . @prefix xsd: . @prefix rdf: . @prefix rdfs: . @prefix owl: . @prefix skos: . @prefix prov: . <> a schema:CreativeWork ; schema:name "Sierra Context Engine Linked Data Context Deck RDF"@en ; schema:description """RDF source of truth for a comparative deck about Sierra's Context Engine thesis and an alternative thesis: context is infrastructure enabled by Linked Data principles, loose coupling, identity-aware access, and pluggable data spaces."""@en ; schema:dateCreated "2026-08-05T00:00:00Z"^^xsd:dateTime ; schema:dateModified "2026-08-05T00:00:00Z"^^xsd:dateTime ; schema:author ; schema:about :deck . :deck a schema:PresentationDigitalDocument ; schema:name "Context Is Infrastructure: A Linked Data Alternative to App-Siloed Context"@en ; schema:headline "Context Is Infrastructure"@en ; schema:abstract """The deck argues that the durable advantage in agentic software is not app-contained memory alone, but the quality of pluggable context built from HTTP IRIs, RDF, ontologies, deterministic inference, provenance, identity-aware authorization, and linked data spaces. It uses agent-rdf-memory and the Virtuoso Support Skill as concrete demonstrations of the alternative approach."""@en ; schema:isBasedOn source:article ; schema:creator ; schema:publisher ; schema:hasPart :slide-01-thesis, :slide-02-sierra-position, :slide-03-loose-coupling, :slide-04-linked-data-context, :slide-05-context-sources, :slide-06-quality-frontier, :slide-07-ontology-reasoning, :slide-08-sparql-solution-pipeline, :slide-07-agent-rdf-memory, :slide-08-virtuoso-support-skill, :slide-07-comparison, :slide-08-close, :glossary, :faq, :comparison-set, :howto, :kg-explorer-model ; schema:about :context-infrastructure, :semantic-web, :linked-data, :ontology, :deterministic-inference, :pluggable-context, :agent-rdf-memory, :support-resolution-context ; prov:wasGeneratedBy , . source:article a schema:BlogPosting ; schema:name "Rent the intelligence, own the relationship"@en ; schema:url ; schema:datePublished "2026-08-04"^^xsd:date ; schema:author source:karthik-thiyagarajan ; schema:publisher ; schema:about , , :customer-relationship-context . source:karthik-thiyagarajan a schema:Person ; schema:name "Karthik Thiyagarajan"@en ; schema:url . a schema:Organization ; schema:name "Sierra"@en ; schema:url . a schema:SoftwareApplication ; schema:name "Context Engine"@en ; schema:url ; schema:description "Sierra product concept presented as turning customer relationship context into a competitive advantage for long-running agents."@en . a schema:SoftwareApplication ; schema:name "Horizon agents"@en ; schema:url ; schema:description "Sierra long-horizon agents described as pursuing outcomes over days, weeks, or months."@en . a schema:SoftwareApplication ; schema:name "agent-rdf-memory"@en ; schema:url ; schema:applicationCategory "RDF memory substrate"@en ; schema:description """Working prior-art demonstration of context as loosely coupled RDF infrastructure: core identity, operational preferences, rule-linked HowTo documents, session indexes, and session memory are stored as named resources that can be retrieved through SPARQL or direct RDF reads."""@en ; schema:hasPart , , . a schema:CreativeWork ; schema:name "core.ttl"@en ; schema:description "RDF document that identifies the operator, agent connection, and output routing context."@en . a schema:CreativeWork ; schema:name "preferences.ttl"@en ; schema:description "RDF operational-rule manifest that links preferences to specific HowTo documents."@en . a schema:CreativeWork ; schema:name "index.ttl"@en ; schema:description "RDF session-discovery index that makes prior sessions addressable context."@en . a schema:SoftwareApplication ; schema:name "Virtuoso Support Skill"@en ; schema:url ; schema:applicationCategory "Technical support agent skill"@en ; schema:description """Concrete support-resolution example for a Linked Data context layer: it scopes the target Virtuoso instance, uses server-prefixed tools, resolves schema and entity context, applies predefined query templates, runs audits, generates RDF Views and ontology/data rules, and verifies outcomes with SPARQL."""@en ; schema:supports :support-resolution-context . :support-resolution-context a schema:DefinedTerm, skos:Concept ; schema:name "Support resolution context"@en ; schema:description """The linked evidence required to resolve a support case: chosen instance, tool namespace, schema metadata, entity discovery, query templates, generated RDF Views, audit results, scripts, and validation queries."""@en ; schema:relatedLink . :ontology a schema:DefinedTerm, skos:Concept ; schema:name "Ontology"@en ; schema:description """A Linked Data vocabulary of classes, properties, constraints, and relationships that gives context entities shared meaning and enables deterministic reasoning."""@en ; schema:relatedLink , , . :deterministic-inference a schema:DefinedTerm, skos:Concept ; schema:name "Deterministic inference"@en ; schema:description """Repeatable derivation of new facts from explicit RDF statements and ontology rules, such as class subsumption, property entailments, validation failures, and policy-relevant conclusions."""@en ; schema:isPartOf :context-infrastructure . :sparql-solution-production a schema:DefinedTerm, skos:Concept ; schema:name "SPARQL solution production"@en ; schema:description """The query-evaluation pipeline that produces SPARQL variable bindings. In a reasoning-aware engine, solution production can exploit explicit RDF statements plus ontology-driven inferred statements."""@en ; schema:isPartOf :context-infrastructure ; schema:about :deterministic-inference, . :spasql a schema:DefinedTerm, skos:Concept ; schema:name "SPASQL"@en ; schema:description """SPARQL used within SQL, enabling SQL-oriented workflows to invoke RDF graph queries and consume graph-derived solutions."""@en ; schema:about , . :gql-mapping a schema:DefinedTerm, skos:Concept ; schema:name "GQL mapping"@en ; schema:description """A Virtuoso-oriented graph-query bridge where RDF and Linked Data context can be mapped into GQL-oriented graph-query usage."""@en ; schema:about :context-infrastructure . a schema:SoftwareSourceCode ; schema:name "SPARQL"@en ; schema:description "RDF graph query language used to produce bindings over explicit and inferred graph facts."@en . a schema:SoftwareSourceCode ; schema:name "SQL"@en ; schema:description "Relational query language that can participate in graph workflows through SPASQL in Virtuoso-oriented settings."@en . a schema:SoftwareSourceCode ; schema:name "GQL"@en ; schema:description "Graph Query Language referenced here as a graph-query surface that can be mapped to when Virtuoso is the engine of choice."@en . a schema:SoftwareSourceCode ; schema:name "OWL"@en ; schema:url ; schema:description "Web Ontology Language used to express rich ontologies for RDF data."@en . a schema:SoftwareSourceCode ; schema:name "RDFS"@en ; schema:url ; schema:description "RDF Schema vocabulary used for basic classes, properties, domains, ranges, and subclass relations."@en . a schema:SoftwareSourceCode ; schema:name "SHACL"@en ; schema:url ; schema:description "Shapes Constraint Language used to validate RDF graphs against structural and semantic constraints."@en . :rdf-views-workflow a schema:HowTo ; schema:name "RDF Views support-resolution workflow"@en ; schema:description "Virtuoso Support Skill workflow for turning relational data into Linked Data context with audits and SPARQL validation."@en ; schema:step :step-confirm-instance, :step-discover-schema, :step-generate-rdf-views, :step-run-audits, :step-validate-graph . :step-confirm-instance a schema:HowToStep ; schema:position "1"^^xsd:integer ; schema:name "Confirm target instance"@en ; schema:text """Select Demo, URIBurner, or Localhost before any support operation."""@en ; schema:isPartOf :rdf-views-workflow . :step-discover-schema a schema:HowToStep ; schema:position "2"^^xsd:integer ; schema:name "Discover schema and entities"@en ; schema:text """Use schema metadata and entity-discovery tools before assuming data shape."""@en ; schema:isPartOf :rdf-views-workflow . :step-generate-rdf-views a schema:HowToStep ; schema:position "3"^^xsd:integer ; schema:name "Generate RDF Views and ontology"@en ; schema:text """Use high-level RDF Views tools to generate mappings, ontology, and data rules."""@en ; schema:isPartOf :rdf-views-workflow . :step-run-audits a schema:HowToStep ; schema:position "4"^^xsd:integer ; schema:name "Run pre- and post-audits"@en ; schema:text """Audit metadata health before and after generated scripts are executed."""@en ; schema:isPartOf :rdf-views-workflow . :step-validate-graph a schema:HowToStep ; schema:position "5"^^xsd:integer ; schema:name "Validate with SPARQL"@en ; schema:text """Verify quad maps and sample entities using SPARQL queries."""@en ; schema:isPartOf :rdf-views-workflow . :slide-01-thesis a schema:CreativeWork ; schema:position "1"^^xsd:integer ; schema:name "Context Belongs To Infrastructure"@en ; schema:headline "Alternative thesis"@en ; schema:text """If foundation-model intelligence is rentable, durable advantage comes from pluggable context infrastructure: named entities, linked relationships, identity-aware access, and reusable data spaces that remain independent of any one application."""@en ; schema:about :customer-relationship-context ; schema:isPartOf :deck . :slide-02-sierra-position a schema:CreativeWork ; schema:position "2"^^xsd:integer ; schema:name "Sierra's Position"@en ; schema:headline "Rent intelligence, own relationships"@en ; schema:text """Sierra argues that enterprises can rent model intelligence, while the unique record of customer relationships, decisions, observations, and outcomes becomes the defensible moat."""@en ; schema:about :customer-relationship-context ; schema:isPartOf :deck . :slide-03-loose-coupling a schema:CreativeWork ; schema:position "3"^^xsd:integer ; schema:name "The Loose-Coupling Gap"@en ; schema:headline "Where the thesis changes"@en ; schema:text """The strongest version of the context thesis separates context from the app. Identity, identification, authentication, authorization, and source data can be independently governed while still being joined by HTTP IRIs and RDF relationships."""@en ; schema:about :context-infrastructure ; schema:isPartOf :deck . :slide-04-linked-data-context a schema:CreativeWork ; schema:position "4"^^xsd:integer ; schema:name "Linked Data Turns Context Into Addressable Infrastructure"@en ; schema:headline "URIs, HTTP, RDF, links"@en ; schema:text """Linked Data principles make each entity and relationship addressable. A customer, policy, claim, file, table row, API operation, decision, and outcome can carry its own resolvable identity and provenance."""@en ; schema:about :context-infrastructure ; schema:isPartOf :deck . :slide-05-context-sources a schema:CreativeWork ; schema:position "5"^^xsd:integer ; schema:name "Sources Of Truth Stay Pluggable"@en ; schema:headline "Databases, knowledge bases, filesystems, APIs"@en ; schema:text """A Semantic Web context layer does not require one universal database. It lets multiple data spaces remain sources of truth while agents consume a linked, policy-aware view over them."""@en ; schema:about :context-infrastructure ; schema:isPartOf :deck . :slide-06-quality-frontier a schema:CreativeWork ; schema:position "6"^^xsd:integer ; schema:name "The New Quality Frontier"@en ; schema:headline "Pluggability beats hoarding"@en ; schema:text """The differentiator shifts from who owns the largest app-contained memory to who can deliver the best governed, interoperable, current, and explainable context to many agents and tools."""@en ; schema:about :context-infrastructure ; schema:isPartOf :deck . :slide-07-ontology-reasoning a schema:CreativeWork ; schema:position "7"^^xsd:integer ; schema:name "Ontologies Make Context Reasonable"@en ; schema:headline "Deterministic inference layer"@en ; schema:text """Linked Data names and connects things; ontologies define what those things mean. Classes, properties, domains, ranges, constraints, and inference rules let agents derive repeatable conclusions from context instead of improvising every join in prompt space."""@en ; schema:about :context-infrastructure ; schema:isPartOf :deck . :slide-08-sparql-solution-pipeline a schema:CreativeWork ; schema:position "8"^^xsd:integer ; schema:name "SPARQL Surfaces Inferred Solutions"@en ; schema:headline "Reasoning in the query pipeline"@en ; schema:text """Reasoning and inference are exploitable inside SPARQL query solution production. A query can return solutions based on explicit triples plus ontology-driven entailments produced in the engine pipeline, so the answer reflects governed semantics rather than only stored assertions."""@en ; schema:about :context-infrastructure ; schema:isPartOf :deck . :slide-07-agent-rdf-memory a schema:CreativeWork ; schema:position "9"^^xsd:integer ; schema:name "agent-rdf-memory Is The Demonstration"@en ; schema:headline "Prior work as evidence"@en ; schema:text """The agent-rdf-memory system already demonstrates the alternative approach: operational context is encoded as RDF documents, indexed by session, routed through HowTo rules, and retrievable by SPARQL or direct RDF reads without depending on a single app memory silo."""@en ; schema:about :context-infrastructure ; schema:isPartOf :deck . :slide-08-virtuoso-support-skill a schema:CreativeWork ; schema:position "10"^^xsd:integer ; schema:name "Virtuoso Support Skill Shows Resolution Context"@en ; schema:headline "Support cases as linked operations"@en ; schema:text """The Virtuoso Support Skill shows why support resolution needs pluggable context. Instance selection, tool namespaces, query templates, RDF Views generation, audits, SPARQL validation, SQL/SPASQL execution, and GQL-oriented mappings become reusable resolution state rather than a private exchange inside a chat UI."""@en ; schema:about :context-infrastructure ; schema:isPartOf :deck . :slide-07-comparison a schema:CreativeWork ; schema:position "11"^^xsd:integer ; schema:name "App Context vs Semantic Web Context"@en ; schema:headline "Comparative frame"@en ; schema:text """Sierra's Context Engine is an application-platform answer to compounding customer context. A Linked Data answer turns context into a cross-application infrastructure layer."""@en ; schema:about :context-infrastructure ; schema:isPartOf :deck . :slide-08-close a schema:CreativeWork ; schema:position "12"^^xsd:integer ; schema:name "Context Is The Interface Contract"@en ; schema:headline "A decision architecture for agents"@en ; schema:text """Agents should plug into context the way browsers plug into Web pages: through resolvable identifiers, typed relationships, content negotiation, and access controls. Applications can innovate above that layer without trapping the context beneath it."""@en ; schema:about :context-infrastructure ; schema:isPartOf :deck . :glossary a schema:DefinedTermSet ; schema:name "Context Infrastructure Glossary"@en ; schema:hasDefinedTerm :semantic-web, :linked-data, :context-infrastructure, :data-space, :webid, :pluggable-context, :ontology, :deterministic-inference, :sparql-solution-production, :spasql, :gql-mapping, :agent-rdf-memory, :support-resolution-context ; schema:isPartOf :deck . :semantic-web a schema:DefinedTerm, skos:Concept ; schema:name "A Semantic Web"@en ; schema:description """A deployment of Linked Data principles where entities and relationships are identified by resolvable IRIs and described using RDF."""@en ; schema:inDefinedTermSet :glossary . :linked-data a schema:DefinedTerm, skos:Concept ; schema:name "Linked Data"@en ; schema:description """A practice of publishing structured data with HTTP IRIs, useful descriptions, and links to other named things."""@en ; schema:inDefinedTermSet :glossary . :context-infrastructure a schema:DefinedTerm, skos:Concept ; schema:name "Context infrastructure"@en ; schema:description """A shared semantic layer that presents identity-aware, policy-aware, provenance-bearing context independent of one application."""@en ; schema:inDefinedTermSet :glossary . :data-space a schema:DefinedTerm, skos:Concept ; schema:name "Data space"@en ; schema:description """A source of truth such as a database, knowledge base, filesystem, or API that can expose or participate in linked descriptions."""@en ; schema:inDefinedTermSet :glossary . :webid a schema:DefinedTerm, skos:Concept ; schema:name "WebID"@en ; schema:description """An HTTP IRI that identifies an agent, person, or organization and can connect identity to authentication and authorization workflows."""@en ; schema:inDefinedTermSet :glossary . :pluggable-context a schema:DefinedTerm, skos:Concept ; schema:name "Pluggable context"@en ; schema:description """Context that can be joined, governed, and reused across agents because it is expressed through standards and resolvable identifiers."""@en ; schema:inDefinedTermSet :glossary . :ontology a schema:DefinedTerm, skos:Concept ; schema:name "Ontology"@en ; schema:description """A Linked Data vocabulary of classes, properties, constraints, and relationships that defines the meaning of context entities."""@en ; schema:inDefinedTermSet :glossary . :deterministic-inference a schema:DefinedTerm, skos:Concept ; schema:name "Deterministic inference"@en ; schema:description """Repeatable derivation of new facts from explicit RDF statements and ontology rules, rather than probabilistic reconstruction in a prompt."""@en ; schema:inDefinedTermSet :glossary . :sparql-solution-production a schema:DefinedTerm, skos:Concept ; schema:name "SPARQL solution production"@en ; schema:description """The pipeline that evaluates graph patterns and returns variable bindings, potentially over asserted and inferred RDF statements."""@en ; schema:inDefinedTermSet :glossary . :spasql a schema:DefinedTerm, skos:Concept ; schema:name "SPASQL"@en ; schema:description """Use of SPARQL from SQL, allowing relational workflows to invoke graph queries and consume RDF-derived solutions."""@en ; schema:inDefinedTermSet :glossary . :gql-mapping a schema:DefinedTerm, skos:Concept ; schema:name "GQL mapping"@en ; schema:description """A graph-query access path in which Virtuoso can map Linked Data and RDF graph context into GQL-oriented graph-query usage."""@en ; schema:inDefinedTermSet :glossary . :agent-rdf-memory a schema:DefinedTerm, skos:Concept ; schema:name "agent-rdf-memory"@en ; schema:description """A working RDF memory substrate that stores agent identity, preferences, HowTo rules, session logs, and provenance as queryable Linked Data."""@en ; schema:inDefinedTermSet :glossary . :support-resolution-context a schema:DefinedTerm, skos:Concept ; schema:name "Support resolution context"@en ; schema:description """The evidence, tool choices, audits, queries, instance selection, and validation steps needed to resolve a technical support case."""@en ; schema:inDefinedTermSet :glossary . :faq a schema:FAQPage ; schema:name "Comparative Context FAQ"@en ; schema:mainEntity :q1, :q2, :q3, :q4, :q5, :q6, :q7, :q8, :q9 ; schema:isPartOf :deck . :q1 a schema:Question ; schema:name "What is the core alternative thesis?"@en ; schema:acceptedAnswer :a1 ; schema:isPartOf :faq . :a1 a schema:Answer ; schema:text """Context should be treated as infrastructure built from Linked Data and identity-aware access, not as a private memory feature of one application platform."""@en ; schema:isPartOf :faq . :q2 a schema:Question ; schema:name "How does this differ from Sierra's Context Engine thesis?"@en ; schema:acceptedAnswer :a2 ; schema:isPartOf :faq . :a2 a schema:Answer ; schema:text """Sierra emphasizes owned customer relationship context inside a long-running agent platform. The alternative emphasizes interoperable context that many authorized applications can discover and reuse."""@en ; schema:isPartOf :faq . :q3 a schema:Question ; schema:name "Why does loose coupling matter?"@en ; schema:acceptedAnswer :a3 ; schema:isPartOf :faq . :a3 a schema:Answer ; schema:text """Loose coupling lets identity, authentication, authorization, and data spaces evolve independently while still participating in one linked context fabric."""@en ; schema:isPartOf :faq . :q4 a schema:Question ; schema:name "What becomes the competitive differentiator?"@en ; schema:acceptedAnswer :a4 ; schema:isPartOf :faq . :a4 a schema:Answer ; schema:text """The quality of pluggable context: provenance, freshness, semantic precision, policy fidelity, and the reach of links across trustworthy sources."""@en ; schema:isPartOf :faq . :q5 a schema:Question ; schema:name "What role do ontologies play?"@en ; schema:acceptedAnswer :a5 ; schema:isPartOf :faq . :a5 a schema:Answer ; schema:text """Ontologies provide the shared vocabulary and formal relationship model that lets context be interpreted deterministically. They allow agents and reasoners to infer classes, relationships, constraints, and policy-relevant facts from Linked Data."""@en ; schema:isPartOf :faq . :q6 a schema:Question ; schema:name "How does SPARQL exploit reasoning and inference?"@en ; schema:acceptedAnswer :a6 ; schema:isPartOf :faq . :a6 a schema:Answer ; schema:text """SPARQL query solutions can be produced over explicit triples and inferred facts. Ontology-driven entailments can change which variable bindings satisfy a graph pattern, making reasoning part of the solution-production pipeline."""@en ; schema:isPartOf :faq . :q7 a schema:Question ; schema:name "How do SQL/SPASQL and GQL fit the thesis?"@en ; schema:acceptedAnswer :a7 ; schema:isPartOf :faq . :a7 a schema:Answer ; schema:text """When Virtuoso is the engine of choice, SPARQL is not isolated from other query surfaces. It can be used from SQL through SPASQL and mapped into GQL-oriented graph-query access, allowing the same context infrastructure to serve relational, RDF, and graph-query consumers."""@en ; schema:isPartOf :faq . :q8 a schema:Question ; schema:name "How does agent-rdf-memory demonstrate the alternative thesis?"@en ; schema:acceptedAnswer :a8 ; schema:isPartOf :faq . :a8 a schema:Answer ; schema:text """It externalizes operational memory into RDF files such as core.ttl, preferences.ttl, index.ttl, and sessions/*.ttl. That makes context inspectable, linkable, portable, and queryable beyond the current application session."""@en ; schema:isPartOf :faq . :q9 a schema:Question ; schema:name "Why does the Virtuoso Support Skill matter?"@en ; schema:acceptedAnswer :a9 ; schema:isPartOf :faq . :a9 a schema:Answer ; schema:text """It treats support resolution as a structured, tool-mediated, auditable context workflow: select the target instance, use predefined templates first, retrieve schema and entity context, generate or validate RDF Views, and confirm outcomes with SPARQL."""@en ; schema:isPartOf :faq . :comparison-set a schema:CreativeWork ; schema:name "Comparative Thesis Set"@en ; schema:hasPart :comparison-platform-context, :comparison-linked-context, :comparison-moat, :comparison-agent-access, :comparison-ontology-proof, :comparison-query-proof, :comparison-memory-proof, :comparison-support-proof ; schema:isPartOf :deck . :comparison-platform-context a schema:CreativeWork ; schema:name "Application-contained context"@en ; schema:description """Context is accumulated and optimized primarily inside one product or platform boundary."""@en ; schema:isPartOf :comparison-set . :comparison-linked-context a schema:CreativeWork ; schema:name "Linked Data context"@en ; schema:description """Context is expressed as resolvable, typed relationships across independently governed data spaces."""@en ; schema:isPartOf :comparison-set . :comparison-moat a schema:CreativeWork ; schema:name "Moat"@en ; schema:description """The platform view emphasizes exclusive accumulated observations. The Linked Data view emphasizes reusable context quality, provenance, and policy-aware interoperability."""@en ; schema:isPartOf :comparison-set . :comparison-agent-access a schema:CreativeWork ; schema:name "Agent access"@en ; schema:description """Agents should retrieve relevant context through resolvable identifiers and authorization policies rather than through platform-specific memory alone."""@en ; schema:isPartOf :comparison-set . :comparison-ontology-proof a schema:CreativeWork ; schema:name "Ontology proof"@en ; schema:description """Ontologies make Linked Data context deterministic enough for inference, validation, and policy-sensitive support workflows."""@en ; schema:isPartOf :comparison-set . :comparison-query-proof a schema:CreativeWork ; schema:name "Query proof"@en ; schema:description """SPARQL query solutions can reflect reasoning and inference, while Virtuoso lets those graph solutions participate through SQL/SPASQL and GQL-oriented graph-query access."""@en ; schema:isPartOf :comparison-set . :comparison-memory-proof a schema:CreativeWork ; schema:name "Operational memory proof"@en ; schema:description """agent-rdf-memory shows context as durable RDF and SPARQL-addressable memory rather than hidden transcript state."""@en ; schema:isPartOf :comparison-set . :comparison-support-proof a schema:CreativeWork ; schema:name "Support resolution proof"@en ; schema:description """The Virtuoso Support Skill shows a case-resolution workflow in which tools, queries, audits, graph validation, and chosen data spaces are explicit context."""@en ; schema:isPartOf :comparison-set . :howto a schema:HowTo ; schema:name "How to implement context as Linked Data infrastructure"@en ; schema:step :step-name-entities, :step-expose-sources, :step-bind-identity, :step-apply-policy, :step-measure-quality ; schema:isPartOf :deck . :step-name-entities a schema:HowToStep ; schema:position "1"^^xsd:integer ; schema:name "Name entities"@en ; schema:text """Assign stable HTTP IRIs to customers, accounts, products, claims, files, API operations, decisions, and outcomes."""@en ; schema:isPartOf :howto . :step-expose-sources a schema:HowToStep ; schema:position "2"^^xsd:integer ; schema:name "Expose source descriptions"@en ; schema:text """Publish RDF descriptions or views from each source of truth without forcing all data into one application database."""@en ; schema:isPartOf :howto . :step-bind-identity a schema:HowToStep ; schema:position "3"^^xsd:integer ; schema:name "Bind identity to identifiers"@en ; schema:text """Use Web-scale identity patterns so agents, people, organizations, and services can be identified separately from login mechanisms."""@en ; schema:isPartOf :howto . :step-apply-policy a schema:HowToStep ; schema:position "4"^^xsd:integer ; schema:name "Apply authorization at the context layer"@en ; schema:text """Use policy-aware access to determine which agent can resolve which context in which situation."""@en ; schema:isPartOf :howto . :step-measure-quality a schema:HowToStep ; schema:position "5"^^xsd:integer ; schema:name "Measure pluggable context quality"@en ; schema:text """Track freshness, provenance, link coverage, entity resolution accuracy, and outcome usefulness as first-class metrics."""@en ; schema:isPartOf :howto . :kg-explorer-model a schema:Dataset ; schema:name "Deck knowledge graph explorer model"@en ; schema:description "Compact graph model used by the deck to show the relationships among Sierra's thesis, Linked Data, identity, authorization, and pluggable data spaces."@en ; schema:isPartOf :deck . a schema:SoftwareApplication ; schema:name "kg-generator skill"@en ; schema:url ; schema:description "Skill used to generate RDF Turtle source material for the deck."@en . a schema:SoftwareApplication ; schema:name "rdf-infographic-skill"@en ; schema:url ; schema:description "Skill used to generate the presentation and knowledge graph explorer."@en . a schema:Organization ; schema:name "OpenLink Software"@en .