Re: Starter Document for Akoma Ntoso Naming Convention Version 1.0

Hi LegalDocumentML TC members,

I'm attaching an updated ZIP file that contains an HTML template which I believe will be a more accurate starting point for publishing your work on the Akoma Ntoso Naming Convention (compared to the previously delivered material).

The ZIP file contains the material in the following formats:

- OpenOffice (.odt) - the source format (which does not produce accurate HTML output)

- MS Word (.doc) - intermediate format derived from the .odt (which produces fairly accurate rendering in HTML)

- HTML format produced from the .doc format

Please feel free to contact me or the OASIS TC Administrator (Chet Ensign) with any questions about this.  We will be happy to discuss and support your document production processes.

Kind regards,

Paul

On Wed, Apr 30, 2014 at 12:40 PM, Paul Knight <> wrote:

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

Akoma Ntoso Naming Convention Version 1.0

WP-abbrev: akn-nc

I 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:

http://docs.oasis-open.org/legaldocml/akn-nc/v1.0/csd01/akn-nc-v1.0-csd01.html

The permanent "Latest version" URI will be:

http://docs.oasis-open.org/legaldocml/akn-nc/v1.0/akn-nc-v1.0.html

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:

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

[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

-- 

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