Re: The Future of Browser-Bound XML?

CSS is concerned with the appearance of elements on your web page, and
not their semantics. That's why you can't explain via CSS that one element
is a link and the other is an inline image. 

Concepts such as "link" and "inline image" belong to the world of HTML.
You could alter the appearance of these elements by transforming their
contents into HTML tags that browsers understand (such as "div", "span",
"h1") with XSLT, and then alter their appearance by manipulating the
element's "style" object properties with CSS.

-- 
Charles Knell
cknell@xxxxxxxxxx - email


---- Sebastian Rahtz <sebastian.rahtz@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
> > today -- or just have browser aware output. And of course, 
> > it requires that your XML is already pretty much in order 
> > and fully complete for rendering. 
>  
> Unless I am mistaken, it also requires that CSS be enhanced.
> Suppose my otherwise ready-for-frying XML file contains 
> 
>  <xref url="www.microsoft.com">the gates of hell</xref>
> and
>  <figure url="somestupidpenguin.jpg"/>
> 
> I never did understand how to explain via CSS that these
> are respectively a link and an inline image. is not CSS
> completely tied to the semantics of HTML elements?
> 
> -- 
> Sebastian Rahtz      OUCS Information Manager
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 
>  

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list