W3C home > Mailing lists > Public > www-style@w3.org > January 2006

Re: [Selectors], XSLT, and a browser's internal view of an xml document

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Sun, 29 Jan 2006 15:19:51 -0600
Message-ID: <43DD3177.3000809@mit.edu>
To: Noah Scales <noahjscales@yahoo.com>
CC: www-style@w3.org

Noah Scales wrote:
> The output document would have to contain CSS
> Selectors if the output were XML in the form of an
> embedded stylesheet pointed to by a #name in the href
> of the <?xml-stylesheet> tag.

Why?  You claim this repeatedly, but this is simply not true.  If you feel that 
it's true for some reason, I'd love to hear your reason.

> And a whole bunch of other
> things (arbitrary XML formats)? So the css namespace
> is useful to modularize how new XML formats can be
> styled.

Again, I don't follow what you mean.  Perhaps an example is in order?

> If what you write is true:
> 
> " It needs to use some selector mechanism.  At the
> moment, the only selector mechanism CSS allows is
> Selectors (the specification under discussion)."
> 
> Then it should be called "CSS Selectors", for that
> reason alone.

Um... no.  CSS at the moment only allows Selectors, so CSS depends on Selectors. 
  But Selectors is used in places other than CSS.  So Selectors is NOT dependent 
on CSS.

Your logic is basically the following: "XML documents may only consist of 
Unicode characters, so Unicode should actually be called 'XML Unicode'."  That's 
clearly false, no?  What you're saying is equivalent.

> As far as why using the attr() and content() functions
> combined with selectors creates an internal view of
> different DOM than the original file

You've never defined the term "internal view".  I have no idea what it means, so 
no idea what you're actually saying here.  Please define the term before using 
it again; otherwise you're wasting both your time and your readers'.

> you need an
> example in which use of the attr() function with
> selectors creates a different DOM from its source
> prior to transformation by CSS+CSS Selectors? 

It never does.

> Is showing you an XSLT transformation that produces the
> same output sufficient?

Of course not.  XSLT creates a different DOM, by definition (see XSLT 
specification).  CSS does not, also by definition (see the CSS specification). 
Your offer quoted above makes me strongly suspect some fundamental 
misunderstandings on your part about how CSS and XSLT work...

-Boris
Received on Sunday, 29 January 2006 21:19:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:42 GMT