This document demonstrates how a forked OCG repository can publish a human-oriented specification alongside its ontology, shapes, examples, graph, reference page, and generated term pages.
This is an unofficial example document. Replace this source file with
the ReSpec document for your own vocabulary when enabling the
features.specPage option.
The Example Capability Vocabulary describes capabilities, requirements,
constraints, and audiences using the namespace
https://example.org/ecv#. The generated companion site
derives its reference and graph views from the configured ontology.
A capability can be declared as ecv:Capability, linked to
requirements with ecv:hasRequirement, and optionally
associated with ecv:Constraint resources.
@prefix ecv: <https://example.org/ecv#> .
@prefix ex: <https://example.org/data/> .
ex:capability
a ecv:Capability ;
ecv:hasRequirement ex:authRequirement .
Set sources.spec to this document or another ReSpec source
file, then set features.specPage to true. The
build publishes it at spec/index.html and adds
Specification to the generated navigation.