Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mention MIME type parameter 'content' #15

Open
tomdonaldson opened this issue May 13, 2020 · 0 comments
Open

Mention MIME type parameter 'content' #15

tomdonaldson opened this issue May 13, 2020 · 0 comments
Milestone

Comments

@tomdonaldson
Copy link
Contributor

tomdonaldson commented May 13, 2020

(Also see original mention on the IVOA Applications mail list.)

Section 8 on MIME types currently mentions the serialization parameter and the generic charset parameter. The DataLink specification recommends using the content parameter (application/x-votable+xml;content=datalink) to denote VOTables that are DataLink responses.

According to RFC2046 and RFC2048, introducing new ad-hoc parameters along these lines is not forbidden. Unless the content parameter is already being used in other VOTable contexts, it might make sense to mention it in VOTable section 8 to bring it in sync with the DataLink recommendations, and avoid other standards reinventing the same thing with a different name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant