Updates for week of March 4 #79
Merged
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
duglin
force-pushed
the
Mar4
branch
5 times, most recently
from
9e0c2b3 to
1046700
Compare
- add some clarifications around the use of `latest` attribute - clarify that attributes with default values don't require their owning Objects to be present - be consistent about case after dashes (e.g. -word vs - Word) - treat hasDocument resources like Groups. Use of ?meta is meaningless, every MUST always be in the HTTP body. No xRegistry HTTP headers - DELETE will NOT return the deleted resources, use "204" - "latest" on a request that would result in "no latest version" is an error - "contenttype" is ok to use with RESOURCEurl. No guarantee it matches the Content-Type of a the GET to RESOURCEurl though - URI Template type : per RFC6570 section 3.2.1 (level 1) Signed-off-by: Doug Davis <[email protected]>
|
Approved on the 3/7 call |
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.
Objects to be present
MUST always be in the HTTP body. No xRegistry HTTP headers
Content-Type of a the GET to RESOURCEurl though