the eXist XML database: a perfect couple", Bruchez showed that many people were discovering synergistic benefits of XForms on the client and XQuery on the server. The label for XRX was suggested by a blog posting by Dan McCreary on December 14, 2007. It was in this article that Dan suggested the need for a contagious meme for the ideas behind the XRX architecture. Generalizations of XRX Although XRX was originally intended to connote the use of XForms on the client, REST as an interface and XQuery on the server, other proponents of the symmetrical use of XML on the client and server have generalized the term to encompass any XML-centric web client and any server that can store and query XML documents. This use of XRX is generally referred to as "shallow XRX". These generalizations do benefit from a simplified zero-translation architecture but many do not benefit from REST interfaces, XPath for consistent data selection, declarative systems in the client, and functional languages on the server (one of the key aspects of XRX). Use of all three technologies (XForms, REST and XQuery) is referred to as "deep XRX". Although XRX architecture is centred on XForms and XQuery, it does not preclude the use of other technologies that manipulate XML natively, such as XSLT, XProc, and XSL-FO. See also Web application framework References Additional Resource XRX: Simple, Elegant, Disruptive by Dan McCreary Google Code repository for XRX developers Metaphorical Web and XRX by Kurt Cagle XRX Queries using the eXist database by Jeni Tennison XRX Mapping URLS with Orbeon Forms by Jeni Tennison XRX Performing Updates by Jeni Tennison XRX Locking Grain Design by Dan McCreary XRX Wikibook XRX Wikibook with tutorials for creating CRUDS application using the eXist database The Agile Stack by Jason Monberg Jesse Alama's Blog on XQuery and XRX Web applications Software architecture