Starter Document for ebCore Agreement Update Specification Version 1.0

Members of the ebXML Core TC, 

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

ebCore Agreement Update Specification Version 1.0

WP-abbrev: ebcore-au

We expect this Work Product to be published at:

http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/csd01/ebcore-au-v1.0-csd01.odt

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 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-2134

[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 regards, 

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Attachment:
ebcore-au-v1.0-wd01.odt

Description: application/vnd.oasis.opendocument.text