At 05:00 PM 07/18/1999 -0400, Hunting, Sam wrote:
>> By not finding an XSL DTD, you haven't uncovered a shocking
>> oversight on
>> the part of the W3C; you've simply identified a particular case of the
>> general rule that mixing namespaces plays havoc with validation.
>And so I know that an XML stylesheet conforms to the W3C recommendatation,
>how, exactly? Just by seeing if it "looks right" in this or that piece of
Right. You've still got to know the principles of XSL as laid out in the
spec or your favorite tutorial(s) or book(s); some XSL elements, for
example, may be used only as children of certain other elements. But in
this respect XSL isn't so different from HTML, CSS, or any programming
language. If it doesn't "look right" to the software that's processing it,
it's... well, not right.
Of course software makers have their own ways of interpreting a given W3C
standard. Some packages might not complain at all when they encounter
violations, simply display the result in some unexpected way; some tell you
what line and character position an error is discovered at; some implement
the standard incompletely; some add their own extensions and filigrees that
may be more or less useful depending on the target audience. James Clark,
one of the editors of the XSL spec, has developed the XT package which
tracks the spec (at least the transformation part of it) pretty much
precisely (although still not completely -- but it's getting there).
The short answer to "But how do I *know*?" is (a) read the spec and other
resources, (b) ask questions, and (c) choose your software carefully.
John E. Simpson
[log in to unmask]
Just XML - Now available from Prentice-Hall