IdCommons - Recent changes [en]

MCAF

2010-09-07T02:31:40Z

← Older revision		Revision as of 02:31, 7 September 2010
Line 4:		Line 4:


-	'''The problem:'''	+	''The problem:''

	Today there is a lack of notice and transparency around the use of volunteered personal information that is becoming a bigger issue every day. As there is an onus on the individual to protect their own data, take responsibility for themselves, there is also a need for the tools to do this with.		Today there is a lack of notice and transparency around the use of volunteered personal information that is becoming a bigger issue every day. As there is an onus on the individual to protect their own data, take responsibility for themselves, there is also a need for the tools to do this with.
Line 13:		Line 13:
	== Terms Definition ==		== Terms Definition ==

-	The Master Controller Access Framework	+	The Master Data Controller Access Framework

-	""Master:"" Refers to what is commonly know as the data subject,	+	'''Master:''' Refers to what is commonly know as the data subject,

-	~~""Controller:""~~ refers to the ~~fact~~ that the Master ~~data provider~~ is the ~~person that~~ is ~~responsible~~ for ~~controlling the~~ data ~~that they share~~	+	'''Data''' - Data refers to the data that the Master Controller can control, although since Master is explicit in the use of the MCAF, as far as rights go, a master controller is repsonsible for their own actions. The term data doesnt need to be explicitly spelt out accept in particular use. This is why the acronym is (MCAF) not MDCAF.

-	~~Access~~: ~~Refers~~ to the ~~physical ability for~~ the ~~individual to gain information regarding~~ the ~~circumstances, process, contracts, technical ramifications, and so on of~~ the ~~information~~ that ~~a person holds.~~	+	'''Controller:''' refers to the fact that the Master data provider is the person that is responsible for controlling the data that they share

-	""Framework:"" Refers to the methods and infrastructure the master controller uses to access the information regarding how their personal information is going to be used, managed, controlled. As an individual in society is responsible for their own actions, responsible for their own security, and responsible to defend their own rights, it is critical that an individual has reasonable access to information regarding the circumstances, technology, and process that surround the use of their personal information, and in fact the information they share.	+	'''Access:''' Refers to the physical ability for the individual to gain information regarding the circumstances, process, contracts, technical ramifications, and so on of the information that a person holds.
		+
		+	'''Framework:''' Refers to the methods and infrastructure the master controller uses to access the information regarding how their personal information is going to be used, managed, controlled. As an individual in society is responsible for their own actions, responsible for their own security, and responsible to defend their own rights, it is critical that an individual has reasonable access to information regarding the circumstances, technology, and process that surround the use of their personal information, and in fact the information they share.

Identity Trust Charter

2010-09-07T00:04:45Z

Licenses and/or Restrictions on Usage of Work Product:

← Older revision		Revision as of 00:04, 7 September 2010
(3 intermediate revisions not shown)
Line 31:		Line 31:
	=== Licenses and/or Restrictions on Usage of Work Product ===		=== Licenses and/or Restrictions on Usage of Work Product ===

-	~~Conversation~~ on the list is private to the list. Permission must be granted by the author to republish. The contents of the wiki are licensed under Creative Commons 2.5 Attribution license http://creativecommons.org/licenses/by/2.5/	+	Conversations on the list are private to the list. Permission must be granted by the author to republish. The contents of the wiki are licensed under Creative Commons 3.0 Attribution license http://creativecommons.org/licenses/by-nc-sa/3.0/
-	~~There may be a Lexicon 2.0 that continues the Shared Language work.~~	+

-	Dependant on participation and volunteers/sponsorship, collaborative discussion and analysis will be summarised and disseminated for use in other projects. The resulting collaboration will be used to develop the principles of this working group.

-	~~The MCAF is also shared under Creative Commons License~~, ~~although if the MCAF is used~~ for ~~profit purposes, license fee's may be applied~~.	+	Dependant on participation and volunteers/sponsorship, collaborative discussion and analysis will be summarised and disseminated for use in other projects.

-	~~<a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/3.0/"><img alt="~~Creative Commons License~~" style="border-width:0" src="http://i.creativecommons.org/l/by-nc-sa/~~3.0~~/88x31~~.~~png" /></a><br /><span xmlns~~:~~dc="http~~:~~//purl.org/dc/elements/1.1/" property="dc:title">~~(~~MCAF~~) ~~Master Data Controller Access Framework</span> by <a xmlns:cc="http://creativecommons~~.~~org/ns#" href="http~~:~~//www.identitytrustcic.org~~" ~~property=~~"~~cc:attributionName" rel="cc:attributionURL">Mark Lizar</a> is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by~~-~~nc-sa/3~~.~~0/">Creative Commons Attribution-NonCommercial-ShareAlike 3~~.~~0 Unported License</a>~~.~~<br />Permissions beyond~~ the ~~scope of~~ this ~~license may be available at <a xmlns:cc="http://creativecommons~~.~~org/ns#" href="http~~:~~//wiki~~.~~identitycommons~~.~~net/Identity_Trust_Charter" rel="cc~~:~~morePermissions">http://wiki~~.~~identitycommons~~.~~net/Identity_Trust_Charter</~~a>.	+	The [[MCAF]] is shared under Creative Commons License 3.0 this means.
		+
		+
		+	You are free:
		+
		+	* to Share — to copy, distribute and transmit the work
		+	* to Remix — to adapt the work
		+	*
		+
		+	Under the following conditions:
		+
		+	Attribution — You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).
		+
		+	Attribute this work:
		+	Information
		+	What does "Attribute this work" mean?
		+	The page you came from contained embedded licensing metadata, including how the creator wishes to be attributed for re-use. You can use the HTML here to cite the work. Doing so will also include metadata on your page so that others can find the original work as well.
		+	*
		+
		+	Noncommercial — You may not use this work for commercial purposes.
		+	*
		+
		+	Share Alike — If you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
		+
		+	With the understanding that:
		+
		+	* Waiver — Any of the above conditions can be waived if you get permission from the copyright holder. (Which is this working group Identity Trust)
		+	* Public Domain — Where the work or any of its elements is in the public domain under applicable law, that status is in no way affected by the license.
		+	* Other Rights — In no way are any of the following rights affected by the license:
		+	o Your fair dealing or fair use rights, or other applicable copyright exceptions and limitations;
		+	o The author's moral rights;
		+	o Rights other persons may have either in the work itself or in how the work is used, such as publicity or privacy rights.
		+	* Notice — For any reuse or distribution, you must make clear to others the license terms of this work. The best way to do this is with a link to this web page.

	=== Current Meeting Schedule ===		=== Current Meeting Schedule ===
