Sorry for the confusion between field/data and construct/variable. My question was about having a reference to the domain variable **in addition** to the attributes that already describe the domain (implicitly) on the data variable so I am not sure how it would break backwards compatibility.
I agree that it introduces some redundancy, but I would argue that is already the case when several data variables share the same domain and each of these data variables defines this very same domain implicitly with their attributes. Allowing a reference to the domain variable on data variables would add a way to check that the attributes on these data variables (that are meant to describe the same domain) are consistent with each other. -- 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/301#issuecomment-708318429 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, 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 cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
