Fwd: Embrace YAML or Hedge on JSON

On Mon, Aug 6, 2012 at 12:36 PM, john saylor <[email protected]> wrote:
> maybe thinking of trade-offs will help. what do you lose by dropping
> json support?

I wan to make it as easy as possible for people to access this data.
Ideally they only need to do `YAML.load_file(file_name)` (in Ruby),
and they have all the info they need. Thinking about it that way makes
me realize that tags probably won't work anyway because the consuming
application would have to be setup already to comprehend them --
Ruby's YAML implementation uses global registration to handle tags and
doesn't provide a way to simply query this information after loading.
That sucks. I don't know, but I assume it is the same for other
implementations.

On the emitter side, if an app wants to generate the metadata files
they could output JSON instead of YAML and it would be okay since JSON
is a subset of YAML.

I am still debating whether to use extensions `.yaml` or `.json` for
these files, or just require that YAML always be used to load them and
not require an extension.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/