Version response - Revision history

Jimg at 19:25, 22 December 2008

2008-12-22T19:25:48Z

← Older revision		Revision as of 19:25, 22 December 2008
Line 28:		Line 28:

	[http://scm.opendap.org/trac/wiki/CEFunctionDiscovery One possible design].		[http://scm.opendap.org/trac/wiki/CEFunctionDiscovery One possible design].

			[[Category:Development\|Version response]][[Category:DAP4\|Version response]]

Jimg: /* DAP 3.2 */

2008-07-31T22:18:44Z

DAP 3.2

← Older revision		Revision as of 22:18, 31 July 2008
Line 23:		Line 23:
	== DAP 3.2 ==		== DAP 3.2 ==

	The DAP version document as provided should be changed to make it's output more in line with something a person would really read and understand quickly. See ''discussion'' for more about this.		The DAP version document as provided should be changed to make it's output more in line with something a person would really read and understand quickly. See [[:Talk:version_response\|discussion]] for more about this.

	To provide DAP with a way for clients to discover server features that are common but not completely universal, the version response may be extended to include information about server-side functions.		To provide DAP with a way for clients to discover server features that are common but not completely universal, the version response may be extended to include information about server-side functions.

	[http://scm.opendap.org/trac/wiki/CEFunctionDiscovery One possible design].		[http://scm.opendap.org/trac/wiki/CEFunctionDiscovery One possible design].

Jimg: /* DAP 3.2 */

2008-07-31T22:17:36Z

DAP 3.2

← Older revision		Revision as of 22:17, 31 July 2008
Line 22:		Line 22:

	== DAP 3.2 ==		== DAP 3.2 ==

			The DAP version document as provided should be changed to make it's output more in line with something a person would really read and understand quickly. See ''discussion'' for more about this.

	To provide DAP with a way for clients to discover server features that are common but not completely universal, the version response may be extended to include information about server-side functions.		To provide DAP with a way for clients to discover server features that are common but not completely universal, the version response may be extended to include information about server-side functions.

	[http://scm.opendap.org/trac/wiki/CEFunctionDiscovery One possible design].		[http://scm.opendap.org/trac/wiki/CEFunctionDiscovery One possible design].

Jimg at 23:37, 29 July 2008

2008-07-29T23:37:00Z

← Older revision		Revision as of 23:37, 29 July 2008
Line 4:		Line 4:

	In the past, the ''.ver'' suffix was also going to return the version number of the data referenced by the URL. However, often that information does not exist. A better solution to this is to generate CRC codes or digital watermarks on the fly. This does not provide a version number for the data, but it does provide a way to determine if a given request is returning the same data and, in the case of a watermark, may also help determine the origin of a subset.		In the past, the ''.ver'' suffix was also going to return the version number of the data referenced by the URL. However, often that information does not exist. A better solution to this is to generate CRC codes or digital watermarks on the fly. This does not provide a version number for the data, but it does provide a way to determine if a given request is returning the same data and, in the case of a watermark, may also help determine the origin of a subset.

			While we are requiring that 3.2 clients read and understand 3.1, 3.0 and 2.0 (and so on for 3.3, ...) that is not practical for the Version response since there are some widely different forms and since no clients actually use the 3.1 response. DAP 3.2 or 3.3 will set this in stone and then all 3.2 or 3.3 and subsequent clients will need to read and understand it.

	== DAP 3.1 ==		== DAP 3.1 ==

Jimg: /* DAP 3.1 */

2008-07-29T22:33:34Z

DAP 3.1

← Older revision		Revision as of 22:33, 29 July 2008
Line 16:		Line 16:

	An [[example Version response]] from a 3.1-compliant server (Hyrax 1.4.0).		An [[example Version response]] from a 3.1-compliant server (Hyrax 1.4.0).

			'''Note''': See the ''discussion'' page for an alternative design.

	== DAP 3.2 ==		== DAP 3.2 ==

Jimg: /* DAP 3.1 */

2008-07-29T22:29:30Z

DAP 3.1

@@ Line 15: / Line 15: @@
 The entire document is wrapped in a ''OPeNDAP-Version'' element.
+An [[example Version response]] from a 3.1-compliant server (Hyrax 1.4.0).
 == DAP 3.2 ==

Jimg at 21:57, 29 July 2008

2008-07-29T21:57:12Z

@@ Line 1: / Line 1: @@
 The version response is a way for a DAP-compliant server to advertise the versions of the DAP it supports along with the versions of the software with which it is built.
 == DAP 3.1 ==
-In DAP 3.1, the version response is an XML document such as the following:
+In DAP 3.1, the version response is an XML document. This document contains version information for:
 <pre>
 <?xml version="1.0" encoding="UTF-8"?>
@@ Line 63: / Line 75: @@
 == DAP 3.2 ==

Jimg: New page: The version response is a way for a DAP-compliant server to advertise the versions of the DAP it supports along with the versions of the software with which it is built. == DAP 3.1 == In...

2008-07-29T21:29:23Z

New page: The version response is a way for a DAP-compliant server to advertise the versions of the DAP it supports along with the versions of the software with which it is built. == DAP 3.1 == In...

New page

The version response is a way for a DAP-compliant server to advertise the versions of the DAP it supports along with the versions of the software with which it is built.

== DAP 3.1 ==

In DAP 3.1, the version response is an XML document such as the following:
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<OPeNDAP-Version>
<BES-Version>
<BES>
<prefix>/</prefix>
<lib>
<name>bes</name>
<version>3.6.2</version>
</lib>
</BES>
<Handlers>
<lib>
<name>dap-server/ascii</name>
<version>3.8.5</version>
</lib>
<DAP>
<version>2.0</version>
<version>3.0</version>
<version>3.1</version>
</DAP>
<lib>
<name>hdf4_handler</name>
<version>3.7.8</version>
</lib>
<lib>
<name>netcdf_handler</name>
<version>3.7.9</version>
</lib>
<lib>
<name>dap-server/usage</name>
<version>3.8.5</version>
</lib>
<lib>
<name>wcs_module</name>
<version>1.0.0</version>
</lib>
<lib>
<name>dap-server/www</name>
<version>3.8.5</version>
</lib>
</Handlers>
</BES-Version>
<OLFS>
<lib>
<name>olfs</name>
<version>1.4.0</version>
</lib>
</OLFS>
<Hyrax>
<lib>
<name>Hyrax</name>
<version>1.4.0</version>
</lib>
</Hyrax>
</OPeNDAP-Version>
</pre>

== DAP 3.2 ==