Hi Mike; I went over portions of the guide document. I have the following comments/questions. Apologies if those were already covered on the mailing list. In the section titled "design for use" ... "but the that describe a set of individuals, and individuals are the members of those sets" I found myself wondering if individuals are the same as instances of these classes. If so, why not use instances to explain individuals. In section "simple property", hasWineDescriptor has a range another objectproperty? On page No. 14: "It is now possible to expand the definition of Wine to include the notion of regions..." <owl:Class rdf:ID="Wine"> <rdfs:subClassOf rdf:resource="#PotableLiquid"/> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="#madeFromGrape"/> <owl:minCardinality>1</owl:minCardinality> </owl:Restriction> </rdfs:subClassOf> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="#locatedIn"/> <owl:minCardinality>1</owl:minCardinality> </owl:Restriction> </rdfs:subClassOf> ... </Class> Earlier in the document, you had the following: <owl:Class rdf:ID="Wine"> <rdfs:subClassOf rdf:resource="#PotableLiquid"/> <rdfs:label xml:lang="en">wine</rdfs:label> <rdfs:label xml:lang="fr">vin</rdfs:label> ... </owl:Class> is that legal? Know that label information is missing above.Received on Wednesday, 20 November 2002 17:07:23 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:36 GMT