EKGF Ontologies

A reference to the related EKGF ontologies. These vocabularies describe enterprise knowledge graphs, their concepts, use cases, stories, artifacts, governance, publication and lifecycles.

This editor's draft is generated from the ontology sources and their registry. It is a documentation preview, not an approved standards release. Supplied source annotations are reproduced. Documentation gaps are reported explicitly; ontology imports are not fetched and this publication does not establish semantic correctness.

1.1 EKGF Ontologies§

Explore the 24 ontologies in this family. Select an ontology to read its vocabulary reference.

• Annotation Ontology

  Descriptive text that any resource can carry: a description in Markdown, a subtitle and a summary. These are annotation properties, so they apply to classes and properties as well as to individuals.

• Platform API Ontology

  The EKG Platform API Ontology.

• Artifact Dependency Ontology

  Generic dependency vocabulary for Semantic Modelling artifacts such as OWL ontologies, SHACL shapesets, SKOS taxonomies, and concept sets.

• Artifact Governance Ontology

  Who governs a semantic artifact and which family it belongs to. One vocabulary for OWL ontologies, SHACL shapesets, SKOS taxonomies and concept sets. Replaces the Ontology Ontology (https://ekgf.org/ontology/ontology#).

• Artifact Publication Ontology

  How semantic artifacts are published, either as a family or as explicitly selected artifact references: profiles configure generation, targets identify destinations, runs generate outputs, releases identify versions and approvals record authority decisions about exact releases. Family grouping is optional. The state of a run and of a release is described with the Lifecycle Ontology. SHACL shapes validate the scope and approval records.

• Authorization Ontology

  The EKGF Authorization Ontology.

     Modeling "Role Based Access Control" which is not the same
     as EKG-level entitlement calculation but could be part thereof.
  

• Capability Ontology

  A vocabulary for capabilities and capability domains, with example capabilities for sharing data and managing data products. The current vocabulary does not define the relationships assigning capabilities to domains.

• Communication Ontology

  Channel-neutral ontology for recipients, endpoints, audiences, memberships, consent and legal-basis evidence, campaign snapshots, communication attempts, and delivery outcomes.

• Concept Ontology

  Data element concepts, called concepts for short, identify reusable meanings independently of their business and technical manifestations. The scope includes individual data elements and compound data constructs such as whole classes and shapes. ManifestationOccurrence records where a manifestation appears in a source.

• DataOps Ontology

  A vocabulary for DataOps pipelines, RDF load requests, their processing states, and the single-graph and multi-graph datasets produced during loading and assembly.

• Dataset Ontology

  A vocabulary for RDF datasets and their source files, named graphs, identifiers, and composition into static or compound datasets.

• File System Ontology

  A provider-neutral filesystem vocabulary: rooted views, directories, named directory entries, stable file series, immutable file versions whose content is a MIME-typed literal, symbolic links and service-style shortcuts, external provider objects, tombstones, declared capability profiles, and attachment assertions with explicit tracking modes. Names and parents belong to directory entries, never to files, so hard links, multiple parents, aliases, and provider shortcuts are representable without copying the target. Provider-specific API fields and credentials do not enter this ontology.

• Lifecycle Ontology

  Everything has a lifecycle: use cases, stories, concepts, personas, outcomes, data products and datasets. This ontology says what a lifecycle is, which lifecycle a thing follows and which state the thing is in. It depends on none of the ontologies that describe those things.

  A lifecycle has a name, states and permitted transitions, optionally grouped into phases. Its states and transitions form a directed graph; it does not require a separate RDF named graph. Multiple lifecycles can share an RDF graph, with inLifecycle expressing membership independently of graph placement. State order controls presentation, not which moves are permitted. There can be any number of lifecycles. This ontology defines none: the well-known lifecycles are a dataset (dataset/well-known-lifecycles.ttl), and anyone can define more. The registry uses a separate namespace for each lifecycle to distinguish shared state names such as Draft and Deprecated. This is an IRI naming convention, not a graph-storage requirement; custom lifecycles can use another IRI naming convention.

  Which lifecycles a thing follows is decided in this order:

  1. The complete set of lifecycles the thing names itself, with followsLifecycle.
  2. Otherwise, the union of lifecycles that apply to its classes (including superclasses), with appliesTo.

  A thing has one inState history head per effective lifecycle. Each head is a StateTransition occurrence whose currentState belongs to that lifecycle. priorStateTransition links earlier occurrences; the lifecycle is derived from each state, and optional provenance is recorded on the occurrence.

• Maturity Model Ontology

  A vocabulary for organizing maturity models into pillars, capability areas, capabilities, and levels, with an example EKGF model containing four pillars and five numbered levels.

• Outcome Ontology

  The outcomes that use cases and stories contribute to. An outcome has a stereotype and a priority. Its lifecycle is described with the Lifecycle Ontology.

• Persona Ontology

  A vocabulary for personas participating in EKG stories, their accountabilities, and sub-persona relationships. Persona identities are distinct from individual people.

• Raw Data Ontology

  The Raw Data Ontology is used by a "capture step" in an EKG DataOps pipeline to capture any data from any data source as RDF triples without mapping it to higher level ontologies. It is assumed that subsequent steps in a given EKG DataOps pipeline will transform the raw data to match with target ontologies.

• Specification by Example Ontology

  A vocabulary for executable story scenarios, including initial graph and dataset states, story requests, expected results, chained scenarios, and captured run-time values.

• SHACL Shape Metadata Ontology

  Metadata and validation for grouping SHACL node and property shapes into shapesets, recording their purpose, and linking collections to concrete shapes graphs with separate identities.

• Story Ontology

  Stories, their extensible primary-purpose stereotypes, story-owned input, output, and dependent concept usages, execution requirements, and implementation ownership.

• SPARQL Story Implementation Ontology

  The SPARQL Story Implementation Ontology defines story implementations using executable SPARQL queries or updates, or explicitly declared template documents and renderers that generate SPARQL.

     The Story ontology itself is: https://ekgf.org/ontology/story#
  

• Story Service Ontology

  The Story Service Ontology supports the Story Service which is a program that can translate Use Case Stories to executable APIs.

• Use Case Ontology

  The EKGF Use Case Ontology, based on the EKG/Method as documented on https://method.ekgf.org. It describes the use case tree and the stereotype of each use case. The lifecycle of a use case is described with the Lifecycle Ontology.

• User Experience Ontology

  This ontology covers various minor details, "hints", that can be used by User Interface programmers to optimize the user experience. Details like the default sorting of lists of objects, the default color of things etc.

2.1 Overview§

Annotation Ontology

Descriptive text that any resource can carry: a description in Markdown, a subtitle and a summary. These are annotation properties, so they apply to classes and properties as well as to individuals.

2.2 Properties§

2.2.1 Markdown description§

Label: Markdown description

Identifier: ekg-annotation:markdownDescription

2.2.1.1 Explanatory documentation§

Use this annotation on an ontology, class, property, or individual for explanations that benefit from Markdown: scope, examples, modeling decisions, ownership rules, and application behavior. Use an English language tag for the English explanation. Keep a short definition in rdfs:comment where useful.

Markdown can include headings, lists, tables, fenced code examples, and links. Consumers render this description when present and use rdfs:comment when it is absent.

An explanation is an annotation. Describing a subclass relationship, a property range, a SHACL constraint, or an application default does not implement it. Identify agreed changes awaiting implementation explicitly, so readers can distinguish the recorded decision from the current axioms.

IRI: https://ekgf.org/ontology/annotation#markdownDescription

2.2.2 subtitle§

Label: subtitle

Identifier: ekg-annotation:subtitle

One line shown under the label of the resource.

IRI: https://ekgf.org/ontology/annotation#subtitle

2.2.3 summary§

Label: summary

Identifier: ekg-annotation:summary

A short summary of the resource, in plain text.

IRI: https://ekgf.org/ontology/annotation#summary

3.1 Overview§

Platform API Ontology

The EKG Platform API Ontology.

3.2 Properties§

3.2.1 slug§

Label: slug

Identifier: ekg-api:slug

The short, lowercase, hyphenated name by which a resource is addressed in a URL. Replaces api:key.

IRI: https://ekgf.org/ontology/api#slug

3.2.2 taxonomy kind§

Label: taxonomy kind

Identifier: ekg-api:taxonomyKind

What kind of taxonomy a SKOS concept scheme is, such as thesaurus.

IRI: https://ekgf.org/ontology/api#taxonomyKind

4.1 Overview§

Artifact Dependency Ontology

Separates dependency facts, evidence, and workspace or branch resolution status for Semantic Modelling dependency management.

4.2 Classes§

4.2.1 Dependency§

Label: Dependency

Identifier: ekg-artdep:Dependency

A reified dependency edge from one semantic artifact to another resource or artifact.

IRI: https://ekgf.org/ontology/artifact-dependency#Dependency

4.2.2 Dependency evidence§

Label: Dependency evidence

Identifier: ekg-artdep:DependencyEvidence

The concrete triple, graph, namespace observation, or other fact that supports a dependency edge.

IRI: https://ekgf.org/ontology/artifact-dependency#DependencyEvidence

4.2.3 Dependency kind§

Label: Dependency kind

Identifier: ekg-artdep:DependencyKind

Controlled values describing why the dependency exists.

IRI: https://ekgf.org/ontology/artifact-dependency#DependencyKind

4.2.4 Dependency resolution§

Label: Dependency resolution

Identifier: ekg-artdep:DependencyResolution

Workspace and branch scoped resolution state for a dependency target.

IRI: https://ekgf.org/ontology/artifact-dependency#DependencyResolution

4.2.5 Explicit dependency§

Label: Explicit dependency

Identifier: ekg-artdep:ExplicitDependency

A dependency directly declared by a source triple such as owl:imports, sh:shapesGraph, or artdep:dependsOn.

IRI: https://ekgf.org/ontology/artifact-dependency#ExplicitDependency

4.2.6 Implicit dependency§

Label: Implicit dependency

Identifier: ekg-artdep:ImplicitDependency

A dependency inferred from referenced terms, namespaces, validation constraints, or profile requirements rather than an explicit import declaration.

IRI: https://ekgf.org/ontology/artifact-dependency#ImplicitDependency

4.2.7 Ontology load request§

Label: Ontology load request

Identifier: ekg-artdep:OntologyLoadRequest

A request for a worker node to load an ontology family that would satisfy one or more unloaded dependency targets. How far the request has come is its lifecycle state; by default a request follows the execution lifecycle.

IRI: https://ekgf.org/ontology/artifact-dependency#OntologyLoadRequest

4.2.8 Resolution status§

Label: Resolution status

Identifier: ekg-artdep:ResolutionStatus

Controlled values describing whether and how a dependency target resolved in a workspace context.

IRI: https://ekgf.org/ontology/artifact-dependency#ResolutionStatus

4.2.9 Semantic artifact§

Label: Semantic artifact

Identifier: ekg-artdep:SemanticArtifact

A Semantic Modelling artifact that can depend on another artifact, including OWL ontologies, SHACL shapesets, SKOS taxonomies, and concept sets.

IRI: https://ekgf.org/ontology/artifact-dependency#SemanticArtifact

4.3 Properties§

4.3.1 dependency evidence§

Label: dependency evidence

Identifier: ekg-artdep:dependencyEvidence

Links a dependency edge to one supporting evidence record.

IRI: https://ekgf.org/ontology/artifact-dependency#dependencyEvidence

4.3.2 dependency kind§

Label: dependency kind

Identifier: ekg-artdep:dependencyKind

Classifies why the dependency exists.

IRI: https://ekgf.org/ontology/artifact-dependency#dependencyKind

4.3.3 dependency target§

Label: dependency target

Identifier: ekg-artdep:dependencyTarget

The target resource named by the dependency edge, loaded or not.

IRI: https://ekgf.org/ontology/artifact-dependency#dependencyTarget

4.3.4 dependent artifact§

Label: dependent artifact

Identifier: ekg-artdep:dependentArtifact

The artifact that owns the dependency edge.

IRI: https://ekgf.org/ontology/artifact-dependency#dependentArtifact

4.3.5 depends on§

Label: depends on

Identifier: ekg-artdep:dependsOn

Direct dependency projection from an artifact to the dependency target. Reified edges use artdep:Dependency when evidence or resolution state is needed.

IRI: https://ekgf.org/ontology/artifact-dependency#dependsOn

4.3.6 evidence graph§

Label: evidence graph

Identifier: ekg-artdep:evidenceGraph

Named graph containing the source triple or observation that supports the dependency.

IRI: https://ekgf.org/ontology/artifact-dependency#evidenceGraph

4.3.7 evidence object§

Label: evidence object

Identifier: ekg-artdep:evidenceObject

IRI object of the source triple or observation that supports the dependency.

IRI: https://ekgf.org/ontology/artifact-dependency#evidenceObject

4.3.8 evidence predicate§

Label: evidence predicate

Identifier: ekg-artdep:evidencePredicate

Predicate of the source triple or observation that supports the dependency. It is an annotation property because its values are properties, which are not individuals.

IRI: https://ekgf.org/ontology/artifact-dependency#evidencePredicate

4.3.9 evidence subject§

Label: evidence subject

Identifier: ekg-artdep:evidenceSubject

Subject of the source triple or observation that supports the dependency.

IRI: https://ekgf.org/ontology/artifact-dependency#evidenceSubject

4.3.10 has dependency§

Label: has dependency

Identifier: ekg-artdep:hasDependency

Links a semantic artifact to a reified dependency edge.

IRI: https://ekgf.org/ontology/artifact-dependency#hasDependency

4.3.11 load hint§

Label: load hint

Identifier: ekg-artdep:loadHint

Optional URI hint for loading or locating an unresolved dependency target.

IRI: https://ekgf.org/ontology/artifact-dependency#loadHint

4.3.12 load request authority§

Label: load request authority

Identifier: ekg-artdep:loadRequestAuthority

Authority governing the artifact family named by the load request.

IRI: https://ekgf.org/ontology/artifact-dependency#loadRequestAuthority

4.3.13 load request dependency§

Label: load request dependency

Identifier: ekg-artdep:loadRequestDependency

Links a load request to a dependency edge that the requested family load is expected to satisfy.

IRI: https://ekgf.org/ontology/artifact-dependency#loadRequestDependency

4.3.14 load request family§

Label: load request family

Identifier: ekg-artdep:loadRequestFamily

Artifact family that should be loaded to satisfy the unresolved dependency targets.

IRI: https://ekgf.org/ontology/artifact-dependency#loadRequestFamily

4.3.15 load request target§

Label: load request target

Identifier: ekg-artdep:loadRequestTarget

Dependency target IRI that caused this load request.

IRI: https://ekgf.org/ontology/artifact-dependency#loadRequestTarget

4.3.16 referenced namespace§

Label: referenced namespace

Identifier: ekg-artdep:referencedNamespace

Namespace IRI observed in an implicit dependency, usually derived from a referenced term IRI.

IRI: https://ekgf.org/ontology/artifact-dependency#referencedNamespace

4.3.17 resolution§

Label: resolution

Identifier: ekg-artdep:resolution

Links a dependency edge to its workspace or branch scoped resolution state.

IRI: https://ekgf.org/ontology/artifact-dependency#resolution

4.3.18 resolution branch§

Label: resolution branch

Identifier: ekg-artdep:resolutionBranch

Branch context in which the dependency resolution was computed.

IRI: https://ekgf.org/ontology/artifact-dependency#resolutionBranch

4.3.19 resolution commit§

Label: resolution commit

Identifier: ekg-artdep:resolutionCommit

Commit context in which the dependency resolution was computed, when a resolution is pinned to a specific commit.

IRI: https://ekgf.org/ontology/artifact-dependency#resolutionCommit

4.3.20 resolution message§

Label: resolution message

Identifier: ekg-artdep:resolutionMessage

Human-readable diagnostic explaining a non-loaded or ambiguous resolution.

IRI: https://ekgf.org/ontology/artifact-dependency#resolutionMessage

4.3.21 resolution status§

Label: resolution status

Identifier: ekg-artdep:resolutionStatus

The loaded, unloaded, incomplete, ambiguous, external, or unsupported state of a dependency resolution.

IRI: https://ekgf.org/ontology/artifact-dependency#resolutionStatus

4.3.22 resolution workspace§

Label: resolution workspace

Identifier: ekg-artdep:resolutionWorkspace

Workspace context in which the dependency resolution was computed.

IRI: https://ekgf.org/ontology/artifact-dependency#resolutionWorkspace

4.3.23 resolved artifact§

Label: resolved artifact

Identifier: ekg-artdep:resolvedArtifact

The loaded artifact that satisfies the dependency target, when resolution status is Loaded.

IRI: https://ekgf.org/ontology/artifact-dependency#resolvedArtifact

4.4 Named Individuals§

4.4.1 Ambiguous§

Label: Ambiguous

Identifier: ekg-artdep:Ambiguous

Instance of: ekg-artdep:ResolutionStatus

The dependency target matches more than one candidate artifact in the current workspace context.

IRI: https://ekgf.org/ontology/artifact-dependency#Ambiguous

4.4.2 Declared import dependency§

Label: Declared import dependency

Identifier: ekg-artdep:DeclaredImportDependency

Instance of: ekg-artdep:DependencyKind

A dependency declared by an import-like predicate such as owl:imports.

IRI: https://ekgf.org/ontology/artifact-dependency#DeclaredImportDependency

4.4.3 External§

Label: External

Identifier: ekg-artdep:External

Instance of: ekg-artdep:ResolutionStatus

The dependency target is intentionally outside the workspace and does not need to be loaded locally.

IRI: https://ekgf.org/ontology/artifact-dependency#External

4.4.4 Failed§

Label: Failed

Identifier: ekg-artdep:Failed

Instance of: ekg-artdep:ResolutionStatus

Dependency resolution was attempted and failed in the current workspace context.

IRI: https://ekgf.org/ontology/artifact-dependency#Failed

4.4.5 Incomplete§

Label: Incomplete

Identifier: ekg-artdep:Incomplete

Instance of: ekg-artdep:ResolutionStatus

The dependency target is not sufficiently described to load or resolve automatically.

IRI: https://ekgf.org/ontology/artifact-dependency#Incomplete

4.4.6 Loaded§

Label: Loaded

Identifier: ekg-artdep:Loaded

Instance of: ekg-artdep:ResolutionStatus

The dependency target resolves to an artifact loaded in the current workspace context.

IRI: https://ekgf.org/ontology/artifact-dependency#Loaded

4.4.7 Namespace reference dependency§

Label: Namespace reference dependency

Identifier: ekg-artdep:NamespaceReferenceDependency

Instance of: ekg-artdep:DependencyKind

An implicit dependency derived from terms that share an external namespace.

IRI: https://ekgf.org/ontology/artifact-dependency#NamespaceReferenceDependency

4.4.8 Profile dependency§

Label: Profile dependency

Identifier: ekg-artdep:ProfileDependency

Instance of: ekg-artdep:DependencyKind

A dependency on a standards or implementation profile.

IRI: https://ekgf.org/ontology/artifact-dependency#ProfileDependency

4.4.9 Shape graph dependency§

Label: Shape graph dependency

Identifier: ekg-artdep:ShapeGraphDependency

Instance of: ekg-artdep:DependencyKind

A dependency on a SHACL shapes graph or shapeset used for validation or schema reuse.

IRI: https://ekgf.org/ontology/artifact-dependency#ShapeGraphDependency

4.4.10 Term reference dependency§

Label: Term reference dependency

Identifier: ekg-artdep:TermReferenceDependency

Instance of: ekg-artdep:DependencyKind

An implicit dependency derived from a reference to a specific external class, property, shape, concept, or datatype.

IRI: https://ekgf.org/ontology/artifact-dependency#TermReferenceDependency

4.4.11 Unloaded§

Label: Unloaded

Identifier: ekg-artdep:Unloaded

Instance of: ekg-artdep:ResolutionStatus

The dependency target is known but no matching artifact is loaded in the current workspace context.

IRI: https://ekgf.org/ontology/artifact-dependency#Unloaded

4.4.12 Unsupported§

Label: Unsupported

Identifier: ekg-artdep:Unsupported

Instance of: ekg-artdep:ResolutionStatus

The dependency target uses a form that cannot be resolved yet.

IRI: https://ekgf.org/ontology/artifact-dependency#Unsupported

4.4.13 Validation dependency§

Label: Validation dependency

Identifier: ekg-artdep:ValidationDependency

Instance of: ekg-artdep:DependencyKind

A dependency required to validate an artifact or data graph correctly.

IRI: https://ekgf.org/ontology/artifact-dependency#ValidationDependency

5.1 Overview§

Artifact Governance Ontology

Who governs a semantic artifact and which family it belongs to. One vocabulary for OWL ontologies, SHACL shapesets, SKOS taxonomies and concept sets. Replaces the Ontology Ontology (https://ekgf.org/ontology/ontology#).

5.2 Classes§

5.2.1 Authority§

Label: Authority

Identifier: ekg-artgov:Authority

A role responsible for governing semantic artifacts or their publication namespaces. The party playing the role is linked with cmns-rlcmp:isPlayedBy and has its own identity. An authority and an organization playing it are distinct individuals, following the Commons separation of agents and roles. An authority is assigned a random UUIDv4 URN once in the authority registry. Its identity persists when names, hosts, URLs or the party playing the role change. Hosts and URLs are metadata and may have multiple values; they do not determine identity.

IRI: https://ekgf.org/ontology/artifact-governance#Authority

5.2.2 Authority publishing role§

Label: Authority publishing role

Identifier: ekg-artgov:AuthorityPublishingRole

Controlled role values describing how an authority participates in publishing a family.

IRI: https://ekgf.org/ontology/artifact-governance#AuthorityPublishingRole

5.2.3 Family§

Label: Family

Identifier: ekg-artgov:Family

An optional, enduring collection of related artifacts governed by one or more authorities, such as FIBO. A family spans artifact types: its ontologies, shapesets and taxonomies are members of the same family. Authorities can govern artifacts directly without organizing them into families. When used for publication, the family groups the artifacts across releases; each version and its approvals belong to a distinct standards release.

IRI: https://ekgf.org/ontology/artifact-governance#Family

5.2.4 Organization category§

Label: Organization category

Identifier: ekg-artgov:OrganizationCategory

A classifier describing the kind of organization involved in artifact governance, such as a standards body, consortium, project or community. An organization may have several categories. Categories are distinct from publishing responsibilities, community participation roles and legal or organizational structure.

IRI: https://ekgf.org/ontology/artifact-governance#OrganizationCategory

5.2.5 Reference§

Label: Reference

Identifier: ekg-artgov:Reference

Stands for one artifact. It gives the artifact a stable identity and slug even when the artifact itself is not loaded, or is known under several IRIs that differ only in a trailing hash or slash.

IRI: https://ekgf.org/ontology/artifact-governance#Reference

5.2.6 Standards community role§

Label: Standards community role

Identifier: ekg-artgov:StandardsCommunityRole

Controlled role values for people participating in the standards community behind an authority.

IRI: https://ekgf.org/ontology/artifact-governance#StandardsCommunityRole

5.3 Properties§

5.3.1 Authority acronym§

Label: Authority acronym

Identifier: ekg-artgov:authorityAcronym

Uppercase acronym identifying the authority, such as W3C, OMG, EDMA or EKGF.

IRI: https://ekgf.org/ontology/artifact-governance#authorityAcronym

5.3.2 Authority host§

Label: Authority host

Identifier: ekg-artgov:authorityHost

A host name used in the IRIs of the authority's artifacts, without protocol, such as www.w3.org or spec.edmcouncil.org. An authority may have multiple hosts, including historical hosts whose artifact IRIs remain in use. Adding, removing or changing a host does not change the authority's identity. A shared host does not imply shared governance; hosts are metadata, not identity keys.

IRI: https://ekgf.org/ontology/artifact-governance#authorityHost

5.3.3 Auto-load§

Label: Auto-load

Identifier: ekg-artgov:autoLoad

When false, a loader does not fetch the families of this authority when their artifacts appear as unresolved owl:imports targets.

IRI: https://ekgf.org/ontology/artifact-governance#autoLoad

5.3.4 Base IRI§

Label: Base IRI

Identifier: ekg-artgov:baseIri

A base IRI of artifacts published by an authority. An authority may carry multiple base IRIs, including different hosts, schemes and historical locations. These values do not determine the authority's identity.

IRI: https://ekgf.org/ontology/artifact-governance#baseIri

5.3.5 Community organization§

Label: Community organization

Identifier: ekg-artgov:communityOrganization

Links an authority to the organization that hosts its standards community. The party exercising the authority is stated separately with cmns-rlcmp:isPlayedBy.

IRI: https://ekgf.org/ontology/artifact-governance#communityOrganization

5.3.6 Community role§

Label: Community role

Identifier: ekg-artgov:communityRole

Declares a role used by the standards community behind an authority.

IRI: https://ekgf.org/ontology/artifact-governance#communityRole

5.3.7 Family acronym§

Label: Family acronym

Identifier: ekg-artgov:familyAcronym

Uppercase acronym identifying the family, such as FIBO or CDMC.

IRI: https://ekgf.org/ontology/artifact-governance#familyAcronym

5.3.8 File path prefix§

Label: File path prefix

Identifier: ekg-artgov:filePathPrefix

A portable, case-sensitive literal prefix matched at the beginning of any segment of the actual source file path. For example, fibo/ matches a directory and ekgf- matches a filename prefix. Values use forward slashes, are relative and nonempty, and contain no scheme, drive, empty segment or dot segment. A family may have several. Matching normalizes source path separators to forward slashes and removes current-directory and empty segments; callers must resolve parent-directory segments first. The actual path is supplied independently of the named-graph IRI. The longest matching file path prefix wins within this method; ties across families or disagreement with other methods are errors unless explicit inFamily assignments take precedence.

IRI: https://ekgf.org/ontology/artifact-governance#filePathPrefix

5.3.9 Git branch§

Label: Git branch

Identifier: ekg-artgov:gitBranch

The git branch or tag to clone.

IRI: https://ekgf.org/ontology/artifact-governance#gitBranch

5.3.10 Git path§

Label: Git path

Identifier: ekg-artgov:gitPath

Directory inside the git repository to scan for RDF files. The repository root when absent.

IRI: https://ekgf.org/ontology/artifact-governance#gitPath

5.3.11 Git repository URL§

Label: Git repository URL

Identifier: ekg-artgov:gitRepositoryUrl

HTTPS URL of the git repository that holds the source files of the family. A loader clones it and loads the RDF files it finds.

IRI: https://ekgf.org/ontology/artifact-governance#gitRepositoryUrl

5.3.12 Governed by§

Label: Governed by

Identifier: ekg-artgov:governedBy

Relates an artifact, a reference or a family to an authority that governs it. It has no domain because it applies to every artifact type.

IRI: https://ekgf.org/ontology/artifact-governance#governedBy

5.3.13 Graph IRI prefix§

Label: Graph IRI prefix

Identifier: ekg-artgov:graphIriPrefix

A case-sensitive literal prefix of the complete named-graph IRI, such as s3://standards/fibo/. It is an absolute IRI prefix typed xsd:anyURI. A family may have several. Relative file path prefixes belong in filePathPrefix; a graph name need not reveal its source file path. The longest matching graph IRI prefix wins within this method; ties across families or disagreement with other methods are errors unless explicit inFamily assignments take precedence.

IRI: https://ekgf.org/ontology/artifact-governance#graphIriPrefix

5.3.14 Historical name§

Label: Historical name

Identifier: ekg-artgov:historicalName

A former public name of an authority or organization.

IRI: https://ekgf.org/ontology/artifact-governance#historicalName

5.3.15 In family§

Label: In family

Identifier: ekg-artgov:inFamily

Explicitly assigns an artifact or a reference to a family. It has no domain because it applies to every artifact type. Collect the asserted memberships on the artifact, its references and their known IRI aliases before attempting recognition. These assignments take precedence over all prefix rules, and several explicit memberships are permitted. Recognition applies only when no membership is asserted; its result is derived metadata and must not silently be stored as an explicit inFamily assertion. Without an assertion or a matching rule, the artifact remains without a family.

IRI: https://ekgf.org/ontology/artifact-governance#inFamily

5.3.16 Legal owner§

Label: Legal owner

Identifier: ekg-artgov:legalOwner

Links an authority or an organization to the organization that legally owns or administers it. This relationship is separate from the party exercising an authority role, stated with cmns-rlcmp:isPlayedBy. This is governance metadata, not access inheritance.

IRI: https://ekgf.org/ontology/artifact-governance#legalOwner

5.3.17 Maximum family load quads§

Label: Maximum family load quads

Identifier: ekg-artgov:maxFamilyLoadQuads

Hard ceiling on the total number of quads accepted while loading the family.

IRI: https://ekgf.org/ontology/artifact-governance#maxFamilyLoadQuads

5.3.18 Maximum source quads§

Label: Maximum source quads

Identifier: ekg-artgov:maxSourceQuads

Hard ceiling on the number of quads accepted from one source file of the family.

IRI: https://ekgf.org/ontology/artifact-governance#maxSourceQuads

5.3.19 Namespace IRI prefix§

Label: Namespace IRI prefix

Identifier: ekg-artgov:namespaceIriPrefix

A case-sensitive literal prefix of an artifact's IRI, such as https://spec.edmcouncil.org/fibo/ontology/. It is an absolute IRI prefix, typed xsd:anyURI, and a family may have several. The longest matching namespace prefix wins within this recognition method. Equally long best matches for different families are an error. Lengths are not compared with filePathPrefix or graphIriPrefix; if their winning families disagree, recognition fails. Explicit inFamily assignments take precedence over all recognition methods.

IRI: https://ekgf.org/ontology/artifact-governance#namespaceIriPrefix

5.3.20 Organization category§

Label: Organization category

Identifier: ekg-artgov:organizationCategory

Classifies an organization by one or more organization categories. Set on the organization playing an authority role or hosting its community. An authority's player can be reached with cmns-rlcmp:isPlayedBy. Categories are asserted independently of legal type, organizational hierarchy and the roles that an organization plays; they are not inherited from a parent organization.

IRI: https://ekgf.org/ontology/artifact-governance#organizationCategory

5.3.21 Predecessor authority§

Label: Predecessor authority

Identifier: ekg-artgov:predecessorAuthority

Links an authority to a former authority identity that preceded it.

IRI: https://ekgf.org/ontology/artifact-governance#predecessorAuthority

5.3.22 Publishing role§

Label: Publishing role

Identifier: ekg-artgov:publishingRole

Describes how an authority participates in publishing, owning, maintaining or endorsing artifacts.

IRI: https://ekgf.org/ontology/artifact-governance#publishingRole

5.3.23 RDF file extension§

Label: RDF file extension

Identifier: ekg-artgov:rdfFileExtension

Restricts file discovery to files with this extension, such as .rdf or .ttl. Every supported RDF extension when absent.

IRI: https://ekgf.org/ontology/artifact-governance#rdfFileExtension

5.3.24 Refers to§

Label: Refers to

Identifier: ekg-artgov:refersTo

Relates a reference to the IRI of the artifact it stands for. A reference carries several values when the artifact is known under several IRIs.

IRI: https://ekgf.org/ontology/artifact-governance#refersTo

5.3.25 Source graph repository URL§

Label: Source graph repository URL

Identifier: ekg-artgov:sourceGraphRepositoryUrl

Canonical repository URL used to build stable, commit-pinned named graph IRIs for the source files when the loader clones from a mirror or a local checkout.

IRI: https://ekgf.org/ontology/artifact-governance#sourceGraphRepositoryUrl

5.3.26 Successor authority§

Label: Successor authority

Identifier: ekg-artgov:successorAuthority

Links an authority to a later authority identity that supersedes it.

IRI: https://ekgf.org/ontology/artifact-governance#successorAuthority

5.4 Named Individuals§

5.4.1 co-owner§

Label: co-owner

Identifier: ekg-artgov:AuthorityCoOwnerRole

Instance of: ekg-artgov:AuthorityPublishingRole

The authority co-owns the published artifacts with one or more other authorities.

IRI: https://ekgf.org/ontology/artifact-governance#AuthorityCoOwnerRole

5.4.2 maintainer§

Label: maintainer

Identifier: ekg-artgov:AuthorityMaintainerRole

Instance of: ekg-artgov:AuthorityPublishingRole

The authority maintains the artifacts between publication releases.

IRI: https://ekgf.org/ontology/artifact-governance#AuthorityMaintainerRole

5.4.3 owner§

Label: owner

Identifier: ekg-artgov:AuthorityOwnerRole

Instance of: ekg-artgov:AuthorityPublishingRole

The authority is the primary owning body of the published artifacts.

IRI: https://ekgf.org/ontology/artifact-governance#AuthorityOwnerRole

5.4.4 publisher§

Label: publisher

Identifier: ekg-artgov:AuthorityPublisherRole

Instance of: ekg-artgov:AuthorityPublishingRole

The authority publishes the artifacts or their specification site.

IRI: https://ekgf.org/ontology/artifact-governance#AuthorityPublisherRole

5.4.5 Community§

Label: Community

Identifier: ekg-artgov:CommunityCategory

Instance of: ekg-artgov:OrganizationCategory

An organized community whose participants collaborate around a shared topic or practice.

IRI: https://ekgf.org/ontology/artifact-governance#CommunityCategory

5.4.6 Consortium§

Label: Consortium

Identifier: ekg-artgov:ConsortiumCategory

Instance of: ekg-artgov:OrganizationCategory

An organization through which independent organizations cooperate toward shared objectives.

IRI: https://ekgf.org/ontology/artifact-governance#ConsortiumCategory

5.4.7 Organization categories for artifact governance§

Label: Organization categories for artifact governance

Identifier: ekg-artgov:OrganizationCategoryScheme

Instance of: cmns-cls:ClassificationScheme

An extensible classification scheme for organizations involved in artifact governance. Categories may overlap: an organization may be both a standards body and a consortium. A missing category means that no classification has been asserted.

IRI: https://ekgf.org/ontology/artifact-governance#OrganizationCategoryScheme

5.4.8 Project§

Label: Project

Identifier: ekg-artgov:ProjectCategory

Instance of: ekg-artgov:OrganizationCategory

An organized group carrying out a defined initiative and producing its work products.

IRI: https://ekgf.org/ontology/artifact-governance#ProjectCategory

5.4.9 Standards body§

Label: Standards body

Identifier: ekg-artgov:StandardsBodyCategory

Instance of: ekg-artgov:OrganizationCategory

An organization whose purpose includes developing, maintaining and publishing standards through an established governance process.

IRI: https://ekgf.org/ontology/artifact-governance#StandardsBodyCategory

5.4.10 standards editor§

Label: standards editor

Identifier: ekg-artgov:StandardsEditorRole

Instance of: ekg-artgov:StandardsCommunityRole

A standards-community participation role for editing the content of standards and their supporting artifacts.

IRI: https://ekgf.org/ontology/artifact-governance#StandardsEditorRole

5.4.11 standards publisher§

Label: standards publisher

Identifier: ekg-artgov:StandardsPublisherRole

Instance of: ekg-artgov:StandardsCommunityRole

A standards-community participation role for publishing standards artifacts and releases.

IRI: https://ekgf.org/ontology/artifact-governance#StandardsPublisherRole

5.4.12 standards reviewer§

Label: standards reviewer

Identifier: ekg-artgov:StandardsReviewerRole

Instance of: ekg-artgov:StandardsCommunityRole

A standards-community participation role for reviewing standards content and proposed changes.

IRI: https://ekgf.org/ontology/artifact-governance#StandardsReviewerRole

5.4.13 standards staff§

Label: standards staff

Identifier: ekg-artgov:StandardsStaffRole

Instance of: ekg-artgov:StandardsCommunityRole

A standards-community participation role for staff supporting the operation of the standards community.

IRI: https://ekgf.org/ontology/artifact-governance#StandardsStaffRole

5.4.14 working-group chair§

Label: working-group chair

Identifier: ekg-artgov:WorkingGroupChairRole

Instance of: ekg-artgov:StandardsCommunityRole

A standards-community participation role for chairing a working group and coordinating its work.

IRI: https://ekgf.org/ontology/artifact-governance#WorkingGroupChairRole

6.1 Overview§

Artifact Publication Ontology

How semantic artifacts are published, either as a family or as explicitly selected artifact references: profiles configure generation, targets identify destinations, runs generate outputs, releases identify versions and approvals record authority decisions about exact releases. Family grouping is optional. The state of a run and of a release is described with the Lifecycle Ontology. SHACL shapes validate the scope and approval records.

6.2 Classes§

6.2.1 Publication artifact§

Label: Publication artifact

Identifier: ekg-artpub:PublicationArtifact

A generated output of a publication run, such as a website bundle, PDF, RDF export, changelog, diff report or archive.

IRI: https://ekgf.org/ontology/artifact-publication#PublicationArtifact

6.2.2 Publication profile§

Label: Publication profile

Identifier: ekg-artpub:PublicationProfile

Branch-scoped generator configuration for publishing either one family or one or more explicit artifact references, including section ordering, render policy, validation gates and output targets. Retain the configuration referenced by a release; changed configuration requires a new profile identity.

IRI: https://ekgf.org/ontology/artifact-publication#PublicationProfile

6.2.3 Publication run§

Label: Publication run

Identifier: ekg-artpub:PublicationRun

An execution that generates publication artifacts for the scope selected by a profile, branch and input commit. The scope may be a family or explicit artifact references. How far it has come is its lifecycle state; by default a run follows the execution lifecycle.

IRI: https://ekgf.org/ontology/artifact-publication#PublicationRun

6.2.4 Publication target§

Label: Publication target

Identifier: ekg-artpub:PublicationTarget

A configured destination for a generated publication output, such as a website, PDF, RDF download, archive or package.

IRI: https://ekgf.org/ontology/artifact-publication#PublicationTarget

6.2.5 Release approval§

Label: Release approval

Identifier: ekg-artpub:ReleaseApproval

An affirmative approval decision by one authority about one exact standards release at a recorded time. Several authorities can approve the same release through separate records. An approval does not extend to other releases or future family members, and does not itself publish the release. Supporting evidence can be linked with rdfs:seeAlso. Required approvers and any withdrawal of approval are matters for the applicable governance policy; a governing or publishing role alone does not establish that approval occurred.

IRI: https://ekgf.org/ontology/artifact-publication#ReleaseApproval

6.2.6 Standards release§

Label: Standards release

Identifier: ekg-artpub:StandardsRelease

A versioned snapshot of either one family or one or more explicit artifact references. Its identity, scope, version and content provenance are immutable; changed content requires a new release identity and new approvals. A release may record a branch, input commit, publication run and generated artifacts where available, but externally produced releases do not require a local generator run. Its lifecycle state may change from candidate to published, superseded or withdrawn. A version label is scoped to the release's publication context, not a global identifier. Family membership is optional and is not inferred from the references in a release.

IRI: https://ekgf.org/ontology/artifact-publication#StandardsRelease

6.3 Properties§

6.3.1 Approved at§

Label: Approved at

Identifier: ekg-artpub:approvedAt

Timestamp at which the authority approved the identified release. This is distinct from when it was generated or published.

IRI: https://ekgf.org/ontology/artifact-publication#approvedAt

6.3.2 Approved by§

Label: Approved by

Identifier: ekg-artpub:approvedBy

Identifies the authority role that issued this approval. The organization playing the role has its own identity. A separate decision record is used for each approving authority.

IRI: https://ekgf.org/ontology/artifact-publication#approvedBy

6.3.3 Approves release§

Label: Approves release

Identifier: ekg-artpub:approvesRelease

Identifies the exact release approved by this decision. Approval is never attached to the enduring family or artifact reference.

IRI: https://ekgf.org/ontology/artifact-publication#approvesRelease

6.3.4 Artifact checksum§

Label: Artifact checksum

Identifier: ekg-artpub:artifactChecksum

Checksum or digest of a generated publication artifact.

IRI: https://ekgf.org/ontology/artifact-publication#artifactChecksum

6.3.5 Artifact media type§

Label: Artifact media type

Identifier: ekg-artpub:artifactMediaType

Media type of a generated publication artifact, such as text/html, application/pdf or text/turtle.

IRI: https://ekgf.org/ontology/artifact-publication#artifactMediaType

6.3.6 Artifact URL§

Label: Artifact URL

Identifier: ekg-artpub:artifactUrl

Stable URL where a generated publication artifact can be read.

IRI: https://ekgf.org/ontology/artifact-publication#artifactUrl

6.3.7 Generator version§

Label: Generator version

Identifier: ekg-artpub:generatorVersion

Version of the publication generator used by a publication profile, run, artifact or release.

IRI: https://ekgf.org/ontology/artifact-publication#generatorVersion

6.3.8 Input commit CID§

Label: Input commit CID

Identifier: ekg-artpub:inputCommitCid

Content identifier of the branch commit used as input for a publication run or release.

IRI: https://ekgf.org/ontology/artifact-publication#inputCommitCid

6.3.9 Publication artifact§

Label: Publication artifact

Identifier: ekg-artpub:publicationArtifact

Links a publication run or a standards release to a generated publication artifact.

IRI: https://ekgf.org/ontology/artifact-publication#publicationArtifact

6.3.10 Publication branch§

Label: Publication branch

Identifier: ekg-artpub:publicationBranch

Links a publication run or a standards release to the branch whose commit was published.

IRI: https://ekgf.org/ontology/artifact-publication#publicationBranch

6.3.11 Publication completed at§

Label: Publication completed at

Identifier: ekg-artpub:publicationCompletedAt

Timestamp at which a publication run completed.

IRI: https://ekgf.org/ontology/artifact-publication#publicationCompletedAt

6.3.12 Publication profile§

Label: Publication profile

Identifier: ekg-artpub:publicationProfile

Links a publication run, target, artifact or release to the profile that governed generation.

IRI: https://ekgf.org/ontology/artifact-publication#publicationProfile

6.3.13 Publication release§

Label: Publication release

Identifier: ekg-artpub:publicationRelease

Links a publication run or a generated artifact to the standards release that incorporated it.

IRI: https://ekgf.org/ontology/artifact-publication#publicationRelease

6.3.14 Publication run§

Label: Publication run

Identifier: ekg-artpub:publicationRun

Links a standards release or a generated artifact to the publication run that produced it.

IRI: https://ekgf.org/ontology/artifact-publication#publicationRun

6.3.15 Publication started at§

Label: Publication started at

Identifier: ekg-artpub:publicationStartedAt

Timestamp at which a publication run started.

IRI: https://ekgf.org/ontology/artifact-publication#publicationStartedAt

6.3.16 Publication target§

Label: Publication target

Identifier: ekg-artpub:publicationTarget

Links a publication profile, run or artifact to a configured output target.

IRI: https://ekgf.org/ontology/artifact-publication#publicationTarget

6.3.17 Publishes family§

Label: Publishes family

Identifier: ekg-artpub:publishesFamily

Links a publication profile to the one family that it publishes. Optional: a profile can instead select artifacts individually with publishesReference.

IRI: https://ekgf.org/ontology/artifact-publication#publishesFamily

6.3.18 Publishes reference§

Label: Publishes reference

Identifier: ekg-artpub:publishesReference

Selects an artifact by its stable reference for publication without a family. A profile can select several references. This does not create a family or assert family membership.

IRI: https://ekgf.org/ontology/artifact-publication#publishesReference

6.3.19 Release family§

Label: Release family

Identifier: ekg-artpub:releaseFamily

Identifies the one family whose version this release records. Optional: an ungrouped release selects artifacts with releaseReference instead. This is recorded explicitly, so editing a publication profile cannot change an existing release's scope.

IRI: https://ekgf.org/ontology/artifact-publication#releaseFamily

6.3.20 Release reference§

Label: Release reference

Identifier: ekg-artpub:releaseReference

Identifies an artifact included in a release without family grouping. Each selected artifact is represented by a stable reference; the release supplies its version and content provenance. A release can select several references. These are source artifacts, distinct from generated outputs linked by publicationArtifact.

IRI: https://ekgf.org/ontology/artifact-publication#releaseReference

6.3.21 Release version§

Label: Release version

Identifier: ekg-artpub:releaseVersion

Public version label of a standards release, whether it releases a family or explicitly selected artifact references. The label belongs to the release, not the enduring family or reference, and need not be globally unique.

IRI: https://ekgf.org/ontology/artifact-publication#releaseVersion

6.3.22 Released at§

Label: Released at

Identifier: ekg-artpub:releasedAt

Timestamp at which a standards release was published.

IRI: https://ekgf.org/ontology/artifact-publication#releasedAt

6.3.23 Target kind§

Label: Target kind

Identifier: ekg-artpub:targetKind

Kind of publication target, such as website, pdf, rdf-download, archive or package.

IRI: https://ekgf.org/ontology/artifact-publication#targetKind

6.3.24 Target URL§

Label: Target URL

Identifier: ekg-artpub:targetUrl

Base URL or destination URL of a publication target.

IRI: https://ekgf.org/ontology/artifact-publication#targetUrl

6.4 Named Individuals§

6.4.1 Artifact Publication Validation Shapes§

Label: Artifact Publication Validation Shapes

Identifier: ekg-artpub:ValidationShapeSet

Instance of: ekg-shape:ShapeSet

Validates publication profiles, release scope and provenance, and release-approval records.

IRI: https://ekgf.org/ontology/artifact-publication#ValidationShapeSet

6.5 Shapes§

6.5.1 Publication Profile Shape§

Label: Publication Profile Shape

Identifier: ekg-artpub:PublicationProfileShape

Validates that a publication profile explicitly selects a family or artifact references using the supported scope alternatives.

IRI: https://ekgf.org/ontology/artifact-publication#PublicationProfileShape

6.5.2 Release Approval Shape§

Label: Release Approval Shape

Identifier: ekg-artpub:ReleaseApprovalShape

Validates an approval record identifying the exact release approved, the approving authority, and the approval time.

IRI: https://ekgf.org/ontology/artifact-publication#ReleaseApprovalShape

6.5.3 Standards Release Shape§

Label: Standards Release Shape

Identifier: ekg-artpub:StandardsReleaseShape

Validates a standards release's family or reference scope, version label, and optional publication and content-provenance records.

IRI: https://ekgf.org/ontology/artifact-publication#StandardsReleaseShape

7.1 Overview§

Authorization Ontology

The EKGF Authorization Ontology.

   Modeling "Role Based Access Control" which is not the same
   as EKG-level entitlement calculation but could be part thereof.

7.2 Classes§

7.2.1 Authorization Group§

Label: Authorization Group

Identifier: ekg-authorization:AuthorizationGroup

A grouping used by authorization rules to express role-based access-control requirements. It is distinct from a persona and does not by itself calculate EKG-wide entitlements.

IRI: https://ekgf.org/ontology/authorization#AuthorizationGroup

7.2.2 Authorization Rule§

Label: Authorization Rule

Identifier: ekg-authorization:AuthorizationRule

A rule associating authorization groups with personas in the role-based access-control model. The vocabulary records these relationships without defining a rule evaluation algorithm.

IRI: https://ekgf.org/ontology/authorization#AuthorizationRule

7.3 Properties§

7.3.1 Has Group§

Label: Has Group

Identifier: ekg-authorization:hasGroup

Associates an authorization rule with an authorization group participating in that rule.

IRI: https://ekgf.org/ontology/authorization#hasGroup

7.3.2 Has Persona§

Label: Has Persona

Identifier: ekg-authorization:hasPersona

Associates an authorization rule with a persona to which the rule relates.

IRI: https://ekgf.org/ontology/authorization#hasPersona

8.1 Overview§

Capability Ontology

A vocabulary for capabilities and capability domains, with example capabilities for sharing data and managing data products. The current vocabulary does not define the relationships assigning capabilities to domains.

8.2 Classes§

8.2.1 Capability§

Label: Capability

Identifier: ekg-capability:Capability

An ability represented in the capability model, such as the ability to share data or manage data products.

IRI: https://ekgf.org/ontology/capability#Capability

8.2.2 Capability Domain§

Label: Capability Domain

Identifier: ekg-capability:CapabilityDomain

A subject area used to organize capabilities in a capability model. This vocabulary does not yet declare the relationship assigning capabilities to a domain.

IRI: https://ekgf.org/ontology/capability#CapabilityDomain

8.2.3 Sub-capability§

Label: Sub-capability

Identifier: ekg-capability:SubCapability

A more specific capability represented at a subordinate level of a capability model. The current vocabulary declares it independently and does not assert a subclass relationship to Capability.

IRI: https://ekgf.org/ontology/capability#SubCapability

8.3 Named Individuals§

8.3.1 Data sharing and marketplace§

Label: Data sharing and marketplace

Identifier: ekg-capability:Data_Sharing_and_Marketplace

Instance of: ekg-capability:Capability

The example capability covering the sharing of data and its provision through a marketplace.

IRI: https://ekgf.org/ontology/capability#Data_Sharing_and_Marketplace

8.3.2 Designing and managing data products§

Label: Designing and managing data products

Identifier: ekg-capability:Designing_and_Managing_Data_Products

Instance of: ekg-capability:SubCapability

The example sub-capability covering the design and management of data products.

IRI: https://ekgf.org/ontology/capability#Designing_and_Managing_Data_Products

9.1 Overview§

Communication Ontology

Models communication recipients separately from people and organizations. Audiences, lists, tags, and campaign snapshots are collections with reified memberships. Consent, withdrawal, suppression, legal classification, and derivation evidence attach to memberships rather than being flattened onto recipients.

9.2 Classes§

9.2.1 Audience§

Label: Audience

Identifier: ekg-communication:Audience

A targeting collection that may cluster recipients, endpoints, tags, lists, channel eligibility, and exclusion rules.

IRI: https://ekgf.org/ontology/communication#Audience

9.2.2 Audience membership§

Label: Audience membership

Identifier: ekg-communication:AudienceMembership

A membership in an audience.

IRI: https://ekgf.org/ontology/communication#AudienceMembership

9.2.3 Campaign audience snapshot§

Label: Campaign audience snapshot

Identifier: ekg-communication:CampaignAudienceSnapshot

An immutable collection of recipients or endpoints resolved for a specific campaign or send.

IRI: https://ekgf.org/ontology/communication#CampaignAudienceSnapshot

9.2.4 Campaign recipient§

Label: Campaign recipient

Identifier: ekg-communication:CampaignRecipient

A frozen membership in a campaign audience snapshot, carrying per-send state and delivery correlation.

IRI: https://ekgf.org/ontology/communication#CampaignRecipient

9.2.5 Communication attempt§

Label: Communication attempt

Identifier: ekg-communication:CommunicationAttempt

One concrete attempt to communicate with a recipient or endpoint through a communication program.

IRI: https://ekgf.org/ontology/communication#CommunicationAttempt

9.2.6 Communication channel§

Label: Communication channel

Identifier: ekg-communication:CommunicationChannel

Controlled transport category such as email, SMS, voice, postal mail, push, webhook, or in-app notification.

IRI: https://ekgf.org/ontology/communication#CommunicationChannel

9.2.7 Communication endpoint§

Label: Communication endpoint

Identifier: ekg-communication:CommunicationEndpoint

A concrete channel address or locator used to reach a recipient.

IRI: https://ekgf.org/ontology/communication#CommunicationEndpoint

9.2.8 Communication program§

Label: Communication program

Identifier: ekg-communication:CommunicationProgram

A reusable communication surface combining channel, purpose, sender policy, authorization policy, and suppression rules.

IRI: https://ekgf.org/ontology/communication#CommunicationProgram

9.2.9 Communication purpose§

Label: Communication purpose

Identifier: ekg-communication:CommunicationPurpose

Controlled purpose such as marketing, transactional, operational, legal notice, support, or security.

IRI: https://ekgf.org/ontology/communication#CommunicationPurpose

9.2.10 Delivery event§

Label: Delivery event

Identifier: ekg-communication:DeliveryEvent

Provider or system event describing the outcome of a communication attempt.

IRI: https://ekgf.org/ontology/communication#DeliveryEvent

9.2.11 Delivery status§

Label: Delivery status

Identifier: ekg-communication:DeliveryStatus

Controlled delivery status such as pending, sent, delivered, bounced, complained, suppressed, unsubscribed, failed, or skipped.

IRI: https://ekgf.org/ontology/communication#DeliveryStatus

9.2.12 Email endpoint§

Label: Email endpoint

Identifier: ekg-communication:EmailEndpoint

An email address endpoint.

IRI: https://ekgf.org/ontology/communication#EmailEndpoint

9.2.13 Email recipient§

Label: Email recipient

Identifier: ekg-communication:EmailRecipient

A recipient addressable by email. This class does not imply that the recipient is a person.

IRI: https://ekgf.org/ontology/communication#EmailRecipient

9.2.14 Group recipient§

Label: Group recipient

Identifier: ekg-communication:GroupRecipient

A recipient representing a group, team, role, or shared function.

IRI: https://ekgf.org/ontology/communication#GroupRecipient

9.2.15 Human recipient§

Label: Human recipient

Identifier: ekg-communication:HumanRecipient

A recipient representing a natural person in a communication context.

IRI: https://ekgf.org/ontology/communication#HumanRecipient

9.2.16 In-app endpoint§

Label: In-app endpoint

Identifier: ekg-communication:InAppEndpoint

An account, user, workspace, or inbox locator for in-application communication.

IRI: https://ekgf.org/ontology/communication#InAppEndpoint

9.2.17 In-app recipient§

Label: In-app recipient

Identifier: ekg-communication:InAppRecipient

A recipient addressable by in-application notification or message center delivery.

IRI: https://ekgf.org/ontology/communication#InAppRecipient

9.2.18 Legal basis§

Label: Legal basis

Identifier: ekg-communication:LegalBasis

A controlled classification for recording a legal basis or exemption associated with a communication purpose, channel, recipient category, and jurisdiction. The classification alone does not establish permission to communicate.

IRI: https://ekgf.org/ontology/communication#LegalBasis

9.2.19 List membership§

Label: List membership

Identifier: ekg-communication:ListMembership

A membership in a recipient list or communication scope.

IRI: https://ekgf.org/ontology/communication#ListMembership

9.2.20 Mailbox recipient§

Label: Mailbox recipient

Identifier: ekg-communication:MailboxRecipient

A recipient representing a mailbox, shared inbox, alias, or distribution address.

IRI: https://ekgf.org/ontology/communication#MailboxRecipient

9.2.21 Marketing program§

Label: Marketing program

Identifier: ekg-communication:MarketingProgram

A communication program whose purpose is marketing.

IRI: https://ekgf.org/ontology/communication#MarketingProgram

9.2.22 Membership§

Label: Membership

Identifier: ekg-communication:Membership

A reified edge connecting a recipient or endpoint to a recipient collection, with status and evidence.

IRI: https://ekgf.org/ontology/communication#Membership

9.2.23 Membership derivation evidence§

Label: Membership derivation evidence

Identifier: ekg-communication:MembershipDerivationEvidence

Evidence that a membership was derived from another collection, tag, rule, import, or operator action.

IRI: https://ekgf.org/ontology/communication#MembershipDerivationEvidence

9.2.24 Membership event§

Label: Membership event

Identifier: ekg-communication:MembershipEvent

Append-only event associated with a membership, such as add, remove, consent, withdrawal, or suppression.

IRI: https://ekgf.org/ontology/communication#MembershipEvent

9.2.25 Membership evidence§

Label: Membership evidence

Identifier: ekg-communication:MembershipEvidence

Evidence or provenance supporting a membership, consent, withdrawal, suppression, or derivation.

IRI: https://ekgf.org/ontology/communication#MembershipEvidence

9.2.26 Membership status§

Label: Membership status

Identifier: ekg-communication:MembershipStatus

Controlled current status of a membership.

IRI: https://ekgf.org/ontology/communication#MembershipStatus

9.2.27 Organization recipient§

Label: Organization recipient

Identifier: ekg-communication:OrganizationRecipient

A recipient representing an organization or other legal entity.

IRI: https://ekgf.org/ontology/communication#OrganizationRecipient

9.2.28 Postal endpoint§

Label: Postal endpoint

Identifier: ekg-communication:PostalEndpoint

A postal address endpoint.

IRI: https://ekgf.org/ontology/communication#PostalEndpoint

9.2.29 Postal recipient§

Label: Postal recipient

Identifier: ekg-communication:PostalRecipient

A recipient addressable by postal mail or courier delivery.

IRI: https://ekgf.org/ontology/communication#PostalRecipient

9.2.30 Push endpoint§

Label: Push endpoint

Identifier: ekg-communication:PushEndpoint

A device, subscription, or token endpoint for push notification delivery.

IRI: https://ekgf.org/ontology/communication#PushEndpoint

9.2.31 Push recipient§

Label: Push recipient

Identifier: ekg-communication:PushRecipient

A recipient addressable by mobile, desktop, or browser push notification.

IRI: https://ekgf.org/ontology/communication#PushRecipient

9.2.32 Recipient§

Label: Recipient

Identifier: ekg-communication:Recipient

An addressable communication target. A recipient may represent a person, organization, group, service, mailbox, or other operational target.

IRI: https://ekgf.org/ontology/communication#Recipient

9.2.33 Recipient collection§

Label: Recipient collection

Identifier: ekg-communication:RecipientCollection

A collection of recipients or endpoints. Lists, tags, audiences, and campaign snapshots are specializations.

IRI: https://ekgf.org/ontology/communication#RecipientCollection

9.2.34 Recipient consent§

Label: Recipient consent

Identifier: ekg-communication:RecipientConsent

Evidence that a recipient or endpoint has consented, or that another lawful basis was captured, for a membership scope.

IRI: https://ekgf.org/ontology/communication#RecipientConsent

9.2.35 Recipient consent withdrawal§

Label: Recipient consent withdrawal

Identifier: ekg-communication:RecipientConsentWithdrawal

Evidence that a recipient withdrew consent or opted out for a membership scope. The membership may remain visible with a non-sendable status.

IRI: https://ekgf.org/ontology/communication#RecipientConsentWithdrawal

9.2.36 Recipient legal category§

Label: Recipient legal category

Identifier: ekg-communication:RecipientLegalCategory

Controlled legal category such as natural person, employee, organization, technical service, group mailbox, or public authority.

IRI: https://ekgf.org/ontology/communication#RecipientLegalCategory

9.2.37 Recipient legal classification§

Label: Recipient legal classification

Identifier: ekg-communication:RecipientLegalClassification

Temporal legal classification of a recipient in a jurisdiction for communication, consent, and retention decisions.

IRI: https://ekgf.org/ontology/communication#RecipientLegalClassification

9.2.38 Recipient list§

Label: Recipient list

Identifier: ekg-communication:RecipientList

A named recipient collection normally used as a communication enrollment or list scope.

IRI: https://ekgf.org/ontology/communication#RecipientList

9.2.39 Recipient suppression§

Label: Recipient suppression

Identifier: ekg-communication:RecipientSuppression

Evidence that future communication is suppressed because of unsubscribe, bounce, complaint, policy, or operator action.

IRI: https://ekgf.org/ontology/communication#RecipientSuppression

9.2.40 Recipient tag§

Label: Recipient tag

Identifier: ekg-communication:RecipientTag

A lightweight classification collection such as special-peer, reviewer, or customer.

IRI: https://ekgf.org/ontology/communication#RecipientTag

9.2.41 Service recipient§

Label: Service recipient

Identifier: ekg-communication:ServiceRecipient

A recipient representing a technical system, webhook, service account, robot, or automation endpoint.

IRI: https://ekgf.org/ontology/communication#ServiceRecipient

9.2.42 SMS endpoint§

Label: SMS endpoint

Identifier: ekg-communication:SmsEndpoint

A phone-number endpoint for SMS or similar text-message delivery.

IRI: https://ekgf.org/ontology/communication#SmsEndpoint

9.2.43 SMS recipient§

Label: SMS recipient

Identifier: ekg-communication:SmsRecipient

A recipient addressable by SMS or similar text-message delivery.

IRI: https://ekgf.org/ontology/communication#SmsRecipient

9.2.44 Tag assignment§

Label: Tag assignment

Identifier: ekg-communication:TagAssignment

A membership assigning a recipient or endpoint to a tag.

IRI: https://ekgf.org/ontology/communication#TagAssignment

9.2.45 Voice endpoint§

Label: Voice endpoint

Identifier: ekg-communication:VoiceEndpoint

A phone-number endpoint for voice calls.

IRI: https://ekgf.org/ontology/communication#VoiceEndpoint

9.2.46 Voice recipient§

Label: Voice recipient

Identifier: ekg-communication:VoiceRecipient

A recipient addressable by voice call.

IRI: https://ekgf.org/ontology/communication#VoiceRecipient

9.2.47 Webhook endpoint§

Label: Webhook endpoint

Identifier: ekg-communication:WebhookEndpoint

A URL or callback endpoint for machine-to-machine communication.

IRI: https://ekgf.org/ontology/communication#WebhookEndpoint

9.2.48 Webhook recipient§

Label: Webhook recipient

Identifier: ekg-communication:WebhookRecipient

A recipient addressable by webhook or machine-to-machine callback.

IRI: https://ekgf.org/ontology/communication#WebhookRecipient

9.3 Properties§

9.3.1 allowed channel§

Label: allowed channel

Identifier: ekg-communication:allowedChannel

A channel allowed or expected for members of a collection.

IRI: https://ekgf.org/ontology/communication#allowedChannel

9.3.2 attempt endpoint§

Label: attempt endpoint

Identifier: ekg-communication:attemptEndpoint

Concrete endpoint used by a communication attempt.

IRI: https://ekgf.org/ontology/communication#attemptEndpoint

9.3.3 attempt recipient§

Label: attempt recipient

Identifier: ekg-communication:attemptRecipient

Recipient targeted by a communication attempt.

IRI: https://ekgf.org/ontology/communication#attemptRecipient

9.3.4 campaign audience§

Label: campaign audience

Identifier: ekg-communication:campaignAudience

Source audience resolved into a campaign snapshot.

IRI: https://ekgf.org/ontology/communication#campaignAudience

9.3.5 captured at§

Label: captured at

Identifier: ekg-communication:capturedAt

Timestamp when consent or lawful-basis evidence was captured.

IRI: https://ekgf.org/ontology/communication#capturedAt

9.3.6 collection purpose§

Label: collection purpose

Identifier: ekg-communication:collectionPurpose

The purpose associated with a list, audience, tag, or snapshot when the collection has a communication scope.

IRI: https://ekgf.org/ontology/communication#collectionPurpose

9.3.7 communication program§

Label: communication program

Identifier: ekg-communication:communicationProgram

Communication program associated with a collection, snapshot, membership, or attempt.

IRI: https://ekgf.org/ontology/communication#communicationProgram

9.3.8 consent membership§

Label: consent membership

Identifier: ekg-communication:consentMembership

Membership scope covered by a consent or lawful-basis record.

IRI: https://ekgf.org/ontology/communication#consentMembership

9.3.9 delivery attempt§

Label: delivery attempt

Identifier: ekg-communication:deliveryAttempt

Communication attempt described by a delivery event.

IRI: https://ekgf.org/ontology/communication#deliveryAttempt

9.3.10 delivery status§

Label: delivery status

Identifier: ekg-communication:deliveryStatus

Delivery outcome status for a delivery event.

IRI: https://ekgf.org/ontology/communication#deliveryStatus

9.3.11 derived from membership§

Label: derived from membership

Identifier: ekg-communication:derivedFromMembership

Links a derived membership to another membership that caused or justified it.

IRI: https://ekgf.org/ontology/communication#derivedFromMembership

9.3.12 effective from§

Label: effective from

Identifier: ekg-communication:effectiveFrom

Timestamp from which a classification, membership status, consent, suppression, or policy is effective.

IRI: https://ekgf.org/ontology/communication#effectiveFrom

9.3.13 effective through§

Label: effective through

Identifier: ekg-communication:effectiveThrough

Timestamp through which a classification, membership status, consent, suppression, or policy is effective.

IRI: https://ekgf.org/ontology/communication#effectiveThrough

9.3.14 endpoint address§

Label: endpoint address

Identifier: ekg-communication:endpointAddress

Channel-specific endpoint address, such as an email address, phone number, postal address key, token, URL, or account identifier.

IRI: https://ekgf.org/ontology/communication#endpointAddress

9.3.15 endpoint channel§

Label: endpoint channel

Identifier: ekg-communication:endpointChannel

The transport channel used by an endpoint.

IRI: https://ekgf.org/ontology/communication#endpointChannel

9.3.16 evidence collection§

Label: evidence collection

Identifier: ekg-communication:evidenceCollection

Collection, tag, list, or audience referenced by membership evidence.

IRI: https://ekgf.org/ontology/communication#evidenceCollection

9.3.17 evidence source§

Label: evidence source

Identifier: ekg-communication:evidenceSource

Source resource, import, operator action, rule, tag, form, webhook, or system fact that supports evidence.

IRI: https://ekgf.org/ontology/communication#evidenceSource

9.3.18 has delivery event§

Label: has delivery event

Identifier: ekg-communication:hasDeliveryEvent

Links an attempt to one delivery event.

IRI: https://ekgf.org/ontology/communication#hasDeliveryEvent

9.3.19 has endpoint§

Label: has endpoint

Identifier: ekg-communication:hasEndpoint

Links a recipient to one concrete channel endpoint.

IRI: https://ekgf.org/ontology/communication#hasEndpoint