Add changes since previous versions for ordered.

Author: gkellogg

index.html

@@ -5134,6 +5134,11 @@ <h2>Changes since 1.0 Recommendation of 16 January 2014</h2>
       has been updated to ensure that only <a>well-formed</a> <a>triples</a>
       are emitted; previously, it only ensured that <a>triples</a> containing
       <a>relative IRIs</a> were excluded.</li>
+    <li>The API now adds an <a data-link-for="JsonLdOptions">ordered</a>
+       option, defaulting to <code>false</code> This is used in algorithms to
+       control interation of <a>dictionary member</a> keys. Previously, the
+       algorithms always required such an order. The instructions for
+       evaluating test results have been updated accordingly.</li>
   </ul>
 </section>
 
@@ -5145,6 +5150,11 @@ <h2>Changes since JSON-LD Community Group Final Report</h2>
       has been updated to ensure that only <a>well-formed</a> <a>triples</a>
       are emitted; previously, it only ensured that <a>triples</a> containing
       <a>relative IRIs</a> were excluded.</li>
+    <li>The API now adds an <a data-link-for="JsonLdOptions">ordered</a>
+       option, defaulting to <code>false</code> This is used in algorithms to
+       control interation of <a>dictionary member</a> keys. Previously, the
+       algorithms always required such an order. The instructions for
+       evaluating test results have been updated accordingly.</li>
   </ul>
 </section>
 

tests/README.md

@@ -52,11 +52,13 @@ JSON-LD Object comparison compares JSON objects, arrays, and values recursively
 Note that some tests require re-expansion and comparison, as list values may exist as values of properties that have `@container: @list` and the comparison algorithm will not consider ordering significant.
 
 # Running tests
+
 Implementations create their own infrastructure for running the test suite. In particular, the following should be considered:
 
 * _remote-doc_ tests will likely not return expected HTTP headers, so the _options_ should be used to determine what headers are associated with the input document.
 * Some algorithms, particularly _fromRdf_, may not preserve the order of statements listed in the input document, and provision should be taken for performing unordered array comparison, for arrays other than values of `@list`. (This may be difficult for compacted results, where array value ordering is dependent on the associated term definition).
 * Some implementations may choose an alternative Blank Node Label algorithm, the comparison between documents containing blank node labels should take this into consideration. (One way to do this may be to reduce both results and _expected_ to datsets to extract a bijective mapping of blank node labels between the two datasets as described in [RDF Dataset Isomorphism](https://www.w3.org/TR/rdf11-concepts/#dfn-dataset-isomorphism)).
+
 # Contributing
 
 If you would like to contribute a new test or a fix to an existing test,