[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: CSS Scoping in XML Namespaces

• To: 'Robin Berjon' <robin.berjon@e...>
• Subject: RE: CSS Scoping in XML Namespaces
• From: "Bullard, Claude L (Len)" <clbullar@i...>
• Date: Thu, 4 Mar 2004 08:27:11 -0600
• Cc: xml-dev@l...

The point is made that the colon is a 
special character reserved by two different 
syntax specifications that have to co-exist. 
So one can adopt the convention of escaping 
the colon, or one can wait for support for 
a draft standard.

The web is a collection of working broken hacks. 
That's the ultimate testament for 80/20 designs.

Creating a standard is like pouring cement; get it 
right before it hardens.

len


From: Robin Berjon [mailto:robin.berjon@e...]

> On the other hand, if the namespace prefixes 
> are different, why the backslash?

Because ':' is a special character in CSS, and has to be escaped if you 
want it to be part of a name selector.

> Considering that CSS is in it's own syntax, 
> and inside a comment, there is a distinctly 
> weird feel to the concept of it having ANY 
> impact on the XML namespaces.  Obviously it 
> does.  Is that informally specified, formally 
> specified, or just another "gotta do it 
> somehow because of legacies" solution?

CSS is *not* in a comment, that's just a broken hack. CSS has the 
ability to match on element names, and naturally this includes the 
ability to match namespaces.

• Follow-Ups:
  • The myth of 80/20
    • From: Eric van der Vlist <vdv@d...>
  • 80:20
    • From: David Megginson <dmeggin@a...>

• Prev by Date: Re: CSS Scoping in XML Namespaces
• Next by Date: RE: CSS Scoping in XML Namespaces
• Previous by thread: RE: CSS Scoping in XML Namespaces
• Next by thread: 80:20
• Index(es):
  • Date
  • Thread