I suggest you ...

YAML "in addition to" JSON

YAML is recursive acronym of "YAML ain't a markup language"

YAML specs: http://www.yaml.org/spec/
File extension: .yml or .yaml

Why YAML:

Microsoft was backing XML, while the whole (other) world moved from XML to JSON (a key-value pair format with less footprints and noise). Microsoft was _still_ backing XML while the rest of the world move from JSON to YAML (another key-value pair format with minimalistic footprints and noise).

All those folks suggesting "JSON is new XML" must be living in pervious century: JSON is OLD XML and YAML is new JSON!

In VS2013 Update 2, Visual studio team (with WebDev) added native support for JSON and since then lot of things are move from XML to JSON.

Please add YAML's native support in VS using this robust and feature-complete libyaml: http://pyyaml.org/wiki/LibYAML.

To all VS teams, instead of JSON, please consider YAML for next-gen stuff.

How would the validation work:

Mads Kristensen, web tools project manager @MS created this repository for JSON store http://schemastore.org/ (github repo: https://github.com/madskristensen/SchemaStore). So now if your JSON has the same name as specified by the schema, the VS editor will validate your code with schema as well as provides you with intellisense.

In a similar manner, the schema validations for YAML can be implemented.

21 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    AdeelAdeel shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    6 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • TinaTina commented  ·   ·  Flag as inappropriate

        Points for YAML support. But replacing JSON with YAML is not the ideal case.

        @Eric, who mentioned politics? Your analogy doesn't make sense either! The real data is; Ruby, Python and Linux communities are using YAML a lot. The reason they prefer YAML over JSON is that it has less mess.

      • EricEric commented  ·   ·  Flag as inappropriate

        @Adeel I think the phrase "while the rest of the world move{d} from JSON to YAML" is overly broad and probably not accurate.
        This isn't politics. Let's use real data and examples to make our points -- not hyperbole.

      • EricEric commented  ·   ·  Flag as inappropriate

        From what I've seen, YAML is losing favor while JSON is gaining. I can't say that YAML would be useless, because it obviously has features that JSON lacks (since it is a superset), but I think there are a lot of other priorities for MS to focus on.

      • NathanNathan commented  ·   ·  Flag as inappropriate

        jake: dude I have to disagree. Its brackets + semicolons vs indentation. This sounds like a good tradeoff to me, in terms of least noise.

        Besides, what's wrong with the built-in yaml editor in visual studio?

      • jakejake commented  ·   ·  Flag as inappropriate

        god please no....
        xml = too noisy
        yaml = too terse
        json = good tradeoff

        period.

      Feedback and Knowledge Base