Skip to content

Commit 69e35da

Browse files
committed
credit @dmccreary with coining XRX
1 parent ad41043 commit 69e35da

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

src/main/xar-resources/data/beginners-guide-to-xrx-v4/beginners-guide-to-xrx-v4.xml

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -120,12 +120,14 @@
120120
<emphasis role="bold">XRX</emphasis> is the name of the web
121121
application architecture that we are introducing in this guide.
122122
The term XRX comes from the combination of XForms, REST, and
123-
XQuery. The term was coined by Dan McCreary. XForms are used in
124-
the client (web browser), REST is the interface between the
125-
client and the server, and XQuery is the server language. Two of
126-
the most significant advantages of XRX over other architectures
127-
are: (1) it does not require users to translate data into Java
128-
or .Net objects, and (2) it does not require users to "shred"
123+
XQuery. The term was <link
124+
xlink:href="http://archive.oreilly.com/pub/post/xrx_a_simple_elegant_disruptiv_1.html"
125+
>coined</link> by Dan McCreary. XForms are used in the
126+
client (web browser), REST is the interface between the client
127+
and the server, and XQuery is the server language. Two of the
128+
most significant advantages of XRX over other architectures are:
129+
(1) it does not require users to translate data into Java or
130+
.Net objects, and (2) it does not require users to "shred"
129131
documents into rows of a relational database.</para>
130132
<para>
131133
<emphasis role="bold">XForms</emphasis> is a W3C standard to define the structure of a web form. XForms is much more advanced than traditional

0 commit comments

Comments
 (0)