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 russ):

 Jim,

  My primary concern was a potential for misunderstanding the meaning
  of "unique" in the phrase "for one or more variables where each has
  a unique standard name".  The standard_name attribute of any
  variable that has such an attribute is already unique, in the sense
  that a variable cannot have two attributes with the same name.

  The only other interpretation of "unique standard name" I can think
  of would rule out multiple variables with the same standard_name
  attribute sharing the same ancillary variable.  I don't see a good
  reason to rule out that case, and I provided an example where it
  might be useful.

  The other minor change I suggested was omitting "two or more",
  because in fact the second form of the standard_name string value is
  also required to provide a standard name modifier for a single
  variable.

 --Russ

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