<DAY> March <#>
Time | Item | Who |
---|---|---|
2 min | Welcome & Antitrust Policy Notice | Chair |
10 min | Introductions | Chair & PM |
5 min | Backgrounder | Chair |
XY min | Good Health Pass Blueprint Review | TBC |
XY min | WHO Registry Guidance | TBC |
5 min | Tooling | Chair |
3 min | Wrap up | Chair |
Key Resources:
1. Welcome and Linux Foundation antitrust policy - http://www.linuxfoundation.org/antitrust-policy
The Good Health Pass digital trust ecosystem will not be governed by a single EGF— rather there will be many
.
Each VC issued under a specific EGF will identify its issuer's specific EGF and its type with a type of URI
The VC specification includes a type property which will be used to indicate the type of credential such as CovidVaccnation as CovidTest
Triple framework:
With this architecture, all we need is a simple trust registry protocol to answer the question:
Verifier resolves the EGF DID using their choice of:
In the DID document, the verifier dereferences the trust registry service type to obtain the trust registry service endpoint URI
Spec on the API doesn’t belong in our document but we need to be able to point to it.
[Scott] We need to address how thing get in and how things get out
[Darrell] Governance will deal with how things get in. we just need to say we do CRUD
Trust registry to trust registry needs to be described - Are we going to proxy?
The $64,000 Question:
Who maintains the top-level “trust list” of EGF DIDs?
[Julian]
Action Items
Todd Communicate using the type property to the data model group with a description of how the trust registry plans to use it
Document registry to registry approach with risks of off line copies
Pre details pass of the document - Things we agree needs to get documented with links to specifications yet to be developed with the details