| 40 min | Discuss work backlog priorities for CR v1.1 | David | Consent Receipt v1.1 Work Backlog On Wed, May 10, 2017at 1:56 PM, David Turner <david.turner@voltagegate.com> wrote: I’ve been reviewing the input for v1.1 and I’ve grouped the issues into 5 broad categories to help focus discussions. - Terminology
- Reconcile terms from various ISO specs (e.g., 29100, 29184) with other significant sources (e.g., GDPR).
- We need to be clear that the CR spec is not the authoritative source for definitions and be clear that implementers must follow the appropriate definitions according to their relevant jurisdictions.
- Data model
- What is the proper relationship between different fields? For example, in the v1 spec there is only one dataController; and purpose, purposeCategory and piiCategory are subordinate to a service. What happens when we allow multiple dataControllers? Do we then make services subordinate to dataControllers, or the other way around? I’ve attached two views of the current JSON schema. One is pseudo-ERP and the other an expandable tree graph.
- New fields
- E.g., duration of consent, retention period
- Some of these suggested fields raise the question of how much of a policy’s details should be repeated in the CR. What is the reason for including the field? Is it just for the implementer, for interchange/interop, for the end user, for regulatory compliance?
- Field semantics/syntax
- Some fields need more guidance and possibly specific data types. (e.g., jurisdiction, policyURL, termination)
- Purpose, purposeCategory, piiCategory, primaryPurpose
- A big ol’ discussion all by itself.
From David: CR Schema v1_0_0.html From David: CR-1_0_0 data model v1 (1).gif |
