Operation's Parameter schemas allows nested object schemas?

Is allowed to add a schema like this inside Parameter Object?

type: object
properties:
    name:
        type: string
    surname:
        type: string
    aList:
        type: array
        items:
            type: string
        

If yes, after the first level of tree, i have to take care about explode field? If explode = true, what I have to expect in this case?

[darrelmiller]

@slinkydeveloper The style property is intended to capture a number of common serialization approaches, with the possibility to cleanly add more in the future. It does not cover all scenarios. For more complex scenarios, such as the one you describe, it is necessary to use a content object and use the media-type identifier as a reference to an external specification that describes the serialization format.

If in the future, if we enable alternate schemas, it may be possible to describe formats such as yours with content embedded in the definition. Currently this is not possible without using a specification extension.

[slinkydeveloper]

How nested parameter style works? For example, assume that we want to create a schema for this nested arrays query parameter: parameter_name=value11|value12,value21|value22,value31|value32 When i write tooling, how I have to expect a declaration of a parameter similar to this? As i can see, “style” is allowed only in Parameter object and not inside Schema object. Also, IMHO I think that spec need a little more examples on styles.