CAP 1.2 Vote for CS and OS ??

[Elysa Jones <ejones@warningsystems.com>]

Friends,

As you probably know there is a ballot open now for EM-TC members to 
vote for the CAP 1.2 Committee Specification and to ask OASIS Staff 
to begin the OASIS-wide vote to be held to promote this work to an 
OASIS Standard.  These are two separate ballots open now on our site.

As you may also know, Gary Ham ran into some problems with digital 
signatures and their use in OPEN using JAXB and the Oracle 10G SOA 
Suite.  There have been discussion on the list in the past few days 
about the issue.  Gary has stated the problem he (and Neil) has seen 
for which he has found an available work around.  Don McGary and 
Jocob Westfall have provided proof that the XML is correct and 
validates.  The three companies who made statements of use for CAP 
1.2 have not seen a problem with their implementations.

So, here we are needing to get a vote approved to allow CAP 1.2 to go 
forward - or not.  I wanted to give a brief history of this work and 
begin any discussion the members have for discussion on this list.

The CAP 1.2 was required for the IPAWS profile to accommodate the 
CMAS program need for an "avoid" response type.  DMOPEN is the 
program that will be used to exchange CAP messages for CMAS as well 
as EAS and HazCollect specifically for IPAWS.

Our ITU friends have expressed concern with CAP 1.2 as they have 
members that see this as a major released and not a minor.  Update 
for CAP 1.2 is not likely right away from that community.

Our members that have expressed concern over CAP 1.2 with regard to 
non-repudiation, authorization and authentication anticipate these to 
be covered in the CAP 2.0 spec that will be aligned with the DE 2.0.

Please post any concerns you have about voting on the list so we can 
discuss them openly.  If you do not have concerns and are a voting 
member of the TC, cast your vote so that we will know where we 
stand.  Votes can always be changed until the cut-off on the 15th.

Regards,

Elysa Jones, Chair
OASIS EM-TC
CTO, Warning Systems, Inc.