W3C home > Mailing lists > Public > public-owl-wg@w3.org > October 2007

RE: OWL use cases

From: Conrad Bock <conrad.bock@nist.gov>
Date: Tue, 23 Oct 2007 18:41:12 -0400
To: "'Alan Ruttenberg'" <alanruttenberg@gmail.com>
Cc: <public-owl-wg@w3.org>
Message-ID: <012a01c815c5$d18034c0$b3200681@MEL.NIST.GOV>

Alan,

 >  I'm trying to better understand the uses you describe. What would be
 >  especially helpful would be to write up the OWL or pseudo-owl you
 >  would like to see, followed by an english description of what it is
 >  supposed to mean, and what one should conclude from it (some of the
 >  entailments). This might be most productively done on one or more
 >  wiki pages. Below I'll indicate some areas where I am having
 >  difficulty understanding your examples.

Sure, see below.

 >  (ps. consider using the Wiki and just announcing the Wiki page here.
 >  Individuals can subscribe to get email when any Wiki page changes,
 >  and so by doing so we accommodate those who prefer less email, while
 >  enabling those who would prefer more.)

For all the discussion or just the detailed examples?  Seems like most
discussion is happening on the list.

 >  On Oct 19, 2007, at 4:47 PM, Conrad Bock wrote:
 >  
 >  > Here are a couple uses of OWL I think are important to support:
 >  >
 >  >   - Specializing Class and Property.

 >  This can be done in OWL Full now. Do you mean that OWL-DL/OWL 1.1 DL
 >  should have this ability too?

Yes, and basic DL reasoning works on it also in the tools we've tried.
See example at
http://www.w3.org/2007/OWL/wiki/index.php?title=OWLMetamodeling,
entry [1].  Just wanted to check this would continue under OWL 1.1.

 >  > This is critical to modeling manufactured products and processes,
 >  > to ensure product and process models support subclassing, and
 >  > classification of individuals (eg, individuals corresponding to
 >  > actual cars and actual executing processes).

 >  It would be helpful to get some more motivation/explanation of how
 >  the feature connects to the use cases. Off the top of my head, I
 >  don't see why this can't be done with standard classes and
 >  properties.

See product modeling example on
http://www.w3.org/2007/OWL/wiki/index.php?title=OWLMetamodeling.  can
give one for process modeling if it would be useful.

 >  > Current tools support this, but a message from Bijan (through
 >  > Evan) said "owl:Class" in OWL 1 is part of the "disallowed
 >  > vocabulary", ie, it can't be mentioned in an axiom, like one
 >  > establishing a subclass.  Since instances of subclasses of
 >  > owl:Class (Property) are classes (properties), it seems natural
 >  > for these instances to be treated like any other class (property).

 >  If I understand the current situation, they would be in OWL Full.

Agreed, but see above about OWL DL.

 >  > - OWL Full, in particular, having Class and Property be
 >  >     nondisjoint.

 >  An example of what you want to accomplish with this would help.

 >  >   - RDF Statements (reified triples).
 >  >     These are important together for specializing product 
 >  models with
 >  >     properties that "expand" to a network of other objects and
 >  >     properties in subclasses.

See entry [2] at
http://www.w3.org/2007/OWL/wiki/index.php?title=OWLMetamodeling.

Conrad
Received on Tuesday, 23 October 2007 22:41:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:26 GMT