Dear Jonathan and Martin,
What I was trying to do here was legitimise an already established practice in
at least two communities in the observational oceanographic domain with
thousands of files in existence with the non-standard usage of the Conventions
attribute. I also carried the practice
Roy et al.,
> Martin's comments on namespace highlight a concern I
> identified whilst doing the research for the SeaDataNet
> specification. Several communities have added large numbers
> of both global and variable attributes with no indication of
> namespace. Not only does this make it d
Hello Phil,
> But, assuming these could be resolved, what do people think about
> use of '.' as a namespace separator? Good idea? Bad idea?
>
> Some recent postings to this list have suggested using a 'cf_'
> prefix, with the implied suggestion of a '_' namespace
> separator. IMHO, this approach
Dear Martin and Angelika,
Thank you for your proposals. Thank you also to Philip and Jonathan for their
useful comments in the discussion of these names. I think the molecular
hydrogen and dimethyl sulphate names are unproblematic and well defined. The
following four names are accepted for incl
With respect to netcdf (at least the C version),
it is the case that these characters can appear
unescaped: _.@+-
It should be noted however that dot in particular
causes problems for accessing remote datasets
through DAP because the dot character is used
in DAP constraints to specify fields ins
Any of these special characters, other than the '_', would probably
cause problems for code that deals with NetCDF files. The '.' is used
in Matlab for access to structures, and the '@' is used to identify a
variable as a function handle. There are work-arounds, but they
likely wouldn't add effici
Hi Nan,
Would the CF web site be an appropriate place for communities to post the
attributes they have added to CF - either with or without namespace prefixes?
Cheers, Roy.
From: CF-metadata [cf-metadata-boun...@cgd.ucar.edu] On Behalf Of Nan Galbraith
