Differences from 1.1WD

The most important differences are:

• Transport independence: This specification is transport-independent, so you can use any transport you like. This removes much of the complexity of the 1.1WD. (1.1WD required HTTP.)

• Request:

  • id: required for Requests (like in v1.0)
  • params: always required
  • version: removed (not necessary, because compatible to v1.0)

• Notifications: Notifications still exist (like in 1.0). Every Request with an id of Null is a notification. (1.1WD removed Notifications.)

• Parameter cleanup:

  • The params-syntax is much cleaner.

    (1.1WD specified a complex syntax with some ambiguities.)
  • Either named or positional parameters are allowed, but not both in one call. (If needed, mixed named-and-positional parameters could be added later by an extension.)

    (1.1WD allowed mixed parameters in a somehow strange way.)
  • "Null" is no special value. If any parameter has a value of "Null", that simply means that this parameter should be "Null".

    (1.1WD used "Null" as a special value.)
  • "Null" is no special value, and a parameter-value of "Null" simply means that t parameter should be "Null".

    (1.1WD used "Null" as a special value.)

• Response: - result, error: both are always required. - id: required - version: removed

• Error Object cleanup: The name member was removed, because it does not provide any information. The error-codes were defined.

• Service Description: Use different service descriptions than 1.1WD, and describe them in a separate specification.

• Member Sequence removed: No special member sequence is necessary. (1.1WD suggested the members of the JSON-RPC-object to be in a specific order, and allowed the server to refuse requests which do not stick to this order.)

• No magic: Procedure Call Parity and Call Approximation were removed in this specification. A Service must be called exactly as specified. The server must not "guess".