deletions | additions       diff --git a/A flexible container for paleoclimate data.tex b/A flexible container for paleoclimate data.tex  index 98dbecf..e4217f3 100644  --- a/A flexible container for paleoclimate data.tex  +++ b/A flexible container for paleoclimate data.tex 
...
\end{enumerate}  LiPD encodes these data and metadata into a structured hierarchy that allows explicit description of any aspect of the dataset at any level of the data (Figure 1). LiPD serializes this hierarchy using JSON-LD, using nests of lists and key-value pairs. LiPD would describe the geospatial metadata of site like this:  \begin{verbtim}  "geo": {| {  "latitude": {| {  "units": "decimalDegrees",| "decimalDegrees",  "value": 62.08|  },| 62.08  },  "longitude": {| {  "units": "decimalDegrees",| "decimalDegrees",  "value": -17.82|  },| -17.82  },  "elevation": {| {  "units": "masl",| "masl",  "value": -1938.0|  }| -1938.0  }  "ocean": "Atlantic"| "Atlantic"  "siteName": "RAPiD-12-1K"| "RAPiD-12-1K"  }|\  \end{verbtim}  LiPD does not store the actual tabular data in the JSON-LD format, as this becomes increasingly verbose and inefficient with large data tables. Rather, the tabular data are stored in headerless comma separated value (CSV) files that are referenced and described by the JSON-LD file, like this: