- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Thu, 15 Aug 2013 22:57:32 +0200
- To: "'JSON-LD CG'" <public-linked-json@w3.org>
On Thursday, August 15, 2013 7:44 PM, Sandro Hawke wrote: > On 08/15/2013 01:19 PM, Markus Lanthaler wrote: > > Perhaps we can shorten the CR period to compensate this delay a bit > > given that we already have more than enough implementations!? > > Another option to consider is skipping CR and going to straight to PR. > If the CR exit criteria have already been met, this can be done. That's certainly an option we should discuss as well, yeah. > Speaking of which, what are the planned CR exit criteria, and what's > the plan for dealing with the dependency on Futures/Promises? This is what I put in the spec: [[[ Before this specification exits Candidate Recommendation, two or more independent implementations must pass each test, although no single implementation must pass each test. The working group will decide when the test suite is of sufficient quality to test interoperability and will produce an implementation report (hosted together with the test suite). ]]] The test suite is quite complete already. The only thing that's really missing is negative tests to check the returned error codes. We didn't really talk about the Promises dependency anymore. Both Google [1] and Mozilla [2] will start to support them natively in their browsers soon. So I hope that this won't be a big problem. I don't know if webapps or some other group is going to re-publish the spec as W3C spec. [1] https://code.google.com/p/chromium/issues/detail?id=243345 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=856410 -- Markus Lanthaler @markuslanthaler
Received on Thursday, 15 August 2013 20:58:02 UTC