kmp>Admin No edit summary |
kmp>Admin No edit summary |
||
| Line 1: | Line 1: | ||
{{concept | |||
|parent=HZ University of Applied Sciences | |||
}} | |||
{{BB Hero d | {{BB Hero d | ||
|heading=KMP | |heading=KMP | ||
| Line 9: | Line 12: | ||
|contact button link= | |contact button link= | ||
}} | }} | ||
=== 1. Using SKOS in SMW === | === 1. Using SKOS in SMW === | ||
SKOS (Simple Knowledge Organization System) is based on a few core properties: | SKOS (Simple Knowledge Organization System) is based on a few core properties: | ||
Revision as of 16:03, 14 October 2025
KMP
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.