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

Introduce the concept of a best-practice representation? #81

Open
halostatue opened this issue Oct 29, 2014 · 0 comments
Open

Introduce the concept of a best-practice representation? #81

halostatue opened this issue Oct 29, 2014 · 0 comments

Comments

@halostatue
Copy link
Member

Right now, MIME::Types has two main representations of a MIME content type:

  • content_type: a presentation value from the MIME type registry and should not be used for comparison. The case of the content type is preserved, and extension markers (x-) are kept.
  • simplified: a comparison value, mostly used for sorting. It strips extension markers (x-) and converts to lowercase. The problem here is that application/x-www-url-form-encoded must have the x- present or it is incorrect, even though this fixes for the case of audio/QCELP sorting too early because of the capitalization of QCELP.

Should there be a best-practice representation created as well (see #76, #80)? This might be:

  • best_practice (or mime_type): a lowercase representation of content_type. This would protect the sort of audio/QCELP and keep application/x-www-url-form-encoded legit.
@halostatue halostatue added this to the 3.0 milestone Oct 29, 2014
@halostatue halostatue self-assigned this Oct 29, 2014
@halostatue halostatue modified the milestones: 3.0, Future Nov 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant