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.

Sign up for GitHub

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

Jump to bottom

Discuss/plan/design support for jsonapi.org format #47

Open
oleksandr opened this issue Nov 30, 2014 · 1 comment
Open

Discuss/plan/design support for jsonapi.org format #47

oleksandr opened this issue Nov 30, 2014 · 1 comment
Labels
ready
Milestone
v0.3

Comments

@oleksandr
Copy link
Member

See rationale at the following URL:
http://jsonapi.org/format/

We can use content negotiation and provide jsonld AND jsonapi responses.
@oleksandr oleksandr added this to the v0.3 milestone Nov 30, 2014
@krylovsk
Copy link
Contributor

krylovsk commented Dec 1, 2014

Many people seem to be very attached to unique ids (including jsonapi guys), so maybe we could also consider relaxing the device-id/resource-id convention into uuids (or server-generated ids).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ready
Projects
None yet
Milestone
v0.3
Development

No branches or pull requests
2 participants
@krylovsk @oleksandr