RE: AI 0130-02 - OASIS Profiles SC Meeting - 2012-01-30 [SEC=UNCLASSIFIE

UNCLASSIFIED

Re: Action Item 0130-02 from Jan 30^th meeting: to review the <geocode> Notes and see whether the ambiguities and confusion in the existing 8 Notes could be reduced.

I propose to replace the existing 8 notes with the following 5 notes, which presents a more logical flow of notes and reduces the confusion by removing anything not associated with the <geocode> sub-element:

1) <geocode> SHOULD be used as the backup method to define alert areas whenever the consumer system has no ability to interpret the more accurate geospatial information stated in <polygon> or <circle> sub-elements. Multiple <geocode> sub-elements MAY be used as necessary to fully cover the target area for the alert message.

2) The RECOMMENDED Location Reference source for Australia is the Geo-coded National Address File (G-NAF), maintained by PSMA Australia on behalf of the members of the Intergovernmental Committee on Surveying & Mapping (ICSM). G-NAF covers locations and addresses within the complete national geography of Australia. The latest version of G-NAF can be sourced from: http://www.psma.com.au/products/gnaf.html

3) Location information from the following secondary sources would also be considered suitable to specify if warranted by the hazard situation:

a) ISO3166-2 when the area to be covered by the message includes a whole State region (refer: http://www.iso.org/iso/country_codes.htm);

b) Gazetteer of Australia available from Geoscience Australia (refer: http://www.ga.gov.au/place-name/ ; and

c) Postcodes with four (4) decimal characters and no space between characters(refer: http://www.psma.com.au/products/postcodeboundaries.html).

4) A <geocode> consisting of the ISO3166-2 designator for the continent of Australia (i.e. AU) SHALL be used to indicate a message intended for the entire continent of Australia and its Territories.

5) Messages MAY include <geocode>s from different Location Reference sources in order to provide backward compatibility and to ease transition between list updates.

These changes would require the <geocode> examples to be revised as follows:

1) Revise sub-heading “Example B (for Note 6.a)” to Example B (for Note 3.a):

2) Revise sub-heading “Example C (for Note 6.b)” to Example C (for Note 3.b):

3) Revise sub-heading “Example D (for Note 6.c)” to Example D (for Note 3.c):

Greg Trott

CAP-AU Project Manager

Australian Government Attorney-General's Department

From: emergency-cap-profiles@lists.oasis-open.org [mailto:emergency-cap-profiles@lists.oasis-open.org] On Behalf Of Gary Timm
Sent: Wednesday, 1 February 2012 1:01 AM
To: emergency-cap-profiles@lists.oasis-open.org
Subject: [emergency-cap-profiles] Groups - OASIS Profiles SC Meeting Notes - 2012-01-30 - DRAFT uploaded

Submitter's message
The CAP Profiles SC decided to forego an EMTC vote on 1/31 on our CAP-AU Profile draft as we have received additional comments we are considering. Thus, the next CAP Profiles meeting to continue this process will be on 2/1/2012 at 4:00PM ET.
Here are Minutes of the last meeting: OASIS Profiles SC Meeting Notes - 2012-01-30 - DRAFT
-- Gary Timm

Document Name: OASIS Profiles SC Meeting Notes - 2012-01-30 - DRAFT

Description
OASIS Profiles SC Meeting Notes - 2012-01-30 - DRAFT
Download Latest Revision
Public Download Link

Submitter: Gary Timm
Group: EM CAP Profiles SC
Folder: Meeting Notes
Date submitted: 2012-01-31 06:00:28

emergency-cap-profiles message