/
2014-01-30 Meeting Notes - Schema & API

2014-01-30 Meeting Notes - Schema & API

Owned by Mark Lizar (Unlicensed)
Last updated: Jan 30, 2014

Date

Jan 30, 2014

Attendees

Goals

  • - Updates

    • need to update the call details on the CISWG page. 

  • API - creating an API with the spreadsheet - (volunteers to help Reuben welcome)

  • Schema - Making a first version - scope and focus

Discussion Items

TimeItemWhoNotes
15 minProviding update on SchemaMary
  • Reviewed the IETF email Schema, DNT Track Schema, and SWIFT schema? 
  • Swift schema looks like a form
  • DNT Track schema was an interesting example -
  • We can make a little schema for next saturday
  • But - it looks like we will need to go through a process similar to the the DNT track process with 100 people involved and may take a year to two years to complete
  • Schema that move to standards are remarkably similar in process
 Discussing the APIMary & Reuben
  • are we going to get the laws behind the legal map
  • for each field is there going to be a paragraph behind the references?
  • thinking of having a json format, read only API?
  • Chris Entity Relationship Modelling - Abstraction based data modelling. human readable build – with a bunch of post-it notes - and if done right you end up with a bunch of statements about the relationship. Can use this make the data-model than everyone can buy into this. Best approach is whiteboard and post-its.
  • Do we have the schema in the consent map already? We can make something up and have a draft? Or example to get us going?
  • We need buy in.. dont want to put much down.. before we include enough parties.
  • Tom working with the API -
  • Reuben suggest that we start a repo on github and start working on it now.
 Discussing the SchemaMark
  • To start with the main categories that are the most consistent across all jurisdictions for implicit consent and sensitive PII is to be required to provide a privacy (governing) policies, as per the openness principle which is in all the jurisdictions. The requirement to provide a purpose for the consent (both of which are required for people to know what they are consenting to) and the contact and address of the data controller.

Action Items

  • Mark Lizar (Unlicensed) to fix up the consent map columns
  • @   open notice github/bit bucket – > use git hub. 
    • Tom and Mark to do
  • @mark follow up on the consent map with Andrew, Marianna, Innes, 
  • Former user (Deleted) going to ask Hastings Law students to get involved on the consent map
  • Former user (Deleted) to work on simple API with support from Tom and maybe Chris