- From: James Clark <jjc@jclark.com>
- Date: Tue, 27 Jul 1999 17:54:09 +0700
- To: Kay Michael <Michael.Kay@icl.com>
- CC: "'xsl-editors@w3.org'" <xsl-editors@w3.org>
I don't think it's useful for the spec to micro-manage XSLT processors' handling of runtime errors: the environments in which XSLT processors can potentially be used are too diverse. It's up to you to decide what error handling is appropriate for the environments in which you expect your processor to run. You can provide a top-level element in a non-XSLT namespace to provide user control if you want. Kay Michael wrote: > > The spec doesn't say what should happen if the URL constructed by document() > is an invalid URL, or is a valid URL pointing to no resource, or is a URL > pointing to a resource that cannot be retrieved. > > Possible actions are: > - omit the document silently from the returned nodeset > - output a message (somewhere?) and omit the document from the returned > nodeset > - abandon processing > > One feels this ought to be under user control! > > Mike Kay
Received on Tuesday, 27 July 1999 07:51:02 UTC