On Mon, Feb 3, 2014 at 10:41 AM, Karen Menz <[email protected]> wrote: > <owl:Class rdf:about="Class_1"> > <rdfs:subClassOf> > <owl:Restriction> > <owl:onProperty rdf:resource="prop_1"/> > <owl:someValuesFrom> > <owl:Restriction> > <owl:onProperty rdf:resource="#prop_2"/> > <owl:allValuesFrom rdf:resource="#Class_2"/> > </owl:Restriction> > </owl:someValuesFrom> > </owl:Restriction> > </rdfs:subClassOf> > </owl:Class>
It's easier to understand this if you look at it in a different syntax. E.g., in the Manchester OWL syntax, it's Class1 subClassOf (prop1 some (prop2 only Class2)) It will be easier to understand that if you can use some more descriptive property and class names. E.g,. ThingThatAteAVegetarianDish subClassOf (ateDish some (hasIngredient only Vegetable)) A thing that ate a vegetarian dish is something that ate at least one dish that only had vegetable ingredients. -- Joshua Taylor, http://www.cs.rpi.edu/~tayloj/
