Documentation for Computed Relationship

[cmungall]

The TransitivityGraph page mentions this but it isn't defined.

Computed Relationship

A computed relationship (or inferred relationship) is a relationship that is inferred through the application of a set of rules. For example, if P is declared transitive, then given path

x P y P z

There is a computed relationship x P z.

Implementations may differ in how this is performed, but as a general rule the rules should be specified in OWL, and the implementation should be complete w.r.t the EL++ subset of OWL. This allows for property chains, e.g.

Given

  P o Q -> R

And a path

  x P y Q z

Then there is an inferred relationship x R z

Non-reducible paths

If we have a path

x P y Q z

And there are no property chains connecting P and Q, then the path between x and z cannot be reduced any further than a computed relationship

x (P o Q) z

For now we only allow primitive relations between nodes; thus the path between x and z would be discarded. In future we may make this configurable[??]

Base case

There is at least one computed edge for every asserted edge. Thus if the graph contains

x R y

Then it is valid to call 'x R y' a computed edge

Implementations

We currently use the OWLGraphWrapper implementation

• OGW - http://owltools.googlecode.com/svn/trunk/docs/api/owltools/graph/package-summary.html

[kltm]

@cmungall I'm getting ready to shut this tracker and repo down--all usable parts of the original bbop-js library are either elsewhere or will be Very Soon. If you still want this to be actively tracked, you may want to move it to another repo.

[cmungall]

Can you move it?

[kltm]

I guess this really a doc request to the wiki docs, which would go to berkeleybop/bbop-manager-golr when the times comes. I'll see this when I close those out.

[cmungall]

not https://github.com/berkeleybop/bbop-graph?

[kltm]

bbop-graph is a completely abstract classic graph implementation; the actually concept and use of the topology and transitivity graphs is completely wrapped up in the conventions of GOlr, and the most direct JS connecting point to that is the golr manager. In fact, thinking about it, even the manager has no reference to the topo/trans graphs, they're probably only briefly mentioned in the bbop-response-golr.
One nice thing about a monolithic library is that it does nicely centralize one's documentation.