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:
Error 404 - Page Not Found
Suggested results
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:
-
On Intelligent File Systems, XQuery and the Cloud
Cloud computing has largely passed through it's hype phase - that period where all kinds of magical characteristics are applied to it because no one really knows that much about it, and is shifting to the real world scenarios where people are actually building clouds and finding the limitations therein (and the cycle goes through the Trough of Despair).
Despite this incipient skeptical phase, there are some significant reasons to think hard about the combination of cloud computing and XML Databases, especially those such as MarkLogic or eXist-db that combine the database with a web app server. There are many ways of using such servers, though I believe one of the most powerful is to use a RESTful Services approach in conjunction with URL rewriting in order to create intelligent file systems.
-
Thoughts on Client side XQuery and Android
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.
-
XML, UML and the Zen of Data Modeling
Editor Note: This was originally from May 28, 2010
I've been rather conspicuous of late in the absence from my own site. I can cite moving cross country, starting a new job with a contractor working with a major US archival agency, house hunting, and the stresses related from all of these in that absence, but as things slowly begin to settle down here, I'm hoping to get back to writing regularly for XMLToday.org and elsewhere.
Shortly after starting (within an hour of arriving at my new workplace, in fact), I was handed a dozen or so schemas, generated from UML documents, that were being used to drive an application for the client, and told that my job was to manage them. Over the course of the last two months, this task has turned into a fairly deep, soul searching experience about what exactly we mean by data modeling, and has left scars that will likely take years to heal.
-
Discrete Resource: a definition in support of XRX
Editor Note: This was first published on Nov. 23, 2009.
Here at XML Today there is a strong and laudable push to promote XRX architecture. However, the very loosely defined REST architectural style leaves us a little short on best practice recommendations.
REST is usually presented as "Many nouns, few verbs," with the assumption that, because we know the verbs inside and out, we're going to save time and write simpler code. But really, we don't - we can't - know all of the HTTP verbs as thoroughly as we'd like.
Grappling with that particular problem yields one very basic architectural concept, the Discrete Resource. The characteristics of the Discrete Resource follow pretty naturally from consideration of the HTTP methods GET, PUT, and DELETE.