ISSUE-241: Tokenization of URIs
Tokenization of URIs
Tokenization of URIs
- State:
- CLOSED
- Product:
- Guidelines for Web Content Transformation Proxies
- Raised by:
- Jo Rabin
- Opened on:
- 2008-04-03
- Description:
- I removed the following from an editorial note in the document, but it needs further discussion:
Rob noted at the F2F that Openwave tokenizes URIs - I'm uncertain whether this means the list of methods here needs discussion, or whether this has an effect further on in the document. - Related Actions Items:
ACTION-772 on Robert Finean to Review draft with ISSUE-241 in mind and see if some further actions are needed - due 2008-06-17, closed- Related emails:
- Content Transformation Guidelines 1m (Rev 13) nearly now all 'ship shape and Bristol fashion' (from jrabin@mtld.mobi on 2008-07-22)
- Content Transformation Guidelines 1m (Rev 13) [was Re: Content Transformation Guidelines 1l (Rev 12) and Change List] (from jrabin@mtld.mobi on 2008-07-22)
- RE: Content Transformation Guidelines 1l (Rev 12) and Change List (from SPatterson@Novarra.com on 2008-07-18)
- Content Transformation Guidelines 1l (Rev 12) and Change List (from jrabin@mtld.mobi on 2008-07-11)
- [minutes] BPWG F2F in Sophia, day 1 (from fd@w3.org on 2008-06-17)
- Content Transformation Guidelines - preparation for the F2F (from fd@w3.org on 2008-06-13)
- [minutes] CT Call Tuesday 10 June 2008 (from fd@w3.org on 2008-06-10)
- Re: [agenda] CT Call Tuesday 10 June 2008 (from fd@w3.org on 2008-06-10)
- ISSUE-241 (Tokenization of URIs): Tokenization of URIs [Content Transformation Guidelines] (from sysbot+tracker@w3.org on 2008-04-03)
Related notes:
For the F2F in Sophia:
- no problem identified so far
- rob has an action to review the latest draft with this issue in mind
-> Close the issue if no problem arises
RESOLUTION: For CT guidelines, except in the case of https, the content transformation guidelines document does not differentiate between URI rewriting and so-called "transparent" proxy operation.
RESOLUTION: For CT guidelines, for included resources within a page, additional content tasting is not required.
RESOLUTION: Regarding ISSUE-241, in the CT guidelines we should state that when the proxy makes a request for a linked resource to a new "web site", then what's in section 4.1.2 should happen (allowing for different heuristics for determining whether request is to a different or the same "web site" but giving "hitting a new domain name" as a good example. And remove the word "session" from the previous resolution on 4.1.2.
RESOLUTION: Regarding ISSUE-241, in the CT guidelines we agree that the proxy does not have to taste every linked resource.
Closed after heavy discussion during F2F Day 1 in Sophia-Antipolis
François Daoust, 16 Jun 2008, 12:51:08Display change log
