Simon responds to Brian Donovan’s admonishment not to put (X)HTML markup in content stores, and arrives at the place where I’m comfortable: it’s fine to have markup in a content store.
I’ve worked on a couple of content schemas, one implemented as a relational data model, another an XML content model. And I’ve found that when you’re writing content, at some point you’re either re-inventing HTML, or just importing the DTD. An album review may have artist, title, label, and review text components, but the editors entering the reviews will want blockquotes, cites, strong and emphasis. The editor writing the policy document will want to use the same in the subsection elements.
At some point, you should say “okay, there will be markup in this container, but all we can say is that it must be well-formed and maybe validate against this DTD/Schema”.
Meanwhile, I’m trying to find if it’s legal for an href to consist of “?” and a query string. I know that Gekko and IE do the right thing with such a href, prepending it with the current URI, but is it reasonable to assume any user agent will honor that form.
Possibly Related posts (machine generated):