This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18508 - Media-type registrations should include clipboard flavor names
Summary: Media-type registrations should include clipboard flavor names
Status: RESOLVED MOVED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 editorial
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-09 14:38 UTC by Paul Libbrecht
Modified: 2016-04-20 23:01 UTC (History)
8 users (show)

See Also:


Attachments

Description Paul Libbrecht 2012-08-09 14:38:23 UTC
As suggested on the IETF-types mailing-list, I would like to request that the working group includes two extra fields in the xx section of almost each of the media-types registrations' appendices:
http://www.ietf.org/mail-archive/web/ietf-types/current/msg01715.html

- a Windows Clipboard Flavor Name (probable link: http://msdn.microsoft.com/en-us/library/ms649013.aspx)
- Macintosh Uniform Type Identifier (see http://developer.apple.com/mac/library/documentation/FileManagement/Conceptual/understanding_utis/)

This way platforms, which mostly already define these types, would do so based on an open standard.

Previous examples of doing such include the MathML and the SVG specifications.
Comment 1 Paul Libbrecht 2012-08-09 14:39:33 UTC
I am happy to formulate proposals from experimentation and spec reading.
Comment 2 Ian 'Hixie' Hickson 2012-09-06 19:35:20 UTC
If this is
Comment 3 Michael[tm] Smith 2012-09-07 02:44:33 UTC
Hixie, it looks like your comment #2 got truncated.
Comment 4 Ian 'Hixie' Hickson 2012-09-07 17:37:39 UTC
Oops, sorry. I meant to say, If this was intended for the WHATWG spec (as it may have been since it was assigned to me), then please move this to the WHATWG product, HTML component. I've reassigned it to the default assignee in the W3C HTML5 Spec component in the meantime.
Comment 5 Travis Leithead [MSFT] 2016-04-20 23:00:53 UTC
HTML5.1 Bugzilla Bug Triage: Moved to: https://github.com/w3c/html/issues/227

If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!