OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [office] auto-play presentation file format like PPS - MIME typeparameter


Hi Eike,

If document is structured as a single XML file, I believe it is appropriate to put the open mode option to <office-document-attrs>. But as I know actually all the current implementations(maybe anyone knows exceptions) are to store a document by separate XML files,and MIME types are stored in a manifest.xml file. This manifest file is plain text and can not be encrypted. So maybe it is more appropriate to put the open mode option to the manifest definition. I also think it is better not to change the MIME type content, so we can define this open mode option as an optional attribute of manifest:file-entry, just like the "manifest:media-type" or "manifest:full-path",etc.

BTW, I can not find manifest definition in ODF 1.2 draft 6, who knows what happened since ODF 1.2? literature missing or something else? thanks.

Best Regards,

Mingfei Jia()
IBM Lotus Symphony Development
IBM China Software Development LAB, Beijing
Tel: 86-10-82782244-2493 Fax: 86-10-62982924
NOTES:Ming Fei Jia/China/IBM E-mail: jiamingf@cn.ibm.com
Address: 4/F, DeShi Building No.9, East Road, ShangDi, Haidian District, Beijing 100085, PRC
Inactive hide details for Re: [office] auto-play presentation file format like PPS - MIME type parameterRe: [office] auto-play presentation file format like PPS - MIME type parameter




Re: [office] auto-play presentation file format like PPS - MIME type parameter

Eike Rathke

to:

office

2008-04-08 02:46




Hi David,

On Monday, 2008-04-07 11:41:32 -0400, David A. Wheeler wrote:

> I propose the following, to be added to the end of the "MIME Type Stream" section of the ODF document:
> "If the top-level document has a non-default 'autoplay' value, then the MIME type SHOULD have "; autoplay=" followed immediately by the autoplay value (such as "view"), creating a MIME parameter.

Doing so may actually create incompatibilities with existing software
that reads the mimetype file's content and determines whether it
_equals_ a registered MIME type. Trailing parameters would cause
a mismatch then.

Furthermore, in an unpackaged document ("flat" XML file) the MIME type
is an attribute office:mimetype of the <office:document> element, see
section "2.1.2 Document Root Attributes" of ODF 1.1, so the same
parameter option would had to be applied there.

Though RFC 2045 ff. explicitly permit parameter options I don't think
that those RFCs meant for mail header fields apply here. ODF 1.1 AFAIK
does not mention anywhere that the mimetype attribute would follow the
RFC 204x specifications for the Content-Type header field, so it might
come as a surprise to some if it now would.

I think not changing the mimetype content is vital for the recognition
of ODF document types.

 Eike

--
OpenOffice.org Engineering at Sun:
http://blogs.sun.com/GullFOSS
(See attached file: attimxsa.dat)

GIF image

attimxsa.dat



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]