Title:
State: RAISED OPEN PENDING POSTPONED SUBSUMED CLOSED
Product: All RDFa Recipes SKOS VM
Raised By: Everyone Abhishek Rungta Alistair Miles Antoine Isaac Ben Adida Bernard Horan Clay Redding Dan Brickley Daniel Maycock Daniel Rubin David Peterson Diego Berrueta Ed Summers Elisa Kendall Fabien Gandon Francesco de Leo Guus Schreiber Jan Henke Jeremy Carroll Jon Phipps Justin Thorp Justin Thorp Manu Sporny Margherita Sini Michael Hausenblas Mirghani Mohamed Quentin Reul Rachel Yager Ralph Swick Sean Bechhofer Siegfried Handschuh Simone Onofri Thomas Baker Vit Novacek
Description: SKOS currently has 7 "documentation"/"note" properties: skos:note, skos:scopeNote, skos:defition, skos:historyNote, skos:editorialNote, skos:changeNote, skos:example. In the SKOS Core Guide <http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102>, 3 different design patterns are allowed for these properties -- "documentation as an RDF literal", "documentation as a related resource description", and "documentation as a document reference". Do we continue to allow these different design patterns? If we do, we have to accept a complex range for these properties. Is that OK? How should we formally specify that?
Add notes: