- From: Mike Prorock <mprorock@mesur.io>
- Date: Wed, 15 Mar 2023 14:10:54 -0400
- To: Orie Steele <orie@transmute.industries>
- Cc: John Henderson <john.henderson@energyweb.org>, Mahmoud Alkhraishi <mahmoud@mavennet.com>, W3C Credentials CG <public-credentials@w3.org>
- Message-ID: <CAGJKSNRUN0fkpDRHT9eooNDFqEw2siYcbOMG5vZBzoWne9K12g@mail.gmail.com>
Definitely interested from our side Mike Prorock mesur.io On Wed, Mar 15, 2023, 11:16 Orie Steele <orie@transmute.industries> wrote: > Inline: > > On Wed, Mar 15, 2023 at 9:53 AM John Henderson < > john.henderson@energyweb.org> wrote: > >> Hi Orie, >> >> Following up on your questions: >> >> >>> Do you know how many other implementations are interoperable with yours? >> >> No, I don't. We haven't done interop testing for VC API exchanges yet. >> The implementation (under "EWF") is in the issuer ( >> https://w3c-ccg.github.io/vc-api-issuer-test-suite/) and verifier ( >> https://w3c-ccg.github.io/vc-api-verifier-test-suite/) test suites but >> there isn't a shared test suite for VC API exchanges yet to my knowledge. >> >> >>> It seems you have a reasonable number of related endpoints marked "A >>> NON-STANDARD endpoint currently." >> >> Yes, that's right. There's a table in the docs for our implementation >> that summarizes which endpoints are standard and which are not: >> https://github.com/energywebfoundation/ssi/tree/develop/apps/vc-api#standard-vs-custom-endpoints >> I think the interaction between the holder and the verifier/issuer via VC >> API exchanges (the "Initiate Exchange" and "Continue Exchange" endpoints) >> is in the "standard" group. >> A non-standard endpoint is, for example, how one configures an exchange. >> Perhaps the location of our non-standard endpoints could be reworked to >> make the standard vs non-standard endpoints clearer. >> >> > You have done an excellent job here, I wonder how hard it would be to add > your non standard stuff to the traceability apis... @Mahmoud Alkhraishi > <mahmoud@mavennet.com> @Mike Prorock <mprorock@mesur.io> can you review? > > >> It seems your implementation supports JWTs as well. >>> This is excellent news, since we are interested in JWT based exchange >>> endpoint flows. >>> Do you know how many implementers have demonstrated interoperability for >>> JWT based exchange endpoints? >> >> We don't yet have JWT support for our VC API implementation but it would >> certainly be interesting to know if there is support for JWTs in other >> implementations out there. >> >> > Good to know. > > We are planning to add support for it as soon as FPWD lands for > https://github.com/w3c/vc-jwt, we will probably default to using it some > time later, after maintaining tests for both sides while we improve > confidence in it. > > >> Thanks, >> >> John Henderson >> Energy Web >> >> On Tue, Mar 14, 2023 at 7:01 PM Orie Steele <orie@transmute.industries> >> wrote: >> >>> Inline: >>> >>> On Tue, Mar 14, 2023 at 1:40 PM John Henderson < >>> john.henderson@energyweb.org> wrote: >>> >>>> Who has implemented the "vc-api exchange endpoints" or the "vc-api >>>>> prove endpoint"? >>>> >>>> >>>> Energy Web also has an implementation of the both VC-API exchanges >>>> endpoints ( >>>> https://github.com/energywebfoundation/ssi/blob/cb923a1cbbd0c274917d3fed1281db2cc0a8b260/apps/vc-api/src/vc-api/vc-api.controller.ts#L228) >>>> and the VC-API presentation prove endpoint ( >>>> https://github.com/energywebfoundation/ssi/blob/cb923a1cbbd0c274917d3fed1281db2cc0a8b260/apps/vc-api/src/vc-api/vc-api.controller.ts#L174 >>>> ) >>>> >>> >>> Thank you for these links, this is exactly what I was hoping to find. >>> >>> Do you know how many other implementations are interoperable with yours? >>> >>> It seems you have a reasonable number of related endpoints marked "A >>> NON-STANDARD endpoint currently." >>> >>> We have the same issue. >>> >>> The problem it creates is the following: >>> >>> 1. we don't want to invest in testing "non standard based interop". >>> 2. we cannot get consensus to add these endpoints to "standard based >>> interop". >>> >>> classic chicken or egg. >>> >>> We could add your endpoints to the traceability api profile, and replace >>> the ones we have today. >>> >>> This is why we are asking for evidence of implementation of the >>> exchanges endpoints. >>> >>> We are willing to write the tests, if they connect to some existing >>> value pool, or we are highly confident that they will bootstrap such a pool. >>> >>> It seems your implementation supports JWTs as well. >>> >>> This is excellent news, since we are interested in JWT based exchange >>> endpoint flows. >>> >>> Do you know how many implementers have demonstrated interoperability for >>> JWT based exchange endpoints? >>> >>> >>>> >>>> Great conversation, always good to learn more about the different >>>> specifications and implementations out there. >>>> >>>> Thanks, >>>> >>>> John Henderson >>>> Energy Web >>>> >>>> >>>> >>>> >>>> On Tue, Mar 14, 2023 at 5:30 PM Ganesh Annan <gannan@digitalbazaar.com> >>>> wrote: >>>> >>>>> On Tue, Mar 14, 2023 at 12:29 PM Orie Steele <orie@transmute.industries> >>>>> wrote: >>>>> >>>>>> My question is: >>>>>> >>>>>> Does the chapi playground use the exchange endpoints: >>>>>> >>>>>> - https://w3c-ccg.github.io/vc-api/#exchange-discovery >>>>>> >>>>> >>>>> Yes, we use the exchanges endpoint. >>>>> >>>>> >>>>>> Or the prove endpoint: >>>>>> >>>>>> - https://w3c-ccg.github.io/vc-api/#prove-presentation >>>>>> >>>>> >>>>> No, we don't use the prove endpoint and currently don't have plans to. >>>>> >>>>> >>> >>> -- >>> *ORIE STEELE* >>> Chief Technical Officer >>> www.transmute.industries >>> >>> <https://www.transmute.industries> >>> >> > > -- > *ORIE STEELE* > Chief Technical Officer > www.transmute.industries > > <https://www.transmute.industries> >
Received on Wednesday, 15 March 2023 18:11:17 UTC