UNCLASSIFIED Profiles SC, After reviewing the NWS inputs from Bob Bunge and Mike Gerber regarding the <effective>, <onset>, <expires> topics, I can see that CAP-AU should use: a) <onset> to designate the expected time for the beginning of the event; b) <effective> to be explicit that the information in the message is effective when it is sent, so the <effective> and <sent> will probably be the same value; and c) <expires> to designate when the information in the message should no longer be used. Therefore … I believe the CAP-AU entries for <expires> remain valid so no changes are required for that sub-element and I wish that sub-element USE to remain as REQUIRED. I see no need to insert anything for <onset> because there is no deviation from the use stated in OASIS CAPv1.2. I agree that <effective> SHOULD be interpreted to mean that the information in the message is effective when it is sent, which does not deviate from what OASIS CAP v1.2 intended, so I propose the following changes to the CAP-AU Profile: 1) Change the TYPE for <effective> to OPTIONAL. 2) Change <effective> Note 1) to the following: 1) Messages are considered to be effective when sent, so if the <effective> sub-element is used it SHOULD be the same value as <sent>. 3) Remove <effective> Note 4) as it does not add any value to the document. 4) Change <effective> Example A to include a <sent> line between <alert> and <info> lines as per following (which explicitly highlights that <effective> is to be the same as <sent>) : <alert> … <sent>2011-05-13T07:00:00+10:00</sent> … <info> … <effective>2011-05-13T07:00:00+10:00 </effective> 5) Change <effective> Example B to include a <sent> line between <alert> and <info> lines as per following: <alert> … <sent>2011-05-12T21:00:00-00:00</sent> … <info> … <effective>2011-05-12T21:00:00-00:00 </effective> Greg Trott CAP-AU Project Manager Australian Government Attorney-General's Department From:
emergency@lists.oasis-open.org [mailto:
emergency@lists.oasis-open.org] On Behalf Of Robert Bunge Sent: Wednesday, 1 February 2012 5:44 AM To:
emergency@lists.oasis-open.org Subject: [emergency] NOAA/NWS interpretation of < effective> and <expires> All, The NWS interpretation of <effective> and <expires> as documented in the NWS CAP wiki (
https://wiki.citizen.apps.gov/nws_developers/index.php/Category:Common_Alerting_Protocol ) may not be consistent with the Australian profile. We noticed there is no <onset> tag in the AU profile. However, NWS is making every effort to differentiate between the effective time (<effective>) of the information in the alert message, the expected time of the beginning of the event (<onset>), the time at which the information in the message should no longer be used (<expires>), and the time at which the hazard conditions of the subject event are no longer expected (optional parameter we've added called <eventEndingTime> and wish to propose as standard for CAP v2.0). Mike Gerber will be speaking more about this at the Wednesday meeting. Bob If you have received this transmission in error please notify us immediately by return e-mail and delete all copies. If this e-mail or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the e-mail or attachments.