Remove "Feature at Risk 7: Conversion to/from JSON Native Types" marker
authorMarkus Lanthaler <mark_lanthaler@gmx.net>
Tue, 09 Jul 2013 22:15:18 +0200
changeset 1757 414d758240a5
parent 1756 5e669f9fcc43
child 1758 1eddcdaa5bc4
Remove "Feature at Risk 7: Conversion to/from JSON Native Types" marker

... we resolved this by setting the default value of useNativeTypes to false.
spec/latest/json-ld-api/index.html
--- a/spec/latest/json-ld-api/index.html	Tue Jul 09 22:11:16 2013 +0200
+++ b/spec/latest/json-ld-api/index.html	Tue Jul 09 22:15:18 2013 +0200
@@ -3645,17 +3645,6 @@
   <section>
     <h2>Data Round Tripping</h2>
 
-    <div class="issue atrisk" data-number="7" title="Conversion to/from JSON Native Types">
-      <p class="atrisk-head">Note: This feature is
-        <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">"at risk"</a> and may
-        be removed or modified heavily from the feature described in this specification
-        based on reviewer feedback. Please send feedback to
-        <a href="mailto:[email protected]">[email protected]</a>.
-        For the current status see
-        <a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
-      <p>The JSON-LD-API allows certain RDF literals to be mapped to JSON numbers (if the "use native types" flag is set). The mapping rules are currently being debated as is which JSON-LD API methods the "use native types" will have an effect in. There may be changes made to the algorithm and API based on feedback during the 2nd Last Call. Implementers and reviewers should keep a close eye on the details for this mechanism and comment on any round-tripping concerns that they may have. The algorithm and API will most likely change after the LC2 period.</p>
-    </div>
-
     <p>When <a href="#convert-to-rdf-algorithm">converting JSON-LD to RDF</a>
       JSON-native <tref title="number">numbers</tref> are automatically
       type-coerced to <code>xsd:integer</code> or <code>xsd:double</code>