Re: mimetype for ODF

[James Bryce Clark <jamie.clark@oasis-open.org>]

>Hi Jamie and Mary
>Can you give us an update on the status of the IANA mime type registration 
>for OpenDocument? * * *  Is there anything that we can do to speed this 
>up? Should we approach IANA directly?
>I have included the registration form again for reference...
>All the best, Lars

     Thanks, Lars, for doing the groundwork for this, and my apologies for 
our delayed reply.   The finalized registration may be submitted by you 
directly to IANA on behalf of OASIS and the TC, once it's complete.   Your 
draft does appear to conform to the RFCs, except in the very minor case 
noted below.

     I have inserted a few questions and possible corrections.  We 
particularly would like to bring the TC's attention to the one-time 
opportunity to name other known applications by OASIS members that now 
support ODF.   (Developers do read these posted registrations.)  If my 
notes do not raise any further questions, please go ahead and 
submit.   When you do so, please copy the TC list.

     Possible edits to the text are noted [in brackets] below.
     Questions for your consideration prior to submission are denoted by 
[COMMENT:] and bracketed below, and should be removed prior to submission.

     We're happy to discuss these if it would be useful.  But there aren't 
many, and most are either self-evident, or matters that the expertise of TC 
members can resolve efficiently.  So we do not need to see this again 
before it goes out, if the TC is satisfied with the final version.  After 
it is accepted by IANA, there may be some additional useful steps to 
discuss, to make the MIMEtypes generally known.

     Regards  Jamie Clark

~   James Bryce Clark
~   Director, Standards Development, OASIS
~   jamie.clark@oasis-open.org

====
TEXT OF REGISTRATION

#   MIME Media Type Name
Application

# MIME subtype name ( See Existing subtype names )

vnd.oasis.opendocument.text
vnd.oasis.opendocument.text-template
vnd.oasis.opendocument.text-master
vnd.oasis.opendocument.text-web
vnd.oasis.opendocument.spreadsheet
vnd.oasis.opendocument.spreadsheet-template
vnd.oasis.opendocument.graphics
vnd.oasis.opendocument.graphics-template
vnd.oasis.opendocument.presentation
vnd.oasis.opendocument.presentation-template
vnd.oasis.opendocument.image
vnd.oasis.opendocument.image-template
vnd.oasis.opendocument.formula
vnd.oasis.opendocument.formula-template
vnd.oasis.opendocument.chart
vnd.oasis.opendocument.chart-template

[COMMENT:  We noticed that you elect not to use the "+xml" form permitted 
by RFC 3023.  We assume that's a deliberate choice based on the likelihood 
that office software, and not  generic XML tools, typically will consume 
the formats.  No need to discuss, if you're satisfied with that.]

# Required parameters
- none -

# Optional parameters
- none -

# Encoding considerations
binary

# Security considerations
Documents may contain script programs which are able to perform various 
actions on behalf of the user. Applications should make the user aware of 
this fact when opening a document of unknown/not-trusted origin.

# Interoperability considerations
- none -

# Published specification
[http://www.oasis-open.org/committees/download.php/12572/OpenDocument-v1.0-os.pdf]

# Applications which use this media type

[Any application implementing the OpenDocument Format for Office 
Applications, including]
StarOffice, OpenOffice.org, KOffice [and ...]

[COMMENT:  Starting with the generic statement above seems appropriate, as 
we've done in other cases.  And are there any other apps the TC  wishes to 
name at present?  It seems to me that I have heard of several others.  We 
encourage you to include them, and list them in some neutral manner such as 
alphabetically.]

# Additional information
     * [There are no Magic number(s).]

     * File extension(s)
vnd.oasis.opendocument.text                  -> .odt
vnd.oasis.opendocument.text-template         -> .ott
vnd.oasis.opendocument.text-master           -> .otm
vnd.oasis.opendocument.text-web              -> .oth
vnd.oasis.opendocument.spreadsheet           -> .ods
vnd.oasis.opendocument.spreadsheet-template  -> .ots
vnd.oasis.opendocument.graphics              -> .odg
vnd.oasis.opendocument.graphics-template     -> .otg
vnd.oasis.opendocument.presentation          -> .odp
vnd.oasis.opendocument.presentation-template -> .otp
vnd.oasis.opendocument.image                 -> .odi
vnd.oasis.opendocument.image-template        -> .oti
vnd.oasis.opendocument.formula               -> .odf
vnd.oasis.opendocument.formula-template      -> .otf
vnd.oasis.opendocument.chart                 -> .odc
vnd.oasis.opendocument.chart-template        -> .otc

     * [There are no specified Macintosh file type code(s).]

[COMMENT:  Tweaked because the RFC specifically asks us not to use the 
formulation "none" here.]

# Intended usage
Common

# Other Information/General Comment
-none-

# Person to contact for further information
* Name
Lars Oppermann
* E-mail
lars.oppermann@sun.com

* Author/Change controller
[The OpenDocument specification sets are a work product of the OASIS 
OpenDocument Format for Office Applications  Technical Committee 
(OpenDocument TC). 
<http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office>  OASIS 
and the OpenDocument TC have change control over the specification 
sets.  The chairperson of the OpenDocument TC is] Michael Brauer 
<michael.brauer@sun.com>

[COMMENT:  Modified to the form we normally use, which points to the TC and 
so accounts for possible changes in roles over time.]

END