/
2021-05-04 Rules Engines Drafting Group Meeting Notes

2021-05-04 Rules Engines Drafting Group Meeting Notes

May 04, 2021

Attendees

  • @Chris B, Chair

  • Jason Hare

  • @Kaliya Young, WG Co-chair

  • @Noam Arzt

  • Rob Broere

  • @Steve Magennis

  • @Trev Harmon, PM

  • Viola

Agenda Items

Time 

Item

Who

Time 

Item

Who

2 min

Welcome & Antitrust Policy Notice

Trev

5 min

Review of the draft's primary diagram

Chris



Discussion on diagram and open comments in the draft

Everyone

3 min

Wrap up

Chris

Recording - Link

Notes

  • Did IP and antitrust announcement.

  • We looked at the diagram in the document. Chris would like verification regarding whether or not the diagram matches people's understanding.

  • Rob would like clarification on the difference between B4 and B6. The diagram was derived from some of Rob's earlier diagrams.

  • We discussed the interaction between the system, credentials, and passes.

  • Chris' preferred term in this section would be "access" instead of "travel". The process described is intended to be generic enough to be used in other contexts.

  • Kaliya noted that we are going to need to be able to consume things other than just verifiable credentials as inputs into a rules engine to generate a pass.

  • Chris said we may need to split B4, as it is doing more than one thing.

  • We discussed the meaning of the different boxes, and updated the diagram.

  • There was a discussion regarding where the travel-related information comes into the diagram, as opposed to just healthcare-related data.

  • Chris is going to update the diagram and associated language.

  • We moved on to discussing Challenge #1.

  • Our document is likely to be the first section in the outline in order to provide framing.

  • Drummond has updated the GHP definition of credential to include identity binding, which is missing from the W3C definition that was originally adopted. This should help resolve some of the issues in the document.

  • There is a tension in the possibility of overly minimized credentials that could allow for bad behavior.

Chat Log



00:31:35 Kaliya Identity Woman: we have to orient to travel use case 00:32:05 Kaliya Identity Woman: it can - but our work here has to orient to travel 00:38:25 Kaliya Identity Woman: but who trusts those Notaries? 00:38:33 Kaliya Identity Woman: it’s too complicated 00:39:08 Steve Magennis: in my mind suitability of credentials == trust registry 00:39:29 Steve Magennis: suitability of credential for the context <> trust registry 00:43:47 Kaliya Identity Woman: it IS specific to aviation 00:45:33 Kaliya Identity Woman: please go read some is the other documents 00:48:53 Kaliya Identity Woman: read the other documents :) those questions are answered in other groups 00:51:06 Kaliya Identity Woman: that should be “good health pass” 00:51:27 Kaliya Identity Woman: that would alight with rest of the document 00:51:52 Rob Broere: I agree fully with Noam... B1-B5 are common for all Use cases... B6 should be transfer it to a TravelPAss 00:52:41 Steve Magennis: in this context 'good health' is inseperable from the desire to travel not just an interesting attribute of an individual 00:52:52 Kaliya Identity Woman: B5 should say “Good Health Pass” 00:54:09 Rob Broere: I would call B5 Good Health Credential.... It does NOT yet give any approval to use against the Use Case.. 01:12:47 Trev Harmon: Thank you, everyone. I need to hop to a different drafting group. Chris is now the meeting host. 01:22:47 viola ICTS: hi Chris, my network is not good, i will comment on the documents



Action Items

  1. Everyone is invited to review the other groups' drafts.