Embrace YAML or Hedge on JSON

So I have an application that stores metadata in a set of files. The 
different types of data are revisioned in case a specification should 
change.

So presently an example could be:

    --- !resources,0
    - uri: foo.org
      label: Website
      type: home
    - uri: foo.org/docs
      label: Documentation
      type: doc

Notice the tag `!resources,0`. So this is revision 0 of the resources 
metadata specification.

That works fine. But, I am using YAML tags, so I am all in on YAML, and 
JSON could never be used in it's place. But I could adjust the spec to 
something like:

    --- 
    resources,0:
    - uri: foo.org
      label: Website
      type: home
    - uri: foo.org/docs
      label: Documentation
      type: doc
 
And now JSON could be used instead and it would work just as well.

So my question is, objectively and pragmatically, what would you choose? 
Would you fully embrace YAML? Or would you hedge your "tech investment" and 
support JSON too?

------------------------------------------------------------------------------
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/

_______________________________________________
Yaml-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yaml-core