- From: <bugzilla@jessica.w3.org>
- Date: Wed, 05 Feb 2014 21:09:18 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24531 Bug ID: 24531 Summary: Streamability of NodeComp, is operator Product: XPath / XQuery / XSLT Version: Last Call drafts Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: XSLT 3.0 Assignee: mike@saxonica.com Reporter: abel.braaksma@xs4all.nl QA Contact: public-qt-comments@w3.org Since we have established that node identity of a streaming node is not deterministic, due to the fact that streaming itself is not deterministic, how do we determine node identity? Should we not simply prohibit node identity checks? It seems odd that we allow an instruction like <xsl:value-of select=". is ." /> to return false. However, due to the lacking determinism, this is possible. Along the same lines, if processors do not have a good way of checking node identity, they may resort to deep-equal comparison, which would end up consuming (I think we should prohibit this kind of operation). Perhaps we should be much cruder than we currently are and say that node identity comparison in a streaming environment is always false? This would prevent differences between processors, and might be too far-fetched, but at least it would be stable. Or forbid its use in streaming scenarios, so as not to tempt people from using it. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 5 February 2014 21:09:19 UTC