For me, Ryan's suggestion of a cf-prefix on attributes would be too large a break in backwards-compatibility; I don't think I could support it. Karl's suggestion of listing cf attributes somewhere seems more reasonable. Though maybe it would be better to put it in a separate global attribute rather than in Conventions, which could be a list of multlple conventions?
I also worry about a list of every CF attribute getting really long and being fragile to changes. What if instead of specific attributes, there was a controlled vocabulary of concepts or elements to list, so you'd have something like `cf-elements = "bounds, climatology, flags, mapping, stdname"`? -- 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/273#issuecomment-649656940 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].
