Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[lego] occurs_in inferences #74

Open
ShahimEssaid opened this issue Feb 2, 2015 · 0 comments
Open

[lego] occurs_in inferences #74

ShahimEssaid opened this issue Feb 2, 2015 · 0 comments

Comments

@ShahimEssaid
Copy link

From cmung...@gmail.com on July 24, 2013 15:34:15

If a reaction instance R is part of a process instance P, and that process
instance occurs P in some C, then the yellow box should should show C
for the reaction R too (unless a more specific one is specified).

The challenge here is inferring superclass expressions (e.g. "occurs in
some P"). Options:

  1. Name potential class expressions
  2. Use graphwalker code. Either OWLTools or LEGO native code
  3. Name individuals

I think 3 may be most promising for LEGO in general. The basic idea is
that if you know that P Type: occurs_in some cytosol, then you can
name the specific cytosol instance (e.g. a UUID or a skolemized name
like P-location-in-cytosol).

So given

  • R part_of P
  • P occurs_in L
  • L rdf:type C

(where L is the new named individual)

We can infer

  • R occurs_in L

Given the relevant property chain (check: OPEs in Elk 0.4).

Now this may require a change to the algorith for finding what goes in
the yellow box. Previously there was some kind of graph walking(?)

The modified algorithm would simply be to query for all OPEs for an
individual for the occurs_in property. Use the asserted Type for the
targets of all these OPEs. If you end up with >1 Type, do the usual
(take the most specific, or make an intersection of the most
specific).

This style of instance-based reasoning may be the way we want to go
for LEGO in future.

Original issue: http://code.google.com/p/owltools/issues/detail?id=74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant