Subject: [xsl] REMOVE From: "Brett Harris" <bharris@xxxxxxxxxxx> Date: Mon, 26 Mar 2001 06:52:27 -0800 |
Regards, Brett Harris Director of Technical Information Infopop Corporation 206-283-5999 x222 http://www.infopop.com -----Original Message----- From: owner-xsl-list-digest@xxxxxxxxxxxxxxxxxxxxxx [mailto:owner-xsl-list-digest@xxxxxxxxxxxxxxxxxxxxxx] Sent: Sunday, March 25, 2001 11:30 PM To: xsl-list-digest@xxxxxxxxxxxxxxxxxxxxxx Subject: XSL-List Digest V3 #637 XSL-List Digest Monday, March 26 2001 Volume 03 : Number 637 In this issue: RE: [xsl] Saxon setParameter() of node-set problems RE: [xsl] xsl 1.1 security model? Re: [xsl] xsl 1.1 security model? [xsl] Catching Entities With XSLT? [xsl] Resent: Help please on a select statement. [xsl] About XSLT engines using SAX interface Re: [xsl] Catching Entities With XSLT? [xsl] xsl:call-template : How to use it Re: [xsl] xsl:call-template : How to use it Re: [xsl] xsl:call-template : How to use it RE: [xsl] xsl:call-template : How to use it [xsl] Deferring entity resolution Re: [xsl] Catching Entities With XSLT? [xsl] Full Screen application to allow modification/entry of certain XML child node ---------------------------------------------------------------------- Date: Sat, 24 Mar 2001 03:30:45 +0100 From: "Michael Kay" <mhkay@xxxxxxxxxxxx> Subject: RE: [xsl] Saxon setParameter() of node-set problems > I want to send a NodeSet to a Saxon transformer via the setParameter() > function. You should be able to simply supply the org.w3c.dom.Document object as the value of the parameter: transformer.setParameter("referenceXml", dom); Mike Kay Software AG XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: Sat, 24 Mar 2001 03:36:16 +0100 From: "Michael Kay" <mhkay@xxxxxxxxxxxx> Subject: RE: [xsl] xsl 1.1 security model? > The ability to write to multiple named documents seems to me > to be just > as dangerous as the ability to call external scripts (if not more so - > after all, ecmascript has no standard way of writing to named files). > > Should the xsl:document element be enabled client-side, or is > the answer > so obvious that the question didn't need asking? > > And would an implementation that disabled the xsl:document element > client-side still be XSLT 1.1 compliant? > It's my understanding that Microsoft are reluctant to implement this feature client-side, and I think the spec is clear that it's not required for conformance. This approach makes sense, since the requirement for the feature is mainly fur use during the publishing cycle, not in client-side rendering. Mike Kay Software AG XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: Sun, 25 Mar 2001 11:03:52 +0100 From: David Carlisle <davidc@xxxxxxxxx> Subject: Re: [xsl] xsl 1.1 security model? > .. xsl:document... It's my understanding that Microsoft are reluctant to implement this feature client-side, and I think the spec is clear that it's not required for conformance. This approach makes sense, since the requirement for the feature is mainly fur use during the publishing cycle, not in client-side rendering. Mike Kay Software AG While the ability to actually produce files is perhaps not so important client side, it's still quite useful to chunk an XML to HTML transformation into pieces to save having such a big scrolled display. Currently (using XSLT 1.0 on xt/saxon/msxsl) I use some templates that have processor specific namespace code to use xt:document and friends for the "server side" (actually command line) processors but for IE/msxml3 it just makes one chunk (say one chapter) and discards all the rest. Then <a href and other links are generated by a template which produces href="chapter2.html#foo" when such a file is being made and in the IE case writes something like href="javascript:mydisplay('chapter2','foo')" which invokes a little script that re-applies the XSL stylesheet with a parameter set to chapter2 so just that chapter is displayed as html, then scrolls the browser down to #foo. The XSLT 1.1 xsl:document will simplify the command line part of all of this, as there will no longer have to be a big processor-specific fallback, but I wonder, is there any way of standardising the generation of the href URIs. Perhaps? an XSLT specific XPath function that returns a URI that relates to whatever the system did with a corresponding xsl:document. That is, if the final writeup allows some system dependencies on whether a file is produced by xsl:document, or if so where it is, then if there was a standard way of accessing that file (which needn't exist as a real file, just be some "thing" that is accessible by some URI scheme, such as in the case above, javascript:) then we could use that function in the link templates and so avoid all explict processor-specific coding in stylesheets using xsl:document. David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre. For further information visit http://www.star.net.uk/stats.asp XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: Sun, 25 Mar 2001 14:59:05 +0100 From: Lee Goddard <home@xxxxxxxxxxxxxx> Subject: [xsl] Catching Entities With XSLT? Netscape4 doesn't seem to like some HTML character entities that my XSLT outputs. I've thought the best way of handling this is to get the stylesheet to transform them into explicit &#____; entities.... Is this a good idea, or am I going really over the top? If my DTD defines α, should Netscape expand it or should XSLT? Thanks in anticipation for any advice, Lee XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: Sun, 25 Mar 2001 10:59:28 -0500 From: Wolfgang Bogacz <wbogacz@xxxxxxxxxxx> Subject: [xsl] Resent: Help please on a select statement. Ignore previous message. Problem solved. Syntax, Syntax, Syntax !!! Thanks anyway. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: Sun, 25 Mar 2001 12:07:48 -0800 From: "Peeyush" <xml09@xxxxxxxxx> Subject: [xsl] About XSLT engines using SAX interface Hi, If any body can really answer my question that is : How many level of depths are possible for an XSLT engine that uses SAX parser. Say for example lets take Sablotron I want to really judge it according to the levels of allowable depths of the tree that it builds in the memory by getting triggers from the XML parser. PEEYUSH _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: Sun, 25 Mar 2001 19:19:43 +0100 From: David Carlisle <davidc@xxxxxxxxx> Subject: Re: [xsl] Catching Entities With XSLT? > Netscape4 doesn't seem to like some > HTML character entities that my XSLT > outputs. Netscape 4's implementation of the HTML entity set is just broken. > I've thought the best way > of handling this is to get the stylesheet > to transform them into explicit &#____; It's handling of numeric character entities is only slightly less broken, so this sometimes works. The easiest way to do this is just post process the HTML that your XSL system writes out: give it to perl or sed or somthing to globaly change α to &# whatever. > If my DTD defines α, should Netscape > expand it or should XSLT? which DTD? If you mean the DTD on the input to XSLT then the XML parser will expand them before XSLT sees them. If you mean in the output (HTML) DTD then XSLT engines are allowed to output the characters in any way legal in HTML, so as character data, or a numeric references, or as entity references. These are supposed to be equivalent but Netscape4 doesn't follow the rules... David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre. For further information visit http://www.star.net.uk/stats.asp XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: 25 Mar 2001 20:59:36 +0200 From: Armand Delcros <armand@xxxxxxxxxxxxx> Subject: [xsl] xsl:call-template : How to use it Hello, sorry, i've look on w3c website ... ms website but I don't understand how to call a template. This is the XML code : <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="call.xsl"> <ADMINISTRATION> <COUNTRY> <IDCOUNTRY>1</IDCOUNTRY> <NAMECOUNTRY>USA</NAMECOUNTRY> <PASSWD>FOO</PASSWD> </COUNTRY> </ADMINISTRATION> This is the XSL code: <?xml version="1.0"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl"> <xsl:template match="/"> <html> <body> <form> <xsl:call-template name="countrypasswd"/> </form> </body> </html> </xsl:template> <xsl:template name="countrypasswd" match="ADMINISTRATION"> <xsl:element name="INPUT"> <xsl:attribute name="TYPE">TEXT</xsl:attribute> <xsl:attribute name="NAME">passwd</xsl:attribute> <xsl:attribute name="VALUE"><xsl:value-of select="COUNTRY/PASSWD"/></xsl:attribute> </xsl:element> </xsl:template> </xsl:stylesheet> And MIcrost IE5 say that i'm not allowed to put the xsl:call-template here .... but where must I put the xsl:call-template tag ? What's wrong ? Thanks for your help Regards, Armand Delcros XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: 25 Mar 2001 23:57:01 +0200 From: Armand Delcros <armand@xxxxxxxxxxxxx> Subject: Re: [xsl] xsl:call-template : How to use it Hmmm, sorry if you find my question stupid but I also have read the FAQ : http://www.dpawson.co.uk/xsl/N7654.html But I really don't understant my problem. Help me if you can.. Thanks Armand Delcros On 25 Mar 2001 20:59:36 +0200, Armand Delcros wrote: > Hello, > sorry, i've look on w3c website ... ms website but I don't understand > how to call a template. > > This is the XML code : > <?xml version="1.0"?> > <?xml-stylesheet type="text/xsl" href="call.xsl"> > <ADMINISTRATION> > <COUNTRY> > <IDCOUNTRY>1</IDCOUNTRY> > <NAMECOUNTRY>USA</NAMECOUNTRY> > <PASSWD>FOO</PASSWD> > </COUNTRY> > </ADMINISTRATION> > > This is the XSL code: > <?xml version="1.0"?> > <xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl"> > > <xsl:template match="/"> > <html> > <body> > <form> > <xsl:call-template name="countrypasswd"/> > </form> > </body> > </html> > </xsl:template> > > <xsl:template name="countrypasswd" match="ADMINISTRATION"> > <xsl:element name="INPUT"> > <xsl:attribute name="TYPE">TEXT</xsl:attribute> > <xsl:attribute name="NAME">passwd</xsl:attribute> > <xsl:attribute name="VALUE"><xsl:value-of > select="COUNTRY/PASSWD"/></xsl:attribute> > </xsl:element> > </xsl:template> > </xsl:stylesheet> > > And MIcrost IE5 say that i'm not allowed to put the xsl:call-template > here .... > but where must I put the xsl:call-template tag ? > What's wrong ? > Thanks for your help > > Regards, > Armand Delcros > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: 25 Mar 2001 23:57:01 +0200 From: Armand Delcros <armand@xxxxxxxxxxxxx> Subject: Re: [xsl] xsl:call-template : How to use it Hmmm, sorry if you find my question stupid but I also have read the FAQ : http://www.dpawson.co.uk/xsl/N7654.html But I really don't understant my problem. Help me if you can.. Thanks Armand Delcros On 25 Mar 2001 20:59:36 +0200, Armand Delcros wrote: > Hello, > sorry, i've look on w3c website ... ms website but I don't understand > how to call a template. > > This is the XML code : > <?xml version="1.0"?> > <?xml-stylesheet type="text/xsl" href="call.xsl"> > <ADMINISTRATION> > <COUNTRY> > <IDCOUNTRY>1</IDCOUNTRY> > <NAMECOUNTRY>USA</NAMECOUNTRY> > <PASSWD>FOO</PASSWD> > </COUNTRY> > </ADMINISTRATION> > > This is the XSL code: > <?xml version="1.0"?> > <xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl"> > > <xsl:template match="/"> > <html> > <body> > <form> > <xsl:call-template name="countrypasswd"/> > </form> > </body> > </html> > </xsl:template> > > <xsl:template name="countrypasswd" match="ADMINISTRATION"> > <xsl:element name="INPUT"> > <xsl:attribute name="TYPE">TEXT</xsl:attribute> > <xsl:attribute name="NAME">passwd</xsl:attribute> > <xsl:attribute name="VALUE"><xsl:value-of > select="COUNTRY/PASSWD"/></xsl:attribute> > </xsl:element> > </xsl:template> > </xsl:stylesheet> > > And MIcrost IE5 say that i'm not allowed to put the xsl:call-template > here .... > but where must I put the xsl:call-template tag ? > What's wrong ? > Thanks for your help > > Regards, > Armand Delcros > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: Sun, 25 Mar 2001 23:10:48 +0100 From: "Chris Bayes" <Chris@xxxxxxxxxxx> Subject: RE: [xsl] xsl:call-template : How to use it Armand, Your problem is do do with the namespace you are using. Use this instead <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> This has to be **THE BIGGEST FAQ OF ALL TIME** swamping all others by 90% Ciao Chris XML/XSL Portal http://www.bayes.co.uk/xml >-----Original Message----- >From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx >[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Armand >Delcros >Sent: 25 March 2001 22:57 >To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx >Cc: xsl-list@xxxxxxxxxxxxxxxxxxxxxx; tbarrage@xxxxxxxxxxxxxxxxxxxxxx >Subject: Re: [xsl] xsl:call-template : How to use it > > >Hmmm, sorry if you find my question stupid but I also have read the FAQ >: >http://www.dpawson.co.uk/xsl/N7654.html >But I really don't understant my problem. >Help me if you can.. > >Thanks >Armand Delcros > >On 25 Mar 2001 20:59:36 +0200, Armand Delcros wrote: >> Hello, >> sorry, i've look on w3c website ... ms website but I don't understand >> how to call a template. >> >> This is the XML code : >> <?xml version="1.0"?> >> <?xml-stylesheet type="text/xsl" href="call.xsl"> >> <ADMINISTRATION> >> <COUNTRY> >> <IDCOUNTRY>1</IDCOUNTRY> >> <NAMECOUNTRY>USA</NAMECOUNTRY> >> <PASSWD>FOO</PASSWD> >> </COUNTRY> >> </ADMINISTRATION> >> >> This is the XSL code: >> <?xml version="1.0"?> >> <xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl"> >> >> <xsl:template match="/"> >> <html> >> <body> >> <form> >> <xsl:call-template name="countrypasswd"/> >> </form> >> </body> >> </html> >> </xsl:template> >> >> <xsl:template name="countrypasswd" match="ADMINISTRATION"> >> <xsl:element name="INPUT"> >> <xsl:attribute name="TYPE">TEXT</xsl:attribute> >> <xsl:attribute name="NAME">passwd</xsl:attribute> >> <xsl:attribute name="VALUE"><xsl:value-of >> select="COUNTRY/PASSWD"/></xsl:attribute> >> </xsl:element> >> </xsl:template> >> </xsl:stylesheet> >> >> And MIcrost IE5 say that i'm not allowed to put the xsl:call-template >> here .... >> but where must I put the xsl:call-template tag ? >> What's wrong ? >> Thanks for your help >> >> Regards, >> Armand Delcros >> >> >> 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 ------------------------------ Date: Sun, 25 Mar 2001 14:22:15 -0800 From: kenb@xxxxxxxxxxx Subject: [xsl] Deferring entity resolution I'm using XSLT to do a series of transformations, taking FOO.XML and transforming it into BAR.XML, then transforming bar.xml into ALPHA.TXT, BETA.TXT, and GAMMA.TXT. FOO.XML contains ≤ and ≥ entites. Is there any way to defer resolution of these entites while resolving a large number of remaining entities? I would like to simply copy the reference into the BAR.XML document without modification. If I use ENTITY declarations of "≤" or "&le;" or "&le;" in the DTD associated with FOO.XML, the parser complains of a recursive entity expansion. Any ideas? Thanks. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: Mon, 26 Mar 2001 00:42:45 +0100 From: Peter Flynn <peter@xxxxxxxxxxx> Subject: Re: [xsl] Catching Entities With XSLT? On Sun, 25 Mar 2001, David Carlisle wrote: > > Netscape4 doesn't seem to like some > > HTML character entities that my XSLT > > outputs. > > Netscape 4's implementation of the HTML entity set is just broken. Actually it never worked to start with :-) NS was implemented without reference to the HTML specs, which made it quite hard to get right because they weren't of course any way interested in "getting it right". What seems to be different about XML is that, in most cases, systems are being implemented _with_ reference to the spec, which should mean less of this guesswork in future. ///Peter XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ Date: Mon, 26 Mar 2001 05:37:54 -0000 From: "Richard Benzell" <richard_benzell@xxxxxxxxxxx> Subject: [xsl] Full Screen application to allow modification/entry of certain XML child node Questions with developing a Full Screen application to allow modification/entry of certain XML child node data. I am trying to develop an XSL application that takes a list of data obtained in an XML response from an external ERP database query. My goal is to build a screen that has 1 to nnn screen lines of data, (not counting header/footer lines), corresponding to the number of items in a particular XML child node. I want to present the users with the ability to alter text values, click checkboxes and select pull-down menu options, for each line. I want this to be done in a Full-Screen mode. Once the users enter the text, checkboxes and selection values for each line, I envision they would press the single Submit button on the screen bottom just Once. This would take all the stuff the user entered/modified on any line, build an XML tree structure, and post it as an xmlstring value to a URL that is expecting that format. The backend software at that URL will then update the ERP database with the changes the user made, based on the XML document that was just posted to it. So far, Ive been able to build an XSL program that takes the original XML query response, builds a list on lines on the screen, and even shows input text fields on each line. But I am perplexed as to how I can efficiently take 1 to nnn (where nnn could anywhere to 100+) text fields, build an XML structure and then do the URL post. Ive searched though various XSL archives and postings, but I cannot find a hint as to the appropriate way to do this. To build the input screen, I suppose I could get XSL to loop through each element and generate text and check boxes with unique labels based on an incrementing loop counter. And I suppose I could have the submit button initiate a program to build an xmlstring by hard-coding concatenations of various xml tags the text box values. But it just seems to me that there must be a better and easier way to do this, that I just don't know about. Anyway, can anyone point me in the right direction, or provide tips, comments, or sample code showing how this task could best be tackled in XSL??? And if someone knows of a site with Examples or FAQs regarding this XSL programming challenge, that would be great also. Any help would be appreciated. Thanks Richard _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ------------------------------ End of XSL-List Digest V3 #637 ****************************** XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Data Leakage, Simon Reed | Thread | [xsl] Can one element have more tha, Yao, Mingdong |
RE: [xsl] XSplit & JavaScript, JSP, skhurshid | Date | Re: [xsl] passing username, Jeni Tennison |
Month |