Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

"collection" and "item" link relation types #295

Closed
handrews opened this issue Apr 3, 2017 · 2 comments
Closed

"collection" and "item" link relation types #295

handrews opened this issue Apr 3, 2017 · 2 comments

Comments

@handrews
Copy link
Contributor

handrews commented Apr 3, 2017

These link relation types from RFC 6573 implement one of the most common patterns in REST APIs. Appropriately, the RFC does not discuss HTTP-specific behavior for these links, but provides two media types as reference uses which both specify the create-on-POST pattern for the relations.

We should add similar language for using these relations in the context of application/schema+json Hyper-Schemas.

There is some dependency here on #140 (Link source / "anchor" / "anchorPointer") for properly setting the context of an "item" link to the entire collection and not just the array element or other nested structure representing the idem in the collection.

@handrews handrews added this to the draft-future milestone Apr 3, 2017
@handrews handrews modified the milestones: draft-07 (wright-*-02), draft-future May 16, 2017
@handrews
Copy link
Contributor Author

I'm going to write up a PR for this as soon as #140 is resolved enough to make this workable. Right now there's no way to describe the proper behavior (which is a problem even without these link relations, but it makes these impossible to write up in detail).

@handrews
Copy link
Contributor Author

handrews commented Oct 4, 2017

Merged PR #412.

@handrews handrews closed this as completed Oct 4, 2017
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant