Subject: Re: [xsl] http request - unexpected characters after document end From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx (by way of Mulberry Technologies List Owner) Date: Thu, 30 Aug 2001 17:43:16 -0400 |
From: "Michael Beddow" <mbnospam@xxxxxxxxxxx> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> References: <JIEGINCHMLABHJBIGKBCMEHNCPAA.julian.reschke@xxxxxx> Subject: Re: [xsl] http request - unexpected characters after document end Date: Thu, 30 Aug 2001 09:52:43 +0100 > > I have never known anyone to use document() to call a XML >> by its full URL > > [...] > > Anyone know? - I checked out the spec and I couldn't see anything which > > explicitly said you could or couldn't do this, nor was their anything I > > could find in the XSLT books I've got lying around. > > Why shouldn't it be allowed? It's useful, it works (if what you get is XML), > and it's not forbidden in the spec. It does indeed work and it's extremely useful, allowing you to keep some of your data on a server dedicated to responding to retrievals via document() and access it from XSLT processes running anywhere on the network. I think the reason document() is under-appreciated and under-used is that in some earlier XSLT implementations it was inadequately implemented, but that's no longer a problem with current processors Michael --------------------------------------------------------- Michael Beddow http://www.mbeddow.net/ XML and the Humanities page: http://xml.lexilog.org.uk/ --------------------------------------------------------- XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] http request - unexpected, Mulberry Technologie | Thread | RE: [xsl] http request - unexpected, Tim Watts |
Re: [xsl] Newbie Q: Genealogy Examp, Thomas B. Passin | Date | Re: [xsl] Match prefix, by way of Mulberry T |
Month |