Differences

This shows you the differences between two versions of the page.

--- public:00-sip-ra:03-adoption-process:03-2-the-adoption-process-in-detail:03-2-8-finalization-and-revision [2026/09/12 18:33] – removed - external edit (Unknown date) 127.0.0.1
+++ public:00-sip-ra:03-adoption-process:03-2-the-adoption-process-in-detail:03-2-8-finalization-and-revision [2026/09/12 18:34] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== 3.2.8 Finalization and Revision ======
+[[public:00-sip-ra:03-adoption-process:03-2-the-adoption-process-in-detail:start|Return to The Adoption Process in Detail]]
+Any specification adopted by OMG, by any mechanism, whether through an RFP or otherwise, is subject to finalization.
+A Finalization Task Force (FTF) is chartered by the Technical Committee that recommended the specification. The FTF corrects problems reported by early users of the published specification.
+The FTF first collaborates with OMG's Technical Editor to prepare a cleaned-up version of the Alpha Specification by removing submission-specific material. This cleaned-up version is the Beta 1 specification, which OMG makes publicly available on its website.
+The FTF then works through the list of bug reports (issues) submitted by users of the Beta 1 specification. The FTF produces a Finalization Report and another Beta specification, usually Beta 2, which becomes a candidate for formal publication.
+Once endorsed by the Architecture Board and adopted by the relevant Technical Committee and Board of Directors, OMG publishes the specification as the final Formal Specification.
+Long-term maintenance of OMG specifications is handled by a sequence of Revision Task Forces (RTFs). Each RTF is chartered to address residual problems in the most recently published version of the specification.
+For full details, see Policies and Procedures Section 4.4 [P&P].
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>