[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [tosca] Starter Document for Topology and Orchestration Specification for Cloud Applications (TOSCA) Primer Version 1.0
|
Paul, We already requested this template several weeks ago and received the necessary starter document (1). We will use the first document that we received. Please remove this
document, if possible, to avoid confusion. Otherwise, we’ll just ignore it. Thanks for your help and fast response, however.
Best, Paul
From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org]
On Behalf Of Paul Knight Per the TC's submission requests [1], please find the attached starter document for: Topology and Orchestration Specification for Cloud Applications (TOSCA) Primer Version 1.0 WP-abbrev: tosca-primer We expect this Work Product to be published at: 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: similar to previous request: https://tools.oasis-open.org/issues/browse/TCADMIN-1038; delivered to TC on 10 September 2012 in email: https://lists.oasis-open.org/archives/tosca/201209/msg00016.html [2] Developing Committee Specifications and Notes Starting a Working Draft [3] SVN Version control, via Tools [4] OASIS Naming Directives [5] Approval of a WD as a CD (CSD or CND) [6] TC Administration Requests Page, see Committee Specification Draft Creation / Upload Request Best wishes, Paul -- |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]