RE: XML/XSL and ASP/IIS

Hi James - 

the question I have is that if you<magic/> stuff does work, it would still
be embedded and it looks like in one place only - the advantages of script
is that you could replace the XSL directly -

-> for example, you could use <magic/> to get back a recordset from a
database and then use script within the XSL to populate it.

The example I work with is that you find from a database that a user is
Italian and wants info in Italian - there is one XML doc like

===========================
 <language>
	<italian>
		Ciao Mondo !
	</italian>
	<english>
		Hello World !
	</english>
</language>
===========================

and so you could have and XSL style (parsed as ASP) like :

===========================
<%language=**select from database** %>

<xsl:template match="<%=language%>">
	<xsl:apply-tenmplates/>
</xsl:template>
===========================

This allows you to have a simple single stylesheet to account for any
language additions youmay *ever* make.

What do you think?? 

Anyone from Microsoft there?? What is going to be used to cater for this in
the future?

Duane's product seems to do the same thing for non IIS web servers - pretty
cool...

cheers
steven


Join Association of Internet Professionals - http://www.citix.com/aip

Steven Livingstone
President, AIP Scotland.
ceo@xxxxxxxxx
http://www.citix.com

> -----Original Message-----
> From:	Wilson, James.W [SMTP:James.W.Wilson@xxxxxxxxxxxxx]
> Sent:	09 June 1999 12:04
> To:	'xsl-list@xxxxxxxxxxxxxxxx'
> Subject:	RE: XML/XSL and ASP/IIS
> 
> Having played with XT's extension mechanisms (which allow you to hook into
> Java) I wonder if XSL+extensions could serve as a 'better ASP' as follows:
> 
> source document:
> 
> 	<mystuff>
> 		<my-static-stuff>I like eggs</my-static-stuff>
> 		<my-dynamic-content/>
> 	</mystuff>
> 
> XSL stylesheet:
> 
> 	...
> 	[magic incantation here so <magic/> hooks into Java]
> 	...
> 	<xsl:template match='my-dynamic-content'><magic/></xsl:template>
> 	...
> 
> Result:
> 	...
> 	<p>I like eggs</p>
> 	<p>Magical content: generated on 6/9/99, the DOW is at 666,000, the
> national debt is $25 trillion</p>
> 	...
> 
> it seems like this could be cleaner than embedding scripts into one's
> source
> documents. Everything stays well-formed all the way through, and you don't
> mix static content with scripting logic. You can also define a set of
> dynamic tags which could serve as, for instance, a department-wide
> standard.
> 
> 
> Presumably there will be ways to hook non-Java stuff (possibly through COM
> etc) in the future as well.
> 
> Comments? I haven't actually implemented this yet, but plan to when I get
> a
> few moments free.
> 
> James
> 
> -----Original Message-----
> From: Duane Nickull [mailto:webmaster@xxxxxxxxxxxxxxxxx]
> Sent: Wednesday, June 09, 1999 6:24 PM
> To: xsl-list@xxxxxxxxxxxxxxxx
> Subject: Re: XML/XSL and ASP/IIS
> 
> 
> 
> 
> Steven Livingstone wrote:
> > 
> > I am interested in how I should do the following -
> > 
> > I want to parse a file on the server with one XSL style sheet which
> should
> > generate XML which should then, depending on specifics be parsed again
> with
> > one of a few style sheets and the result returned as HTML.
> >
> Re: Everyone talking about this subject. 
> 
> We are developing a system very similar to *.asp files called XML Server
> Pages which use the *.xsp extension by default and allow authors to
> place instruction templates into their html webpages.  When the server
> receives a client request (get) for the *.xsp page, it processes the
> templates instruction and presents the client with html (or text |
> xml/css | xml/xsl).  The system still needs work on the xml parser.  
> 
> A unfinished website with a few examples of *.xsp can be viewed directly
> at 
> 
> http://www.cartnetwork.com/xml/index.xsp
> 
> Duane Nickull
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


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