John Caron wrote:
> We have a repository at Unidata of sample CF files, but they dont document which features they use.
> It would be very useful to start that documentation, and tie in back to CF section numbers or anchors.
>
> I propose we start a repository of sample files, ideally on the CF site, documented as to what CF
> features they use. It would be good if that documentation is a wiki (or equivilent), so that the
> initial person can make a start, then others can augment and comment on
I think it would be useful for each approved change to have a document
detailing the changes to be made to the CF spec. This document could be
referenced by the test data documents. As it stands, we have the trac
ticket discussions which can be very voluminous and even after approval
aren't always clear what exact changes to the specification are to be made.
Perhaps the closing comment to the trac ticket should be a detailed
change request. Though I think a separate (wiki?) document would be more
useful (both during the trac ticket discussion and afterwards for
documentation purposes).
Ethan
--
Ethan R. Davis Telephone: (303) 497-8155
Software Engineer Fax: (303) 497-8690
UCAR Unidata Program Center E-mail: edavis at ucar.edu
P.O. Box 3000
Boulder, CO 80307-3000 http://www.unidata.ucar.edu/
---------------------------------------------------------------------------
Received on Thu May 08 2008 - 10:07:23 BST
