- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 10 May 2005 15:59:17 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1319 Summary: definition of a XSLT processor Product: XPath / XQuery / XSLT Version: Last Call drafts Platform: PC OS/Version: Windows 2000 Status: NEW Severity: trivial Priority: P2 Component: XSLT 2.0 AssignedTo: mike@saxonica.com ReportedBy: mukul_gandhi@yahoo.com QAContact: public-qt-comments@w3.org I was reading the latest working draft of XSLT 2.0 at http://www.w3.org/TR/xslt20/ , and I noticed an inconsistent description. Section 1.1 says "A transformation expressed in XSLT describes rules for transforming zero or more source trees into zero or more result trees" . Please note the words zero or more.. Is it right to say, if we are using "unparsed-text ($href as xs:string?) as xs:string?" function to parse a text file(which is not a XML file) (and there is no source XML at all as input to transformation) , then there are zero source trees ? Are there any other circumstances when there can be zero source trees? And under what circumstances, we can have zero result trees? Then later in section 2.1 (Terminology) , it is written .. "The software responsible for transforming source trees into result trees using an XSLT stylesheet is referred to as the processor" I feel, the wordings of "definition of a XSLT processor" should reflect the fact, that the XSLT 2.0 processor transforms any text input to any text output (now we may have zero source trees!). My point is quite trivial.. If found appropriate, you may change the wordings of "definition of a XSLT processor" .. Regards, Mukul
Received on Tuesday, 10 May 2005 15:59:24 UTC