Difference between revisions of "Persistent Connection Management"
From MgmtWiki
(→Solution) |
(→External Resources) |
||
Line 54: | Line 54: | ||
<references /> | <references /> | ||
===External Resources=== | ===External Resources=== | ||
− | [[Category:Identifier]] | + | |
− | [[Category:Privacy]] | + | |
+ | [[Category: Identifier]] | ||
+ | [[Category: Privacy]] |
Revision as of 12:52, 8 October 2022
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. |