[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Starter Document for Akoma Ntoso Naming Convention Version 1.0
--Per the TC's submission request [1], please find the attached starter document for:Akoma Ntoso Naming Convention Version 1.0WP-abbrev: akn-ncI am attaching a ZIP file containing the expected format for the front pages of a ready-to-publish "Committee Specification Draft 01" (csd01). This is in Open Office (.odt) format, as well as the HTML and image file generated from the .odt file.The material in the ZIP file incorporates the expected namespace (http://docs.oasis-open.org/legaldocml/ns/akn-nc/v1.0/csd01), based on the pattern requested in [1], but modified to follow the OASIS Naming Directives [4].When the TC first votes [5] to publish this Work Product in the OASIS Library, we expect it to be published at:The permanent "Latest version" URI will be:Please let me know if anything here fails to meet your expectations.(NOTE: some of the text below may not apply to the TC's document production processes.)
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:[2] Developing Committee Specifications and NotesStarting 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 RequestBest wishes,Paul
Paul Knight - Tel: +1 781-861-1013
OASIS - Advancing open standards for the information society
Document Process Analyst
Attachment:
akn-nc-v1.0-csd01-template-update.zip
Description: Zip archive
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]