Thanks, this is perfect.
Joel, please go ahead and publish this as a replacement for GFD-R-P.090

Thanks to the group for efforts on this update!

updated the 'about this document' section as discussed on the GFSG call, added information about API versioning.  Greg, please check if this is what 
you had in mind.  It is not really a vderbatim copy from GFD.152, but I hope it is on target.

Sorry for the delay with this.  I'm checking with the standards council on readiness to go ahead with this document as an update to GFD-R.090. The 
document in the PDF, saga-core.pdf, looks ready to republish.

Update from OGF: Tracker is accurate; still being worked

This document was discussed by the steering council at OGF27.  The AD (Merzsky) confirmed there is still progress on this document, and a related 
experimental document is targeted.

The outcome we are hoping for is that SAGA will be republished as a REC document (from P-REC), along with the errata which come from the document in 
this tracker.

The GFSG discussed this extensively at the OGF 26 meeting.  The AD will speak with the group about this.  The GFSG urges SAGA-WG and related groups to
 move toward interop testing and associated experimental documents.  Then, the proposed errata could be rolled up as a final change in republication 
as a Recommendation (from the current status as Proposed Recommendation).  

The AD will get input.

Errata applied to the saga core spec, as discussed by mail.

updated on the OGF document series 2008-01-22.

also attach final pdf for previous layout fixes
A

small last-minute bugfix...

This is now advanced to 15-day GFSG final review, scheduled for the January 15 telecon or as soon thereafter as is available for schedule.

I've extracted just the saga-core-api-v1.0.pdf (the actual publication-ready document) so it's easier to link to.  This looks good, to me.

Because there were numerous changes, after public comment, we solicited an AD to review the doc and decide whether another round of public comments is
 warranted.  His response:

I've looked at the revised specification following on from the public comments.
+I'm happy (subject to I hope a minor clarification I've sent to Andre) for this
+document to be published as a proposed recommendation. There have been
+significant editorial changes as a result of the public comments, but the
+resulting changes have improved the document from an already high standard, and
+while some of the changes have been normative there has not been any
+significant expansion of the document from its original scope or form.

In my mind this is exactly when public comment is supposed to do. Having a
+further comment period before publishing it as a draft recommendation is
+unlikely to gain new comments. What is needed now is experience, and further
+reflection once this has experience has been obtained, and this will come as
+the document moves from a proposed to full recommendation at some future date.

Sent an email ping to Andre, Thilo & Christopher.

Public comment is now complete.  Authors/editors: please respond to comments in the PC tracker, or this one.  Then, submit a changed document (if 
needed).  Email newby AT arsc.edu when the document is ready for the next steps.

Attaching editable version.  The tgz contains a README with short instructions on document compilation.

Thanks for this submission.  Please upload an editable format, as well.  There is some sort of Gridforge anomaly with the document type (it didn't 
download correctly for me), so I'm uploading another copy-- same file, different name).

This will go into 15-day initial GFSG review, due for discussion during the October 30 telecon or as soon thereafter as it can be scheduled.