Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement ucan: URI subscheme, remove as: and my: support #25

Open
cdata opened this issue Sep 23, 2022 · 4 comments
Open

Implement ucan: URI subscheme, remove as: and my: support #25

cdata opened this issue Sep 23, 2022 · 4 comments
Labels
enhancement New feature or request

Comments

@cdata
Copy link
Member

cdata commented Sep 23, 2022

Part of #11

https://github.com/ucan-wg/spec#42-own

@cdata cdata changed the title Implement own: URI subscheme, remove Implement own: URI subscheme, remove as: and my: support Sep 23, 2022
@cdata
Copy link
Member Author

cdata commented Sep 23, 2022

This maybe weighs on #10 , which maybe needs to have its scope updated.

@cdata cdata added the enhancement New feature or request label Sep 23, 2022
@jsantell
Copy link
Contributor

As of 0.10.0, own is removed ucan-wg/spec#132

@jsantell
Copy link
Contributor

Continuing with this for 0.10.0, own has been removed from the spec, and the new ucan: fulfills a similar role. Additionally, the prf: scheme is no longer supported

@cdata cdata changed the title Implement own: URI subscheme, remove as: and my: support Implement ucan: URI subscheme, remove as: and my: support Jun 27, 2023
@druide
Copy link

druide commented Jun 20, 2024

Done in #131.
ucan:<cid>, ucan:*, ucan:./*, ucan://<did>/* works, ucan://<did>/<scheme> is disabled, as it requires more work.
My concern is the lack of tests to ensure that all cases of delegation work as expected in the specification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants