[PATCH] JSON Schema Mapping property now works as expected

[Konstantinos Chasialis]

Hello,

Recently we had a discussion with Mohammad on IRC about "Mapping" object
on the JSON Schema.

We had an issue the following issue.

Suppose "mapped" was false (which means the object is not mapped), then
"IOS", "strict" and "offset" did not need to be defined so the only truly
"required" field was "mapped".

But this had a flaw. Because "maxProperties" were 4 and the only
"required" property was "mapped" the user could easily define something
like :

"PokeValue" : {
    ...
    "mapping" : {
        "mapped": false,
        "strict": true,
        "IOS": 123,
        "strict": false
    }
}

which is bad imo.

With the new changes, user is obliged to define "strict", "IOS", "offset"
only if the field "mapped" is true.
In case "mapped" is false he is not allowed to define anything else
(or even define the "mapped" field twice).

I know we do not have a validator right now and all of these are not
really applicable but we might have one in the future.

I also added the "default" property which I'd like to mention that it does
not work as : "in case the user did not define this property, define it
and give it this value".

Such thing does not exist in JSON Schema. The "default" property is like
"title", just for documentation purposes.

Sorry for long message, please tell me your comments.

0005-JSON-Schema-Mapping-property-now-works-as-expected.patch
Description: Binary data