-
Notifications
You must be signed in to change notification settings - Fork 9
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
Avoid terms "Primary/Secondary Resource" #96
Conversation
Co-authored-by: Manu Sporny <msporny@digitalbazaar.com>
This was discussed during the did meeting on 14 November 2024. View the transcriptw3c/did-resolution#96markus_sabadello: Discussion about the terms primary and secondary resources and URL de-referencing. Tried to address the confusion mentioned in a recent WG call. Opened today -- please review. markus_sabadello: Good first issues -- 4 have been highlighted. It would be good to get others contributing to the spec, so we'd like that to happen. Please contribute!! <Wip> Issues here - https://github.com/w3c/did-resolution/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22 markus_sabadello: A label has been put on the issues. <markus_sabadello> w3c/did-resolution#17 markus_sabadello: There are some others (???) -- issues have agreement on how to address, so someone could take those and put the PR in. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small stuff. Editorial.
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
Merging after several approvals, suggestions applied, and merge conflicts resolved. |
This PR addresses #94 and replaces #89.
It now has section headings called "Dereferencing the Resource" and "Dereferencing the Fragment" instead of using "Primary Resource" and "Secondary Resource" (except in a small note that references RFC3986).