Dear @Dave-Allured > Hmmm. I can't agree with deleting the subsection break. There is too much > history behind it, and it makes a lot of sense the way it is. This style is > widely used elsewhere in the conformance document.
The conformance document follows the standard document in sections and subsections. When someone wonders which section to put something in, because the distinction doesn't seem clear, I think it's reasonable to infer that the distinction is actually unnecessary, and we can save thought and possible confusion by abolishing it. Introducing divisions is good for efficiency when the amount of stuff is too hard to navigate without them, but if they're not essential I'd rather not have them, because they make things harder. That's the reason for my response! I'm always uncomfortable when a section has a single subsection. I don't see the point in that. I know there are other instances in the standards document and I don't like them but we have more serious matters to attend to than this mild discomfort! :-) > I think we should either move sentences, or leave this exactly the way it is > now with my current additions. I mildly favor the latter. Your thoughts? If you prefer not to muddy the waters by removing the division, I'd leave it where it is and we will live with unclear rationale. Best wishes Jonathan -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/298*issuecomment-812074190__;Iw!!G2kpM7uM-TzIFchu!l2BfYOJ3Zj4et7CZALn5WFEIZHUFXI-h6XoiviHTvMtzg8o_IS9_ulmxZ9vca_xA_ZWIYcXZy3Q$ 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].
