Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Merged
Changes from 1 commit
Commits
Show all changes
30 commits
Select commit Hold shift + click to select a range
9c0b91b
Introduce Profiles to v1.1
dgeb Apr 12, 2018
3f4220f
profiles: tweak definitions a bit
ethanresnick Apr 17, 2018
7533232
profiles: add should about extensibility
ethanresnick Apr 17, 2018
8b51551
profiles: add note about how to serialize space-separated media type …
ethanresnick Apr 17, 2018
fe660ec
profiles: make it a MUST to list the applied profiles in Content-Type
ethanresnick Apr 17, 2018
510e783
profiles: clarify role of profile in `Accept` per prior convos
ethanresnick Apr 17, 2018
36f4c0a
profiles: clarify that `Accept` may be totally ignored
ethanresnick Apr 17, 2018
4085f31
profiles: add example of using Accept to request profile
ethanresnick Apr 17, 2018
e08d3ce
profiles: clarify that keywords must be valid member names
ethanresnick Apr 17, 2018
67ff7f1
profiles: clarify evolution requriments
ethanresnick Apr 17, 2018
51d0be6
profiles: add note about 415 handling from 1.0 servers
ethanresnick Apr 17, 2018
1827986
Add top-level links.profile
ethanresnick Apr 30, 2018
eb2e815
Fix typo and trailing whitespace
dgeb Jul 1, 2018
e0397c2
Use the term `profile` in example (instead of `ext`)
dgeb Jul 1, 2018
7221b18
Clarify that links can specify URIs, not just URLs
dgeb Jul 13, 2018
18b590e
Replace all usages of jsonapi/profiles with links/profile
dgeb Jul 13, 2018
661ddbc
Profiles: fix broken links
ethanresnick Jul 22, 2018
e1232a9
profiles: remove overloaded uses of term "alias"
ethanresnick Jul 22, 2018
1e448f8
profiles: editorial/terminology cleanup/tweaks
ethanresnick Jul 27, 2018
9be7013
profiles: define what a profile is
ethanresnick Jul 27, 2018
7757134
profiles: add must-ignore rule to example timestamps profile
ethanresnick Jul 27, 2018
055a41f
profiles: create separate authoring section
ethanresnick Jul 27, 2018
3599821
profiles: add new minimal extra authoring rules
ethanresnick Jul 27, 2018
7f9eb81
profiles: editorial tweaks
ethanresnick Aug 28, 2018
e151c57
profiles: define handling of unrecognized values
ethanresnick Aug 29, 2018
e666c90
proflies: document extensibility concerns/requirements
ethanresnick Aug 29, 2018
db1e970
profile: define implicit profile query param value
ethanresnick Sep 18, 2018
61ccdff
profiles: clarify shallow definition of elements
ethanresnick Sep 18, 2018
ebae1b5
profiles: small cleanup
ethanresnick Sep 18, 2018
f8770df
profiles: fix profile param value inference
ethanresnick Sep 18, 2018
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
profiles: editorial/terminology cleanup/tweaks
  • Loading branch information
ethanresnick committed Jul 27, 2018
commit 1e448f83d2d73ed715cbc655f5d98475e26af4ee
29 changes: 12 additions & 17 deletions _format/1.1/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -537,19 +537,13 @@ Except for the `profile` key, each key present in a links object **MUST** have
a single link as its value. The `profile` key, if present, **MUST** hold an
array of links.

For example, the following `self` link is simply a URI:

```json
"links": {
"self": "http://example.com/posts"
}
```

By contrast, the following `related` link includes a URI as well as
meta-information about a related resource collection:
In the example below, the `self` link is simply a URI string, whereas the
`related` link uses the object form to provide meta information about a
related resource collection:

```json
"links": {
"self": "http://example.com/articles/1",
"related": {
"href": "http://example.com/articles/1/comments",
"meta": {
Expand All @@ -561,9 +555,9 @@ meta-information about a related resource collection:

#### <a href="#profile-links" id="profile-links" class="headerlink"></a> Profile Links

Each link in an array of `profile` links **MAY** be represented by a links
object. This object **MAY** contain an `aliases` member to represent
any [profile aliases].
Like all [links][link], a link in an array of `profile` links can be represented
with a [link object]. In that case, the link object **MAY** contain an `aliases`
member listing any [profile aliases].

Here, the `profile` key specifies an array of `profile` links, including one
that includes a [profile alias][profile aliases]:
Expand Down Expand Up @@ -1875,9 +1869,9 @@ significant timestamps in a consistent way.

## Document Structure

Every resource **MAY** include a `timestamps` member in its associated `meta`
object. If this member is present, its value **MUST** be an object that **MAY**
contain any of the following members:
Every resource object **MAY** include a `timestamps` member in its associated
`meta` object. If this member is present, its value **MUST** be an object that
**MAY** contain any of the following members:

* `created`
* `updated`
Expand Down Expand Up @@ -1908,7 +1902,7 @@ time.
### <a href="#profile-media-type-parameter" id="profile-media-type-parameter" class="headerlink"></a> `profile` Media Type Parameter

The `profile` media type parameter is used to describe the application of
one or more profiles to the JSON API media type. The value of the `profile`
one or more profiles to a JSON API document. The value of the `profile`
parameter **MUST** equal a space-separated (U+0020 SPACE, " ") list of profile URIs.

> Note: When serializing the `profile` media type parameter, the HTTP
Expand Down Expand Up @@ -2129,6 +2123,7 @@ An error object **MAY** have the following members:
[meta]: #document-meta
[links]: #document-links
[link]: #document-links-link
[link object]: #document-links-link-object
[profiles]: #profiles
[profile aliases]: #profile-keywords-and-aliases
[error details]: #errors
Expand Down