More than one name in Conventions attribute
|Reported by:||Dave.Allured||Owned by:||davidhassell|
It is proposed to support the listing of more than one convention name in the Conventions global attribute. As of CF-1.6, only the CF identification by itself is allowed. The option of a list has been in Unidata's recommendations for a long time; see references. There was some community support for this in the recent mailing list discussion.
I would like to present this in two parts. This trac ticket is part 1, which proposes to adopt verbatim, the Unidata language for listing more than one convention name. The original Unidata recommendation allows the list of names to be separated by either spaces or commas.
Part 2, which I plan to file as a separate ticket, would propose more detailed parsing rules and would probably replace the syntax description of part 1. The main objectives of part 2 would be to accommodate both unambiguous machine parsing, and flexibility in allowable characters in convention names.
Why two tickets? I think that part 1 has a better chance of approval. It accomplishes the most important objective of multiple conventions in a workable way. If part 2 succeeds, it can replace part 1, sooner or later.
The mailing list discussion beginning December 2011 should be considered part of the record for this proposal.
Text of proposed changes
Two new paragraphs are to be added at the end of the current section 2.6.1, Identification of Conventions:
It is possible for a netCDF file to adhere to more than one set of conventions, even when there is no inheritance relationship among the conventions. In this case, the value of the Conventions attribute may be a single text string containing a list of the convention names separated by blank space (recommended) or commas (if a convention name contains blanks). This is the Unidata recommended syntax from NetCDF Users Guide, Appendix B.
When CF is listed with other conventions, this asserts the same full compliance with CF requirements and interpretations as if CF was the sole convention. It is the responsibility of the data-writer to ensure that all common metadata is used with consistent meaning between conventions.
In the conformance document, add a new second line under 2.6.1 Identification of Conventions:
- The Conventions attribute may be a single text string containing a list of convention names separated by blank space or commas, one of which shall be the full CF string as described above.
Ticket #27, Use namespace tags to include other conventions, 2008
(Previous proposal and discussion of Conventions attribute, not yet adopted)