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 rhattersley): Replying to [comment:100 davidhassell]: > The lack of an unambiguouus resolution doesn't affect the data model ... As things stand I disagree with that interpretation. But perhaps discussing a new aspect will help shed light on the issue, so I'd like to bring up the subject of "non-standard attributes"... When one describes the phenomenon in a data variable, one is not confined to using the "standard_name" attribute and can utilise the free-form value of the "long_name" attribute instead. Similarly, one may also use "non- standard attributes" to record additional facets of the metadata. This is explicitly recognised in the conventions document and much use is made of this extensibility in practice. In the light of which, the data model needs to reflect this open-ended capability and include an explicit definition of non-standard attributes. NB. The conventions also state that, "Application programs should ignore attributes that they do not recognise or which are irrelevant for their purposes." But this statement does not apply here as the data model is deliberately intended to be generic and cannot be categorised as an application program. -- Ticket URL: <https://cf-pcmdi.llnl.gov/trac/ticket/95#comment:101> 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.
