Thanks Robin, Much appreciated. Cheers, Rex On 2/23/11 10:13 PM, Robin Cover wrote: AANLkTinjTtcQSPk4fydvO2+
PQrb3GSdJ0yn4QV03uu2N@mail.gmail.com type= cite > Werner and TC members, Here's an updated starter document at WD level for edxl-ct , Emergency Data Exchange Language (EDXL) Reference Information Model (RIM): Common Types Version 1.0 per the submission request. Please let me know if anything fails to meet your expectations. Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the TC Handbook [1]. 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 [2]. 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, e.g., edxl-ct-v1.0-wd02, edxl-ct-v1.0-wd03, etc. 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 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 [3]. When the TC votes [4] 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 [5]. Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library as a Committee Draft (
http://docs.oasis-open.org/ ), including addition of the requisite cover page metadata and other boilerplate information, as described in the TC Handbook. [6] =========== References: [1] Working Drafts
http://docs.oasis-open.org/TChandbook/Reference/WorkingDrafts.html [2] SVN Version control, via Tools
http://tools.oasis-open.org/ [3] OASIS Naming Directives
http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html [4] Approval of a WD as a CD (CSD or CND)
http://www.oasis-open.org/committees/process-2010-07-28.php#committeeDraft [5] TC Administration Requests Page, see Committee Specification Draft Creation / Upload Request
http://docs.oasis-open.org/templates/TCAdminRequests15-10-2010.html [6] Committee Specification Drafts and Committee Note Drafts
http://docs.oasis-open.org/TChandbook/Reference/CommitteeSpecDrafts.html http://docs.oasis-open.org/TChandbook/Reference/CommitteeNoteDrafts.html --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php