Subject: FW: [members] Changes to OASIS TC Process Policy
Most of you probably saw the attached email from the TC Administrator regarding changes in the OASIS TC Process. Please make note of the changes that affect us as an operating TC, including the opportunity for members to declare themselves as Persistent Non-Voting Members and the update to the Leave of Absence request procedure.
Of greatest interest, I believe, is the explicit policy of precedence of between the text of the specification and any separate schemas or XML fragments – according to the updated policy, the separate text files take precedence over the specification text. This is different from what we declared in our specifications – for example, DPWS 1.1 Section 7 says “Normative text within this specification takes precedence over normative outlines, which in turn take precedence over the XML Schema [XML Schema Part 1, Part 2] descriptions, which in turn take precedence over examples.” Similar language appears in WS-Discovery (but not in SOAP-over-UDP, which doesn’t have any separate files). I have sent an email to the TC Administrator asking whether the newly adopted TC Process takes precedence over what we declared in our specifications, and will let you know the response.
For your reference, I’ve attached a red-line version showing the differences between the previous TC Process and the newly-adopted Process.
Toby Nixon | Senior Standards Program Manager | Windows Device and Storage Technologies | Microsoft Corporation
On 31 July 2009 the OASIS Board of Directors approved a set of revisions to the TC Process. The effective date of the new Policy is 1 September 2009 and can be seen here: http://www.oasis-open.org/committees/process-2009-07-30.php. A change-marked PDF copy is available upon request and will be available on the TC Process Policy web page on or before the effective date.
The major changes are as follows:
1. Persistent Non-Voting Member. A new role has been defined, allowing a TC Member to declare their non-voting status. The process by which a Member makes such declaration as well as revoking it is established. (See Definitions: x. as well as Section 2.4.3)
2. Charter submissions. Charter submissions must now include statements of support from the Primary Representatives of Organizational Members listed as co-proposers. They will also be notified if the Charter submission is amended in any way. (See Section 2.2)
3. Schemas, XML instances, etc. associated with a specification. The Process now explicitly states that if a discrepancy occurs between the plain text file and the specification document, the definition in the separate file prevails. (See Section 2.18)
In addition, some smaller changes were made in an attempt to clarify some potentially confusing language:
4. Explicitly state that all notifications to the OASIS TC Administrator must be sent to firstname.lastname@example.org rather than any one individual. (See Definitions: v.)
5. Remove language that was inadvertently left in the Process and obsolete (references to Joint Committees and the need to notify the Chair if you have signed up for a new TC but are unable to attend the first meeting).
6. Leaves of Absence - proper procedure for submitting requests. (See Section 2.6)
7. Standing Rules - allowing for amendments and recisions, as well as explicitly stating that they must be posted on the TC web page in order to be enforceable. (See Section 2.9)
8. Clarification with regard to what can and cannot be changed after approval of a Committee Draft, Committee Specification, or OASIS Standard. (See Section 2.18)
9. Clarification of the Designated Cross References language. (See Section 2.19)
10. Clarification of the Appeals process. (See Section 4.2)
If you have any questions please feel free to contact me.
Mary P McRae
Director, Standards Development
Technical Committee Administrator
OASIS: Advancing open standards for the information society
twitter: fiberartisan #oasisopen
Standards are like parachutes: they work best when they're open.