“Services” are functional capabilities offered by the community:
“Extended”, because they are not native to ECHO.
Published to the ECHO Registry.
ECHO Data Services can be many different things, from dedicated machines that transform or reduce the size of data, to innovative algorithms for discovering data that is relevant to particular research topics, to offerings by organizations to gather in situ data. ECHO is designed to support any type of related data service, enabling more innovative approaches to meeting the EOS mission. ECHO provides interfaces and mechanisms that allow organizations to publish their services and correlate their service to the data types in the clearinghouse.
An ECHO Service Partner is an individual or organization that participates with ECHO by providing access to functions that create Earth Science Data or information.
ECHO advertises these services as well as brokers these services, as the Service Partner requests.
Register – Service Providers register the services
Activate – ECHO operations review and activate them.
Find – Users find the services using the UDDI inquiry API or Extended Services Viewer
Retrieve – Users can get the services to view their details
Update – Service Providers can update their services
Delete – Service Providers can remove their services
- Defines a web service API.
- Defined in WSDL file.
- Hosted within ECHO system.
- Centrally managed interfaces encourages standardization and reuse within community.
- Reusable between provider organizations.
- Examples:
- Common Subsetting interface.
- Common Access service interface (OPeNDAP)
- WMS service
- An executable web service hosted by an ECHO Service Provider.
- Defined in a WSDL file
- Contains at least one service element
- May implement interfaces registered in ECHO.
- By importing interface WSDL from ECHO hosted location.
- Examples:
- An application-specific service (OPeNDAP Query adaptor).
- A predictive model.
- Specific WMS server
- A user interface for a web service.
- Provides a way for human to interact with a web service.
- Includes name, description, and access point.
- Associated with implementations and interfaces registered in ECHO.
- Examples:
- ECHO Query Client
- Domain Specific User Client for subsetting
- A way to advertise a service that is not a real Web Service.
- Includes name and description of service and an access point.
- Example:
- Service for expert advice on a specific application area
- Ability to drop sensors in the Chesapeake Bay
|
and Accessibility Certification