Re: [pbd-se] Groups - Privacy by Design Documentation for Software Engin

Subject: Re: [pbd-se] Groups - Privacy by Design Documentation for Software Engineers - Working Draft uploaded

Hi Frank, hi all ...

Maybe a quick explanation of how the process flows will help. You can find a detailed write up at https://www.oasis-open.org/resources/tcadmin/developing-committee-specifications-and-notes

- First, the TC takes the starter document that Paul sent you and uses it to create a working draft of the specification. The TC stores its working draft(s) (e.g. pbd-se-v1.0-wd01.doc) in the TC document repository at https://www.oasis-open.org/apps/org/workgroup/pbd-se/documents.php . (If you want additional folders there, submit a ticket at https://www.oasis-open.org/resources/tc-admin-requests/folder-creation-request and I will set it up for you.)

- You can approve working drafts as Committee Specification Drafts (CSD) whenever you are ready. Most TCs approve their first CSD when they are ready to send it out for public review. To approve a CSD and to approve it to go out for a public review, you must approve a motion in the TC by Full Majority Vote. The motion must include the URL to the working draft you are approving. You'll find template motion language for these motions here -> https://www.oasis-open.org/resources/tcadmin/tc-motion-language-templates

- You can use the TC Document Submission Checklist at https://www.oasis-open.org/apps/org/workgroup/tca/download.php/47468/tc-submission-checklist-wd03.html to determine whether your working draft is ready to go out for public review. (I'm always happy to answer any questions you have about these steps.) When you are ready for public review, pass the motion to approve the working draft as a CSD and the motion to release it for public review. Then submit the tickets at https://www.oasis-open.org/resources/tc-admin-requests/committee-specification-draft-creation-upload-request and https://www.oasis-open.org/resources/tc-admin-requests/30-day-committee-specification-draft-public-review-request that assign the next steps to me.

- When we have those tickets, we will produce the Committee Spec Draft and the Committee Spec Public Review Draft in doc, html and pdf formats (along with any other artifacts you supply with it, e.g. xml schemas). These documents will be in http://docs.oasis-open.org/pbd-se/pbd-se/v1.0/csd01/ and http://docs.oasis-open.org/pbd-se/pbd-se/v1.0/csprd01/ respectively. We will then announce the public review to OASIS and the world at large.

- You can go through the above steps as many times as needed. At some stage - either when you have received no comments or received no comments requiring significant changes - you can approve the CSD as a Committee Specification. This is done via a Special Majority Vote. You pass a motion in a meeting of the TC to request the Special Majority Vote, submit the request to me in https://www.oasis-open.org/resources/tc-admin-requests/committee-specification-ballot-request and then I set up and run the ballot.

- Once that ballot has passed, I publish the final Committee Specification 01 in http://docs.oasis-open.org/pbd-se/pbd-se/v1.0/cs01/pbd-se-v1.0-cs01.doc.

Then we can talk about the steps for moving to OASIS Standard.

Let me know if you have any questions.

/chet

On Wed, Jul 17, 2013 at 12:09 PM, <Frank.Dawson@nokia.com> wrote:

Hei Ann.

I just got to Paul Knight’s July 3^rd email, as it seems to have been lost in my July 4/Independence Day break. He mentions that the working draft should be stored at the URL http://docs.oasis-open.org/pbd-se/pbd-se/v1.0/csd01/pbd-se-v1.0-csd01.doc. Can we get the TC secretary to move the document there?

Also, I think this is v0.1, not v1.0. Right?

Frank/

From: pbd-se@lists.oasis-open.org [mailto:pbd-se@lists.oasis-open.org] On Behalf Of ext Ann Cavoukian
Sent: 10 July, 2013 16:07
To: pbd-se@lists.oasis-open.org
Subject: [pbd-se] Groups - Privacy by Design Documentation for Software Engineers - Working Draft uploaded

Submitter's message
The specification working draft (v1.0) is now based on the official template provided by OASIS.

The current revised document outline reflects input and feedback received from TC members to date.

Please Note:

- Text in blue-highlighted font contains instructions
on how to complete sections, and is not part of the
specification.

- Text in dark-yellow-highlighted font contains
substantive content drawn primarily from the TC Charter.

- Text in light-yellow-highlighted font contains new
and provisional content.

At the next TC meeting, we seek consensus on:

1. the general document framework / outline
2. TC member contributions / assignments
3. work methods / notional milestones and timetable

-- Dr. Ann Cavoukian

Document Name: Privacy by Design Documentation for Software Engineers - Working Draft

Description
This specification describes software tools that engineers can use to aid
in producing documentation and to show compliance with the Privacy by
Design (PbD) principles, and privacy regulations, throughout the software
development life cycle.
Download Latest Revision
Public Download Link

Submitter: Dr. Ann Cavoukian
Group: OASIS Privacy by Design Documentation for Software Engineers (PbD-SE) TC
Folder: Documents
Date submitted: 2013-07-10 14:07:08

--

/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open

pbd-se message