Comments on: XML on the Web

By: Dan

Dan — Thu, 25 Feb 2010 20:14:05 +0000

To me XML doesn’t belong on the web. That’s why XSL was invented – so you can transform XML into HTML or whatever, if you really must use XML to begin with.

By: esiebe blog » The revolution will not be televised (but may open a new browser tab)

Wed, 16 Dec 2009 14:59:42 +0000

[...] is so unwelcome that it has actually been deprecated in strict XHTML (which may or may not be too strict sometimes, but that’s another argument), and that a page employing the practice will not [...]

By: esiebe blog » The revolution will not be televised (but will open in a new browser tab)

Wed, 16 Dec 2009 13:58:12 +0000

By: anon

anon — Sun, 22 Nov 2009 02:17:15 +0000

you might also want to look at vtd-xml as the latest and most advanced XML processing lib

By: Michael Kozakewich

Michael Kozakewich — Fri, 16 Oct 2009 22:37:49 +0000

I was taught in college how to create my own DTD and validate by it, so I feel lucky.

I think WYSIWYG editors have a responsibility to the internets to create a tool that manufactures well-formed code. This goes beyond standards or draconics — it’s moral responsibility, when you’re creating something for someone to use in different places.

At that point, the majority of people would be writing what would end up being well-formed code. I don’t think anyone (except me) nowadays writes with actual text.
Heck, one could create a Google Document and export it to html.

Essentially, the landscape of the web is changing, and we’re on the climbing up the stairs onto a thin layer of abstraction, where people don’t really need to see the code. We used to get “PASTE THIS INTO YOUR BLOG!!” quiz results; now we have an icon we press.
At this stage in time, well-formedness would be appreciated.

By: Bruce

Bruce — Thu, 15 Oct 2009 11:28:41 +0000

@George ” I thought supporting validity and standards was what you’re doing for a living Bruce!”

It is. I passionately advocate using open web standards, and ensuring that they are used according to the rules of the language.

That’s what professionals do.

I support the HTML5 drive to allow, as valid, different authoring conventions (trailing slashes or not, uppercase tags or not, quoted attributes or not) where the differences don’t matter in the real world.

I support the browsers that render the Web forgiving bad markup so that we can read ancient pages, pages authored by non-professionals or assembled by crappy dinosaur CMSs. I don’t support draconian error handling.

Take the font element; it’s wrong to author with it. Professionals know that. But browsers must render it.