Dear Bert, Jonathan, and all, I would like to try to summarize the ideas that have been discussed in the form of some broad proposals that I hope could be acceptable to allow us conclude this issue. I welcome your feedback.
In no particular order: **(A)** The governance is written up along the lines of @hrajagers ideas: https://github.com/cf-convention/cf-conventions/issues/153#issuecomment-703858946 **(B)** Comprehensive conformance rules are written up for UGRID. These should be maintained alongside UGRID in its repository, and referenced from (not copied into) the [CF conformance document](http://cfconventions.org/cf-conventions/conformance.html). **(C)** Update the aforementioned [CF Appendix A](https://cfconventions.org/Data/cf-conventions/cf-conventions-1.8/cf-conventions.html#attribute-appendix) to include the relevant UGRID attributes, thereby making them visible to all users. Mention in the governance rules that this table needs maintaining. **(D)** Based on @hrajagers [previous comment](https://github.com/cf-convention/cf-conventions/issues/153#issuecomment-703858946), dropping the standardisation of `cf_role` on the "connectivity" variables, but retaining it on the mesh topology variable. This is related to my previous comments [about the use of datasets with meshes but no data](https://github.com/cf-convention/cf-conventions/issues/153#issuecomment-704435832), which I now withdraw. A mesh topology variable can actually contain multiple domains in the CF-sense, one of which can "picked out" by a data variable. This makes it sufficiently different, I realise, to the proposed CF domain variable (#301) that we shouldn't to unify them at this time. **(E)** Add some text to CF 5.8 (Domain Variables) (currently being proposed in #301) to explain the UGRID mesh topology variable and how it relates to a domain variable. It may the case that the occasional note relating to UGRID would be useful in other sections. I don't propose to review for these, but they could always be added as when it was felt to be useful. Thanks, David -- 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/153#issuecomment-710122506 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].
