Mime type for annotated data

[CresitelloDittmar, Mark]

Laurent,

This is out of my wheelhouse so to speak, but..
I'd be careful about #2 since there is the potential for the data to be
mapped to more than one model.

Mark




On Thu, Dec 5, 2024 at 10:01 AM Laurent Michel via apps <apps at ivoa.net>
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20241205/e782c4e1/attachment-0001.htm>