TAPRegExt silent schema update?

[Tom Donaldson]

Hi All,

I also support this change, primarily because I’m convinced that the impact will be very minimal.  

When we come up with a (hopefully very lightweight) process for this sort of change, I expect the impact analysis/review will be the most important aspect.

Thanks,
Tom

> On Jul 28, 2016, at 5:44 AM, Mark Taylor <m.b.taylor at bristol.ac.uk> wrote:
> 
> Thank you.  With this version of the text, I personally support
> the silent update of this schema as Markus has argued.
> 
> Over to the TCG(?) to decide whether that is actually done.
> 
> On Wed, 27 Jul 2016, Markus Demleitner wrote:
> 
>> Hi,
>> 
>> On Tue, Jul 26, 2016 at 01:20:33PM +0100, Mark Taylor wrote:
>>> However I have a quibble.  The updated XSD you mention
>>> (https://volute.g-vo.org/svn/trunk/projects/registry/TAPRegExt/TAPRegExt-v1.0.xsd)
>>> contains some minor but non-essential rewording and reformatting
>>> compared to http://www.ivoa.net/xml/TAPRegExt/TAPRegExt-v1.0.xsd.
>>> If a silent update is done, I think the updated version should be
>>> as close to the original published xsd as possible, though including
>>> a comment near the top explaining the change, when it happened
>>> and with what authorization.  I'd like a diff to look as clean
>>> and comprehensible as possible.  The XSD to be updated should
>> 
>> Fair enough.  How about:
>> 
>>  $ svn diff -r 3496:3497 
>>  Index: TAPRegExt-v1.0.xsd
>>  ===================================================================
>>  --- TAPRegExt-v1.0.xsd	(revision 3496)
>>  +++ TAPRegExt-v1.0.xsd	(revision 3497)
>>  @@ -9,6 +9,12 @@
>>   elementFormDefault="unqualified" 
>>   attributeFormDefault="unqualified" 
>>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>>  +
>>  +<!-- Erratum-type change without change in namespace of version, 2016-07-27:
>>  +dataModel/@ivo-id is now derived xs:anyURI.   See 
>>  +https://volute.g-vo.org/svn/trunk/projects/registry/tapregext-erratum1
>>  +for details. -->
>>  +
>>     <xs:annotation>
>>       <xs:appinfo>
>>         <vm:schemaName>TAPRegExt</vm:schemaName>
>>  @@ -157,7 +163,7 @@
>> 
>>       <xs:simpleContent>
>>         <xs:extension base="xs:token"> 
>>  -        <xs:attribute name="ivo-id" type="vr:IdentifierURI" use="required">
>>  +        <xs:attribute name="ivo-id" type="xs:anyURI" use="required">
>>             <xs:annotation>
>>               <xs:documentation>
>>               The IVORN of the data model.
>> 
>> 
>> This is in a checkout of
>> 
>> https://volute.g-vo.org/svn/trunk/projects/registry/tapregext-erratum1
>> 
>> and the TAPRegExt-v1.0.xsd in rev. 3496 was copied form TAPRegExt
>> REC-1.0:
>> 
>>  $ svn log TAPRegExt-v1.0.xsd | head -20
>>  ------------------------------------------------------------------------
>>  r3497 | msdemlei | 2016-07-27 10:47:16 +0200 (Wed, 27 Jul 2016) | 3 lines
>> 
>>  Applied proposed changes (dataModel/@ivo-id type) to TAPRegExt-v1.0.xsd.
>> 
>> 
>>  ------------------------------------------------------------------------
>>  r3496 | msdemlei | 2016-07-27 10:43:17 +0200 (Wed, 27 Jul 2016) | 3 lines
>> 
>>  Pulled REC-1.0 version of the XSD in question.
>> 
>> 
>>  ------------------------------------------------------------------------
>>  r1711 | volute at g-vo.org | 2012-05-02 12:39:18 +0200 (Wed, 02 May 2012) | 4 lines
>> 
>>  Changed units in limits: rows->row, bytes->byte, as recommended by
>>  Sebastien and after consultation with Pat.
>> 
>> 
>> I'm not saying this is how we should do errata in the future, but
>> perhaps it's good enough in this emergency?  We could put a link to
>> this thread in, too...
>> 
>> Cheers,
>> 
>>        Markus
>> 
> 
> --
> Mark Taylor   Astronomical Programmer   Physics, Bristol University, UK
> m.b.taylor at bris.ac.uk +44-117-9288776  http://www.star.bris.ac.uk/~mbt/