Science Environment for Ecological Knowledge
Ecoinformatics site parent site of Partnership for Biodiversity Informatics site parent site of SEEK - Home
Science Environment for Ecological Knowledge









 

 

 



SMS Service Interfaces

Difference between version 25 and version 24:

Line 1 was replaced by line 1
- !! Concept-Based Searching
+ !!# Concept-Based Searching
Lines 5-9 were replaced by lines 5-9
- This service takes the following three arguments:
- # 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
- The operation returns a set of resources (as LSIDs) with semantic annotations that "match" the given search expression.
+ The arguments for this service are:
+ # A search term represented as a description-logic concept expression;
+ # A set of resource types, e.g., "actor" and/or "dataset"; and
+ # A flag denoting whether local or remote repositories are searched
+ The service returns a set of resources (as LSIDs) that have semantic annotations "matching" the given search term.
Line 11 was replaced by line 11
- 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).
+ We assume that (via a GUI) an initial search string has been converted to a description-logic concept expression. A concept expression can be single concept (like "Biomass") or a complex formula (including nested disjunctive and conjunctive formulas, and so on).
Line 13 was replaced by line 13
- The search operation requires the following kepler object manager services:
+ The {{search}} service depends on the following kepler object manager services:
Lines 15-17 were replaced by lines 15-17
- KeplerObjectManager: ResourceType getResourceType( ResourceID )
- KeplerObjectManager: Set<SemanticAnnotationID> getSemanticAnnotations( RemoteSearchFlag )
- KeplerObjectManager: Set<Ontology> getOntology( OntologyID )
+ getResourceType( ResourceID ) :: ResourceType
+ getSemanticAnnotations( RemoteSearchFlag ) :: Set<SemanticAnnotationID>
+ getOntology( OntologyID ) :: Set<Ontology>
Line 20 was replaced by line 20
- 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).
+ 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 (including annotations stored on remote repositories depending on the value of the search flag). The last operation returns the ontology for a given ontology identifier (also a resource id).
Line 22 was replaced by line 22
- We note that in general, the {{search}} operation requires access to all semantic annotations to determine matching resources (e.g., in the case of search expressions containing conjunctive formulas). As the number of semantic annotations increases, this operation could become expensive.
+ In general, the {{search}} operation requires access to all semantic annotations (i.e., for remote searches all remote annotations) to find matching resources. Because of this requirement, as the number of semantic annotations increases, this operation can become expensive.
At line 23 added 2 lines.
+
+

Back to SMS Service Interfaces, or to the Page History.