[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: reason for application/iotp-xml (was RE: Registration of MIME med ia type APPLICATION/IOTP)
- To: Keith Moore <moore@xxxxxxxxxx>
- Subject: Re: reason for application/iotp-xml (was RE: Registration of MIME med ia type APPLICATION/IOTP)
- From: ned.freed@xxxxxxxxxxxx
- Date: Sun, 12 Mar 2000 15:14:36 -0800 (PST)
- Cc: Scott Lawrence <lawrence@xxxxxxxxxxx>, Dan Kohn <dan@xxxxxxxxxxxxx>, "'Keith Moore'" <moore@xxxxxxxxxx>, ietf-822@xxxxxxx, ietf-xml-mime@xxxxxxx, ietf-types@xxxxxxxx, "Martin J. Duerst" <duerst@xxxxxx>, MURATA Makoto <muraw3c@xxxxxxxxxxxxx>, ned.freed@xxxxxxxxxxxx, "Donald E. Eastlake 3rd" <dee3@xxxxxxxxxxxxxxxxxx>
- In-reply-to: "Your message dated Sun, 12 Mar 2000 12:16:38 -0500" <>
- List-archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
- List-id: <ietf-xml-mime.imc.org>
- List-unsubscribe: <mailto:email@example.com?body=unsubscribe>
- References: <>
- Sender: owner-ietf-xml-mime@xxxxxxxxxxxx
> > the notion of something useful being possible with an arbitrary
> > 'video/foo' type that my application doesn't understand just doesn't
> > fly.
> yes, but it does seem fairly common to have a "universal video tool" that
> understands most video formats - perhaps even formats that the MIME
> reader doesn't know about. having such a tool as the default handler
> for video/* allows your MIME reader to play video clips even when the
> specific video/ type isn't registered with it. similarly for audio/*.
Exactly right. I'd also add "image" to the list.