Re: alternating tags in a list?

ASP is not the only web-based server development environment out there.
Netscape uses LiveWire (Server-Side JavaScript)...and almost any server
can support Java Servlets.

Write your LiveWire or Servlet or ASP application to access your
relational database. If you wish to leverage XSL you can turn your query
results (tables) into an XML document and then run the XML through an
XSL processor using a specified stylesheet.

I don't see XSL as a threat to ASP or as competition to ASP. XSL is
meant for "styling" an XML document. Its not meant to be a web-based
programming environment. I do feel that scripting should be allowed in
an xsl stylesheet, but only to access the relevant objects. Relevant
objects would include the source tree or result tree. Scripting should
also provide some additional computing power such as mathematical
expressions which gets back to how this thread ("alternating tags in a
list?") started.

I feel that the following should be allowed (the "this" keyword
references the current "source" element that is being processed,
"number" would return the position of the given element):

...
<xsl:template match="employee">
 <TD>
 <xsl:process select="name"/>
 </TD>
<xsl:script>
 if ((number(this) % 2) == 1)
   return "<![CDATA[</TR><TR>]]>";
 else 
   return "";
</xsl:script>
</xsl:template>
...

I don't think the next example should be allowed, it really has nothing
to do with XML or XSL other than using XML elements for specifying my
actions, and I think this is what you two are suggesting:

...
<xsl:template match="/*">
<xsl:script>
   var connection =        Database.getConnection("ORACLE",
"beq-local","myuser","mypass");
   var query = "SELECT * FROM exmployees";
   var cursor = connection.cursor(query);
   
   while (cursor.next()) {
      write(cursor.name);
   }
</xsl:script>
</xsl:template>
...

--Keith

Didier PH Martin wrote:
> 
> Hi Guy,
> 
> You said:
> XSL is a direct threat to ASP, you can garantee that MS will be all over
> it, and if they can manage another "embrace and extend" flanking maneuver,
> they will. The W3C are fools if they ignore this. Denying the reality of it
> will just see them loosing control of main-stream XSL to MS.
> 
> Personaly I hope the W3C can avoid making this mistake.
> 
> Reply:
> Right on!!
> 
> So, if we can use scripts in rules, we'll be able to access data bases (XSL
> in its current state cannot do that). So, if XSL has the right stuff, we may
> have it on Appache, Netscape, etc... and be able to do what is more and more
> needed: accessing relational databases.
> 
> For W3 people:
> Have you heard of Internet computing?? Have you heard recently of
> e-commerce??? How can we do that without accessing databases? If at least we
> have something more standard than ASP that could be easily transported on
> different HTTP servers, XSL for instance (with the right tools embedded in
> the language).
> 
> Then, if people are asking for scripting features it is that XSL in its
> current form do not have any mechanism to access data bases. My question is
> then: How could we do that with XSL? Without a good answer to this question,
> I'll say like Guy. Microsoft is a monopoly _because_ some let them be so and
> it seems that W3 is among these. I know daddy government is there to resolve
> the issue :-)))
> 
> Didier PH Martin
> mailto:martind@xxxxxxxxxxxxx
> http://www.netfolder.com
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


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