Hi Nathan,
>From the spec:
"An access element ... always refers to the dataset that
it is immediately contained within."
http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/v1.0.2/InvCatalogSpec.html#access
Also, an access element can only be contained in a dataset element, not
in a metadata element. All access elements MUST contain a "urlPath"
attribute.
Ethan
Nathan Potter wrote:
>
>
> Ethan,
>
> Along the same lines then, can <access> elements be inherited? Or is it
> bound only to the containing dataset and never to that dataset's children?
>
> Example:
>
> <dataset name="level1" ID="SingleFileWcs">
> <metadata inherited='true'>
> <access serviceName=dap />
> </metadata>
> <dataset name="level2_a" urlPath="wcs/foo" ID="wcs/foo" />
> <dataset name="level2_b" urlPath="wcs/foo" ID="wcs/foo" >
> <serviceName>otherService</serviceName>
> </dataset>
> </dataset>
>
>
> N
>
>
> On Dec 1, 2009, at 1:18 PM, Ethan Davis wrote:
>
>> Hi Nathan,
>>
>> Nathan Potter wrote:
>>>
>>> Another question, about service inheritance.
>>>
>>> Example:
>>>
>>> <dataset name="level1" ID="SingleFileWcs">
>>> <serviceName>dap</serviceName>
>>>
>>> <dataset name="level2_a" urlPath="wcs/foo" ID="wcs/foo" />
>>> <dataset name="level2_b" urlPath="wcs/foo" ID="wcs/foo" >
>>> <serviceName>otherService</serviceName>
>>> </dataset>
>>> </dataset>
>>>
>>>
>>> Is the dataset "level2_a" associated with the "dap" service??
>>
>> No. Though it would be if the "dap" serviceName element were enclosed in
>> an inherited metadata element, like this
>> <metadata inherited='true'><serviceName>dap</serviceName></metadata>
>>
>>> Is the dataset "level2_b" associated with the "dap" service??
>>
>> No. Not even if the "dap" serviceName was inherited, because the
>> "otherService" association overrides any inherited association.
>>
>>> Is the dataset "level2_b" associated with the "otherService" service??
>>
>> Yes, it is.
>>
>> Ethan
>>
>>>
>>>
>>> Nathan
>
> = = =
> Nathan Potter ndp at opendap.org
> OPeNDAP, Inc. +1.541.231.3317
>
>
>
