<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>There are different sets of generic settings.</div><div><br></div><div>for online sets there could be 20 for low vision.</div><div><br></div><div>in a kiosk there might be only 10 tags for all disabilities -- and the tag would be labelled with names that make sense to the people in the kiosk perhaps - or to the person who does not know what they want.    For example someone who is older may not know they want high contrast or even what it is.  But if there are two tags for low vision they might try them both and see if one of them makes the phone easier to use.    THis all needs exploration -- but the idea is to discover   a) what the set of 'starter' configs might be and b) what to call them that will be most useful in that particular situation. </div><div><br></div><div>RE terms to use -- we should do the same.      </div><div><br></div><div>Statement seems to be something quite definite rather than a set of options or variable values etc.   But I am open to anything.  I just think that profiles is increasingly looking like the wrong word.  </div><div><br></div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><i>Gregg</i><br><div>--------------------------------------------------------<br>Gregg Vanderheiden Ph.D.<br>Director Trace R&D Center<br>Professor Industrial & Systems Engineering<br>and Biomedical Engineering<br>University of Wisconsin-Madison<br></div><br>Co-Director, Raising the Floor - International<br>and the Global Public Inclusive Infrastructure Project<br><a href="http://Raisingthefloor.org">http://Raisingthefloor.org</a>   ---   <a href="http://GPII.net">http://GPII.net</a></div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br></div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br></div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br></div></span></div></span></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Jul 6, 2012, at 2:44 PM, Treviranus, Jutta (Academic) wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>This discussion of a generic set is straying a little too close to what people objected about profiling, e.g.,  "for people with low vision". I think whatever we call it we always want to state it as functional needs and preferences even when generic  "magnified, high contrast". People with low vision are not homogenous. There are many different functional strategies that apply. In WebForAll when we wanted to start generic we used larger categories for this interaction from the user's perspective, the utility  had the choice "Make it easier to see".<br><br>Regarding set vs. statement, I think we want to also communicate the concept that the user is in control or making the wish, stating their needs and preferences.  Set is technical and mathematical to me. I agree with Erlend that internationalization is important. I wonder whether there is another term we could use. <br><br>BTW, my dictionary has the following definitions for Statement:<br>state·ment   [steyt-muhnt]  noun<br>1.something stated- written words of something such as a fact, intention, or policy, or an instance of this<br>• a statement of intent<br>2.a communication or declaration in speech or writing, setting forth facts, particulars, etc.<br>3.a single sentence or assertion: I agree with everything you said except for your last statement.<br>4.Commerce . an abstract of an account, as one rendered to show the balance due.<br>5.an appearance of a theme, subject, or motif within amusical composition.<br><br>Jutta<br><br>On 2012-07-06, at 1:46 AM, Gregg Vanderheiden wrote:<br><br><blockquote type="cite">How about we use the word  KEY and  SET<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The KEY is what you pass up to the server so that it can figure out what preference SET to look up / use.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">You can have many SETS that you might use.   One for when in private.  one while in public.  One that is Silent.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">There can be keys to GENERIC SETS.<br></blockquote><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">  </span><span class="Apple-tab-span" style="white-space:pre">    </span>- for example - an older person doesn’t have a set of preferences yet and they go up to a kiosk to buy a phone.  The user says 'do you have one with large print".  The person at the phone kiosk (a little shop in the aisle of a big shopping market)   doesn’t really know what features there are or how to set them up.  But they do have a set of tags behind the counter and one says "for people low vision".   They touch it to the phone and it turns on all the low vision features.   If the phones have more than a simple set then there might be several "low vision 1" 2, 3 etc so the older person can try different sets easily. <br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">     </span><span class="Apple-tab-span" style="white-space:pre">    </span>- another example -- a person is traveling and doesn’t want to expose their whole SET of preferences to this unknown machine (that might data mine them).  They only need basic setting on this ticket machine  so they use a GENERIC SET that matches them pretty well and they get it set up but leave only a Generic footprint behind.  (anything of course leaves some info -- but if they don't log in -- there is just a note that someone with that generic profile used that kiosk) .<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Gregg<br></blockquote><blockquote type="cite">--------------------------------------------------------<br></blockquote><blockquote type="cite">Gregg Vanderheiden Ph.D.<br></blockquote><blockquote type="cite">Director Trace R&D Center<br></blockquote><blockquote type="cite">Professor Industrial & Systems Engineering<br></blockquote><blockquote type="cite">and Biomedical Engineering<br></blockquote><blockquote type="cite">University of Wisconsin-Madison<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Co-Director, Raising the Floor - International<br></blockquote><blockquote type="cite">and the Global Public Inclusive Infrastructure Project<br></blockquote><blockquote type="cite"><a href="http://Raisingthefloor.org">http://Raisingthefloor.org</a>   ---   <a href="http://GPII.net">http://GPII.net</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Jul 6, 2012, at 12:52 AM, Andy Heath wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">What is the relationship between the keys and sets of preferences ?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">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 ?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">andy<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">instead of saying "user is identified"<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">how about  we say "user’spreferencekeyis read (or obtained)"<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">In general<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">We talk about the user "identifying themselves"  and that info being<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">used to fetch their preferences all over the place as the first step<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">In fact they don't have to identify themselves - they just need to<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">provide a key that can be used to look up a set of preferences.  They<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">don't even have to be their preferences. they could be a generic preference.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">This has privacy implications and implies that users identify themselves<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">in order to use GPII when they don't.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">OK to change our language?<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Someone have a better phrase to use than     "User preference key"  ?<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/Gregg/<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">--------------------------------------------------------<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Gregg Vanderheiden Ph.D.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Director Trace R&D Center<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Professor Industrial & Systems Engineering<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">and Biomedical Engineering<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">University of Wisconsin-Madison<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Co-Director, Raising the Floor - International<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">and the Global Public Inclusive Infrastructure Project<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://Raisingthefloor.org">http://Raisingthefloor.org</a>   --- <a href="http://GPII.net">http://GPII.net</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Accessforall mailing list<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="mailto:Accessforall@fluidproject.org">Accessforall@fluidproject.org</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://lists.idrc.ocad.ca/cgi-bin/mailman/listinfo/accessforall">http://lists.idrc.ocad.ca/cgi-bin/mailman/listinfo/accessforall</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Cheers<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">andy<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">-- <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">__________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Andy Heath<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://axelafa.com">http://axelafa.com</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">Accessforall mailing list<br></blockquote><blockquote type="cite"><a href="mailto:Accessforall@fluidproject.org">Accessforall@fluidproject.org</a><br></blockquote><blockquote type="cite"><a href="http://lists.idrc.ocad.ca/cgi-bin/mailman/listinfo/accessforall">http://lists.idrc.ocad.ca/cgi-bin/mailman/listinfo/accessforall</a><br></blockquote><br></div></blockquote></div><br></body></html>