Update Style Values and Style Examples for consistency about openapi-specification

[karenetheridge]

I've added comments/suggestions to all 3 PRs following the discussion at the meeting today.

[karenetheridge]

Please refer to the 3.1.1 specification in the v3.1.1-dev branch, as there have already been some corrections to this area of the specification.

It does appear that the table is incorrect for simple, at least -- primitive and object types are supported there, and it probably makes sense to allow primitives for spaceDelimited and pipeDelimited.

[mikekistler]

Why does it make sense to allow primitives for spaceDelimited and pipeDelimited? The description for these two styles is specific to arrays.

spaceDelimited: Space separated array values.
pipeDelimited: Pipe separated array values.

[karenetheridge]

I'm coming at it from the perspective of a request/response validation author, where we're taking data in a request or response and deserializing it into a data structure. From this angle, allowing more types means fewer places where the validation would error out because of the wrong type being specified in the schema, but indeed it doesn't add any value to allow it (the application might as well accept an array with a single value).

[karenetheridge]

Update: we discussed this PR at the TSC meeting today (#3672) and decided:

• the changes for simple are sensible - all of primitives, arrays and objects are possible and make sense, so the spec should reflect that
• regarding spaceDelimited and pipeDelimited, a primitive type is not useful here (when writing an api spec, if you're expecting a string why would you specify style: spaceDelimited? just use simple form).

Therefore -- @charjr: could you possibly revert the changes to spaceDelimited and pipeDelimited in your PRs? I think then we should be able to review and merge them quickly (e.g. before or by the next TSC meeting). thanks!

[charjr]

@karenetheridge I've updated each PR to remove the primitive type from spaceDelimited and pipeDelimited.

Hopefully it's ready to go, if not let me know.

[karenetheridge]

looks great, thank you!

[charjr]

@karenetheridge updated, let me know if it needs any further changes.