How to Avoid Being Called a Bozo When Producing XML (2005)
1–10 of 255 posts
Re: How to Avoid Being Called a Bozo When Producing XML (2005)
#2Had to post this old article because I encountered some bozo code again. Reading more about some CMS and planning on using it for my blogs when I saw the code of the RSS feed. It was written by the lead developer of the CMS and used text templates.
Re: How to Avoid Being Called a Bozo When Producing XML (2005)
#3Back in the early days of XML, Internet Explorer would insert "+" characters to fold nested sections of XML. And was the default program to open .xml files. Guess what showed up in the documents I got from an integration partner?
Re: How to Avoid Being Called a Bozo When Producing XML (2005)
#4The sheer amount of sites that produce badly formed RSS feeds is staggering, the whole point of a feed is to make your content accessible to everyone, a bit like meta-tags. Why have it if you're not going to at least implement it properly?
Re: How to Avoid Being Called a Bozo When Producing XML (2005)
#5Why would anyone choose to use XML over JSON, other than for RSS?
Re: How to Avoid Being Called a Bozo When Producing XML (2005)
#6I had no idea there's such a beast called "XML 1.1". That sounds fun!
Re: How to Avoid Being Called a Bozo When Producing XML (2005)
#7Back in the early days of XML, Internet Explorer would insert "+" characters to fold nested sections of XML. And was the default program to open .xml files. Guess what showed up in the documents I got from an integration partner?
I think if you select/copied what was displayed you'd get the plus and minus signs. If you saved that wouldn't happen.
Re: How to Avoid Being Called a Bozo When Producing XML (2005)
#8Some of this (avoiding pretty printing, mainly) is just dealing with XML's insanity. The rest is pretty solid advice, but fairly obvious for the most part. Then again, I've already done a lot of Scheme programming, understand common sense, and I read Steve Yegge's The Emacs Problem, So I already looked at XML as a tree structure, and crawling a pre-existing tree to turn it into XML is just the most natural way to deal with XML in Lisps.
Re: How to Avoid Being Called a Bozo When Producing XML (2005)
#9Why would anyone choose to use XML over JSON, other than for RSS?
If you're actually marking up text, JSON doesn't really work. XML works alright for its intended use as a language. (That doesn't mean I hate it any less.)
Re: How to Avoid Being Called a Bozo When Producing XML (2005)
#10Why would anyone choose to use XML over JSON, other than for RSS?
I can parse/print XML (using either in memory parser or streaming parser), use XML Schema to validate XML, XPath expressions to select necessary parts, automatic object mapping, and that's all with standard library without a single external dependency in Java. I don't know why would I use JSON over XML, unless I have very good reasons to do so.
For me the only thing that JSON got better is that JSON is directly mapped to commonly used data structures: arrays and maps.