gist namespace policy
policies/gist-namespace-policyChecked by automation only
still a draft
Written 2026-10-27 by ktl-librarian (automation). Last checked 2026-10-28 by ktl-librarian (automation).
The full record
- Checks
- 2026-10-28 by
ktl-librarian(automation)
- 2026-10-28 by
- Sources
- References
- About
- Source
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/lmodel/gist/knowledge/policies/gist-namespace-policy- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
gist namespace policy
Section titled “gist namespace policy”Semantic Arts publishes gist under CC BY 4.0 and adds two conditions: “any terms used from gist remain in the gist namespace”, and “you do not define your own terms in the gist namespace” (gist README, release 14.1.0). This repository holds to both.
| Prefix | Namespace | Holds |
|---|---|---|
gist |
https://w3id.org/semanticarts/ns/ontology/gist/ |
gist’s classes and properties, under their own IRIs |
gistd |
https://w3id.org/semanticarts/ns/data/gist/ |
gist’s named individuals |
gist_linkml |
https://w3id.org/lmodel/gist/ |
what the LinkML rendering adds: the schema documents, the GistThing mixin, the types for the datatypes linkml:types lacks, the enums, the subsets, the SHACL shapes, and the LinkML element definitions that the OWL links to gist’s classes with skos:exactMatch |
Three mechanisms enforce it:
- Converter.
scripts/gist_to_linkml.pybindsgistto Semantic Arts’ namespace, writesclass_uriandslot_uriasgist:CURIEs, and sets every module’sdefault_prefixtogist_linkml, so an element without its own IRI takes lmodel’s namespace (transform). - Generator flags. The published OWL comes from a separate
gen-owlcall that takes its flags fromLINKML_GENERATORS_OWL_ARGSinconfig.public.mk, among them--no-use-native-uris --default-permissible-value-type owl:NamedIndividual..linkml/generators.yamlgivesgen-projectthe same OWL settings, and givesgen-shacluse_class_uri_names: falsewith the suffixShape(generated artefacts). - Tests.
TestGistNamespaceintests/test_schema_validation.pyandTestGistIrisInArtifactsintests/test_generated_artifacts.pycheck the schema modules and the committed OWL and SHACL against the vendored release, and run in CI throughjust test.