[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency-cap] Groups - cap-etl-v1.0-wd05-Rev02.docx uploaded
Still not correct… Draft 5 Rev 2… Line 22: “<element>” should be “<event> element” Line 23: “<element>” should be “<event> element” Line 27: “<element>” should be “<event> element” Line 29: “<element>” should be “<event> element” Line 178: “<event><element” should be “<event> element” Line 193: “OASIS” should be “the EMTC” (Since the above changes need fixing, we can catch this one too). Line 304: Extra space after “example” Line 406: Extra “3.0” Line 638: The yellow highlight should be removed Line 704: “as and event” should be “as an event type” Lines 807 to 818 are
still the old text from before Monday the 26th. Go get the correct text below… Appendix C is missing. Norm The correct text for Appendix B Appendix B. OASIS Event Terms
The OASIS event
code value is for use in the cap.alertInfo.eventCode.value element
Note: “OET” represents “OASIS Event Term”
The version of the OASIS Event Terms list that the OASIS event code is taken from is indicated in the cap.alertInfo.eventCode.valueName element.
Note: It is of the form "OET:m.n", where "m.n" is the major.minor version of this document.
The OASIS event
term is for use in the cap.alertInfo.event element
Note: The OASIS Event Term is supporting material for comparison purposes and for systems that have no Event term list.
The "Grouping" column is used to indicate other CAP Event terms which are related.
Note: Most often, the grouping term is a broad grouping term on the broad to narrow spectrum, where the term on the row is a more specific term on the same spectrum. The Grouping term
can lead to other related terms if the given Event term "doesn't quite fit" the situation.
The CAP Category Code(s) value is for use in the cap.alertInfo.category element
Note: The "CAP Category Code(s)" column, lists the known CAP Categories the OASIS Event term is associated, and OASIS recommends all values listed should be included in the multi-instanced
cap.alertInfo.category element in a CAP message. From: emergency-cap@lists.oasis-open.org <emergency-cap@lists.oasis-open.org>
On Behalf Of Rex Brooks Submitter's message
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]