EKGF Ontologies / EKGF Ontologies

EKGF Editor's Draft

EKGF Ontologies

An ontology family for enterprise knowledge graphs: concepts, use cases, stories, artifacts, governance, publication and lifecycles.

EKGF Editor's Draft

Status of this document

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. Family overview§

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

Counts show distinct documented resources explicitly declared as classes or properties; multiple declarations of the same resource count once.

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.

Classes
21
Properties
62

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.

Classes
5
Properties
12

B. Document provenance§

This record identifies the generator and the source revisions collected for this publication. Committers below describe recent repository changes, rather than authorship of the whole document.

Generated by
Grapharch 0.2.26 (build 78)
Build operator
Build operator was not recorded.

Generator source commit: 615760949a54246d2cb29b1b164478fa3ed0ccdf

Generator build: 78

Source repository

Repository
https://github.com/EKGF/ekg-ontologies
Source commit
3a07397e139d134f87a08403d784efc1ccbb2003
Source state
Local working tree observed against this commit; collected files may contain uncommitted changes.

Recent committers

Up to five commits, following the first-parent history from the source commit. This is not the full contributor list.

  1. Jacobus Geluk
    3a07397e139d134f87a08403d784efc1ccbb2003

Search this specification