Skip to content

Conversation

@runcom
Copy link
Member

@runcom runcom commented Sep 8, 2016

@mtrmac PTAL

@runcom
Copy link
Member Author

runcom commented Sep 8, 2016

lgtm

Approved with PullApprove

@runcom
Copy link
Member Author

runcom commented Sep 8, 2016

@mtrmac please review and merge

@mtrmac
Copy link
Collaborator

mtrmac commented Sep 8, 2016

I’m not happy with the s/MIME/Media/; “MIME type” clearly refers to RFC 2046 and friends; “media type" could be anything.

Is it practical to push back?

@mtrmac
Copy link
Collaborator

mtrmac commented Sep 8, 2016

👍, sigh

Approved with PullApprove

@mtrmac mtrmac merged commit 58dedd8 into containers:master Sep 8, 2016
@runcom runcom deleted the api-fixes branch September 8, 2016 11:13
@runcom
Copy link
Member Author

runcom commented Sep 8, 2016

fixing skopeo ...

@stevvooe
Copy link

stevvooe commented Sep 9, 2016

@mtrmac They are actually called Media Types. I'm not sure if you've actually read RFC2046, but the title is actually "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types" and goes on to define a series of Media Types. While these can be used with MIME, there is no such thing as a "MIME Type".

The term "Media Type" is used consistently throughout the container standards and specifications.

@mtrmac
Copy link
Collaborator

mtrmac commented Sep 9, 2016

@stevvooe Of course the RFC introducing the concept of types to MIME predates their widespread usage outside of MIME, and thus was fine with using a generic name which has a specific meaning within its own context and found it unnecessary to use a self-referential name, I stand by my opinion that on the wide internet, saying “MIME type” is specific and “media type” may be something else like a fourCC code in RIFF/MPEG containers (and using "media” to refer to filesystem tarballs is awkward).

Anyway, this has been merged.

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

Successfully merging this pull request may close these issues.

3 participants