Line 71:		Line 101:
	===History===		===History===

-	Identity Trust is a working group that has been [[gestating\| gestating ~~for~~ since 2007]] as in preparing to be officially ~~launched~~ at the IIW 2010 in London on October 11th.	+	Identity Trust is a working group that has been [[gestating\| gestating since 2007]] as in preparing to be officially restarted at the IIW 2010 in London on October 11th.

	This working group effort was started to develop a framework for the individual for [[Trust\|Trust and control]] in Identity Management.		This working group effort was started to develop a framework for the individual for [[Trust\|Trust and control]] in Identity Management.

MCAF

2010-09-06T23:33:54Z

← Older revision		Revision as of 23:33, 6 September 2010
(2 intermediate revisions not shown)
Line 1:		Line 1:
-	This is a brief introduction to the Master Data Controller Access Framework or (MCAF).	+	This is a brief introduction to the Master Data Controller Access Framework or (MCAF) intended to develop a trust and transparency with the use of digital identity management.

-	Simply put, the MCAF is a rights based framework for developing digital identity architecture.	+	Simply put, the MCAF is a rights based framework for developing digital identity architecture. A framework intended to bridge the gaps between the use of access rights and Notice infrastructure by the individual (A.K.A. The Data Subject) in order to develop trusted digital services and infrastructure.

-	Today there is a lack of notice and transparency that is becoming a bigger issue every day. As there is an onus on the individual to protect their own data, take responsibility for themselves, there is also a need for the tools to do this with.

-	~~Using data protection~~ and ~~technical language~~ this framework ~~adds~~ the ~~word Master to~~ the ~~term~~ Data Controller ~~as a~~ way to ~~bridge technical~~ and ~~legal language gaps~~. -(See MCAF CCTV Use Case for ~~details~~)	+	'''The problem:'''
-	~~rveillance, regulation, and compliance designed to illustrate hot to evolve the use of rights and privacy until they are suitably operational.~~	+
		+	Today there is a lack of notice and transparency around the use of volunteered personal information that is becoming a bigger issue every day. As there is an onus on the individual to protect their own data, take responsibility for themselves, there is also a need for the tools to do this with.
		+
		+	This framework introduces the conceptual framework of the Master Data Controller to data protection and technical lexicons. In this way the MCAF bridges these gaps and provides a methodology to address the gap between consent and current notice policies. -(See MCAF CCTV Use Case for example)
		+

	== Terms Definition ==		== Terms Definition ==
Line 12:		Line 15:
	The Master Controller Access Framework		The Master Controller Access Framework

-	Master: Refers to what is commonly know as the data subject,	+	""Master:"" Refers to what is commonly know as the data subject,

-	Controller: refers to the fact that the Master data provider is ~~in fact~~ the person that is responsible for controlling the data that they share	+	""Controller:"" refers to the fact that the Master data provider is the person that is responsible for controlling the data that they share

	Access: Refers to the physical ability for the individual to gain information regarding the circumstances, process, contracts, technical ramifications, and so on of the information that a person holds.		Access: Refers to the physical ability for the individual to gain information regarding the circumstances, process, contracts, technical ramifications, and so on of the information that a person holds.

-	Framework: Refers to the methods and infrastructure the master controller uses to access the information regarding how their personal information is going to be used, managed, controlled. As an individual in society is responsible for their own actions, responsible for their own security, and responsible to defend their own rights, it is critical that an individual has reasonable access to information regarding the circumstances, technology, and process that surround the use of their personal information, and in fact the information they share.	+	""Framework:"" Refers to the methods and infrastructure the master controller uses to access the information regarding how their personal information is going to be used, managed, controlled. As an individual in society is responsible for their own actions, responsible for their own security, and responsible to defend their own rights, it is critical that an individual has reasonable access to information regarding the circumstances, technology, and process that surround the use of their personal information, and in fact the information they share.


-	=== Introduction ===	+	== Introduction ==
	Master Controller, distinctly refers to a hierarchical concept of responsibility, control and personal ownership in information rights, and more importantly, the natural rights an individual inherently have to control how they communicate.		Master Controller, distinctly refers to a hierarchical concept of responsibility, control and personal ownership in information rights, and more importantly, the natural rights an individual inherently have to control how they communicate.

-	Currently in law, the explicit requirement for institutions to provide notice to the Master Controller of information is unclear, not ~~standised~~ and consists of ad-hoc standards. A great deal of existing regulation like the Data Protection Act (DPA) only covers the right for an individual to access information about themselves held by the ~~organisation~~. Although this does not include technical physical requirements of notice beyond just basic information of purpose, contact details, and who the information is shared with.	+	Currently in law, the explicit requirement for institutions to provide notice to the Master Controller of information is unclear, not standarised and consists of ad-hoc standards. A great deal of existing regulation like the Data Protection Act (DPA) only covers the right for an individual to access information about themselves held by the organization. Although this does not include technical physical requirements of notice beyond just basic information of purpose, contact details, and who the information is shared with.

-	In fact, there are many little details that are not covered by data ~~protetion~~ regulation, privacy laws and so on, which directly affect the security and responsibility of the Master Controller regarding the environment, context, and process of the existing (rights based) data gathering tools (e.g. Freedom Of Information Requests, Subject Access Requests)	+	In fact, there are many little details that are not covered by data protection regulation, privacy laws and so on, which directly affect the security and responsibility of the Master Controller regarding the environment, context, and process of the existing (rights based) data gathering tools (e.g. Freedom Of Information Requests, Subject Access Requests)

	The lack of rights based and user controlled infrastructure for the individual in society is becoming ever more apparent and critical as information sharing and technology advances.		The lack of rights based and user controlled infrastructure for the individual in society is becoming ever more apparent and critical as information sharing and technology advances.

