<div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">it's been awhile but can someone take a look at and comment on this:</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><a href="https://github.com/ivoa-std/VOTable/issues/26">https://github.com/ivoa-std/VOTable/issues/26</a></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">which says:</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><p>In DataLink, we specify a parameter to add to the VOTable mime type to tell clients that the table contains "datalinks":</p>
<div class="gmail-snippet-clipboard-content gmail-position-relative gmail-overflow-auto"><pre><code>application/x-votable+xml; content=datalink
</code></pre></div>
<p>Over in the DataLink discussions about adding params to other
content-type values (eg in the content_type column), we found out that
this really goes against the spirit of the mime type RFC 2045 and that
params should be defined by the spec that owns the type. So, this is a
request for VOTable to add an allowed mime type parameter <code>content</code>
that other specs can define values for. It would thus be open ended but
clients would know to anticipate the param in some cases.</p></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div>--<br></div><div>Patrick Dowler<br></div>Canadian Astronomy Data Centre<br></div>Victoria, BC, Canada<br></div></div></div></div></div></div>