- From: D.W.Chadwick <info@verifiablecredentials.info>
- Date: Wed, 8 Apr 2020 16:32:01 +1200
- To: Alex Puig <alex@caelumlabs.com>, Adrian Gropper <agropper@healthurl.com>
- Cc: Moses Ma <moses.ma@futurelabconsulting.com>, Christopher Allen <ChristopherA@lifewithalacrity.com>, Credentials Community Group <public-credentials@w3.org>
Hi Alex do you want a VC example in JSON, or a signed example using JWT? These are the only ones I have. If you want a ZKP or JSON-LD signed one you will need to ask someone else. Note that the example we are using is not a medically correct one, but rather is a template that will need to be completed with medical details once these have been standardised. Perhaps Adrian might be able to fill in more details? kind regards David On 08/04/2020 15:58, Alex Puig wrote: > This is relevant to me. > > We are working on an implementation of > https://github.com/DP-3T/documents using Zenroom. > > An immunity credential example would help us. > > Alex > > El mar., 7 abr. 2020 a las 23:27, Adrian Gropper > (<agropper@healthurl.com <mailto:agropper@healthurl.com>>) escribió: > > HT to Juan C. > https://unherd.com/2020/04/how-far-away-are-immunity-passports/ > > I would ask: IWhat is the role of VC relative to local or > decentralized governance to solving this issue? > > - Adrian > > > On Tue, Apr 7, 2020 at 3:10 PM D.W.Chadwick > <info@verifiablecredentials.info > <mailto:info@verifiablecredentials.info>> wrote: > > Hi Moses > > over the last week or so we have developed a proof of concept > COVID-19 > Immunity Certificate application demonstrator built on our > application > independent verifiable credential middleware. We would like to > participate in challenge (1) headed by Victoriano. I am > currently in the > process of making a video of our demo > > Kind regards > > David > > On 08/04/2020 06:51, Moses Ma wrote: > > Hi Christopher et al, > > > > You're absolutely right. This is why we have recruited: Dr. Ab > > Osterhaus to join our team - he is one of the world's > leading experts > > in coronaviruses, and his team was first to sequence the > SARS virus, > > Dr. Tony Cox - a data scientist who specializes in > epidemiology, and > > Triall.io - a clinical research organization that has run > over 30 > > Phase I-IV trials and is the developer of the first > blockchain tool > > for clinical trials. All of our proposed pilots will adhere to > > clinical research methodologies that preserve patient > privacy and > > insure validated data production. > > > > However, what we could use more of are privacy experts who > can quickly > > produce innovative working solutions. > > > > Two challenges we've identified are: (1) the use of verifiable > > credentials to serve as digital certificates of immunity, > and (2) the > > possibility of developing interoperable contact managers and > globally > > unique IDs to enable international travel. A big thanks to > Victoriano > > Giralt for stepping up to manage the first one, but I think > we still > > need to find a MacGyvered approach to solving the second... > in a way > > that has a low barrier to federation and adoption. To be > brutally > > honest, we are triaging a solution, and we need to see > reality clearly > > as to whether DIDs can add value short term. > > > > If you'd like to work on these sub-projects, please let me > know. > > Again, this is an action-primary team that will need to deliver > > software on an super-agile basis. > > > > Anyway, I promised to share the recording of our first call > so you > > know what we're up to, and you can find it here: > > > https://www.dropbox.com/s/rqhpum88k28usti/Zoom-DefenderDIDcall-040620.mp4?dl=0 > > > > Finally, I'll try to make time for CCG calls, but I'm getting > > exponentially busier these days. > > > > > > Stay healthy everyone! > > > > Moses > > > > > > PS, thisis a very interesting article about user acceptance > of contact > > managers:https://045.medsci.ox.ac.uk/user-acceptance - > respondents > > were most concerned about “government using the app as an > excuse to > > increase surveillance after the epidemic”. > > > > > > <https://045.medsci.ox.ac.uk/user-acceptance> > > > > On 4/7/20 10:19 AM, Christopher Allen wrote: > >> As was discussed briefly in the call today, if we are going > to talk > >> about #Covid19 technology solutions, we must partner with > health & > >> epidemiological experts to do it right. > >> > >> For instance, it has been proposed that we support some > kind of > >> digital immunity certificate. Even if we ignore its possible > >> human-rights & privacy risks, it can have still have risky > public > >> health care choices: > >> > >> https://unherd.com/2020/04/how-far-away-are-immunity-passports/ > >> > >> “If you issue immunity passports on this basis, /barely a > third /of > >> the people you give them to will actually be immune. > “There’s nothing > >> peculiar about this statistically,” Kevin McConway, an > emeritus > >> professor of statistics at the Open University, told me. > “It’s just > >> Bayes’ theorem > <https://en.wikipedia.org/wiki/Bayes%27_theorem>.” The > >> likelihood of you having had Covid-19, if you’ve had a > positive test, > >> depends not just on the accuracy of the test but on the > prevalence in > >> the population you’re looking at. > >> … > >> In the end, that’s going to be a horribly cold-blooded > calculation. > >> If you let people out when they’re 90% likely to be immune, > that > >> means one person in 10 is going to be at risk of getting and > >> spreading the disease. Is that risk a price worth paying > for reducing > >> the real costs (economic, social, physical, mental) of > isolation? I > >> don’t know and I’m glad I don’t have to work it out. But > someone has > >> to. And they’ll have to start by getting a reasonably > effective test, > >> and testing hundreds of thousands of people, to see how > many of us > >> have had it.” > >> > >> — Christopher Allen > > > > > > -- > > > > *Moses Ma | Managing Partner* > > > > moses.ma@futurelabconsulting.com > <mailto:moses.ma@futurelabconsulting.com> | moses@ngenven.com > <mailto:moses@ngenven.com> > > > > v+1.415.568.1068 | skype mosesma | /linktr.ee/moses.tao/ > <http://linktr.ee/moses.tao/> > > <http://linktr.ee/moses.tao> > > > > FutureLab provides strategy, ideation and technology for > breakthrough > > innovation and third generation blockchains. > > > > Learn more at /www.futurelabconsulting.com/ > <http://www.futurelabconsulting.com/> > > <http://futurelabconsulting.com>. For calendar invites, > please cc: > > mosesma@gmail.com <mailto:mosesma@gmail.com> > > > > > > Or whet your appetite by reading /Agile Innovation/ > > > <http://www.amazon.com/Agile-Innovation-Revolutionary-Accelerate-Engagement/dp/B00SSRSZ9A> > > > | /Quantum Design Sprint/ > > > <https://www.amazon.com/Quantum-Design-Sprint-Application-Disruptive/dp/1799143864> > > > | my blog at /psychologytoday.com/ > <http://psychologytoday.com/> > > <http://www.psychologytoday.com/blog/the-tao-innovation>. > > > > NOTICE TO RECIPIENT: THIS E-MAIL IS MEANT FOR ONLY THE INTENDED > > RECIPIENT OF THE TRANSMISSION. IF YOU RECEIVED THIS E-MAIL > IN ERROR, > > ANY REVIEW, USE, DISSEMINATION, DISTRIBUTION, OR COPYING OF > THIS > > E-MAIL IS STRICTLY PROHIBITED. PLEASE NOTIFY THE SENDER > IMMEDIATELY OF > > THE ERROR BY RETURN E-MAIL AND PLEASE DELETE THIS MESSAGE > FROM YOUR > > SYSTEM. THIS EMAIL SHOULD NOT BE CONSIDERED BINDING; HARD COPY > > DOCUMENTS ARE REQUIRED TO CREATE LEGALLY BINDING > COMMITMENTS. FOR > > CALENDAR INVITES, PLEASE CC: MOSESMA@GMAIL.COM > <mailto:MOSESMA@GMAIL.COM> > > > > > > -- > > Alex Puig > > CTO > > +34 678544357 > > alex@caelumlabs.com <mailto:alex@caelumlabs.com> > > Follow us!Twitter <https://twitter.com/caelumlabs>| > > linkedin <https://www.linkedin.com/company/caelumlabs/>| Newsletter > <http://newsletter.caelumlabs.com/>|Gitlab <https://gitlab.com/caelumlabs> > > IMPORTANT: The contents of this email and any attachments are > confidential. It is strictly forbidden to share any part of this > message with any third party, without a written consent of the sender. > If you received this message by mistake, please reply to this message > and follow with its deletion, so that we can ensure such a mistake > does not occur in the future. > > * > > *
Received on Wednesday, 8 April 2020 04:32:25 UTC