W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2010

[Bug 8791] [XPath21] Allowing intermediate XPath steps to return atomic values

From: <bugzilla@wiggum.w3.org>
Date: Fri, 22 Jan 2010 01:05:43 +0000
To: public-qt-comments@w3.org
Message-Id: <E1NY7y3-0006Vc-Vo@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8791





--- Comment #2 from Mukul Gandhi <gandhi.mukul@gmail.com>  2010-01-22 01:05:43 ---
Hi Mike,
  Thanks for the answer.

(In reply to comment #1)
> It still leaves the problem of (1/2).
Can't we treat this case, as returning an empty sequence (i.e, if both lhs &
rhs of "/" are atomic values)?

btw, I'm now slightly inclined to think, that the current design (i.e, allowing
only last step of XPath expression, to have atomic values) is probably correct.
An XPath (2.x) expression essentially has to select nodes from an input XML
document (it may though return atomic values, from 2.x onwards).

Allowing something like, /atomic_value(s)/node(s) (or,
/atomic_value(s)/atomic_value(s)) is like enhancing mathematical capability of
the language, and not adhering to the design principles of XPath (which is,
essentially to select nodes from input document. Or more correctly, a sequence
of XDM item values, in XPath 2.x).

I'm now inclined to take my comment back.

Regards,
Mukul 


-- 
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 Friday, 22 January 2010 01:05:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:41 UTC