Who ? The People

These pages are for developers who want to understand how to use the JSON format, for interoperable communication with financial service APIs.

We help financial services communicate information & integrate systems using international & industry standards. Most of these have been XML based. Now we’re also supporting JSON.

Why ? The Purpose

The purpose of this website is to help developers identify & select among documented JSON styles. Especially for conversion to and from XML.

What ? The Problem.

Many developers find HTML & XML’s Document Object Model too abstract. DOM Classes model the generic parts of xml such as Element, Attribute.

Developers want something more concrete & convenient which represents Element & Attribute names directly as class properties, so have turned to JSON. However, there are many ways to represent these in JSON. There are a variety of methods to convert between JSON & XML – some are lossy, some XML Schema type information.
We present lossless high fidelity methods.

How ? The Provision of a Solution

These pages define and illustrate:

• Document, Object Oriented, and multiplicity dependent styles of JSON structures
  and round trip mapping between them.
• profiles for financial services.
• how data and its meta data should be structured in a JSON payload.
• extension mechanisms.

enabling developers to make an informed choice that suits their mission.

What If ?

1. Use JSON+PSVI, if you want to use XML’s Post Schema Validation Infoset.
   eg. such as default values provided by the schema.
2. Use JSON+XML, if you want high fidelity XML, preserving document order.
3. Use JSON+MetaData, if you want to attach metadata to parts of your JSON model.
4. Use JsonML, if you want to preserve document order.
5. Use Badgerfish, if you want a consistent representation,
   when the order of child elements and separation of mixed text is unimportant.
6. Use bespoke conversion if your data follows a particular style that mixes data and metadata.