This message came from the CF Trac system.  Do not reply.  Instead, enter your 
comments in the CF Trac system at https://cf-pcmdi.llnl.gov/trac/.

#107: CF Data Model 1.7
-----------------------------+----------------------------------------------
  Reporter:  markh           |       Owner:  [email protected]
      Type:  task            |      Status:  new                          
  Priority:  medium          |   Milestone:                               
 Component:  cf-conventions  |     Version:                               
Resolution:                  |    Keywords:                               
-----------------------------+----------------------------------------------
Comment (by markh):

 I would like to raise a concern regarding the proposed text for
 [wiki:Ticket107Text9Nov13Properties properties].

 There is explicit mention of:
  * Conventions
  * history
  * title
  * featureType

 as property names valid for Field instances.

 The CF-NetCDF conventions describe these as file attributes, not valid for
 individual data variables, in [http://cf-pcmdi.llnl.gov/documents/cf-
 conventions/1.6/apa.html Appendix A].

 I can see how featureType and Conventions could be treated as spanning
 across data variables, and the 'file only' constraint for NetCDF files
 being a logical extension of how CF instances are encode in NetCDF.  As
 such I am not concerned by these two.

 However, the use of history and title is inherited from the
 [http://www.unidata.ucar.edu/software/netcdf/docs/netcdf.html#Attribute-
 Conventions NUG] and their use is heavily linked to files, collections of
 Fields.

 As the data model does not have a sense of 'a collection of fields' I
 suggest that these are removed from the data model and put into the list
 of reserved property names, not to be used except in NetCDF files.

-- 
Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/107#comment:15>
CF Metadata <http://cf-pcmdi.llnl.gov/>
CF Metadata

This message came from the CF Trac system.  To unsubscribe, without 
unsubscribing to the regular cf-metadata list, send a message to 
"[email protected]" with "unsubscribe cf-metadata" in the body of your 
message.

Reply via email to