Concept Ontology
EKGF Editor's Draft
1. Concept Ontology§
1.1 Overview§
Concept Ontology
| Identifier | Value |
|---|---|
| Ontology IRI / Namespace | https://ekgf.org/ontology/concept# |
| Prefix | ekg-concept |
Every organization describes the same things in many ways. A form says
"Customer ID", a spreadsheet has a cust_no column, an API takes
customerId, a query uses ?customer, and an ontology defines a Customer
class. The reverse also happens: one word means different things in different
departments. Without an explicit record of what each of these means, and where
it appears, nobody can tell whether two systems talk about the same thing.
The Concept Ontology gives each meaning its own identity: the data element concept (DEC), or data element for short. A DEC is a logical data element with all its various forms of physical manifestations and their sightings.
Despite its name, a DEC is not a skos:Concept. A skos:Concept is an entry
in a taxonomy or thesaurus. Such an entry can be one of a data element's
manifestations, just like a column or an API parameter.
The Concept Ontology lets an enterprise knowledge graph:
- Preserve business language. Capture terms as the business uses them, not as an external standard names them.
- Connect meaning to every physical form. Link the same data element to its business terms, API parameters, query variables, columns, ontology classes, SHACL shapes and taxonomy entries.
- Keep meaning consistent. Reuse one data element across use cases, stories, languages and systems wherever the meaning is the same.
- Make the semantics explicit. Represent different terms for the same data element, and the same term for different data elements, instead of hiding them.
- Check reality against intent. Compare where a data element was actually found with where stories declare that they use it.
1.1.1 Why this much detail: data lineage§
Maintaining data elements with all their manifestations and all their sightings is a lot of work. Sightings do not record themselves: finding them takes discovery mechanisms, such as harvesters that scan datasets, files, statements and source code.
The reason to do this work is full, detailed data lineage: tracing a piece of data from system to system, for example from a form field through an API parameter and a query variable to the column where it is stored. That trace is only possible with an explicit record of every manifestation and every place where it appears. An organization that needs detailed data lineage needs this level of detail.
1.1.2 Meaning, manifestations and sightings§
| Layer | Resource | Answers |
|---|---|---|
| Meaning | DataElementConcept | What does the data element mean? |
| Manifestation | ConceptManifestation | How is it expressed, as a business term or as one of many kinds of technical term? |
| Sighting | ManifestationOccurrence | Where was each manifestation observed, and in which statement position? |
A data element for a single attribute, such as a customer identifier, works the same way as a data element for a compound construct, such as a whole customer record with an OWL class and a SHACL shape as its manifestations. Data elements have no subtype hierarchy for classes, properties or shapes; their manifestations carry that detail. Matching names alone never establish that two manifestations express the same meaning.
1.1.3 Start with business language§
At the start of a use case, capture what the business calls things and what those things mean in its context. Ontologies are not needed at this stage. The business owns its use cases and should recognize its language throughout their lifecycle. Capturing a data element before its technical manifestations are known is normal.
1.1.4 From capture to ontology mapping§
As the use case matures, map its data elements to technical manifestations:
ontology classes and properties, shapes, taxonomies, API parameters, columns
and code identifiers. A technical manifestation points at the ontology resource
or shape through manifestationResource, or records its exact token through
manifestationValue. Harvesters record where each manifestation appears as
sightings. As understanding grows, adjust data elements to better reflect the
domain, and link them to more appropriate ontology resources.
1.1.5 Reuse across the use case tree§
Data elements are grouped into vocabularies, represented by ConceptSet.
A use case owns its vocabularies through ekg-use-case:ownsConceptSet, and its
stories select data elements from those vocabularies and the ones of its
ancestor use cases. Reuse an existing data element wherever its meaning fits,
even when a new context needs a different name or technical form. Create a
separate data element only for a different meaning. When owners establish that
independently created data elements mean the same thing, they can merge them.
1.1.6 Data elements in stories§
A story declares how it uses a data element through a story-owned usage: an input the caller supplies, an output the story returns, or a dependent data element used internally, such as a join or filter data element. The Story Ontology defines those usages and compares them with the sightings in a story's implementation. A data element used in an implementation but not declared by its story is reported for review.
1.1.7 Relationship to ISO/IEC 11179§
DataElementConcept follows the distinction between meaning and representation
in ISO/IEC 11179-31:2023, section
3.25, where a data element concept combines an object class and a property,
such as Customer and Identifier. This ontology extends that scope to compound
data constructs. That broader scope does not claim formal equivalence to the
ISO model.
The EKG/Method explains how data elements, vocabularies and stories fit into the Use Case Tree Method.
1.1.8 Vocabulary class labels§
Classes in this ontology have English title-case rdfs:label values, such as
Data Element Concept and Business Term. Labels preserve acronyms such as
OWL, RDF, SHACL and SPARQL, and language names such as JavaScript. These labels
name the vocabulary classes. Business-term manifestations supply the names
used for individual data elements in their business languages and contexts.
1.2 Classes§
1.2.1 Abbreviation§
A shortened business term used as a business-language manifestation of a data element concept.
ekg-concept:Abbreviation | |
https://ekgf.org/ontology/concept#Abbreviation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Abbreviation |
rdfs:subClassOf | ekg-concept:BusinessTerm |
1.2.2 Business Term§
A human-facing manifestation such as a preferred label, synonym, or abbreviation.
ekg-concept:BusinessTerm | |
https://ekgf.org/ontology/concept#BusinessTerm | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Business Term |
rdfs:subClassOf | ekg-concept:ConceptManifestation |
1.2.3 Concept Manifestation§
A business or technical expression of a data element concept: a human term, abbreviation, synonym, API parameter, variable name, RDF resource, OWL class, OWL axiom, SHACL shape, SKOS concept, table, column, or source-code identifier. Its appearances in sources are recorded as ManifestationOccurrence instances.
ekg-concept:ConceptManifestation | |
https://ekgf.org/ontology/concept#ConceptManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Concept Manifestation |
1.2.4 Concept Set§
A governed set of related data element concepts.
ekg-concept:ConceptSet | |
https://ekgf.org/ontology/concept#ConceptSet | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Concept Set |
1.2.5 Cypher Identifier Manifestation§
A technical manifestation expressing a data element concept through an identifier in Cypher source or queries. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:CypherIdentifierManifestation | |
https://ekgf.org/ontology/concept#CypherIdentifierManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Cypher Identifier Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.6 Data Element Concept§
A data element concept describes a logical data element in three layers:
| Layer | Resource | Answers |
|---|---|---|
| Meaning | DataElementConcept | What does the data element mean? |
| Manifestation | ConceptManifestation | How is it expressed, as a business term or as one of many kinds of technical term? |
| Sighting | ManifestationOccurrence | Where was each manifestation observed physically, and in which statement position? |
For example, one concept can manifest as the business term "Product category",
as a product_category column in a dataset and as a placeholder in a story's
statement template. Each observed appearance is a separate occurrence:
foundIn identifies the dataset, file, template or story implementation, and
statementPosition records how the appearance is used within a statement.
These sightings are the evidence of how and where the logical data element
manifests physically. The concept keeps its identity when terms are renamed
or new sightings are recorded.
Reuse across stories
For example, a customer-identifier concept can be an input to one story and an output from another. Both stories reference the same data element concept. Each story owns a separate usage object describing how it uses that concept. Requiredness and server provision describe an input usage, rather than the reusable meaning.
Vocabulary membership and ownership
inConceptSet links a concept to its vocabularies. A use case owns a concept
set through ekg-use-case:ownsConceptSet. Stories select concepts from their
use case's own vocabularies and those inherited from ancestor use cases.
Referencing a concept does not give the story ownership of the concept.
Manifestations
A business term, an API name, and a SPARQL variable can express the same
concept in different ways. ConceptManifestation resources record those
expressions, and ManifestationOccurrence resources record their appearances
in sources. A compound concept may also have a whole OWL class or SHACL shape
as a manifestation.
Reuse one manifestation for the same expression of the same concept within
the same language across story implementations; record individual appearances
as occurrences. For
example, twenty statement templates using $m as a placeholder for the same
meaning can reference one TemplateParameterManifestation with label and
manifestationValue "$m". Its appearances in the template sources are
separate occurrences. The manifestation's templateLanguage identifies
the syntax in which that token is a placeholder. Native SPARQL variables use
SPARQLVariableManifestation. SPARQL itself permits dollar-prefixed query
variables, so the template language and the expression's role determine
the distinction; spelling alone does not establish it or shared meaning.
The template processor must use a documented, explicitly supported language profile. For SPARQL value substitution, validated inputs must be serialized as RDF terms for their intended positions, rather than copied as arbitrary query fragments. The rendered statement must be parsed before execution. The generic manifestation class neither selects an engine nor certifies that an engine or its output is safe.
occursWithin links one observed occurrence to another, preserving the context
in which an attribute manifestation appears within a compound manifestation.
The same attribute concept can occur in different compounds in different
sources; containment belongs to the occurrence records, not to the shared
concepts or manifestations. A Story's concept usages declare its contract;
occurrences record observed appearances. Neither side is inferred from the other.
See the occurrence containment guide
for an executable example and the limits of declaration/observation comparisons.
TemplateLanguage identifies the source language/profile, not its renderer
or its generated output language. A template targeting SPARQL is still a
document in the declared template language until rendered. The
SPARQL Story Implementation Ontology
declares template documents, renderers, and their implementation relationships.
Template-placeholder migration
LegraDollarManifestation is retired. Replace that type assertion with
TemplateParameterManifestation and declare the manifestation's documented
templateLanguage profile. Keep the manifestation's identity, token, concept
links, and occurrence references. Do not infer its language from the $
prefix. LegacyTemplateManifestationShape rejects the retired classification
even when the current type and a language are also present.
See the Method's concept-vocabulary documentation.
ekg-concept:DataElementConcept | |
https://ekgf.org/ontology/concept#DataElementConcept | |
| RDF predicate | Value |
dct:created | |
rdf:type | owl:Class |
rdfs:label | Data Element Concept |
rdfs:seeAlso | https://www.iso.org/standard/78925.html |
1.2.7 Description§
A longer human-facing description of a concept — hover text, tooltips, and detail panes.
ekg-concept:Description | |
https://ekgf.org/ontology/concept#Description | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Description |
rdfs:subClassOf | ekg-concept:BusinessTerm |
1.2.8 Full Plural Business Term§
The plural noun form of a concept's business term — what a column header or collection heading shows.
ekg-concept:FullPluralBusinessTerm | |
https://ekgf.org/ontology/concept#FullPluralBusinessTerm | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Full Plural Business Term |
rdfs:subClassOf | ekg-concept:BusinessTerm |
1.2.9 Full Singular Business Term§
A business term expressing the full name of a data element concept in singular form.
ekg-concept:FullSingularBusinessTerm | |
https://ekgf.org/ontology/concept#FullSingularBusinessTerm | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Full Singular Business Term |
rdfs:subClassOf | ekg-concept:BusinessTerm |
1.2.10 JSON Field Manifestation§
A technical manifestation expressing a data element concept through a field in a JSON document or interface. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:JSONFieldManifestation | |
https://ekgf.org/ontology/concept#JSONFieldManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | JSON Field Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.11 Java Identifier Manifestation§
A technical manifestation expressing a data element concept through an identifier in Java source code. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:JavaIdentifierManifestation | |
https://ekgf.org/ontology/concept#JavaIdentifierManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Java Identifier Manifestation |
rdfs:subClassOf | ekg-concept:SourceCodeIdentifierManifestation |
1.2.12 JavaScript Identifier Manifestation§
A technical manifestation expressing a data element concept through an identifier in JavaScript source code. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:JavaScriptIdentifierManifestation | |
https://ekgf.org/ontology/concept#JavaScriptIdentifierManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | JavaScript Identifier Manifestation |
rdfs:subClassOf | ekg-concept:SourceCodeIdentifierManifestation |
1.2.13 Literal Datatype Manifestation§
A technical manifestation expressing a data element concept through a literal datatype. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:LiteralDatatypeManifestation | |
https://ekgf.org/ontology/concept#LiteralDatatypeManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Literal Datatype Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.14 Manifestation Occurrence§
An occurrence records where a manifestation was observed. occurrenceOf
identifies the manifestation. foundIn identifies the artifacts containing the
sighting, such as a dataset, file, statement template or story implementation.
Repository, system, path, commit and line/column metadata locate it further.
Separate appearances of the same manifestation have separate occurrence
records. An occurrence is disjoint from the reusable DataElementConcept and
ConceptManifestation roles.
The manifestation's class records how the concept appears, for example as a
raw source field or a template placeholder. Within a query or update statement,
statementPosition records the role of the appearance: a parameter, a
projected result, a graph-template term or a graph-pattern term.
occursWithin records observed direct containment between occurrences.
Containment is optional, may have several parents, and must be acyclic.
Validate a coherent source/version context. A source analyzer is responsible
for identifying that context and determining the actual structure. Paths and
line/column literals alone do not identify a source artifact or source span;
foundIn links the sighting to resources representing its artifacts.
Observing a manifestation in a shape specification records the specification's appearance. The requirements expressed by that specification remain distinct from observations of the data it constrains. Similarly, a Story's declared input, output and dependent usages remain distinct from observations in an implementation source. Observations never create those declarations. Statement positions identify the usage role a Story analysis expects; the Story Ontology compares that evidence with the declared usages and reports gaps as warnings. See the sightings guide.
ekg-concept:ManifestationOccurrence | |
https://ekgf.org/ontology/concept#ManifestationOccurrence | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Manifestation Occurrence |
owl:disjointWith | ekg-concept:ConceptManifestation |
owl:disjointWith | ekg-concept:DataElementConcept |
1.2.15 OWL Axiom Manifestation§
A technical manifestation expressing a data element concept through an OWL axiom. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:OWLAxiomManifestation | |
https://ekgf.org/ontology/concept#OWLAxiomManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | OWL Axiom Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.16 OWL Class Manifestation§
A technical manifestation expressing a data element concept through an OWL class. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:OWLClassManifestation | |
https://ekgf.org/ontology/concept#OWLClassManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | OWL Class Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.17 OWL Named Individual Manifestation§
A technical manifestation expressing a data element concept through an OWL named individual. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:OWLNamedIndividualManifestation | |
https://ekgf.org/ontology/concept#OWLNamedIndividualManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | OWL Named Individual Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.18 OWL Property Manifestation§
A technical manifestation expressing a data element concept through an OWL property. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:OWLPropertyManifestation | |
https://ekgf.org/ontology/concept#OWLPropertyManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | OWL Property Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.19 Python Identifier Manifestation§
A technical manifestation expressing a data element concept through an identifier in Python source code. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:PythonIdentifierManifestation | |
https://ekgf.org/ontology/concept#PythonIdentifierManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Python Identifier Manifestation |
rdfs:subClassOf | ekg-concept:SourceCodeIdentifierManifestation |
1.2.20 RDF Predicate Manifestation§
A technical manifestation expressing a data element concept through a predicate used in RDF statements. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:RDFPredicateManifestation | |
https://ekgf.org/ontology/concept#RDFPredicateManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | RDF Predicate Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.21 RDFS Class Manifestation§
A technical manifestation expressing a data element concept through an RDFS class. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:RDFSClassManifestation | |
https://ekgf.org/ontology/concept#RDFSClassManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | RDFS Class Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.22 Raw Source Field Manifestation§
A technical manifestation expressing a data element concept through a field in captured raw source data. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:RawSourceFieldManifestation | |
https://ekgf.org/ontology/concept#RawSourceFieldManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Raw Source Field Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.23 SHACL Shape Manifestation§
A technical manifestation expressing a data element concept through a SHACL shape. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:SHACLShapeManifestation | |
https://ekgf.org/ontology/concept#SHACLShapeManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | SHACL Shape Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.24 SHACL Shape Set Manifestation§
A technical manifestation expressing a data element concept through a collection of SHACL shapes. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:SHACLShapeSetManifestation | |
https://ekgf.org/ontology/concept#SHACLShapeSetManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | SHACL Shape Set Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.25 SKOS Concept Manifestation§
A technical manifestation expressing a data element concept through a SKOS concept. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:SKOSConceptManifestation | |
https://ekgf.org/ontology/concept#SKOSConceptManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | SKOS Concept Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.26 SKOS Concept Scheme Manifestation§
A technical manifestation expressing a data element concept through a SKOS concept scheme. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:SKOSConceptSchemeManifestation | |
https://ekgf.org/ontology/concept#SKOSConceptSchemeManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | SKOS Concept Scheme Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.27 SPARQL Result Column Manifestation§
A technical manifestation expressing a data element concept through a column in a SPARQL query result. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:SPARQLResultColumnManifestation | |
https://ekgf.org/ontology/concept#SPARQLResultColumnManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | SPARQL Result Column Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.28 SPARQL Variable Manifestation§
A technical manifestation expressing a data element concept through a variable in a SPARQL statement. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:SPARQLVariableManifestation | |
https://ekgf.org/ontology/concept#SPARQLVariableManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | SPARQL Variable Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.29 SQL Column Manifestation§
A technical manifestation expressing a data element concept through a column in a relational database schema. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:SQLColumnManifestation | |
https://ekgf.org/ontology/concept#SQLColumnManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | SQL Column Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.30 SQL Table Manifestation§
A technical manifestation expressing a data element concept through a table in a relational database schema. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:SQLTableManifestation | |
https://ekgf.org/ontology/concept#SQLTableManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | SQL Table Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.31 Source Code Identifier Manifestation§
An identifier in a programming language, such as a variable, field, function, or class name. Use this class directly for languages without a dedicated subclass. manifestationValue records the exact identifier; ManifestationOccurrence records where it appears.
ekg-concept:SourceCodeIdentifierManifestation | |
https://ekgf.org/ontology/concept#SourceCodeIdentifierManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Source Code Identifier Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.2.32 Statement Position§
The four built-in positions are distinct named individuals. Applications can
define more positions as IRIs with a label and a definition. A position
compared with Story declarations must also identify the usage role it implies
through ekg-story:expectedUsageRole.
The built-ins classify SPARQL query and update positions. They do not yet
classify terms in DELETE templates or DELETE DATA; that usage role remains
an open modeling decision, so analyzers must not record those terms as
GraphTemplatePosition.
ekg-concept:StatementPosition | |
https://ekgf.org/ontology/concept#StatementPosition | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Statement Position |
owl:disjointWith | ekg-concept:ConceptManifestation |
owl:disjointWith | ekg-concept:DataElementConcept |
owl:disjointWith | ekg-concept:ManifestationOccurrence |
1.2.33 Tagline§
A short subtitle or tagline shown beneath a concept's title.
ekg-concept:Tagline | |
https://ekgf.org/ontology/concept#Tagline | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Tagline |
rdfs:subClassOf | ekg-concept:BusinessTerm |
1.2.34 Technical Manifestation§
A machine-facing manifestation such as an API token, query variable, code identifier, RDF resource, schema object, table, or column.
ekg-concept:TechnicalManifestation | |
https://ekgf.org/ontology/concept#TechnicalManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Technical Manifestation |
rdfs:subClassOf | ekg-concept:ConceptManifestation |
1.2.35 Template Language§
A documented template language or substitution profile defining how a template document is interpreted. Its identity is distinct from a renderer implementing it and from the language of the rendered output. Declaring a profile does not approve it for execution.
ekg-concept:TemplateLanguage | |
https://ekgf.org/ontology/concept#TemplateLanguage | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Template Language |
1.2.36 Template Parameter Manifestation§
A concept's appearance as a placeholder in a statement template. A template processor substitutes validated input values before the resulting statement is parsed and executed. The template language determines the token syntax; its spelling alone does not identify a language or a native query variable.
ekg-concept:TemplateParameterManifestation | |
https://ekgf.org/ontology/concept#TemplateParameterManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | Template Parameter Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
rdfs:subClassOf | (rdf:type: owl:Restriction; owl:minCardinality: 1; owl:onProperty: ekg-concept:templateLanguage) |
rdfs:subClassOf | (rdf:type: owl:Restriction; owl:maxCardinality: 1; owl:onProperty: ekg-concept:templateLanguage) |
1.2.37 URI Parameter Manifestation§
A technical manifestation expressing a data element concept through a URI parameter in an interface. The manifestation is distinct from the reusable meaning of the concept and from its occurrences in source files.
ekg-concept:URIParameterManifestation | |
https://ekgf.org/ontology/concept#URIParameterManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:Class |
rdfs:label | URI Parameter Manifestation |
rdfs:subClassOf | ekg-concept:TechnicalManifestation |
1.3 Properties§
1.3.1 concept§
Identifies the data element concept expressed by a concept manifestation; it is the inverse of hasManifestation.
ekg-concept:concept | |
https://ekgf.org/ontology/concept#concept | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:ConceptManifestation |
rdfs:label | concept |
rdfs:range | ekg-concept:DataElementConcept |
owl:inverseOf | ekg-concept:hasManifestation |
1.3.2 found in§
Links an occurrence to each artifact in which it was sighted: a dataset, a
dataset file, a statement template, a story implementation, a raw-data view,
a code file or another identified source artifact. Assert the levels the
harvester has resolved. One sighting in a statement template can be found in
the template, in the story implementation using it, and in the dataset
containing the template's file. Querying foundIn for a dataset then finds
both column sightings and statement sightings, while the manifestation class
and statementPosition distinguish how the concept appears in each.
Values are IRIs or blank nodes representing artifacts. They are not
occurrences, concepts, manifestations or statement positions; containment
between occurrences uses occursWithin. The property is not functional: an
occurrence can be found in several containing artifacts at different
granularities. Paths, lines and columns remain literals locating the sighting
within an artifact. A harvester must resolve artifact identity explicitly;
matching paths do not establish that two sightings share an artifact.
ekg-concept:foundIn | |
https://ekgf.org/ontology/concept#foundIn | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:ManifestationOccurrence |
rdfs:label | found in |
rdfs:range | rdfs:Resource |
1.3.3 has concept§
Associates a resource with a data element concept. It does not impose a domain on the resource using the concept.
ekg-concept:hasConcept | |
https://ekgf.org/ontology/concept#hasConcept | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:label | has concept |
rdfs:range | ekg-concept:DataElementConcept |
1.3.4 has manifestation§
Links a concept to a concrete manifestation such as a business term, API parameter, SPARQL variable, OWL class, SHACL shape, SKOS concept, source-code identifier, table, or column.
ekg-concept:hasManifestation | |
https://ekgf.org/ontology/concept#hasManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:DataElementConcept |
rdfs:label | has manifestation |
rdfs:range | ekg-concept:ConceptManifestation |
1.3.5 in concept set§
Associates a data element concept with a concept set containing it.
ekg-concept:inConceptSet | |
https://ekgf.org/ontology/concept#inConceptSet | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:DataElementConcept |
rdfs:label | in concept set |
rdfs:range | ekg-concept:ConceptSet |
1.3.6 manifestation resource§
The RDF resource manifested by a technical manifestation, for example an OWL class, OWL property, SHACL shape, SKOS concept, datatype, named graph, table IRI, or external schema identifier.
ekg-concept:manifestationResource | |
https://ekgf.org/ontology/concept#manifestationResource | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:TechnicalManifestation |
rdfs:label | manifestation resource |
rdfs:range | rdfs:Resource |
1.3.7 manifestation value§
The exact lexical value for a manifestation when it is not naturally represented as an RDF resource. Examples: customerId, ?customer, _abc22, a SQL column token, or a Cypher identifier.
ekg-concept:manifestationValue | |
https://ekgf.org/ontology/concept#manifestationValue | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:DatatypeProperty |
rdfs:domain | ekg-concept:ConceptManifestation |
rdfs:label | manifestation value |
rdfs:range | xsd:string |
1.3.8 occurrence of§
Identifies the concept manifestation that occurs at a particular source location.
ekg-concept:occurrenceOf | |
https://ekgf.org/ontology/concept#occurrenceOf | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:ManifestationOccurrence |
rdfs:label | occurrence of |
rdfs:range | ekg-concept:ConceptManifestation |
1.3.9 occurs within§
Links a ManifestationOccurrence to an occurrence directly containing it in the
same observed source context. For example, a column occurrence can be contained
in a worksheet occurrence. Following each endpoint's occurrenceOf and concept
links then relates the observed attribute meaning to the observed compound
meaning in that context.
Both endpoints are occurrences, not DataElementConcepts or ConceptManifestations.
One occurrence can have several observed containers, and a container can have
several children. This property is neither functional nor inverse-functional;
shared endpoints do not merge identities. It is irreflexive and not transitive.
Query occursWithin+ to walk to all ancestors; the ontology does not materialize
indirect ancestors as direct containment assertions.
An analyzer must establish and assert containment from the source structure. Matching paths, positions, types or manifestation identities do not create a link. A referenced definition and a reference to it are different source occurrences. Source-location and provenance properties remain on the observed occurrences; containment does not copy or inherit those values.
OccurrenceContainmentShape checks resource endpoints, occurrence roles and cycles. It does not read source content or prove that the asserted endpoints share the same source context. See the containment guide for validation and queries.
ekg-concept:occursWithin | |
https://ekgf.org/ontology/concept#occursWithin | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:IrreflexiveProperty |
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:ManifestationOccurrence |
rdfs:label | occurs within |
rdfs:range | ekg-concept:ManifestationOccurrence |
1.3.10 preferred business term§
Identifies a preferred business-language term for a data element concept.
ekg-concept:preferredBusinessTerm | |
https://ekgf.org/ontology/concept#preferredBusinessTerm | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:DataElementConcept |
rdfs:label | preferred business term |
rdfs:range | ekg-concept:BusinessTerm |
rdfs:subPropertyOf | ekg-concept:preferredManifestation |
1.3.11 preferred manifestation§
Identifies a preferred manifestation of a data element concept, specializing hasManifestation.
ekg-concept:preferredManifestation | |
https://ekgf.org/ontology/concept#preferredManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:DataElementConcept |
rdfs:label | preferred manifestation |
rdfs:range | ekg-concept:ConceptManifestation |
rdfs:subPropertyOf | ekg-concept:hasManifestation |
1.3.12 preferred query parameter manifestation§
Identifies a preferred URI-parameter manifestation for a data element concept.
ekg-concept:preferredQueryParameterManifestation | |
https://ekgf.org/ontology/concept#preferredQueryParameterManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:DataElementConcept |
rdfs:label | preferred query parameter manifestation |
rdfs:range | ekg-concept:URIParameterManifestation |
rdfs:subPropertyOf | ekg-concept:preferredManifestation |
1.3.13 preferred result column manifestation§
The manifestation whose label is the concept's public response-column name — what the edge projector renders in place of the SPARQL projection variable (story-signature design).
ekg-concept:preferredResultColumnManifestation | |
https://ekgf.org/ontology/concept#preferredResultColumnManifestation | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:DataElementConcept |
rdfs:label | preferred result column manifestation |
rdfs:range | ekg-concept:SPARQLResultColumnManifestation |
rdfs:subPropertyOf | ekg-concept:preferredManifestation |
1.3.14 source column§
Records the column position of a manifestation occurrence in its source. The ontology does not specify whether the position is zero-based or one-based.
ekg-concept:sourceColumn | |
https://ekgf.org/ontology/concept#sourceColumn | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:DatatypeProperty |
rdfs:domain | ekg-concept:ManifestationOccurrence |
rdfs:label | source column |
rdfs:range | xsd:integer |
1.3.15 source commit§
Records the source repository commit associated with a manifestation occurrence.
ekg-concept:sourceCommit | |
https://ekgf.org/ontology/concept#sourceCommit | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:DatatypeProperty |
rdfs:domain | ekg-concept:ManifestationOccurrence |
rdfs:label | source commit |
rdfs:range | xsd:string |
1.3.16 source line§
Records the line position of a manifestation occurrence in its source. The ontology does not specify whether the position is zero-based or one-based.
ekg-concept:sourceLine | |
https://ekgf.org/ontology/concept#sourceLine | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:DatatypeProperty |
rdfs:domain | ekg-concept:ManifestationOccurrence |
rdfs:label | source line |
rdfs:range | xsd:integer |
1.3.17 source path§
Records the source path at which a manifestation occurrence is located.
ekg-concept:sourcePath | |
https://ekgf.org/ontology/concept#sourcePath | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:DatatypeProperty |
rdfs:domain | ekg-concept:ManifestationOccurrence |
rdfs:label | source path |
rdfs:range | xsd:string |
1.3.18 source repository§
Records the repository IRI associated with a manifestation occurrence as an xsd:anyURI literal.
ekg-concept:sourceRepository | |
https://ekgf.org/ontology/concept#sourceRepository | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:DatatypeProperty |
rdfs:domain | ekg-concept:ManifestationOccurrence |
rdfs:label | source repository |
rdfs:range | xsd:anyURI |
1.3.19 source system§
The system in which this occurrence of a manifestation was observed, identified by a resource IRI. A source repository is not required; the same manifestation may occur in multiple systems.
ekg-concept:sourceSystem | |
https://ekgf.org/ontology/concept#sourceSystem | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:ManifestationOccurrence |
rdfs:label | source system |
rdfs:range | rdfs:Resource |
1.3.20 statement position§
Classifies a position of an occurrence within the query or update statement,
or the statement template rendering one, identified through foundIn:
| Position | Appearance | Example |
|---|---|---|
ParameterPosition | A value supplied for the invocation. | A template placeholder, or a variable the service pre-binds. |
ProjectionPosition | A result the statement returns. | A projected SELECT variable or alias. |
GraphTemplatePosition | A term the statement constructs or inserts. | A predicate in a CONSTRUCT or INSERT template. |
GraphPatternPosition | A term matched against data. | A class or predicate in the WHERE clause. |
One appearance can have several positions. A placeholder used in a triple
pattern is a parameter appearing in the graph pattern; record both. Record
the parameter position from the template language or the service's documented
binding profile, never from a token's spelling: SPARQL treats $name and
?name as one variable.
A positioned occurrence must identify at least one artifact through foundIn.
Positions are evidence about a statement. They do not declare a story's concept
usages; the Story Ontology maps each position to the usage role it leads an
analysis to expect.
ekg-concept:statementPosition | |
https://ekgf.org/ontology/concept#statementPosition | |
| RDF predicate | Value |
rdf:type | owl:ObjectProperty |
rdfs:domain | ekg-concept:ManifestationOccurrence |
rdfs:label | statement position |
rdfs:range | ekg-concept:StatementPosition |
1.3.21 taxonomy kind§
Use a string such as thesaurus to describe the kind of a SKOS concept scheme.
This metadata concerns the scheme's organization; it does not identify a data
element concept or classify an individual SKOS concept as a data element.
The property retains its string range and has no domain inference or closed list of permitted kinds. Moving it into the Concept Ontology does not introduce a new classification model or change the types of resources carrying it.
ekg-concept:taxonomyKind | |
https://ekgf.org/ontology/concept#taxonomyKind | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:DatatypeProperty |
rdfs:label | taxonomy kind |
rdfs:range | xsd:string |
1.3.22 template language§
Identifies the documented template language or substitution profile of a template document or placeholder manifestation. This general metadata property imposes no domain; each resource kind constrains its own language cardinality.
ekg-concept:templateLanguage | |
https://ekgf.org/ontology/concept#templateLanguage | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:ObjectProperty |
rdfs:label | template language |
rdfs:range | ekg-concept:TemplateLanguage |
1.4 Named Individuals§
1.4.1 Graph Pattern§
Instance of: ekg-concept:StatementPosition
An appearance in the graph pattern that the statement matches against data: its WHERE clause, including filters, bindings, inline data, optional, union, negation and subquery patterns, and the solution modifiers applied to those solutions.
ekg-concept:GraphPatternPosition | |
https://ekgf.org/ontology/concept#GraphPatternPosition | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:NamedIndividual |
rdf:type | ekg-concept:StatementPosition |
rdfs:label | Graph Pattern |
1.4.2 Graph Template§
Instance of: ekg-concept:StatementPosition
An appearance in a graph template whose instantiations the statement returns or adds: a CONSTRUCT template, an INSERT template, or INSERT DATA. This is the statement's own SPARQL graph template, not a template document in a template language. Terms in DELETE templates and DELETE DATA are not classified by this position.
ekg-concept:GraphTemplatePosition | |
https://ekgf.org/ontology/concept#GraphTemplatePosition | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:NamedIndividual |
rdf:type | ekg-concept:StatementPosition |
rdfs:label | Graph Template |
owl:differentFrom | ekg-concept:GraphPatternPosition |
1.4.3 Parameter§
Instance of: ekg-concept:StatementPosition
An appearance whose value is supplied for an invocation rather than matched or produced by the statement: a template placeholder substituted before the statement is parsed, or a statement variable that the executing service pre-binds under its documented binding profile. Spelling does not establish this position; SPARQL treats $name and ?name as the same variable.
ekg-concept:ParameterPosition | |
https://ekgf.org/ontology/concept#ParameterPosition | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:NamedIndividual |
rdf:type | ekg-concept:StatementPosition |
rdfs:label | Parameter |
owl:differentFrom | ekg-concept:GraphPatternPosition |
owl:differentFrom | ekg-concept:GraphTemplatePosition |
owl:differentFrom | ekg-concept:ProjectionPosition |
1.4.4 Projection§
Instance of: ekg-concept:StatementPosition
An appearance as a result the statement returns: a variable or expression alias projected by its SELECT clause, or a DESCRIBE target. A projection inside a subquery belongs to the enclosing graph pattern, not to the statement's results.
ekg-concept:ProjectionPosition | |
https://ekgf.org/ontology/concept#ProjectionPosition | |
| RDF predicate | Value |
|---|---|
rdf:type | owl:NamedIndividual |
rdf:type | ekg-concept:StatementPosition |
rdfs:label | Projection |
owl:differentFrom | ekg-concept:GraphPatternPosition |
owl:differentFrom | ekg-concept:GraphTemplatePosition |
1.5 Shapes§
1.5.1 Legacy Template Manifestation Shape§
Rejects instances of the retired product-specific template-placeholder class, including instances also given the current type or a language. Migration must remove the retired type and identify the placeholder's language profile.
ekg-concept:LegacyTemplateManifestationShape | |
https://ekgf.org/ontology/concept#LegacyTemplateManifestationShape | |
| RDF predicate | Value |
|---|---|
rdf:type | sh:NodeShape |
rdfs:label | Legacy Template Manifestation Shape |
sh:message | LegraDollarManifestation is retired. Replace that type with TemplateParameterManifestation and declare its documented templateLanguage profile. |
sh:not | (sh:class: ekg-concept:LegraDollarManifestation) |
sh:targetClass | ekg-concept:LegraDollarManifestation |
1.5.2 Occurrence Containment Shape§
Targets subjects and objects of occursWithin, including untyped endpoints.
Endpoints must be IRI or blank-node ManifestationOccurrences and must not also
be DataElementConcepts or ConceptManifestations. RDFS inference with the Concept
Ontology supplies endpoint types from the property's domain and range. Without
inference, supply those occurrence types explicitly.
A SPARQL property-path constraint rejects self-links and longer containment cycles without adding transitive property semantics. Roots without a container, multiple children and multiple direct parents remain valid. This validator and its nested constraints belong to the Concept Ontology's shapes graph.
The shape validates supplied graph structure. It does not inspect source files, infer containment from coordinates, enforce source-provenance equality or check harvest completeness. An analyzer must supply observed same-context edges.
ekg-concept:OccurrenceContainmentShape | |
https://ekgf.org/ontology/concept#OccurrenceContainmentShape | |
| RDF predicate | Value |
|---|---|
rdf:type | sh:NodeShape |
rdfs:label | Occurrence Containment Shape |
sh:class | ekg-concept:ManifestationOccurrence |
sh:nodeKind | sh:BlankNodeOrIRI |
sh:not | (sh:or: ((sh:class: ekg-concept:DataElementConcept), (sh:class: ekg-concept:ConceptManifestation))) |
sh:property | (sh:class: ekg-concept:ManifestationOccurrence; sh:nodeKind: sh:BlankNodeOrIRI; sh:path: ekg-concept:occursWithin) |
sh:sparql | (sh:message: Occurrence containment must be acyclic; an occurrence cannot contain itself directly or through other occurrences.; sh:select: SPARQL SELECT query 1) |
sh:targetObjectsOf | ekg-concept:occursWithin |
sh:targetSubjectsOf | ekg-concept:occursWithin |
1.5.2.1 SPARQL query 1§
Occurrence containment must be acyclic; an occurrence cannot contain itself directly or through other occurrences.
PREFIX concept: <https://ekgf.org/ontology/concept#>
SELECT $this WHERE {
$this concept:occursWithin+ $this .
}
1.5.3 Occurrence Sighting Shape§
Targets subjects of foundIn and statementPosition, which must be
ManifestationOccurrences and not concepts or manifestations. Artifact values
must be resources other than occurrences, concepts, manifestations and
positions. Position values must be StatementPosition IRIs. An occurrence with a
statement position must identify at least one artifact. RDFS inference supplies
occurrence and position types from the property domains and ranges; without
inference, supply those types explicitly.
The shape checks the supplied graph. It does not read source files or prove that the asserted artifacts and positions match the source.
ekg-concept:OccurrenceSightingShape | |
https://ekgf.org/ontology/concept#OccurrenceSightingShape | |
| RDF predicate | Value |
|---|---|
rdf:type | sh:NodeShape |
rdfs:label | Occurrence Sighting Shape |
sh:class | ekg-concept:ManifestationOccurrence |
sh:nodeKind | sh:BlankNodeOrIRI |
sh:not | (sh:or: ((sh:class: ekg-concept:DataElementConcept), (sh:class: ekg-concept:ConceptManifestation))) |
sh:property | (sh:message: foundIn must identify an artifact resource, not a literal, occurrence, concept, manifestation or statement position. Containment between occurrences uses occursWithin.; sh:nodeKind: sh:BlankNodeOrIRI; sh:not: (sh:or: ((sh:class: ekg-concept:ManifestationOccurrence), (sh:class: ekg-concept:DataElementConcept), (sh:class: ekg-concept:ConceptManifestation), (sh:class: ekg-concept:StatementPosition))); sh:path: ekg-concept:foundIn) |
sh:property | (sh:class: ekg-concept:StatementPosition; sh:message: statementPosition must identify a StatementPosition IRI.; sh:nodeKind: sh:IRI; sh:path: ekg-concept:statementPosition) |
sh:sparql | (sh:message: An occurrence with a statement position must identify, through foundIn, an artifact containing that statement.; sh:select: SPARQL SELECT query 1) |
sh:targetSubjectsOf | ekg-concept:foundIn |
sh:targetSubjectsOf | ekg-concept:statementPosition |
1.5.3.1 SPARQL query 1§
An occurrence with a statement position must identify, through foundIn, an artifact containing that statement.
PREFIX concept: <https://ekgf.org/ontology/concept#>
SELECT $this WHERE {
$this concept:statementPosition ?position .
FILTER NOT EXISTS { $this concept:foundIn ?artifact }
}
1.5.4 Statement Position Shape§
Targets declared positions and every object of statementPosition. A position
must be an IRI with a nonempty label and a nonempty definition in rdfs:comment
or markdownDescription, and must not also be a concept, manifestation or
occurrence. Load the Concept Ontology as the ontology graph to supply the
built-in definitions.
ekg-concept:StatementPositionShape | |
https://ekgf.org/ontology/concept#StatementPositionShape | |
| RDF predicate | Value |
|---|---|
rdf:type | sh:NodeShape |
rdfs:label | Statement Position Shape |
sh:nodeKind | sh:IRI |
sh:not | (sh:or: ((sh:class: ekg-concept:DataElementConcept), (sh:class: ekg-concept:ConceptManifestation), (sh:class: ekg-concept:ManifestationOccurrence))) |
sh:or | ((sh:property: (sh:minCount: 1; sh:path: rdfs:comment)), (sh:property: (sh:minCount: 1; sh:path: ekg-annotation:markdownDescription))) |
sh:property | (sh:minLength: 1; sh:nodeKind: sh:Literal; sh:path: rdfs:comment) |
sh:property | (sh:minCount: 1; sh:minLength: 1; sh:nodeKind: sh:Literal; sh:path: rdfs:label) |
sh:property | (sh:minLength: 1; sh:nodeKind: sh:Literal; sh:path: ekg-annotation:markdownDescription) |
sh:targetClass | ekg-concept:StatementPosition |
sh:targetObjectsOf | ekg-concept:statementPosition |
1.5.5 Template Language Shape§
Requires a stable language/profile IRI, a human-readable name, and a reference to its documentation. These metadata do not certify renderer behavior or execution approval.
ekg-concept:TemplateLanguageShape | |
https://ekgf.org/ontology/concept#TemplateLanguageShape | |
| RDF predicate | Value |
|---|---|
rdf:type | sh:NodeShape |
rdfs:label | Template Language Shape |
sh:nodeKind | sh:IRI |
sh:property | (sh:minCount: 1; sh:minLength: 1; sh:nodeKind: sh:Literal; sh:path: rdfs:label) |
sh:property | (sh:minCount: 1; sh:nodeKind: sh:IRI; sh:path: rdfs:seeAlso) |
sh:targetClass | ekg-concept:TemplateLanguage |
sh:targetObjectsOf | ekg-concept:templateLanguage |
1.5.6 Template Parameter Manifestation Shape§
Requires a template-placeholder manifestation to identify its language and its exact nonempty token. A shared token is interpreted within that language, not from its punctuation alone.
ekg-concept:TemplateParameterManifestationShape | |
https://ekgf.org/ontology/concept#TemplateParameterManifestationShape | |
| RDF predicate | Value |
|---|---|
rdf:type | sh:NodeShape |
rdfs:label | Template Parameter Manifestation Shape |
sh:nodeKind | sh:BlankNodeOrIRI |
sh:property | (sh:class: ekg-concept:TemplateLanguage; sh:maxCount: 1; sh:minCount: 1; sh:nodeKind: sh:IRI; sh:path: ekg-concept:templateLanguage) |
sh:property | (sh:datatype: xsd:string; sh:maxCount: 1; sh:minCount: 1; sh:minLength: 1; sh:path: ekg-concept:manifestationValue) |
sh:targetClass | ekg-concept:TemplateParameterManifestation |