semaphore-taxonomy

Semaphore Taxonomy Authoring

Build order (follow exactly — steps 5 and 6 are the ones people miss)

1. Check connectivity — semaphore_status, semaphore_studio_status
2. Create the model — semaphore_kmm_model_create(name=…, default_namespace=…) → model URI is model:<Name>
3. Author the SKOS Turtle — start from templates/taxonomy-skeleton.ttl
4. Load it — semaphore_kmm_skos_load with skos_content=<turtle>
5. Validate structure — semaphore_taxonomy_validate
6. ⚠ Add SKOS-XL reification — REQUIRED, immediately after loading
7. Fix plain-SKOS publish config — semaphore_publish_config_fix_plain_skos
8. Publish — semaphore_publish(wait_for_completion=true)
9. Confirm active — semaphore_publish_sets shows the model (lowercased) as ACTIVE
10. Verify — semaphore_classify(content=…, threshold=0) on representative text

⚠ The ConceptScheme URI convention

The ConceptScheme URI must be {namespace}{ModelId}Taxonomy. For a model named Example in namespace http://example.com/tax/, that is http://example.com/tax/ExampleTaxonomy.

Get this wrong and the publish appears to succeed but emits one rule — for the scheme root — instead of one per concept.

@prefix ns: <http://example.com/tax/> .
ns:ExampleTaxonomy a skos:ConceptScheme ;
    skos:prefLabel "Example Taxonomy"@en ;
    skos:hasTopConcept ns:TopConcept1 .

⚠ SKOS only — no OWL

KMM supports SKOS, not OWL. Loading an OWL ontology yields 0 concepts with no obvious error. Convert first:

OWL	SKOS
owl:Class	skos:Concept
rdfs:subClassOf	skos:broader
owl:Ontology	skos:ConceptScheme

sem:guid is generated automatically by KMM during semaphore_kmm_skos_load — no manual INSERT needed.

Verifying a load

semaphore_kmm_sparql(model_uri="model:<Name>",
  query="PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
         SELECT (COUNT(?c) AS ?n)
         WHERE { GRAPH <urn:x-evn-master:<Name>> { ?c a skos:Concept } }")