Trust, but verify
I now have a
nightly
job which verifies that each of my Atom feeds are well formed
xml, none of the content needs to be escaped, and all my cached
queries are correct.
For the record, I didn't call anybody a dufus... ;-)
The reason why I instituted this is because I was finding that my site was all too often straying from validity.
This is becoming more important to me as some of my site's functionality (example: XPath queries) depend on well formedness for best results.
Posted by Sam Ruby atOh, no, you didn't call me a dufus. That's entirely my own term for myself :)
Posted by l.m.orchard at
And I'd like to whip my site into shape, since treating it as a database accessable via XPath is looking nicer and nicer. So far, though, it's a semi-haphazard mishmash of HTML tag soup, TWiki shorthand, and Textile shorthand all in text files to be consumed by blosxom and it's fleet of plugins. I think I need to cobble something together to munge it all into valid XHTML.
Posted by l.m.orchard at
Trust, but verify some more
I've since added some code to verify that each of the pages in the cache of pages served in the past 24 hours are well formed and valid XHTML. This uncovered an interesting boundary case that I hadn't considered. Last week, I created a nightly job to... [more]Trackback from Sam Ruby at
Ooh, I might have to check that out. As you commented (thanks, by the way), and as I have yet to address, my site's all over the place on validity and encoding. Thinking I need to toss in some plugins for blosxom to tidy things up, since I'm a dufus...
Posted by l.m.orchard at