[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: XSLT, XHTML, and default attribute values [somewha
At 08:03 AM 9/14/2004, Andrew wrote:
> that's true. but then why not just remove the DTD > altogether? then you don't have to support obscure and/or > parser dependant configuration options. The biggest direct benefit is from tools that leverage the DTD to provide authoring support for creators of markup. Likewise, there's the philosophical position that a DTD in some sense represents a kind of Platonic ideal of the document markup, in which it's appropriate to declare things like what an attribute should be if it's not otherwise stated. If you don't do this in the schema (small 's') you have to find some other way of recording and implementing such expectations; and the schema is not self-sufficient as a specification of the "document type" (not that it ever really was). That being said, it's a perfectly defensible position (IMHO) that defaulting attributes can and should be done in a transformation, at least in many architectures. This is another case (like its weakness in up-conversion) where it becomes apparent how XSLT 1.0 was designed for "terminal" transformations (formatting output for display), not medial data-massaging, where the output conforms to the same DTD as the input, and hence doesn't need to render defaulted attribute values. Different kinds of application scenarios have different functional requirements for their various stages. Alert the media. Cheers, Wendell
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|