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
Normative vs. non-normative references #53
Comments
@iherman, can you split the above out into a separate issue, please? That one needs discussion by the group, but the other stuff you mention is purely editorial. |
|
I'll update all the normative and non-normative references in the spec. |
|
PR to fix references was merged a month ago, can we close this? |
|
Yes, stale issue, closing unless there is an objection from @iherman. |
|
No objections, closing. |


There are some document references that are done in a normative section and have a normative reference role, although the target is currently just an IETF draft, a note of the CG, etc. It is not a problem now but may become when the document becomes a Rec (unless the target documents become standards by then). The ones I spotted (and there may be more):
hlreferring to the Hashlink spec (which is a draft)I am also not sure how we should handle the registries (LD Cryptographic Suite Registry, DID method registry) listed in Appendix A. There are discussions at W3C on setting up a somewhat more controlled approach for such registries, and this may be at our disposal in the lifetime of this WG. Alternatively, we may want to publish them as WG notes, to give them somewhat more weight. Something to keep an eye on.The text was updated successfully, but these errors were encountered: