JSON v2

From John's wiki
Revision as of 13:16, 8 July 2017 by Sixsigma (talk | contribs) (work, work...)
Jump to navigation Jump to search

These are some thoughts on an improved JSON data-format that includes support for namespaces and schema description.

We want to optionally include a JSON schema for a namespace. Schema could be either inline or a URL which would return the schema. For example below the 'jj5' schema is inline but the 'example' schema is by-ref.

The rules for namespaces are that you have to nominate an alias for each namespace that you use. The alias 'default' is special (a reserved word) and it is used to point to the alias for the namespace which is assumed when no namespace alias appears on data items. The 'version' and 'namespace' data is listed first, then the 'data' itself', then the 'schema' data if it's available. We put the schema last because it's the least interesting thing to read when a human is looking at the data.

var data = {
  "json": {
    "version": 2,
    "namespace": {
      "default": "jj5",
      "jj5": "net.jj5.json.schema.example.v2",
      "ex": "com.example.json.schema.example.v1"
    },
    "data": [
      {
        "first_name": "John",
        "last_name": "Elliot",
        "ex:lucky_number": 37
      }
    ],
    "schema": {
      "jj5": {
        "title": "List of people",
        "type": "array",
        "items": {
          "title": "Person",
          "type": "object",
          "properties": {
             "first_name": {
                "type": "string"
              },
              "last_name": {
                "type": "string"
              },
              "age": {
                "description": "Age in years",
                "type": "integer",
                "minimum": 0
              }
            }
          }
        },
        "required": [ "first_name", "last_name" ]
      },
      "example": "https://v1.example.schema.json.example.com/schema.json"
    }
  }
};