Simplification of json rules as per Pat's suggestion.

Author: msdemlei

DALI.tex

@@ -594,12 +594,12 @@ \section{Data Types and Literal Values}
 interoperable and metadata-rich VOTable constructs can be employed
 instead.
 
-In the following, where we say \verb|datatype="char"| we also allow the VOTable 
-\verb|datatype="unicodeChar"|. Where we say \verb|arraysize="*"| we also allow 
-providers to be more explicit by using a fixed size (e.g. \verb|20|) or fixed 
+In the following, where we say \verb|datatype="char"| we also allow the VOTable
+\verb|datatype="unicodeChar"|. Where we say \verb|arraysize="*"| we also allow
+providers to be more explicit by using a fixed size (e.g. \verb|20|) or fixed
 with a limit (e.g. \verb|20*|) when applicable.
 
-In the following, where we say "VOTable type metadata", we mean either VOTable 
+In the following, where we say "VOTable type metadata", we mean either VOTable
 \xmlel{FIELD} or \xmlel{PARAM} elements.
 
 Services may use non-standard \xmlel{xtype} values for non-standard datatypes, but if they
@@ -619,7 +619,7 @@ \subsection{Boolean}
 values in service parameters, the serialization for \xmlel{TABLEDATA} must be used.
 
 \subsection{Timestamp}
-Timestamp values serialised in VOTable or described in service parameters must have 
+Timestamp values serialised in VOTable or described in service parameters must have
 the following VOTable type metadata:
 
 \begin{verbatim}
@@ -686,15 +686,15 @@ \subsection{Intervals}
 intervals have one or both bounding values that are infinite. Intervals with two identical values
 are equivalent to a scalar value but must still be serialised as a pair of values.
 
-Floating point interval values serialised in VOTable or described in service parameters must have 
+Floating point interval values serialised in VOTable or described in service parameters must have
 the following VOTable type metadata:
 
 \begin{verbatim}
 datatype="double" arraysize="2" xtype="interval"
 \end{verbatim}
 \noindent where \verb|float| is also permitted.
 
-Integer interval values serialised in VOTable or described in service parameters must have the 
+Integer interval values serialised in VOTable or described in service parameters must have the
 following VOTable type metadata:
 
 \begin{verbatim}
@@ -730,7 +730,7 @@ \subsection{Intervals}
 upper bound of interval(s) respectively.
 
 \subsection{Sexagesimal Coordinates}
-Coordinate values expressed in sexagesimal form can be described using the 
+Coordinate values expressed in sexagesimal form can be described using the
 following VOTable type metadata. For right ascension:
 
 \begin{verbatim}
@@ -747,25 +747,25 @@ \subsection{Sexagesimal Coordinates}
 values and seconds is a real value. All hours must fall within [0,24], degrees
 (latitude) must fall within [-90,90], minutes must fall within [0,60), and seconds
 must fall within [0,60). Leading zeros are permitted so that values of minutes and the integer
-part of seconds can be expressed as 2-digit numbers. Valid values for \verb|xtype="hms"| are 
+part of seconds can be expressed as 2-digit numbers. Valid values for \verb|xtype="hms"| are
 from 00:00:00 to 24:00:00.
 Valid values for \verb|xtype="dms"| are from -90:00:00 to 90:00:00; an optional + sign at
-the start is allowed (e.g. +10:20:30) but not required. The upper bound on minutes 
-and seconds is not part of the valid range; for example 12:34:60 is not allowed and must 
+the start is allowed (e.g. +10:20:30) but not required. The upper bound on minutes
+and seconds is not part of the valid range; for example 12:34:60 is not allowed and must
 be expressed as 12:35:00 instead.
 
 \subsection{Point}
 Geometry values are two-dimensional; although they are usually longitude and
 latitude values in spherical coordinates this is specified in the coordinate
 metadata and not in the values.
 
-Point values serialised in VOTable or described in service parameters must have following 
+Point values serialised in VOTable or described in service parameters must have following
 VOTable type metadata:
 
 \begin{verbatim}
 datatype="double" arraysize="2" xtype="point"
 \end{verbatim}
-\noindent where \verb|float| is also allowed. 
+\noindent where \verb|float| is also allowed.
 
 For points in a spherical coordinate system, the values are ordered as: longitude latitude. For example:
 
@@ -789,7 +789,7 @@ \subsection{Circle}
 \begin{verbatim}
 datatype="double" arraysize="3" xtype="circle"
 \end{verbatim}
-\noindent where \verb|float| is also allowed. 
+\noindent where \verb|float| is also allowed.
 
 The values are ordered as a point followed by a radius. For example:
 
@@ -814,11 +814,11 @@ \subsection{Circle}
 more limited context.
 
 \subsection{Range}
-Range values serialised in VOTable or described in service parameters must have the following VOTable type metadata: 
+Range values serialised in VOTable or described in service parameters must have the following VOTable type metadata:
 \begin{verbatim}
 datatype="double" arraysize="4" xtype="range"
 \end{verbatim}
-\noindent where \verb|float| is also allowed. 
+\noindent where \verb|float| is also allowed.
 
 A range is a coordinate bounding box specified
 as two pairs of coordinate values: min-coordinate1 max-coordinate1 min-coordinate2 max-coordinate2.
@@ -851,13 +851,13 @@ \subsection{Range}
 more limited context.
 
 \subsection{Polygon}
-Polygon values serialised in VOTable or described in service parameters must have the 
+Polygon values serialised in VOTable or described in service parameters must have the
 following VOTable type metadata:
 
 \begin{verbatim}
 datatype="double" arraysize="*" xtype="polygon"
 \end{verbatim}
-\noindent where \verb|float| is also allowed. 
+\noindent where \verb|float| is also allowed.
 
 The array holds a sequence of vertices (points) (e.g. longitude latitude longitude
 latitude ...) with an even number of values and at least three (3) points (six
@@ -994,15 +994,15 @@ \subsection{Shape}
 more limited context.
 
 \subsection{URI}
-URI values \citep{std:RFC3986} serialised in VOTable or described in service parameters 
+URI values \citep{std:RFC3986} serialised in VOTable or described in service parameters
 should have the type following metadata:
 
 \begin{verbatim}
 datatype="char" arraysize="*" xtype="uri"
 \end{verbatim}
 
 \subsection{UUID}
-Universal Unique Identifier (UUID) values serialised in VOTable or described in service parameters 
+Universal Unique Identifier (UUID) values serialised in VOTable or described in service parameters
 should have the following VOTable type metadata:
 
 \begin{verbatim}
@@ -1020,11 +1020,12 @@ \subsection{JSON}
 (e.g., as a \xmlel{GROUP} for a \xmlel{PARAM} or as unrolled
 \xmlel{FIELD}\/s or a separate table for table cells) is preferred.
 
-\xmlel{PARAM}\/s and \xmlel{FIELD}\/s containing JSON values should be
-marked up with a \xmlel{datatype} of \verb|char| or \verb|unicodeChar|,
-with variable or fixed \xmlel{arraysize} and an \xmlel{xtype} of
-\verb|json|.
+JSON values serialised in VOTable or described in service parameters should have
+the following VOTable type metadata:
 
+\begin{verbatim}
+datatype="char" arraysize="*" xtype="uri"
+\end{verbatim}
 
 \subsection{Unsupported Types}