On Tue, Dec 10, 2013 at 4:12 PM, Carsten Bormann <[email protected]> wrote:
So a JSON infoset would capture a processed AST, but not yet the > transformation to the data model level. > > JSON implementations would create the JSON data model from that infoset > (typically without actually reifying the latter as an AST), and JSON > extensions like ECMAscript's would be free to do whatever they want. > It is just important to distinguish the two, so people don’t confuse the > data model with the infoset, or think that a JSON implementation needs to > provide access to the infoset. I agree it would reduce confusion to use a different term for the infoset versus the data model. "Infoset"/"data model" is one possible choice of terms, though I wonder whether the XML heritage of "infoset" might be off putting to many. Another possibility would be "abstract data model"/"concrete data model". > I’d argue that you want to reduce toward the denominator being the minimal > power of ten, i.e. > 1 is [1, 1] > 1.0 is [1, 1] > 1.5 is [15, 10] > That would be my preference too. The only thing that makes me hesitate is that I could imagine implementations that distinguish integers and floats, and use C-style rules to distinguish the two. For example, 1 is an integer but 1.0 or 1e0 is a float. I don't know whether any such implementations exist. James
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
