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

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

 Replying to [comment:63 markh]:
 > Replying to [comment:62 bnl]:
 > > Replying to [comment:61 markh]:
 > >
 > > > Should a CF Field know which of it's attributes were encoded in the
 file as globals and which were encoded as data attributes?
 > >
 > > Absolutely not. It's irrelevant. How can it matter? The key is in the
 word "encoded", the data model should be independent of the encoding.
 >
 > I'll rephrase my question:
 >
 >   Does the semantics of an attribute include it's typing, variable or
 global?
 >
 >   i.e: Is a global attribute of 'institute' able to be differentiated
 from a data variable attribute of 'institute' within the scope of a Field
 in the data model?

 One of the nice things about not having read the rest of the discussion,
 is that I can just dive in with a confident: No!

 Global attributes are an artefact of file based encoding, a convenience
 artefact at that ...

 ... so one only ends up with an issue when there is a global attribute and
 a field attribute, and they differ, and we have a convention that in this
 case, one effectively ignores the global attribute while creating the
 field. Thereafter it matters not (or should not matter).

 This becomes obvious when one encodes the same content alongside different
 fields in a different file ... the original global attributes are just
 field attributes ... one might, I suppose, in the new file grab out common
 attributes and encode them as global file attributes, but that's just the
 encoding.

 >
 > mark

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