OASIS - Revision history

Antoniok at 16:41, 3 April 2017

2017-04-03T16:41:13Z

← Older revision		Revision as of 18:41, 3 April 2017
Line 32:		Line 32:
	\|		\|
	*Committee Specification Draft V1.0 26 March 2012. [http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf]		*Committee Specification Draft V1.0 26 March 2012. [http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf]
			*Slides prepared by John Sabo during IPEN workshop (June 5th 2015)[http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf]
	*Version 1.0, OASIS Committee Specification 02, incorporating numerous enhancements and clarifications to CS01, was approved by the TC on 17 May 2016 and is available at[http://docs.oasis-open.org/pmrm/PMRM/v1.0/cs02/PMRM-v1.0-cs02.html http://docs.oasis-open.org/pmrm/PMRM/v1.0/cs02/PMRM-v1.0-cs02.html]		*Version 1.0, OASIS Committee Specification 02, incorporating numerous enhancements and clarifications to CS01, was approved by the TC on 17 May 2016 and is available at[http://docs.oasis-open.org/pmrm/PMRM/v1.0/cs02/PMRM-v1.0-cs02.html http://docs.oasis-open.org/pmrm/PMRM/v1.0/cs02/PMRM-v1.0-cs02.html]
	*Slides prepared by John Sabo during IPEN workshop (June 5th 2015)[http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf]

	\|-		\|-

Antoniok at 16:40, 3 April 2017

2017-04-03T16:40:42Z

← Older revision		Revision as of 18:40, 3 April 2017
Line 32:		Line 32:
	\|		\|
	*Committee Specification Draft V1.0 26 March 2012. [http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf]		*Committee Specification Draft V1.0 26 March 2012. [http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf]
	*		*Version 1.0, OASIS Committee Specification 02, incorporating numerous enhancements and clarifications to CS01, was approved by the TC on 17 May 2016 and is available at[http://docs.oasis-open.org/pmrm/PMRM/v1.0/cs02/PMRM-v1.0-cs02.html http://docs.oasis-open.org/pmrm/PMRM/v1.0/cs02/PMRM-v1.0-cs02.html]
	Version 1.0, OASIS Committee Specification 02, incorporating numerous enhancements and clarifications to CS01, was approved by the TC on 17 May 2016 and is available at[http://docs.oasis-open.org/pmrm/PMRM/v1.0/cs02/PMRM-v1.0-cs02.html http://docs.oasis-open.org/pmrm/PMRM/v1.0/cs02/PMRM-v1.0-cs02.html]

	*Slides prepared by John Sabo during IPEN workshop (June 5th 2015)[http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf]		*Slides prepared by John Sabo during IPEN workshop (June 5th 2015)[http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf]

Antoniok at 16:40, 3 April 2017

2017-04-03T16:40:10Z

← Older revision		Revision as of 18:40, 3 April 2017
Line 32:		Line 32:
	\|		\|
	*Committee Specification Draft V1.0 26 March 2012. [http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf]		*Committee Specification Draft V1.0 26 March 2012. [http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf]
			*
			Version 1.0, OASIS Committee Specification 02, incorporating numerous enhancements and clarifications to CS01, was approved by the TC on 17 May 2016 and is available at[http://docs.oasis-open.org/pmrm/PMRM/v1.0/cs02/PMRM-v1.0-cs02.html http://docs.oasis-open.org/pmrm/PMRM/v1.0/cs02/PMRM-v1.0-cs02.html]

	*Slides prepared by John Sabo during IPEN workshop (June 5th 2015)[http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf]		*Slides prepared by John Sabo during IPEN workshop (June 5th 2015)[http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf]

Antoniok: Undo revision 721 by Antoniok (talk)

2017-04-03T16:39:02Z

Undo revision 721 by Antoniok (talk)

← Older revision		Revision as of 18:39, 3 April 2017
Line 1:		Line 1:
	~~<span style="font-size:larger;"></span>~~[[File:OASIS.png]]		[[File:OASIS.png]]

	== <span style="font-size:larger;">Introduction</span> ==		== <span style="font-size:larger;">Introduction</span> ==
Line 9:		Line 9:
	== <span style="font-size:larger;">Technical Committees</span> ==		== <span style="font-size:larger;">Technical Committees</span> ==

	~~<parsererror style="display: block; white-space: pre; border: 2px solid #c77; padding: 0 1em 0 1em; margin: 1em; background-color: #fdd; color: black">~~
	~~=== This page contains the following errors: ===~~
	~~<div style="font-family:monospace;font-size:12px">error on line 1 at column 2155: attributes construct error </div>~~
	~~=== Below is a rendering of the page up to the first error. ===~~
	~~</parsererror>~~
	=== <span style="font-size:larger;">PMRM (Privacy Management Reference Model)</span> ===		=== <span style="font-size:larger;">PMRM (Privacy Management Reference Model)</span> ===

Line 27:		Line 22:
	<span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, 'DejaVu Sans', sans-serif; font-size: 12px; line-height: 18px;">The OASIS PMRM TC works to provide a standards-based framework that will help business process engineers, IT analysts, architects, and developers implement privacy and security policies in their operations. PMRM picks up where broad privacy policies leave off. Most policies describe fair information practices and principles but offer little insight into actual implementation. PMRM provides a guideline or template for developing operational solutions to privacy issues. It also serves as an analytical tool for assessing the completeness of proposed solutions and as the basis for establishing categories and groupings of privacy management controls.</span>		<span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, 'DejaVu Sans', sans-serif; font-size: 12px; line-height: 18px;">The OASIS PMRM TC works to provide a standards-based framework that will help business process engineers, IT analysts, architects, and developers implement privacy and security policies in their operations. PMRM picks up where broad privacy policies leave off. Most policies describe fair information practices and principles but offer little insight into actual implementation. PMRM provides a guideline or template for developing operational solutions to privacy issues. It also serves as an analytical tool for assessing the completeness of proposed solutions and as the basis for establishing categories and groupings of privacy management controls.</span>


	~~<span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, 'DejaVu Sans', sans-serif; font-size: 12px; line-height: 18px;"></span>~~
	\|-		\|-
	\| Web pages		\| Web pages
Line 39:		Line 32:
	\|		\|
	*Committee Specification Draft V1.0 26 March 2012. [http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf]		*Committee Specification Draft V1.0 26 March 2012. [http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf]
	*		*Slides prepared by John Sabo during IPEN workshop (June 5th 2015)[http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf]

			\|-
			\| Comments
			\|
			[Antonio Kung]

			*use case based process
			*integrates concept of touch points (supporting systems developed by several organisations)

	\|}		\|}

Antoniok at 16:37, 3 April 2017

2017-04-03T16:37:47Z

← Older revision		Revision as of 18:37, 3 April 2017
Line 9:		Line 9:
	== <span style="font-size:larger;">Technical Committees</span> ==		== <span style="font-size:larger;">Technical Committees</span> ==

			<parsererror style="display: block; white-space: pre; border: 2px solid #c77; padding: 0 1em 0 1em; margin: 1em; background-color: #fdd; color: black">
			=== This page contains the following errors: ===
			<div style="font-family:monospace;font-size:12px">error on line 1 at column 2155: attributes construct error </div>
			=== Below is a rendering of the page up to the first error. ===
			</parsererror>
	=== <span style="font-size:larger;">PMRM (Privacy Management Reference Model)</span> ===		=== <span style="font-size:larger;">PMRM (Privacy Management Reference Model)</span> ===

Line 18:		Line 23:
	\| Overview		\| Overview
	\|		\|
	~~<span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, 'DejaVu Sans', sans-serif; font-size: 12px; line-height: 18px;"></span>~~<span style="line-height: 20.7999992370605px;">Privacy Management Reference Model and Methodology (PMRM) Version 1.0 was approved as an Committee Specification Draft on 26 March 2012</span>		<span style="line-height: 20.7999992370605px;">Privacy Management Reference Model and Methodology (PMRM) Version 1.0 was approved as an Committee Specification Draft on 26 March 2012</span>

	~~<span style="line-height: 20.7999992370605px;"></span>~~<span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, 'DejaVu Sans', sans-serif; font-size: 12px; line-height: 18px;">The OASIS PMRM TC works to provide a standards-based framework that will help business process engineers, IT analysts, architects, and developers implement privacy and security policies in their operations. PMRM picks up where broad privacy policies leave off. Most policies describe fair information practices and principles but offer little insight into actual implementation. PMRM provides a guideline or template for developing operational solutions to privacy issues. It also serves as an analytical tool for assessing the completeness of proposed solutions and as the basis for establishing categories and groupings of privacy management controls.</span>		<span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, 'DejaVu Sans', sans-serif; font-size: 12px; line-height: 18px;">The OASIS PMRM TC works to provide a standards-based framework that will help business process engineers, IT analysts, architects, and developers implement privacy and security policies in their operations. PMRM picks up where broad privacy policies leave off. Most policies describe fair information practices and principles but offer little insight into actual implementation. PMRM provides a guideline or template for developing operational solutions to privacy issues. It also serves as an analytical tool for assessing the completeness of proposed solutions and as the basis for establishing categories and groupings of privacy management controls.</span>


			<span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, 'DejaVu Sans', sans-serif; font-size: 12px; line-height: 18px;"></span>
	\|-		\|-
	\| Web pages		\| Web pages
Line 32:		Line 39:
	\|		\|
	*Committee Specification Draft V1.0 26 March 2012. [http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf]		*Committee Specification Draft V1.0 26 March 2012. [http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf http://docs.oasis-open.org/pmrm/PMRM/v1.0/csd01/PMRM-v1.0-csd01.pdf]
	*Slides prepared by John Sabo during IPEN workshop (June 5th 2015)[http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf http://ipen.trialog.com/wiki/File:PMRM_Overview-_Short_IPEN_5_June_2015.pdf]		*

	\|-
	~~\| Comments~~
	\|
	~~[Antonio Kung]~~

	*use case based process
	*integrates concept of touch points (supporting systems developed by several organisations)

	\|}		\|}

Antoniok at 15:12, 4 August 2015

2015-08-04T15:12:20Z

← Older revision		Revision as of 17:12, 4 August 2015
Line 17:		Line 17:
	\|-		\|-
	\| Overview		\| Overview
	\| <span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, 'DejaVu Sans', sans-serif; font-size: 12px; line-height: 18px;">The OASIS PMRM TC works to provide a standards-based framework that will help business process engineers, IT analysts, architects, and developers implement privacy and security policies in their operations. PMRM picks up where broad privacy policies leave off. Most policies describe fair information practices and principles but offer little insight into actual implementation. PMRM provides a guideline or template for developing operational solutions to privacy issues. It also serves as an analytical tool for assessing the completeness of proposed solutions and as the basis for establishing categories and groupings of privacy management controls.</span>~~<br/>~~		\|
			<span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, 'DejaVu Sans', sans-serif; font-size: 12px; line-height: 18px;"></span><span style="line-height: 20.7999992370605px;">Privacy Management Reference Model and Methodology (PMRM) Version 1.0 was approved as an Committee Specification Draft on 26 March 2012</span>

			<span style="line-height: 20.7999992370605px;"></span><span style="color: rgb(0, 0, 0); font-family: Verdana, Tahoma, 'DejaVu Sans', sans-serif; font-size: 12px; line-height: 18px;">The OASIS PMRM TC works to provide a standards-based framework that will help business process engineers, IT analysts, architects, and developers implement privacy and security policies in their operations. PMRM picks up where broad privacy policies leave off. Most policies describe fair information practices and principles but offer little insight into actual implementation. PMRM provides a guideline or template for developing operational solutions to privacy issues. It also serves as an analytical tool for assessing the completeness of proposed solutions and as the basis for establishing categories and groupings of privacy management controls.</span>

	\|-		\|-
	\| Web pages		\| Web pages
Line 40:		Line 44:
	\|}		\|}

	=== <span style="font-size:larger;">PbD-SE</span> ===		=== <span style="font-size:larger;">PbD-SE (Privacy-by-Design Documentation for Software Engineers)</span> ===

	{\| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"		{\| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
Line 49:		Line 53:
	\| Overview		\| Overview
	\|		\|
	~~Privacy Management Reference Model and Methodology (PMRM) Version~~ 1.~~0 was approved as an Committee Specification Draft on 26 March 2012~~		<span style="line-height: 1.6;">The OASIS PbD-SE TC provides privacy governance and documentation standards for software engineers. It enables software organizations to embed privacy into the design and architecture of IT systems, without diminishing system functionality.</span>

	The OASIS PbD-SE TC provides privacy governance and documentation standards for software engineers. It enables software organizations to embed privacy into the design and architecture of IT systems, without diminishing system functionality.

	The PbD-SE TC work follows the Seven Foundational Principles of Privacy by Design:		The PbD-SE TC work follows the Seven Foundational Principles of Privacy by Design:

Antoniok at 15:48, 25 June 2015

2015-06-25T15:48:43Z

← Older revision		Revision as of 17:48, 25 June 2015
Line 9:		Line 9:
	== <span style="font-size:larger;">Technical Committees</span> ==		== <span style="font-size:larger;">Technical Committees</span> ==

	=== <span style="font-size:larger;">PMRM</span> ===		=== <span style="font-size:larger;">PMRM (Privacy Management Reference Model)</span> ===

	{\| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"		{\| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"

Antoniok at 12:29, 19 June 2015

2015-06-19T12:29:44Z

← Older revision		Revision as of 14:29, 19 June 2015
Line 1:		Line 1:
			<span style="font-size:larger;"></span>[[File:OASIS.png]]

	== <span style="font-size:larger;">Introduction</span> ==		== <span style="font-size:larger;">Introduction</span> ==

	~~<span style="font-size:larger;"></span>~~<span style="color: rgb(37, 37, 37); font-family: sans-serif; font-size: 14px; line-height: 22.3999996185303px;">The objective of this page is to provide a high-level view of activities related to privacy standards in OASIS</span>		<span style="color: rgb(37, 37, 37); font-family: sans-serif; font-size: 14px; line-height: 22.3999996185303px;">The objective of this page is to provide a high-level view of activities related to privacy standards in OASIS</span>

	== <span style="font-size:larger;">Some conventions on OASIS standards</span> ==		== <span style="font-size:larger;">Some conventions on OASIS standards</span> ==

Antoniok at 10:39, 19 June 2015

2015-06-19T10:39:55Z

← Older revision		Revision as of 12:39, 19 June 2015
Line 43:		Line 43:
	\|-		\|-
	\| Chair		\| Chair
	\| ~~Danw~~ Jutla, Ann Cavoukian		\| Dawn Jutla, Ann Cavoukian
	\|-		\|-
	\| Overview		\| Overview

Antoniok at 18:16, 18 June 2015

2015-06-18T18:16:34Z

← Older revision		Revision as of 20:16, 18 June 2015
Line 1:		Line 1:
	== <span style="font-size:larger;">Introduction</span> ==		== <span style="font-size:larger;">Introduction</span> ==

			<span style="font-size:larger;"></span><span style="color: rgb(37, 37, 37); font-family: sans-serif; font-size: 14px; line-height: 22.3999996185303px;">The objective of this page is to provide a high-level view of activities related to privacy standards in OASIS</span>

	== <span style="font-size:larger;">Some conventions on OASIS standards</span> ==		== <span style="font-size:larger;">Some conventions on OASIS standards</span> ==