Fyi ... (01)
In view of the Ontolog policy that in the absence of established an
explicit, established process, our (the Ontolog) community process
will default to the current OASIS TC Process (ref.
http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid20 ) ...
please note the announcement of the "Changes to OASIS TC Process
Policy" below. (02)
Regards. =ppy (03)
Peter Yim
Co-convener, ONTOLOG
-- (04)
---------- Forwarded message ----------
From: Mary McRae <mary.mcrae@xxxxxxxxxxxxxx>
Date: Wed, Aug 5, 2009 at 12:25 PM
Subject: [members] Changes to OASIS TC Process Policy
To: members@xxxxxxxxxxxxxxxxxxxx, tc-announce@xxxxxxxxxxxxxxxxxxxx
Cc: OASIS TAB <tab@xxxxxxxxxxxxxxxxxxxx>,
board-plus@xxxxxxxxxxxxxxxxxxxx, OASIS Staff
<staff@xxxxxxxxxxxxxxxxxxxx> (05)
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. (06)
The major changes are as follows: (07)
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) (08)
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) (09)
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) (010)
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 tc-admin@xxxxxxxxxxxxxx rather than any
one individual. (See Definitions: v.) (011)
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). (012)
6. Leaves of Absence - proper procedure for submitting requests. (See
Section 2.6) (013)
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) (014)
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) (015)
9. Clarification of the Designated Cross References language. (See Section 2.19) (016)
10. Clarification of the Appeals process. (See Section 4.2) (017)
If you have any questions please feel free to contact me.
Regards,
Mary (018)
Mary P McRae
Director, Standards Development
Technical Committee Administrator
OASIS: Advancing open standards for the information society
email: mary.mcrae@xxxxxxxxxxxxxx
web: www.oasis-open.org
twitter: fiberartisan #oasisopen
phone: 1.603.232.9090
Standards are like parachutes: they work best when they're open. (019)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (020)
|