Table 1: CAP v1.2 Australia Profile Specification CAP Element Profile Specification Profile Specification Normative Non-Normative Elements and Sub-elements “alert” REQUIRED Note: Technical alert The <alert> element is not specific to any included <info> element, but is to serve as a general reference to all associated <info> elements and their content. identifier REQUIRED Notes: Technical Example: 1) be assigned by the message producer. CAP v1.2 Standard 2) For messages that are to be shared between organisations, the <identifier> SHOULD enable the message to be associated with a specific hazard event and originating organisation. 3) A national database of hazard event identifiers does not yet exist in Australia sender REQUIRED Notes: Technical Example (note 3): 1) email address in the format example@domain that identifies When the Duty Operations Officer at the Fire the agency that assembled the message, or another agency and Emergency Services Authority (FESA) of that originated the message. Western Australia (WA) receives hazard alerting information from the WA Police (WAPOL) in non-CAP format (i.e. it was 2) Use of Third Level Domain (example@bom.gov.au) or received via a telephone call), the FESA Duty Fourth Level Domain (example@ses.sa.gov.au) names as the Operations Officer reformats the data into CAP <sender> value, are considered acceptable methods to create format using that State’s alerting system, then uniqueness. redistributes the message on behalf of WAPOL. 3) If an alert message created by another agency is being
Table 1: CAP v1.2 Australia Profile Specification CAP Element Profile Specification Normative Profile Specification Non-Normative “alert” Elements and Sub-elements alert REQUIRED Note: The <alert> element is not specific to any included <info> element, but is to serve as a general reference to all associated <info> elements and their content. Technical identifier REQUIRED Notes: 1) be assigned by the message producer. 2) For messages that are to be shared between organisations, the <identifier> SHOULD enable the message to be associated with a specific hazard event and originating organisation. 3) A national database of hazard event identifiers does not yet exist in Australia Technical Example: CAP v1.2 Standard sender REQUIRED Notes: 1) email address in the format example@domain that identifies the agency that assembled the message, or another agency that originated the message. 2) Use of Third Level Domain (example@bom.gov.au) or Fourth Level Domain (example@ses.sa.gov.au) names as the <sender> value, are considered acceptable methods to create uniqueness. 3) If an alert message created by another agency is being Technical Example (note 3): When the Duty Operations Officer at the Fire and Emergency Services Authority (FESA) of Western Australia (WA) receives hazard alerting information from the WA Police (WAPOL) in non-CAP format (i.e. it was received via a telephone call), the FESA Duty Operations Officer reformats the data into CAP format using that State’s alerting system, then redistributes the message on behalf of WAPOL.
edxl-cap-v1.2-au-profile-v1%200-wd05_redline.docx