Difference between revisions of "DAP4 Web Services - StartingPoint"

From OPeNDAP Documentation
(Dataset: The metadata)
(Data: The data response for the dataset.)
Line 48: Line 48:
The standard URL for this response is:  
The standard URL for this response is:  
:<font size="2"><code>baseURL + '.dap'</code></font>
:<font size="2"><code>baseURL + '.dap' + [?dap_constraint]</code></font>
== Data + Checksum ==
== Data + Checksum ==

Revision as of 18:01, 22 February 2012

1 Are we going to use this page? Should we flesh it out?

1.1 Protocol Independence

Proposal: The DAP4 data model and it's persistent (over-the-wire) representations are transport protocol agnostic. All of the information required by the DAP must be present in the content of the DAP requests and responses. The DAP won't uniquely embed information required by the DAP into HTTP Headers or AMQP thingys, or other whatnot.


  1. Does this matter? Is it something to strive for? Is it a Must? Is this just noise??
  2. Can the clients really make a request that's protocol independent?
  3. Would we need to add new syntax server-side functions etc. to the protocol to enable this?

1.2 Overview

This page describes the various web services that a DAP4 server must provide. These are for the most part REST services and as such are stateless unless noted otherwise.

The services are all defined as a modification of the service (aka resource or base) URL. This base URL essentially becomes a prefix (and could even be seen as a namespace) for all of the services available for that data resource.

In practice these have traditionally been implemented over HTTP. However they could just as easily be pushed over a different protocol, as long as the usage of the URL components remain consistent.

1.3 Service URL

The base URL for a data set accessed through a DAP4 web server will return a service document that describes the various responses possible for that data set, including URLs that can be used to access those responses.

DAP Service Terminus

The standard URL for this response is:


1.4 Dataset: The metadata

The Dataset response is an XML document containing a dap:Dataset object as it's root element. It contains the persistent DAP4: Data Model representation of the dataset held at the server. If a constraint expression has been successfully applied, the service will returned the constrained view of the dap:Dataset object. The constrained view may contain different data structures than the unconstrained view as the constraint may alter the reasonable representation of the data set.

Also: All dap:Attribute objects have been removed from constrained dap:Dataset objects.

More information on the Dataset response can be found on the DAP4: Dataset Response page.

More information on the syntax of DAP4 constraint expressions can be found on DAP4: Data Model page.

The standard URL for this response is:

baseURL + '.xml' + [?dap_constraint]

1.5 Data: The data response for the dataset.

The standard URL for this response is:

baseURL + '.dap' + [?dap_constraint]

1.6 Data + Checksum

The standard URL for this response is:

baseURL + '.cdap'

2 Requests