You're right, Dave--thanks for the correction!
And thanks to Bernard for the additional case. Though there might be a problem with
owl:hasValue and "it does not prevent an instance of such a class to belong to
another skos:ConceptScheme". My previous owl:someValuesFrom was perhaps a bit more
fi
Hi all
I'm with Antoine and Dave on this - as previously written (I think).
owl:hasValue is indeed a nice and too much overlooked OWL construct
allowing to define a class based on any property-value pair, e.g.,
"A "Blue Thing" is a Thing of which property "color" has value "Blue"
ex:BlueThing a
On 28/08/12 20:39, Antoine Isaac wrote:
Sorry, my owl:someValuesFrom should have been owl:allValuesFrom, I guess.
Actually I think owl:someValuesFrom is right though the easiest
construct is owl:hasValue :
some:codeAConcept owl:equivalentClass [
owl:intersectionOf ( skos:Concept