<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Solving the &#8220;It&#8221; Problem</title>
	<atom:link href="http://www.azarask.in/blog/post/solving-the-it-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.azarask.in/blog/post/solving-the-it-problem/</link>
	<description>-- aza &#124; ɐzɐ --</description>
	<lastBuildDate>Tue, 07 Sep 2010 21:31:38 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Drew F</title>
		<link>http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3953</link>
		<dc:creator>Drew F</dc:creator>
		<pubDate>Mon, 16 Feb 2009 01:55:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=354#comment-3953</guid>
		<description>I don&#039;t really have anything new to offer (although I am trying to think of something). I have opinions about the already mentioned concepts. 
I am against the quotation system. I agree with Aza it doesn&#039;t feel natural. I think a main point of the natural language command architecture is to impose far less semantics.

Having specific key words has both a positive and negative effects. The positive being that this seems like a more frequently used word than image or url so the probability of errors occurring are less likely. But by making more keywords if the problems do occur now conflicts arise from each of those keywords.

I like Gerv&#039;s idea of ths and hm but I am more favored to thiss and himm. I have gotten used to this on the iPhone, and although not very discoverable, it is very memorable (as I use it for getting we&#039;ll instead of well). This seems like a solution for a more technically savvy user though as I also use it in things like textExpander. Although I feel that this should be the demographic ubiquity targets, if these features will eventually be added to the awesome bar then I feel that Aza&#039;s recommendation fits a more general audience.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t really have anything new to offer (although I am trying to think of something). I have opinions about the already mentioned concepts.<br />
I am against the quotation system. I agree with Aza it doesn&#8217;t feel natural. I think a main point of the natural language command architecture is to impose far less semantics.</p>
<p>Having specific key words has both a positive and negative effects. The positive being that this seems like a more frequently used word than image or url so the probability of errors occurring are less likely. But by making more keywords if the problems do occur now conflicts arise from each of those keywords.</p>
<p>I like Gerv&#8217;s idea of ths and hm but I am more favored to thiss and himm. I have gotten used to this on the iPhone, and although not very discoverable, it is very memorable (as I use it for getting we&#8217;ll instead of well). This seems like a solution for a more technically savvy user though as I also use it in things like textExpander. Although I feel that this should be the demographic ubiquity targets, if these features will eventually be added to the awesome bar then I feel that Aza&#8217;s recommendation fits a more general audience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerv</title>
		<link>http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3940</link>
		<dc:creator>Gerv</dc:creator>
		<pubDate>Fri, 13 Feb 2009 17:42:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=354#comment-3940</guid>
		<description>Here&#039;s an idea: embrace the txt speak. It&#039;s like the &quot;thisselection&quot; idea but much less clunky. Make it so the vowelless form of the word triggers the substitution. So &quot;ths&quot; is this, substituted, &quot;t&quot; is &quot;it&quot;, &quot;hm&quot; is him and so on. I think people would get the hang of this fairly quickly, and the rule for converting a pronoun to the substitutable form is simple.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s an idea: embrace the txt speak. It&#8217;s like the &#8220;thisselection&#8221; idea but much less clunky. Make it so the vowelless form of the word triggers the substitution. So &#8220;ths&#8221; is this, substituted, &#8220;t&#8221; is &#8220;it&#8221;, &#8220;hm&#8221; is him and so on. I think people would get the hang of this fairly quickly, and the rule for converting a pronoun to the substitutable form is simple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Cannon</title>
		<link>http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3938</link>
		<dc:creator>Kevin Cannon</dc:creator>
		<pubDate>Fri, 13 Feb 2009 10:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=354#comment-3938</guid>
		<description>Why not simply use quotation marks if there is ambiguity. That&#039;s a fairly common method of solving this problem. So, highlight Ubuiquities keywords in a different way to show they&#039;re &#039;special&#039; - or do best guesses if possible, but ultimately let the user over ride it themselves. It&#039;s something that is easily learned.

email &quot;I think this website alot&quot; to john