-	=== Benefits Of This Effort ===	+	==Objectives==
		+
		+	This framework is intended to develop the individuals infrastructure for engaging with institutions
		+	Developing individually driven access rights, making privacy visible, and providing a personal platform for control and commoditization of personal information.
		+
		+	Challenges:
		+	One of the major challenges to developing master controller access has been the issues of identity, both proving that you are the identity of the subject that requires access, but also safe guarding the rights of the individual when using rights. Up until recently this hasnt been solved. In 2010 new R&D in digital identity now makes this framework possible.
		+
		+	=== Draft Benefits Of This Effort ===

	* The MCAF provides an identity rights access framework for bridging gaps between security, privacy, the citizen and the community which obstruct current use of information rights.		* The MCAF provides an identity rights access framework for bridging gaps between security, privacy, the citizen and the community which obstruct current use of information rights.
-	* The MCAF explicitly being a framework for 'individually driven rights based access' (IDRBA) to the infrastructure of data subject information	+
	* The MCAF is a perspective typically represented by processes like the Freedom Of Information Request to government, Subject Access Requests to companies, compulsory notices (mandatory policies) that are comprised of current industrial age 'data subject' information architecture. (like CCTV Signs, Privacy Policies, Terms of Service Agreements, Acceptable Use Policies)		* The MCAF is a perspective typically represented by processes like the Freedom Of Information Request to government, Subject Access Requests to companies, compulsory notices (mandatory policies) that are comprised of current industrial age 'data subject' information architecture. (like CCTV Signs, Privacy Policies, Terms of Service Agreements, Acceptable Use Policies)
	* Functionally the MCAF contributes a framework perspective to facilitate appropriate digital identity infrastructure that provides appropriate and reciprocal transparency to the Master Data Controller.		* Functionally the MCAF contributes a framework perspective to facilitate appropriate digital identity infrastructure that provides appropriate and reciprocal transparency to the Master Data Controller.
-	* ~~Operationally the~~ MCAF is a rights based ~~approach~~ to ~~designing people driven notice~~ with ~~use cases~~ ~~that cover su~~	+	* The MCAF explicitly being a framework for ''''individually driven rights based access'''' (IDRBA) to the infrastructure of data subject information.
		+
		+	* This framework, along with the infrastructure development it is meant to inspire trusted digital services development.
		+
		+	Clearly regulators alone will not solve all of the challenges faced today. This Framework is designed to bridge these legal gaps.

-	* This framework, along with the infrastructure development it is meant to inspire, is needed as there frankly has been a lot of lip service to privacy compliance, subject access rights and little in the way of enforcement, access or real usability. Clearly regulators alone will not solve all of the challenges faced today. This Framework is designed to bridge these legal gaps.
	* What has in fact happened is principles, guidelines, and regulations for fair information practices are not adhered to in the collection and use of personal information. Even when these are developed into law, the infrastructure for their use is almost non existent, limited to opt-in/out check boxes, and appeals to toothless privacy commissioners.		* What has in fact happened is principles, guidelines, and regulations for fair information practices are not adhered to in the collection and use of personal information. Even when these are developed into law, the infrastructure for their use is almost non existent, limited to opt-in/out check boxes, and appeals to toothless privacy commissioners.
	* The most functionally critical of rights, is the right of access, and control of ones own personal information. This right is the stalwart of autonomy, self-determination, and self motivation. An incredibly important right for community health and human development.		* The most functionally critical of rights, is the right of access, and control of ones own personal information. This right is the stalwart of autonomy, self-determination, and self motivation. An incredibly important right for community health and human development.
-	* Ultimately this MCAF is a framework for evolving the existing rights infrastructure to provide user driven access to information.	+
-	* As a use case Identity Trust CIC has picked CCTV as a long standing issue in privacy, rights and user access. Representing online and off line issues.	+
-	* This Use ~~Case is also a very defined and practical use case that is a first step towards designing Master Control for individuals on the internet, dealing with Privacy Policies, and Terms Of Service.~~	+	== Use Cases ==
-	* This use case is intended to illustrate the need for greater transparency, notice, and user involvement for more advance and sensitive information sharing activities that are now emerging in main stream society	+

-	~~Objectives:~~	+	CCTV - The first MCAF use case is the application of this framework to address the use of Notice in Video Surveillance.
		+	* As a use case Identity Trust CIC has picked CCTV as a long standing issue in privacy, rights and user access. Representing online and off line issues.
		+	* This Use Case is also a very defined and practical use case that is a first step towards designing Master Control for individuals on the internet, dealing with Privacy Policies, and Terms Of Service.
		+	* This use case is intended to illustrate the need for greater transparency, notice, and user involvement for more advance and sensitive information sharing activities that are now emerging in main stream society.

-	~~This framework is intended to develop the individuals infrastructure for engaging with institutions~~
-	~~Developing individually driven access rights, making privacy visible, and providing a personal platform for control and commoditization of personal information.~~

-	~~Challenges:~~	+	== Historical Materials ==
-	One of the major challenges to developing master controller access has been the issues of identity, both proving that you are the identity of the subject that requires access, but also safe guarding the rights of the individual when using rights. Up until recently this hasnt been solved. ~~In 2010 new R&D in digital identity now makes this framework possible~~.	+
		+	== Research ==
		+	Check http://www.identitytrustcic.org

Identity Trust Charter

2010-09-06T21:17:44Z

Purpose:

← Older revision		Revision as of 21:17, 6 September 2010
(2 intermediate revisions not shown)
Line 11:		Line 11:
	The MCAF is actively being developed to be able to input requirements for a digital standard in notice. The bulk of the work done here will be evolving Access and Notice infrastructure.		The MCAF is actively being developed to be able to input requirements for a digital standard in notice. The bulk of the work done here will be evolving Access and Notice infrastructure.

