[PROPOSED WORK ITEM] Vaccination Certificate Vocabulary

[tplooker]

New Work Item Proposal

A work item to define a vocabulary for issuing vaccination certificates in the form of Verifiable Credentials.

Include Link to Abstract or Draft

Draft Spec - https://w3id.org/vaccination
GH Repo - https://github.com/mattrglobal/vaccination-certificate-vocab/

List Owners

@tplooker

[OR13]

I would be happy to support / edit this vocabulary... I'd love to help provide JSON Schema like we have done for https://github.com/w3c-ccg/traceability-vocab

[mprorock]

We would absolutely be willing to engage and support this initiative. We have a definite use case surrounding food processing worker validation as well as farmer worker validation

[AdamJLemmon]

Love it @tplooker !
We're working with healthcare providers in Singapore to issue Vaccination Certificates (Healthcerts) and be great to collaborate on a unified vocab.

[wyc]

I personally welcome this work item, and commend that it's focused on defining a concrete shared vocabulary instead of an overbroad framework that may not work for everyone.

To move forward, is someone willing to step up as a co-owner of this item, as per the CCG work item process?

[jstclair2019]

Be happy to contribute as well! I think we discussed this somewhere? :)

[mprorock]

Absolutely willing to step up as a co-owner Mike Prorock CTO, Founder https://mesur.io/

…

On Mon, Feb 15, 2021 at 5:13 PM wyc ***@***.***> wrote: I personally welcome this work item, and commend that it's focused on defining a concrete shared vocabulary instead of an overbroad framework that may not work for everyone. To move forward, is someone willing to step up as a co-owner of this item, as per the CCG work item process <https://w3c-ccg.github.io/workitem-process/#additional-ccg-requirements>? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#182 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2VJZFDVILTBCVNJONTVMTS7GMATANCNFSM4XT7WZGA> .

[cstoecker]

We love this work a lot and would like to contribute to the work item. We would like to help with the JSON LD schema and some testing / test vectors (e.g. creating randomized test vectors user a faker implementation) ... potentially in a similar way as @OR13 is referring to in the traceability vocab.

We started doing a MVP for a field test via retrofitting of existing Doctor Office SW ... so that a doctor can issue a Vaccination Credential via API integration of his / her doctor software or patient appointment management system and his Vaccination Credential Issuance Module (aka Doctor Wallet). We are planning to use W3C Verifiable Credential featuring Ed25519 Digital Signatures.

We developed a basic vaccination schema in accordance to recommendations of the EU Health Network. The data structure of the EU Health Network work item is very, very similar to the CCI work. There is only one difference. EU Health Network recommends to include an optional Person Identifier: "An identifier of the vaccinated person, according to the policies applicable in each country. It should be captured what type of identifier is used. Examples: citizen ID card or identifier within the health system/IIS/e-registry"

One consideration that we would support to add to the specs is a physical-digital authentication consideration. I.e. how can I make sure that the real physical person is in front of me as a verifier when I verify the digital credential. This consideration intersects with privacy consideration and practicability questions for a verifier such as an event organizer or a public transport/travel company.

Another consideration might be auditability of the verification process. I.e. did the verifier properly verify all customers prior to providing access to a facility or service and can the verifier proof this via an audit trail. The auditability will also intersect with privacy and consent of the customer.

[tplooker]

Thanks all for the feedback, looking forward to the collaboration, thanks @mprorock and @OR13 for offering to be co-owners, I will start by updating the spec to include you, however welcome contributions from as many people willing. @wyc after this is complete what is the next step?

[vsnt]

@tplooker next step is for the chairs to create the repo.

[tplooker]

@vsnt last time I contributed a work item I believe we actually transferred it instead, keeps the GH level links working, I will have to update the w3id setup once transfered though to prevent a double redirect.