OK - a quick Google search reveals that "common extension" is probably not the
right term. Apparently many parsers try to adhere to the quoted standard
strictly. However, others do not, and I would argue that it is better to
support both. I wouldn't want a potential use case for Pivot to be invalidated
because Pivot is unable to consume the JSON output that a non-compliant web
service produces. It also seems to be a common sentiment that the JSON standard
should support non-quoted keys.
On Wednesday, April 08, 2009, at 07:34AM, "Christopher Brind"
<[email protected]> wrote:
>To be honest, I'm not aware of what Pivot uses being a common extension,
>I've only ever seen it in Pivot.
>What Pivot actually seems to support is actually a hybrid of CSS and JSON,
>which is OK, but it makes answering questions like Sandro's quite
>subjective, IMHO
>
>
>Cheers,
>Chris
>
>
>2009/4/8 Greg Brown <[email protected]>
>
>> >This means that the existing JSON based preferences files are incorrect.
>> > They currently look like this:
>> >
>> >{
>> > key1 : "Value1",
>> > key2 : "Value2"
>> >}
>> >
>> >Really they should look like this:
>> >{
>> > "key1" : "Value1",
>> > "key2" : "Value2"
>> >}
>>
>> We support both styles. I believe this is a common extension to the JSON
>> standard. We also support single-quoted string values, because it is easier
>> to use them in WTKX:
>>
>> <Label styles="{color:'#ff0000'}"/>
>>
>>
>>
>
