<feed xmlns="http://www.w3.org/2005/Atom" xmlns:foaf="http://xmlns.com/foaf/0.1/"><title>norman.walsh.name: Comments on /2008/07/02/xquery</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/07/02/xquery"/><id>http://norman.walsh.name/2008/07/02/xquery/comments.atom</id><updated>2012-02-13T04:37:32.081366Z</updated><entry><title>Comment 1 on /2008/07/02/xquery</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/07/02/xquery#comment0001"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0001</id><published>2008-07-03T01:34:28Z</published><updated>2008-07-03T01:34:28Z</updated><author><name>Micah Dubinko</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>Besides casting to xs:string, there's also good old fn:string(), which has some recursive benefit. -m</p>
  </div></content></entry><entry><title>Comment 2 on /2008/07/02/xquery</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/07/02/xquery#comment0002"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0002</id><published>2008-07-03T07:09:05Z</published><updated>2008-07-03T07:09:05Z</updated><author><name>Dave Pawson</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>So what is it good at Norm? You've listed the odd bits. Does it have any real use, better than xslt 2 areas?</p>
  </div></content></entry><entry><title>Comment 3 on /2008/07/02/xquery</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/07/02/xquery#comment0003"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0003</id><published>2008-07-03T11:25:07Z</published><updated>2008-07-03T11:25:07Z</updated><author><name>Ed Davies</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p><i>The problem is that the element name “&lt;l:someothername/&gt;” in an actual XML document </i>can never<i> be in no namespace.</i>
</p>
    <p>
Is it possible that, in this instance, it's XML that's broken, not XQuery?  
</p>
    <p>
Having a default namespace for the bulk of your markup but being able to insert a few no-namespace elements doesn't seem completely ridiculous to me though, of course, you might want to ask why the inserted elements aren't in a namespace.  A possible use case would be an XSLT stylesheet which generates no-namespace documents where you could avoid all the xsl: prefixes.</p>
  </div></content></entry><entry><title>Comment 4 on /2008/07/02/xquery</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/07/02/xquery#comment0004"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0004</id><published>2008-07-03T13:33:02Z</published><updated>2008-07-03T13:33:02Z</updated><author><name>Bob DuCharme</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>My main difficulty with XQuery, which I think is reflected a bit in your posting, is that it's a few different syntaxes combined, and if I haven't coded in it in a few months I get confused about which bits are supposed to go where--for example, when to use XML comments and when to use the adorable smiley face comments. (Idiosyncratic as perl is, I don't have that problem there.) But remember, XQuery wasn't designed to appeal to XML people; it's the XML manipulation program for people who don't like XML, with its curly braces and semicolons (just like a real programming language!) and the "SQL-like" keywords. </p>

<p>I don't <i>hate</i> XQuery, like I hated, say, Omnimark syntax, but I find it a bit frustrating at times. The real power is in the implementations: the ability to retrieve subsets of gigabytes of indexed XML purely based on element and attribute conditions, with no need for the storage program to "chunk" the storage into something that it can map to its legacy document storage technology. </p>
  </div></content></entry><entry><title>Comment 5 on /2008/07/02/xquery</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2008/07/02/xquery#comment0005"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0005</id><published>2008-07-14T06:59:47Z</published><updated>2008-07-14T06:59:47Z</updated><author><name>Chris Wallace</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>Interesting to hear about your encounters with XQuery syntax here and via Twitter.  I've just added a few of your gotchas to 
</p>
    <p>
http://en.wikibooks.org/wiki/XQuery/Gotchas
</p>
    <p>
in the XQuery Wikibook which you may like to improve.
</p>
    <p>
This XQuery resource is mainly examples of simple applications I'm interested in but I'm working on a new section focused on patterns of XQuery application design. The book is rather  eXist focused because that's my environment but I'd like to be able to include some Mark Logic examples, perhaps as comparative implementations of the same problem.</p>
  </div></content></entry></feed>

