2017-01 (January 2017) Meetings
...
Verifiable claims: We looked at Manu's responses to Adrian's questions. Adrian is advocating for moving away from federation. Thomas and Eve's analysis focused on being dubious about much being new in the approach vs. what's possible with JWTs, and this being troublesome from the perspective of "respecting and balancing all ecosystem parties' needs". Kathleen comments that for our readers to consider the spectrum of ecosystems (tight to loose), what is the most an individual should "have to put with" just to get the service they want and have trust? The goal should be to find discoverable semantics, and compute the trust you need.
One thing we missed in the W3C charter is that it talks about extensible semantics. But otherwise it doesn't differentiate what it's trying to do from other claim formats.
The temptation is to design a JWT-based format that has the extensions that do what VC is doing! Susan observes that it was ID2020 that was the impetus. She suggests going back to the VC people and asking for a brief analysis that shows a compare/contrast over existing tools in extended form, for the empowerment goals we hold (the charter doesn't mention this goal). Lowering friction in development and deployment is one that we're concerned about (for accelerating adoption and also for reducing complexity = greater security); can they speak to that?
...
Hence seemingly a good match for our use case criteria. Colin will introduce them to Eve in email, and she'll send them the questionnaire. SecureKey has gotten investment for blockchain-based efforts, and they are on the Kantara board, so let's at least ask them for feedback on our report, if not as well contributing a use case; Colin will reach out and cc Susan (whose connection is through Mary Hodder and IDESG). Susan can also send the questionnaire to Bitpesa, and we'll see how much time we have to combine what we get.
Discussion of the prescription use case submitted by Adrian (which Eve will forward to the list, for full context): By "The current introduction of hospitals and other institutional intermediaries into the prescription order process" is meant identity management/authentication (for checking the physician's identity) and the management of EHRs (because the prescription is generated within the EHR system). There is rent-seeking by the systems that have performed this consolidation. The goal with the use case is to have the clinician use as many as three apps or more, e.g. one for login, one for proving you deserve to prescribe, one for payment, etc. The idea is that they're horizontal and you'd have way fewer in total.
Adrian has commented that the Sedona report's logical model of EHR discovery trust (p. 64 here) doesn't account for decentralization, which blockchain can enable. Sedona is an influencer on e-discovery; lawyers and Google and MSFT and others do pay attention to it. So we may want to reflect on this in our Observations section, given that we have several use cases that have implications for health. We recognize that health data itself wouldn't be stored on a blockchain, but the generally accepted approach would be to store a transaction record stating something happened, then a later transaction record stating something else happened (or even some previous record had to be corrected), etc.
Tuesday, January 3
Agenda:
...