> Key distinction: > > DTDs are used to *VALIDATE*, not render. That's one reason. The other is to allow the document to be edited in a structured editor. Our documents are all created by humans, so we need to use a system which guides creation and editing. The Document Type Declaration is therefore present in the XML file so that the type of document can be detected by software (whether or not the DTD is used). The root element type name is insufficient for this (too many DTDs for articles use the root element type <article> already :-)
> True, but it is not uncomon to have a working stylsheet in > applications, and before release the web monkeys are let loose to > make it look nice. Of course both these developments can be > happening simultaneously. THe doc writer should not care how the > info is presented, that isn't their concern. This is a contentious point. Frequently the doc writer is the only one who knows how the information should be presented: document stylists are notoriously ignorant of technical matters, just as authors are notoriously ignorant of typographic matters. > >>The sample sitemap bundled with Cocoon offers these 'defaults' already. > > > > If that is so, why does it not transform my sample XML document with > > its accompanying XSL stylesheet? > > Are you volunteering to write something that reacts to PIs? :-) Done too many of them already. > It's not really a trivial task, and considering the amount of work > involved in it, for something we really don't want to encourage, > its not a likely thing to happen soon. No, I don't want to if I can avoid it. PIs should be kept for their real task: affecting processing *outside* the domain of the processor (think TeX/dvi \specials). Basically tweaks. > Going back to your "associated" XSL document, and distributing the files > w/o a server: you can still do that with your PIs. A browser that knows > how to treat the PIs will do so correctly. However, for serving up to > older browsers, you should use the preferred method. Your Sitemap won't > change much. You stated something like every few years. When you > change your site, you only need to update the sitemap to point to the > new stylesheet--even if you have hundreds of documents by then. I still need to bind a stylesheet to the documents. The Document Type is the obvious key, but I can't see how to achieve this in sitemap.xmap ///Peter --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
