OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] CSS does not use the XML syntax. Why not?

That's the well-known impedance mismatch with objects:  attributes are not
OOP fields.  No matter how it is explained away, some want atts to have
structure and that is the same as saying they might as well-be subtrees (the
Xerox solution from way before XML or HTML).

It's fun to play what-if in a historical mode, but there isn't much chance
of a change here.  The alternative is to get the CSS out-of-line but the
implementations for this and other things att values are used for has
possibly gone too far for too long. 

I do remember the CSS vs markup syntax discussions, but didn't want to
comment publicly.  The outcomes are what they are and having seen what
markup looks like in graphics, my mind changed.  Sometimes pointies are the
wrong way to go for aesthetics.


From: Thomas Lord [mailto:lord@emf.net] 
Len Bullard wrote:
> The problem of having values in attributes would still exist. 

I was vaguely imagining that CSS attributes would become
element attributes in isolated namespaces, so, no problem.
What is currently a single attribute in HTML would get bust
out into several attributes in HTML.   (This is not to say that
moving away from the current CSS syntax in browsers and as
used in HTML is practical.   Just how it might be if history had
happened in a slightly different order or how it might look if
the current situation can be sealed off like a blowed up reactor
and covered over with clean new standards and translators in between.)

>  A follow on
> question might be is the use of microformats and other values in
> such as scripts a sound use of XML attribute value-pairs.

You're asking the wrong guy, partly.   I have (unsurprising and
probably somewhat shared) views on what's practical and appropriate
in that area but, in the bigger picture, I think the limitation of
XML attribute values to be strings is a mistake:  attribute values
which are arbitrary elements should be permitted, in my view.

QNames for element names and attribute names I can see -- you
want values with a fast equality test and namespaces for those
things.   Attribute values, however, should be less constrained.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS