Support APIs using FIX mapping to JSON

[donmendelson]

The first release candidate of FIX JSON primarily considered the use case of translating tag=value encoding to JSON for web presentation of FIX messages. Such translation from existing messages does not require a formalized schema.

However, JSON has been popularized for web APIs as, largely as a substitute for complicated XML APIs. For a potential RC2, this use case should be considered. For example, a REST API could be provided that filters data by FIX fields encoded in JSON, while the result returns JSON-encoded FIX messages.

[donmendelson]

Current need: web APIs

A major industry driver is REST API architecture with JSON payloads. I propose that we expand the scope of JSON Encoding RC2 to deliver standard API formats for FIX.

Characteristics of REST

• Synchronous request/response
• A resource uniquely identified by a URI
• HTTP - parameters may be passed in the URI, HTTP headers or message body. Responses provide a status code, HTTP headers and message body.