2020-01-10 Meeting notes (ISI)
Date
2020-01-10
Status of Minutes
Approved
Approved at: 2020-01-30 Meeting notes (ISI) DRAFT
Attendees
Voting
- jim pasquale
- John Wunderlich
- iainh1 NA (Unlicensed)
- Former user (Deleted)
- Former user (Deleted)
- Former user (Deleted)
- Nancy Lush (Unlicensed)
Non-Voting
- Former user (Deleted)
- Ken Klingenstein
- vitor jesus (Unlicensed)
Regrets:
- Andrew Hughes
- Former user (Deleted)
Quorum Status
Quorum not required for this meeting
Participant Roster in process of being updated for the new WG. Quorum requirements to be determined and updated here by jim pasquale
Discussion Items
Time | Item | Who | Notes |
---|---|---|---|
mins |
| 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.
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. |
min | Motion to approve prior minutes | Not quorate | MOTION: To approve all and any outstanding meeting minutes requiring approval. Moved by: Second: Discussion: Motion: |
V. next contributions | 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. | ||
0 min | News about new implementations | All | None mentioned |
0 min | Demo status update | all | iainh1 NA (Unlicensed) agrees to do a JLINC demo for the first February 6th Meeting. |
0 min | Specification update approach | See a flowchart version of this here: https://share.mindmanager.com/#publish/b-DWOcuKGnVY1PXBKXTpL0-DQOeqmZMGfGUAPiC5 | |
0 min | WG Charter operational structure | Jim | 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 |
min | Upcoming events update | All | |
40 min | AOB | ||
Next meeting | *** Next call 2020-01-23 10:30 am Eastern DAYLIGHT Time https://global.gotomeeting.com/join/323930725
|
- jim pasquale to check out creating tasks in Confluence