Ah! That makes sense. I suggest adding the following to the end of that
paragraph in {8.5.2} :"The "value" key must have a JSONString value. If the invalid value isn't a string, the server must convert it to a string. If the server includes the "value" key, it must also include the "field" key." - Wendy Roome From: "Y. Richard Yang" <[email protected]> Date: Wed, October 9, 2013 14:13 To: Wendy Roome <[email protected]> Cc: IETF ALTO <[email protected]> Subject: Re: [alto] New error format in draft 20 On Wed, Oct 9, 2013 at 1:42 PM, Wendy Roome <[email protected]> wrote: > A few comments and questions on the new error reporting. > > * For code = E_INVALID_FIELD_VALUE, what is the JSON type of the "value" > field"? Seems like it should be the type of the field with the bad value. > But that means "value" has a polymorphic type. That's not impossible to > handle, but so far we're avoided that. That also implies that if the > server returns "value", the server MUST set "field" the name of the > offending field, so the client knows what type to expect for "value". > Good comment! The thought was that "value" is a JSONString of the relevant wrong value specified in the request, as your good example below suggested. You are definitely right that if "value" is specified, "field" should be specified as well.
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
