W3C home > Mailing lists > Public > public-bpwg-ct@w3.org > April 2008

RE: ACTION-725: Send a list of content-types for which content transformation applies

From: Sean Patterson <SPatterson@Novarra.com>
Date: Tue, 29 Apr 2008 09:03:40 -0500
Message-ID: <24889886D84B794A9259323D7354CF33060BC882@novarrainet2.internalnt.novarra.com>
To: "Francois Daoust" <fd@w3.org>
Cc: "public-bpwg-ct" <public-bpwg-ct@w3.org>

For text/plain the main thing I had in mind was segmentation of long pages.  (RFCs and W3C recommendations for example :-)  Headers and/or footers might also be added.

> -----Original Message-----
> From: Francois Daoust [mailto:fd@w3.org]
> Sent: Tuesday, April 29, 2008 5:23 AM
> To: Sean Patterson
> Cc: public-bpwg-ct
> Subject: Re: ACTION-725: Send a list of content-types for which content
> transformation applies
> 
> Thanks Sean!
> 
> I was about to react on "text/xml" but remembered that it is indeed
> possible to serve XHTML pages using this generic content type, as
> explained in:
> http://www.w3.org/TR/xhtml-media-types/
> (I only mention it so that I don't forget about it again ;-))
> 
> I'm more puzzled by "text/plain". What are the transformations that a
> proxy may do to resources served with that content type? A conversion to
> an HTML response?
> 
> François.
> 
> 
> Sean Patterson wrote:
> > Here is a list of content types that a CT proxy may want/need to
> transform:
> >
> > ***_Text and markup:_*
> >
> > text/html
> >
> > application/xhtml+xml  (if not identified as mobile content in DOCTYPE)
> >
> > application/xml  (if XTHML and not identified as mobile content in
> DOCTYPE)
> >
> > text/xml  (if XTHML and not identified as mobile content in DOCTYPE)
> >
> > text/plain
> >
> > application/rtf
> >
> > ***_De facto_****_ standards and proprietary types_****_:_****__*
> >
> > application/pdf
> >
> > application/msword
> >
> > application/msexcel
> >
> > application/vnd.ms-excel
> >
> > application/vnd.ms-powerpoint
> >
> > application/mspowerpoint
> >
> > application/x-shockwave-flash
> >
> > ***_CSS:_*
> >
> > text/css
> >
> > ***_Images:_*
> >
> > image/gif
> >
> > image/jpeg
> >
> > image/png
> >
> > ***_JavaScript:_*
> >
> > application/x-javascript
> >
> > text/javascript
> >
> > I think this includes the most common content types that would be
> > transformed, but it's possible I've left some off.  Of course there are
> > a large number of uncommon content types that a particular CT proxy may
> > want to transform.
> >
> > I've left multimedia types (audio, video) off the list for now.  Not
> > sure if we want to say anything about those types.
> >
> > Sean
> >
Received on Tuesday, 29 April 2008 14:03:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 29 April 2008 14:03:26 GMT