Deprecating prism-jwt and stick to jwt standard instead #112
Labels
Commited
Commitment to deliver in the current PI
type:roadmap
This issue will appear in the [project roadmap](https://github.com/orgs/hyperledger/projects/48)
Short Description
We are not really usign prism-jwt or anything like that but at some point it was decided to name it like that, while it makes no sense now we are proposing to remove that specification and make sure we call it jwt, sdjwt and anoncreds
On top of the specification, we are also going to be required to analise and make sure we are complying with the jwt standard and using normative spec as much as possible and clarify in which areas we may be using non-normative improvements
Value statement
Code is cheaper to maintain and more interoperable with other identity solutions by removing duplicate functionality (Presentation exchange protocol VS existing Verification protocols) and (prism-jwt VS jwt specification)
Components
Cloud Agent
SDKS
Team members
@hyperledger/identus-maintainers
Architect
@hyperledger/identus-maintainers
QA Member
@hyperledger/identus-maintainers
Owner
@hyperledger/identus-maintainers
The text was updated successfully, but these errors were encountered: