Difference between revisions of "Persistent Connection Management"

From MgmtWiki
Jump to: navigation, search
(Solution)
(Solution)
 
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
==Full Title==
 
==Full Title==
 +
Management of the [[Persistent]] connections that exist between user and [[Enterprise]]s on the web.
  
 
==Solution==
 
==Solution==
Line 9: Line 10:
 
|ID of web enterprise || might be a URL or similar
 
|ID of web enterprise || might be a URL or similar
 
|-
 
|-
|ID of me at this site || this allows a user to have more than one connex with a web site
+
|ID of user at this site (sub) || this allows a user to have more than one connex with a web site
 
|-
 
|-
 
|Friendly name of the above pair || also called a connex
 
|Friendly name of the above pair || also called a connex
Line 17: Line 18:
 
|date updated ||
 
|date updated ||
 
|-
 
|-
|date authorized to hold my data (as reported to the connex) || may not belong here but in stipulations or terms
+
|date authorized to hold user data (as reported to the connex) || may not belong here but in stipulations or terms
 
|-
 
|-
|date deleted (or disabled) ||
+
|date deleted (or disabled) || after this date this connection must not be used for any new transactions
 
|-
 
|-
 
|status  ||(ok, dangerous(perhaps more detail here), disabled)
 
|status  ||(ok, dangerous(perhaps more detail here), disabled)
 
|-
 
|-
|pointer to stipulations i have given this connex || eg consents
+
|pointer to stipulations user gave to this connex || eg consents
 
|-
 
|-
|pointer to the terms given me by this connex || machine readable privacy policy, ToS etc.
+
|pointer to the terms given user by this connex || machine readable privacy policy, ToS etc.
 
|-
 
|-
|payment authz ||
+
|payment authz || Name any payment methods that exist as JSON object
 
|-
 
|-
|purpose (commercial, health, financial) ||
+
|purpose || (commercial, health, financial)
 
|}
 
|}
The following fields may be in the above schema, or a separate one keyed by the ID of me
+
The following fields may be in the above schema, or a separate one keyed by the ID of user
 
{| class="wikitable"
 
{| class="wikitable"
 
| Field Name ||  notes
 
| Field Name ||  notes
 +
|-
 +
|sub || key if this is in a separate record
 
|-
 
|-
 
|key protection or CSP id || where the private key is to be found
 
|key protection or CSP id || where the private key is to be found
 
|-
 
|-
|Key ID of my public key  ||NOT THE PUBLIC KEY - perhaps belongs in the above key?
+
|Key ID of my public key  || this may be the public key only if in a separate file
 +
|-
 +
|Date created|| seconds in the epoch
 +
|-
 +
|Date retired|| seconds in the epoch - NULLABLE
 +
|-
 +
|Purposes|| JSON object (see KI CR)
 
|-
 
|-
 +
|[[Generally Accepted Privacy Profiles]]|| list of purposes for which private information may be released.
 
|}
 
|}
 +
* CSP = [[Cryptographic Service Provider]]
  
 
==References==
 
==References==
 
<references />
 
<references />
 
===External Resources===
 
===External Resources===
[[Category:Identifier]]
+
 
[[Category:Privacy]]
+
 
 +
[[Category: Identifier]]
 +
[[Category: Networking]]
 +
[[Category: Privacy]]

Latest revision as of 09:48, 24 September 2024

Full Title

Management of the Persistent connections that exist between user and Enterprises on the web.

Solution

Table of data elements for a personal store of Persistent Identifiers.

Field Name notes
ID of web enterprise might be a URL or similar
ID of user at this site (sub) this allows a user to have more than one connex with a web site
Friendly name of the above pair also called a connex
date created
date updated
date authorized to hold user data (as reported to the connex) may not belong here but in stipulations or terms
date deleted (or disabled) after this date this connection must not be used for any new transactions
status (ok, dangerous(perhaps more detail here), disabled)
pointer to stipulations user gave to this connex eg consents
pointer to the terms given user by this connex machine readable privacy policy, ToS etc.
payment authz Name any payment methods that exist as JSON object
purpose (commercial, health, financial)

The following fields may be in the above schema, or a separate one keyed by the ID of user

Field Name notes
sub key if this is in a separate record
key protection or CSP id where the private key is to be found
Key ID of my public key this may be the public key only if in a separate file
Date created seconds in the epoch
Date retired seconds in the epoch - NULLABLE
Purposes JSON object (see KI CR)
Generally Accepted Privacy Profiles list of purposes for which private information may be released.

References

External Resources