-
Notifications
You must be signed in to change notification settings - Fork 17
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
Draft Explainer #309
Draft Explainer #309
Conversation
Comments from mtg May 16:
|
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 to me in general :) See a couple of comments below.
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.
@mmccool That's a great explanainer. Well done!
I've found some typos and minor issues worth fixing.
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.
Left some minor comments below, but overall the explainer looks good!
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Co-authored-by: Farshid Tavakolizadeh <[email protected]>
Ready for review. Please check carefully for technical accuracy. We should also decide whether we should really allow non-HTTP self-description explorations given that our spec has
almostno assertions constraining them. The explainer would have to be updated if we do decide to support non-HTTP explorations (which the current specification DOES allow).