Arrays and objects have limited support in parameters

RFC6570-based serialization will not go beyond what is specified
to unpack arrays and objects.

Author: handrews

versions/3.0.4.md

@@ -3574,6 +3574,8 @@ parameters:
 This example is equivalent to RFC6570's `{?foo*,bar}`, and ***NOT*** `{?foo*}{&bar}`, which is problematic because if `foo` is not defined, the result will be an invalid URI.
 The `&` prefix operator has no equivalent in the Parameter Object.
 
+Note that RFC6570 does not specify behavior for compound values beyond the single level addressed by `explode`.  The results of using objects or arrays where no behavior is clearly specified for them is implementation-defined.
+
 ### Non-RFC6570 Field Values and Combinations
 
 Configurations with no direct RFC6570 equivalent SHOULD also be handled according to RFC6570.