Schema versioning with errata

[Patrick Dowler]

If the xsd is in version control and gets merged I don't think out-of-order
errata changes will be lost. Of course, pending errata changes should
remain in a branch (or pull request if github) until accepted, then merged.
The xsd on www.ivoa.net should always come from the VC system, not from an
upload by an arbitrary participant. We could make that a "process" but in
reality the WG chair/vice-chair should probably be the ones pulling the
trigger on VC -> web site and that should suffice.

my 2c,

--
Patrick Dowler
Canadian Astronomy Data Centre
Victoria, BC, Canada


On Wed, 5 Jun 2019 at 02:45, Markus Demleitner <
msdemlei at ari.uni-heidelberg.de> wrote:

> Hi Brian,
>
> On Mon, Jun 03, 2019 at 12:16:40PM -0700, Brian Major wrote:
> > I'm guess I'm wondering what the use cases are for determining the 'patch
> > level' of a schema.  A common pattern would be something like:
>
> Oh, I think the one main use case is: it lets errata authors and the
> document coordinator figure out if what's in the schema repo matches
> their expectations without having to look at the concrete changes of
> the errata and whether they are in the schema they see.
>
> The situation I'd like to be able to detect is, in a nutshell:
>
> (1) Alice starts Erratum-m and fixes her local copy of the schema
>     accordingly
> (2) Bob uploads the Erratum-n changed schema
> (3) After Erratum-m is accepted, Alice uploads *her* version of the
>     Erratum-m changes -- which by construction is still missing changes
>     from Erratum-n.
>
> In effect, as far as the schema is concerned, Erratum-n is rolled
> back.
>
> Having these little tags in the (otherwise essentially unused)
> /@version of the schema would raise the likelihood we (mostly, the
> document coordinator) has a fair chance of catching such a mishap
> significantly (I'd say).
>
> > - someone builds an implementation against a schema for some version of a
> > standard
> > - an error is discovered which affects the schema so an erratum is
> > published and the schema file updated
> > - the implementor notices the erratum (which says it has affects on the
> > schema) so, to fix the implementation, he/she acquires the updated schema
> > file.
>
> Yes, that's another scenario.  Essentially, again: "Catching version
> skews".
>
> Thanks,
>
>          Markus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/grid/attachments/20190605/acca5846/attachment.html>