Reference ISSUE-53 on changes to the Normalization algorithm, with some discussion.
authorGregg Kellogg <gregg@kellogg-assoc.com>
Wed, 11 Jan 2012 11:25:05 -0800
changeset 328 69fe37f6ec42
parent 327 60b8aa170d52
child 329 5458bd10c815
Reference ISSUE-53 on changes to the Normalization algorithm, with some discussion.
spec/latest/json-ld-api/index.html
--- a/spec/latest/json-ld-api/index.html	Wed Jan 11 10:46:10 2012 -0800
+++ b/spec/latest/json-ld-api/index.html	Wed Jan 11 11:25:05 2012 -0800
@@ -1475,6 +1475,18 @@
   as described in <a href="#rdf-conversion">RDF Conversion</a>, invoking the normalization procedure
   as described in [[!RDF-NORMALIZATION]], returning the serialized results.</p>
 
+<div class="issue">
+  <p>There an open issue (<a href="https://github.com/json-ld/json-ld.org/issues/53">ISSUE-53</a>)
+    on the purpose and results of performing normalization. Previous versions of the
+    specification generated JSON-LD as the result of the normalization algorithm, however
+    normalization is a process required across different linked data serializations. To be useful,
+    a graph requires an identical normalized representation that is independent of the
+    data format originally used for markup, or the way in which language features or publisher
+    preferences create differences in the markup of identical graphs.</p>
+  <p>It may be that the need for either or both of flattening algorithm or to retrieve such a
+    cryptographic signature.</p>
+</div>
+
 <p>Normalization is useful when comparing two graphs against one another,
   when generating a detailed list of differences between two graphs, and
   when generating a cryptographic digital signature for information contained