Mime type for annotated data

Laurent Michel laurent.michel at astro.unistra.fr
Thu Dec 5 18:31:33 CET 2024


Mark,

Honestly, I haven't considered using the VOTable mime type, but that might work.

My motivation for suggesting this is twofold:
1- An annotated VOTable is a VOTable that contains an XML block that obeys its own schema. In other words, it is something different from a regular VOTable. So having a specific mime type makes sense.
2- More pragmatically, having a specific mime type allows clients to request annotated data via the &FORMAT TAP parameter as they could for any other format (JSON...).

Laurent

> On 5 Dec 2024, at 16:49, Mark Taylor <m.b.taylor at bristol.ac.uk> wrote:
> 
> Laurent,
> 
> I don't necessarily disagree with these suggestions, but another
> alternative would just be to use a standard VOTable MIME type
> on its own (application/x-votable+xml).  MIME types are a fairly
> blunt instrument and don't usally say much about the content of
> resources, just rather basic information about the format.
> 
> Can you say something about why it's useful to have the fact of
> MIVOT/MANGO annotation declared in the the MIME type, e.g. what
> client behaviour would benefit from it?
> 
> Thanks
> 
> Mark
> 
> On Thu, 5 Dec 2024, Laurent Michel via apps wrote:
> 
>> Dear groups
>> 
>> At the last interop, apps session, I showed a TAP service that annotates data with MIVOT, as long as you use 
>>    FORMAT=application/mango.
>> 
>> I was rightly told that this was probably the worst choice I could have made, even for a simple demonstrator.
>> 
>> The question now is to construct a mime type, compatible with the RFCs and expressing the fact that the response to the request is a VOTable, whose data is mapped onto a model using the MIVOT syntax.
>> 
>> I think the right solution is to use the parameters as defined in rfc2045
>> 
>> There are two options:
>> 
>> 1- say the data is annotated with MIVOT and let the client find out which model it is.
>> 
>>    application/x-votable+xml;mapping=mivot
>> 
>> 2- say the data is mapped to the MANGO model with MIVOT
>> 
>>    application/x-votable+xml;mivot=mango
>> 
>> This second solution highlights a particular model, but it may make sense for our use cases.
>> 
>> Any suggestions or comments?
>> 
>> All the best, 
>> 
>> Laurent
> 
> --
> Mark Taylor  Astronomical Programmer  Physics, Bristol University, UK
> m.b.taylor at bristol.ac.uk          https://www.star.bristol.ac.uk/mbt/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20241205/e30e8e77/attachment.htm>


More information about the apps mailing list