Code Monkey home page Code Monkey logo

Comments (3)

wyc avatar wyc commented on July 30, 2024 3

I like the idea of versioning the /vc/v0.0.1 on a per-component basis with respect to the spec version. This way we can also have /didcomm/v0.1.0 coexisting. If we add non-standard endpoints, we could be explicit and call it /${customName}/${customVersion}/.

from didkit.

clehner avatar clehner commented on July 30, 2024

The API we implemented is now frozen/archived as v0.0.1 of vc-http-api.

We could have DIDKit support multiple vc-http-api versions. One of the other vendors appear to be doing this, i.e. Transmute has these endpoints:

The latest vc-http-api now has version 0.0.2-unstable. The previous spec version one is archived at versions/v0.0.1/ (repo, web). We could serve our latest-tracking implementation under /v0.0.2-unstable/, and move the current API to /v0.0.0/.

Alternatively, we could only support the latest API. Then if someone wants to use multiple then they can run multiple versions of didkit-http and use e.g. nginx to reverse-proxy to them under different paths.

In either case, maybe this should be a different issue but I wonder how didkit-http should handle non-vc-http-api routes. e.g. HTTP(S) Binding for DID resolvers, or DID controller APIs, or DIDComm endpoints. Should these all be versioned (or dated) too, and differentiated by subdirectories? e.g. instead of the current route /verify/credentials, we could have /vc/v0.0.1/verify/credentials. Another option could be to instead version the didkit-http API as a whole, and say e.g. /1.0/vc/ provides vc-http-api v0.0.1, and /1.0/identifiers/ provides DID resolution according to the spec as of 2020-12-02 (going loosely by the endpoint example in the did-resolution spec).

from didkit.

clehner avatar clehner commented on July 30, 2024

didkit-http was updated to use the controller pattern (vc-http-api v0.0.2) in #102. But the routes are not yet versioned.

from didkit.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.