A client in the context of this document is any application that accesses a service through the service interface.
Plural of Entity.
In the context of this document, represents a specialization of the Prov-O: Entity in that the object is digital, and should be accessible through DataONE service interfaces.
A Port enables a Program to send or receive Entity items. See ProvONE: Port
A Program represents a computational task that consumes and produces data through its input and output ports, respectively. It can be atomic or composite, the latter case represented by a possibly nested Program. See ProvONE: Program
registered service
Registered Service
A Service that has been registered through the Service Registration process.
A service in the context of this document is a Program that is accessible over the internet using a standard protocol that performs some operation on Entities that ideally are accessible through the DataONE get() operation.
Service Description
A document that contains metadata describing a Service that includes a description of the Service Interface and the Service Endpoint.
Service Endpoint
The service endpoint is the internet address at which the service can be accessed by clients.
Service Interface
The mechanism through which clients interact with a service in a manner compliant with the advertised service specifications.
Service Registration
The process whereby a service is registered with DataONE and so may be discovered through searches.
Service Specification
Description of the specific mechanisms that a client may utilize for programmatic interaction with a service. The service specification should include the protocol being used to access the service as well as the structure of messages, protocol specific paths or endpoints, service behavior, and error condition notification.

Related Topics