Re: [odata] Starter Document for OData Extension for JSON Data Version 1.0

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

Thanks, Ram.

It is fine (and almost expected) for the TC to add or change the information in the document templates, such as  names of editors, abstract text, list of related work (if any), etc. 

The only areas in the header which should not be modified are the "Status" section and the copyright information... and even these will be modified by TC Administration during the publication of Committee Specification Drafts, after the TC approves a Working Draft for publication.

I expect to complete (and send to the TC mailing list) the nine or so remaining Working Draft requests tomorrow.

Best regards,

Paul

On Thu, Aug 2, 2012 at 6:39 PM, Ram Jeyaraman (MS OPEN TECH) <Ram.Jeyaraman@microsoft.com> wrote:

Attached is a minor revision to the spec template (for OData Extension to correct the editor name. I did not provide the correct editor name to Paul (copied) earlier.

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Paul Knight
Sent: Thursday, August 02, 2012 11:48 AM
To: odata@lists.oasis-open.org
Subject: [odata] Starter Document for OData Extension for JSON Data Version 1.0

 

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

OData Extension for JSON Data Version 1.0

WP-abbrev: odata-json-ext

 

We expect this Work Product to be published at:

http://docs.oasis-open.org/odata/odata-json-ext/v1.0/csd01/odata-json-ext-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-1005

[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