- From: Bob Morris <morris.bob@gmail.com>
- Date: Fri, 22 Feb 2013 00:01:47 -0500
- To: public-openannotation <public-openannotation@w3.org>
Ummm, in the Feb 8 http://openannotation.org/spec/core/appendices.html#ExtendingMotivations the example avows oa:motivationScheme a skos:ConceptScheme ; and then puts some skos data on it, presumably in order to support the skos breadth comparisons to oa:editing. Rather than expect such triples oa:motivationScheme a skos:ConceptScheme ; oa:editing a oa:Motivation ; skos:inScheme oa:motivationScheme ; skos:prefLabel "Editing"@en. to be in extension code, I would think such triples are actually meant to be part of the spec in the case of every Section 2.3 declared Motivation. In this case, I think I would also expect that for the most part, it would be discouraged for extensions to change much of the skos in these Section 2.3 Motivations except, perhaps the skos:prefLabel. In other words, I imagine that Appendix is not really inviting the world to put whatever skos semantics it wishes on the Section 2.3 instances. Am I confused? Bob -- Robert A. Morris Emeritus Professor of Computer Science UMASS-Boston 100 Morrissey Blvd Boston, MA 02125-3390 IT Staff Filtered Push Project Harvard University Herbaria Harvard University email: morris.bob@gmail.com web: http://efg.cs.umb.edu/ web: http://wiki.filteredpush.org http://www.cs.umb.edu/~ram === The content of this communication is made entirely on my own behalf and in no way should be deemed to express official positions of The University of Massachusetts at Boston or Harvard University.
Received on Friday, 22 February 2013 05:02:15 UTC