Currently, I find myself in a similar situation as a non-expert in JavaScript, working on an exciting project to enhance my understanding of JavaScript, Ajax, and JSON.

To address the issue at hand, I implemented three distinct steps. Feedback on enhancing this solution is greatly appreciated.

The initial step involved querying the NFL site for retrieving scores. Given that the JSON source, which is the NFL site, differs from your own site, overcoming JavaScript's security constraints against cross-domain queries was necessary. Referencing a useful Stack Overflow link, I opted for a JSONP workaround using as the intermediary site.

$.getJSON('http://whateverorigin.org/get?url=' + encodeURIComponent('http://www.nfl.com/liveupdate/scorestrip/scorestrip.json') + '&callback=?', handleQueryForScoresResult);

It's worth noting that other users have highlighted the invalid JSON data returned by the NFL site. An example illustrating this issue is shown below:

["Sun","4:25","Final",,"TEN","7","MIN","30",,,"55571",,"REG5","2012"],

The presence of empty array elements (repeated commas without any data) prompted me to correct the data within my JSON callback function before parsing using jQuery:

function handleQueryForScoresResult(data) {
    var jsonStr = data.contents;
    jsonStr = jsonStr.replace(/,,/g, ',"",');
    jsonStr = jsonStr.replace(/,,/g, ',"",');

    var scoresData = jQuery.parseJSON(jsonStr).ss;
    .
    .
    .
}

Furthermore, I developed a GameScores object to encapsulate the JSON data effectively.

function GameScore(scoreData) {
    this.scoreData = scoreData;
    scoreData[2] = scoreData[2].toLowerCase();
    scoreData[5] = parseInt(scoreData[5]);
    scoreData[7] = parseInt(scoreData[7]);
} 

// Additional functions here...

GameScore.prototype.getHomeTeam = GameScore_getHomeTeam;
GameScore.prototype.getAwayTeam = GameScore_getAwayTeam;
// Continuing with additional prototype assignments...

In my implementation, I included only essential accessors based on my requirements, but these can be adjusted according to one's specific needs.

Utilizing MooTools for tasks of this nature, though achieving the same results is achievable using pure JavaScript as demonstrated here: http://www.json.org/js.html.

Let's say you have a valid JSON String called jsonString that needs to be parsed. (If you're unsure how to get a String for parsing using XMLHttpRequest from a specific URL, you'll need to research that first.)

If you're working with plain JavaScript, you may need to include Douglas Crockford's JSON library (or something similar) to have a parsing Function if there isn't a native implementation available:

var json = json_parse(jsonString);

• link

Using a JavaScript library like jQuery, the process would look like this:

var json = $.parseJSON(jsonString);

Next, navigating through the resulting JSON Object can be challenging as you must understand its structure before extracting specific data. In the case mentioned here - presuming it is well-structured - the following steps are necessary:

var data = json.ss;

     for(var i = 0; i < data.length; i++) {

          var entry = data[i];

          var day = entry[0]; // The Arrays appear to follow a pattern where the first entry holds the data
          /* ... */

          // Proceed to handle the extracted data

     }

The main issue lies in the fact that the JSON you are fetching is either malformed or does not adhere to RFC 4627 standards.

To rectify this, you can copy the JSON data and utilize a formatting tool such as to structure it properly.

Once you have formatted the data, you can proceed to make an ajax call using jQuery:

$.ajax({
    url: "your-formatted.json",
    dataType: 'json',

    success: function (data) {

        for (var i = 0; i < data.ss.length; i++) {
            document.write("Day: " + data.ss[i][0]);
            document.write("<br/>");
            document.write("Time: " + data.ss[i][1]);
            document.write("<br/><br/>");
        }
    }
});

It's important to note that using document.write in your actual application is not recommended. The usage here is solely for demonstration purposes to showcase how the data is displayed.

To address the issue of empty indexes within arrays from the JSON response, I implemented a regex replacement technique utilizing a lookahead assertion. In situations where the request involves the XMLHttpRequest:

request.responseText.replace(/,(?=,)/gm, ",\"\"")

This approach effectively transforms instances of ,, into ,"",, and can also handle scenarios with multiple commas in sequence, such as ,,, being converted to ,"","",. Following this transformation, one can proceed to use JSON.parse() on the modified data.

If you encounter malformed JSON, fear not! The dirty-json NPM package (crafted by yours truly) can come to the rescue.

To see this miracle worker in action, head over to:

Your original JSON quandary is no match for this parser as it magically transforms it into a readable format like so:

{
    "ss": [
        [
            "Thu",
            "7:00",
            "Final",
            "BAL",
            "19",
            "ATL",
            "20",
            "56808",
            "PRE4",
            "2015"
        ],
        [
            "Thu",
            "7:00",
            "Final",
            "NO",
            "10",
            "GB",
            "38",
            "56809",
            "PRE4",
            "2015"
        ]
    ]
}