[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: document not there ambiguity
On Wednesday, April 23, 2003, at 12:38 PM, Robin Berjon wrote: Since when have massive cross-posts become good netiquette? I cross posted to three lists. Each one has a group of people who would be interested axkit-users : some people use XSLT xslt : because I'm using libxslt xsl-list : because there are quite a few people on that list who either implement XSLT processors or are members of various WGs at the W3C that design XSLT/Xpath Since this seems to me now to be an axkit specific problem that is no longer necessary. xsltproc does the IMO "right thing". I include xsl-list because there is a problem with the spec -- still in xslt 2.0 S Woodside wrote:On Wednesday, April 23, 2003, at 10:23 AM, Chris Leishman wrote:I wonder why people that complain about problems they find in specs don't ask themselves "why is this here?" before bitching out loud. Some specs, like all software, have misfeatures. In other cases there is a real need and reason for the given feature, whether it is liked or not.They're already on the way... the WD for xslt 2.0 says this about "unparsed-text" functionThe spec states in section 12.1 Multiple Source DocumentsReally...what where the W3C thinking? Perhaps someone should start a list of 'standard implementation choices for implementing the xslt standard' (rolls eyes) and maybe that'll become YAWNS (Yet Another W3C uNsuccessful Standard). I did ask myself why is this here and googled for it. What I found was (a) other people asking "why is this here" and (b) a variety of processors that implement it as a warning instead of an error, such as libxslt, 4suite, saxon (configurable), ... there is a nice discussion starting here http://www.biglist.com/lists/xsl-list/archives/200101/msg00073.html There are cases in which non-failing document() is desired (eg optional inclusion of data, often using the "relative to nodeset" approach) Yes. and others where failing is better. Can you explain a situation where that would be better? The spec addresses both. Since the spec is ambiguous, and people have complained about it on a number of occasions, without a satisfactory answer, therefore there is a problem with the spec. Since at the time we have the spec as is, then yes, it is also an application problem. So it is an application problem. Are you saying that AxKit's behaviour is correct? simon
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|