SMS Service Interfaces

This is version 15. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Concept-Based Searching

The following service interface performs simple concept-based searching of resources:

AnnotationEngine:  Set<ResourceID>  search( ConceptExpression, Set<ResourceType>, RemoteSearchFlag )  

Given a search expression (represented as a description-logic concept expression), a list of resource types (e.g., "actor", "dataset", etc.), and whether the search should be local or include remote repositories, this operation returns a set of resources that have semantic annotations that "match" the given search expression.

Here, we assume that an initial search string has been converted to a description-logic concept expression, which can be a simple concept id (like "Biomass") or a more complex formula (including nested disjunctive and conjunctive formulas, and so on).

The search operation requires the following kepler object manager services:

KeplerObjectManager:  ResourceType               getResourceType( ResourceID )
KeplerObjectManager:  Set<SemanticAnnotationID>  getSemanticAnnotations( RemoteSearchFlag ) 
KeplerObjectManager:  Set<Ontology>              getOntology( OntologyID )

Both of these services are implemented by the kepler object manager. The first operation returns the resource type of a given resource identifier (an LSID). The second operation returns the set of semantic annotations known to the kepler object manager (inlcuding any annotations stored on remote repositories denoted by the search flag argument). The last operation returns the ontology for a given ontology identifier (also a resource id).

We note that in the simplest form as stated above, the search operation requires access to all annotations to determine matching resources.

We can remove this implementation requirement with the following additional aggregation services:

... what are these ... ?