[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [pbd-se] Starter Document for Privacy by Design Documentation for Software Engineers Version 1.0
Hi Frank,Sure.A csd or 'Committee Specification Draft' gets published to that location after a work product ballot, so to actually approve a document as such by the TC.All document artifacts before that 'work product ballot' are working drafts and only available in e.g. the TC repository.Please have a look at the TC process, which will clarify most of this: https://www.oasis-open.org/policies-guidelines/tc-process#dWPballotIf you have more questions, pleae let me know.Kind regards,Gershon JanssenOn Wed, Jul 17, 2013 at 6:13 PM, <Frank.Dawson@nokia.com> wrote:Thank you, but I was confused because the URL had “csd01” as a sub-path under “v1.0” which clearly implies each draft will be put in a sub-path under “v1.0” to help with document management and version control. No?
From: pbd-se@lists.oasis-open.org [mailto:pbd-se@lists.oasis-open.org] On Behalf Of ext Gershon Janssen
Sent: 17 July, 2013 11:12
To: Dawson Frank (Nokia-CIC/Dallas)
Cc: Paul Knight; pbd-se@lists.oasis-open.org
Subject: Re: [pbd-se] Starter Document for Privacy by Design Documentation for Software Engineers Version 1.0
Hi Frank,
> We expect this Work Product to be published at:
The location mentioned is the target location of the document, after the necessary work by the TC.
The starter document with first modifications is available in our TC Kavi space:
This link, including a few pointers for today's discussion are also included in the agenda for today's meeting.
Does this answer your question?
Kind regards,
Gershon Janssen
On Wed, Jul 17, 2013 at 6:06 PM, <Frank.Dawson@nokia.com> wrote:
Hei Paul.
The link to the csd01 document generates a HTTP 404 error, so appears to be broken? Can we get the TC secretary to put the document here so that readers of the email threads can find it.
Frank/
From: pbd-se@lists.oasis-open.org [mailto:pbd-se@lists.oasis-open.org] On Behalf Of ext Paul Knight
Sent: 03 July, 2013 08:54
To: pbd-se@lists.oasis-open.org
Subject: [pbd-se] Starter Document for Privacy by Design Documentation for Software Engineers Version 1.0
Per the TC's submission request [1], please find the attached starter document for:
Privacy by Design Documentation for Software Engineers Version 1.0
WP-abbrev: pbd-se
We expect this Work Product to be published at:
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 Notes
Starting 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 Request
Best wishes,
Paul
--
Paul Knight - Tel: +1 781-861-1013
OASIS - Advancing open standards for the information society
Document Process Analyst
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]