| Time | Item | Who | Notes |
|---|
| 15 min | Providing update on Schema | Mary | - 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 API | Mary & 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 Schema | Mark | - 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.
|