Russ et al,
I suggest that the Unidata recommendation needs to be changed to
commas only. I recall seeing recent cases where a convention name
includes spaces, but I have never seen a comma in such name. Case in
point, from Nan's follow-up:
Conventions = "OceanSITES 1.1, CF-1.1" ;
Also I agree that CF should be amended to allow more than one
convention within the Conventions attribute, comma separation only.
Does anyone see a problem with this?
--Dave A.
NOAA/PSD/CIRES
On Wed, Dec 21, 2011 at 2:46 PM, Russ Rew <russ at unidata.ucar.edu> wrote:
>
> The recommendation on the Unidata site for multiple conventions
>
> ?http://www.unidata.ucar.edu/netcdf/conventions.html
>
> is to use spaces rather than commas:
>
> ?It is possible for a netCDF file to adhere to more than one set of
> ?conventions, even when there is no inheritance relationship among the
> ?conventions. In this case, the value of the `Conventions' attribute
> ?may be a single text string containing a list of the convention names
> ?separated by blank space (recommended) or commas (if a convention name
> ?contains blanks), for example
>
> ? ?:Conventions = "XXX YYY" ;
Received on Wed Dec 21 2011 - 15:32:08 GMT
