RE: [emergency-comment] cap 1.2 IPAWS profile comments

[Elysa Jones <ejones@warningsystems.com>]

Thanks Gary,  I knew this was properly covered but just couldn't 
recall the resolution when Harold asked the question today.  I'm sure 
discussions about it are found in the detailed meeting notes that 
were kept and also on line.  Elysa

At 02:29 PM 8/11/2009, Gary Ham wrote:

>If you look at the mask for datetime in CAP1.2 the time zone is required.
>Time zone is identified by the offset from GMT.  This is far more accurate
>than any string identified time zone designation and much easier to
>calculate from.  Time Zone is there -- and in a better way than as a
>separate field.
>
>Gary A. Ham
>http://grandpaham.com
>703-899-6241
>Grandpa can do IT!
>
>-----Original Message-----
>From: Harold Price [mailto:hprice@sagealertingsystems.com]
>Sent: Tuesday, August 11, 2009 2:36 PM
>To: emergency-comment@lists.oasis-open.org
>Subject: [emergency-comment] cap 1.2 IPAWS profile comments
>
>1) EAS requires a UTC start time in its protocol.  The dateTime
>element used by CAP has an optional timezone field, the timezone
>isn't required.  A dateTime without a timezone can't be converted
>into an EAS UTC time unless the CAP to EAS converter knows what the
>local time of the originator of the message was.
>
>There is no method within CAP to provide that additional data.
>
>Early recommendations from the EAS vendor community asked that the
>optional timezone be made mandatory in CAP, or at least in the EAS
>profile, otherwise undetectable duplicate messages will result in the
>EAS domain.  The CAP 1.2 IPAWS profile update removed the discussion
>of a mandatory timezone, and I don't see anywhere else where it was
>added.  The timezone, or some way to determine the timezone of the
>originator, is required for CAP to EAS conversion.  This concept
>needs to appear in the document set somewhere.
>
>2)  In the discussion of geocode, "000000" is defined to be all US
>territory.  It should be noted that some legacy EAS equipment does
>not recognize 000000, as it was not in the original FCC referenced
>FIPS document, and the use of 000000 could result in a rejected message.
>
>Regards,
>Harold Price
>Sage Alerting Systems
>
>
>--
>This publicly archived list offers a means to provide input to the
>OASIS Emergency Management TC.
>
>In order to verify user consent to the Feedback License terms and
>to minimize spam in the list archive, subscription is required
>before posting.
>
>Subscribe: emergency-comment-subscribe@lists.oasis-open.org
>Unsubscribe: emergency-comment-unsubscribe@lists.oasis-open.org
>List help: emergency-comment-help@lists.oasis-open.org
>List archive: http://lists.oasis-open.org/archives/emergency-comment/
>Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
>List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>Committee:
>http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency
>
>
>--
>This publicly archived list offers a means to provide input to the
>OASIS Emergency Management TC.
>
>In order to verify user consent to the Feedback License terms and
>to minimize spam in the list archive, subscription is required
>before posting.
>
>Subscribe: emergency-comment-subscribe@lists.oasis-open.org
>Unsubscribe: emergency-comment-unsubscribe@lists.oasis-open.org
>List help: emergency-comment-help@lists.oasis-open.org
>List archive: http://lists.oasis-open.org/archives/emergency-comment/
>Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
>List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>Committee: 
>http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency