24436 2014-01-29 09:52:23 +0000 [XSLT 3.0] Poorly-designed JSON example 2014-02-24 15:51:53 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Last Call drafts PC All CLOSED FIXED P2 normal --- 1 mike mike fgeorges public-qt-comments oldest_to_newest 99393 0 mike 2014-01-29 09:52:23 +0000 The JSON example in 21.2.1 is rather inelegant in that the only array it contains (the phone numbers) contains a single entry (a map), and it's not clear why an array is needed here. It's legal JSON, but not a very good example. 99494 1 fgeorges 2014-01-30 20:06:41 +0000 (In reply to Michael Kay from comment #0) > The JSON example in 21.2.1 is rather inelegant in that the only array it > contains (the phone numbers) contains a single entry (a map) It looks like it is an adaptation of an example I've sent on the mailing list, which I took from the Wikipedia page for JSON <http://en.wikipedia.org/wiki/JSON>. But the value of the array has been changed from: "phone numbers" : [ { "type": "home", "number": "212 732-1234" }, { "type": "fax", "number": "646 123-4567" } ] to: "phone numbers" : [ { "home": "212 732-1234", "fax": "646 123-4567" } ] The first one looks legitimate to me, WRT having an array. I can try and come with another example, but this one (with the above modification) looks good to me. By the way, the example also uses spaces in the names. As far as I can see, this is valid syntax, but I guess it would generate an error if someone tries to parse it as a Javascript object. Do we want to remove spaces in names? 99667 2 fgeorges 2014-02-04 18:54:29 +0000 Another candidate, self-explanatory, with strings, numbers, a date-time, a boolean, null, objects, and legitimate arrays: { "desc" : "Distances between several cities, in kilometers.", "updated" : "2014-02-04T18:50:45", "uptodate": true "author" : null "cities" : { "Brussels": [ {to: "London", distance: 322}, {to: "Paris", distance: 265}, {to: "Amsterdam", distance: 173} ], "London": [ {to: "Brussels", distance: 322}, {to: "Paris", distance: 344}, {to: "Amsterdam", distance: 358} ], "Paris": [ {to: "Brussels", distance: 265}, {to: "London", distance: 344}, {to: "Amsterdam", distance: 431} ], "Amsterdam": [ {to: "Brussels", distance: 173}, {to: "London", distance: 358}, {to: "Paris", distance: 431} ] } } 99703 3 mike 2014-02-04 23:07:21 +0000 Thanks. But the "to" and "distance" should be in quotes, surely? 100330 4 fgeorges 2014-02-11 21:42:02 +0000 I used plain JavaScript notation, which does not require to quote object member names when they follow the rules for variable names. But from http://tools.ietf.org/html/rfc4627, it seems you are right and quotes are indeed required for names, always. 100967 5 mike 2014-02-20 16:46:25 +0000 I have used the example in comment #2, with quotes added to make it legal.