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 62 and version 61:

At line 17 added 2 lines.
+ Boolean match( ConceptExpression, ResourceID, RemoteFlag )
+
Line 26 was replaced by line 28
- ConceptExpression semanticType( ResourceID, String, RemoteFlag ) // for summarizing annotations
+ ConceptExpression semanticTypeConcepts( ResourceID, String, RemoteFlag ) // for summarizing annotations
Line 43 was replaced by line 45
- The service returns a set of resources (as LSIDs) that have semantic annotations "matching" the given search term.
+ The service returns a set of resources (as LSIDs) that have semantic types "matching" the given search term.
Line 49 was replaced by line 51
- ResourceType getResourceType( ResourceID )
+ ResourceType getResourceType( ResourceID )
Line 51 was replaced by line 53
- Set<SemanticAnnotationID> getSemanticAnnotations( RemoteSearchFlag )
+ Set<SemanticTypeID> getSemanticAnnotations( RemoteSearchFlag )
Line 53 was replaced by line 55
- Set<Ontology> getOntology( OntologyID )
+ Set<Ontology> getOntology( OntologyID )
Line 56 was replaced by line 58
- 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 remote flag). The last operation returns the ontology for a given ontology identifier (also a resource id). Note that this last operation could be used with an ontology service, e.g., the simple one described at the end of this page[simple ontology service|1].
+ The first operation returns the resource type of a given resource identifier (an LSID). The second operation returns the set of semantic types known to the kepler object manager (including semantic types stored on remote repositories depending on the value of the remote flag). The last operation returns the ontology for a given ontology identifier (also a resource id). Note that this last operation could be used with an ontology service, e.g., the simple one described at the end of this page[simple ontology service|1].
Line 60 was replaced by line 62
- In general, the {{search}} operation requires access to all semantic annotations to find matching resources. For example, consider a search expression {{A and B}}, i.e., a resource must contribute to both concept {{A}} and concept {{B}}. To find appropriate matches for this search term, the algorithm must look for annotations that explicitly state {{A and B}} as well as those that state only {{A}} and only {{B}} (which taken together make {{A and B}}). Note that an annotation that states only {{A}} may be in one repository, while an annotation that states only {{B}} may be in another. Thus, for remote searches, the {{search}} algorithm must obtain and consider all remote annotations to find matching resources, making the {{search}} operation inherently centralized.
+ In general, the {{search}} operation requires access to all semantic types to find matching resources. For example, consider a search expression {{A and B}}, i.e., a resource must contribute to both concept {{A}} and concept {{B}}. To find appropriate matches for this search term, the algorithm must look for semantic types that explicitly state {{A and B}} as well as those that state only {{A}} and only {{B}} (which taken together make {{A and B}}). Note that a semantic type that states only {{A}} may be in one repository, while a semantic type that states only {{B}} may be in another. Thus, for remote searches, the {{search}} algorithm must obtain and consider all remote semantic types to find matching resources, making the {{search}} operation inherently centralized.
At line 81 added 6 lines.
+ !!!{{Match}}: Checking Resource Matches
+
+ {{{
+ Boolean match( ConceptExpression, ResourceID, RemoteFlag
+ }}}
+
Line 86 was replaced by line 94
- compatible( ResourceID, Connection, ResourceID, StructTypeFlag, RemoteFlag ) :: Boolean
+ Boolean compatible( ResourceID, Connection, ResourceID, StructTypeFlag, RemoteFlag )
Line 94 was replaced by line 102
- searchCompatible( ResourceID, Port, StructTypeFlag, RemoteFlag ) :: Set<ResourceID>
+ Set<ResourceID> searchCompatible( ResourceID, Port, StructTypeFlag, RemoteFlag )
Line 101 was replaced by line 109
- compose( ResourceID, Connection, ResourceID, RemoteFlag ) :: Set<StructMapping>
+ Set<StructMapping> compose( ResourceID, Connection, ResourceID, RemoteFlag )
Line 107 was replaced by line 115
- merge( ResourceID, Connection, ResourceID, RemoteFlag ) :: Set<StructMapping>
+ Set<StructMapping> merge( ResourceID, Connection, ResourceID, RemoteFlag )
Line 114 was replaced by line 122
- semanticType( ResourceID, String, RemoteFlag ) :: ConceptExpression
+ ConceptExpression semanticType( ResourceID, String, RemoteFlag )

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