[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [pmrm] Updated: Starter Document for Privacy Management Reference Model Version 1.0
|
Thanks Paul Guys, as promised on the last call, I’ll take a first bash at decanting the current content into the official template. I’ll do this in two passes: -
First pass: without any change of content and without “track changes” active; -
Second pass: with changes and edits to make best use of the formal template structure, with “track changes” active Cheers, Peter Peter F Brown Independent Consultant P.O. Box 49719, Los Angeles, CA 90049, USA Tel: +1.310.694.2278 From: pmrm@lists.oasis-open.org [mailto:pmrm@lists.oasis-open.org]
On Behalf Of Paul Knight Sorry for the repetition... Please use the attached document, in MS-Word format (as requested) instead of OpenOffice format. - Paul Best wishes as the Privacy Management Reference Model TC undertakes its first publication! Per the TC's submission request [1], please find the attached starter document for: Privacy Management Reference Model Version 1.0 WP-abbrev: PMRM The expected URI pattern: 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 TC Handbook [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 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. [7] =========== References: [2] Working Drafts [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 Request [7] Committee Specification Drafts and Committee Note Drafts Best wishes, Paul
--
-- |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]