Mime type for annotated data

[Mark Taylor]

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/