Newbie Q

[Dean Roddey]

>I do not think this assumption has any basis whatever in the XML 1.0
>specification, and it certainly has no basis in the parent standard,
>ISO 8879.  There is some basis in HTML browser behavior, but that is
>(in my opinion) a Bad Thing, and not to be perpetuated as a standard
>agreement.  It is dangerous for all the same reasons as in "HTML":
>the industry got stuck with hard-coded application processing semantics.
>XML encoding itself should used with the semantic opacity that the
>specification implies, in my judgment; styles and other (separate)
>processing specifications should determine how/whether certain (character)
>data in an XML document is acted upon (displayed, suppressed, etc.).

So does anyone have any opinions on whether something like XSL will be more
convenient to
deal with attributes than elements? Are the semantics of XSL such that one
would be more easily
and compactly notated than the other?

----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
roddey at us.ibm.com

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)