kmp>Admin No edit summary |
kmp>Admin No edit summary |
||
| Line 1: | Line 1: | ||
{{BB Hero d | |||
|heading=Technology Water Environment | |||
|lead= | |||
|summary=Kennis leveren voor duurzame innovatie van de vrijetijdssector | |||
Applied Research Center Vitality is dé kennispartner van de Zeeuwse vrijetijdssector. Wij doen onderzoek en realiseren projecten. Zo geven wij inzicht en creëren perspectieven. Dat doen we met ondernemers, inwoners, overheden en maatschappelijke organisaties. Wij geloven in de kracht van co-creatie en bedenken en ontwikkelen samen kennis, samenwerkingsverbanden en praktijkcasussen. | |||
|image=Night-photograph-2183637_1280.jpg | |||
|button text= | |||
|button link= | |||
|contact button text= | |||
|contact button link= | |||
}} | |||
{{concept | {{concept | ||
|parent=HZ University of Applied Sciences | |parent=HZ University of Applied Sciences | ||
Revision as of 13:08, 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.