Brian Clubb | 1 Feb 19:27 2011
Picon

Re: Request for review of standards tree registration request for OpenXPS

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 [mailto:paul <at> hoplahup.net] 
Sent: Monday, January 31, 2011 12:58 PM
To: Brian Clubb
Cc: ietf-types <at> iana.org
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.
(Continue reading)

Paul Libbrecht | 1 Feb 19:45 2011
Picon

Re: Request for review of standards tree registration request for OpenXPS

Brian,

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 com.pkware.zip-archive
    Windows Clipboard Name:
        "OpenXPS"

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).

paul

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-----
(Continue reading)

MURATA Makoto | 3 Feb 00:43 2011
Picon

Re: Mime Type Reg for "application/epub+zip"

Dear colleagues,

In 2007, IDPF (http://www.idpf.org/) submitted a request to register a
standard-tree media type "application/epub+zip" for EPUB documents. 
There were no discussions or registrations, however.  The I-D 
at that time, namely http://www.idpf.org/draft-idpf-mime-ocf-01.txt, has
already expired.

Since then, things have changed.  EPUB has become a very important 
e-book format, and is very widely used by Apple, Adobe, Sony, Barns & Noble, 
among others.  EPUB implementations appear to use "application/epub+zip".
The IDPF EPUB WG is actively designing the next version of EPUB, namely
EPUB3, and has committed to finish it in May, 2011.

Standardization of EPUB at ISO, IEC, or JTC1 is also being discussed 
at ISO/IEC JTC1/SC34/AHG4 (EPUB).    IDPF is involved.

Moreover, the EPUB WG of IDPF is currently talking about introducing
fragment identifiers for EPUB3.   A proposal is available at
http://code.google.com/p/epub-revision/wiki/ImplementationProposalFragmentIdentifier

For EPUB to be a good citizen of Internet, I think that registration 
of application/epub+zip is a necessary step.  I am wondering how we 
should go forward.  Here are some possibilities I can think of.

1) Create an IDPF EPUB3 spec,  describe everything about this media 
type (including possible frag. identifiers), and request for the
approval of IESG.

2) Create an ISO or IEC or JTC1 EPUB specification (possible EPUB2),
(Continue reading)

Bjoern Hoehrmann | 3 Feb 01:21 2011
Picon
Picon

Re: Mime Type Reg for "application/epub+zip"

* MURATA Makoto wrote:
>For EPUB to be a good citizen of Internet, I think that registration 
>of application/epub+zip is a necessary step.  I am wondering how we 
>should go forward.  Here are some possibilities I can think of.
>
>1) Create an IDPF EPUB3 spec,  describe everything about this media 
>type (including possible frag. identifiers), and request for the
>approval of IESG.
>
>2) Create an ISO or IEC or JTC1 EPUB specification (possible EPUB2),
>describe everything there, and request for the approval of IESG.
>
>3) Begin with an I-D and describe everything there and try to reach 
> (proposed standard?) RFC status, and register the media type.

Well, as far as ietf-types review is concerned, if a type is actually
used, then it should be registered, the registration should not clash
with conflicting usage (like, if the type in question is also used for
something else) and the registration information should meet the re-
quirements of RFC 4288 and dependencies. From that perspective, the
options above seem relatively equal. Your third option seems to have
the best chances to produce results quickly though.
--

-- 
Björn Höhrmann · mailto:bjoern <at> hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Brian Clubb | 15 Feb 19:08 2011
Picon

Re: Request for review of standards tree registration request for OpenXPS

Paul,

Thanks again for the feedback.  I am making the changes to the template.  I am including, then, the final
template in this reply.  If there are no other issues, then I will submit it for acceptance by the end of this week.

Thanks for all your help!  It is much appreciated!

Brian

<template>
Name : Brian Clubb

Email : bclubb <at> microsoft.com

MIME media type name : application

MIME subtype name : Standards Tree - openxps

Required parameters : N/A

Optional parameters :
N/A

Encoding considerations : 8-bit

Security considerations :
OpenXPS uses ZIP compression as specified in .ZIP File Format Specification from PKWARE, Inc., version
6.2.0 (2004).  ZIP compressed XML requires parsing untrusted XML data and untrusted ZIP data.  consumer is
responsible for validating the .zip archive, the XML structure, and the resource content.  Per spec,
there should be no active content provided as part of the OpenXPS format.  The consumer must ensure that no
(Continue reading)


Gmane