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] CAP issues summary



Thanks David for reaching out!  I understand there has been an absence in meetings due to vacations and work projects this summer.  Jacob shared with me recently that he will break away from his tasks to reconvene the group soon.  We have only one more EM-TC meeting before the CAP workshop.  I know the SC was close to having something to bring to the TC for consideration.  All, stay tuned to the list as the end of summer should bring us back together.




Elysa Jones, Chair OASIS

Emergency Management Technical Committee

Emergency Interoperability Member Section




From: emergency-cap@lists.oasis-open.org [mailto:emergency-cap@lists.oasis-open.org] On Behalf Of David Askov
Sent: Thursday, August 27, 2015 4:09 PM
To: Jacob Westfall <jake@jpw.biz>; emergency-cap@lists.oasis-open.org
Subject: RE: [emergency-cap] CAP issues summary


Hi everyone,


I was pretty out of the loop over June and July with work travel and vacation. I haven’t seen any CAP-SC emails or calendar invites in quite a while, so I was wondering if we have plans to resume meeting at some point.


Thanks, David



Geospatial Information Services Advisor

Pacific Disaster Center

808.891.7937  |  daskov@pdc.org



-----Original Message-----
From: emergency-cap@lists.oasis-open.org [mailto:emergency-cap@lists.oasis-open.org] On Behalf Of Jacob Westfall
Sent: Friday, June 05, 2015 08:33
To: emergency-cap@lists.oasis-open.org
Subject: [emergency-cap] CAP issues summary



                As discussed on the CAP SC call today, here are my thoughts on how to address the issues now that they have all been reviewed.


- Errata -

The following issues would be incorporated into the existing CAP 1.2 Errata draft and this draft would be advanced to the TC.


1, 2, 22, 27, 31



- Practices Guide -

The following issues would be incorporated into an update to the CAP Practices Guide and this recommendation would be advanced to the TC.  Guidance would be created for each issue as part of passing this work over to the Adoption TC and volunteers to spearhead this work would be sought.


1, 2, 17, 25, 27, 28, 29, 31



- Implementers Workshop -

The following issues would be incorporated into a discussion document for the CAP Implementers Workshop.  A short summary of each issue would be provided, along with the link to the JIRA issue for details.  The document would request that implementers provide feedback using some other mechanism than JIRA though, perhaps like the recent Survey, to make tracking easier.  The SC would create this document and advance it to the TC.


8, 16, 17, 25, 29, 30, 34



- Next Version -

There are a number of issues that have been identified as applicable to the next version of CAP.  I'd like to propose a ballot be held to decide if a 1.X or 2.X is the appropriate path forward for these issues.  The results of this ballot would be forwarded to the TC.




Jacob Westfall <jake@jpw.biz>



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:



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