Yes, that will be fine. I have attached a modified starter document, with this change.
I used the abbreviation etmf-std,
I'm also sending a copy of this to the TC mailing list, so the Editors can retrieve it directly from the mailing list archive if needed.
Best regards,
Paul
On Sun, Apr 27, 2014 at 11:44 AM, Zack Schmidt <zs@sureclinical.net> wrote:
Hi Paul,I believe we'll be discussing this WD spec tomorrow in our TC.I have a question re: the title assigned by Oasis - can we change it?Here is the Oasis preliminary assigned title:Electronic Trial Master File (eTMF) Model Version 1.0Here is a proposed new title (subject to TC and Oasis admin approval):Electronic Trial Master File (eTMF) Standard Version 1.0Thanks.On Fri, Apr 18, 2014 at 12:36 PM, Paul Knight <paul.knight@oasis-open.org> wrote:
--Per the TC's submission request [1], please find the attached starter document for:Electronic Trial Master File (eTMF) Model Version 1.0WP-abbrev: etmf-model
NOTE: The TC may modify the title before initial publication.When the TC first votes [5] to publish this Work Product in the OASIS Library, we expect it to be published at:The permanent "Latest version" URI will be: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:[2] Developing Committee Specifications and NotesStarting a Working Draft[3] SVN Version control, via Tools[4] OASIS Naming Directives[5] Approval of a WD as a CD (CSD or CND)[6] TC Administration Requests Page, see Committee Specification Draft Creation / Upload RequestBest wishes,Paul
Paul Knight - Tel: +1 781-861-1013
OASIS - Advancing open standards for the information society
Document Process Analyst
---------------------------------------------------------------------
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
--Zack Schmidt, CEO
SureClinicalHealthscience Applications
2865 Sunrise Blvd Suite 218
Rancho Cordova, CA 95742zs@SureClinical.netSupport: 916-265-2000Direct: 916-265-2004
![]()
| SureClinical is committed to business processes that protect the environment through the reduction of paper
Paul Knight - Tel: +1 781-861-1013
OASIS - Advancing open standards for the information society
Document Process Analyst
OASIS - Advancing open standards for the information society
Document Process Analyst