RE: [tgf] Starter Document for TGF Pattern Language: Patterns for CAMSS Version 1.0

Thanks Paul.

I’ll take it from here, as agreed on the TC call this week

 

Peter

 

From:  [mailto:]
On Behalf Of Paul Knight

Sent: Friday, 03 August, 2012 12:05

To: 

Subject: [tgf] Starter Document for TGF Pattern Language: Patterns for CAMSS Version 1.0

 

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

TGF Pattern Language: Patterns for CAMSS Version 1.0

WP-abbrev: TGF-PL-CAMSS

 

Please note: This is a slight modification of the TC's requested title (TGF Pattern Language - Patterns for CAMSS).  The
 OASIS Naming Directives [7] state that OASIS Work Product titles should avoid the use of the "hyphen" character.

 

We expect this Work Product to be published at:

http://docs.oasis-open.org/tgf/TGF-PL-CAMSS/v1.0/csd01/TGF-PL-CAMSS-v1.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-1018

[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

[7] http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#workProductName

 

Best wishes,

Paul

 

-- 

Paul Knight  - Tel: +1 781-861-1013

OASIS - Advancing open standards for the information society

Document Process Analyst