Yes, I'm mostly focused on the web programming world (which includes the enterprise, though not my current project) and I can't account for how much XML is used behind firewalls, versus JSON, YAML, protocol buffers, or anything else. When I previously worked in finance and logistics industries, I constantly found the theoretical benefits of XML never translated into reality due to a range of problems (e.g. even XML schema left ambiguities if it hadn't been spec'd right, horrendous Java library dependency issues, complexity of XPath). Maybe it's a better situation now.
There's plenty of people using JSON for data exchange outside of web and JavaScript developers. It's surely convenient that JSON is valid JS, and some might say they have the same "father", but it's real benefit is as a lightweight data format. Example - I'm using it right now to interface from a Java/Android client to a Rails server. There are 3000-odd SO questions on "Android JSON" (http://stackoverflow.com/questions/tagged/json+android) and I'm guessing most of those Android devs aren't interfacing with JS.
There's plenty of people using JSON for data exchange outside of web and JavaScript developers. It's surely convenient that JSON is valid JS, and some might say they have the same "father", but it's real benefit is as a lightweight data format. Example - I'm using it right now to interface from a Java/Android client to a Rails server. There are 3000-odd SO questions on "Android JSON" (http://stackoverflow.com/questions/tagged/json+android) and I'm guessing most of those Android devs aren't interfacing with JS.