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:97 biard]: > As I read this discussion, I can't help feeling that we are over- thinking this. A physical analogy to the file/variable attribute question is a box with widgets inside it, all of which have various labels on them. The label on the box named "handling" tells me about the handling of the box (or the collection of widgets in the box, taken as a whole). A label on a widget in the box that is also named "handling" tells me about the handling of the widget. The only way to know whether or not to treat the information on a widget label as replacing or adding to the information on the box label is to read and understand them both. > > Without coming up with some sort of formalized grammar and vocabulary for this, I don't see any good way to resolve the "person-in-the-loop" issue. I am also not convinced that there is a need to resolve it. If the attribute is named "comment", I think it is almost assuredly OK to just treat them as independent. If the attribute is named source, it's going to depend on details of what the attribute values are. And so on, and so forth. That's exactly what I was saying in my penultimate paragraph, but you've put it better by not suggesting any best practice *in processing*. I think the global/variable attribute as currently formulated does not allow an unambiguous resolution, and so the data model cannot either. -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/95#comment:98> 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.
