I would agree with adding either a server side (config override) or client side control (query param with `?delim=.`) as it will be compatible with the current v1 endpoint.
In the future we could introduce a v2 endpoint(s), but I would want to wait for OpenAPI 4 because they address this by allowing multi-segment pathing via URI templates in RFC 6570 <https://datatracker.ietf.org/doc/html/rfc6570>, which is the original way we wanted to represent namespaces, but it wasn't supported (e.g. .../{+namespaces}/tables/{table}). I doubt it's really worth the effort though, so I feel like a configurable delimiter makes the most sense. -Dan
