The related value is likely a service catalog and the common transports, not the services themselves, and that ship has sailed already with things like Kong Ser

The related value is likely a service catalog and the common transports, not the services themselves, and that ship has sailed already with things like Kong Service Hub or the Swagger / OpenAPI spec [1]. A lot of people will likely not want to wait behind the open-source standardization effort on how to extend the service definitions for an API like email sending or file reading, e.g., does the file ACL go in the generic metadata map [2]? There probably could be value for service definitions and a proxy that allow you to directly access a proprietary API but with a transport of your choice like gRPC which only happen to offer REST/JSON. But trying to come up with a standard API without collaboration among the largest of industry players will likely go virtually unused. [1] https://en.wikipedia.org/wiki/Swagger_(software) https://en.wikipedia.org/wiki/Swagger_(software) [2] https://github.com/m3o/m3o/blob/fb7eb42512e4c7db49ab03da0b471bbe67fcf74a/services/file/proto/file.proto#L27 https://github.com/m3o/m3o/blob/fb7eb42512e4c7db49ab03da0b47...