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: Certification of Use

Allen -

The Partnership for Public Warning (PPW), an OASIS member 
organization in good standing, is pleased to certify its successful 
use of the CAP 1.0 committee draft specification in demonstrations 
and field trials by a number of its member organizations and 
companies as well as by its individual representative to OASIS and 
your Emergency Management Technical Committee.

In addition, we would like to acknowledge our receipt and review of 
the OASIS IPR policy at 

PPW sees CAP as a much-needed element in improving and integrating 
public warning and emergency response systems nationally and locally. 
We look forward to its speedy submission for adoption as an OASIS 
standard, and to its future refinement based on expert review and 
practical experience.


   Art Botterell
   Partnership for Public Warning

At 7:02 PM +0000 2/5/04, emergency-tc@earthlink.net wrote:
>To: emergency@lists.oasis-open.org
>From: emergency-tc@earthlink.net
>Subject: [emergency] CAP 1.0 Ballot Results
>Ok gang, the results are in 
>We will be moving forward with taking CAP 1.0 to the next step in 
>the OASIS process.
>To do such, we have to complete the 10 items specified in the TC 
>Process (http://www.oasis-open.org/committees/process.php#standard). 
>These are summarized here, along with next steps.
>[NOTE: these have to be submitted to OASIS by the 15th of each 
>month, so if we want it to go in this month we need to act fast. 
>Otherwise, it will have to wait until next month.]
>1. The spec document in an OASIS template: Art circulated this 
>a few days ago, so that should be set.
>2. Clear English-language Summary: should be able to pull out of the 
>spec document.
>3. Statement regarding relationships to similar work of other OASIS 
>TCs: this is something we need to do. Rex, you forwarded some 
>thoughts on a couple of WS-* standards. Can you pull something 
>together to describe the relationship CAP has to them? Also, is any 
>of the group aware of any others?
>4. Certification by at least three OASIS member organizations: we 
>need to get 3 member implementers to certify this. I am checking 
>with Karl at OASIS to make sure it is "3 members" and not "3 
>organizations" as well.
>5. Comments/issues/resolution: we have that in our spreadsheet.
>6. An account of and results of the voting to approve the approve 
>the specification as a Committee Draft: this is actually the next 
>thing we need to do, now that the edits are in and we have formally 
>decided to move forward. We need to vote again on 1.0 (post-edits) 
>to make it an official Committee Draft.
>7. Pointer to votes and comments received in any earlier attempts to 
>standardize substantially the same specification, together with the 
>originating TC's response to each comment: I can handle this.
>8. A pointer to the publicly visible comments archive for the 
>originating TC: Walid, I may need some of you help here since some 
>of these comments came from the Incident.com list.
>9. A statement from the chair of the TC certifying that all members 
>of the TC have been provided with a copy of the OASIS IPR Policy: 
>will send shortly.
>10. Pointer to any minority reports: this is what Rex was talking 
>about in his email 
>and again on the last call. We would include a link to the 
>additional details provided on the ballot, as well as posted to the 
>email list.
>And that should be it!

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