[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Why you should not design JSON data models
On Mon, Jul 3, 2017 at 7:47 AM, Ghislain Fourny <gfourny@inf.ethz.ch> wrote:
You see the problem is that what should happen is that the JSON community should say - right if we want to use JSON in XYZ context we need to upgrade our ecosystem so that we can support it. Instead what I see happening is JSON advocates demand JSON support without contemplating whether or not they have the prerequisite infrastructure. The receiving body then decides that if they don't jump to the beat they are at risk of becoming irrelevant and so eventually cobble together some hotpotch of a compromise which is the best they can do. Now everybody else using the product/model has to figure out what features were compromised/disabled in case they have to send or receive a packet in JSON form. It's like being made to teach Calculus to students who refuse to bother learning the prerequisite algebra
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|