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/.

#74: Allow sharing of ancillary variables among multiple data variables
---------------------------------------+------------------------------------
  Reporter:  [email protected]  |       Owner:  
[email protected]             
      Type:  enhancement               |      Status:  new                      
                 
  Priority:  medium                    |   Milestone:                           
                 
 Component:  cf-conventions            |     Version:                           
                 
Resolution:                            |    Keywords:  "ancillary data" 
"standard name modifiers"
---------------------------------------+------------------------------------
Comment (by [email protected]):

 Folks:

 Almost a month has elapsed since I summarized the status of this trac
 item.  In the summary, I advocated updating the CF conventions as
 identified in the original proposal above, which I will repeat here:

 Change the text in the CF metadata conventions section 3.3 that reads

 "A standard name is associated with a variable via the attribute
 standard_name which takes a string value comprised of a standard name
 optionally followed by one or more blanks and a standard name modifier (a
 string value from Appendix C, Standard Name Modifiers)."

 to

 "A standard name is associated with a variable via the attribute
 standard_name which takes a string value that can have either of two
 forms. The first form is a standard name alone. The second form is a
 blank-separated list beginning with one or more standard names and ending
 with a single standard name modifier (i.e. standard_name [standard_name
 ...] standard_name_modifier). The standard name modifiers are defined in
 Appendix C, Standard Name Modifiers. This second form permits a single
 variable to provide ancillary data (see section 3.4) for two or more
 variables where each has a unique standard name."


 Note that...

 Changes to CF software tools are required. For example, the CF_checker,
 which validates the standard_name attribute needs to change. However, it
 does not require any change to software that uses the complete attribute
 simply as an identifying string (e.g. to label plots, etc.)

 No one has taken issue with the summarization for this trac item in the
 last 3 week.

 I support this enhancement.  Does the conventions committee support this
 enhancement ?

-- 
Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/74#comment:13>
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