On Aug 18, 2008, at 07:03, Ovid wrote:
Those are certainly important issues, but JSON will make some of them trivial. The YAML types, embedded documents and the "one format to rule them all" concept is precisely what makes it unsuitable for TAP. That's a damned shame because if there was something useful like a "core YAML" spec which could be followed along the lines of JSON, I would prefer it.
Given that JSON is arguably a subset of YAML, one could call it a "core YAML" spec. ;-)
Best, David
