RE: VC HTTP API specification structure

If it helps, I can probably find one or more contributors to assist (including myself) to represent healthcare use cases.
Separate but related note, I'm part of a work group advancing a new project effort in HL7 for patient identity, which we're seeking collaboration with other HL7 project in patient data exchange, Consent, Administration, etc etc.
I'd welcome the collaboration to see where HTTP API factors as a consideration for the patient data model....

Best regards,
Jim
_______________ 
 
Jim St.Clair 
Chief Trust Officer 
jim.stclair@lumedic.io | 228-273-4893 
Let’s meet to discuss patient identity exchange: https://calendly.com/jim-stclair-1


-----Original Message-----
From: Manu Sporny <msporny@digitalbazaar.com> 
Sent: Friday, April 30, 2021 3:47 PM
To: W3C Credentials CG <public-credentials@w3.org>
Subject: VC HTTP API specification structure

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


Hey Adrian G.,

A request, please read on...

The VC HTTP API Task Force has attempted to take up the following proposal[1] on the last two calls:

PROPOSAL: Create 1 ReSpec specification in addition to separating the existing OAS files into modular components.

You objected the first time, you were not present the second time (so we didn't press on since you were the only detractor on the proposal and it would have been bad form to make a decision when you weren't there). Instead, we considered the counter-proposal, which was to split the specification, and that resulted in a large and insurmountable number of disapprovals.

The people that are doing work on this specification need a decision to make progress.

To be clear, the details of the proposal are something along these lines:

There will be a single VC HTTP API specification. The specification will be split into a number of sections (by functionality -- issuing, verification, etc.), each with a primary Editor in charge of moving that part of the specification along. The OAS files will be split up among the same sort of lines. We will use ReSpec and automatic processing logic to construct the pieces into one whole.

The VC HTTP API group will be picking up this proposal for the final time on the next call. We would like explicit agreement or continuing dissent from you before proceeding. If your response is dissent, the group needs an alternative proposal that would address your concerns.

You had requested that whatever the new structure is, that it support your healthcare prescription and/or referral use cases. I believe that whatever the construction of the specification, that those use cases will be possible. We cannot be certain of it until we have a specification to have a discussion around.

Could you please let us know your current thoughts on the proposal above with an explicit decision to take back to the group?

-- manu

[1]https://w3c-ccg.github.io/meetings/2021-04-22-vchttpapi/#120


--
Manu Sporny - https://www.linkedin.com/in/manusporny/

Founder/CEO - Digital Bazaar, Inc.
blog: Veres One Decentralized Identifier Blockchain Launches https://tinyurl.com/veres-one-launches

Received on Friday, 30 April 2021 21:08:15 UTC