ASCII Data DDX - Revision history

Ndp: /* Questions */

2010-08-03T13:07:19Z

Questions

← Older revision		Revision as of 13:07, 3 August 2010
Line 92:		Line 92:
	* .axml (may be in use)		* .axml (may be in use)
	* .ascx (in use http://www.fileinfo.com/extension/ascx)		* .ascx (in use http://www.fileinfo.com/extension/ascx)
			* .addx (not in use)

Ndp: /* Questions */

2010-08-03T13:05:05Z

Questions

← Older revision		Revision as of 13:05, 3 August 2010
Line 90:		Line 90:
	Suggestions:		Suggestions:
	* .dodx (not in use as an extension)		* .dodx (not in use as an extension)
	* .axml (may be ~~used~~)		* .axml (may be in use)
	* .ascx (In use ~~my microsoft~~)		* .ascx (in use http://www.fileinfo.com/extension/ascx)

Ndp at 13:03, 3 August 2010

2010-08-03T13:03:38Z

@@ Line 1: / Line 1: @@
 Although inefficient, a pure XML data response could be very useful for inferencing engines. I imagine a response in which variables contain their values, much like Attributes. Consider this modified DDX:
@@ Line 83: / Line 84: @@
   </Dataset>
 :* Alternately we could try embedding the values in the template variables. Each variable would have a sequence of <value> elements representing its value in each row of the parent Sequence. I think this is sub optimal because of memory and response generation efficiency concerns.

Ndp at 16:37, 15 April 2010

2010-04-15T16:37:51Z

← Older revision		Revision as of 16:37, 15 April 2010
Line 82:		Line 82:
	</Sequence>		</Sequence>
	</Dataset>		</Dataset>
	** Alternately we could try embedding the values in the template variables. Each variable would have a sequence of <value> elements representing its value in each row of the parent Sequence. I think this is sub optimal because of memory and response generation efficiency concerns.		:* Alternately we could try embedding the values in the template variables. Each variable would have a sequence of <value> elements representing its value in each row of the parent Sequence. I think this is sub optimal because of memory and response generation efficiency concerns.

Ndp at 16:37, 15 April 2010

2010-04-15T16:37:17Z

← Older revision		Revision as of 16:37, 15 April 2010
Line 82:		Line 82:
	</Sequence>		</Sequence>
	</Dataset>		</Dataset>
			** Alternately we could try embedding the values in the template variables. Each variable would have a sequence of <value> elements representing its value in each row of the parent Sequence. I think this is sub optimal because of memory and response generation efficiency concerns.

Ndp at 16:33, 15 April 2010

2010-04-15T16:33:34Z

@@ Line 7: / Line 7: @@
      <Grid name="bears">
          <Array name="bears">
-             <String/>
+             < Float32/>
              <dimension name="i" size="2"/>
              <dimension name="j" size="3"/>
@@ Line 32: / Line 32: @@
      </Grid>
   </Dataset>
-We would need to iron out the details of how the <data> element could be organized for the various data types. Possible ideas:
+We would need to iron out the details of how the <value> elements could be are for the various data types. Possible ideas:
 * Simply use the same ordering and markers we use now in the XDR encoded binary content, and simply produce all of the values as their ASCII versions, suitably encoded for XML content.
-* Develop a structure for the content of the data element that is dependent on it its parents type. So atomic types would have single <value> element. One dimensional arrays would have multiple values elements. We would need to look at a possible more complex structure for multidimensional arrays and for Sequences. Structures and Grids would simply contain types already represented.
+** Grids, and Structures could embed the variable values as above.

Ndp at 21:56, 14 April 2010

2010-04-14T21:56:17Z

← Older revision		Revision as of 21:56, 14 April 2010
Line 10:		Line 10:
	<dimension name="i" size="2"/>		<dimension name="i" size="2"/>
	<dimension name="j" size="3"/>		<dimension name="j" size="3"/>
	~~<data>~~		<value>72.022</value>
	<value>72.022</value>		<value>72.184</value>
	<value>72.184</value>		<value>72.256</value>
	<value>72.256</value>		<value>72.745</value>
	<value>72.745</value>		<value>72.297</value>
	<value>72.297</value>		<value>72.367</value>
	<value>72.367</value>
	~~</data~~>
	</Array>		</Array>
	<Map name="i">		<Map name="i">
	<Int32/>		<Int32/>
	<dimension name="i" size="2"/>		<dimension name="i" size="2"/>
	~~<data>~~		<value>1</value>
	<value>1</value>		<value>2</value>
	<value>2</value>
	~~</data~~>
	</Map>		</Map>
	<Map name="j">		<Map name="j">
	<Float32/>		<Float32/>
	<dimension name="j" size="3"/>		<dimension name="j" size="3"/>
	~~<data>~~		<value>92</value>
	<value>92</value>		<value>93</value>
	<value>93</value>		<value>94</value>
	<value>94</value>
	~~</data~~>
	</Map>		</Map>
	</Grid>		</Grid>

Ndp: New page: Although inefficient, a pure XML data response could be very useful for inferencing engines. I imagine a response in which variables contain their values, much like Attributes. Consider th...

2010-04-14T21:55:02Z

New page: Although inefficient, a pure XML data response could be very useful for inferencing engines. I imagine a response in which variables contain their values, much like Attributes. Consider th...

New page

Although inefficient, a pure XML data response could be very useful for inferencing engines. I imagine a response in which variables contain their values, much like Attributes. Consider this modified DDX:

<Dataset name="bears.nc"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://xml.opendap.org/ns/DAP/3.3#"
>
<Grid name="bears">
<Array name="bears">
<String/>
<dimension name="i" size="2"/>
<dimension name="j" size="3"/>
<data>
<value>72.022</value>
<value>72.184</value>
<value>72.256</value>
<value>72.745</value>
<value>72.297</value>
<value>72.367</value>
</data>
</Array>
<Map name="i">
<Int32/>
<dimension name="i" size="2"/>
<data>
<value>1</value>
<value>2</value>
</data>
</Map>
<Map name="j">
<Float32/>
<dimension name="j" size="3"/>
<data>
<value>92</value>
<value>93</value>
<value>94</value>
</data>
</Map>
</Grid>
</Dataset>
We would need to iron out the details of how the <data> element could be organized for the various data types. Possible ideas:

* Simply use the same ordering and markers we use now in the XDR encoded binary content, and simply produce all of the values as their ASCII versions, suitably encoded for XML content.
* Develop a structure for the content of the data element that is dependent on it its parents type. So atomic types would have single <value> element. One dimensional arrays would have multiple values elements. We would need to look at a possible more complex structure for multidimensional arrays and for Sequences. Structures and Grids would simply contain types already represented.