The description should contain information about what is the service, the purpose of the service, the parameters (or variables) being invoked, and what are the sources of these data for the service
Examples:
OPeNDAP example: OPeNDAP, the Open-source Project for a Network Data Access Protocol, is a NASA community standard DAP that provides a simple way for researchers to access and work with data over the internet. OPeNDAP's client/server software allows users to subset and reformat data using an internet browser, command line interface, or custom user interface such as a C NetCDF or Java NetCDF-compliant data analysis program.
SEDAC Hazards mapper example: The SEDAC Hazards Mapper enables users to visualize data and map layers related to Socioeconomic, Infrastructure, Natural Disasters, and Environment and analyze potential impacts and exposure. The web app mashups layers from various sources including SEDAC, NASA LANCE, NASA GIBS, USGS, NOAA, ESRI, and others.
Web service example: MODAPS Web Services provides an Application Programming Interface (API) to access the data products provided by the Level 1 and Atmosphere Archive and Distribution System (LAADS). The mission of MODAPS Web Services is to provide programmatic and/or scriptable access to MODIS level 1 and atmosphere data products. Capabilities include parameter sub-setting, geographic sub-setting, day/night granule search, metadata search, masking, channel sub-setting, tile re-projection, order tracking, granule re-projection, GeoTIFF re-formatting and mosaicking.
Element Specification
Model
Element
Type
Constraints
Required
Cardinality
Notes
UMM-S
Description
String
1-1024 characters
Yes
1
Metadata Validation
All records undergo CMR schema and business rule validation before entering the system.
This element is required.
Must contain at least 1 character and be no longer than 1024 characters in length.
