Skip to content

convert non-normative note into constraint #434

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

Merged
merged 1 commit into from
Mar 8, 2015

Conversation

tkellen
Copy link
Member

@tkellen tkellen commented Mar 8, 2015

This non-normative note included RFC2119 keywords, making its
status as a note ambiguous. Per our previous discussion, json-api
should not disallow implementors from including hasOne fkeys as
attributes, but it should require that any relations which are
provided must be represented under the links object.

@tkellen tkellen force-pushed the fkey-note branch 2 times, most recently from 63f31d3 to 1e5ca6e Compare March 8, 2015 17:24
@dgeb dgeb added this to the 1.0 milestone Mar 8, 2015
@dgeb
Copy link
Member

dgeb commented Mar 8, 2015

👍

@tkellen tkellen changed the title convert non-normative note into constraint for spec convert non-normative note into constraint Mar 8, 2015
@tkellen tkellen force-pushed the fkey-note branch 2 times, most recently from f5b7a6d to 734f942 Compare March 8, 2015 18:27
This non-normative note included RFC2119 keywords, making its
status as a note ambiguous. Per our previous discussion, json-api
should not disallow implementors from including hasOne fkeys as
attributes, but it should require that any relations which are
provided must be represented under the links object.
tkellen pushed a commit that referenced this pull request Mar 8, 2015
convert non-normative note into constraint
@tkellen tkellen merged commit 51663da into json-api:gh-pages Mar 8, 2015
@tkellen tkellen deleted the fkey-note branch March 8, 2015 18:28
@bintoro
Copy link
Contributor

bintoro commented Mar 8, 2015

@tkellen There's one occurrence of *SHOULD NOT* instead of **SHOULD NOT**.

@tkellen
Copy link
Member Author

tkellen commented Mar 8, 2015

Thanks for catching that @bintoro, will push a fix after we land #417.

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

Successfully merging this pull request may close these issues.

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy