James makes the case for choosing HTML over XHTML. He makes several good points, but overlooks what is, to me, the single biggest reason to use HTML: because HTML is clearly the future, not XHTML. Today, the choice is mostly arbitrary. In my opinion, neither markup language offers significant advantages or disadvantages compared to the other. But, it’s clear (at least to me) that HTML5 is where things are going, so stepping away from XHTML now may better prepare you for the future.
That having been said, I still keep using XHTML out of habit, even if I think HTML is the better choice. :)
My former co-worker Matt Croydon cleverly looks under the hood of NFL.com’s in-game update Flash app, and finds it’s powered by JSON-formated versions of the data — meaning it’s there for the taking. Makes me wonder how many “accidental APIs” are out there, if we check out the source XML and JSON files for various Flash widgets.
David Hyatt asks: “What do you think you are getting out of using XHTML (considering you’re probably not serving your document as XML anyway)?” My answer? An easier upgrade path to actualXHTML (served as XML) when the time comes for me to do that. I think this is a good enough reason, especially when I don’t see a good answer from the opposing camp to the counter question (i.e. “What good reason do you have for me to not use XHTML, other than the fact that you’re a pedant and it bothers your OCD?”)
Adrian Holovaty, one of a new generation of geek-journalists and a main developer of Django, offers some suggestions for XML elements that could be used to make news stories more dynamic and more machine-readable.
Cool of 37s to do this. I’m not sure the Basecamp API will prove as useful as a photo (Flickr) or maps (Google) API, but I’m sure some creative people will come up with interesting things to do with it, no less.