Date
Mar 07, 2016
Attendees
Goals
- Mark Gave update on Kantara Changes
- Mark is now BOT Liaison
- Colin Wallis is now the Executive Director
- Kantara is moving out the IEEE umbrella as independant non-profit
- Kantara can also be a and SDO
- Leadership Council Elections Happening
- , Mary suggested we list a things we needed or want to do - agree the process, schedule the work and then get through it.
- ie. (for the IDESG group)
- need to be compliance with policy
- consistent set of definitions
- making things are consistent
- how should we check the spec.
- ie. (for the IDESG group)
- Mark - we learned alot but that we need to clarify objectives and scope to make the work easier, this last bit of work really clarified this
- Mary suggested then we schedule these items in per week and cover them regardless who comes to get it finished.
- Mark suggests schedule
- scope and objective
- table review
- terms
- guidance as we go along and finish
- Knowledge base/appendix
Mark suggest that the specification should have
Preamble - why a spec is needed
Objective
- i.e.
- what a spec should do
Scope
- each field should have guidance for the specific elements, for providing a record, how to present the record, the timing of the record, the format and order of fields and what is in them, linking the fields and linking to documents, adding additional elements
- each field should have legal reference or requirement
- guidance for the fields and the specification .
Terms
- list of definitions
Table
- the table we have now - needs reviewing and comments
Guidance for Consent
- suggesting adding consent guidance documentation for fields and for consent receipts/records
Knowledge Base - (similar appendix)
- cover purpose categories
- action; Mark Lizar (Unlicensed) to propose refined objectice and scope on list for discussion
Discussion Items
| Time | Item | Who | Notes |
|---|---|---|---|