MIVOT implementor feedback 1: RESOURCE location

Laurent Michel laurent.michel at astro.unistra.fr
Wed Dec 21 10:03:27 CET 2022


Dear DM,

The MIVOT proposal (20/12/2023) has been updated (PR #174) in order to allow the RESOURCE containing the MIVOT block to be anywhere in the HOST resource.

The Markus proposal goes further since he suggest to drop the requirement of having the MIVOT block into a specific RESOURCE.
I’ve no strong opinion on that topic although it makes sense to me to see the model annotation block as a resource.

We need your comments on that that topic before to decide to go in one way or another.
An issue has been open for this 
    https://github.com/ivoa-std/ModelInstanceInVot/issues/176


MIVOT authors

—
Translate with https: //www.deepl.com/translator
-- 
jesuischarlie/Tunis/Paris/Bruxelles/Berlin

Laurent Michel
SSC XMM-Newton
Tél : +33 (0)3 68 85 24 37
Fax : +33 (0)3 )3 68 85 24 32
Université de Strasbourg <http://www.unistra.fr>
Observatoire Astronomique
11 Rue de l'Université
F - 67200 Strasbourg

> On 15 Dec 2022, at 12:02, Markus Demleitner <msdemlei at ari.uni-heidelberg.de> wrote:
> 
> Dear DM,
> 
> On Wed, Dec 14, 2022 at 12:31:58PM -0500, CresitelloDittmar, Mark wrote:
>> If I recall, it was originally that the annotation syntax would be in the
>> first RESOURCE of the VOTABLE, making it a simple insert with minimal
>> impact on the native VOTABLE.  When it moved into the 'results' RESOURCE, I
>> think we wanted it to retain that 'minimal impact' on the native VOTABLE,
>> so required it to be the first child.
>> 
>> I think that operationally it shouldn't matter where it resides within the
>> parent RESOURCE since there can be only 1 annotation block per 'results'
>> block.
> 
> Whatever the history: Looking again, when you put the annotation into
> the RESOURCE it annotates anyway (which I think will make Mark
> Taylor's life simpler when he merges multiple VOTables into one, so I
> won't argue against it), you could drop the extra RESOURCE around the
> VODML element entirely.
> 
> Just write the VODML element directly into the RESOURCE with the
> table (or whatever) and be done with it.  This actually has the
> advantage that parsing clients already have seen all the ID-s you are
> talking about, because syntactically, this means VODML is at the end
> of the RESOURCE.
> 
> Thanks,
> 
>          Markus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dm/attachments/20221221/0c67faab/attachment.htm>


More information about the dm mailing list