DDX - Revision history

Jimg at 19:24, 22 December 2008

2008-12-22T19:24:07Z

← Older revision		Revision as of 19:24, 22 December 2008
Line 47:		Line 47:

	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.

			[[Category:Development\|DDX]][[Category:DAP4\|DDX]]

Jimg: /* Added the ''Data'' element to ease defining the ''DataDDX'' response */

2008-12-11T00:27:29Z

Added the ''Data'' element to ease defining the ''DataDDX'' response

← Older revision		Revision as of 00:27, 11 December 2008
Line 40:		Line 40:
	=== Added the ''Data'' element to ease defining the ''DataDDX'' response ===		=== Added the ''Data'' element to ease defining the ''DataDDX'' response ===

	See the design/discussion in [[DataDDX]].		See the design/discussion in [[DataDDX]]. The ''Data'' element is essentially the old BLOB element, but I'm calling it 'Data' this time ;-)

	=== Suggestions ===		=== Suggestions ===

Jimg: /* DAP 3.2 */

2008-12-11T00:22:36Z

DAP 3.2

← Older revision		Revision as of 00:22, 11 December 2008
Line 37:		Line 37:

	The ''schemaLocation'' attribute is used by conforming validating parsers but is not used to assign namespaces for the elements and attributes in the document, so the information is repeated.		The ''schemaLocation'' attribute is used by conforming validating parsers but is not used to assign namespaces for the elements and attributes in the document, so the information is repeated.

			=== Added the ''Data'' element to ease defining the ''DataDDX'' response ===

			See the design/discussion in [[DataDDX]].

	=== Suggestions ===		=== Suggestions ===

Jimg: /* Version information and the structure of the ''Dataset'' element */

2008-10-07T15:21:35Z

Version information and the structure of the ''Dataset'' element

← Older revision		Revision as of 15:21, 7 October 2008
Line 30:		Line 30:
	xsi:schemaLocation="http://xml.opendap.org/ns/DAP/3.2# http://xml.opendap.org/dap/dap/3.2.xsd"		xsi:schemaLocation="http://xml.opendap.org/ns/DAP/3.2# http://xml.opendap.org/dap/dap/3.2.xsd"
	xmlns="http://xml.opendap.org/ns/DAP/3.2#"		xmlns="http://xml.opendap.org/ns/DAP/3.2#"
	xmlns:~~dap3.2~~="http://xml.opendap.org/ns/DAP/3.2#"		xmlns:dap="http://xml.opendap.org/ns/DAP/3.2#"
	~~dap3.2:version~~="3.2">		dap_version="3.2">
	</pre>		</pre>

	Why have ''.../DAP/3.2#'' appear twice? Because this sets the default namespace to DAP 3.2 and sets the prefix ''~~dap3.2~~'' to that as well. The default namespace is not used by XML attributes, only elements, so defining the symbol ''~~dap3.2~~'' as a shorthand provides an easy way to place attributes is a given namespace.		Why have ''.../DAP/3.2#'' appear twice? Because this sets the default namespace to DAP 3.2 and sets the prefix ''dap'' to that as well. The default namespace is not used by XML attributes, only elements, so defining the symbol ''dap'' as a shorthand provides an easy way to place attributes is a given namespace.

	The schemaLocation attribute is used by conforming validating parsers but is not used to assign namespaces for the elements and attributes in the document, so the information is repeated.		The ''schemaLocation'' attribute is used by conforming validating parsers but is not used to assign namespaces for the elements and attributes in the document, so the information is repeated.

	=== Suggestions ===		=== Suggestions ===

Jimg: /* Implemented */

2008-10-01T22:18:40Z

Implemented

← Older revision		Revision as of 22:18, 1 October 2008
Line 8:		Line 8:

	=== Implemented ===		=== Implemented ===

			==== GRDDL Namespace ====

			In version 3.2 the namespace for ''grddl'' is defined and the DDX to RDF XSL transform is the value of the ''grddl:transform'' attribute in the ''Dataset'' element.

			xmlns:grddl="http://www.w3.org/2003/g/data-view#"
			grddl:transformation="http://xml.opendap.org/transforms/ddxToRdfTriples.xsl"

	==== BLOB element ====		==== BLOB element ====

Jimg: /* Implemented */

2008-10-01T22:07:39Z

Implemented

← Older revision		Revision as of 22:07, 1 October 2008
Line 8:		Line 8:

	=== Implemented ===		=== Implemented ===

			==== BLOB element ====

			Removed as of Version 3.2.

	==== Version information and the structure of the ''Dataset'' element ====		==== Version information and the structure of the ''Dataset'' element ====

Jimg: /* Version information and the structure of the ''Dataset'' element */

2008-10-01T21:54:15Z

Version information and the structure of the ''Dataset'' element

← Older revision		Revision as of 21:54, 1 October 2008
Line 22:		Line 22:
	dap3.2:version="3.2">		dap3.2:version="3.2">
	</pre>		</pre>

			Why have ''.../DAP/3.2#'' appear twice? Because this sets the default namespace to DAP 3.2 and sets the prefix ''dap3.2'' to that as well. The default namespace is not used by XML attributes, only elements, so defining the symbol ''dap3.2'' as a shorthand provides an easy way to place attributes is a given namespace.

			The schemaLocation attribute is used by conforming validating parsers but is not used to assign namespaces for the elements and attributes in the document, so the information is repeated.

	=== Suggestions ===		=== Suggestions ===

Jimg: /* DAP 3.2 */

2008-10-01T21:48:29Z

DAP 3.2

@@ Line 6: / Line 6: @@
 == 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.

Jimg: /* Dap 3.2 */

2008-07-31T22:31:46Z

Dap 3.2

← Older revision		Revision as of 22:31, 31 July 2008
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 ==		== 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.

Jimg at 22:30, 31 July 2008

2008-07-31T22:30:51Z

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

	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.

			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.