Inconsistence in error message between spec and example

[Leandro Santiago]

In the specification, the error message with code -32601 is "Method
not found", but in the example it's written "Procedure not found.".

--
Atenciosamente,
Leandro

[Sebastiaan van Erk]

On 12/09/2011 07:23 PM, Leandro Santiago wrote:
> In the specification, the error message with code -32601 is "Method
> not found", but in the example it's written "Procedure not found.".
>

Actually if you nitpick, then even the other messages in the examples
are different form in the table because of the trailing period.

I'm wondering if the message in the table is intended to be the exact
message (as in, an implementation must use exactly the specified
message), or if it is more a suggested/possible message. I had actually
interpreted it as the latter for two reasons:

1) The code is there for programs to recognize the error, so there's no
reason for programs to look at the message (I think it's bad practice
anyway). Therefore, the message is purely informational (for
humans/developers), so no need to nail it down.

2) It can actually be useful to give extra information when available:
in my implementation I actually give the exact error when a parse error
happens (i.e., Parse error: Expected a ',' or '}' at character 40). It's
nice if implementations are allowed to do this. :)

Regards,
Sebastiaan

[Matt (MPCM)]

Thank you for pointing this out, I have updated the example in the
specification at jsonrpc.org.

--
Matt (MPCM)