DDX: Difference between revisions
No edit summary |
|||
| Line 5: | Line 5: | ||
DAP 3.1 contains an implementation of this feature, which is described, in spirit, in the original [[Media:Dap_objectsdraft3nov03.pdf | Draft DAP 4 specification document]]. | DAP 3.1 contains an implementation of this feature, which is described, in spirit, in the original [[Media:Dap_objectsdraft3nov03.pdf | Draft DAP 4 specification document]]. | ||
== | == DAP 3.2 == | ||
Adopt the use of MIME that is used by WCS 1.1. | Adopt the use of MIME that is used by WCS 1.1. | ||
Modify Attributes so that they appear 'anywhere' in the DDX and eliminate the ''Attribute'' element. At the same time, every Attribute must be in a namespace to bind that attribute to some semantic context. We will define an 'opendap' namespace for stuff that's not clearly part of CF, FGDC, et cetera. | Modify Attributes so that they appear 'anywhere' in the DDX and eliminate the ''Attribute'' element. At the same time, every Attribute must be in a namespace to bind that attribute to some semantic context. We will define an 'opendap' namespace for stuff that's not clearly part of CF, FGDC, et cetera. | ||
Revision as of 22:31, 31 July 2008
The DDX is an attempt to combine the information in the both the DDS and DAS into one response to eliminate the need to cross-walk the two responses when applying DAS information to variables. It will also streamline access somewhat and will employ XML as the content-type, although these are secondary objectives.
DAP 3.1
DAP 3.1 contains an implementation of this feature, which is described, in spirit, in the original Draft DAP 4 specification document.
DAP 3.2
Adopt the use of MIME that is used by WCS 1.1.
Modify Attributes so that they appear 'anywhere' in the DDX and eliminate the Attribute element. At the same time, every Attribute must be in a namespace to bind that attribute to some semantic context. We will define an 'opendap' namespace for stuff that's not clearly part of CF, FGDC, et cetera.
