.. slideconf:
   :autoslides: False

Glossary
========

.. glossary::

  client
  Client
    A client in the context of this document is any application that accesses a
    service through the service interface.

  Entities
    Plural of :term:`Entity`.

  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.

  port
  ports
    A Port enables a Program to send or receive Entity items. See `ProvONE:
    Port`_

  program
  Program
    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 :term:`Service` that has been registered through the :term:`Service
    Registration` process.

  service
  Service

    A service in the context of this document is a :term:`Program` that is
    accessible over the internet using a standard protocol that performs some
    operation on :term:`Entities` that ideally are accessible through the DataONE
    :func:`get()<dataone:MNRead.get>` operation.

  Service Description
  	A document that contains metadata describing a :term:`Service` that
  	includes a description of the :term:`Service Interface` and the
  	:term:`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.


.. _Prov-O\: Entity: http://www.w3.org/TR/2013/REC-prov-o-20130430/#Entity

.. _ProvONE\: Port: http://jenkins-1.dataone.org/jenkins/view/Documentation%20Projects/job/ProvONE-Documentation-trunk/ws/provenance/ProvONE/v1/provone.html#concept-entity

.. _ProvONE\: Program: http://jenkins-1.dataone.org/jenkins/view/Documentation%20Projects/job/ProvONE-Documentation-trunk/ws/provenance/ProvONE/v1/provone.html#concept-entity


.. slide:: Empty