Sorry, I've looked everywhere but I can't find the page you're looking for.
If you follow the link from another website, I may have removed or renamed the page some time ago. You may want to try searching for the page:
Sorry, I've looked everywhere but I can't find the page you're looking for.
If you follow the link from another website, I may have removed or renamed the page some time ago. You may want to try searching for the page:
I've done a courtesy search for the term for you. See if you can find what you're looking for in the list below:
To a certain extent, I think those people that are looking to get XQuery into the browser are tilting at windmills, and frankly are wasting their time. It's not that I don't see advantages to having browsers be XQuery aware - far from it. The ability to both manipulate the DOM and to manipulate external data resources using XQuery would dramatically simplify a lot of the code written in JavaScript. The problem is that the JavaScript does exist, is in wide usage, and I see a language like Python or Ruby making its way into the browser before I see XQuery doing so. Building a JavaScript-based Xquery system is probably the cleanest approach to getting that support, but even that's probably a fool's errand.
Editor Note: This was first publishing Nov. 23, 2009.
And no. I'm not going to start out with "It was the best of times, it was the worst of times". But I will tell you what kind of time it was.
It was a big damn Gold Rush.
As gold rushes tend to do, it made a mess of a lot of things; some got rich and most didn't, and those who were already wealthy figured out how to take advantage of the situation. And there's one other major thing that gold rushes do: they tend to tilt balances.
Enthusiatic people about XQuery are numerous and I remember XML Prague 2010 as mainly about XQuery. I also often read that XQuery is much easier for beginners than XSLT.
Nevertheless, there is still no XQuery cross-implementation for browsers without plug-in. This was a problem for XForms too, until products such as XSLTForms or Ubiquity XForms appeared. The no-plugin constraint implies to use what is natively implemented in browsers: Javascript, of course, but also XSLT 1.0 as proved by XSLTForms.
A first step is to consider XQuery for rendering: XQuery is, surely, very good to generate well-formed HTML from XML data.
Editor Note: This was originally published 30 October 2009.
One of the more problematic issues involved with working with XML Databases is what may seem to be relatively simple - getting files into the database in the first place. This was one of the challenges that was put to me by Dan McCreary for a series of open source applications that he's developing around the eXist XML database as part of his efforts with Syntactica. While you can use WebDAV (and in general probably should for production level work), a generalized file uploader web app is also possible, and serves to illustrate how you can actually create some very powerful tools with application vendor augmented XQuery. Note that the examples given here are all built around the eXist-db XML Database. It's definitely possible to do similar applications using the MarkLogic database, though I'll leave this as an exercise for a future article.
... and we're back.
XML Today has been an exercise in discovering the limits of what PHP can do in handling content management systems. This site has run under Drupal and (very briefly) Joomla, and after having the last couple of months of content wiped out by an errant database error during a system upgrade on the previous system, it seemed like a good time to give WordPress a try.
The mission remains (more or less) the same ... cover what's going on in the XML Community, explore evolving technologies such as XQuery, XProc and the Semantic Web, and provide help and discussion about the technical and developmental aspects of XML.