DAP3/4: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
Line 1: Line 1:
== DAP2 and DAP4 Specification efforts ==
== DAP2 and DAP4 Specification efforts ==


The DAP4 specification work has morphed into separate DAP2 and DAP4 specification efforts. The [http://www.opendap.org/pdf/ESE-RFC-004v1.1.pdf DAP 2.0 specification] was approved by NASA as a 'Community Standard' on 10/8/2007
The DAP4 specification work has morphed into separate DAP2 and DAP4 specification efforts. The [http://www.opendap.org/pdf/ESE-RFC-004v1.1.pdf DAP 2.0 specification] ([http://www.esdswg.org/spg/rfc/ese-rfc-004 official version] with notes, et c.) was approved by NASA [http://www.esdswg.org/spg/ ESE/SPG] as a 'Community Standard' on 10/8/2007.


This page holds a collection of the DAP4 specification information
This page holds a collection of the DAP4 specification information

Revision as of 20:22, 24 June 2008

DAP2 and DAP4 Specification efforts

The DAP4 specification work has morphed into separate DAP2 and DAP4 specification efforts. The DAP 2.0 specification (official version with notes, et c.) was approved by NASA ESE/SPG as a 'Community Standard' on 10/8/2007.

This page holds a collection of the DAP4 specification information


[DAPFourSpec DAP4 Specification Issues] A collection of DAP Data Model (mostly) issues

Changes to the DAP 2.0 implementation

I'm not sure if these should be writen into the 2.0 (2.x?) spec or if we should add these into a 3.x spec and pursue an iterative development of 3.x specs on the way to a 4.0 spec. These _are_, however, ideas that came out of reading over the old DAP 2.0 document.

2 Add support (maybe in XDAP-Version 2.1?) for reliable error delivery 3 Support for 'any character in a name' using double quotes.

-- Main.JamesGallagher - 12 May 2004


Editorial changes:

  • Need to conform to ESE RFC 003

If we're given the opportunity to think about DAP 2.1, I'd suggest:

2 Chunked encoding for data (so that we can have reliable error delivery in all cases) and 3 Eliminating the repetition of the array size for an array of Atomic types.

-- Main.JamesGallagher - 19 May 2004

Completed Changes From DAP2

OPeNDAP has three implementations of the DAP that it maintains: libdap (C++), Java-OPeNDAP (Java) and Ocapi (C; client-side only). There are other implementations which have been developed by other groups.

Features of DAP3/4 implemented in libdap

libdap is the reference implementation for DAP. Here are the DAP3 features implement in it so far:

  • DDX (although this implementation needs significant review and update)
  • XDAP header for the protocol version
  • Updated Version response which provides information about software versions and DAP version.

Proposed Changes To DAP2

Most desirable features

This is a list of the very most desirable features proposed for DAP3 (which when final will become DAP4). Only the very most important items are listed here, other documents list everything that's ever been suggested:

  • Reliable error delivery when accessing data (known defect);
  • Use of Multi-part MIME for DataDDX (feature --> adherence to standard where applicable);
  • Develop the DataDDX (feature --> adherence to standard ...);
  • Ability to return checksums from data requests (feature with several use cases).