Unnecessary statement on map keys: keep it for the future?

[ralfhandl]

Section "Format" talks about "fields that are used as keys in a map":

All field names in the specification are case sensitive.
This includes all fields that are used as keys in a map, except where explicitly noted that keys are case insensitive.

The Overlay specification so far doesn't have any of these maps, the sentence probably was copied from the OpenAPI specification, which defines several maps with "free-style" keys.

Should we keep this currently effectless statement in case we add such maps to the Overlay specification?

[baywet]

Hey @ralfhandl ,
Thanks for bringing this up!
Related to this issue, I did put together #246 to bring some alignment with OAS 3.2.0 wording as you suggested in #236.

To answer the question at hand, I think we should leave it in there so we don't forget to bring it back whenever we introduce maps. Why?

• It's a single sentence.
• If there are no maps in the spec, it has no impact.
• It might be useful in the context of extensions and interoperability to some extent (for extensions that use maps).
• We might have usage really soon with feat: adds a parameter object for the action object #238 (latest revision has one map)

What do you think?