backslashes in URLs

[NARKOZ]

"spec":"http:\/\/www.w3.org\/TR\/WOFF\/",
"url":"http:\/\/hacks.mozilla.org\/2009\/10\/woff\/",

Is it for escaping? According to http://www.ietf.org/rfc/rfc4627.txt it's not really required.

[CWSpear]

I think part of the confusion comes from the more easier to understand http://json.org, where it says the forward slash (or solidus, I guess? I've never heard that word) is to be escaped (see diagram defining a string). Update: I guess you could interpret that escaping the forward slash is optional from what it says, but from looking at it, I would definitely escape them, as that's definitely "legal."

Some languages seem to escape the forward slash, like PHP's json_encode(), while other's do not, like Chrome's (and I'm sure others') implementation of JSON.stringify().

I would guess that not all of the JSON is hand authored on caniuse, and that they are using something to encode a more manageable object/array and then encoding it to JSON for the site.

It should be noted, both methods mentioned above were able to correctly decode/parse JSON with and without escaped forward slashes.

[Fyrd]

Yeah, this was unintentional, and has now been fixed. Thanks for pointing it out! :)