TAPRegExt erratum, Identifiers for Obscore

[Markus Demleitner]

Bob,

[fixing an IVORN in an example]

On Tue, Dec 10, 2013 at 09:45:56PM +0000, Robert J. Hanisch wrote:
> I think it would be more consistent with the versioning system we have
> been using for nearly 10 years to make an incremental (0.01 delta) release
> of the document, note the errors that have been corrected in the change
> log, and fix the problem in the main document.  If people don't bother to
> look at the change log / erratum they will go on implementing the wrong
> thing.

A link to errata on the "landing page", alongside the links to the
various document formats, will probably be considered fairly gravely.

> It was never the intention to make it onerous to fix minor problems with
> documents.

The way things have worked out, it has become onerous; there's just
many little things, down to updating the Standards Record.  And with
this, there's more trouble, at least if the current practice of
encoding the version number in the IVORN (which this is about,
incidentally) is kept.  If TAPRegExt encoded a capability, would this
capability's standardId change?  If so, it'd be a really devastating
change.

What I'm trying to say: A lightweight process to fix typos would save
us a lot of potentially serious technical issues.  If small changes
in version numbers became frequent as Errata get pushed out, some
IVOA practices may need some revision.

> If the WG Chair advises the TCG chair and IVOA chair that the nature of
> the change is that of a correction, repair of a typo, etc., there would be
> no need to go through the full-up review and sign-off process.

But then, we might as well try it to figure out how much hassle it
really is.  I've just submitted a PR containing the fix to Pat.

First impression: 

msdemlei at victor:/home/msdemlei/gavo/standards/tapregext > svn diff | wc -l
224

-- seems a bit, well, heavywheight for a 10-character patch (but of
course, this is a bit unfair, as there's the formatted document in
the repo and I needed a slight update to the build system, too, but
between "previous version" and "changes from" there's quite a bit of
bookkeeping that's going on).  This is volute Rev. 2388.

Cheers,

       Markus