There is definitely an argument for understanding elementary data types later on application level instead on config format, so we do not create arbitrary disti

There is definitely an argument for understanding elementary data types later on application level instead on config format, so we do not create arbitrary distinction between types on config format level and on application level, and forcing IP addresses (and other domain-specific types) to be encoded as strings. But i do not think this is good argument for structural data types like lists, sets and so on, because M applications would use N different ways how to encode them. While a human can recognize them, it is hard to human to remember that this specific application uses that specific encoding with its own quirks.