I think there will be an endless amount of desirable customizations like this. But, rather than wire them all through the core code, increasing complexity and code churn, I'd like to encourage a more [Open/Closed](http://en.wikipedia.org/wiki/Open/closed_principle) approach. For example, this feature could be easily implemented with the IModelFilter extensibilty point:

    public class ApplyCamelCasing : IModelFilter
    {
        public void Apply(DataType model, DataTypeRegistry dataTypeRegistry, Type type)
        {
            var camelCasedProperties = new Dictionary<string, DataType>();
            foreach (var entry in model.Properties)
            {
                var key = entry.Key;
                camelCasedProperties[Char.ToLower(key[0]) + key.Substring(1)] = entry.Value;
            }

            model.Properties = camelCasedProperties;
        }
    }

My intention would be for individual app's to utilize the IOperationFilter and IModelFilter interfaces to apply app-specific customizations of this nature. That said, I think there will be certain filters that add enough value to be included with the core code and exposed via a convenient method on SwaggerSpecConfig (IncludeXmlComments being one that comes to mind).