-
Notifications
You must be signed in to change notification settings - Fork 209
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
Working group updates #339
Conversation
Wow, thanks for putting this together so quickly. This is great. I worry about grouping all the nit / string changes with what looks like at least 2 functionality changes. Should we split off the bigger changes (SHOULD => MUST & maybe reference => digest) into separate issues to make sure we really have consensus and give folks who weren't at the meeting this morning a chance to chime in? |
- "refers" -> "refers field" - "referrers" -> "referrers list" - lower case for defined words in the spec - change `reference` to `digest` in the referrers API - add an error code for an invalid referrers API request - add a "*note*" to stress the risk of data loss Signed-off-by: Brandon Mitchell <git@bmitch.net>
9df5e26
to
aa890a1
Compare
@michaelb990 you got it. I left "reference => digest" because I think we intended that in our WG, but I removed the comment that we reserve the right to add tag support later while we get more consensus there. And the "SHOULD => MUST" change is also pulled from this PR. |
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.
IANAM but LGTM. Opened #340 to track the remaining question.
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.
LGTM
This is a follow up to #335 with changes noted in #337.
reference
todigest
in the referrers APISigned-off-by: Brandon Mitchell git@bmitch.net