Ethan,
Is it allowed for a dataset to have the serviceName and/or the urlPath
specified as child elements? (I think the answer is yes to serviceName
and no to urlPath)
Examples:
<dataset name="level2_b" ID="nc/level2_b.nc" >
<serviceName>s2</serviceName>
<urlPath>nc/level2b_.nc</urlPath>
</dataset>
<dataset name="level2_b" urlPath="nc/level2_b.nc" ID="nc/
level2_b.nc" >
<serviceName>s2</serviceName>
</dataset>
<dataset name="level2_b" serviceName="s2" ID="nc/level2_b.nc" >
<urlPath>nc/level2b_.nc</urlPath>
</dataset>
Is it allowed for a dataset to have both a serviceName/urlPath pair as
attributes AND as child elements?
If so, which has priority? (My guess is that none of these are allowed)
Examples:
<dataset name="level2_b" serviceName="s2" urlPath="nc/level2_b.nc"
ID="nc/level2_b.nc" >
<serviceName>s3</serviceName>
</dataset>
<dataset name="level2_b" serviceName="s2" urlPath="nc/level2_b.nc"
ID="nc/level2_b.nc" >
<serviceName>s3</serviceName>
<urlPath>data/level2b_.nc</urlPath>
</dataset>
<dataset name="level2_b" serviceName="s2" urlPath="nc/level2_b.nc"
ID="nc/level2_b.nc" >
<urlPath>data/examples/level2b_.nc</urlPath>
</dataset>
Is a dataset allowed to have a serviceName/urlPathr via inheritance,
attribute, or children and also have access element children?
If so are there rules about precedence? Is it cumulative?
Examples:
<dataset name="level1" ID="degenerate examples">
<metadata inherited='true'>
<serviceName>s1</serviceName>
</metadata>
<dataset name="level2_a" urlPath="nc/level2_a.nc" ID="nc/
level2_a.nc">
<access serviceName="s2" urlPath="nc/level2_a"
dataFormat="NetCDF" />
</dataset>
<dataset name="level2_b" serviceName="s2" urlPath="nc/level2_b.nc"
ID="nc/level2_b.nc" >
<access serviceName="s3" urlPath="nc/level2_a"
dataFormat="NetCDF" />
</dataset>
<dataset name="level2_b" urlPath="nc/level2_b.nc" ID="nc/
level2_b.nc" >
<serviceName>s2</serviceName>
<access serviceName="s3" urlPath="nc/level2_a"
dataFormat="NetCDF" />
</dataset>
</dataset>
Thanks for all of your help with this!
N
= = =
Nathan Potter ndp at opendap.org
OPeNDAP, Inc. +1.541.231.3317