That&#039;s quite a simple solution.
Also, natural language interpretation is always going to be difficult, so maybe you need to set a grammar for Ubiquity, that keywords aren&#039;t allowed in the middle of random strings. You can add rules to the language to be used. If someone tries one form and it doesn&#039;t work, then they&#039;re smart enough to rephrase it.</description>
		<content:encoded><![CDATA[<p>Why not simply use quotation marks if there is ambiguity. That&#8217;s a fairly common method of solving this problem. So, highlight Ubuiquities keywords in a different way to show they&#8217;re &#8217;special&#8217; &#8211; or do best guesses if possible, but ultimately let the user over ride it themselves. It&#8217;s something that is easily learned.</p>
<p>email &#8220;I think this website alot&#8221; to john</p>
<p>That&#8217;s quite a simple solution.<br />
Also, natural language interpretation is always going to be difficult, so maybe you need to set a grammar for Ubiquity, that keywords aren&#8217;t allowed in the middle of random strings. You can add rules to the language to be used. If someone tries one form and it doesn&#8217;t work, then they&#8217;re smart enough to rephrase it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Hasler</title>
		<link>http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3936</link>
		<dc:creator>Sam Hasler</dc:creator>
		<pubDate>Thu, 12 Feb 2009 15:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=354#comment-3936</guid>
		<description>Looking at this mockup: http://www.flickr.com/photos/azaraskin/3272673947/

that makes the modifiers discoverable, but what about having to press the right arrow key to see the suggestions, that&#039;s not discoverable. Why not show an image of the right arrow key above the first modifier, then the more the user uses the right arrow key the fainter it gets until it doesn&#039;t appear at all.

Could the right arrow key be pressed again to select the &quot;from&quot; modifier instead of &quot;to&quot;, swapping them over? What happens if there are three or more modifiers, how do you know which will be brought across next? what if you select past the modifier you want, can you select the previous one? I&#039;m assuming the left-arrow key would just move the cursor, maybe ctrl+z, or would they cycle so you have to go full circle. 

How about if the cursor is at the far right but not after whitespace pressing the right-arrow selects the first modifier that the preceeding word fragment matches the start of. So if you your example the user typed &quot;f&quot; and hit the right arrow it would bring from across. As the user is type if the start of a modifier matches the word fragment before the cursor that word fragment could be highlighted in bold so the user knows which modifier pressing the right-arrow will select.</description>
		<content:encoded><![CDATA[<p>Looking at this mockup: <a href="http://www.flickr.com/photos/azaraskin/3272673947/" rel="nofollow">http://www.flickr.com/photos/azaraskin/3272673947/</a></p>
<p>that makes the modifiers discoverable, but what about having to press the right arrow key to see the suggestions, that&#8217;s not discoverable. Why not show an image of the right arrow key above the first modifier, then the more the user uses the right arrow key the fainter it gets until it doesn&#8217;t appear at all.</p>
<p>Could the right arrow key be pressed again to select the &#8220;from&#8221; modifier instead of &#8220;to&#8221;, swapping them over? What happens if there are three or more modifiers, how do you know which will be brought across next? what if you select past the modifier you want, can you select the previous one? I&#8217;m assuming the left-arrow key would just move the cursor, maybe ctrl+z, or would they cycle so you have to go full circle. </p>
<p>How about if the cursor is at the far right but not after whitespace pressing the right-arrow selects the first modifier that the preceeding word fragment matches the start of. So if you your example the user typed &#8220;f&#8221; and hit the right arrow it would bring from across. As the user is type if the start of a modifier matches the word fragment before the cursor that word fragment could be highlighted in bold so the user knows which modifier pressing the right-arrow will select.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Hasler</title>
		<link>http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3935</link>
		<dc:creator>Sam Hasler</dc:creator>
		<pubDate>Thu, 12 Feb 2009 14:51:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=354#comment-3935</guid>
		<description>when it&#039;s possible to press a key to activate some functionallity the interface should show an image of the key. The more the user uses the key the fainter the image gets until it doesn&#039;t appear at all.</description>
		<content:encoded><![CDATA[<p>when it&#8217;s possible to press a key to activate some functionallity the interface should show an image of the key. The more the user uses the key the fainter the image gets until it doesn&#8217;t appear at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3930</link>
		<dc:creator>David</dc:creator>
		<pubDate>Thu, 12 Feb 2009 00:32:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=354#comment-3930</guid>
		<description>Whatever you do, don&#039;t make people take their hands off of home row to make Ubiquity selections. That defeats the whole purpose. (So, obviously, clicking or up-arrow-ing the &#039;this&#039; wouldn&#039;t cut it. Clicking should be an option, of course, but the keyboard equivalent should leave your hands be.)</description>
		<content:encoded><![CDATA[<p>Whatever you do, don&#8217;t make people take their hands off of home row to make Ubiquity selections. That defeats the whole purpose. (So, obviously, clicking or up-arrow-ing the &#8216;this&#8217; wouldn&#8217;t cut it. Clicking should be an option, of course, but the keyboard equivalent should leave your hands be.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Cardin</title>
		<link>http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3929</link>
		<dc:creator>Dan Cardin</dc:creator>
		<pubDate>Thu, 12 Feb 2009 00:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=354#comment-3929</guid>
		<description>I agree with Robby. having more specific nouns makes mroe sense. As i understood it, Ubiquity was to feel natural and flowing. Taking the time to take your fingers away from the typing position isnt very natural, nor would it save time. While having to type the whole thing over again might be slightly annoying or slower i think it would flow well and would give many more meanings to each general keyword. 

As said above this could relate to url, selection, image, etc</description>
		<content:encoded><![CDATA[<p>I agree with Robby. having more specific nouns makes mroe sense. As i understood it, Ubiquity was to feel natural and flowing. Taking the time to take your fingers away from the typing position isnt very natural, nor would it save time. While having to type the whole thing over again might be slightly annoying or slower i think it would flow well and would give many more meanings to each general keyword. </p>
<p>As said above this could relate to url, selection, image, etc</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex.r.</title>
		<link>http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3925</link>
		<dc:creator>alex.r.</dc:creator>
		<pubDate>Wed, 11 Feb 2009 20:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=354#comment-3925</guid>
		<description>A suggestion:

You let the user chose as they type but the default changes as you collect the responses.

It could be done based on the probability of choice given context p(c&#124;magic word, preceding words). 

An HMM could be used to estimate that.

Obviously this would only help when users repeat the same actions. I don&#039;t know if it&#039;s generally the case.</description>
		<content:encoded><![CDATA[<p>A suggestion:</p>
<p>You let the user chose as they type but the default changes as you collect the responses.</p>
<p>It could be done based on the probability of choice given context p(c|magic word, preceding words). </p>
<p>An HMM could be used to estimate that.</p>
<p>Obviously this would only help when users repeat the same actions. I don&#8217;t know if it&#8217;s generally the case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sushu</title>
		<link>http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3924</link>
		<dc:creator>Sushu</dc:creator>
		<pubDate>Wed, 11 Feb 2009 05:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=354#comment-3924</guid>
		<description>The auto-complete is already part of it, no?  Like, the preview section tells me that &quot;this&quot; means whatever I selected.   In any case, I&#039;d like to have it integrated with the existing preview pane, instead of having one down at the bottom and one right by where I&#039;m typing.

Also, I was frustrated by the map command and I was told to take it up with you guys.  ;)  (Basically, I wanted to get directions w/ map, but since there was no directions choice on the preview pane, I tried to go to the Gmaps site from the preview pane, but clicking on the Google logo didn&#039;t work, and I didn&#039;t know I had to hit enter b/c all the rest of the map stuff was clicking.  The randomness of click-based commands and type-y commands is sometimes disorienting!  :(</description>
		<content:encoded><![CDATA[<p>The auto-complete is already part of it, no?  Like, the preview section tells me that &#8220;this&#8221; means whatever I selected.   In any case, I&#8217;d like to have it integrated with the existing preview pane, instead of having one down at the bottom and one right by where I&#8217;m typing.</p>
<p>Also, I was frustrated by the map command and I was told to take it up with you guys.  ;)  (Basically, I wanted to get directions w/ map, but since there was no directions choice on the preview pane, I tried to go to the Gmaps site from the preview pane, but clicking on the Google logo didn&#8217;t work, and I didn&#8217;t know I had to hit enter b/c all the rest of the map stuff was clicking.  The randomness of click-based commands and type-y commands is sometimes disorienting!  :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robby Macdonell</title>
		<link>http://www.azarask.in/blog/post/solving-the-it-problem/comment-page-1/#comment-3922</link>
		<dc:creator>Robby Macdonell</dc:creator>
		<pubDate>Tue, 10 Feb 2009 23:38:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=354#comment-3922</guid>
		<description>Disclaimer: up until I read this post, I had no idea that the magic pronouns even existed in Ubiquity, so this is a noob perspective.

I think the solution you have is an elegant one, with one caveat. The pronouns themselves can mean way too many different things in my mind (regardless of what limitations you impose on the meaning in Ubiquity). I feel like that&#039;s the reason I&#039;ve never used them. (hopefully, I need to go back and check my tweets now to see if something got unintentionally replaced!)

I think about the things that &#039;this&#039; could refer to and what comes to mind are: &#039;this page&#039; (that I&#039;m currently on, I may be interested in the URL or the entire contents of the page), and &#039;this selection&#039; (which may be text or an image, and may or may not be hyperlinked). 

I feel like a two-word solution feels pretty natural.

&quot;Download these links&quot;
&quot;edit this image&quot;
&quot;Bookmark this page&quot;
&quot;email this page to him&quot;

But, that&#039;s two words, and probably has it&#039;s own drawbacks. Another solution would be to say pronouns are too vague and have magic nouns instead. 

&quot;Download links&quot;
&quot;edit image&quot;
&quot;Bookmark url&quot;
&quot;email url to him&quot;

Granted, that language sounds a little stunted, but the meaning is clear from each phrase. &quot;This&quot; would be understood, or could possibly be typed and ignored.

But as for the phone-like predictive text ui you mocked up. It does seem like it would be a pretty natural-feeling interaction, as I sit here and mime it out on my keyboard a few times.</description>
		<content:encoded><![CDATA[<p>Disclaimer: up until I read this post, I had no idea that the magic pronouns even existed in Ubiquity, so this is a noob perspective.</p>
<p>I think the solution you have is an elegant one, with one caveat. The pronouns themselves can mean way too many different things in my mind (regardless of what limitations you impose on the meaning in Ubiquity). I feel like that&#8217;s the reason I&#8217;ve never used them. (hopefully, I need to go back and check my tweets now to see if something got unintentionally replaced!)</p>
<p>I think about the things that &#8216;this&#8217; could refer to and what comes to mind are: &#8216;this page&#8217; (that I&#8217;m currently on, I may be interested in the URL or the entire contents of the page), and &#8216;this selection&#8217; (which may be text or an image, and may or may not be hyperlinked). </p>
<p>I feel like a two-word solution feels pretty natural.</p>
<p>&#8220;Download these links&#8221;<br />
&#8220;edit this image&#8221;<br />
&#8220;Bookmark this page&#8221;<br />
&#8220;email this page to him&#8221;</p>
<p>But, that&#8217;s two words, and probably has it&#8217;s own drawbacks. Another solution would be to say pronouns are too vague and have magic nouns instead. </p>
<p>&#8220;Download links&#8221;<br />
&#8220;edit image&#8221;<br />
&#8220;Bookmark url&#8221;<br />
&#8220;email url to him&#8221;</p>
<p>Granted, that language sounds a little stunted, but the meaning is clear from each phrase. &#8220;This&#8221; would be understood, or could possibly be typed and ignored.</p>
<p>But as for the phone-like predictive text ui you mocked up. It does seem like it would be a pretty natural-feeling interaction, as I sit here and mime it out on my keyboard a few times.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
