Along with the Notes 8 beta comes the updates to the outputformat=JSON parameter that they unveiled. Here’s some snippets for a quick example.
Notes 7.0.2
{“@toplevelentries”: 208,
viewentry: [
...
{"@position": '57',"@unid": '6925F9DFB92E6BB9862572200057745B',"@noteid": '9D6',"@siblings": 208,entrydata: [
{"@columnnumber": 0,"@name": 'Player',text: {0: 'Terrell Owens'}},
{"@columnnumber": 1,"@name": 'Sport',text: {0: 'Football'}},
{"@columnnumber": 2,"@name": 'Team',text: {0: 'Dallas Cowboys'}},
{"@columnnumber": 3,"@name": 'Jersey',number: {0: 81}},
{"@columnnumber": 4,"@name": 'Salary',number: {0: 5000000}},
{"@columnnumber": 5,"@name": 'Created',datetime: {0: '20061108'}},
{"@columnnumber": 6,"@name": 'Last Modified',datetime: {0: '20061108T095514,55-06'}}
]},
…
]}
Notes 8 Beta 2
{“@toplevelentries”: “112″,
“viewentry”: [
{"@position": "1","@unid": "144B24CCC71E3DF18525725E00596ADA","@noteid": "A42","@siblings": "112","entrydata": [
{"@columnnumber": "0","@name": "Player","text": {"0": "Terrell Owens"}},
{"@columnnumber": "1","@name": "Sport","text": {"0": "Football"}},
{"@columnnumber": "2","@name": "Team","text": {"0": "Dallas Cowboys"}},
{"@columnnumber": "3","@name": "Jersey","number": {"0": "81"}},
{"@columnnumber": "4","@name": "Salary","number": {"0": "5000000"}},
{"@columnnumber": "5","@name": "Created","datetime": {"0": "20070109"}},
{"@columnnumber": "6","@name": "Last Modified","datetime": {"0": "20070109T111640,60-05"}}
]},
…
]}
Some newlines have been stripped to shorten things a bit. Anyhow, someone said before that they would be dropping the @ as it doesn’t translate well to javascript (and doesn’t allow direct access to the properties of the serialized object) but that doesn’t appear to be the case. They updated all the attribute names and values to make sure everything is enclosed in double quotes. They also changed the content type from “application/x-javascript” to “application/json”.
Looks like the updates are as promised, and this should not require any code updates for those who implemented code on the 7.0.2 version. 
- Heavily moderated, SPAM will be dealt with.
Rich, thanks for posting this… I’d been meaning to find out what had changed, and it’s a relief to know the syntax is essentially the same, albeit a bit annoying that we’ll have to continue using array syntax instead of dot syntax to reference attributes.
Tim Tripcony
March 16th, 2007
Yea, I personally find the blah.["@toplevelentries"] syntax a bit annoying as well. I’ve been considering customizing a json parser a bit to strip out the ‘@’ signs so we could just use blah.toplevelentries… I figure some performance testing would be in order to see if it takes more time to access the properties via the array syntax vs. the extra conversion time when parsing the string.
Rich Waters
March 18th, 2007