I hope it is in order to cc: peter. I have been looking at S&AS and found a small problem. While I do not believe this would cause actual interoperability problems, it might be better if we could address it before Rec. I am open to being told I am being too picky. Section 4.2 fails to mention that built-in annotation properties and ontology properties can only be used as such. It appears to be the intent of [[ There are several built-in annotation properties in OWL, namely owl:versionInfo, rdfs:label, rdfs:comment, rdfs:seeAlso, and rdfs:isDefinedBy. In keeping with their definition in RDF, rdfs:label and rdfs:comment can only be used with data literals. There are also several built-in ontology properties; they are owl:imports, owl:priorVersion, owl:backwardCompatibleWith, and owl:incompatibleWith. Ontology annotations that use owl:imports have the extra effect of importing the target ontology. ]] in section 2.1 but I suspect there is still a (perverse?) reading which notes that it is not prohbited to use such things as e.g. an owl:ObjectProperty. (If that is the intended reading, I apologise). I wonder whether the text in 4.2 might benefit from a) making the text in 2.1 linkable and highlighting "built-in annotation properties" and "built-in ontology properties" (i.e. defining the terms) b) modifying the defn of separated vocabulary poitn 3 from [[ the ontologies in O only use the class-only vocabulary as class IDs; only use the datatype-only vocabulary as datatype IDs; only use rdfs:Literal in data ranges; only use the property-only vocabulary as datavaluedProperty IDs, individualvaluedProperty IDs, or annotationProperty IDs; and do not mention any disallowed vocabulary. ]] to [[ the ontologies in O only use the class-only vocabulary as class IDs; only use the datatype-only vocabulary as datatype IDs; only use rdfs:Literal in data ranges; only use the property-only vocabulary as datavaluedProperty IDs, individualvaluedProperty IDs, annotationProperty IDs *** or ontologyPropertyIDs; only use the built-in annotation properties as annotationProperty IDs; only use the built-in ontology properties as ontologyProperty IDs; *** and do not mention any disallowed vocabulary. ]] Combining with my earlier proposal [1] in response to Holger we would get [[ the ontologies in O, *** except as the values of annotations, *** only use the class-only vocabulary as class IDs; only use the datatype-only vocabulary as datatype IDs; only use rdfs:Literal in data ranges; only use the property-only vocabulary as datavaluedProperty IDs, individualvaluedProperty IDs, annotationProperty IDs *** or ontologyPropertyIDs; only use the built-in annotation properties as annotationProperty IDs; only use the built-in ontology properties as ontologyProperty IDs; *** and do not mention any disallowed vocabulary. ]] Jeremy [1] http://lists.w3.org/Archives/Public/www-webont-wg/2003Dec/0063Received on Friday, 9 January 2004 06:17:22 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:03 GMT