- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 15 Sep 2006 09:39:12 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3661 ------- Comment #2 from frans.englich@telia.com 2006-09-15 09:39 ------- Consider this scenario: A user constructs nodes with element constructors, and then later on filters them with path expressions(indirectly, perhaps as part of other nodes). One implementation do this fine, but another one has decided to generate anonymous element types for the constructed nodes and therefore fail. What I find interesting about XQuery is that it's an XML-aware, statically-typed, "real" programming language. But I don't see where the XPST0005-mechanism fits in. It isn't a well-crafted typing feature, it is a free-card which says "Do whatever you like". If one knows what static error checking is about -- spec it. If not, what potential problems aren't you not missing then? XQuery 1.0 isn't the end of the world, but what you put in it you can't pull out, which can pose a problem to XQuery 1.Next. I'd rather see real static error features in XQuery 1.Next.
Received on Friday, 15 September 2006 09:39:21 UTC