@@ -185,73 +185,12 @@ <h2>Scope</h2>
185185
186186 < section id ="section-feature-updates ">
187187 < h3 id ="in-scope "> In Scope</ h3 >
188- < p > In addition to Errata and synchronization with the RDF-star Working Group, the following features tracked on the
188+ < p > In addition to Errata and synchronization with the RDF-star Working Group, features tracked on the
189189 < a href ="https://github.com/orgs/w3c/projects/84 "> Project Management Page</ a >
190- are in-scope for updates to the core JSON-LD specifications:</ p >
191-
192- < ul class ="scope ">
193- < li > Additional updates to properly abstract serialization/deserialization based on content type
194- (PR < a href ="https://github.com/w3c/json-ld-api/pull/608 "> w3c/json-ld-api#608</ a > ).</ li >
195- < li > Address concerns from Verifiable Credentials
196- (issue < a href ="https://github.com/w3c/json-ld-syntax/issues/422 "> w3c/json-ld-syntax#422</ a > ).</ li >
197- < li > Allow class-scoped framing
198- (issue < a href ="https://github.com/w3c/json-ld-framing/issues/29 "> w3cjson-ld-framing#29</ a > ).</ li >
199- < li > Allow custom datatypes on JSON Literals
200- (issue < a href ="https://github.com/w3c/json-ld-syntax/issues/425 "> w3c/json-ld-syntax#425</ a > ).</ li >
201- < li > Change IANA Considerations to make the profile parameter required
202- (PR < a href ="https://github.com/w3c/json-ld-framing/pull/154 "> w3c/json-ld-framing#154</ a > ).</ li >
203- < li > Clarify that lexicographical order uses code point ordering
204- (PR < a href ="https://github.com/w3c/json-ld-syntax/pull/417 "> w3c/json-ld-syntax#417</ a > ),
205- (PR < a href ="https://github.com/w3c/json-ld-api/pull/574 "> w3c/json-ld-api#574</ a > ),
206- (PR < a href ="https://github.com/w3c/json-ld-framing/pull/153 "> w3c/json-ld-framing#153</ a > ).</ li >
207- < li > Compact IRI expansion support for non-trivial prefix term definitions
208- (issue < a href ="https://github.com/w3c/json-ld-syntax/issues/191 "> w3c/json-ld-syntax#191</ a > ).</ li >
209- < li > Compacting native values
210- (issue < a href ="https://github.com/w3c/json-ld-api/issues/545 "> w3c/json-ld-api#545</ a > ).</ li >
211- < li > Consider context by reference with metadata
212- (issue < a href ="https://github.com/w3c/json-ld-syntax/issues/108 "> w3c/json-ld-syntax#108</ a > ).</ li >
213- < li > Consider < code > @prefix</ code >
214- (issue < a href ="https://github.com/w3c/json-ld-syntax/issues/329 "> w3c/json-ld-syntax#329</ a > ).</ li >
215- < li > Consistent treatment of JSON Literals
216- (issue < a href ="https://github.com/w3c/json-ld-api/issues/613 "> w3c/json-ld-api#613</ a > ),
217- (PR < a href ="https://github.com/w3c/json-ld-api/pull/559 "> w3c/json-ld-api#599</ a > ).</ li >
218- < li > < code > @default</ code > in < code > @context</ code >
219- (issue < a href ="https://github.com/w3c/json-ld-syntax/issues/328 "> w3c-json-ld-syntax#328</ a > ).</ li >
220- < li > Expansion does not take property-scoped contexts for nested properties into account
221- (issue < a href ="https://github.com/w3c/json-ld-api/issues/380 "> w3c/json-ld-api#380</ a > ).</ li >
222- < li > Fix context processing for reverse terms(issue < a href =""> </ a > ).</ li >
223- < li > Fix context processing for reverse terms
224- (PR < a href ="https://github.com/w3c/json-ld-api/pull/566 "> w3c/json-ld-api#566</ a > ).</ li >
225- < li > Framing nexted graphs
226- (issue < a href ="https://github.com/w3c/json-ld-framing/issues/150 "> w3c/json-ld-framing#150</ a > ).</ li >
227- < li > Graph-aliased keywords don't work as containers
228- (issue < a href ="https://github.com/w3c/json-ld-api/issues/536 "> w3c/json-ld-api#536</ a > ).</ li >
229- < li > Integer JSON value should be able to expand to IRI
230- (issue < a href ="https://github.com/w3c/json-ld-api/issues/509 "> w3c/json-ld-api#509</ a > ).</ li >
231- < li > Language map with global context
232- (issue < a href ="https://github.com/w3c/json-ld-framing/issues/126 "> w3c/json-ld-framing#126</ a > ).</ li >
233- < li > Language-maps don't allow separate base direction
234- (issue < a href ="https://github.com/w3c/json-ld-syntax/issues/280 "> w3c/json-ld-syntax#280</ a > ).</ li >
235- < li > Lists, sets, and multisets
236- (issue < a href ="https://github.com/w3c/json-ld-api/issues/473 "> w3c/json-ld-api#473</ a > ).</ li >
237- < li > Make it easier to keep semantics of object-oriented models
238- (issue < a href ="https://github.com/w3c/json-ld-syntax/issues/376 "> w3c/json-ld-syntax#376</ a > ).</ li >
239- < li > Nested properties and compaction
240- (issue < a href ="https://github.com/w3c/json-ld-api/issues/391 "> w3c/json-ld-api#391</ a > ).</ li >
241- < li > Pattern Matching
242- (issue < a href ="https://github.com/w3c/json-ld-framing/issues/118 "> w3c/json-ld-framing#118</ a > ).</ li >
243- < li > Reframing Relationships
244- (issue < a href ="https://github.com/w3c/json-ld-framing/issues/73 "> w3c/json-ld-framing#73</ a > ).</ li >
245- < li > Several frames in the same frame document
246- (issue < a href ="https://github.com/w3c/json-ld-framing/issues/38 "> w3c/json-ld-framing#38</ a > ).</ li >
247- < li > Specify a node type when interpreting JSON as JSON-LD
248- (issue < a href ="https://github.com/w3c/json-ld-syntax/issues/386 "> w3c/json-ld-syntax#386</ a > ).</ li >
249- < li > Support multiple IRIs for < code > @reverse</ code >
250- (issue < a href ="https://github.com/w3c/json-ld-syntax/issues/372 "> w3c/json-ld-syntax#372</ a > ).</ li >
251- < li > Type Coercion / Node Conversion: < code > @coerce</ code > keyword or similar
252- (issue < a href ="https://github.com/w3c/json-ld-syntax/issues/335 "> w3c/json-ld-syntax#335</ a > ).</ li >
253- < li > Miscellaneous test improvements.</ li >
254- </ ul >
190+ are in-scope for updates to the core JSON-LD specifications.</ p >
191+ < p > The Working Group will also consider < a href ="https://www.w3.org/2021/Process-20211102/#allow-new-features "> allowing new features</ a > in
192+ these recommendations, according to < a href ="https://www.w3.org/2021/Process-20211102/#revised-rec-features "> Section 6.3.11.4 of the W3C
193+ process</ a > , in order to render future evolutions easier.</ p >
255194 </ section >
256195
257196 < section id ="section-out-of-scope ">
0 commit comments