Versions Compared

Key

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

...

Attendees

Goals

  • Mark Gave : update on Kantara Changes
    • Mark is now BOT Liaison
    • Colin Wallis is now the Executive Director
    • Kantara is moving out from the IEEE umbrella as independant non-profit
    • Kantara can also be a nonprofit and an SDO
    • Leadership Council Elections Happening

...

  • , Mary suggested we list a things we needed or want to do - agree the  processcould use the format the UXC at IDESG has to finish:
    • group agrees on what is needed: agree on a process, make a finite list of things that have to be checked for consistency, 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.

  • 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
    • :
      • make compliant with relevant policy

      • create a consistent set of definitions or terms either in doc, or as addendum

      • check spec against any references, systems or resources we determine are critical

    • schedule these items in each week, cover them regardless who comes to get it finished, document decisions.

  • Mark suggests schedule for review: 
    • 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

...

  • for Fields - the table we have now - needs reviewing and comments
    • is for explicit consent
    •  each field should have guidance for the specific elements

...

    • :
      • for providing a record,
      • how to present the record,

...

      • timing

...

      • for 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 Guidance for the fields and the specification.
  • Terms
    • list of definitions

...

  • the table we have now - needs reviewing and comments
  • Guidance for Consent
      suggesting
      • suggest adding consent guidance documentation for fields and
      for
      • consent receipts/records
    • Knowledge Base - (similar appendix)
        cover purpose
        •  purpose categories

       

       

      Discussion Items

      ...

      • (as set in email)

       

      ...

      Action Items

      •