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

Add vc-data-integrity as a non-browser spec. #1205

Merged
merged 1 commit into from Feb 14, 2024

Conversation

jyasskin
Copy link
Member

FYI @msporny, this should help with w3c/vc-di-ecdsa#57.

@dontcallmedom dontcallmedom merged commit 981600d into w3c:main Feb 14, 2024
1 check passed
@jyasskin jyasskin deleted the patch-1 branch February 14, 2024 05:56
@msporny
Copy link
Member

msporny commented Feb 14, 2024

@jyasskin thank you!

Please help me understand what adding vc-data-integrity to browser-specs does? I read the repo README.md and couldn't really tell, tried seeing what pulls this repo in upstream (and couldn't find anything). I thought that maybe this helps ReSpec xref do it's job, but that doesn't seem right, either? IOW, I tried to figure out how this helps but kept hitting dead-ends.

If you tell me, I'm happy to do a PR against this repo's README.md to clarify why listing a spec in this repo is "A Good Thing To Do"(tm).

@dontcallmedom
Copy link
Member

@msporny the specs catalogued in this repo are the ones that are crawled regularly by reffy to produce the extracts published in webref, including the definitions that are used by ReSpec and bikeshed automatic links.

(the repo is called browser-specs because it was historically the focus of that catalogue; it is now open to any spec that can reasonably be qualified as a web spec)

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

Successfully merging this pull request may close these issues.

None yet

3 participants