cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kjetil Kjernsmo <>
Subject Re: Is it a good idea to avoid the use of xsp ?
Date Mon, 16 Sep 2002 16:35:49 GMT
On Monday 16 September 2002 11:35, Nicola Ken Barozzi wrote:

> XHTML has a low *semantic* content, because it does not use tags that
> give big insight to what they contain.
> If I write
> <info>
>   <organization>Apache</organization>
>   <personell>
>    <person>
>     <name>Me</name>
>     <surname>MEME</surname>
>    </person>
>   </personell>
> </info>
> or
> <html><body>
>   <h1>Organization: Apache</h1>
>   <ul>
>    <li>Me MEME</li>
>   </ul>
> </body></html>
> Do you see the difference?

Sure, all those things are well known. As I said, I do not advocate the 
superiority of HTML in any way, on the contrary, HTML has many flaws 
and I hope to only serve it to older user agents. My issues are 
entirely different. 

To make an oversimplified example:

		if (name != "Somebody") {

This isn't much cleaner than it would if you had stuck HTML in there. 
OK, this was a very bad example, because the nesting of markup wasn't 
very different from that of logic, and I didn't need multiple xsp:logic 
blocks, but anyway. You could make this really obfuscated with not too 
many lines.

Yes, the output from XSP is easier to process further, but I'm not 
talking about the output. I'm talking about the logic. And most of all, 
I'm talking about what others find easier to understand. And that's 
when I conclude that XSP is OK for rapid development, but that one 
should look to components to see brilliance. 


Kjetil Kjernsmo
Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer

Please check that your question  has not already been answered in the
FAQ before posting.     <>

To unsubscribe, e-mail:     <>
For additional commands, e-mail:   <>

View raw message