Summary of Changes

v 004.1.1, 8 October 2007

• Updated version number to reflect current status.

v 004.0.09 - 28 August 2007

• Added missing double quotes to grammar rules for array-dim (now called projectionarray-dim), corrected an error in the grammar for a CE (although servers can accept an id without a projectionarray-dim, the grammar did not make that explicit) and corrected an error in the characters REQUIRED to be accepted for an id (most servers accept more characters, but the required set is fairly restricted) on pages 21 and 22;
• In Section 7 (page 23) the footnote listed the values for carriage return and line feed in reverse order;
• Corrected the grammar for a DDS in Section 7.2.2 (page 28) ’data-source’ ! ’dataset’;
• Added a note in Appendix A.2 regarding RFC 2616’s suggestion that ’tolerant’ applications ignore the CR and use only LF as a separator when they process a CRLF pair - we suggest not assuming HTTP software will follow this advice;
• In Section 7.1.4 (page 24) ’includ’ ! ’include’; In Section 8 (page 35) The value of the ’XDODS-Server’ header has been changed to more accurately reflect typical values;
• Added a note that DAP servers MUST return the Last-Modified header in Section 6.3 (page 23);
• The production rules for Structure, Sequence and Grid have been corrected to indicate the accepted literal values of the respective keywords (see Sections 7.2.2.3, 7.2.2.4 and 7.2.2.5 on pages 29, 29 and 30);
• The trailing semicolon was missing from the Error response grammar (Section 7.2.4, page 31);
• In Section 7.2.5 (page 31) the rule for the version number should have indicated that the third digit and its leading dot (.) are optional;
• In Section 8.1 (page 36) a note has been added to state explicitly that CRLF pairs in the data portion of a data response will be treated as data values and not as a line terminator;
• Removed an errant "CRLF" in the finale example of Section 8 (page 40).

v 004.0.08, 27 October 2005

• Added a note that the type names are case-insensitive on page 3.2.1;
• Clarified the typical use of XDR so that it’s clear that the number of elements of an array is sent twice in the case of an array of atomic types (Byte, ..., Float64) but only once in the case of the remaining types (see page 7.3.2.1);
• An error in the grammar for Sequences which was discovered previously was left out of a previous revision. Sequences are limited to at most a single inner Sequence ‘per level.’ See page 7.2.2.4.

v 004.0.07, 3 May 2005

• Corrected the description of the Host header in Section 6.2.2. The header was incor- rectly described as containing the DNS name or IP address of the client. In fact (and in conformance with HTTP/1.1) it contains the name/number of the server.

v 004.0.06, 12 April 2005

• Changed designation from ‘Proposed. . . ’ to ‘Draft Community Standard;’
• Added a clarification of ‘stride’ in a hyperslab (Section 4.1.1);
• Corrected the grammar for Attributes to indicate that they may have both scalar and vector values (Section 7.2.1);
• Added a description of Conditional Requests (Section 6.3); Added a description of the encoding of empty Sequence responses (Paragraph 7.3.2.3);
• Added addresses for all authors. 004.0.05, 17 Jan 2005, Added a note about the Expires header to the section on HTTP/1.1 caching (Sec- tion 7.1.4);
• Added note about XDR encoding of the Start of Instance and End of Sequence markers (Para- graph 7.3.2.3).

v 004.0.04, 20 Dec. 2004

• Corrected the descriptions of the Array, Grid and Sequence types so that all use zero-based indexing and so that all explanatory and example text is consistent with row-major ordering of data (Sections 3.3.3, 3.3.4, and 4.1.1);
• Corrected the description of the relational operators in the selection part of the constraint expression (Table 5 on page 17);
• Added information on supporting HTTP/1.1 caching (Sec- tion 7.1.4);
• Added information on the encoding of byte arrays (Paragraph 7.3.2.1)

v 004.0.03, 13 Sept. 2004

• Editorial changes; Added a clarification of the terms ‘persistent representation’ and ‘on-the-wire’ to “Data Representation” (Section 2.1);
• Added this “Change Explanation” section for confor- mance with ESE RFC 003 and made entries for the two previous versions using information from CVS;
• Adopted the new RFC version numbering system and set the number of this document at 004.0.03.

v 004.0.02, 6 Aug. 2004

• Editorial changes; Added Steve Hankin and Glenn Fleirl as authors;
• Marked as ‘Pro- posed Community Standard’ as per ESE RFC 003;
• Added “Motivation for Proposing Standardization” (Sec- tion 1.1);
• Added note about Error objects in “Overall Operation” (Section 2).

v 004.0.01, 28 June 2004

• Added Authors section
• Added Errata section.