BUG :: json-schema constraints don't allow for variations in message types

[gdbrown]

When a field of type "message" is used it creates an inline reference which points to an exact version of the message schema. This makes validation problematic as the message isn't likely to always be the same version.

    "ctx_cloud": {
      "type": "object",
      "description": "The \"ctx_cloud\" is set by the server receiving the command and is generally only used internally for tracking and performance monitoring.",
      "anyOf": [
        {
          "$ref": "#/definitions/cloud"
        }
      ],
      "pbj": {
        "type": "message",
        "rule": "single"
      }
    },

inline definitions:

  "definitions": {
    "app": {
      "$ref": "https://schemas.gdbots.io/gdbots/contexts/app/1-0-0.json"
    },
    "cloud": {
      "$ref": "https://schemas.gdbots.io/gdbots/contexts/cloud/1-0-0.json"
    }
  },

In order to make this still validate the field properly and allow for multiple version the definition itself should be an anyOf that allows for any version of the message type.

Using the curie you can get a reference for all versions of the message and generate that array. Php solves this with an interface (one without the version)... json schema has no way to describe "so long as it's a blah, accept it, regardless of version)".

[excelwebzone]

I can point the ref to the laterst.json or I can also create a v<major>.json and point to that?

[gdbrown]

it must be able to validate against any of that message. latest pins it at only one version and json schema doesn't render a curie major rev.

we'd either have to render a curie major json schema file OR the anyOf points to all available versions.