In the light of the point made by @DocOtak (https://github.com/cf-convention/cf-conventions/issues/221#issuecomment-562369361), I'm happy to drop the idea of sub-directories, and just put the file `conformance.adoc` in the same top-level directory as the other conventions' `*.adoc` files.
The idea of putting the conformance document as an appendix to the main conformance document is tempting, but I think that it should remain separate. This is because (quoting from http://cfconventions.org/Data/cf-documents/requirements-recommendations/requirements-recommendations-1.7.html): _"This document is intended to be a concise summary of the CF Conventions document. If there are any discrepencies between the two, the conventions document is the ultimate authority."_ The conventions shouldn't contain a summary of itself that may disagree with itself! (Thanks to @RosalynHatcher for highlighting this.) @marqh Thank you very much for your offer of help with the Travis stuff - much appreciated -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/221#issuecomment-567405618 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].
