Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
What BioPAX communicates and how to extend OWL to help it (was: BioPAX Boston meeting, 11 October 2007)
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Oliver Ruebenacker  
View profile  
 More options Oct 12 2007, 12:26 pm
From: "Oliver Ruebenacker" <cur...@gmail.com>
Date: Fri, 12 Oct 2007 12:26:39 -0400
Local: Fri, Oct 12 2007 12:26 pm
Subject: What BioPAX communicates and how to extend OWL to help it (was: BioPAX Boston meeting, 11 October 2007)
     Dear friends,

  I think the paper accurately describes the tensions surrounding
BioPAX and I like the proposals to extend OWL with one caveat: I would
not propose them as extensions of OWL, but as a separate layer.

  The extensions are very useful and easily implemented in principle,
but deeply clash with OWL principles. As the authors understand, they
do not freely blend with OWL reasoning. The suggested restrictions do
not behave like established OWL restrictions:

  - Usually in OWL, class restrictions are inherited to subclasses,
but the suggested restriction of no direct instances is not.

  - Usually, OWL reasoning can continue at any point, but some
proposed extensions are intended to be used after established OWL
reasoning has finished.

  - Usually, OWL reasoning does not identify something as incomplete,
because in an open world there always might be data somewhere that
completes it

  Therefore, I suggest to introduce the extensions as a separate
layer: They deserve their own name (maybe OWLCAGE?) and their own
syntax to avoid confusion.

  OWLCAGE reasoning builds on OWL reasoning and introduces new
assumptions. While OWL makes only conclusions that are still valid
when new data is added (open world assumption), OWLCAGE reasoning
makes conclusions valid only for a certain set of data (closed world
assumption). While OWL has no notion of completeness, OWLCAGE has a
well-defined notion that the present set of data is complete for a
particular purpose.

     Take care
     Oliver

On 10/10/07, Dan Corwin <d...@lexikos.com> wrote:

--
Oliver Ruebenacker, Post-Doc Researcher
Theoretical Biological Physics and Soft Statistical Mechanics
Cell Biology at UConn Health Center and Physics at Harvard
http://people.deas.harvard.edu/~oliver/

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google