kmp>Admin Created blank page |
kmp>Admin No edit summary |
||
| Line 1: | Line 1: | ||
=== 1. Using SKOS in SMW === | |||
SKOS (Simple Knowledge Organization System) is based on a few core properties: | |||
* <code>skos:Concept</code> — your entities (projects, docs, subdocs) can all be modeled as concepts. | |||
* <code>skos:prefLabel</code> — the main human-readable label (your “header”). | |||
* <code>skos:broader</code> / <code>skos:narrower</code> — parent–child hierarchy. | |||
* <code>skos:related</code> — cross-links. | |||
SMW supports RDF export, so if you model your concepts with these properties, you can stay SKOS-compliant. | |||
---- | |||
=== 2. Modeling in SMW === | |||
Define SMW properties that map directly to SKOS terms: | |||
* <code>Property:PrefLabel</code> → <code>skos:prefLabel</code> (Text) | |||
* <code>Property:Broader</code> → <code>skos:broader</code> (Page) | |||
* <code>Property:Narrower</code> → <code>skos:narrower</code> (Page, inverse of Broader) | |||
Optionally, you can use SMW’s <code>Equivalent URI</code> to bind them directly to SKOS URIs so RDF export matches SKOS out of the box. | |||
Revision as of 17:28, 4 October 2025
1. Using SKOS in SMW
SKOS (Simple Knowledge Organization System) is based on a few core properties:
skos:Concept— your entities (projects, docs, subdocs) can all be modeled as concepts.skos:prefLabel— the main human-readable label (your “header”).skos:broader/skos:narrower— parent–child hierarchy.skos:related— cross-links.
SMW supports RDF export, so if you model your concepts with these properties, you can stay SKOS-compliant.
2. Modeling in SMW
Define SMW properties that map directly to SKOS terms:
Property:PrefLabel→skos:prefLabel(Text)Property:Broader→skos:broader(Page)Property:Narrower→skos:narrower(Page, inverse of Broader)
Optionally, you can use SMW’s Equivalent URI to bind them directly to SKOS URIs so RDF export matches SKOS out of the box.