| |
Comment: |
Version 5 submitted; sending to standards council for input. The major changed text is to streamline the process of going to a full recommendation.
4.5.3 Grid Recommendation
Once a document is published as a Proposed Recommendation, a 24-month
timer will begin. During this period it is expected that operational
experience will be gained. Typically, this will mean that at least
two interoperable implementations (from different code bases and, in
the case of licensed code, from two separate license agreements) must
be demonstrated (if appropriate). The entire protocol or
specification should be implemented in the interoperable
implementations. If needed, the AD and relevant Council will determine
whether interoperable implementations (or implementations in software
at all) are necessary or whether operational experience can be gained
in a different fashion.
A document must remain at the GFD Proposed Recommendation level for a
minimum of 6 months before it is eligible for advancement to a Grid
Recommendation.
Within the 24-month period that begins with publication as a Proposed
Recommendation, operational experience must be documented in the form
of published documents, preferably one or more Experimental documents.
When sufficient operational experience has been achieved and
documented, an expert review will be solicited. Expert reviewers
should not be document authors or otherwise have a conflict of
interest. More than one expert review may be desirable. The review
may be solicited by any interested party, not only the document
authors and editors. However, including the athors/editors in the
review process, if possible, is desirable. Depending on the subject
matter, expert review may be desired from relevant standards bodies
(such as the W3C or IETF).
The review will provide input to the relevant Council in determining
whether the Proposed Recommendation should (a) become a Grid
Recommendation, (b) remain at the same status level, or (c) be moved
to obsolete or historical status. In any case, the relevant Area
Director(s) will briefly summarize the reasoning of the Council, also
providing this summary to the group chairs and/or authors. While a
formal solicitation for public comments will not typically be made,
the OGF will advertise the document’s status in moving to
Grid Recommendation, so that interested parties can provide input.
Small changes (as described in the Errata section below) may be
applied from the Proposed Recommendation to the Grid Recommendation,
but these should be used with caution, and changes that would impact
interoperability should be avoided. If substantive changes are
needed, a new Proposed Recommendation must be developed.
When a Proposed Recommendation document has not reached the Grid
Recommendation level after twenty-four months, and every twelve months
thereafter until the status is changed, the Council will review the
viability of moving to a Grid Recommendation. Following each such
review, the Council will decide whether to maintain the specification
at the same maturity level or to move it to obsolete or historical
status (thereby removing the Proposed Recommendation from further
consideration to advance). This decision will be communicated to the
OGF to allow the OGF community an opportunity to comment. This
provision is not intended to threaten a legitimate and active working
group effort, but rather to provide an administrative mechanism for
terminating a moribund effort.
4.5.4 Summary of Document Processing for Grid Recommendation Documents
A document may be returned to an earlier phase of the document
process, if deemed necessary.
1. Passage of time: At least 6 months since publication as a GFD-R-P
must pass.
2. Document review: A written expert review, summarizing operational
experience and documents published that reflect the
readiness of the document to become a Grid Recommendation.
Other parties may solicit this on behalf of the document
authors. It may be submitted to the document authors, the
AD, or directly to the OGF Editor.
3. Process check: When document authors or other interested parties
inform the OGF Editor of the desire to move the document to
Grid Recommendation status, the Editor will check that
requirements are met and seek consensus from the AD that the
document is ready for advancement to Grid Recommendation.
4. Final document preparation: If small changes are sought to the
final document, the submitters must propose them in the form
of a replacement document.
5. Public notice: The Editor will inform the OGF community of the
intention to move the document to Grid Recommendation,
including a summary of or link to the expert review.
6. Final review: The AD will present the result of the review and all
other evidence (such as Experimental documents) to the
appropriate Council, with a recommendation for whether to
change the status to a Grid Recommendation. The Council
will be given 15 days to read and comment on the document.
At the end of that period, the AD will gain consensus as to
whether the document is acceptable for advancement.
7. Republication: The OGF Editor will replace GFD-R-P with GFD-R in
the document, and apply any other needed changes. The
Editor will inform the OGF community of the new document.
|
