You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>The following is a list of issues open at the time of publication.</p>
12230
-
<pclass="issue" data-number="4">Consider using <code>"@type": "@json"</code> to describe native values in the compact form.</p>
12231
12230
<pclass="issue" data-number="9">Provide a means for refering to a remote context without without requiring it to be downloaded.</p>
12232
12231
<pclass="issue" data-number="19">Consider a mechanism such as Microdata's <code>@itemref</code> for including objects within another referencing node.</p>
12233
-
<pclass="issue" data-number="20">Mechinism to allow freezing terms so that additional contexts don't override them.</p>
12234
-
<pclass="issue" data-number="46">Consider documentation best practices.</p>
12235
-
<pclass="issue" data-number="59">Define a recommended context to import.</p>
12236
-
<pclass="issue" data-number="76">Node Types in <code>@context</code>.</p>
12237
-
<pclass="issue" data-number="86"></p>
12232
+
<pclass="issue" data-number="86">Can SRI be used in JSON-LD and for which use cases?</p>
12233
+
<pclass="issue" data-number="108">Consider context by reference with metadata.</p>
12234
+
<pclass="issue" data-number="134">Does HTML's <code><base></code> effect <code>@context</code> IRI resolution?</p>
12235
+
<pclass="issue" data-number="149">DocumentLoader should be more visible in the specs.</p>
12236
+
<pclass="issue" data-number="155">IRIs are terms can be misdefined.</p>
0 commit comments