[transition] [JSON-LD WG] CR Request for json ld11, json ld11 api, and json ld11 framing

From https://github.com/w3c/transitions/issues/194

# Document title, URLs, estimated publication date
- JSON-LD 1.1
    - Editor's draft: https://w3c.github.io/json-ld-syntax/?specStatus=CR&publishDate=2019-12-10
    - Expected publication date: 2019-12-10
- JSON-LD 1.1 Processing Algorithms and API
    - Editor's draft: https://w3c.github.io/json-ld-api/?specStatus=CR&publishDate=2019-12-10
    - Expected publication date: 2019-12-10
- JSON-LD 1.1 Framing
    - Editor's draft: https://w3c.github.io/json-ld-framing/?specStatus=CR&publishDate=2019-12-10
    - Expected publication date: 2019-12-10

# Abstract
- JSON-LD 1.1: https://w3c.github.io/json-ld-syntax/?specStatus=CR&publishDate=2019-12-10#abstract
- JSON-LD 1.1 Processing Algorithms and API: https://w3c.github.io/json-ld-api/?specStatus=CR&publishDate=2019-12-10#abstract
- JSON-LD 1.1 Framing: https://w3c.github.io/json-ld-framing/?specStatus=CR&publishDate=2019-12-10#abstract

# Status
- JSON-LD 1.1: https://w3c.github.io/json-ld-syntax/?specStatus=CR&publishDate=2019-12-10#sotd
- JSON-LD 1.1 Processing Algorithms and API: https://w3c.github.io/json-ld-api/?specStatus=CR&publishDate=2019-12-10#sotd
- JSON-LD 1.1 Framing: https://w3c.github.io/json-ld-framing/?specStatus=CR&publishDate=2019-12-10#sotd

# Link to group's decision to request transition

- WG resolution on call: https://www.w3.org/2018/json-ld-wg/Meetings/Minutes/2019/2019-11-22-json-ld#resolution2
- Based on CfC: https://lists.w3.org/Archives/Public/public-json-ld-wg/2019Nov/0017.html

# Changes

- Changes to JSON-LD Syntax [since 1.0](https://w3c.github.io/json-ld-syntax/#changes-from-10) and [since the CG final report](https://w3c.github.io/json-ld-syntax/#changes-from-cg). The exact changes in the text can also be highlighted (not done by default, but can be chosen by the reader using a button).
- Changes to JSON-LD API [since 1.0](https://w3c.github.io/json-ld-api/#changes-since-1-0-recommendation-of-16-january-2014) and [since the CG final report](https://w3c.github.io/json-ld-api/#changes-from-cg)
- Changes to JSON-LD Framing [since 1.0 draft](https://w3c.github.io/json-ld-framing/#changes-since-1-0-draft-of-30-august-2012) and [since the CG final report](https://w3c.github.io/json-ld-framing/#changes-from-cg)

# Requirements satisfied

We have tracked our requirements in Github using issues. 

- JSON-LD 1.1
  - Total: 179 issues, mostly editorial change tracking.
  - [21 Satisfied Requirements](https://github.com/w3c/json-ld-syntax/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3Asatisfied)
  - [19 Rejected](https://github.com/w3c/json-ld-syntax/issues?q=is%3Aissue+sort%3Acreated-asc+label%3Aspec%3Awontfix) - These issues were invalid, out of scope for the work, or proposals that were discussed and rejected.
  - [3 Deferred for Future Work](https://github.com/w3c/json-ld-syntax/issues?q=is%3Aissue+sort%3Acreated-asc+defer+label%3Adefer-future-version)

  - Total: 71 Issues, mostly editorial change tracking
  - [12 Satisfied Requirements](https://github.com/w3c/json-ld-api/issues?q=is%3Aissue+is%3Aclosed+sort%3Acreated-asc+label%3Asatisfied)
  - [4 Won't Fix](https://github.com/w3c/json-ld-api/issues?q=is%3Aissue+sort%3Acreated-asc+label%3Awontfix)
  - [3 Deferred for Future Work](https://github.com/w3c/json-ld-api/issues?q=is%3Aissue+is%3Aopen+label%3Adefer-future-version)

- JSON-LD 1.1 Framing
  - Total: 30 issues, as always mostly editorial and questions
  - [9 Satisfied Requirements](https://github.com/w3c/json-ld-framing/issues?q=is%3Aissue+is%3Aclosed+sort%3Acreated-asc+label%3Asatisfied)
  - [2 Won't Fix](https://github.com/w3c/json-ld-framing/issues?q=is%3Aissue+is%3Aclosed+sort%3Acreated-asc+label%3Aspec%3Awontfix)
  - [3 Deferred for Future Work](https://github.com/w3c/json-ld-framing/issues?q=is%3Aissue+is%3Aopen+label%3Adefer-future-version)

# Dependencies met (or not)

# Wide Review
All reviews, comments, etc, were tracked in Github issues, see below

# Issues addressed
- JSON-LD 1.1
   - Open issues minus editorial, deferred, or transferred to best practices: https://tinyurl.com/yyys74xg
   - Same as above, but included closed issues: https://tinyurl.com/y5tgxj2u
- JSON-LD 1.1 Processing Algorithms and API
   - Open issues minus editorial, deferred, or transferred to best practices: https://tinyurl.com/y67bemer
   - Same as above, but included closed issues: https://tinyurl.com/y3hssblp
- JSON-LD 1.1 Framing
   - Open issues minus editorial, deferred, or transferred to best practices: https://tinyurl.com/y32fltkb
   - Same as above, but included closed issues: https://tinyurl.com/y6djf6dt

# Formal Objections

# Implementation

There is a (draft) [implementation report](https://w3c.github.io/json-ld-api/reports/) with pointers to all the tests (and instructions on how to submit implementation reports). Tests prepared for each feature of JSON-LD (some tests are covering more than one); see also the separate [test documentation](https://w3c.github.io/json-ld-api/tests/manifest). 

The exit criteria is that each feature (i.e., each test) must be passed by at least two, independent implementations. The WG intends to leave the CR duration open for a minimum of 3 months after the publication of the CR.

At the moment, members of the Working Groups are actively involved in different implementations in Ruby, Javascript, Python, and TypeScript (the latter is a streaming JSON-LD parser). The WG expects all four of them to submit test results. We also have contacts with an implementer active with a Java implementations. The group is also actively reaching out to implementers to find implementations in C/C++ and possibly Rust. 

Note that the test suite and the implementation aim to cover the _full_ JSON-LD 1.1, i.e., including the JSON-LD 1.0 features.

# Patent disclosures

See https://www.w3.org/2004/01/pp-impl/107714/status


@gkellogg @pchampin @dlongley @BigBlueHat @azaroth42

Received on Wednesday, 27 November 2019 09:58:00 UTC