Ontology families and modules

Example: group two vocabularies into a module

Declare the two ontologies in their own RDF source files, then add this module membership to the family's RDF:

@prefix ex: <https://example.org/vocabularies/> .
@prefix ga: <https://ekgf.org/ontology/grapharch#> .
@prefix dct: <http://purl.org/dc/terms/> .
ex:Commerce a ga:OntologyModule ;
    dct:title "Commerce"@en ;
    dct:hasPart ex:Customers, ex:Products .

Given a configured family containing these two vocabularies, this declaration groups them into Commerce. A bookshelf publication can give that module a book with Customers and Products chapters and its own PDF. The declaration above describes membership; the family workflow supplies the registry and target configuration.

For an existing family, inspect the EKGF source repository and open the generated family reference. Choose an ontology from the overview, then follow a reference into another ontology. Bookshelves explains the modular output option.

Supporting collectors

The RDF File Collector retains family registry and module assertions. Local and remote repository scanners discover the member source files and dispatch RDF-file collectors. An explicit SPARQL Endpoint Collector can supply the same assertions from a service. Family discovery uses the collected declarations to determine membership; a directory name alone is not membership evidence.

Recognised families

A family publication documents several selected vocabularies together. Each vocabulary keeps its identity, namespace, terms, and source provenance. Family membership is declared through the Artifact Governance registry: a family has references or artifacts that identify its members. GraphArch does not assume that every RDF file in a repository belongs to one family.

The current family pipeline accepts OWL ontology declarations and standalone SKOS concept schemes. A source file currently declares at most one selected ontology or standalone scheme; the SKOS guide explains standalone scheme selection. Cross-reference links connect the resources documented in the selected family.

Explicit modules

Collectors recognise ga:OntologyModule and the native FIBO Module type:

<https://spec.edmcouncil.org/fibo/ontology/FND/Utilities/AnnotationVocabulary/Module>

For explicitly typed modules, dct:hasPart supplies membership links to named ontologies or nested modules. Native assertions remain intact, while the collector retains normalised module membership for publication planning. Directories and file names alone do not create modules.

Modules provide another level of reading structure above their ontologies. They can appear in a family reference, a paginated site, or a bookshelf whose module books have independent specifications and PDFs. Membership cycles and references to uncollected members are reported as errors instead of creating a partial family silently.

Configure and publish

See Publish an ontology family for source configuration, registry reuse, authority roles, repository sources, and CLI commands. See Bookshelves and module books for the publication model suited to large modular families.

Search documentation

Enter words to search this site.