| Working
document |
Process event |
| <version
number> Alpha specification |
A proposed specification (called a Revised Submission) which has been adopted
by the OMG Board of Directors. |
| <version
number> Beta specification |
The Alpha
specification as it moves through its finalization prior to formal
publication. There are several Beta specifications. <version
number> Beta 1 represents the Alpha specification with all
non-normative sections called out by the RFP removed by the OMG
Technical Editor and reviewed by the submitters (formerly called the
Final Adopted
Specification). The Beta 1 specification serves as the baseline document for a FTF
and becomes the document against
which all issues are filed. <version number> Beta 2 represents the end product
(finalized specification) of the FTF (formerly called the Proposed
Available Specification). A <version number> Beta 3
specification is the document used in final author review. If a 2nd FTF is chartered,
the Beta 2 specification serves as its input and its output is
designated <version number> Beta 3. The author review
document for a 2nd FTF is <version number> Beta
4. |
| Version 1.0 or x.0 |
1.0 is the formal publication
of first release of the specification. x.0 is the formal publication
of a major revision to the specification. |
| Version x.y |
RTF begins. This is
the baseline document, formally published, for a RTF and the
document against which issues are filed. |
| <version
x.y+1> Beta 1 specification |
RTF
report completed and adoption vote underway. There may be more
than one beta, labeled <version number> Beta n, if the RTF
issues more than one report. This document was formerly called
the Proposed Available Revision. If only one document produced,
it is designated <version number> Beta 1. The author review
document for a RTF is <version number> Beta 2 (assuming only one
report).
|
| Version x.y+1 |
Formal publication
of a minor revision to the specification. |
