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

Enumerate the ways in which spec.md language/layout is unclear #117

Closed
jdolitsky opened this issue Mar 25, 2020 · 5 comments
Closed

Enumerate the ways in which spec.md language/layout is unclear #117

jdolitsky opened this issue Mar 25, 2020 · 5 comments

Comments

@jdolitsky
Copy link
Member

cc @pmengelbert

@jdolitsky
Copy link
Member Author

related to #62

@pmengelbert
Copy link
Contributor

pmengelbert commented Mar 30, 2020

I began a list of issues with the spec here:
https://hackmd.io/ZlKd3uzMSgC98OAwOQ3SHQ?view

It's a working document but I hope to make it more complete. The 3 things that will likely make the biggest difference are:

  • Combine overview and corresponding detail sections, and carefully remove all duplications.
  • Mass will be to MUST
  • Rewrite all language written from client perspective to be from registry perspective
  • Be more specific about what error codes should happen when
  • A table of endpoints with expected response codes

@vbatts
Copy link
Member

vbatts commented Apr 2, 2020

Related: #125

@mikebrow
Copy link
Member

mikebrow commented Apr 3, 2020

  • Rewrite all language written from client perspective to be from registry perspective

so long as no detail is lost in the change of perspective...

@vbatts
Copy link
Member

vbatts commented Jan 28, 2021

i'm closing this issue, as there are other issues opened now, with discussion on this.

@vbatts vbatts closed this as completed Jan 28, 2021
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

No branches or pull requests

4 participants