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

Re: ACTION-831: Continue discussion of the title on the list (CT Guidelines; LC-2018)

From: Francois Daoust <fd@w3.org>
Date: Wed, 10 Sep 2008 15:17:04 +0200
Message-ID: <48C7C8D0.2080804@w3.org>
To: Sean Patterson <SPatterson@Novarra.com>
CC: public-bpwg-ct <public-bpwg-ct@w3.org>

Thanks for this long list of choices, Sean.

About the long title in 10., I would even complete it with 
"communication", because what we're trying to achieve here is to define 
ways for Content Providers and Content Transformation Proxies to 
communicate with each other.

"Content Transformation by HTTP Proxies: Communication Guidelines for 
Content Providers and Content Transformation Proxies"

... but I don't quite like the result. I'm merely mentioning it in case 
someone comes up with a better idea that captures the abstract more 
precisely.

That being said, I'd go for 12. as well, which also has the advantage of 
not changing the title too radically.

Francois.


Sean Patterson wrote:
> In LC-2018 it is suggested the title “Content Transformation Guidelines” 
> is too generic and uninitiated readers would really not have any clue 
> that the CT Guidelines refer to content transformation using an HTTP 
> proxy server for (typically) mobile devices.  I can see the point and on 
> the CT call on last Tuesday, the consensus seemed to be that a more 
> descriptive name would be nice if we could come up with a good one.
> 
> Here are some suggestions from LC-2018, from the teleconference, and a 
> few that I came up with:
> 
> 1. Mobile Web Content Transformation (from LC-2018)
> 
> 2. Content Transformation for Mobile Presentation (from LC-2018)
> 
> 3. Content Adaptation Guidelines
> 
> 4. Content Transformation by Proxies
> 
> 5. Content Transformation by HTTP Proxies
> 
> 6. Content Transformation by HTTP Proxies: Guidelines
> 
> 7. Guidelines for Content Transformation by HTTP Proxies
> 
> 8. Guidelines for Content Transformation Proxies
> 
> 9. Content Transformation Orientation Guide
> 
> 10. Content Transformation by HTTP Proxies:  Guidelines for Content 
> Providers and Operators of Content Transformation Proxies (in case we 
> want a really long title)
> 
> 11. Guidelines for Operation of and Interaction with Content 
> Transformation Proxies
> 
> 12. Content Transformation Proxies: Guidelines
> 
> 13. Content Transformation by HTTP Proxies for Limited Browsers: Guidelines
> 
> In most of the above, we could also replace the word “proxies” with 
> “proxy servers”.
> 
> In a previous call I remember that we discussed adding “mobile” to the 
> title and decided against it because the CT Guidelines did not 
> necessarily only have to apply to mobile devices.
> 
> With the word “guidelines” there are several options: put it the 
> beginning of the title (e.g., 11), put it at the end (e.g., the current 
> title), make it a subtitle (e.g., 6), or just leave it off altogether 
> (e.g., 4).  There are lots of combinations that I haven’t enumerated above.
> 
> I think I’m partial to 8 or 12.  10 is really not that bad (although 
> others may disagree with me) if we want a more descriptive title.
> 
> Sean
> 
Received on Wednesday, 10 September 2008 13:17:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 10 September 2008 13:17:38 GMT