Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:00-sip-ra:03-adoption-process:03-2-the-adoption-process-in-detail:03-2-1-development-and-issuance-of-rfp [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-1-development-and-issuance-of-rfp [2026/09/12 18:34] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== 3.2.1 Development and Issuance of RFP ====== | ||
| + | |||
| + | [[public: | ||
| + | |||
| + | RFPs, such as this one, are drafted by OMG Members interested in adopting an OMG specification in a particular area. The draft RFP is presented to the appropriate Task Force (TF), discussed and refined, and, when ready, recommended for issuance. If endorsed by the Architecture Board, the RFP is issued as an OMG RFP by a Technical Committee (TC) vote. | ||
| + | |||
| + | Under the terms of OMG's Intellectual Property Rights Policy [IPR], every RFP SHALL include a statement of the IPR Mode under which any resulting specification is published. To achieve this, RFP authors choose one of the three allowable IPR modes specified in [IPR] and include the selected IPR Mode in the RFP. See [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||