Footnotes

 (1)

OPeNDAP, Inc. jgallagher at opendap.org

 (2)

Oregon State University, ndp at coas.oregonstate.edu

 (3)

OPeNDAP, Inc. jchamberlain at opendap.org

 (4)

XML or HTML are not the only syntaxes, but they are the standard ones described in the bulk of the documentation.

 (5)

...as opposed to SOAP RPC. See Appendix A.

 (6)

As is the case with DAP2, a valid constraint expression is the empty string, which provides no constraint on the returned data (i.e., it instructs the server to return all of the data in the data source).

 (7)

Proposed is an optimization of the `always use XDR' approach where the client announces to the server that it uses either big- or little-endian representation and the server then responds either using the XDR-based big-endian (as default) or matches the client's representation, thus eliminating, in the worst case scenario, the need to transform the data values on both ends.

 (8)

The SOAP interface described before is also capable of this.

 (9)

For the sake of backward compatibility, we will support the DAP2 CE grammar in DAP4.

 (10)

http://webservices.xml.com/pub/a/ws/2002/02/20/rest.html

 (11)

Fielding, p 76.

 (12)

Fielding, p 23.

 (13)

Fielding, p 148.

 (14)

Fielding, p 109.

 (15)

Fielding, p 111.

 (16)

Fielding, p 24.

 (17)

Fielding, p 142.