Need a role descrption based on the "cross product" of two concepts

[GoogleCodeExporter]

Suppose we need to define a role called "fatherOf" which is a subrole 
of "parentOf". Would like the ability to define it as follows:

of course, subPropertyOf(father_of, parent_of)
But a more precise specification could be:

fatherOf = parentOf INTERSECTION crossProduct(Male, Person)

Another approach could be:

fatherOf = parentOf AND (ALL inverse(parentOf) Male)
However, I am not sure if the above is a well defined OWL 1.1 expression 
as it sort of mixes concept and role descriptions.

Look forward to suggestions on this issue.

Original issue reported on code.google.com by kashyap....@gmail.com on 23 May 2007 at 10:39

[GoogleCodeExporter]

You are asking for the ability to define roles.

A similar definition would be 
brother = sibling INTERSECTION range(Male)
using range(x) as a shorthand for crossProduct(owl:Thing,x)

This expands expressive power (I'm pretty sure).  I don't know whether there is 
a
reasoning algorithm for this construct.

Original comment by pfpschne...@gmail.com on 11 Oct 2007 at 2:37

• Changed title: Need a role descrption based on the "cross product" of two concepts

[GoogleCodeExporter]

Peter,

Thanks for the response. 
Agree with you is that what I am looking for is role definitions.

So the other thing you bring up is that are we focused only on reasoning as a 
functionality?

Would we want to consider other functionalities such as "loss-less round trip 
and 
model interchange" or querying and data retrieval in addition to reasoning?

Original comment by kashyap....@gmail.com on 11 Oct 2007 at 2:52

[GoogleCodeExporter]

Clarification to comment 1:

The shorthand is confusing.  I meant to define brother as "those sibling
relationships whose object is Male".

Original comment by pfpschne...@gmail.com on 12 Oct 2007 at 2:15

[GoogleCodeExporter]

Yes, there are other things that need to be considered besides reasoning.  
However,
without the ability to do reasoning (reasonably) effectively, how are you going 
to do
the other things you want?  It seems to me that data retrieval is a kind of
reasoning, and lossless round-tripping depend on reasoning.

Original comment by pfpschne...@gmail.com on 12 Oct 2007 at 2:18

[GoogleCodeExporter]

As far as querying and data retrieval is concerned, there have been effective 
and 
scalable ways of specifying algebras and coming up with query optimization 
techniques. Would view this as an alternative model of computation in contrast 
to 
reasoning.

I get the feeling that I am now going out of scope for the WG, so feel free to 
scope this discussion:

Would it make sense to consider say an algebra underlying OWL 1.1 with the goal 
of 
identifying optimizations for data and query retrieval? Of course the tableaux 
technique seeks to optimize an inference operation and there might be some 
common 
ground between the two approaches?

Original comment by kashyap....@gmail.com on 12 Oct 2007 at 2:26

[GoogleCodeExporter]

Response to comment 3:

Let's park the issue of role definitions for now.

Is it possible to specify "those sibling
relationships whose object is Male"

Will range(brother) = Male
and brother subPropertyOf sibling do the trick?

Original comment by kashyap....@gmail.com on 12 Oct 2007 at 2:29

[GoogleCodeExporter]

Original comment by pfpschne...@gmail.com on 24 Oct 2007 at 9:02

• Changed state: Migrated