I'm sorry to call into question a validated point about use of snake_case instead of camelCase but I'm bit uncomfortable about this direction regarding the facts that:

• A lot of of our current API are still using camelCase (QoD, Sim Swap Mobile connect flavor, Edge cloud, Carrier billing, etc..)
• camelCase is used in other Standard Organisations and if we want to reuse their assets (in a simplified way) we will not have to redefine their attribute (and break conformance if any) . I have check there OMA (Open Mobile alliance - use for Carrier Billing) , TMF (usable to fast track OAM API in future like currently assessed in a TMF/Camara catalyst where a lot of our companies are involved) & 3GPP (monitoring event). The currently defined SIM swap API Mobile connectflavor provided response with camelCase.
• In the industry snake_case is not widely popular - yes it is used in Vonage & Twillio for example - but in the other hand Infobip, Google map API or Amazon API are camelCase.

I see what we could lose to not use camelCase (misalignment with other SDO and so complicated the telco software developer coding our api on their product) but I did not see the added value of the snake_case.

As we have not aligned our APIs it is perhaps no to late to challenge our decision?

Looking for feedback from this community.