owl:sameAs temptation

Hi,

I'm sure this is talked somewhere, I'd love a pointer if you know any:

I often see resources of type owl:Class get paired with resources of 
type owl:Thing using owl:sameAs. As far as I understand, this is 
incorrect since domain and range of owl:sameAs should be owl:Thing.

I'm tempted to change my resource that is a skos:Concept 
skos:exactMatch'ed with a resource of type owl:Thing, and use 
owl:sameAs. Sort of like "everyone else is doing it, it should be okay", 
and "don't need to fear the thought police".

However, I don't wish to do that with a clear conscience, hence, I'd 
appreciate it if anyone can shed some light here for me and help me 
understand to make an informed decision based on reason (no pun intended).

Related to this, I was wondering whether it makes sense to claim a 
resource to be of type owl:Class as well as of type owl:Thing, where may 
be appropriate, or one could get away with it e.g., a country. If this 
is okay, I imagine it is okay to use owl:sameAs for the subject at hand 
and point to yet another thing.

Thanks all.

-Sarven

Received on Wednesday, 7 March 2012 06:43:56 UTC