Re: Updated implementation report with 100% feature coverage

> On Apr 15, 2020, at 11:58 PM, Ivan Herman <ivan@w3.org> wrote:
> 
> Brilliant!
> 
> [1] below is an example of the transition issue we will have to raise to go to PR. We would have to decide tomorrow what are exactly the pointers we would add to the issue regarding 'wide review' and 'issues addressed'. Otherwise it is simple.

We might use the “wr:spec-updated” tag on issues to note “issues addressed”. For example in API [1]. My practice comencing with CR has been to tag most incoming issues with “wr:…”, ultimately leading to updates with “wr:spec-updated”. There is usually a “wr:commenter-agreed” for each of these, with a couple of exceptions.

Gregg

[1] https://github.com/w3c/json-ld-api/issues?q=is%3Aissue+is%3Aclosed+label%3Awr%3Aspec-updated <https://github.com/w3c/json-ld-api/issues?q=is:issue+is:closed+label:wr:spec-updated>

> Ivan
> 
> 
> [1] https://github.com/w3c/transitions/issues/193
> 
>> On 15 Apr 2020, at 18:55, Gregg Kellogg <gregg@greggkellogg.net> wrote:
>> 
>> The latest report has been generated [1], which shows each feature (including non-normative and HTML) with at least two implementations passing the test, which matches our criteria for entering PR.
>> 
>> Notably, there are six implementations covering To/From RDF transformation, recently including Rust, Go, Perl, and Guile in addition to Python, Ruby and Javascript.
>> 
>> I think we can expect an implementation report for jsonld.js shortly, and hopefully java-jsonld.
>> 
>> Gregg Kellogg
>> gregg@greggkellogg.net
>> 
>> [1] https://w3c.github.io/json-ld-api/reports/
> 
> 
> ----
> Ivan Herman, W3C 
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> ORCID ID: https://orcid.org/0000-0003-0782-2704
>