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

Paul Libbrecht <> Tue, 01 February 2011 18:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EEFEA3A6C41 for <>; Tue, 1 Feb 2011 10:42:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cSm+OHTRlIgC for <>; Tue, 1 Feb 2011 10:42:36 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id D1FCA3A6D8D for <>; Tue, 1 Feb 2011 10:42:35 -0800 (PST)
Received: from ( []) by (8.13.8/8.13.8) with ESMTP id p11IjGAY026587 for <>; Tue, 1 Feb 2011 13:45:36 -0500
Received: from ( []) by (node=mrbap2) with ESMTP (Nemesis) id 0LnDWH-1QNEsH38ZR-00hvPH; Tue, 01 Feb 2011 19:45:14 +0100
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="iso-8859-1"
From: Paul Libbrecht <>
In-Reply-To: <>
Date: Tue, 01 Feb 2011 19:45:09 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <>
To: Brian Clubb <>
X-Mailer: Apple Mail (2.1082)
X-Provags-ID: V02:K0:eFtutV0ujrPX8uZhdDcHAChAmK1zkbZTVJe3NWPA8Yg rjEJwhA8SwF3ckIclm3qJ+YVPj8emqkcn3uvTGDdiCwOezjuqB dCjv2u1I1i8UVV19BmiHGCcjacLW4Wkkn2MYpUuGXB7D+ZWvId riM3L8GYQn8tfSSc08FYNdnuDNBP7p0Rgl1vQRrXKIcMamDaGp 3UmexGbOp583mnz4JwR2oqgmPziMYHq4sDIBWn9zrw=
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 ( []); Tue, 01 Feb 2011 13:45:36 -0500 (EST)
Cc: "" <>
Subject: Re: [ietf-types] Request for review of standards tree registration request for OpenXPS
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Media \(MIME\) type review" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 01 Feb 2011 18:42:37 -0000


my suggestion was to add something similar to the following in the Additional Information section:

    Macintosh Universal Type Identifier code:
        org.ecma.xps conforms to
    Windows Clipboard Name:

This allows putting or expecting OpenXPS in the clipboard or a drag-and-drop, when this comes, to safely put and select by name.

I do not think that stating that it must be a complete OpenXPS file nor anything wrt its name is useful. 
(the first is natural, the second is not applicable since clipboards don't have filenames that are visible).


Le 1 févr. 2011 à 19:27, Brian Clubb a écrit :

> Thanks, Paul!  I appreciate the detailed feedback!
> I propose to add the following to the "Additional Information" section of the template:
> "To ensure interoperability, the clipboard format must be a complete OpenXPS file with .oxps extension."
> Thanks!
> Brian
> -----Original Message-----
> From: Paul Libbrecht [] 
> Sent: Monday, January 31, 2011 12:58 PM
> To: Brian Clubb
> Cc:
> Subject: Re: [ietf-types] Request for review of standards tree registration request for OpenXPS
> Hello Brian, 
> Le 31 janv. 2011 à 19:33, Brian Clubb a écrit :
>> While the OpenXPS package contains XML, the document itself requires the hierarchical tree structure of pages and resources to be functional.  It is intended that only a complete OpenXPS document would ever be posted to the clipboard.  
> Sure. Only well formed data here (and well formedness is more than XML's).
>> Posting a fragment of an OpenXPS file to the clipboard would not be a useful scenario in the same way that I understand it would work in MathML or SVG.  The resource tree in OpenXPS is integral to its functionality.
> But that is clear.
> It doesn't remove the usefulness of such a thing.
> As I said, PDF is the preferred flavor for vector graphics on MacOSX.
> And rest assured that copying from a page of a 200 pages book with Apple Preview does not create a PDF with  many pages when copying a rectangle.
> Earlier examples on the mac of such transfers include the PICT format and the Adobe "AIFB" (?? I think ??) format which was taken huge time to be produced when you had just copied something, say, in PhotoShop and was switching away from it (in MaOS 7-9, I suppose the same must have been done on Windows).
>> For example, copying the XML for a fixed page out of one file onto the clipboard would not take into account the image and font resources which are stored in other locations in the OpenXPS file.  
> That's the duty of the clipboard exporter. A normal composition programme can do that but viewers may have difficulties "at first", this is true.
> In the very same fashion copying html in a browser also inlines all the styles (even coming from very far from this element) when going out to, say, an email or word-processing application (in html or rtf).
>> Furthermore, re-integrating that page markup into the structure of another OpenXPS file would be extraordinarily complex.  If one were to wish to copy pages from one OpenXPS file to another, they would need to create a complete OpenXPS package containing just the required pages plus the required resources from the original OpenXPS package then post the new OpenXPS file to the clipboard.  The consuming application would then be able to access that file and its resources reliably and logically insert the pages and resources into their OpenXPS document package as needed.
> I'm sure this can be and has been already done.
>> If an application such as an XPS Viewer were to allow selecting and copying of the text or image elements displayed on the screen, that data would be placed on the clipboard as text or whatever image format the application chooses to provide,
> right.
> And one day that format might be openXPS.
>> but posting the markup for the selection to the clipboard would not provide the relevant resource data and hierarchy and would thus be unusable as OpenXPS at that point.
> no markup only copy.
>> I believe, then, that it is correct to say that the clipboard format would always be a complete OpenXPS file with .oxps extension.  It is the only format for the clipboard that would provide the required interoperability between OpenXPS-consuming applications.
> I think this is correct.
> paul