-	~~=== Background ===~~	+	Link to the Draft contribution of the MCAF [[http://wiki.idcommons.net/MCAF]]
-		+
-	~~Identity Trust is a working group that has been [[gestating\| gestating for since 2007]] as in preparing~~ to ~~be officially launched at~~ the ~~IIW 2010 in London on October 11th.~~	+
-		+
-	~~This working group effort was started to develop a framework for~~ the ~~individual for~~ [[~~Trust\|Trust and control~~]] ~~in Identity Management.~~	+

	=== Practices ===		=== Practices ===
Line 74:		Line 70:

	===History===		===History===
		+
		+	Identity Trust is a working group that has been [[gestating\| gestating for since 2007]] as in preparing to be officially launched at the IIW 2010 in London on October 11th.
		+
		+	This working group effort was started to develop a framework for the individual for [[Trust\|Trust and control]] in Identity Management.

MCAF

2010-09-06T21:11:45Z

Created page with 'This is a brief introduction to the Master Data Controller Access Framework or (MCAF). Simply put, the MCAF is a rights based framework for developing digital identity architect...'

New page

This is a brief introduction to the Master Data Controller Access Framework or (MCAF).

Simply put, the MCAF is a rights based framework for developing digital identity architecture.

Today there is a lack of notice and transparency that is becoming a bigger issue every day. As there is an onus on the individual to protect their own data, take responsibility for themselves, there is also a need for the tools to do this with.

Using data protection and technical language this framework adds the word Master to the term Data Controller as a way to bridge technical and legal language gaps. -(See MCAF CCTV Use Case for details)
rveillance, regulation, and compliance designed to illustrate hot to evolve the use of rights and privacy until they are suitably operational.

== Terms Definition ==

The Master Controller Access Framework

Master: Refers to what is commonly know as the data subject,

Controller: refers to the fact that the Master data provider is in fact the person that is responsible for controlling the data that they share

Access: Refers to the physical ability for the individual to gain information regarding the circumstances, process, contracts, technical ramifications, and so on of the information that a person holds.

Framework: Refers to the methods and infrastructure the master controller uses to access the information regarding how their personal information is going to be used, managed, controlled. As an individual in society is responsible for their own actions, responsible for their own security, and responsible to defend their own rights, it is critical that an individual has reasonable access to information regarding the circumstances, technology, and process that surround the use of their personal information, and in fact the information they share.

=== Introduction ===
Master Controller, distinctly refers to a hierarchical concept of responsibility, control and personal ownership in information rights, and more importantly, the natural rights an individual inherently have to control how they communicate.

Currently in law, the explicit requirement for institutions to provide notice to the Master Controller of information is unclear, not standised and consists of ad-hoc standards. A great deal of existing regulation like the Data Protection Act (DPA) only covers the right for an individual to access information about themselves held by the organisation. Although this does not include technical physical requirements of notice beyond just basic information of purpose, contact details, and who the information is shared with.

In fact, there are many little details that are not covered by data protetion regulation, privacy laws and so on, which directly affect the security and responsibility of the Master Controller regarding the environment, context, and process of the existing (rights based) data gathering tools (e.g. Freedom Of Information Requests, Subject Access Requests)

The lack of rights based and user controlled infrastructure for the individual in society is becoming ever more apparent and critical as information sharing and technology advances.

=== Benefits Of This Effort ===

* The MCAF provides an identity rights access framework for bridging gaps between security, privacy, the citizen and the community which obstruct current use of information rights.
* The MCAF explicitly being a framework for 'individually driven rights based access' (IDRBA) to the infrastructure of data subject information
* The MCAF is a perspective typically represented by processes like the Freedom Of Information Request to government, Subject Access Requests to companies, compulsory notices (mandatory policies) that are comprised of current industrial age 'data subject' information architecture. (like CCTV Signs, Privacy Policies, Terms of Service Agreements, Acceptable Use Policies)
* Functionally the MCAF contributes a framework perspective to facilitate appropriate digital identity infrastructure that provides appropriate and reciprocal transparency to the Master Data Controller.
* Operationally the MCAF is a rights based approach to designing people driven notice with use cases that cover su

* This framework, along with the infrastructure development it is meant to inspire, is needed as there frankly has been a lot of lip service to privacy compliance, subject access rights and little in the way of enforcement, access or real usability. Clearly regulators alone will not solve all of the challenges faced today. This Framework is designed to bridge these legal gaps.
* What has in fact happened is principles, guidelines, and regulations for fair information practices are not adhered to in the collection and use of personal information. Even when these are developed into law, the infrastructure for their use is almost non existent, limited to opt-in/out check boxes, and appeals to toothless privacy commissioners.
* The most functionally critical of rights, is the right of access, and control of ones own personal information. This right is the stalwart of autonomy, self-determination, and self motivation. An incredibly important right for community health and human development.
* Ultimately this MCAF is a framework for evolving the existing rights infrastructure to provide user driven access to information.
* As a use case Identity Trust CIC has picked CCTV as a long standing issue in privacy, rights and user access. Representing online and off line issues.
* This Use Case is also a very defined and practical use case that is a first step towards designing Master Control for individuals on the internet, dealing with Privacy Policies, and Terms Of Service.
* This use case is intended to illustrate the need for greater transparency, notice, and user involvement for more advance and sensitive information sharing activities that are now emerging in main stream society

Objectives:

This framework is intended to develop the individuals infrastructure for engaging with institutions
Developing individually driven access rights, making privacy visible, and providing a personal platform for control and commoditization of personal information.

Challenges:
One of the major challenges to developing master controller access has been the issues of identity, both proving that you are the identity of the subject that requires access, but also safe guarding the rights of the individual when using rights. Up until recently this hasnt been solved. In 2010 new R&D in digital identity now makes this framework possible.

Identity Trust Charter

2010-09-06T21:11:31Z

Purpose:

← Older revision		Revision as of 21:11, 6 September 2010
Line 5:		Line 5:
	=== Purpose ===		=== Purpose ===

-	This work group has been set up to develop the ~~[[Master \|~~Master Data Controller Access Framework (MCAF)]]. This Framework (contributed by Identity Trust CIC 06-10-2010) is used as a rights based framework for developing digital identity architecture.	+	This work group has been set up to develop the Master Data Controller Access Framework [[MCAF\|(MCAF)]]. This Framework (contributed by Identity Trust CIC 06-10-2010) is used as a rights based framework for developing digital identity architecture.

	The purpose of this work group is to organize a development community for this framework that can be used to launch, implement, and develop community interest applications and infrastructure. This work group encourages the formation of sub-working groups that use the framework for open development.		The purpose of this work group is to organize a development community for this framework that can be used to launch, implement, and develop community interest applications and infrastructure. This work group encourages the formation of sub-working groups that use the framework for open development.

Master

2010-09-06T21:10:06Z

New page

Identity Trust Charter

2010-09-06T21:04:57Z

Current Meeting Schedule:

← Older revision		Revision as of 21:04, 6 September 2010
(6 intermediate revisions not shown)
Line 5:		Line 5:
	=== Purpose ===		=== Purpose ===

-	~~Identity Trust is a working~~ group ~~that~~ has been [[~~gestating~~\| ~~gestating for 3 years~~]] ~~now~~. This ~~working group effort was started to develop~~ a framework for ~~the individual for [[Trust\|Trust and control]] in Identity Management~~.	+	This work group has been set up to develop the [[Master \|Master Data Controller Access Framework (MCAF)]]. This Framework (contributed by Identity Trust CIC 06-10-2010) is used as a rights based framework for developing digital identity architecture.

-	~~Today I am proud~~ to ~~announce~~ that the MCAF	+	The purpose of this work group is to organize a development community for this framework that can be used to launch, implement, and develop community interest applications and infrastructure. This work group encourages the formation of sub-working groups that use the framework for open development.
		+
		+	The MCAF is actively being developed to be able to input requirements for a digital standard in notice. The bulk of the work done here will be evolving Access and Notice infrastructure.
		+
		+	=== Background ===
		+
		+	Identity Trust is a working group that has been [[gestating\| gestating for since 2007]] as in preparing to be officially launched at the IIW 2010 in London on October 11th.
		+
		+	This working group effort was started to develop a framework for the individual for [[Trust\|Trust and control]] in Identity Management.

	=== Practices ===		=== Practices ===

-	~~=== Requirements of Participation and How to Join ===~~

-	~~Membership is open to anyone who is interested in putting the law~~ and ~~policy together~~ to ~~create~~ a ~~secure, user-centric identity legal framework~~.	+	There will be regular calls and workgroup use case submissions that will form the bulk of development practice. This WG intends to contribute to discussion of regulation and support work towards a digital standard of notice.

		+	This WG will interact with community, advocacy, academic, standard based, governmental, and industry efforts.
		+	(Updated list forth coming)

-	~~Anyone may join although the working group is not actively using a mailing list at this time. [if you are interested, please send an email~~ to ~~identitytrust@gmail.com]~~	+	=== Requirements of Participation and How to Join ===

-	~~If you are~~ interested in ~~getting more involved~~ and ~~participating in this proposed working group~~, ~~please email us and let us know~~.	+	Membership is open to anyone who is interested in putting the law and policy together to create a secure, user-centric identity legal framework.


-	~~Please feel invited to edit this wiki and add your name to~~ the ~~list of people who read this~~ mailing list, this ~~is the most important sponsorship of all~~. ~~All sponsorship would need~~ to ~~clearly enable the charter of this working group, including the principles which guide it. Sponsorship will be posted clearly on this wiki in the charter~~.	+	Anyone may join although the working group is not actively using a mailing list at this time.
		+	[if you are interested, please send an email to identitytrust@gmail.com]

	=== Licenses and/or Restrictions on Usage of Work Product ===		=== Licenses and/or Restrictions on Usage of Work Product ===
Line 29:		Line 39:

	Dependant on participation and volunteers/sponsorship, collaborative discussion and analysis will be summarised and disseminated for use in other projects. The resulting collaboration will be used to develop the principles of this working group.		Dependant on participation and volunteers/sponsorship, collaborative discussion and analysis will be summarised and disseminated for use in other projects. The resulting collaboration will be used to develop the principles of this working group.
		+
		+	The MCAF is also shared under Creative Commons License, although if the MCAF is used for profit purposes, license fee's may be applied.
		+
		+	<a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/3.0/"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-nc-sa/3.0/88x31.png" /></a><br /><span xmlns:dc="http://purl.org/dc/elements/1.1/" property="dc:title">(MCAF) Master Data Controller Access Framework</span> by <a xmlns:cc="http://creativecommons.org/ns#" href="http://www.identitytrustcic.org" property="cc:attributionName" rel="cc:attributionURL">Mark Lizar</a> is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/3.0/">Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License</a>.<br />Permissions beyond the scope of this license may be available at <a xmlns:cc="http://creativecommons.org/ns#" href="http://wiki.identitycommons.net/Identity_Trust_Charter" rel="cc:morePermissions">http://wiki.identitycommons.net/Identity_Trust_Charter</a>.

	=== Current Meeting Schedule ===		=== Current Meeting Schedule ===

-	There are no regular in person meetings. The main activity at this moment is ~~starting~~ this ~~working group anew~~.	+	There are no regular in person meetings. The main activity at this moment is finishing the draft and first use case of the Work Group. Once this has been review, this Charter Will be announced and invites sent for a face to face meeting at IIW 2010 in London.

	=== Current Deliverables and Milestones ===		=== Current Deliverables and Milestones ===

Gestating

2010-09-06T20:38:30Z

Created page with ''''Background''' - effort started at the 2006 IIW. - Based most on two sessions - One called the Identity Legal Framework, The Other Identity Trust. After an unncessful atte...'

New page

'''Background'''

- effort started at the 2006 IIW.
- Based most on two sessions - One called the Identity Legal Framework, The Other Identity Trust.

After an unncessful attempt to start this WG and have been waiting for Identity Company to become a formal organisation, and for the contribution of the Master Controller Access Framework (MCAF). The MCAF is focused to develop greater (more granular) access control to information for sharing, gaining access to information once it is shared, and most of all, transparency over the information sharing environment. Fundamentally an opt-in, mandatory preference approach, the MCAF is more than a default policy of control for the individual. The MCAF looks to address information sharing after disclosure and provide tools for providing a platform so that an individual can have the choice of trust when online.

Various ideas for work group focus include the development of control and trust metrics that are cross jurisdictional.

One proposal for this working group is to develop a single metric to measure if an individual has interpersonal or institutional control over personal information. Similarily there is a proposal to develop a metric for the quality and strength of transaprency in the use of identity management.

The purpose is to help support efforts that are creating an information sharing environment which enables people to manage identity, not environments that enable identity to manage people.

Identity Trust Charter

2010-09-06T20:34:57Z

Purpose:

← Older revision		Revision as of 20:34, 6 September 2010
Line 5:		Line 5:
	=== Purpose ===		=== Purpose ===

-	Identity Trust is a working group that has been gestating for 3 years now. ~~Over this time trust based research has been conducted in consent,~~ control ~~and confidence~~ in Identity ~~and Access~~ Management~~. This research is being applied here in the area of Identity and Trust~~.	+	Identity Trust is a working group that has been [[gestating\| gestating for 3 years]] now. This working group effort was started to develop a framework for the individual for [[Trust\|Trust and control]] in Identity Management.

-	~~The purpose of this application is~~ to ~~represent a sovereign policy and perspective of identity. With this focus propose activities or input~~ that ~~can be developed from this working group. Some guiding research references are listed below.~~	+	Today I am proud to announce that the MCAF
-		+
-	~~[[Trust\|Trust and control]] are interchangeable and in~~ the absence of trust there is control.' Although, 'Trust in fact is a deficiency of control that expresses itself as a desire to progress despite the inability to control.' '.. while control is reducible to trust, trust cannot be reducible to control'. (Cofta 2007:p.28)	+
-		+
-	~~Recent research indicates that there is two different types of trust that need to be operational in society. There is interpersonal trust and there is institutional trust.~~	+
-		+
-	Morrone Tontoranelli, et al., produced an OECD Statistics Working Paper in 2009, to explore the value of trust in society, illustrating that interpersonal trust and institutional trust are different concepts that need to be made operational in different ways. The need for distinguishing them lies in the fact that they enter people’s live in different ways, and that they have different effects on various dimensions of progress.	+
-		+
-	"Trust is one of the dimensions of the framework to measure the progress of societies proposed by the OECD Global Project. In this framework, trust is considered as a key input into human well being because it indicates the willingness of individuals to co-operate with others. As underlined in this paper trust has emerged as one of the best available measures of social capital and the evidence in this paper shows that trust displays close associations with a number of other dimensions of social progress." (Morrone, Tortoraneli, et al, 2009:p.31)	+
-		+
-		+
-	~~----- Stay Tuned -----~~	+
-		+
-	~~We are currently working towards contributing the Master Controller Access Framework (~~MCAF) into this working group. The MCAF is focused on greater (more granular) access control to information for sharing, gaining access to information once it is shared, and most of all, transparency over the information sharing environment. Fundamentally an opt-in, mandatory preference approach, the MCAF is more than a default policy of control for the individual. The MCAF looks to address information sharing after disclosure and provide tools for providing a platform so that an individual can have the choice of trust when online.	+
-		+
-	~~Various ideas for work group focus include the development of control and trust metrics that are cross jurisdictional.~~	+
-		+
-	One proposal for this working group is to develop a single metric to measure if an individual has interpersonal or institutional control over personal information. Similarily there is a proposal to develop a metric for the quality and strength of transaprency in the use of identity management.	+
-		+
-	~~The purpose is to help support efforts that are creating an information sharing environment which enables people to manage identity, not environments that enable identity to manage people.~~	+

	=== Practices ===		=== Practices ===

Trust

2010-09-06T20:32:26Z

Created page with ''Trust and control are interchangeable and in the absence of trust there is control.' Although, 'Trust in fact is a deficiency of control that expresses itself as a desire to pro...'

New page

'Trust and control are interchangeable and in the absence of trust there is control.' Although, 'Trust in fact is a deficiency of control that expresses itself as a desire to progress despite the inability to control.' '.. while control is reducible to trust, trust cannot be reducible to control'. (Cofta 2007:p.28)

Recent research indicates that there is two different types of trust that need to be operational in society. There is interpersonal trust and there is institutional trust.

Morrone Tontoranelli, et al., produced an OECD Statistics Working Paper in 2009, to explore the value of trust in society, illustrating that interpersonal trust and institutional trust are different concepts that need to be made operational in different ways. The need for distinguishing them lies in the fact that they enter people’s live in different ways, and that they have different effects on various dimensions of progress.

"Trust is one of the dimensions of the framework to measure the progress of societies proposed by the OECD Global Project. In this framework, trust is considered as a key input into human well being because it indicates the willingness of individuals to co-operate with others. As underlined in this paper trust has emerged as one of the best available measures of social capital and the evidence in this paper shows that trust displays close associations with a number of other dimensions of social progress." (Morrone, Tortoraneli, et al, 2009:p.31)

Identity Trust Charter

2010-09-06T20:32:13Z

← Older revision		Revision as of 20:32, 6 September 2010
Line 9:		Line 9:
	The purpose of this application is to represent a sovereign policy and perspective of identity. With this focus propose activities or input that can be developed from this working group. Some guiding research references are listed below.		The purpose of this application is to represent a sovereign policy and perspective of identity. With this focus propose activities or input that can be developed from this working group. Some guiding research references are listed below.

-	'Trust and control are interchangeable and in the absence of trust there is control.' Although, 'Trust in fact is a deficiency of control that expresses itself as a desire to progress despite the inability to control.' '.. while control is reducible to trust, trust cannot be reducible to control'. (Cofta 2007:p.28)	+	[[Trust\|Trust and control]] are interchangeable and in the absence of trust there is control.' Although, 'Trust in fact is a deficiency of control that expresses itself as a desire to progress despite the inability to control.' '.. while control is reducible to trust, trust cannot be reducible to control'. (Cofta 2007:p.28)

	Recent research indicates that there is two different types of trust that need to be operational in society. There is interpersonal trust and there is institutional trust.		Recent research indicates that there is two different types of trust that need to be operational in society. There is interpersonal trust and there is institutional trust.

Identity Landscape

2010-09-04T14:23:37Z

Groups, Communities, Projects:

← Older revision		Revision as of 14:23, 4 September 2010
(One intermediate revision not shown)
Line 51:		Line 51:

	The ITU is a technical standards body for telecommunications-related protocol standards following international standardization processes. The objective of the Focus Group is to facilitate the development of a generic Identity Management framework, by fostering participation of all telecommunications and ICT experts on Identity Management. http://www.itu.int/ITU-T/studygroups/com17/fgidm.		The ITU is a technical standards body for telecommunications-related protocol standards following international standardization processes. The objective of the Focus Group is to facilitate the development of a generic Identity Management framework, by fostering participation of all telecommunications and ICT experts on Identity Management. http://www.itu.int/ITU-T/studygroups/com17/fgidm.
		+
		+	=== Kantara Initiative ===
		+
		+	Kantara Initiative is a robust and well-funded focal point for collaboration to address the issues shared across the identity community: Interoperability and Compliance Testing; Identity Assurance; Policy and Legal Issues; Privacy; Ownership and Liability; UX and Usability; Cross-Community Coordination and Collaboration; Education and Outreach; Market Research; Use Cases and Requirements; Harmonization; and Tool Development.

	=== Kerberos Consortium ===		=== Kerberos Consortium ===
Line 58:		Line 62:
	=== Liberty Alliance ===		=== Liberty Alliance ===

-	An industry association for the development and promotion of federated identity standards. Established in 2001, it has focused mostly on intra and inter-enterprise scenarios. http://projectliberty.org.	+	An industry association for the development and promotion of federated identity standards. Established in 2001, it has focused mostly on intra and inter-enterprise scenarios. http://projectliberty.org. UPDATE - As of June 2009, the work of the Liberty Alliance is transitioning to the Kantara Initiative.

	=== Oath ===		=== Oath ===

Stewards Council Telecom: 2010 September 1

2010-09-01T16:20:28Z

Attending:

← Older revision		Revision as of 16:20, 1 September 2010
(3 intermediate revisions not shown)
Line 2:		Line 2:

	== Attending ==		== Attending ==
-		+	* Mary Ruddy
		+	* Dean Landsman
		+	* Drummond Reed
		+	* Kaliya Hamlin

	== Agenda ==		== Agenda ==

Stewards Council Telecom: 2010 August 4

2010-09-01T14:38:17Z

← Older revision		Revision as of 14:38, 1 September 2010
Line 9:		Line 9:
	*Drummond Reed		*Drummond Reed
	*Dan Perry		*Dan Perry
		+	*Paul Trevithick
		+	*Aaron Titus

	== Agenda ==		== Agenda ==
Line 29:		Line 31:

	== Minutes ==		== Minutes ==
		+	*Mary: I’ve added the call-in number to the agenda page, so it is easier to find.
		+	*Mary: While we are waiting for people to join, we can talk about some tactical items. We have a new, clean, virtual server to which to move the identity commons blog. The person who is doing the moving is having trouble finding the virus in the existing blog so that he doesn’t inadvertently move it to the new location for the blog.
		+	*John: With viruses for WordPress, the vector is normally in the data. It is entirely driven out of MySQL.
		+	*Dan: Will try to move it to new machine.
		+	*Dan: I thought we were moving to Drupal.
		+	*Dan: There was a change of plans to make updates easier.
		+	*Dan: Send me the information so that we can charge the new hosting fee to my credit card.
		+	*Mary: We can handle this offline.
		+	*Dan: We should also upgrade the budget.
		+	*Mary: The new server is already in the budget.
		+	*Mary: John, do you know who can help Stas find the virus?
		+	*John: Not off hand. Pam probably would have the best notion.
		+	*Mary: Pam is on vacation.
		+	*Kaliya: Pam will be willing to help.
		+	*Mary: So I have a second action item to follow-up with Pam.
		+	*Mary: The general instructions are to move all of the blog to the new server, except the virus.
		+	*Mary: Kaliya can you tell us about IIW-East?
		+	*Kaliya: We are having our first IIW-East. It is Sep 9-10 in DC. And now we need people to register. That is my job today, to work on registration and blog posts.
		+	*Mary: People should put references [to IIW-East] on their own blogs and websites
		+	*John: I booked my airplane ticket yesterday.
		+	*Kaliya: Are the Protiviti people registered?
		+	*John: Debbie and I communicated yesterday. The NIH-Protiviti people are coming.
		+	*Aaron: I was going to send out emails on this. I went to Identity Commons and saw nothing there.
		+	*Mary: I put something there yesterday.
		+	*Kaliya: You can point them to http://www.internetidentityworkshop.com/ It has the links for all three of the next IIWs
		+	*Mary: That looks great!
		+	*Kaliya: If you clink on the DC button, it takes you to the DC registration.
		+	*Kaliya: I will make another set of badges (web logo buttons) and hook them to the wiki.
		+	*Kaliya: Phil is also worried about Europe. I’m less, as we have a per person site fee that includes food.
		+	*Dan: Will IIW Europe get the un-conference approach?
		+	Kaliya: Yes. They have been asking for it as current events haven’t been letting people get work done. It is just one day in Europe.
		+	*Dan: Do we have testimonials from attendees?
		+	*Kaliya: No. We were much better about collection those in the beginning. We should probably ask the IIW-Europe organizer to do this. In a way, we are trying to do this with the DC invite by listing key people who are registered.
		+	*Dan: Marketing is everything. If we could give them a short, tweetable, and re-tweetable testimonial, that would be great.
		+	*Dan: Are we doing a pure un-conference, or are we still doing a keynote?
		+	*Kaliya: In both cases, I will give an introduction talk about the context of IIW. There is another question about what IIW11 will become. We now have people looking for information about implementations. In the beginning, we were just talking about the edge. Now that the conference has grown and protocols have matured, don’t want to leave people out.
		+	*Aaron: I was at the White House last week to talk about NSTIC, and asked if they would participate in an open forum. We could make this a forum for them to explain NSTIC. If we could turn it into that, we already have an active coalition to engage.
		+	*Kaliya: Clearly NSTIC is important. That is important. I just don’t want it to be a whole morning of talking heads.
		+	*Aaron: We are sold about what an un-conference is.
		+	*Kaliya: I’m open to that idea. And I think Phil would be to. Can we have a call later today about what the invitation should be? Want it to be a forum for existing communities to move the ball forward and that is clearly one of them. It should help with sponsorship too.
		+	*Aaron: Shoot me an email. I’m flexible today.
		+	*Dean: I’m on the call.
		+	*Kaliya: How is the VRM Summit coming?
		+	*Dean: On Aug 26-27, there will be a VRM-CRM Conference at Pound Hall at Harvard Law. We are looking at this to be an event where people from the CRM and commercial side see how we can work together. We are working very hard on that. There is a very big CRM event going on in NY talking about social CRM, which is similar to VRM. It is an exciting and active and interesting moment. We’re matriculating from being only a Berkman entity to being its own self contained entity. Exciting times in VRM world.
		+	*Kaliya: I’ll send you the note I sent Doc. Can IIW be seen as a forum in London for showing how VRM is key and not just for freaks? There is in interesting dance between VRM being about identity. I don’t think CRM people will be coming to IIW. How do we make sure the VRM community is activated to come to IIW London.
		+	*Drummond: I think that is a question best directly posed to the people who are active there. While VRM is its own continuing entity, it is a close cousin. There should be cohesion between VRM and IIW.
		+	*Drummond: I apologize for joining late. If the topic is IIW and VRM, are there any conclusions being reached?
		+	*Dean: Adriana, Ian, I don’t think any of them would have a problem with IIW.
		+	*Kaliya: I just want to name it right so there is cross registration.
		+	*Kaliya: Drummond do you want to give us a report on your stuff?
		+	*Drummond: I’m juggling the balls for ICF and OIX and the rest of my time I working on the creation of the PDS ecosystem. Some of it in conjunction with Kaliya and everyone else who wants to do that.
		+	*Kaliya: Is there anything in particular you think is working on the interop?
		+	*Mary: That is an OSIS thing.
		+	*Drummond: When I’m wearing my IC hat, hat, it was really good. It was more successful at RSA, not just because the bits interoped. It was a larger community, multiple protocols and multiple LOA, so it highlighted more issues and had better visibility than at RSA; but Mary is more closely attuned.
		+	*John: It more closely related to things we would actually use. Pretty much none of it worked perfectly, and that was good. Now we have tasks for vendor to focus on to that next time it will work better.
		+	*Mary: The visibility was much higher. There was a panel to debrief after the interop, and there were multiple mentions in other presentations.
		+	*John: The people who came to the event saw a shiny thing.
		+	Mary: We also used the event as a forcing function for the creation of John’s Federation Interoperability working group at Kantara to set the standard for multi- protocol meta-data interoperability.
		+	*John: I will try to keep some of the endpoints up. I’ve talked with some of the vendors. They are not interested in having OSIS host some SAML endpoint, as this is politically sensitive.
		+	*Mary: Please explain.
		+	*John: Kantara is vendors certifying themselves as good. Have test endpoints that are the other vendors. Their testing is by the vendors for the vendors. So it makes it difficult to do test endpoints for negative testing. There is interest in permanent test endpoints, that is, open source tests available on the internet. This will enable Kantara to test more. So this isn’t competitive. It is positioned to be complementary, i.e. open source
		+	*Mary: It would be great if you can provide some additional endpoints.
		+	*Drummond: John do you have any thoughts on how this can integrate OSIS more with what Kantara wants to do, testing test suites and that sort of thing?
		+	*John: The conversation I’m having is with Joni and the IOP. If we can get options tests, they might be included in Kantara’s September round of testing. Everyone sees it as useful. Everyone wants someone else to pay for it. I need to see what I can scourge together. I lobbied MS for this.
		+	*Mary: How much space do you need?
		+	*John: I need a windows machine.
		+	*Mary: All mine are Linux.
		+	*John: I’m leaning on MS to provide free hosting. For the Linux stuff, I can probably tap a university. I’m going to try to get OIDF to pay Andrew to clean up and build test for them as well. That is pretty much what is up with OSIS.
		+	*John: I take it that the dates for IIW 11 are now set in stone?
		+	*Kaliya: Why are you asking?
		+	*John: Now I see that they were tentative and now are not tentative. Just wanted to make sure so I can book flights.
		+	*Kaliya: Yes. It is set.
		+	*Kaliya: I’m having an internal debate with myself. Should I reduce it to 2 days and leave a day for other organizations to have meetings?
		+	*Drummond: That is interesting. It acknowledges that there are more and more projects that are far enough along that they need their own dedicated time.
		+	*Drummond: That is interesting Kaliya.
		+	*Dean: Are there any updates on Washington? I may have missed the beginning.
		+	*Mary: Yes. We are moving forward with planning for the first IIW-East in DC on September 9-10.
		+	*Kaliya: The URL for registration is http://www.internetidentityworkshop.com This is the URL for registering for all the IIW’s
		+	*Dean: The world we live in is familiar and immediate to us, but to others it isn’t . We need to constantly remind and educate people.
		+	*Dean: This website is nicely done. We should do an IIW story. We could sell a lot of IIW t-shirts.
		+	*Dean: And do it with an outsourcer that creates the merchandise as it is ordered.
		+	*Kaliya: I’m glad you like the site. I will work more to promote it in the community.
		+	*Drummond: I found it very helpful also.
		+	*Kaliya: Our time is up. Mary and I are excited that so many people attended the call in August [vacation time] when we didn’t bug people to come.
		+	*Paul: I’m here also
		+	*Chris: And so is Chris Reynolds.
		+	*Mary: Other items. I’m still waiting for the latest draft of the budget.
		+	*Dan: I’ve been extracting the data. I’ll send it by Friday.
		+	*Kaliya: That was all I had.
		+	*Mary: The other agenda item is the discussion period for the new "The Givotovsky "New Digital Deal" Working Group has ended.
		+	*Dean: I have to go. Can you open the voting for the Givotovsky working group today?
		+	*Mary: Yes, I can do it today.
		+	*Dean: Please do. I want to voice my support.
		+	*Kaliya: Do you have anything else?
		+	*Silence
		+	*Kaliya: Thank you everyone.