JSON files are text files – so they are definitely “human readable”. Comprehension might be low, depending on who’s doing the reading, but the content, like XML (except for embedded binary encoded data) is readable.
A sample JSON structure – with phony data – of a person’s entry in a CRM database follows. One could read this and get an idea of what’s going on. Obviously, though, this is structured for behind-the-scenes use by the CRM program.
[
{
"_id": "60bd1f16b27db261489021d5",
"index": 0,
"guid": "e1c11565-15cc-4c28-b78e-c80f8c75841e",
"isActive": true,
"balance": "$3,789.55",
"picture": "http://example.it/32x32",
"age": 30,
"eyeColor": "brown",
"name": "Mercer Ward",
"gender": "male",
"company": "INDEXIA",
"email": "mercerward@example.com",
"phone": "+1 (212) 555-1212",
"address": "111 Main Street, Anytown, Michigan, 1704",
"about": "Veniam proident Lorem exercitation anim incididunt aliqua nulla duis mollit laborum minim. Aute magna mollit deserunt irure consectetur cillum velit. Mollit minim do incididunt sint. Ex velit exercitation et et. Id fugiat velit sint non laboris occaecat mollit. Culpa quis veniam aliqua elit sit mollit officia ad do ut elit esse culpa in. Eu exercitation consectetur ea deserunt consectetur elit commodo aliqua ipsum mollit.\r\n",
"registered": "2015-11-10T01:01:13 +05:00",
"latitude": 86.408155,
"longitude": 154.400167,
"tags": [
"laboris",
"excepteur",
"est",
"in",
"esse",
"dolore",
"commodo"
],
"friends": [
{
"id": 0,
"name": "Evelyn Briggs"
},
{
"id": 1,
"name": "Concepcion Frank"
},
{
"id": 2,
"name": "Fran Hood"
}
],
"greeting": "Hello, Mercer Ward! You have 7 unread messages.",
"favoriteFruit": "apple"
}
]