Difference between revisions of "Persistent Connection Management"
From MgmtWiki
(→Solution) |
(→Solution) |
||
| Line 10: | Line 10: | ||
|ID of web enterprise || might be a URL or similar | |ID of web enterprise || might be a URL or similar | ||
|- | |- | ||
| − | |ID of | + | |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 18: | Line 18: | ||
|date updated || | |date updated || | ||
|- | |- | ||
| − | |date authorized to hold | + | |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 | |date deleted (or disabled) || after this date this connection must not be used for any new transactions | ||
| Line 24: | Line 24: | ||
|status ||(ok, dangerous(perhaps more detail here), disabled) | |status ||(ok, dangerous(perhaps more detail here), disabled) | ||
|- | |- | ||
| − | |pointer to stipulations | + | |pointer to stipulations user gave to this connex || eg consents |
|- | |- | ||
| − | |pointer to the terms given | + | |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 | |payment authz || Name any payment methods that exist as JSON object | ||
| Line 32: | Line 32: | ||
|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 | + | 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 | ||
Revision as of 17:06, 13 July 2019
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 |
| 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? |
