<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Bryan, Jeremy,<br>
<br>
Thanks muchisimo for finding the energy to send out this summary of
action plan commitments. It's almost more valuable arriving a bit late
-- at about the right time to see if the activities in question were
successfully initiated or not. Rocky posed the question of how we
should turn this document into a reporting mechanism. One partial
answer is that in preparation for the next meeting we will all provide
written responses and then look over our collective successes at the
next meeting. As to mid-term (between-meeting) reporting, the level of
detail required is so high that I cannot imagine it being handled well
by email. It seems a good candidate to be put on a Wiki and
collectively edited detail by detail on the parts we each "own". Kyle
-- does the PCMDI site include a Wiki? Other volunteers?<br>
<br>
Regarding the "CF Action Plan" that you sent around on 9/26 -- here is
an interim report on the topic of "<b>how best to handle in situ
observations</b>", that has my name on it. Some interesting things are
happening.<br>
<blockquote>Mike Johnson, the NOAA program manager in charge of NOAA's
climate observing system effort, ponied up some funds for a contract to
write up the DAPPER (OPeNDAP) protocol as a formal specification. Joe
Sirott issued a draft of that specification on Oct. 3
(<a class="moz-txt-link-freetext" href="http://www.epic.noaa.gov/epic/software/dapper/dapperdocs/conventions/">http://www.epic.noaa.gov/epic/software/dapper/dapperdocs/conventions/</a>).
Email discussion has been vigorous -- very encouraging to see. Joe
expressed a preference to manage changes on this document informally at
least for the next few months, during which modifications may be
relatively rapid. Thereafter I hope we can migrate the document to the
CF site at PCMDI and see if we can move towards an orderly issue
tracking in the evolution of the standard. The current draft does not
handle point data (scattered) nor track data. Nor was it intended to.
The pressing need to support these data types, however, has been voiced
already in the dialog. Hopefully those needs will be addressed as
DAPPER evolves.<br>
</blockquote>
- Steve<br>
<br>
=========================================<br>
<br>
Bryan Lawrence wrote:
<blockquote cite="mid1160308447.12586.28.camel@localhost.localdomain"
type="cite">
<pre wrap="">Hi Folks
At the June meeting we identified some key actions for the GO-ESSP
community over the current year. Attached are the notes from that
discussion outlining what we agreed are significant things to be working
on. I'm sorry they're so late.
I'd be glad of corrections and comments. I plan to hassle the named
folks around the end of the year to see how we're going ...
(I'll try and address the GO-ESSP wiki issues shortly too, we're aware
that the old wiki is locked).
Cheers
Bryan</pre>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
GO-ESSP mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GO-ESSP@ucar.edu">GO-ESSP@ucar.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.ucar.edu/mailman/listinfo/go-essp">http://mailman.ucar.edu/mailman/listinfo/go-essp</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
--
Steve Hankin, NOAA/PMEL -- <a class="moz-txt-link-abbreviated" href="mailto:Steven.C.Hankin@noaa.gov">Steven.C.Hankin@noaa.gov</a>
7600 Sand Point Way NE, Seattle, WA 98115-0070
ph. (206) 526-6080, FAX (206) 526-6744</pre>
</body>
</html>