Re: [ietf-types] Request for review of standards tree registration request for OpenXPS

[Paul Libbrecht <[e-mail]>]

Le 26 janv. 2011 à 00:33, Brian Clubb a écrit :

> For your feedback on changing certain responses to lower-case, I will do so in my final submission.  I appreciate your attention to detail on this matter.

good.

> For the comment on encoding, per rfc4288 section 4.8, the possible responses here are 7bit, 8bit, binary, and framed.  This response appears to be correct for ZIP archives and matches a previous registration for Microsoft's version of XPS (http://www.iana.org/assignments/media-types/application/vnd.ms-xpsdocument).  If there is some other consideration here, I am happy to make a note of it elsewhere in the template as needed.

I am too little of an expert here.

> As to the clipboard request, I checked the clipboard values on both Windows OS and Mac OS.  For Windows, the clipboard contains the full file path to the copied .oxps file as a string.  On a Mac OS (10.x), the filename plus extension is provided on the clipboard as "text / items".  Since these conventions may change over time based on the OS independent of any changes to OpenXPS, I am not certain this would be useful as part of the template.

I'm afraid you misunderstood my request.
The objective was to specify within this registration names that would denote one of the alternate representations of a fragment copied to clipboard to be encoded in OpenXPS. This would allow fragments to be stored by one application in the clipboard at the copy command and to be read from the clipboard at the paste command.

Lack of specifying this in the past for MathML has lead to a multitude of names, mostly killing interoperability, with the last suggest being... put the XML in the text flavor (which is clearly wrong for, say, a mail).

(see the MathML and SVG registrations for examples)

paul