[Accessforall] [Profiles] "User preference key" instead of "User ID"

Gregg Vanderheiden gv at trace.wisc.edu
Fri Jul 6 10:05:29 UTC 2012


We seem to have converged on using KEY.   Seems to have many nice aspects -- including the feeling of security it engenders. 


Jutta   -  have you seen the discussion about using  "SET" instead of 'STATEMENT" ?

Your thoughts there?




On Jul 6, 2012, at 1:27 AM, Treviranus, Jutta (Academic) wrote:

> I like the notion of a key. You can have several keys, they don't need to have your personal information attached to them.  They unlock something or start something. Each key could be attached to a specific PNP. There could be a master key as well. 
> 
> Given the sensitivity regarding the term profile and profiling, I'm wondering whether we can avoid using the term. The PNP referred to Personal Needs and Preferences. We have been using the term "statement" rather than "profile", or PNP statement as a less contentious term. Also it was pointed out to us that people are profiled by others but they state what they need and prefer. 
> 
> Jutta
> 
> 
> On 2012-07-05, at 7:00 PM, Liddy Nevile wrote:
> 
>> I think we simply need to say that they are identifying the needs profile (PNP) they want to use -
>> 
>> Liddy
>> 
>> On 06/07/2012, at 8:52 AM, Andy Heath wrote:
>> 
>>> What is the relationship between the keys and sets of preferences ?
>>> Is it that one key can be associated with more than one set of preferences ?  Is one set of preferences associated with more than one key ?
>>> 
>>> andy
>>>> 
>>>> instead of saying "user is identified"
>>>> 
>>>> how about  we say "user’spreferencekeyis read (or obtained)"
>>>> 
>>>> 
>>>> In general
>>>> 
>>>> We talk about the user "identifying themselves"  and that info being
>>>> used to fetch their preferences all over the place as the first step
>>>> 
>>>> In fact they don't have to identify themselves - they just need to
>>>> provide a key that can be used to look up a set of preferences.  They
>>>> don't even have to be their preferences. they could be a generic preference.
>>>> 
>>>> This has privacy implications and implies that users identify themselves
>>>> in order to use GPII when they don't.
>>>> 
>>>> 
>>>> OK to change our language?
>>>> 
>>>> Someone have a better phrase to use than     "User preference key"  ?
>>>> 
>>>> /Gregg/
>>>> --------------------------------------------------------
>>>> Gregg Vanderheiden Ph.D.
>>>> Director Trace R&D Center
>>>> Professor Industrial & Systems Engineering
>>>> and Biomedical Engineering
>>>> University of Wisconsin-Madison
>>>> 
>>>> Co-Director, Raising the Floor - International
>>>> and the Global Public Inclusive Infrastructure Project
>>>> http://Raisingthefloor.org   --- http://GPII.net
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Accessforall mailing list
>>>> Accessforall at fluidproject.org
>>>> http://lists.idrc.ocad.ca/cgi-bin/mailman/listinfo/accessforall
>>>> 
>>> 
>>> 
>>> 
>>> Cheers
>>> 
>>> andy
>>> -- 
>>> __________________
>>> Andy Heath
>>> http://axelafa.com
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Accessforall mailing list
>>> Accessforall at fluidproject.org
>>> http://lists.idrc.ocad.ca/cgi-bin/mailman/listinfo/accessforall
>> 
>> _______________________________________________
>> Accessforall mailing list
>> Accessforall at fluidproject.org
>> http://lists.idrc.ocad.ca/cgi-bin/mailman/listinfo/accessforall
> 
> _______________________________________________
> Profiles mailing list
> Profiles at lists.gpii.net
> http://lists.gpii.net/cgi-bin/mailman/listinfo/profiles

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/accessforall/attachments/20120706/a5789ef9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7318 bytes
Desc: not available
URL: <http://lists.idrc.ocad.ca/pipermail/accessforall/attachments/20120706/a5789ef9/attachment.bin>


More information about the Accessforall mailing list