Currently the service only support kebab case in the property names for the json configuration. For example resource-base.
We want to also support camel case in these cases, eg: resourceBase as this is more the standard in json documents.
The service should be able to detect at the start of the parsing if any of the 2 cases is used and act accordingly