Re: Editorial questions

Arnaud,

It is more work for the editor but less work for the reviewers. Since there are more reviewers than editors, marking the revisions makes the WG more efficient.  

-- Arthur

> On Jul 6, 2015, at 11:26 AM, Arnaud Le Hors <lehors@us.ibm.com> wrote:
> 
> Arthur,
> although I understand the desire for this, unless there is a tool that can generate this automatically I don't think we can reasonably ask the edtior(s) to markup all the changes in such a way. This is just too much of a pain.
> --
> Arnaud  Le Hors - Senior Technical Staff Member, Open Web Technologies - IBM Software Group
> 
> 
> 
> 
> From:        Arthur Ryman <arthur.ryman@gmail.com>
> To:        Holger Knublauch <holger@topquadrant.com>
> Cc:        RDF Data Shapes Working Group <public-data-shapes-wg@w3.org>
> Date:        07/06/2015 01:45 PM
> Subject:        Re: Editorial questions
> 
> 
> 
> On Fri, Jul 3, 2015 at 1:50 AM, Holger Knublauch <holger@topquadrant.com> wrote:
> 
> 2) Arthur, you stated you wanted change bars on the sides. Do you have an example of this (in HTML) and does anyone know how to do such thing in respec? Meanwhile I have added a link to the detailed version history in github to the "Revision History" section after the Abstract. 
> 
> Thanks for adding the Revision History section. 
> 
> HTML has tags <ins> and <del> to markup inserted and deleted text [1], e.g.
> <p>My favorite color is <del>blue</del> <ins>red</ins>!</p> 
> 
> I know't know what this looks like in respect, but we can modify the CSS to improve the appearance if necessary.
> 
> The key thing is that we need a simple way to see the delta from version to version. Change bars in the margin would be fine, but as long as the inserted/modifed  and deleted text is clearly visible, then reviewers won't have to reread the entire spec.
> 
> [1] http://www.w3schools.com/tags/tag_ins.asp
> 
> -- Arthur
>