Template for The DocBook Publishers Schema Version 1.1

[Paul Knight <paul.knight@oasis-open.org>]

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

The DocBook Publishers Schema Version 1.1

WP-abbrev: publishers

Since the TC is using the DocBook publishing system, we are providing current examples of the template in HTML, PDF and the source MS-Word (DOC) formats.  All three formats are included in the attached ZIP file.

We expect you will use the attached templates to update your existing DocBook format, as exemplified by the previous version of this Work Product [2].  We will be happy to work with you to proofread the results for conformance with current OASIS styles.

We expect this Work Product to be published at:

http://docs.oasis-open.org/docbook/publishers/v1.1/csd01/publishers-v1.1-csd01.html

Please let me know if anything here fails to meet your expectations.

For each later revision, you will need to:

1) increment the Committee Specification Draft revision (number) from 01 to 02, 03, 04 etc., as successive Committee Specification Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier ( Committee Specification Draft ##) and in the document identifier within the page footer.

2) supply the relevant publication/release/upload date for each successive Committee Specification 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, Committee Specification 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 CSD 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 [3].

When the TC votes [4] to approve a Working Draft as a Committee Specification Draft, the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests Page [5].  

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.

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

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

[2] The DocBook Publishers Schema. OASIS Committee Specification 01.

     http://docs.oasis-open.org/docbook/specs/publishers-1.0-spec-cs-01.html

[3] OASIS Naming Directives

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

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

[5] 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: publishers-v1.1-csd01.zip
Description: Zip archive