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


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-msg message

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

Subject: Re: [emergency-msg] CAP 1.2 items

Hi Jacob,

I think this should be on our agenda tomorrow, along with CAP-EAS. 
The fact is, while our membership has expanded a bit recently, taking 
on both of these tasks, which have short-term priority, need 
dedicated person-hours. And this applies not just the person-hours 
for drafting the language, but, just as importantly, to prompt, 
thoughtful review and discussion. So we need to field another team to 
take on this work, if that's what the TC decides. That means we need 
folks to show up regularly for meetings and pitch in, such as 
volunteering to take meeting notes so that the chair duties are not 
so concentrated.

What we did as we pushed through EDXL-RM with two co-chairs was often 
for one chair to do the chair duties while the other took notes. I've 
also participated in TCs and SCs where note-taking rotated through 
the membership on an informal basis, but the work has been spread out 
such that one person did not shoulder the majority of the work. This 
applies to the TC, too. If I wasn't taking on these roles for a 
couple of SCs, I'd volunteer, but we can only do so much as 
individuals before our performance degrades from overuse.

So, we need enough members committed to the whole process if we are 
to take it on in the near term as you indicate is needed.


At 3:32 PM -0400 9/28/08, Jacob Westfall wrote:
>	I'm following up on my comments regarding the need for a CAP 
>1.2 during the last teleconference.  Hopefully everyone has had a 
>chance to review the comments list that was very well summarized.
>Its been 3 years since CAP 1.1 was released and there are now 
>efforts underway to introduce national systems (IPAWS in US, NPAS in 
>Canada) that use 1.1  However I have run into some minor problems 
>with 1.1 and I have also heard from others about similar issues. 
>All indications I have seen say that CAP 2.0 could take some time to 
>produce and could be non-backward compatible.  This will mean that 
>with national systems based on 1.1 and a reluctance to switch to 2.0 
>for some time after implementation, 1.1 will remain in wide-spread 
>use for quite some time.  I'm asking that the committee deal with 
>some immediate problems with 1.1, addressed with a 1.2 release in 6 
>months that is backward compatible, so that these national systems 
>could be built and/or transition to 1.2 easily and avoid these 
>I have summarized the comments that I believe can be quickly 
>addressed to create CAP 1.2, others could be left to a future 2.0 
>Major Issues
>1. responseTypes of Avoid and AllClear
>2. clarify format for incidents element
>3. prevent null values for required elements
>4. Update/Cancel examples
>Minor Issues
>5. language element clarification
>6. resource element description update
>7. code element editorial fix
>8. event element editorial fix
>9. references element clarification
>10. polygon and circle element clarifications
>11. multi-lingual examples
>12. event element size limit
>13. instruction element size limit
>Optional additions that could enhance interop and provide 
>significant capabilities
>1. mime-type for CAP
>2. suggested index feed format
>3. geo resources
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  Follow this link to all your TCs in OASIS at:

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]