|
Difference between
version 11
and
version 10:
| 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, etc.) |
| + 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). |
| Line 15 was replaced by lines 15-16 |
| - AnnotationEngine: Set<ResourceID> getMatchingResources(SemanticAnnotationID, ConceptExpression) |
| + KeplerObjectManager: ResourceType getResourceType( ResourceID ) |
| + KeplerObjectManager: Set<SemanticAnnotationID> getSemanticAnnotations( RemoteSearchFlag ) |
| Lines 18-21 were replaced by lines 19-23 |
| - The searc operation also requires that the following operation be implemented by the Kepler Object Manager: |
| - {{{ |
| - KeplerObjectManager: Set<SemanticAnnotationID> getSemanticAnnotations( RemoteSearchFlag) |
| - }}} |
| + 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). |
| + |
| + We note that in the simplest form as stated above, the {{search}} operation requires access to all annotations to determine matching resources. |
| + |
| + |
Back to SMS Service Interfaces,
or to the Page History.
|
