@ngalbraith regarding the `references` attribute, I went back and checked [Appendix A](http://cfconventions.org/cf-conventions/cf-conventions.html#attribute-appendix) and was relieved to see it's valid as both a global and variable attribute. I don't know if there might still be software issues as a result or not, but I think we're ok in terms of the by the book rules for that, hopefully. The IOOS Compliance Checker [4.3.2](https://github.com/ioos/compliance-checker/releases/tag/4.3.2) now checks attributes against the rules in this appendix, so if we weren't, our metadata profile would be failing our own checker, which isn't great.
We do suggest data providers add an IOOS label to the `Conventions` attribute (e.g. `Conventions = "CF-1.6, ACDD-1.3, IOOS-1.2"`) in our profile, so I think we're good there as well. @GeyerB @japamment I noticed there's been a lot of traffic on the discuss repo over the past week accepting new standard names, I just wanted to check that this issue and the list of new names in the [comment above](https://github.com/cf-convention/cf-conventions/issues/216#issuecomment-565064929) are on your radar and can be approved to be added to Version 71 due out soon. We would very much appreciate it. Many thanks! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/216#issuecomment-575727388 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
