Explain that xsd:integer's value space is not limited
authorMarkus Lanthaler <mark_lanthaler@gmx.net>
Thu, 04 Apr 2013 17:09:53 +0200
changeset 1536 97d0f3b0a326
parent 1535 4ad0289b9e36
child 1537 394709b48ee2
Explain that xsd:integer's value space is not limited

as @afs suggested.

This addresses #237
spec/latest/json-ld-api/index.html
--- a/spec/latest/json-ld-api/index.html	Thu Apr 04 15:59:02 2013 +0200
+++ b/spec/latest/json-ld-api/index.html	Thu Apr 04 17:09:53 2013 +0200
@@ -3659,7 +3659,13 @@
       representation might be lost. An <code>xsd:double</code> with a value
       of <code>2.0</code> will, e.g., result in an <code>xsd:integer</code>
       with a value of <code>2</code> in <tref>canonical lexical form</tref>
-      when converted from RDF to JSON-LD and back to RDF.</p>
+      when converted from RDF to JSON-LD and back to RDF. It is important
+      to highlight that in practice it might be impossible to losslessly
+      convert an <code>xsd:integer</code> to a <tref>number</tref> because
+      its value space is not limited. While the JSON specification [[RFC4627]]
+      does not limit the value space of <tref title="number">numbers</tref>
+      either, concrete implementations typically do have a limited value
+      space.</p>
 
     <p>To ensure lossless round-tripping the
       <a href="#convert-from-rdf-algorithm">Converting from RDF algorithm</a>