Fwd: [emergency-adopt] Starter Document for Common Alerting Protocol Version 1.2 Practices Guide Version 1.0

Hi Everyone,

    
I am forwarding this,
        minus the actual document that was attached to let you know that
        we have received the starter document and I will now begin
        working on it with Eliot Christian. I am currently expecting
        paragraphs explaining the three multi-info-blocks positions from
        Norm, Jake and Eliot and materials from Jake on Issue 29 and
        Norm on Issue 30 (though it may come from Jake if he finds
        Norm's email first).

    
Cheers,

    
Rex

    

    

      

      -------- Forwarded Message --------
      
        
          

            Subject:
            
            [emergency-adopt] Starter Document for Common Alerting
              Protocol Version 1.2 Practices Guide Version 1.0
          

          

            Date: 
            Tue, 2 Aug 2016 13:28:16 -0400
          

          

            From: 
            Chet Ensign <>
          

          

            To: 
            
          

        
      
      

      

      

        
Members of the Emergency Management Adoption TC, 

          

          

          
Per the TC's submission request [1], please find the
            attached starter document for:

          

          

          
Common Alerting Protocol Version 1.2 Practices Guide
            Version 1.0

          
WP-abbrev: CAP-v1.2-practices-guide-v1.0

          

          

          
Unless you choose to submit the draft to public review,
            we expect this Work Product to be published at:

          

          

          
http://docs.oasis-open.org/emergency-adopt/CAP-v1.2-practices-guide/v1.0/cn01/CAP-v1.2-practices-guide-v1.0-cn01.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 to the
            TC's Subversion (SVN) repository, if SVN 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].

          

          

          
When the TC votes [5] 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 [6].

          

          

          
Upon receipt of this form, the TC Administrator will QC
            and process the Work Product for official publication in the
            OASIS Library (http://docs.oasis-open.org/)
            as a Committee Draft, including addition of the requisite
            cover page metadata and other boilerplate information.

          

          

          
A quality checklist of commonly-occurring issues found in
            draft specifications is available at https://www.oasis-open.org/committees/download.php/54999/latest.
            This checklist was developed by the OASIS Technical Advisory
            Board (TAB) and is used to provide feedback to TC's when a
            document goes out for its first public review. The document
            can help spec editors and anticipate and address a number of
            routine problems. 

          

          

          

          

          
=========== References:

          
[1] https://tools.oasis-open.org/issues/browse/TCADMIN-2411

          
[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] SVN Version control, via Tools

          
    https://tools.oasis-open.org/

          
[4] OASIS Naming Directives

          
    http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html

          
[5] 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

          
[6] TC Administration Requests Page, see Committee
            Specification Draft

          
Creation / Upload Request

          
    https://www.oasis-open.org/resources/tc-admin-requests

        

        

        

        -- 

        

          

            

              

                /chet 

                ----------------

                Chet Ensign

                Director of Standards Development and TC Administration 

                OASIS: Advancing open standards for the information
                society

                http://www.oasis-open.org

                

                Primary: +1 973-996-2298

                Mobile: +1 201-341-1393