OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-cap-profiles message

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


Subject: RE: [emergency-cap-profiles] Groups - Action Item "Review [Revised] ALERT elements / Sub-Elements in CAP-AU Profile" added


Here are my comments on the additional changes we will discuss later today that Greg made to Section 2 and ALERT Block beyond what we discussed in last week’s meeting. (see document link at bottom of email below for his changed document)

 

Section 2 language was changed.  I think the two references to “CAPv1.2” that were eliminated need to stay in.  I actually liked the former wording better.

 

In Section 2, what is the “Reference Standard in Section 1”?

 

Greg’s question: Need to decide on terms Element, Block, or Segment.  [I usually use Block for the ALERT, INFO, RESOURCE, and AREA, and Element for anything under those levels.  However, CAPv1.2 in its tables uses the terms “alert Element and Sub-elements”, and in its aggregated table 3.1 showing everything, it uses the term “element” to describe all the elements and sub-elements.  I would vote that we use the term “element” to refer to all elements in the CAP-AU Profile.]

 

In ‘sender’ element, it says if ‘sender’ value gets changed by an aggregator, “the original message ‘identifier’ is to be added to the ‘incidents’ block”.  Do you really want to do that?  This is not in keeping with the example back in the ‘incidents’ element which shows a value representing a logical incident name.  Can/should a previous message ‘identifier’ coexist with the normal use of the ’incident’ element?

 

Greg’s question: Should all the Examples be moved to an Appendix?

 

The ‘addresses’ element no longer appears separately in the Profile, so it is presumed it now follows CAPv1.2 as written.

 

There is a lot of other added content, but it all looks ok to me, but others should take a look as well.

 

Gary

 

From: emergency-cap-profiles@lists.oasis-open.org [mailto:emergency-cap-profiles@lists.oasis-open.org] On Behalf Of Greg Trott
Sent: Thursday, October 13, 2011 1:02 AM
To: emergency-cap-profiles@lists.oasis-open.org
Subject: [emergency-cap-profiles] Groups - Action Item "Review [Revised] ALERT elements / Sub-Elements in CAP-AU Profile" added

 

Action Item Subject: Review [Revised] ALERT elements / Sub-Elements in CAP-AU Profile
Item Number: #0001


Description
REVIEW the REVISED ALERTS elements in the attached document

These elements have been updated in response to outcomes from Profiles SC telecon of Oct 12th.

Responses to this action item should be posted on Kavi PRIOR TO next Profiles SC call scheduled on Oct 19th to facilitate discussion.

Owner: Mr. Greg Trott
Status: Open
Priority: High
Due Date: 20 Oct 2011


Comments
Mr. Greg Trott 2011-10-13 05:01 GMT
Please focus your reviews on the following issues:
1) Is the content appropriate for the Section / Element and each Sub-Element?
2) Are the Notes appropriate or are more Notes required?
3) Are the proposed examples correct in terms of content and syntax?
4) Is there anything else that should be added to each Sub-Element?


Referenced Items

REVISED - ALERT elements of CAP Australia Profile document (130K)

2011-10-12

Download | View Details

 



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