[minutes] CT Call Tuesday 13 May 2008

Hi,

The minutes for today's call are available at:
http://www.w3.org/2008/05/13-bpwg-minutes.html

... and copied as text below.

Resolutions taken during the call:
- don't go any further with the XHR topic [fd to write a "thank you" 
email to public-webapi]
- 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:".

Francois.




13 May 2008

    [2]Agenda

       [2] 
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008May/0016.html

    See also: [3]IRC log

       [3] http://www.w3.org/2008/05/13-bpwg-irc

Attendees

    Present
           Pontus, francois, rob, andrews, SeanP

    Regrets
           jo, MartinJ, Bryan, Murari, hgerlach

    Chair
           fd

    Scribe
           Andrew

Contents

      * [4]Topics
          1. [5]Introducing Pontus
          2. [6]XHR last call comment
          3. [7]Consistency in the behavior of the CT-proxy
          4. [8]Examination of URIs
      * [9]Summary of Action Items
      _________________________________________________________

Introducing Pontus

    Pontus2: Part of devices team in Ericsson for last 2 years. Working
    in mobile internet for 8 years. Replacing Magnus.

XHR last call comment

    <francois> [10]last call comment

      [10] 
http://lists.w3.org/Archives/Public/public-webapi/2008May/0064.html

    francois: HR is just one case. iFrame is another example.
    ... Explaining explicitly what is wanted (eg no-transform) is better
    than identifying origin of request.

    <francois> PROPOSED RESOLUTION: don't go any further with the XHR
    topic.

    +1

    <francois> +1

    <Pontus2> +1

    RESOLUTION: don't go any further with the XHR topic.

Consistency in the behavior of the CT-proxy

    francois: No guidelines about handling of sessions
    ... CT-proxies should be consistent within a session but how do we
    define a session?

    Rob: Example - content is being transformed and then a style sheet
    says no-transform
    ... links may contain URLs pointing back to CT-proxy

    francois: may be we don't need to make any recommendations in the
    guidelines.

    <francois> ACTION: daoust to summarize the issue that may be raised
    by sessions [recorded in
    [11]http://www.w3.org/2008/05/13-bpwg-minutes.html#action01]

    <trackbot-ng> Created ACTION-755 - Summarize the issue that may be
    raised by sessions [on Fran├žois Daoust - due 2008-05-20].

Examination of URIs

    <francois> [12]Sean's point

      [12] 
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008May/0000.html

    francois: Reference discussions about URIs indicating mobile content
    e.g. mobile.site.com.
    ... some content providers use such URIs already.
    ... However, URIs should not necessarily relate to the content.
    ... Guidelines should not specify specific URI patterns.

    Sean: Agree should just be a heuristic.
    ... until there is a better way.

    <francois> PROPOSED RESOLUTION: Mention examination of URIs in the
    list of heuristics in 4.4 (transformation of the response) and
    mention Sean's list (wap.*, m.*, ...) as examples

    francois: We can not come up with a comprehensive list of URI
    patterns that would indicate a mobile aware site.

    <SeanP> +1

    francois: suggest that we just site this as ah heuristic and give
    examples

    <francois> +1

    <rob> +1

    +1

    <Pontus2> +1

    <francois> PROPOSED RESOLUTION: Mention examination of URIs in the
    list of heuristics in 4.4 (transformation of the response) and
    mention Sean's list (wap.*, m.*, ...) as examples

    RESOLUTION: 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

    <francois> PROPOSED RESOLUTION: Mention examination of URIs as a
    bullet point in 4.1.2 (transformation of the request) to complete
    the list "the proxy SHOULD analyze whether it intends to offer
    transformation services by referring to [...]".

    SeanP: Should say this in the request section.

    francois: URI is one of the only indicators of mobile content at
    request time.

    <francois> PROPOSED RESOLUTION: 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:".

    <francois> +1

    <SeanP> +1

    +1

    <rob> +1

    RESOLUTION: 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:".

    francois: Aim is to publish guidelines at end June after
    face-to-face meeting.

    SeanP: Dates for face-to-face?

    francois: 16, 17, 18 June in SE France
    ... moving to "last call" indicates that we, the task force, think
    that we have solved all problems.

Summary of Action Items

    [NEW] ACTION: daoust to summarize the issue that may be raised by
    sessions [recorded in
    [13]http://www.w3.org/2008/05/13-bpwg-minutes.html#action01]

    [End of minutes]

Received on Tuesday, 13 May 2008 14:52:51 UTC