emergency-cap — archive

Starter Document for Common Alerting Protocol Event Terms List Version 1.0

From: Rex Brooks <[email protected]>
To: [email protected]
Date: Thu, 27 Jun 2019 15:27:00 -0000

Hi Everyone, I'm forwarding the notification of the Committee Note Starter Document, which I received last week, without the actual document to ensure that we don't end up with various versions of the CN circulating during the process of drafting the first Committee Note Draft. I'm still working on the overview of the OASIS Non-Standards Track Committee Note Process, which I will, hopefully distribute via this email list a little later today in advance of tomorrow's meeting. Cheers, Rex -------- Forwarded Message -------- Subject: [emergency] Starter Document for Common Alerting Protocol Event Terms List Version 1.0 Date: Thu, 20 Jun 2019 18:20:47 -0400 From: Paul Knight <[email protected]> To: [email protected] Per the TC's submission request [1], please find the attached starter document for: Common Alerting Protocol Event Terms List Version 1.0 WP-abbrev: cap-etl When the TC first votes [6] to publish this Work Product in the OASIS Library, we expect it to be published at: https://docs.oasis-open.org/emergency/cap-etl/v1.0/cnd01/cap-etl-v1.0-cnd01.docx The permanent Latest version URI will be: https://docs.oasis-open.org/emergency/cap-etl/v1.0/cap-etl-v1.0.docx Please let me know if anything here fails to meet your expectations. Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the OASIS TC Administration How-to Guide [2]. Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Github or Subversion (SVN) repository, if it has been activated for your TC [3]. TCs are encouraged to use ZIP packaging when the WD releases contain multiple files (and directories). For each WD revision, you will need to: 1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in the document identifier within the page footer. 2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier, Working Draft ##) and in the page footer. 3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc. 4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision. 5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed URIs/namespaces [4]. 6) examine the instructions for construction of XML Namespace Identifiers (namespace URIs) and Namespace Documents [5] if your specification declares one or more XML namespaces or other namespace-related identifiers for (e.g.,) link relations, named properties, functions, dialects, faults, actions, or any named message types. All such identifiers, if HTTP-scheme, must begin with: https://docs.oasis-open.org/[tc-shortname]/ns/xxxx When the TC votes [6] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a Committee Specification Draft Creation and Upload Request accessible on the TC Administration Requests Page [7]. Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library ( https://docs.oasis-open.org/ ) as a Committee Draft, including addition of the requisite cover page metadata and other boilerplate information. =========== References: [1] https://tools.oasis-open.org/issues/browse/TCADMIN-3477 [2] Developing Committee Specifications and Notes https://www.oasis-open.org/resources/tcadmin/developing-committee-specifications-and-notes Starting a Working Draft https://www.oasis-open.org/resources/tcadmin/starting-a-working-draft [3] Github and SVN Version control, via Tools https://tools.oasis-open.org/ [4] OASIS Naming Directives http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html [5] OASIS Naming Directives - Namespace Identifiers and Namespace Documents http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#xml-namespaces [6] Approval of a WD as a CD (CSD or CND) https://www.oasis-open.org/resources/tcadmin/approving-a-committee-specification-or-note-draft https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft [7] TC Administration Requests Page, see Committee Specification Draft Creation / Upload Request https://www.oasis-open.org/resources/tc-admin-requests Best wishes, Paul -- Paul Knight ... . Document Process Analyst ... mobile: +1 781-883-1783 OASIS - Advancing open standards for the information society This email has been checked for viruses by Avast antivirus software. www.avast.com