Data Controller - Revision history

Tom: /* Other Materiel */

2025-08-28T21:38:04Z

‎Other Materiel

Tom: /* Problems */

2024-08-31T00:27:37Z

‎Problems

Tom: /* Problems */

2024-08-31T00:05:52Z

‎Problems

Tom: /* Problems */

2024-08-30T23:48:23Z

‎Problems

Tom: /* Context */

2024-08-30T23:41:20Z

‎Context

Tom: /* References */

2021-02-14T17:37:51Z

‎References

Tom: /* Problems */

2021-02-14T17:31:03Z

‎Problems

Tom: /* Problems */

2021-02-14T17:30:24Z

‎Problems

Tom: /* Problems */

2021-02-14T17:26:48Z

‎Problems

Tom: /* Solutions */

2021-02-14T17:20:47Z

‎Solutions

@@ Line 25: / Line 25: @@
 ===Other Materiel===
 * The wiki on [[Data Controller Options]] attempts to define a few of the ways that a [[Data Controller]] might give the required level of control.
 [[Category:Glossary]]
 [[Category:Privacy]]

@@ Line 12: / Line 12: @@
 * Even where the user has legal control of their own data, legal limitation are often imposed on the retention of that data by an entity that uses that a data in actions that are controlled by laws. Examples of this sort of entity are financial transactions and healthcare.
 * The above two examples of exclusions from data protection regulations are part of the 40 exclusions included in the GDPR. One result is the user privacy is primarily a legal exercise that requires high-priced legal opinions to help the [[Data Controller]] determine its obligations to the user and to the state.
-* Much of the activity about improving [[Privacy]] for [[[User Private Information]] has focus strictly on the data handling. For example a new effort start in the IEEE Standards Association in 2024 on [https://ieee-sa.imeetcentral.com/cybersecurityfornextgen/doc/WzIsODI0OTI1Mzld/w-CyberSecurityForNextGenerationConnectivitySystems Cyber Security For Next Generation Connectivity Systems]. This has done little to improve users privacy before that and there is low expectation that a data oriented procedure will do much better in the future.
+* Much of the activity about improving [[Privacy]] for [[User Private Information]] has focus strictly on the data handling. For example a new effort start in the IEEE Standards Association in 2024 on [https://ieee-sa.imeetcentral.com/cybersecurityfornextgen/doc/WzIsODI0OTI1Mzld/w-CyberSecurityForNextGenerationConnectivitySystems Cyber Security For Next Generation Connectivity Systems]. This has done little to improve users privacy before that and there is low expectation that a data oriented procedure will do much better in the future.
 ==Solutions==

@@ Line 12: / Line 12: @@
 * Even where the user has legal control of their own data, legal limitation are often imposed on the retention of that data by an entity that uses that a data in actions that are controlled by laws. Examples of this sort of entity are financial transactions and healthcare.
 * The above two examples of exclusions from data protection regulations are part of the 40 exclusions included in the GDPR. One result is the user privacy is primarily a legal exercise that requires high-priced legal opinions to help the [[Data Controller]] determine its obligations to the user and to the state.
-* Much of the activity about improving [[Privacy]] for [[User Private Data]] has focus strictly on the data handling. For example a new effort start in the IEEE Standards Association in 2024 on [https://ieee-sa.imeetcentral.com/cybersecurityfornextgen/doc/WzIsODI0OTI1Mzld/w-CyberSecurityForNextGenerationConnectivitySystems Cyber Security For Next Generation Connectivity Systems]. This has done little to improve users privacy before that and there is low expectation that a data oriented procedure will do much better in the future.
+* Much of the activity about improving [[Privacy]] for [[[User Private Information]] has focus strictly on the data handling. For example a new effort start in the IEEE Standards Association in 2024 on [https://ieee-sa.imeetcentral.com/cybersecurityfornextgen/doc/WzIsODI0OTI1Mzld/w-CyberSecurityForNextGenerationConnectivitySystems Cyber Security For Next Generation Connectivity Systems]. This has done little to improve users privacy before that and there is low expectation that a data oriented procedure will do much better in the future.
 ==Solutions==

@@ Line 9: / Line 9: @@
 ==Problems==
-*The term [[Data Controller]], is not helpful in understanding the practical consequences of the legislation putting the onus on the data controller to determin which legal jurisdition applies and what obligations apply to them.
+*The term [[Data Controller]], is not helpful in understanding the practical consequences of the legislation putting the onus on the data controller to determine which legal jurisdiction applies and what obligations apply to them.
-* Even where the user has legal control of their own data, legal limitiation are often imposed on the retention of that data by an entity that uses thata data in actions that are controlled by laws. Examples of this sort of entity are finacial transactions and healthcare.
+* Even where the user has legal control of their own data, legal limitation are often imposed on the retention of that data by an entity that uses that a data in actions that are controlled by laws. Examples of this sort of entity are financial transactions and healthcare.
-* The above two examples of exclusions from data protection regulations are part of the 40 exclusions included in the GDPR. One result is the user privacy is primarily a legal exercise that requires high-priced legal opinons to help the [[Data Controller]] determine its obligations to the user and to the state.
+* The above two examples of exclusions from data protection regulations are part of the 40 exclusions included in the GDPR. One result is the user privacy is primarily a legal exercise that requires high-priced legal opinions to help the [[Data Controller]] determine its obligations to the user and to the state.
 ==Solutions==

@@ Line 3: / Line 3: @@
 ==Context==
-*The [[GDPR]] uses the term term liberally but never defines it.
+* The [[GDPR]] uses the term term liberally but never defines it.
-*Several "Member States" of the EU have defined the [[GDPR]] terms, for example Ireland.<ref>Irish Data Protection Commission, ''Are you a "data controller"?'' https://www.dataprotection.ie/docs/Are-you-a-Data-Controller/y/43.htm</ref>
+* Several "Member States" of the EU have defined the [[GDPR]] terms, for example Ireland.<ref>Irish Data Protection Commission, ''Are you a "data controller"?'' https://www.dataprotection.ie/docs/Are-you-a-Data-Controller/y/43.htm</ref>
 ==Problems==

@@ Line 20: / Line 20: @@
 ==References==
+<references />
 [[Category:Glossary]]

← Older revision		Revision as of 17:26, 14 February 2021
Line 9:		Line 9:

	*The term [[Data Controller]], is not helpful in understanding the practical consequences of the legislation putting the onus on the data controller to determin which legal jurisdition applies and what obligations apply to them.		*The term [[Data Controller]], is not helpful in understanding the practical consequences of the legislation putting the onus on the data controller to determin which legal jurisdition applies and what obligations apply to them.
		+	* Even where the user is legal control of their own data, legal limitiation are often imposed on the retention of that data by an entity that uses thata data in actions that are controlled by laws. Examples of this sort of entity are finacial transactions and healthcare.

	==Solutions==		==Solutions==

@@ Line 11: / Line 11: @@
 ==Solutions==
-In this wiki we will use two terms that together seem to meet most definitions of [[Data Controller]] and more context to discuss the practical solutions.
+In this wiki we will use two terms that together seem to meet most definitions of [[Data Controller]] and provide more context to discuss the practical solutions.
 #A [[Identifier or Attribute Provider]] is the source of [[User Information]] in any covered transaction on the internet.
 #A [[Relying Party]] is the sink of [[User Information]] in any covered transaction on the internet.