ACTION-723: Raise discussion on session settings vs persistent settings

Context
-------
If I recall correctly, it started with an in-scope/out-of-scope 
discussion resulting in the "Control by Administrative or Other 
Arrangements" section (now §3.2.3) being created and detailed.

I proposed a list of examples to fill that section, Bryan amended it and 
proposed to add user static preferences  as an example in the list of 
out-of-scope examples. Last email of the thread is available at:
http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Mar/0025.html

The idea was that static (or permanent) settings would be out-of-scope 
while session (or semi-permanent) settings would be in scope. There were 
some more discussion during a call where we wondered what session could 
mean here:
http://www.w3.org/2008/03/25-bpwg-minutes.html#item05
... and created this action.


Persistent vs. Semi-persistent?
-------------------------------
Actually, the more I think about it, the less I understand why we should 
make a distinction (even less, oppose) persistent and semi-persistent 
settings:

- both pre-suppose that the CT-proxy has means to record the user's 
preferences.
- in both cases, we're talking about control by the User.
- in both cases, we're mostly talking about indirect interaction between 
the CT-proxy and the user. In other words, the user is not prompted by 
the proxy during browsing (although he may be), but rather sets 
preferences prior to browsing.
- I'm not sure there's any such thing as the notion of a "user session" 
in most CT-proxies. Is there?

To split them between in-scope and out-of-scope seems confusing. I 
suggest we simply don't make any distinction between "persistent" and 
"semi-persistent", and call the whole thing "persistent" (or "static"?)


Proposed resolution
--------------------
Rewrite §3.2.1 roughly based on what it was before:
"They MAY also provide the ability for their users to make a persistent 
expression of preferences."


François.


PS: note this is different from the discussion we need to have on 
"session" for "consistency" purposes in §4.1.2.

Received on Monday, 21 April 2008 14:39:03 UTC