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

Editorial: tweak MIME type group definitions #59

Merged
merged 1 commit into from
Feb 16, 2018
Merged

Conversation

domenic
Copy link
Member

@domenic domenic commented Feb 5, 2018

Notably, this ensures that the terms always say "MIME type", instead of sometimes "type" and sometimes "MIME type". It also tidies up some of the essence lists.


This does not touch the font type definition, since #27 fixes that in similar ways.


Preview | Diff

<code>application/pdf</code>
</ul>
<p>A <dfn>scriptable MIME type</dfn> is an <a>XML MIME type</a>, <a>HTML MIME type</a>, or any
<a>MIME type</a> whose <a for="MIME type">essence</a> is "<code>application/pdf</code>".
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this list be expanded to other MIME types, rather than collapsed for the single entry it has now?

I'm thinking, for example, of Postscript and others.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure! Seems like a reasonable issue to open. But I was doing a purely editorial change for now.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But you didn't inline application/zip above...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess since that's actively marked as an open issue. Okay.

Notably, this ensures that the terms always say "MIME type", instead of sometimes "type" and sometimes "MIME type". It also tidies up some of the essence lists.
<code>application/pdf</code>
</ul>
<p>A <dfn>scriptable MIME type</dfn> is an <a>XML MIME type</a>, <a>HTML MIME type</a>, or any
<a>MIME type</a> whose <a for="MIME type">essence</a> is "<code>application/pdf</code>".
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But you didn't inline application/zip above...

@@ -947,7 +937,7 @@ matches, if any, use the following <dfn>image type pattern matching algorithm</d

<h3 id=matching-an-audio-or-video-type-pattern>Matching an audio or video type pattern</h3>

<p>To determine which <a>audio or video type</a> <a>byte pattern</a> a <a>byte sequence</a>
<p>To determine which <a>audio or video MIME type</a> <a>byte pattern</a> a <a>byte sequence</a>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this become media MIME type?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah maybe; I didn't want to change things much.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough.

<code>application/pdf</code>
</ul>
<p>A <dfn>scriptable MIME type</dfn> is an <a>XML MIME type</a>, <a>HTML MIME type</a>, or any
<a>MIME type</a> whose <a for="MIME type">essence</a> is "<code>application/pdf</code>".
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess since that's actively marked as an open issue. Okay.

@domenic domenic merged commit 4529389 into master Feb 16, 2018
@domenic domenic deleted the editorial-groups branch February 16, 2018 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants