EM CAP SC

Hi all, I agreed to look into both creating a sample tsunami CAP message and locating a foreign CAP message. I located the attached 20160302223139.xml from InaTEWS, the Indonesia Tsunami Early Warning System, which might serve as both. It has 4 info blocks, one for tsunami warning and another for tsunami advisory, and each is repeated in Indonesian and English. I'm not sure if having more than 1 plus repeats in other languages is ideal, but please check it out. Also, here is a link to the National Tsunami Warning Center's CAP initiative, with sample CAP messages: http://wcatwc.arh.noaa.gov/?page=cap This also can have multiple info blocks in the same language. Both have their own profiles. Talk to you tomorrow, David DAVID ASKOV   PACIFIC DISASTER CENTER   808.891.7937   daskov@pdc.org

Hi all, I have attached the original CAP message from the provider, as well as my attempt to shorten it. - Removed two of the four info sections. I left the ones with severity=Severe and deleted the severity=Moderate. - Deleted all geocodes after the first four. - Removed the corresponding parameter tags for predictedWaveHeight and predictedArrivalTime for the geocode areas that I deleted. - Removed one of two resources - Added a comment everywhere that I deleted content. The file now 304 lines, which is still pretty long, and 20-30 lines go past 100 characters, which will probably wrap onto a new line in a document presentation. Other ideas to shorten: - Truncate the description - Remove more geocodes and corresponding parameters - just keep 2? - Remove the observation parameters - Remove other parameters (EventLocationName, ShortLocationName, etc.) We had also discussed making this more generic. The goal was not to identify the sender or at least to remove the dates, times and message identifier, since we are modifying it. The more I thought about that, I think it is better to just insert comments where we're shortening it and then leave it alone. Let's chat about this approach tomorrow and then I would like to ask them if it's ok to use this as an example. Thanks, David DAVID ASKOV   PACIFIC DISASTER CENTER   808.891.7937  daskov@pdc.org
Original Message----- From: David Askov Sent: Thursday, May 12, 2016 11:11 PM To: Jacob Westfall <jake@jpw.biz>; emergency-cap@lists.oasis-open.org Subject: Tsunami and foreign CAP Hi all, I agreed to look into both creating a sample tsunami CAP message and locating a foreign CAP message. I located the attached 20160302223139.xml from InaTEWS, the Indonesia Tsunami Early Warning System, which might serve as both. It has 4 info blocks, one for tsunami warning and another for tsunami advisory, and each is repeated in Indonesian and English. I'm not sure if having more than 1 plus repeats in other languages is ideal, but please check it out. Also, here is a link to the National Tsunami Warning Center's CAP initiative, with sample CAP messages: http://wcatwc.arh.noaa.gov/?page=cap This also can have multiple info blocks in the same language. Both have their own profiles. Talk to you tomorrow, David DAVID ASKOV   PACIFIC DISASTER CENTER   808.891.7937   daskov@pdc.org

Resending this to bubble it up to the top of everyone's email for our telecon on Friday.
Original Message----- From: David Askov Sent: Thursday, June 09, 2016 17:52 To: emergency-cap@lists.oasis-open.org Subject: FW: Tsunami and foreign CAP Hi all, I have attached the original CAP message from the provider, as well as my attempt to shorten it. - Removed two of the four info sections. I left the ones with severity=Severe and deleted the severity=Moderate. - Deleted all geocodes after the first four. - Removed the corresponding parameter tags for predictedWaveHeight and predictedArrivalTime for the geocode areas that I deleted. - Removed one of two resources - Added a comment everywhere that I deleted content. The file now 304 lines, which is still pretty long, and 20-30 lines go past 100 characters, which will probably wrap onto a new line in a document presentation. Other ideas to shorten: - Truncate the description - Remove more geocodes and corresponding parameters - just keep 2? - Remove the observation parameters - Remove other parameters (EventLocationName, ShortLocationName, etc.) We had also discussed making this more generic. The goal was not to identify the sender or at least to remove the dates, times and message identifier, since we are modifying it. The more I thought about that, I think it is better to just insert comments where we're shortening it and then leave it alone. Let's chat about this approach tomorrow and then I would like to ask them if it's ok to use this as an example. Thanks, David DAVID ASKOV   PACIFIC DISASTER CENTER   808.891.7937  daskov@pdc.org
Original Message----- From: David Askov Sent: Thursday, May 12, 2016 11:11 PM To: Jacob Westfall <jake@jpw.biz>; emergency-cap@lists.oasis-open.org Subject: Tsunami and foreign CAP Hi all, I agreed to look into both creating a sample tsunami CAP message and locating a foreign CAP message. I located the attached 20160302223139.xml from InaTEWS, the Indonesia Tsunami Early Warning System, which might serve as both. It has 4 info blocks, one for tsunami warning and another for tsunami advisory, and each is repeated in Indonesian and English. I'm not sure if having more than 1 plus repeats in other languages is ideal, but please check it out. Also, here is a link to the National Tsunami Warning Center's CAP initiative, with sample CAP messages: http://wcatwc.arh.noaa.gov/?page=cap This also can have multiple info blocks in the same language. Both have their own profiles. Talk to you tomorrow, David DAVID ASKOV   PACIFIC DISASTER CENTER   808.891.7937   daskov@pdc.org