OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: EM-Msg Meeting Notes for 11-11-08 Approved


Hi Elysa, Everyone,

I wanted to report that the EM Messages and Notification SC voted to 
approve the Meeting Notes from 11-11-08, so our recommendation is 
approved.

Without getting into the details of the discussion on the various 
comments, which is the task of the SC, I wanted to provide the 
following for our next TC meeting.

For reference, I am copying here the TC Process that applies to errata:

3.5 Approved Errata

A TC may approve a set of Errata to an OASIS Standard as "Approved 
Errata" to the corrected specification by:

(a) Adopting the set of proposed corrections as a Committee Draft, in 
the form of a list of changes, and optionally accompanied by a copy 
of the original specification text marked to incorporate the proposed 
changes.

(b) Confirming by Full Majority Vote that the proposed corrections do 
not constitute a Substantive Change.

(c) Submitting the proposed corrections for a 15-day public review, 
and completing that review, pursuant to Section 3.3.

(d) After the public review, confirming the proposed corrections as 
Approved Errata by a Full Majority Vote.

Once approved, the Approved Errata shall be with the specification it 
corrects, in any publication of that specification. Disposition of 
Approved Errata must be identified in the subsequent Public Review 
Draft of the corrected specification.

A TC may not adopt Approved Errata to an OASIS Standard more than 
once in any consecutive six-month period.

Here is Section 3.3 mentioned in the above quote:

3.3 Approval of a Committee Specification

After the public review of a Public Review Draft the TC may approve 
the specification as a Committee Specification. If any comments have 
been received during the most recent Public Review period, that vote 
may not commence any earlier than 7 days after the last day of that 
Public Review. The approval of a Committee Specification shall 
require a Special Majority Vote. The TC Chair shall notify the TC 
Administrator that the TC is ready to vote on the approval of the 
specification, and provide to the TC Administrator the location of 
the editable versions of the specification files. The TC 
Administrator shall set up and conduct the ballot to approve the 
Committee Specification.

I suggest that we should limit our discussion to the issues of the 
timeline for completing any work that fits into the limitations of 
errata v. 1.2 v. 2.0, otherwise we'd end up rehashing several hours 
of discussions.

However, if you want to review the comments and their inclusion into 
Best Practices, 1.2 or 2.0 categories, you can download the last 
spreadsheet 
http://www.oasis-open.org/apps/org/workgroup/emergency-msg/download.php/29957/CAP-NextGen-CommentsList_v1.4.xls

Cheers,
Rex
-- 
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]