Re: In preparation to REC...

Actually… I may have found some ways of including the issues automatically into the errata page. It will require some javascripting, but I do not mind playing with this. This means that the content of the errata page will be filled automatically. I would still keep that page on github, if anybody wants to make some change at some point later…

Ivan




> On 18 Nov 2015, at 14:23, Ivan Herman <ivan@w3.org> wrote:
> 
> … while I was at it, I have made the necessary changes in the document config for the REC, with the provisional date of the 17th of December.
> 
> Additionally, I have set up an errata page. Although it has a W3C URI
> 
> http://www.w3.org/2013/csvw/errata.html <http://www.w3.org/2013/csvw/errata.html>
> 
> it redirects to
> 
> http://w3c.github.io/csvw/errata/ <http://w3c.github.io/csvw/errata/>
> 
> This is just a proposal on how we can proceed with errata; because we always used GitHub, it seemed logical to use github for that purpose, too.
> 
> It is a bit of a pain that the accepted errors have to be recorded on the errata page manually, although it may help in separating the real errata from the fake ones. Nevertheless… if somebody knows some good javascript tricks to get the data directly from github on the fly rather than doing it manually, that would be better. I believe there is Github API, so it may not be impossible. I will have a look, but, in the meantime, what is there may be fine.
> 
> If you prefer another approach, let us discuss it now, while we still have time…
> 
> Cheers
> 
> Ivan
> 
> ----
> Ivan Herman, W3C
> Digital Publishing Lead
> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
> mobile: +31-641044153
> ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>
> 
> 
> 
> 


----
Ivan Herman, W3C
Digital Publishing Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704