intermine.webservice.Registry:
Registries are web-services that mines can automatically register
themselves with, and thus enable service discovery by clients.
urllib.URLopener:
Class to open URLs.
urllib.FancyURLopener:
Derived class with handlers for errors we can handle (perhaps).
intermine.model.Class:
These objects refer to the table objects in the InterMine ORM
layer.
intermine.model.Column:
Column objects allow constraints to be constructed in something
close to a declarative style
intermine.constraints.ConstraintFactory:
A constraint factory is responsible for finding an appropriate
constraint class for the given arguments and instantiating the
constraint.
intermine.model.Reference:
In addition the the behaviour and properties of Field, references
may also have a reverse reference, if the other record points back
to this one as well.
intermine.constraints.LogicNode:
Objects which can be represented as nodes in the AST of a
constraint logic graph should inherit from this class, which
defines methods for overloading built-in operations.
intermine.constraints.CodedConstraint:
Constraints that have codes are the principal logical filters on
queries, and need to be refered to individually (hence the codes).
intermine.constraints.BinaryConstraint:
These constraints assert a relationship between the value
represented by the path (it must be a representation of a value, ie
an Attribute) and another value - ie.
intermine.constraints.TernaryConstraint:
These constraints request a wide-ranging search for matching fields
over all aspects of an object, including up to coercion from
related classes.
intermine.constraints.ListConstraint:
These constraints assert a membership relationship between the
object represented by the path (it must always be an object, ie.
intermine.constraints.MultiConstraint:
These constraints require the value they constrain to be either a
member of a set of values, or not a member.
intermine.constraints.RangeConstraint:
Constraints for testing where a value lies relative to a set of ranges
======================================================================
intermine.constraints.Constraint:
All constraints inherit from this class, which simply defines the
type of element for the purposes of serialisation.
intermine.constraints.CodedConstraint:
Constraints that have codes are the principal logical filters on
queries, and need to be refered to individually (hence the codes).
intermine.constraints.BinaryConstraint:
These constraints assert a relationship between the value
represented by the path (it must be a representation of a value, ie
an Attribute) and another value - ie.
intermine.constraints.TernaryConstraint:
These constraints request a wide-ranging search for matching fields
over all aspects of an object, including up to coercion from
related classes.
intermine.constraints.ListConstraint:
These constraints assert a membership relationship between the
object represented by the path (it must always be an object, ie.
intermine.constraints.MultiConstraint:
These constraints require the value they constrain to be either a
member of a set of values, or not a member.
intermine.constraints.RangeConstraint:
Constraints for testing where a value lies relative to a set of ranges
======================================================================
intermine.constraints.SubClassConstraint:
If an object has a reference X to another object of type A, and
type B extends type A, then any object of type B may be the value
of the reference X.
intermine.query.Query:
Objects of this class have properties that model the attributes of
the query, and methods for performing the request.
intermine.query.Template:
Templates are ways of saving queries and allowing others to run
them simply.
intermine.webservice.Registry:
Registries are web-services that mines can automatically register
themselves with, and thus enable service discovery by clients.
intermine.constraints.TemplateConstraint:
Constraints on templates can also be designated as "on",
"off" or "locked", which refers to whether they
are active or not.