I think the best option is to leave association between JSON Schema constructs and built-in types to the implementation.
The implementation would have to define rules to recognized specific patterns which can map to types defined by their language.
We may be able to suggest several simplistic ones, like {"type": "integer"} maps to the 32-bit integer type, if there is one, but I don't know that JSON Schema will be able to specify more than that.
I think the best option is to leave association between JSON Schema constructs and built-in types to the implementation.
The implementation would have to define rules to recognized specific patterns which can map to types defined by their language.
We may be able to suggest several simplistic ones, like
{"type": "integer"}maps to the 32-bit integer type, if there is one, but I don't know that JSON Schema will be able to specify more than that.