Re: [clipboard API] platform integration stuff - in spec or out of scope?

We never really came to a decision on if RTF ("application/rtf") should be
listed as a mandatory MIME type but the general consensus seemed to be
leaning toward "yes":
   https://lists.w3.org/Archives/Public/public-webapps/2013OctDec/0197.html

Sincerely,
    James Greene


On Sat, Jan 31, 2015 at 5:31 PM, Hallvord Reiar Michaelsen Steen <
hsteen@mozilla.com> wrote:

>
> I don't know what these "map to" on platforms that do not use MIME types
> to describe clipboard contents. Should this information be dug up and
> included?
>
>
>> First request: can we add the three MathML media-types?
>>
>
> I know you've brought this up before, I haven't done anything about it and
> it's partly because I'm not actually sure myself what an implementation
> would have to do to "support" a data type..
>
>
>> I think I could help dig the names out by looking at the following
>> documents:
>>
>>
> That would be absolutely terrific Paul - maybe make a wiki page or
> etherpad somewhere? It would really help me - coming more from the
> JavaScript side of things I can figure out and describe how all the
> JavaScript stuff works, but it's much harder to determine how the platform
> side needs to be specified.
>
>
>> -
>> http://developer.apple.com/mac/library/documentation/FileManagement/Conceptual/understanding_utis/
>> -
>> https://msdn.microsoft.com/en-us/library/system.windows.dataformats.aspx
>>
>> Also, some specs and media-type-registration RFCs indicate the names in
>> the native formats.
>> I think this would be the right place to hunt too  (I know that MathML
>> and SVG do).
>> Probably it'll never be complete (e.g. I do not think
>> application/octet-stream can have a name on clipboards).
>>
>
> So..  If the most important platforms do not have a clipboard format or
> description for a specific MIME type, does that mean telling
> implementations to "support" it is meaningless? Sort of seems like it..
> -Hallvord
>