Let us suppose that you want to create an environment that insuresthat XHTML stays valid XHTML. The corollary of how validationfailures should punish the person actually responsible for them is that the site author should bepunished for invalid XHTML, and you need to punish them directly.

So let's make the web server itself validate your XHTML; if it's notvalid, it doesn't get served. Does this punish the site author? Notnecessarily, because in order for the site author to notice they have

This is one of those things that is easier to discuss in specific,so I want to say that I'm not picking on ZFS here. Well, not toomuch.

Like a number of other filesystems, ZFS has several different versions,with later ones adding new features not supported by earlier code;this change is marked with an on-disk version number. Sensibly, ZFSallows you to explicitly set the version of a new filesystem when youcreate it, so that you can use a new system but

There are two schools about dealing with errors in pseudo-XML formatslike syndication feeds and XHTML : strictfailure (the Firefox model, where the user gets a big BZZT dialog)and graceful failure (the Universal Feed Parser model, where you try toget as much as possible out of things). Which school is better is oneof those frequently argued things on the Internet.

(Yes, yes, theoretically both syndication feeds and 'XHTML' are real XMLand there is only one valid failure mode. This