Re: Guidelines on marking up data using XML/XSL

[Francois Belanger <francois@xxxxxxxxxxx>]

Kent Fitch wrote on 30/04/98 00:15:

>Yes, but that is probably implementation dependent - functions
>to access attributes could be very efficient depending on the
>data structures used by the XSL processor.

However you implement it, it's still within an eval, so it means 
validating, compiling, and executing the code just to access the 
attribute value. All this for a simple My name is 
<eval>getAttribute("name")</eval>. I don't how you can get away from it 
without resorting to tricks.

Why not add <attrib type="name"/> to XSL spec? 

It would let people choose between storing data in attributes or content 
in respect to their perpeption of the content, not about how it may 
affect performance.  More complex access should still be done with eval 
like My parent name is <eval>this.parent.getAttribute("name")</eval>

I'd like to hear from the W3C group about this.



Francois Belanger
Sitepak, Bringing Internet Business into Focus
http://www.sitepak.com



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