- From: Jim Hendler <hendler@cs.umd.edu>
- Date: Sun, 12 Jan 2003 17:39:33 -0500
- To: Mike Dean <mdean@bbn.com>, Jerome.Euzenat@inrialpes.fr (Jerome Euzenat)
- Cc: www-webont-wg@w3.org
I meant to ask this at the f2f -- in the Guide the example of oneOf does this: ><owl:Class rdf:ID="WineColor"> > <rdfs:subClassOf rdf:resource="#WineDescriptor"/> > <owl:oneOf rdf:parseType="Collection"> > <owl:Thing rdf:about="#White"/> > <owl:Thing rdf:about="#Rose"/> > <owl:Thing rdf:about="#Red"/> > </owl:oneOf> ></owl:Class> and then ><owl:Class rdf:ID="WineColor"> > <rdfs:subClassOf rdf:resource="#WineDescriptor"/> > <owl:oneOf rdf:parseType="Collection"> > <WineColor rdf:about="#White" /> > <WineColor rdf:about="#Rose" /> > <WineColor rdf:about="#Red" /> > </owl:oneOf> ></owl:Class> > with text simply describing each as an alternative. If one of these is preferred by most tools, I wonder if the Guide might add a word or two to say "the preferred way" -- so the question is really, do we care? Do we want to recommend one or the other? -JH p.s. Jerome makes a good point, if oneOf can be used for datatypes, we should show an example (perhaps in the datatype section) since this will be a relatively complex construction - but very useful (use case: saying a value must be the string "a", the string "b", the string "c" or the string "d" would be very valuable in recognizing legal answers for your online 'Who wants to be a millionaire') -JH -- Professor James Hendler hendler@cs.umd.edu Director, Semantic Web and Agent Technologies 301-405-2696 Maryland Information and Network Dynamics Lab. 301-405-6707 (Fax) Univ of Maryland, College Park, MD 20742 240-731-3822 (Cell) http://www.cs.umd.edu/users/hendler
Received on Sunday, 12 January 2003 17:40:14 UTC