Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version 3

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

2016-11-18

Attendees

Voting

Non-Voting

...

 

Info
titleQuorum Status
Meeting achieved did not achieve quorum.

 

 

Info
titleVoting participants

Participant Roster (2016) - Quorum is 4 of 7 as of 2016-10-06

Iain Henderson, Mary Hodder, Harri Honko, Mark Lizar, Jim Pasquale, John Wunderlich, Andrew Hughes

Discussion Items

Not enough attendees - will revert to list for discussion

 

 

TimeItemWhoNotes
10 mins
  • Roll call
  • Agenda bashing
  • Meeting minutes approval
Former user (Deleted)

 

25 minFormer user (Deleted)
  • Based on feedback from implementors, there are some issues that should be addressed for CR v1.0:
    v1
    • Conformance is missing ; Major schema change to add validation. (Samuli can explain)
    • ‘PII Principle ID” is used without reference or definition. I assume that this is the data subject (which seems like a more intuitive name). PII Principle. i.e., the individual's name is missing.
    • I think you’ll need an array of strings to name multiple third parties.
    • We need an array for multiple controllers in json – this is suggested in the spec but no array is available. 
    • Mark Added - "Public Key should be in Data Controller section"
    • Mark Added "Add Data Retention Field as suggested in v.0.9.3” 
    v1.x
    • Need an explanation of the relationship between the elements.
    • publicKey: currently string, should this be JWK object? 
    • collectionMethod: table says type is object, schema says type is string, I guess string is correct
    • Consent type - requests for both content and JSON structure
    • Purpose termination / data retention
Former user (Deleted) 

 

CR Spec publication schedule

...