8000 Update _format/1.1/index.md · roy-coder/json-api@97f20e2 · GitHub
[go: up one dir, main page]

Skip to content

Commit 97f20e2

Browse files
dgebgabesullice
andauthored
Update _format/1.1/index.md
Co-authored-by: Gabe Sullice <gabriel@sullice.com>
1 parent 6dc43fb commit 97f20e2

File tree

1 file changed

+11
-3
lines changed

1 file changed

+11
-3
lines changed

_format/1.1/index.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -142,9 +142,17 @@ The rules for profile usage are dictated by [RFC
142142
A profile **MAY** define document members, query parameters, and processing
143143
rules that are reserved for implementors.
144144

145-
A server implementation that supports profile-defined query parameters **MUST
146-
NOT** support more than one profile per unique URL (including the entire query
147-
string).
145+
A profile **MUST NOT** define any query parameters.
146+
147+
A profile **MUST NOT** alter or remove processing rules that have been defined
148+
by this specification or by an [extension][extensions]. However, a profile
149+
**MAY** define processing rules for query parameters whose processing rules
150+
have been reserved for implementors to define at their discretion.
151+
152+
For example, a profile could define rules for interpreting [the `filter` query
153+
parameter](#fetching-filtering), but it could not specify that relationship
154+
names in [the `include` query parameter](#fetching-includes) are
155+
space-separated instead of dot-separated.
148156

149157
Unlike extensions, profiles do not need to define a namespace for document
150158
members and query parameters because profiles cannot define specification

0 commit comments

Comments
 (0)
0