@JonathanGregory, thanks for the feedback. Your help with the wording is appreciated.
I thought the term "functional attributes" might be understood from context. I was looking for a short collective term that means "attributes that are functionally active in the CF interpretation of the variable". On review, I notice that the original sentence in CF-1.8 is kind of puzzling in its own way. > Boundary variable attributes which determine the coordinate type (units, > standard_name, axis and positive) or those which affect the interpretation of > the array values (units, calendar, leap_month, leap_year and month_lengths) > must always agree exactly with the same ... Is it appropriate here to explain distinction between the first and second groups? What is the best way to describe the general intention here, yet try to remain concise? For the purpose of this section, I think we only care about indicating which attributes are significant in some way to CF interpretation and processing. Let me tentatively merge the two groups, because the distinction may not be locally relevant, and try this simplified wording without "functional": > Boundary variable attributes which are significant to CF interpretation > (units, standard_name, axis, positive, calendar, leap_month, leap_year and > month_lengths) must always agree exactly with the same ... Do you like this, or have another suggestion? -- 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/265#issuecomment-737437164 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.
