Here's my idea about merging (or rewriting) DDX into NcML. I just hope
that the future DDX output by Hyrax like below:
<Attribute name="units" type="String">
becomes NcML-compatible output like below:
<dimension name='phony0' size=4>
<dimension name='phony1' size=8>
<variable name='temperature' type='float' shape='phony0 phony1' >
<attribute name='units' value='K' />
OPeNDAP's DDX output looks overly complicated.
Of course, there are some things that NcML can't represent (e.g., DAP
url, unnamed dimensions, and attribute container). I think extending
NcML part belongs to Unidata. Thus, I'm asking team work to come up
with a single XML that can cover both netCDF NcML and OPeNDAP DDX.
HDF Product Designer: Ideate interoperable Bigdata for Citizen Science and IoT.
On Mon, Oct 5, 2015 at 1:35 PM, Nathan Potter <n...@opendap.org
> I think that the DDX is really a dead end. There’s nothing in the DDX that isn’t in the DDS and DAS which are good enough representations of the DAP2 data model. At least in Hyrax I think that the DDX is built from a DDS object to which a DAS has been added. I guess it has the advantage to a client of being a single request to the server instead of two (one for DDS and one for DAS).
> Is there something in the DDX you need? I am not sure I understand what you mean about "merge the DDX into NcML”. Is there an idea you have that you want to share?