addresses issue #41 (REST architectural style and the JSON data-interchange format) #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mwullink
approved these changes
Nov 21, 2024
pawel-kow
changed the title
pawel-kow
reviewed
Nov 21, 2024
| @@ -3,7 +3,8 @@ | |||
| The Extensible Provisioning Protocol (EPP) was standardized ([STD69](https://datatracker.ietf.org/doc/std69/)) | |||
| in 2009 to address the needs of domain name management between domain name registries and registrars. | |||
| Though EPP is still serving the domain name industry well, the progress in available development, integration and operational | |||
| patterns, tools and technologies create a desire to have a provisioning protocol using the REST architectural style and the JSON data-interchange format. | |||
| patterns, tools and technologies create a desire to have a provisioning protocol using the [REST](https://ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm) | |||
There was a problem hiding this comment.
I think this is the right reference: http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm
At least this is how it's linked on the author's own publication page: https://roy.gbiv.com/vita.html
There was a problem hiding this comment.
That's the reference for the full paper. The link I provided goes specifically to Section 5, the REST architectural style.
There was a problem hiding this comment.
I know, I was just trying to follow the general pattern of references to the full publication, same as in other IETF documents, not deep link to the specific chapter.
This was just a remark, I can live with deep link as well.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses issue #41