m Text replacement - "BB Hero d" to "Heading" |
No edit summary |
||
| Line 2: | Line 2: | ||
|parent=HZ University of Applied Sciences | |parent=HZ University of Applied Sciences | ||
}} | }} | ||
{{Heading | {{Heading a | ||
|heading | |heading=HZ Kennis Manamagement | ||
|image=Het Groene Woud.jpg | |||
|image= | |||
}} | }} | ||
=== 1. Using SKOS in SMW === | === 1. Using SKOS in SMW === | ||
Revision as of 18:01, 10 November 2025
KMP
HZ Kennis Manamagement
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.