Change warnings about i18n-datatpe and compound-literal sections as being AT RISK (they're already informative).

Author: gkellogg

index.html

@@ -12853,9 +12853,11 @@ <h3>Serializing/Deserializing RDF</h3>
       the value of `@language`, if any, followed by an underscore (`"_"`) followed
       by the value of `@direction`.</p>
 
-    <p class="warning">This feature is experimental, as RDF does not have a
+    <p class="issue atrisk">This feature is experimental, as RDF does not have a
       standard way to represent base direction in <a>RDF literals</a>.
-      A future RDF Working Group may support base direction differently.</p>
+      A future RDF Working Group may support base direction differently.
+      The JSON-LD Working Group solicits feedback from the community on the
+      usefulness of these transformations.</p>
 
     <p>The following example shows two statements with literal values of `i18n:ar-EG_rtl`,
       which encodes the language tag `ar-EG` and the base direction `rtl`.</p>
@@ -12904,9 +12906,11 @@ <h3>Serializing/Deserializing RDF</h3>
       describe the <a>base direction</a> and optional <a>language tag</a> from
       value objects containing `@direction` and optionally `@language`.</p>
 
-    <p class="warning">This feature is experimental, as RDF does not have a
+    <p class="issue atrisk">This feature is experimental, as RDF does not have a
       standard way to represent base direction in <a>RDF literals</a>.
-      A future RDF Working Group may support base direction differently.</p>
+      A future RDF Working Group may support base direction differently.
+      The JSON-LD Working Group solicits feedback from the community on the
+      usefulness of these transformations.</p>
 
     <p>The following example shows two statements with compoud literals
       representing strings with the <a>language tag</a> `ar-EG` and <a>base direction</a> `rtl`.</p>