Difference between revisions of "Persistent Connection Management"
From MgmtWiki
(→Full Title) |
(→Solution) |
||
| Line 28: | Line 28: | ||
|pointer to the terms given me by this connex || machine readable privacy policy, ToS etc. | |pointer to the terms given me 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 me | ||
Revision as of 17:03, 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 me at this site | 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 my data (as reported to the connex) | may not belong here but in stipulations or terms |
| date deleted (or disabled) | |
| status | (ok, dangerous(perhaps more detail here), disabled) |
| pointer to stipulations i have given this connex | eg consents |
| pointer to the terms given me 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 me
| 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? |
