Github user rgodfrey commented on the issue:
    The encoding of a single offered capability as a symbol (rather than as an 
array of symbols) is valid.  As per
    > The multiple attribute of a field description controls whether multiple 
element values are permitted in the representation. A single element of the 
type specified in the field description is always permitted. Multiple values 
are represented by the use of an array where the type of the elements in the 
array is the type defined in the field definition. Note that a null value and a 
zero-length array (with a correct type for its elements) both describe an 
absence of a value and MUST be treated as semantically identical.
    So I don't think this change is necessary


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to