I wasn't able to upload it but here's a really simple example of what JSON looks like.

{

  "squad": {
    "name": "Best Squad 2015",
    "email": "best@5starsquad.com",
    "url": "http://5starsquad.com",
    "picture": "amazing.png",
    "tagline": "We'll knock your socks off",

    "members": {
      "Scroll_Tro0L": {
        "steam_id": 1234125234523456,
        "role": "20-star general of sooper special forces",
        "email": "theman@5starsquad.com",
        "icq": "nobody uses icq anymore, just have a link to their steam profile instead",
        "remark": "ppl beware me"
      },

      "Sidekick": {
        "steam_id": 12423234234563,
        "role": "Tactical snack manager",
        "email": "donuts@5starsquad.com",
        "icq": false,
        "remark": "omg I'm FAMOUS!"
      }

    }

  }

}

I don't see the need for it tbh. There is a website that does all the hard work for you, https://www.armasquads.com it allows you to upload a png file and it will automatically convert to .paa file format.

Link is not open, how much? - "Url": "http://5starsquad.com", [^]

@kripto202 Awesome site! Got it bookmarked now. Nonetheless, there are many issues yet with squad.xml that need to be addressed. My suggestion here is that when BI gets around to modernizing it the best thing to do is to switch to JSON because of how outdated XML is. ArmA asks for a Squad URL; that's web jurisdiction. In web, XML is pretty much deprecated in favor of JSON.

There's a good bit of disagreement with this that's focused mostly on two points: 1. XML works fine, don't do anything to it (Including inconvenience to current squad.xml users) and 2. It's difficult to implement. Though XML does work fine, again, squad.xml as a whole needs to be addressed and revamped anyways. This leads into the second point, JSON is not difficult to implement at all. Every modern language can access JSON with ease.

Even with this, I don't want the focus to be lost from the 4 original points I made. JSON is simply the best choice for data transfer involving the web.

@Lex None of that information is real, it was all in jest.

In my opinion, the main problem is not in XML paa or png format logo. The problem is to find a place where to place the files XML (sqd_logo.paa, sqd_logo.png, squad.css, squad.dtd, squad.xml, squad.xsl). All of these files are needed for the proper page design XML. The two files enough (sqd_logo.paa, squad.xml) for the appearance of the logo in the game.
JSON change this rule?
Or for him, too, need sqd_logo.png and squad.xml, placed on Internet resource?

Hey guys, i'm the creator of armasquads.com :)

I would love this suggestion from a developer perspective.
But i also got a few concerns about this suggestion.

Pro:
+ Less Traffic as XML generates a lot of unnecessary information/control strings
+ Mostly easy to ready

Con:

• Many users love the feature that you can style your xml for frontend use
• JSON needs special character escaping to not break the hole json file

So i don't see any major reasons that switching to JSON is currently better then XML.

But to be fair, xml got equal shit problems.

From a developer perspektive i would love this - from a normal non-tech user perspective this makes creating Squad Files "worse" and removes a feature that many users love - styling there xml.