- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 25 Jan 2010 19:03:50 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8815 Summary: [XSLT 2.0] Validation applied to nodes other than elements and attributes Product: XPath / XQuery / XSLT Version: Recommendation Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: XSLT 2.0 AssignedTo: mike@saxonica.com ReportedBy: mike@saxonica.com QAContact: public-qt-comments@w3.org What happens when the user specifies the validation or type attributes on the xsl:copy or xsl:copy-of instructions, and the value returned by this instruction is a node other than an element or attribute node, or indeed an atomic value? The specification does not appear to answer this question. I would propose: (a) validation = (preserve | strip | lax) is a no-op: the validation attribute is ignored, and the supplied item is copied as-is. (b) validation = strict causes a type error (c) type = type-name causes a type error -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 25 January 2010 19:03:51 UTC