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

clarify that the collection.href property value is not always the "self" URL #9

Open
mamund opened this issue Mar 5, 2015 · 1 comment
Assignees
Milestone

Comments

@mamund
Copy link
Member

mamund commented Mar 5, 2015

the URL in the collection.href property is not meant to represent the response URL. IOW, a Cj response from:

http://example.org/list/123 (showing a selected item)

will still have

collection.href="http://example.org/list/"

Note that is it fine to include a "self" link in the links collection, if desired.

This is a backward-compatible change for the format but it is possible some client libraries are not following this guidance. This should be discussed.

@mamund mamund self-assigned this Mar 5, 2015
@mamund mamund modified the milestone: cleanup Mar 5, 2015
@sviox
Copy link

sviox commented Jan 12, 2017

Having the collection.href point to collection instead of the requested item creates a situation where the client is unable to identify the requested item in case of an assorted collection using only mandatory, spec defined fields. Also, in many implementations the reference to parent collection might be something the service does not want to have due to access control on single item level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants