Re: [tosca] Starter Document for Topology and Orchestration Specification for Cloud Applications Version 2.0

[Doug Davis <dug@us.ibm.com>]

tosca-chairs,
  during the call on Thursday we talked a lot of v2 activities and perhaps I should have given the terminology more consideration (or I apologize if this was discussed during the call and I missed it) but I was interpreting the talks to really be about v.next - meaning "whatever we do next".  Whether that turns out to be a full v2, a v1.x or just an errata is yet to be seen.  So, I was a bit surprised to see these "starter" documents get created with the assumption that we're immediately going to work on a v2.  I would prefer that we didn't make this assumption and waited until the TC made changes to our documents and _then_ we decided how best to release those - ie. as an errata, v1.x or v2.  I think its too soon to jump to the v2 conclusion.

thanks
-Doug
________________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.

Paul Knight ---04/05/2013 03:32:45 PM---Per the TC's submission request [1], please find the attached starter document for:

From: Paul Knight <paul.knight@oasis-open.org>
To: tosca@lists.oasis-open.org,
Date: 04/05/2013 03:32 PM
Subject: [tosca] Starter Document for Topology and Orchestration Specification for Cloud Applications Version 2.0
Sent by: <tosca@lists.oasis-open.org>

---

Per the TC's submission request [1], please find the attached starter document for: 
Topology and Orchestration Specification for Cloud Applications Version 2.0
WP-abbrev: TOSCA

We expect this Work Product to be published at:
http://docs.oasis-open.org/tosca/TOSCA/v2.0/csd01/TOSCA-v2.0-csd01.doc

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 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.

=========== References:
[1] https://tools.oasis-open.org/issues/browse/TCADMIN-1237
[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

Best wishes,
Paul
-- 
Paul Knight  - Tel: +1 781-861-1013
OASIS - Advancing open standards for the information society
Document Process Analyst
[attachment "TOSCA-v2.0-wd01.doc" deleted by Doug Davis/Raleigh/IBM] 
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php