SKOS taxonomies
The RDF File Collector and
SPARQL Endpoint Collector retain SKOS
assertions with source provenance. Repository scanners
discover RDF files in local or remote Git sources. A taxonomy does not
need an invented OWL ontology declaration. Register its skos:ConceptScheme as
a vocabulary in a publication family and use the normal
publication build-family workflow.
A standalone scheme supplies its title and namespace metadata, for example:
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
<https://example.org/business> a skos:ConceptScheme ;
skos:prefLabel "Business taxonomy"@en ;
skos:definition "The business vocabulary maintained by this project."@en ;
sh:declare [ sh:prefix "business" ;
sh:namespace "https://example.org/business/" ] .
<https://example.org/business/product> a skos:Concept ;
skos:prefLabel "Product"@en ;
skos:altLabel "Offering"@en ;
skos:definition "An item offered to customers."@en ;
skos:inScheme <https://example.org/business> .
Namespace metadata can also live in the publication definitions. Publication settings, authority, license, scope, and family registration work as they do for ontology publications. The existing command and JSON counters retain their ontology-oriented names when a selected vocabulary is a concept scheme.
See the input and the result
In the runnable example, Data product is narrower than Product, has an external mapping, and belongs to an ordered portfolio. Compare the Turtle source files with the generated taxonomy reference and PDF. Open Concepts for the definitions and hierarchy links, then Collections for the retained portfolio order.
Supporting collectors
The RDF File Collector reads SKOS assertions. Repository scanners discover RDF files; the SPARQL Endpoint Collector can supply assertions from a configured query. Vocabulary recognition then selects declared schemes, concepts, and collections for documentation. There is no separate SKOS file format or a collector that infers a taxonomy from arbitrary text.
Reference content
Concepts appear inside their Concept Scheme in the HTML reference, table of
contents, and PDF. Membership comes from explicit skos:inScheme,
skos:topConceptOf, or skos:hasTopConcept statements. The scheme includes linked
navigation using the asserted skos:broader and skos:narrower relationships.
GraphArch does not assign scheme membership from a broader-concept relationship.
A concept can belong to several schemes. It is listed in each, with one complete reference entry and links from the other schemes. Concepts without a documented scheme have a separate section. Hierarchy cycles appear as review warnings in the scheme and the quality appendix; navigation links retain the repeated concept without recursively expanding the cycle.
Ordered Collections retain their RDF member-list order. The
ga:referenceSection hints can rename or reorder the scheme and collection
sections using the kinds schemes and collections; concepts controls the
standalone scheme's concept section.
English skos:prefLabel takes precedence over rdfs:label. Ordinary reference
entries retain competing annotations for quality review.
A standalone vocabulary's heading metadata must currently be unambiguous.
Definitions, alternative and hidden labels,
notations, notes, examples, hierarchy links, scheme membership, collections,
and mappings remain source assertions in the KG. Reference entries show retained
facts and link to other documented resources. Markdown descriptions use the
same annotation support as ontology terms.
For a standalone scheme, term discovery reads the pinned collected-project
snapshot, so concepts can be supplied in separate files. Explicit skos:inScheme,
skos:topConceptOf, and skos:hasTopConcept links select typed resources even
outside the declared namespace. Typed resources in the declared namespace are
also documented. No membership, inverse links, hierarchy closure, or external
imports are inferred.
SKOS schemes embedded in an OWL ontology are documented within that ontology's reference. A standalone source file currently supports one declared scheme; multiple standalone schemes in one file, overlapping selected vocabulary ownership, and ambiguous namespace declarations fail explicitly. Separate scheme declarations into distinct files and give each selected vocabulary unambiguous namespace metadata.
Publication formats
Taxonomies use the specification, paginated specification, and bookshelf renderers. A standalone scheme can form a book with its own PDF. Publication works from an exported and restored KG after deleting the original source files. This is vocabulary-reference documentation; it does not add a dedicated taxonomy browsing or print renderer: interactive tree navigation, a specialist A–Z index, and taxonomy-specific print layouts are not part of this current reference presentation.
Dedicated showcase
The showcase gallery includes a standalone business-data taxonomy with a specification, PDF, and downloadable KG. Run it locally with:
cargo run --example publish_showcase -- --skos
Its self-contained Turtle is in examples/skos.