deletions | additions       diff --git a/Discussion.tex b/Discussion.tex  index 326ec0c..f200f18 100644  --- a/Discussion.tex  +++ b/Discussion.tex 
...
The data container and preliminary data standard described here are extremely flexible, and can accomodate any paleoclimatic or paleoenvironmental data that are based on any expansion of dependent/independent variable pairs. This encompasses all paleoclimate and paleoenvironmental datasets that we can imagine. The challenge for developing a sufficiently broad paleodata framework has long been 1) defining all of the relevant terms for such a diverse community and 2) managing the appropriate level of detail (lumping versus splitting) in the terminology. The framework presented here accommodates the first challenge by being extensible to accommodate the complexity and inevitable proliferation of terms, variables and interpretations, and by assigning explicit meaning to the terms through the Open Linked Data framework. Implementation of these semantics will be an evolving, community-driven process; which is critical, since defining an ontology \textit{a priori} has proven impossible to date.   The LiPD framework accomodates the second challenge by adopting a hierarchical structure, that starts with more general terminology and allowing further detail to be assigned deeper in the structure. Consider the example of two $\delta$^{18}O datasets, one measured on a coral archive, and the other derived from foraminifera extracted from a marine sediment core. On one hand, these two records are measuring the same parameter, and there are times when researchers might be interested in investigating all $\delta$^{18}O regardless of the details of how they were measured. On the other hand, there are some important differences between the two measurements that users would like to include in the data repository. If we were trying to describe each parameter in a single term, we'd have to decide whether to call them both "$\delta$^{18}O", or to call one "$\delta$^{18}O-skeletal aragonite" and the other "$\delta$^{18}O-foraminfera >120$\mu$m size class". By taking advantage of JSON's capacity to build hierarchical metadata structures, we can encode these as  Points to hit :