This sample shows a snippet of Bond IDL which expresses data annotations converted to a sample OpenAPI document. The OpenAPI document is then validated against both JSON Draft 4 schema and OpenAPI 2.0 schema.

The extension to JSON schema is based on section 5.6 of JSON Schema Draft 4

5.6. Extending JSON Schema Implementations MAY choose to define additional keywords to JSON Schema. Save for explicit agreement, schema authors SHALL NOT expect these additional keywords to be supported by peer implementations. Implementations SHOULD ignore keywords they do not support.

Bond IDL expressing a data annotation.

namespace Examples

struct QoSEventPartC
{
    [DataClass("EII")]
    10: required string UserEmailAddress;
    20: optional string UserPUID;
};

Swagger document specifying both an endpoint as well as `the data schema for QoSEventPartC. See the JSON schema excerpt below:

...
"definitions": {
        "QoSEventPartC": {
            "type": "object",
            "required": [
                "UserEmailAddress"
            ],
            "properties": {
                "UserEmailAddress": {
                    "type": "string",
                    "format": "email",
                    "x-ms-attributes": {
                        "Microsoft.Azure.DataClass": "EII"
                    }
                },
                "UserPUID": {
                    "type": "string"
                }
            }
        }
    }

Sample JSON document which represents the JSON schema above which corresponds to the Bond IDL

{
  "UserEmailAddress": "[email protected]",
  "UserPUID":  "foo"
}