|
26 | 26 | background: yellow;
|
27 | 27 | }
|
28 | 28 |
|
29 |
| - ul.out-of-scope > li { |
| 29 | + ul.scope > li { |
30 | 30 | font-weight: bold;
|
31 | 31 | }
|
32 | 32 |
|
33 |
| - ul.out-of-scope > li > ul > li{ |
| 33 | + ul.scope > li > ul > li{ |
34 | 34 | font-weight: normal;
|
35 | 35 | }
|
36 | 36 |
|
@@ -166,11 +166,82 @@ <h2>Scope</h2>
|
166 | 166 | </p>
|
167 | 167 | <p>The Working group is expected to coordinate with the <a href='https://www.w3.org/community/json-ld/'>JSON for Linking Data Community Group</a> on consensus-based proposals related to content changes for the JSON-LD Working Group Deliverables. The Chairs of this group may choose to reject proposals that are incompatible with this Charter.</p>
|
168 | 168 |
|
| 169 | + <section id="section-feature-updates"> |
| 170 | + <h3 id="in-scope">In Scope</h3> |
| 171 | + <p>In addition to Errata and synchronization with the RDF-star Working Group, the following features tracked on the |
| 172 | + <a href="https://github.com/orgs/w3c/projects/84">Project Management Page</a> |
| 173 | + are in-scope for updates to the core JSON-LD specifications:</p> |
| 174 | + |
| 175 | + <ul class="scope"> |
| 176 | + <li>Additional updates to properly abstract serialization/deserialization based on content type |
| 177 | + (PR <a href="https://github.com/w3c/json-ld-api/pull/608">w3c/json-ld-api#608</a>).</li> |
| 178 | + <li>Address concerns from Verifiable Credentials |
| 179 | + (issue <a href="https://github.com/w3c/json-ld-syntax/issues/422">w3c/json-ld-syntax#422</a>).</li> |
| 180 | + <li>Allow class-scoped framing |
| 181 | + (issue <a href="https://github.com/w3c/json-ld-framing/issues/29">w3cjson-ld-framing#29</a>).</li> |
| 182 | + <li>Allow custom datatypes on JSON Literals |
| 183 | + (issue <a href="https://github.com/w3c/json-ld-syntax/issues/425">w3c/json-ld-syntax#425</a>).</li> |
| 184 | + <li>Change IANA Considerations to make the profile parameter required |
| 185 | + (PR <a href="https://github.com/w3c/json-ld-framing/pull/154">w3c/json-ld-framing#154</a>).</li> |
| 186 | + <li>Clarify that lexicographical order uses code point ordering |
| 187 | + (PR <a href="https://github.com/w3c/json-ld-syntax/pull/417">w3c/json-ld-syntax#417</a>), |
| 188 | + (PR <a href="https://github.com/w3c/json-ld-api/pull/574">w3c/json-ld-api#574</a>), |
| 189 | + (PR <a href="https://github.com/w3c/json-ld-framing/pull/153">w3c/json-ld-framing#153</a>).</li> |
| 190 | + <li>Compact IRI expansion support for non-trivial prefix term definitions |
| 191 | + (issue <a href="https://github.com/w3c/json-ld-syntax/issues/191">w3c/json-ld-syntax#191</a>).</li> |
| 192 | + <li>Compacting native values |
| 193 | + (issue <a href="https://github.com/w3c/json-ld-api/issues/545">w3c/json-ld-api#545</a>).</li> |
| 194 | + <li>Consider context by reference with metadata |
| 195 | + (issue <a href="https://github.com/w3c/json-ld-syntax/issues/108">w3c/json-ld-syntax#108</a>).</li> |
| 196 | + <li>Consider <code>@prefix</code> |
| 197 | + (issue <a href="https://github.com/w3c/json-ld-syntax/issues/329">w3c/json-ld-syntax#329</a>).</li> |
| 198 | + <li>Consistent treatment of JSON Literals |
| 199 | + (issue <a href="https://github.com/w3c/json-ld-api/issues/613">w3c/json-ld-api#613</a>), |
| 200 | + (PR <a href="https://github.com/w3c/json-ld-api/pull/559">w3c/json-ld-api#599</a>).</li> |
| 201 | + <li><code>@default</code> in <code>@context</code> |
| 202 | + (issue <a href="https://github.com/w3c/json-ld-syntax/issues/328">w3c-json-ld-syntax#328</a>).</li> |
| 203 | + <li>Expansion does not take property-scoped contexts for nested properties into account |
| 204 | + (issue <a href="https://github.com/w3c/json-ld-api/issues/380">w3c/json-ld-api#380</a>).</li> |
| 205 | + <li>Fix context processing for reverse terms(issue <a href=""></a>).</li> |
| 206 | + <li>Fix context processing for reverse terms |
| 207 | + (PR <a href="https://github.com/w3c/json-ld-api/pull/566">w3c/json-ld-api#566</a>).</li> |
| 208 | + <li>Framing nexted graphs |
| 209 | + (issue <a href="https://github.com/w3c/json-ld-framing/issues/150">w3c/json-ld-framing#150</a>).</li> |
| 210 | + <li>Graph-aliased keywords don't work as containers |
| 211 | + (issue <a href="https://github.com/w3c/json-ld-api/issues/536">w3c/json-ld-api#536</a>).</li> |
| 212 | + <li>Integer JSON value should be able to expand to IRI |
| 213 | + (issue <a href="https://github.com/w3c/json-ld-api/issues/509">w3c/json-ld-api#509</a>).</li> |
| 214 | + <li>Language map with global context |
| 215 | + (issue <a href="https://github.com/w3c/json-ld-framing/issues/126">w3c/json-ld-framing#126</a>).</li> |
| 216 | + <li>Language-maps don't allow separate base direction |
| 217 | + (issue <a href="https://github.com/w3c/json-ld-syntax/issues/280">w3c/json-ld-syntax#280</a>).</li> |
| 218 | + <li>Lists, sets, and multisets |
| 219 | + (issue <a href="https://github.com/w3c/json-ld-api/issues/473">w3c/json-ld-api#473</a>).</li> |
| 220 | + <li>Make it easier to keep semantics of object-oriented models |
| 221 | + (issue <a href="https://github.com/w3c/json-ld-syntax/issues/376">w3c/json-ld-syntax#376</a>).</li> |
| 222 | + <li>Nested properties and compaction |
| 223 | + (issue <a href="https://github.com/w3c/json-ld-api/issues/391">w3c/json-ld-api#391</a>).</li> |
| 224 | + <li>Pattern Matching |
| 225 | + (issue <a href="https://github.com/w3c/json-ld-framing/issues/118">w3c/json-ld-framing#118</a>).</li> |
| 226 | + <li>Reframing Relationships |
| 227 | + (issue <a href="https://github.com/w3c/json-ld-framing/issues/73">w3c/json-ld-framing#73</a>).</li> |
| 228 | + <li>Several frames in the same frame document |
| 229 | + (issue <a href="https://github.com/w3c/json-ld-framing/issues/38">w3c/json-ld-framing#38</a>).</li> |
| 230 | + <li>Specify a node type when interpreting JSON as JSON-LD |
| 231 | + (issue <a href="https://github.com/w3c/json-ld-syntax/issues/386">w3c/json-ld-syntax#386</a>).</li> |
| 232 | + <li>Support multiple IRIs for <code>@reverse</code> |
| 233 | + (issue <a href="https://github.com/w3c/json-ld-syntax/issues/372">w3c/json-ld-syntax#372</a>).</li> |
| 234 | + <li>Type Coercion / Node Conversion: <code>@coerce</code> keyword or similar |
| 235 | + (issue <a href="https://github.com/w3c/json-ld-syntax/issues/335">w3c/json-ld-syntax#335</a>).</li> |
| 236 | + <li>Miscellaneous test improvements.</li> |
| 237 | + </ul> |
| 238 | + </section> |
| 239 | + |
169 | 240 | <section id="section-out-of-scope">
|
170 | 241 | <h3 id="out-of-scope">Out of Scope</h3>
|
171 | 242 | <p>The following features are out of scope, and will not be addressed by this Working Group.</p>
|
172 | 243 |
|
173 |
| - <ul class="out-of-scope"> |
| 244 | + <ul class="scope"> |
174 | 245 | <li>RDF Dataset Normalization.</li>
|
175 | 246 | <li>Linked Data Signatures.</li>
|
176 | 247 | </ul>
|
|
0 commit comments