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 attributes
> 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.

-t





> len
>
>
> From: Thomas Lord [mailto:lord@e...] 
>
> Clearly, if one were to be designing CSS from scratch
> today many compelling arguments for an XML syntax
> could be made.   Equally or more compelling arguments
> could be made for the current syntax.
>
> 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.
>
>