Re: [CF Metadata] #157: Clarification to Section 2.3 - Naming Conventions

[CF Metadata]

#157: Clarification to Section 2.3 - Naming Conventions
-+--
  Reporter:  ros |  Owner:  cf-conventions@…
  Type:  defect  | Status:  new
  Priority:  medium  |  Milestone:
 Component:  cf-conventions  |Version:
Resolution:  |   Keywords:
-+--

Comment (by heiko.klein):

 Hi,

 concerning beginning underscores. We have alread one exception for
 attributes with _FillValue. Currently we have to add some other attributes
 starting with _ because netcdf-java needs them, e.g. _CoordinateAxisType
 when distributing through thredds. I wouldn't like to invalidate these
 datasets.

 I see any good reason why we would need a '''must''' rather than a
 '''should''' for variables/attributes and dimensions? Where does this
 cause problems or misunderstandings?

 Heiko

--
Ticket URL: 
CF Metadata 
CF Metadata

Re: [CF Metadata] #157: Clarification to Section 2.3 - Naming Conventions

[CF Metadata]

#157: Clarification to Section 2.3 - Naming Conventions
-+--
  Reporter:  ros |  Owner:  cf-conventions@…
  Type:  defect  | Status:  new
  Priority:  medium  |  Milestone:
 Component:  cf-conventions  |Version:
Resolution:  |   Keywords:
-+--

Comment (by davidhassell):

 Hello,

 Starting an attribute with a [0-9] (e.g. `133Xe_concentration`) is a
 different case to starting it with an underscore (e.g. `_myAttribute`),
 because of the netCDF "system use" rule. I think that I'm in favour of
 disallowing leading underscores, because of the potential conflicts
 between the netCDF and CF namespaces. Could we allow:

   Variable, dimension and attribute names '''must''' begin with a letter
 '''or digit''' ...

 Are there many existing dataset which use leading underscores?

 David

--
Ticket URL: 
CF Metadata 
CF Metadata