Question: nullable & optional/required marks

Can we represent in specification that a field is non-nullable & optional? this mean, or we send a data for the field, or just do not send the field in request, null is not allowed. {"foo": "bar", "baz": true} is allowed {"baz": true} is allowed, because is optional {"foo": null, "baz": true} is NOT allowed, because is non-nullable

Basically null has the meaning of “this property existed before, and I want to nullify its value”. If there’s no value, or the value needs not change (for requests, for example), it just shouldn’t be sent.

[raderio]

As I understand, it will be like

{
  "type": "object",
  "properties": {
    "counter": {
      "type": "integer",
      "nullable": true,
    },
   "required": [
      "counter"
   ]
}

Am I correct?

[MikeRalphson]

Non-nullable and optional is the default in a schema object for properties.