@@ -2147,20 +2147,20 @@ when encountering unrecognized values.
2147
2147
If a profile does not define its own rules for handling unrecognized values,
2148
2148
the following rule applies by default:
2149
2149
2150
- 1 . If the unrecognized value occurs is the value of a profile-defined query
2151
- parameter, the server ** MUST** fail the request and respond with a
2152
- ` 400 Bad Request ` and an [ error object] [ error objects ] indicating the
2153
- problematic parameter.
2150
+ 1 . If the value of a profile-defined query parameter is unrecognized, the
2151
+ server ** MUST** fail the request and respond with a ` 400 Bad Request ` and
2152
+ an [ error object] [ error objects ] indicating the problematic parameter.
2154
2153
2155
- 2 . Otherwise, if the unrecognized value is a JSON object, and the only thing
2156
- that makes it unrecognized is that it contains one or more keys that have
2157
- no meaning assigned to them (in the latest revision of the profile that the
2158
- application is aware of), then the application ** MUST** simply ignore those
2159
- unknown keys and continue processing the profile.
2154
+ 2 . Otherwise, if the unrecognized value is a JSON object in the
2155
+ request/response document, and the only thing that makes it unrecognized
2156
+ is that it contains one or more keys that have no meaning assigned to them
2157
+ (in the latest revision of the profile that the application is aware of),
2158
+ then the application ** MUST** simply ignore those unknown keys and
2159
+ continue processing the profile.
2160
2160
2161
2161
3 . In all other cases, the application ** MUST** assume that the profile has
2162
2162
been applied erroneously and ** MUST** totally ignore the profile (i.e.,
2163
- process the document as if the profile were not there).
2163
+ process the request as if the profile were not there).
2164
2164
2165
2165
In the case of our example [ timestamps profile] , it does not define its own
2166
2166
rules, so the above defaults would apply.
0 commit comments