Deploy Resources

Back to the Transverse Technology Use Cases list.

Brief description

Role and purpose: this use case describes the conditions and steps to configure and deploy a component with associated service interfaces, in order to make a resource accessible and usable within GEOSS.
This use case is a precondition that is implicit in all other "Interact with Service" specialized Use Cases.

Basic flow of events


 Service Publication and Registration


This GEOSS Transverse Technology Use Case first identifies many of the aspects that are, or should be, common to all or multiple Web Services interface Implementation Specifications. It refers notably to the OGC Web Services Common document (OGC 06-121), i.e. OGC  Web Map Service (WMS), Web Feature Service (WFS), and Web Coverage Service (WCS), but shall encompass as well OpenDAP and W3C W*S. Web Services common aspects include: service operation request and response encoding; and parameters included in operation requests and responses.
It also deals with best practices for service Registration in the GEOSS Common Infrasturcture, ensuring proper service discovery, retrieval, and testing by the GEOSS communities of practice.

 Actors and Interfaces

  • Service Provider
  • GEOSS Common Infrastructure Registry

Initial Status and preconditions

  •  Service Provider has a resource of interest for GEOSS. For example: a model, an observation or another process (grid transformation, workflow...)


(basic flow steps)

  1. Service Provider implements in his component the best available Web Service standard (OGC, W3C...) to make its resource available on GEOSS (based on best practices for that type of data, plus availability and familiarity of software tools)
  2. Service Provider configures or validates all the information about its Service interface as provided in the service Capabilities document:
    • Service Type, Version, Title and Abstract, Supported languages
    • Contact information (service provider PoC)
    • Supported service operations request and response encoding
    • Contents : Layers Names (normalized terms for M2M processing) and Titles (human readable)
    • Domains of validity : dimensions, units, range, scales, reference systems
  3. Service Provider publishes its Component and associated Service interfaces to the GEOSS registry
    • Metadata about the Service (ISO 19139)  is generated automatically from the service or
    • additional information (e.g. metadata not found in the getCapabilities) needs to be added when registering the service

 Post Condition

 The following pieces of information about a Service must be available from the GEOSS registry:

  • Service getCapabilities URL
  • Service type (WMS, WCS, SPS, etc..)
  • Type of procedure:
  • Model
  • Sensor or Platform
  • Other
  • Input (e.g. Phenomena, configuration variables..)
  • Output (e.g. Phenomena, file,..)

Ideally all of these pieces should have an associated URI (Uniform Resource Identifier)

Alternative flows of events


Special Requirements