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


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-cap message

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

Subject: RE: [emergency-cap] Tony can't attend 10-28 CAP SC meeting

Hi Yu,


Thank you for your comments.  These can be added directly to the list of comments for consideration as your company is a member of the TC.  Rather than the “perpetual” list that we have deliberated in years past and are required by process to review at each release, these should go on the list of new comments to be deliberated along with the other input from Steve, the NWS, EnvCA and others. 


I’m sorry that I will not be able to attend the call today as IAEM is taking all my cycles since Sat and through Wed.  If the meeting does not make, I am available next Mon if the SC decides to reschedule.





From: emergency-cap@lists.oasis-open.org [mailto:emergency-cap@lists.oasis-open.org] On Behalf Of Yu Chen
Sent: Monday, October 28, 2013 3:42 AM
To: Tony Mancuso
Cc: emergency-cap@lists.oasis-open.org
Subject: Re: [emergency-cap] Tony can't attend 10-28 CAP SC meeting


I will call in for the meeting on Monday.


Since I noticed some discussions regarding perpetual CAP issues for CAP 2.0, I'd like to raise a few more items related data I've seen in more countries. 


1. Multiple areas. 

An event can have multiple types of areas, for example an earthquake may have an incident location plus shaking locations. A fire would have start location, burn area, and warning areas. A tsunami has multiple arrival segments, and within each segment there may be breakpoints with different wave heights and arrival times. Even though CAP is supposed to only have warning areas, I think it may be useful to allow for multiple areas and have some standard labeling.


2. Formatting. 

This is the question of HTML in the descriptions. It's strongly discouraged but not listed anywhere. However, there's no getting around the fact that if CAP is to be used dissemination over the internet, it'd be nice to better support HTML formatting in <description> and <instruction>


3. Languages. 

I'd like better documentation on parameters names across languages. Many countries have multiple official languages. Should parameter names be the same across languages? Or be language dependent?


On Sun, Oct 27, 2013 at 7:19 PM, Tony Mancuso <amancuso@google.com> wrote:

I have a schedule conflict and I won't be able to attend and chair/take minutes at the Monday 10-28 CAP SC meeting. I hope another chair can take over. Yu Chen may attend to raise new issues for consideration by the group.

Tony Mancuso
co-chair CAP SC




Yu Chen | Partner Technology Manager | Partner Solutions, gTech | +1 (650) 214-4851 


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