- From: Olivier Grisel <olivier.grisel@ensta.org>
- Date: Mon, 3 Oct 2011 16:38:01 +0200
- To: Ivan Herman <ivan@w3.org>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, Manu Sporny <msporny@digitalbazaar.com>, "public-linked-json@w3.org JSON" <public-linked-json@w3.org>
2011/10/3 Ivan Herman <ivan@w3.org>: > Two issues. One positive, the other negative... > > For my specific issue in Python I have installed Python 2.7 on my machine, and made a test with this ordered dictionary and the built-in json parser. It works. Thanks to Olivier (I did not know about this extra in Python 2.7). > > However, following up one of the remarks I found on the Web, the JSON RFC[1] says > > [[[ > An object is an unordered collection of zero or more name/value pairs... > ]]] > > right in the introduction. Which means that, although the specific issue in Python is solvable indeed, other parsers or JSON serializers may not offer the same flexibility if they simply follow the RFC. Ok then I assume that we cannot make the @context position a requirement but I think the spec should still emphasize that it is a good practice for serializers to put the @context node in the first position to allow "smart" parsers to semantically process large payloads in a one-pass / streamed manner. -- Olivier http://twitter.com/ogrisel - http://github.com/ogrisel
Received on Monday, 3 October 2011 14:38:51 UTC