[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: CAP-AU Motions to be proposed at EM-TC call on July 30, 2013 [SEC=UNCLASSIFIED]
|
UNCLASSIFIED EM-TC, In accordance with TC ADMIN’s advice shown in the email trail below, I will be seeking to put the following two CAP-AU motions to the TC for a vote at the July 30, 2013 meeting: Motion 1: I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP)
v1.2 Australia (AU) Profile Version 1.0 Committee Specification Draft 03 contained in
https://www.oasis-open.org/apps/org/workgroup/emergency/document.php?document_id=50060 as a Committee Specification.
Motion 2: I move that the TC affirm that changes have been made since the last public review, that the changes made are documented in
https://www.oasis-open.org/apps/org/workgroup/emergency/document.php?document_id=50059 and that the TC judges these changes to be Non-Material in accordance with the definition in the OASIS TC Process (http://www.oasis-open.org/policies-guidelines/tc-process#dNonmaterialChange). Information related to Motion 1: The TC already voted unanimously on the redlined CAP-AU document during the July 16, 2013 meeting. The redlined document was used as the basis of the Change Log document being
voted on in Motion 1. The only changes from the redline document are configuration changes recommended by Chet Ensign.
I would appreciate Member support to AGREE to both these motions so that I can then progress the public release of the next revision to the CAP-AU Profile once the CSD03 is released by TC ADMIN. Regards, Greg Trott
CAP-AU Custodian for the Australian Government standard for Common Alerting Protocol
Australian Government Attorney-General's Department From: emergency@lists.oasis-open.org
[mailto:emergency@lists.oasis-open.org] On Behalf Of Trott, Gregory UNCLASSIFIED EM-TC, Following the vote that was conducted at EM-TC call on July 16, 2013, regarding the acceptability of the CAP-AU redlined document (see:
https://www.oasis-open.org/apps/org/workgroup/emergency/email/archives/201307/msg00008.html), I contacted Chet Ensign at TC ADMIN to clarify the outstanding configuration and release process questions. Chet clarified all questions raised and how the final configuration changes will be incorporated into the document.
Chet also confirmed the next steps in the release process required by TC ADMIN are as follows: 1) Change the stage for the current draft from "Committee Specification 01" to "Committee Specification Draft 03" and save it with a filename like edxl-cap1.2-au-v1.1-cs01-change-log.doc.
Chet clarified that the current practice is that when the TC wants to approve a Committee Spec Draft that has had changes since its last public review as a Committee Specification, the TC has to provide some kind of log of what was changed
so that others can decide if they agree. The easiest way to do that is to simply supply a red-lined version of the draft along with the final working draft so that reviewers can see, in-line, the changes made.
I was unable to upload the document to Kavi due to an apparent firewall / file block issue, so the file edxl-cap1.2-au-v1.1-cs01-change-log.doc is
attached to this email. 2) Then accept all the changes, purge all the comments and save it as edxl-cap1.2-au-v1.1-csd03.doc.
Chet clarified that since the evolution of a document is Working Draft -> Committee Spec Draft -> Committee Spec Public Review Draft -> Committee Specification (and then on to OASIS Standard), we iterate through them as numbered stages.
So the previous Committee Spec Draft and Public Review Draft for CAP-AU was 02, so the next one is ticked up to 03. Since this will be an approval of a draft with Non-Material Changes, there won't be any Public Review Draft so only the CSD will be created.
I was able to upload the file edxl-cap1.2-au-v1.1-csd03.doc to Kavi - see:
3) Load both documents to the TC's document repository. 4) the TC will then need to approve a motion requesting that TC ADMIN start a Special Majority Vote to approve the document with Non-Material Changes as a Committee Specification.
Chet suggested the motion can be as follows: I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) v1.2 Australia (AU) Profile Version 1.0 Committee Specification
Draft 03 contained in <publicly visible URL for the csd03 draft in Kavi> as a Committee Specification. I further move that the TC affirm that changes have been made since the last public review, that the changes made are documented in <publicly visible URL
to the -change-log version of the draft in Kavi> and that the TC judges these changes to be Non-Material in accordance with the definition in the OASIS TC Process (http://www.oasis-open.org/policies-guidelines/tc-process#dNonmaterialChange). 5) Once EM-TC has that motion "approved" in the meeting minutes, enter a ticket to TC ADMIN to request the Special Majority Vote at
https://www.oasis-open.org/resources/tc-admin-requests/committee-specification-ballot-request
6) TC ADMIN will then start the Special Majority Vote as soon as possible. That will run for 7 days. If there are no objections from anyone outside to the changes being Non-Material, then on closure of the ballot and its passing of course,
TC ADMIN will publish both the CSD03 version and the CS02 versions of the document and announce them.
Regards, Greg Trott
CAP-AU Custodian for the Australian Government standard for Common Alerting Protocol
Australian Government Attorney-General's Department Download the CAP-AU-STD from
www.em.gov.au/CapAuStd
If you have received this transmission in error please notify us immediately by return e-mail and delete all copies. If this e-mail or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the e-mail or attachments. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]