Rules for omission of properties in an operation request

[HeikoTheissen]

There seem to be no rules for omission of properties in a request that invokes an action or a function, except for this statement in OData-JSON, section 18:

Entity typed parameter values MAY include a subset of the properties

What about properties of complex types (at least if they are nullable or collection-valued), or about properties of entities in function invocation URLs? Neither null (#392) nor the empty collection can be specified as a default value, and

If no value is specified, the client SHOULD NOT assume a default value.

[mikepizzo]

Discussed 2025/7/9:
Complex typed parameter values include the subset of the properties appropriate to the action.
For entities, MAY include a subset of the properties and/or the entity reference or key properties.

Same rules for functions, although function parameters are passed in the URL so would not be mentioned in the JSON format specification. Could move both statements to the appropriate action/function invocation section in [Protocol].