ISSUE-255 (the mdot thing): Subdomain and Path as a heuristic in content transformation [Content Transformation Guidelines]

ISSUE-255 (the mdot thing): Subdomain and Path as a heuristic in content transformation [Content Transformation Guidelines]

http://www.w3.org/2005/MWI/BPWG/Group/track/issues/

Raised by: Jo Rabin
On product: Content Transformation Guidelines

Resolutions of CT TF of 13 May: (I wasn't there)

- Mention examination of URIs in the list of heuristics in 4.4 
(transformation of the response) and mention SeanP's list (wap.*, m.*, 
....) as examples
- Mention examination of URIs also in 4.1.2 (transformation of the 
request) to complete the list after "the proxy SHOULD analyze whether it 
intends to offer transformation services by referring to:".

The specific list of sub-domains given 

m.*
mobile.*
wap.*
*.mobi
<domain>/m/*
<domain/mobile/*

a couple of questions:

i) on the request side, how does the URI requested constitute a heuristic, if we are saying that the headers should not be transformed a) unless the user requests it and b) unless the request is rejected?

ii) on the response side, I think we may mean the URI of the response (i.e. content-location or the result of resolving redirects, rather then the originally requested URI, and if that is what we mean we should say so ....)

Jo

Received on Friday, 6 June 2008 14:42:45 UTC