Subject: Re: Mime-types
From: Thomas Fletcher (thomasf@qnx.com)
Date: Thu Feb 08 2001 - 14:28:01 CST
On Thu, 8 Feb 2001, WJCarpenter wrote:
> > One minor detail - what is the Abiword mime-type? I guess something
> > like application/x-abiword would be a reasonable stab at it. Or do
> > we want to register it officially, and hence lose the 'x-'? Or
> > even, has someone already registered it?
>
> I think we want to register a MIME type officially. It's a fairly
> painless process, and I'd be happy to own the logistics of doing the
> registration once there is some concensus on what it should be. (So,
> if someone else wants to do the registration stuff, tell me explicitly
> or I'll assume it's on my plate.)
I think that having you own this issue is a great idea. It is all
yours!
> The controlling document for this is RFC-2048. Here are some
> highlights from that and my own biased experience/observations of the
> process (you get to guess which is which :-)
>
[Naming Rules, Regulations and Conventions Snipped]
Since I'm the guy who did the initial bindings for BeOS I'll tell
you the rational behind the naming.
There are two things that need to be named. The first ... for
identification by other apps for lauching puporses ... is the
actual application id. This I think should be:
application/vnd.abisuite.abiword
The second is the label to give to the output files that abiword
produces. Since the files are textual, and the text category
is a valid place for our files, I would suggest text/abiword as
the content type for the files.
Thus this mapping results in telling the system that text/abiword
(or really just text/*) files are handled by the type identified
as application/vnd.abisuite.abiword.
Just my two cents for what it is worth.
Thomas
-------------------------------------------------------------
Thomas (toe-mah) Fletcher QNX Software Systems
thomasf@qnx.com Neutrino Development Group
(613)-591-0931 http://www.qnx.com/~thomasf
This archive was generated by hypermail 2b25 : Thu Feb 08 2001 - 14:27:09 CST