[Rprotobuf-commits] r840 - papers/jss

[noreply at r-forge.r-project.org]

Author: jeroenooms
Date: 2014-01-23 05:09:38 +0100 (Thu, 23 Jan 2014)
New Revision: 840

Modified:
   papers/jss/article.Rnw
Log:
Switch around a sentence to get a better flow

Modified: papers/jss/article.Rnw
===================================================================
--- papers/jss/article.Rnw	2014-01-23 03:42:24 UTC (rev 839)
+++ papers/jss/article.Rnw	2014-01-23 04:09:38 UTC (rev 840)
@@ -179,15 +179,15 @@
 applications.
 %
 
-A more modern, widely used format is \emph{JavaScript Object
-  Notation} (\texttt{JSON}), which is derived from the object literals of
-\proglang{JavaScript}, and used increasingly on the world wide web. \texttt{JSON} natively
-supports arrays and distinguishes 4 primitive types: numbers, strings,
+A more modern, widely used format is \emph{JavaScript ObjectNotation} 
+(\texttt{JSON}), which is derived from the object literals of
+\proglang{JavaScript}, and used increasingly on the world wide web. 
+Several \proglang{R} packages implement functions to parse and generate
+\texttt{JSON} data from \proglang{R} objects \citep{rjson,RJSONIO,jsonlite}.
+\texttt{JSON} natively supports arrays and 4 primitive types: numbers, strings,
 booleans, and null. However, as it too is a text-based format, numbers are
 stored as human-readable decimal notation which is inefficient and
-leads to loss of type (double versus integer) and precision. Several \proglang{R} packages
-implement functions to parse and generate \texttt{JSON} data from \proglang{R}
-objects \citep{rjson,RJSONIO,jsonlite}.
+leads to loss of type (double versus integer) and precision. 
 A number of binary formats based on \texttt{JSON} have been proposed
 that reduce the parsing cost and improve efficiency, but these formats
 are not widely supported.  Furthermore, such formats lack a separate