Hi Detlef

here is the architecture document that we are using in our design and implementation. All the APIs have been published. The Verifier API is part of the W3C CCG HTTP API. The others have been published as part of the eSSIF project

Kind regards

David

On 08/04/2021 19:23, detlef.huehnlein@ecsec.de wrote:

Hi David,

 

thank you for your mail.

 

To have a simple universal verifier for all sorts of W3C Verifiable Credentials
sounds very inviting. Are there any design documents or sources, which are

published or could be shared here?

 

BR,

Detlef

 

Von: David Chadwick <d.w.chadwick@verifiablecredentials.info>
Gesendet: Mittwoch, 7. April 2021 21:19
An: Tony Rose <tony@proofmarket.io>; detlef.huehnlein@ecsec.de; vaccination@eid.as; nick.pope@secstanassoc.com
Betreff: Re: [Vaccination] Re: Hello and some questions from a new member

 

Hi All

I am working with East Kent NHS to pilot vaccination certificates.

I am also a member of the eSSIF project, in which I have proposed a simple universal verifier (SUV) to allow interworking between different W3C VC based systems.

As you probably know, there are now 90 DID methods published and probably more in use that have not been published yet. The idea of the SUV is similar to that of a universal resolver for DIDs. If the different VC based systems support a few simple APIs then a resource should be able to support any of them sending a W3C VP to it and should be able to verify it and validate the user's COVID status

Kind regards

David

On 07/04/2021 18:32, Tony Rose wrote:

Hi - 

I am a member of CCI, ToIP, on the drafting committee for the Good Health Pass, and we helped create the MIT Paper Credentials specification.  

Proof Market developed the MedCreds platform based on W3C verifiable credentials built with open source on Hyperledger INDY and ARIES.

Would this be helpful?

Tony

 

--

Tony Rose
Founder & CEO | ProofMarket

LinkedIn

Cell +1 650 504 5154

 

—> Sign up for your own MedCreds Wallet!


The content of this email is confidential and intended for the recipient specified in message only. 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.

On Apr 7, 2021, 8:51 AM -0700, nick.pope@secstanassoc.com, wrote:

Detlef,

You say the aim is:
To improve the technical interoperability of the existing and emerging vaccination certificate services out there.

Do we have representation from those involved in the existing and emerging vaccination certificate services?

Nick

-----Original Message-----
From: detlef.huehnlein@ecsec.de <detlef.huehnlein@ecsec.de>
Sent: 07 April 2021 15:45
To: vaccination@eid.as
Subject: [Vaccination] Re: Hello and some questions from a new member

Dear Steven,

thank you for your mail, which was the first mail ever on this brand new mailing list. 😉

Thank you for kicking off the discussion and raising the important questions below. As the initiative just started, you will find all what is currently available at https://cloud.eid.as/index.php/s/p6WRRwR9dD5JP4F.


I’ve just joined the mailing list. May I ask a few questions :
- is there a charter / terms of reference for this group somewhere ?


As the initiative is, at least currently, completely informal, there is no formal charter or ToR (yet?). The document at https://cloud.eid.as/index.php/s/g8ywMMYHp7fs7Ma outlines what we are aiming to: To improve the technical interoperability of the existing and emerging vaccination certificate services out there.


- is there a public list of individual and organisational membership?


Please refer to https://cloud.eid.as/index.php/s/P2fxnfwALZ95tcM, but keep in mind that there is not any formal organisational setting or embedding.


- is the a group collaboration tool (eg GitHub) ?


The different supporting organisations maintain different GitHub repositories, such as https://github.com/oasis-tcs/dss-x-openapi for example and as soon as we have produced technical content and source code, we should talk about whether we should use one of the existing repos or create a new one. In the meantime I would like to invite everybody to register at https://cloud.eID.AS to get write access to the folder corresponding to the first link above.


- under what governance / IP ownership / license if model does this group operate?


There are no governance or IP ownership rules defined and no discussions and hence agreements with respect to licenses yet. The only fixed point, which is somewhat clear from the goal of the initiative, is that the outcome should be usable and by everybody under a suitable open source / creative common license, and if we one day produce something, which could be called "standard", it should be an open one in the sense of https://open-stand.org/ .

Best Regards,
Detlef

Mob: +49 171 9754980

Kind regards

Steven Capell
Mob: 0410 437854
_______________________________________________
Vaccination mailing list -- vaccination@eid.as To unsubscribe send an email to vaccination-leave@eid.as _______________________________________________
Vaccination mailing list -- vaccination@eid.as To unsubscribe send an email to vaccination-leave@eid.as
_______________________________________________
Vaccination mailing list -- vaccination@eid.as
To unsubscribe send an email to vaccination-leave@eid.as



_______________________________________________
Vaccination mailing list -- vaccination@eid.as
To unsubscribe send an email to vaccination-leave@eid.as

_______________________________________________
Vaccination mailing list -- vaccination@eid.as
To unsubscribe send an email to vaccination-leave@eid.as