<div>How do we make sure that an erratum does not have adverse effects? I understand that for you it may not be so important because you consider that errata come and go. I think that we need to have at least a light review mechanism at least at TCG level, a possibility offered in the 'endorsed note' mechanism. Your (or any other erratum author's) plea that the erratum is OK may not be felt as sufficient. What do the other TCG members think?<br/>
<br/>
Francoise <br/>
<br/>
<font color="#888888"><font color="#888888">Envoyé depuis mon appareil Android.</font></font><br/><br/>-----Original Message-----<br/>From: Markus Demleitner <msdemlei@ari.uni-heidelberg.de><br/>To: tcg@ivoa.net, ivoadoc@ivoa.net, stdproc@ivoa.net<br/>Sent: mar, 04 nov. 2014 16:20<br/>Subject: Erratum uploaded<br/><br/></div>Dear Colleagues, <br/>
<br/>
As I've not heard loud protests, I've gone ahead and uploaded the <br/>
erratum, and I got even more convinced we shouldn't use the strong <br/>
note process for the errata. <br/>
<br/>
One point that reinforced my conviction: Notes are versioned, and <br/>
Errata shouldn't be, i.e., there should never be a version 2.0 of an <br/>
erratum. If an erratum itself is flawed, it should be withdrawn (but <br/>
let's figure out how to do that if and when the problem actually <br/>
occurrs). I'm very sure Errata simply aren't normal documents and <br/>
they shouldn't be treated as such [yes, this is a request to put this <br/>
on the agenda for the next TCG telecon with a view to revise the <br/>
previous decision]. <br/>
<br/>
Still, as I said, I've now uploaded a file <br/>
DERR-TREErr1-1.0-20141104.pdf (and HTML and so) to the doc repo. <br/>
DERR I made up as "Draft Erratum"; there probably would have to be <br/>
PERR and ERR in addition if we adopted the strong notes process. <br/>
<br/>
In addition, I had to improvise the status text. This is <br/>
provisionally in ivoatex, and it's <br/>
<br/>
This is a draft for an erratum to an IVOA recommendation made <br/>
available for public review. Interested parties are invited to <br/>
evaluate the erratum's validity and impact, but at this stage the <br/>
erratum does not yet change the normative content of the <br/>
recommendation. <br/>
<br/>
I'm completely open to revisions of this text. <br/>
<br/>
<br/>
We'll also have to work out with the document coordinator how the <br/>
erratum should be shown in the document repository. A few days ago I <br/>
sent out a proposal that suggested to put on <br/>
<br/>
<a href="http://ivoa.net/documents/TAPRegExt/index.html">http://ivoa.net/documents/TAPRegExt/index.html</a> <br/>
<br/>
right below the "Available Formats:" something like <br/>
<br/>
Errata: [IdentifierURI] (DRAFT), [WrongTense] (PROPOSED), [BadWords] (REC) <br/>
<br/>
Cheers, <br/>
<br/>
Markus <br/>