Re: [emergency-comment] Comments on IPAWS Profile

[Rex Brooks <rexb@starbourne.com>]

Thanks Gary,

We will add these Items to our IssuesList. As we 
go through them, the dispositions will be 
included and the most current document, i.e. 
CAPv1.1-IPAWS-Profile_IssuesList vX.X will be 
posted.

Cheers,
Rex

At 1:05 PM -0700 3/22/09, Gary Timm wrote:
>Comments to OASIS on CAP v1.1, USA IPAWS Profile v1.0, 26 February 2009
>
>
>
>From: Gary Timm, Broadcast Chair, Wisconsin EAS Committee
>
>
>
>My
>
>#
>
>Page
>
>Document Line
>
>or Table Cell
>
>Observation
>
>Recommendation / Comments
>
>1
>
>5
>
>Document Line 29
>
>Typo
>
>"Section 1.2" should be "Section 1.3"
>
>2
>
>5
>
>Document Line 39
>
>Typo?
>
>Should CMAS be "Alerting" as here, or "Alert" as 
>Page 6, Line 52? [see #3 below]
>
>3
>
>6
>
>Document Line 52
>
>Typo?
>
>Should CMAS be "Alert" as here, or "Alerting" as 
>Page 5, Line 39? [see #2 above]
>
>4
>
>9&11
>
>"sent", "status", and "resourceDesc"
>
>table cells.
>
>Clarification
>
>Why are the words "sent", "status", and "resourceDesc" bolded?
>
>Need explanation on Page 11, Document Line 173?
>
>5
>
>9
>
>"status" Non-Normative table cell
>
>Typo?
>
>Text should start with "(1)"?
>
>Also, messages" should be messages'.
>
>6
>
>9
>
>"info" Normative table cell
>
>Typo?
>
>Should "(2)" and "(3)" instead be "(1)" and "(2)"?
>
>7
>
>9
>
>"info" Non-Normative table cell
>
>Clarification
>
>In (2), what is meant by "IPAWS System 
>Partners"?  Or should it be IPAWS Exchange 
>Partners?
>
>8
>
>10
>
>"eventCode" Normative table cell
>
>Clarification
>
>In (3), is "EAS CAP Profile" the proper term?
>
>9
>
>10
>
>"eventCode" Normative table cell
>
>Clarification
>
>In (3), regarding "approved by the FCC".  How is 
>one to know which special codes are approved by 
>the FCC?  I believe ECIG just said if it is a 
>3-letter code, pass it on.
>
>10
>
>10
>
>"parameter" Normative table cell
>
>Conflict
>
>(1) says EAS-ORG required for HazCollect, but 
>Page 16, "parameter" HazCollect table cell does 
>not list EAS-ORG as required.  Doesn't NWS CRS 
>assume ORG = CIV?
>
>11
>
>10
>
>"parameter" Normative table cell
>
>Conflict
>
>There is no mention here of the EAS-STN-ID 
>parameter, but on Page 16, "parameter" EAS table 
>cell, it says EAS-STN-ID is required.
>
>12
>
>11
>
>"resourceDesc" Normative table cell
>
>Conflict
>
>This uses value of "EAS Broadcast Content". 
>Page 17, "resourceDesc" EAS table cell uses 
>values of "EAS Audio" and "EAS Streaming Audio". 
>Is this a conflict?
>
>13
>
>11
>
>"geocode" Normative table cell
>
>Typo
>
>"territoriy" should be "territory" or "territories".
>
>14
>
>12
>
>Document Line 183
>
>Typo?
>
>Should "The two" be "The three"?
>
>15
>
>15
>
>"note" EAS table cell
>
>Error
>
>The "Ignored:" Note goes with a msgType of 
>Error, not Ack.  The EAS cell should be reworded 
>to:
>
>If msgType is "Ack", should include "Accepted:" 
>or "Aired on:" plus station callsign.  If 
>msgType is "Error", should include "Error:" or 
>"Ignored:".
>
>16
>
>16
>
>"eventCode" CMAS table cell
>
>Conflict
>
>This table "recommends" that an eventCode be 
>used for CMAS, but Page 10, "eventCode" 
>Normative table cell, (1) says CMAS "MUST" 
>include an eventCode.
>
>17
>
>16
>
>"expires" CMAS table cell
>
>Typo?
>
>Should "4." and "5." be "1." and "2."?
>
>18
>
>17
>
>"mimeType" EAS table cell
>
>Typo
>
>Add superscript "TM" ("trademark") after Shoutcast and Icecast.
>
>Also, word "service" should be "type-service".
>
>19
>
>17
>
>identifier, sent, status, msgType, source, 
>scope, certainty, eventCode, expires, senderName 
>CAP Element table cells
>
>Clarification
>
>All of these are bolded.
>
>Should there be an explanation on Page 17, 
>Document Line 233 as to why they are bolded?
>
>20
>
>19
>
>Last line of Revision History table
>
>Clarification
>
>Should "PR 02" be "PR 01"?
>
>
>
>I may have additional future Comments, but this is it so far.
>
>
>
>Gary Timm
>
>Attachment converted: Macintosh HD:Comments to 
>OASIS o#14DD673.doc (WDBN/«IC») (014DD673)
>--
>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


--
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670