|
|||||
|
|
Government Domain Task Force (GovDTF)FTF: Records Management Service Finalization Task Force
|
|
|
|||||||||||||||||||
IndexReporting IssuesAnyone, OMG member or not, may submit an Issue with the RMS-FTF. Issues may be reported by either the Web Form or eMail (links below) In either case report only one issue per form or email. Do not report an issue as "urgent" unless it is stopping production of a product since the FTF is required to resolve urgent issues within two (2) weeks. Background:The RMS-FTF was chartered in the Domain Technology Committee Plenary on 27-March-2009 in anticipation of a successful DTC electronic vote. The mission of the RMS-FTF is to produce the initial Beta specification from the Alpha specification as approved by the GovDTF and the Architecture Board. An F/RTF is chartered by the appropriate TC to gather comments on a particular OMG Specification from OMG Members and others, and to decide whether changes are necessary in response to those comments. An F/RTF may recommend changes that provide clarification of the wording without changing its intent, or minor revisions that correct the detail of the specification without adding or removing significant functionality. Enhancements to the specification are outside the scope of the F/RTF, and must be deferred to a later adoption process (see section 4.2). Issue ResolutionThe chair is responsible for moderating discussion of an issue, ensuring that a response is formulated, and organising the poll on that response. The chair will maintain an issue log that serializes issue discussion and documents resolution. From this issue log the Final Report of the RMS-FTF will be generated. Email Discussion: All email discussion is to take place on the RMS-FTF@omg.org mail list. This mail list is archived and mail is sorted by the issue to which it pertains. Therefore include the OMG Issue Number in the subject line of each message and discuss only one issue in a given email (unless of course your point is that two issues are redundant, dependent, or otherwise coupled.) The eMail discussion will be recorded in the Issue Log. Meeting Discussion: Most meetings will be held by teleconference. Whether a teleconference or face-to-face, the chair or a designated scribe will maintain minutes of the discussion for capture in the issue log. Issue Ballots: When the chair initiates an email poll (ballot) he must set a voting deadline and take reasonable steps to ensure the F/RTF members are aware of it. To pass any motion in an F/RTF requires a simple majority of the non-abstaining votes cast. Quorum for all F/RTF polls, however conducted, is half the F/RTF membership; currently Four (4). The chair will record all ballots. Members:All members are to review the OMG Policy & Procedures, Section 4.4, "Finalisation and Revision". (http://doc.omg.org/pp/2009-01-02) Larry Johnson, Tethersend Consulting is the Chair of the RMS-FTF Members can only be added or removed by a successful motion in a Domain Technology Committee Plenary at an OMG Technology Committee meeting (removal can also be effected by the resignation of the member, of course). Members are required to vote.
Members shown in bold are submitters with veto power (those who submitted Business Questionnaires acceptable to the Board of Directors.) A "No" vote is not a veto. To exercise veto power on an issue the qualifying member must explicitly vote "Veto".
Quorum is Four (4). Schedule
Related Documents
Activity History:20091207, Long Beach TC Meeting – The FTF schedule was changed to report delivery for the Minneapolis meeting in June 2010. 20090624, San José, Costa Rica TC Meeting – Initial FTF meeting/teleconference was held during the San José, Costa Rica TC Meeting. Issues identified by the original submitters were reviewed and those that were still unresolved were submitted to the FTF. 20090327, Washington DC TC Meeting – The RMS-FTF was officially chartered by the Domain Technology Committee.
|
|||||||||||||||||||
Last updated on: 01/30/2010
Last updated on: 03/02/2010 |