2020-01-10 Meeting notes (ISI)

Jim P

Welcome to the new Group Everyone. jim pasquale reminds us that the focus of the WG is personal information, while identity and information sharing are very much intertwining, other Kantara WG are focus on identity, and when appropriate or require consulting or working in those groups should be the proper procedure.

• Updates on proposed or possible projects discussed:
  • Consent Receipt v2 (??)
    
    • Current v1.1
    • Next Release vNext (accountability)
    • Purpose of Use Taxonomies (Ken)
  • Information Sharing Sustainability (John)
    • Information Sharing Dashboard (Iain)
      
    • Intent Casting (Iain)
    • Information Sharing Agreements (John)
    • Health Care Use Cases (Nancy)
  • Personal Data Record (Andrew Hughes)
    
    • Accountability
    • Health Care Use Cases (Nancy)
    • Data in Motion and Data at Rest 
      
  • Purpose of Use Taxonomies (Ken where does it fit? is it all three projects)

• Nominations for officers
  • Rules of the road for WG 
  • Rules of the road for project teams

• Minimum nominations required: Nominations are now open and will continue to be open for a Vote 2020-02-09
  • Chair
  • Vice-Chair (or Co-Chairs)
  • Secretary (if no nominations, Jim moves that Co-chairs alternate capturing notes)

jim pasquale encourages participants to use the blog section of the WG to communicate and share. This enables newcomers to understand how the WG deals with various terms and definitions and concepts. The group needs to capture what terms mean what to the group and in what context this WG uses them.  Examples: Interoperability/ Interfaces/ Integration, and Syntax/Taxonomies/Ontologies  

jim pasquale points out that we don't want to overextend, or boil the Ocean, so the list above needs to be clarified with respect to available resources and too many projects.  The Projects will need and be required to have their own spaces on the system and additionally there own columns on the meetings and minutes Notes.  These can be drawn from using tasks for the projects (thanks for recommending John) for tracking progress easily and dynamically.   

The survey indicates that all contributors have agreed to move 1.1 to v.next. It can't be done officially until the time period expires.

jim pasquale recommends that we break out the various sections of work in progress in the minutes by project and/or by issue so that it can be dealt with on a more granular or specific basis, rather than one large section about edits.

iainh1 NA (Unlicensed) agrees to do a JLINC demo for the first February 6th Meeting.

John Wunderlich suggests that WG meetings are for reporting back and coordinating between projects. But this begs the question about how the projects will self-organize to be both effective and transparent. i.e. do projects want project managers, leaders, managers, rapporteurs, contributors, editors, etc.

jim pasquale WG also needs to ensure that the WG is aware of status and can help address issues or roadblocks as they arise. Maybe separate project pages in Confluence as a start. Or a separate Team Leader manager call once a quarter

Nancy Lush (Unlicensed) points out that if the projects are doing most of the work, then the frequency of Work Group Meetings may be reduced.

jim pasquale  Is in complete agreement with Nancy and believes it may only require a Full WG call once a month. as part of the "Demo" 1st monthly call