Re: [w3c/editing] Add revised OS custom format naming. (#316)

@dway123 commented on this pull request.



> +
+On Windows it will be inserted as `Web Custom Format Map`, on MacOS `com.web.custom.format.map` & On Linux/Android/CrOS etc `application/web;type="web/customformatmap"`.
+The payload in this format map will be of type JSON with the key representing the MIME type and the web custom format as the value.
+e.g. On Windows the web custom format map will have the below payload:
+```
+{
+
+  "text/html" : "Web Custom Format0",
+  "text/plain" : "Web Custom Format1",
+  "text/csv" : "Web Custom Format2"
+}
+```
+
+The web custom format in the value contains the actual payload of the custom MIME type. It will be serialized in terms of raw bytes and will have the below formating naming convention:
+
+On MacOS (and iOS), clipboard formats are named using the UTI reverse-DNS naming convention. Therefore, a MIME type `"custom/format"` will be transformed to `"com.web.custom.format(0-99)"`. Note that the pickling prefix `"com.web"` precedes the transformed format name `"custom.format"`, and the slash is converted to a period.

Ooh yeah, it read to me like if the web author provided "foo/type", it will be transformed to `"com.web.foo.type(0-99)"`. From our discussions, it seems instead like the web-provided type won't affect naming of OS-registered formats.

Maybe we could mention the web-provided format in line 138 in the more platform-neutral explanation, then just discuss how each platform will name the container formats here?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/pull/316#discussion_r674222495