<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_06_02_1647213</id>
	<title>Triangular Buttons Make On-Screen Keyboards More Usable</title>
	<author>timothy</author>
	<datestamp>1243962240000</datestamp>
	<htmltext>As someone targeted for perpetual failure by the designers of most keyboards, I'm happy to read
The Register's report that <i>"A British inventor has submitted a patent application for a <a href="http://go.theregister.com/feed/www.reghardware.co.uk/2009/06/02/crocodile\_keyboard/">wacky touchscreen keyboard design</a> which, he claims, could spell the end for accidental key presses."</i></htmltext>
<tokenext>As someone targeted for perpetual failure by the designers of most keyboards , I 'm happy to read The Register 's report that " A British inventor has submitted a patent application for a wacky touchscreen keyboard design which , he claims , could spell the end for accidental key presses .
"</tokentext>
<sentencetext>As someone targeted for perpetual failure by the designers of most keyboards, I'm happy to read
The Register's report that "A British inventor has submitted a patent application for a wacky touchscreen keyboard design which, he claims, could spell the end for accidental key presses.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184857</id>
	<title>With all that space between keys...</title>
	<author>Anonymous</author>
	<datestamp>1243967700000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>With all that space between the keys, there's room for even more buttons!</htmltext>
<tokenext>With all that space between the keys , there 's room for even more buttons !</tokentext>
<sentencetext>With all that space between the keys, there's room for even more buttons!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184833</id>
	<title>Hah!</title>
	<author>beadfulthings</author>
	<datestamp>1243967520000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>They may make commercials about butt-dialing. But on the day after I got my iPhone, I hung up on a customer and dialed the veterinarian's office all without being aware I was doing it--with the side of my face. I therefore invented face-dialing. It took several days to get used to the keyboard, but it took longer to accustom myself to not mashing down on crucial icons while talking. I can use the keyboard efficiently now, but I suspect the learning curve would have been less with the keyboard described in the article. And it's not a mental learning curve. It's a physical skill like typing on a full sized keyboard.I'd also like to see them add a very slight lip around the perimeter of the screen where the silver metal is located. It would be a tactile reminder to keep the damned thing away from my face.</p></htmltext>
<tokenext>They may make commercials about butt-dialing .
But on the day after I got my iPhone , I hung up on a customer and dialed the veterinarian 's office all without being aware I was doing it--with the side of my face .
I therefore invented face-dialing .
It took several days to get used to the keyboard , but it took longer to accustom myself to not mashing down on crucial icons while talking .
I can use the keyboard efficiently now , but I suspect the learning curve would have been less with the keyboard described in the article .
And it 's not a mental learning curve .
It 's a physical skill like typing on a full sized keyboard.I 'd also like to see them add a very slight lip around the perimeter of the screen where the silver metal is located .
It would be a tactile reminder to keep the damned thing away from my face .</tokentext>
<sentencetext>They may make commercials about butt-dialing.
But on the day after I got my iPhone, I hung up on a customer and dialed the veterinarian's office all without being aware I was doing it--with the side of my face.
I therefore invented face-dialing.
It took several days to get used to the keyboard, but it took longer to accustom myself to not mashing down on crucial icons while talking.
I can use the keyboard efficiently now, but I suspect the learning curve would have been less with the keyboard described in the article.
And it's not a mental learning curve.
It's a physical skill like typing on a full sized keyboard.I'd also like to see them add a very slight lip around the perimeter of the screen where the silver metal is located.
It would be a tactile reminder to keep the damned thing away from my face.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28193759</id>
	<title>Why crocodile? Why not Shark?</title>
	<author>pbrooks100</author>
	<datestamp>1244031360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>A shark has multiple rows of teeth just like the picture, and everyone knows anything is better with sharks with friggen' lasers on them!</htmltext>
<tokenext>A shark has multiple rows of teeth just like the picture , and everyone knows anything is better with sharks with friggen ' lasers on them !</tokentext>
<sentencetext>A shark has multiple rows of teeth just like the picture, and everyone knows anything is better with sharks with friggen' lasers on them!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425</id>
	<title>The Best Thing To Do</title>
	<author>sycodon</author>
	<datestamp>1243966020000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>Is to get rid of the damned, usless, pain in the ass keycaps key.</p><p>As for the keyboard itself, seems I've seen that in some si-fi movie.</p></htmltext>
<tokenext>Is to get rid of the damned , usless , pain in the ass keycaps key.As for the keyboard itself , seems I 've seen that in some si-fi movie .</tokentext>
<sentencetext>Is to get rid of the damned, usless, pain in the ass keycaps key.As for the keyboard itself, seems I've seen that in some si-fi movie.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184917</id>
	<title>I tried it</title>
	<author>Anonymous</author>
	<datestamp>1243967880000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>I made the <a href="http://regmedia.co.uk/2009/06/02/crocodile\_keyboard\_iphone\_002.jpg" title="regmedia.co.uk">image</a> [regmedia.co.uk] fit the screen (CTRL + [+]) and, well that was it. It felt no different. It looked no different.

</p><p>Surely it's just a matter of practice when using large on screen keyboards?

</p><p>Aim for the top of the triangle? Why bother outlining the keyboard letters at all?</p></htmltext>
<tokenext>I made the image [ regmedia.co.uk ] fit the screen ( CTRL + [ + ] ) and , well that was it .
It felt no different .
It looked no different .
Surely it 's just a matter of practice when using large on screen keyboards ?
Aim for the top of the triangle ?
Why bother outlining the keyboard letters at all ?</tokentext>
<sentencetext>I made the image [regmedia.co.uk] fit the screen (CTRL + [+]) and, well that was it.
It felt no different.
It looked no different.
Surely it's just a matter of practice when using large on screen keyboards?
Aim for the top of the triangle?
Why bother outlining the keyboard letters at all?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184889</id>
	<title>Maybe we won't need autocorretion?</title>
	<author>Anonymous</author>
	<datestamp>1243967820000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Great.  Now lets get this dang iPhone to stop replacing the words I type.  This always results to unnecessary text messaging where I have to explain myself.  "What?"</p></htmltext>
<tokenext>Great .
Now lets get this dang iPhone to stop replacing the words I type .
This always results to unnecessary text messaging where I have to explain myself .
" What ? "</tokentext>
<sentencetext>Great.
Now lets get this dang iPhone to stop replacing the words I type.
This always results to unnecessary text messaging where I have to explain myself.
"What?"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184565</id>
	<title>Only Apple</title>
	<author>Djupblue</author>
	<datestamp>1243966500000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>0</modscore>
	<htmltext>However, Baker believes that the virtual keyboard's full potential will only be realised if it's integrated into every area of the iPhone that uses a keyboard, such as SMS and email, rather than developed as a standalone application. For this to happen, he requires Apple's aid, something he described as "very difficult to get".

So, for the time being at least, the Crocodile Keyboard for touchscreen phones remains just a dream.</htmltext>
<tokenext>However , Baker believes that the virtual keyboard 's full potential will only be realised if it 's integrated into every area of the iPhone that uses a keyboard , such as SMS and email , rather than developed as a standalone application .
For this to happen , he requires Apple 's aid , something he described as " very difficult to get " .
So , for the time being at least , the Crocodile Keyboard for touchscreen phones remains just a dream .</tokentext>
<sentencetext>However, Baker believes that the virtual keyboard's full potential will only be realised if it's integrated into every area of the iPhone that uses a keyboard, such as SMS and email, rather than developed as a standalone application.
For this to happen, he requires Apple's aid, something he described as "very difficult to get".
So, for the time being at least, the Crocodile Keyboard for touchscreen phones remains just a dream.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186365</id>
	<title>Re:Apple is, or should be, FAR ahead of this...</title>
	<author>goodmanj</author>
	<datestamp>1243974300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Keep swearing!  The phone will eventually figure out you're a pottymouth and adapt its autocorrect dictionary.</p></htmltext>
<tokenext>Keep swearing !
The phone will eventually figure out you 're a pottymouth and adapt its autocorrect dictionary .</tokentext>
<sentencetext>Keep swearing!
The phone will eventually figure out you're a pottymouth and adapt its autocorrect dictionary.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185051</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184707</id>
	<title>Re:The Best Thing To Do</title>
	<author>sycodon</author>
	<datestamp>1243967040000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext><p>I remember reading an interview many years ago with Ray Bradbury or one of the other leading authors of the time. In it he described the most irritating things that interviewers do.</p><p>First, is to ask where they get their ideas from.</p><p>The second, was to call their genre of books "SiFi". It's called "Science Fiction", he said.</p></htmltext>
<tokenext>I remember reading an interview many years ago with Ray Bradbury or one of the other leading authors of the time .
In it he described the most irritating things that interviewers do.First , is to ask where they get their ideas from.The second , was to call their genre of books " SiFi " .
It 's called " Science Fiction " , he said .</tokentext>
<sentencetext>I remember reading an interview many years ago with Ray Bradbury or one of the other leading authors of the time.
In it he described the most irritating things that interviewers do.First, is to ask where they get their ideas from.The second, was to call their genre of books "SiFi".
It's called "Science Fiction", he said.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184535</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28187995</id>
	<title>Considering that the trend...</title>
	<author>macraig</author>
	<datestamp>1243937640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>... has pretty consistently been toward smaller and smaller keyboards, this is probably doomed to failure even though it's a virtual one.  It's a rather obvious observation, in any case, that adding extra "whitespace" around keys would reduce the chance of mis-strikes.</p><p>I also don't grok the whining about his not being able to fully integrate it into the iPhone.  I have several third-party virtual keyboards for my Pocket PC (Windows Mobile), and I can select and use whichever one I want, and do so across all applications, as well as be able to switch between them at will.  You mean the same capability doesn't exist in the iPhone?</p></htmltext>
<tokenext>... has pretty consistently been toward smaller and smaller keyboards , this is probably doomed to failure even though it 's a virtual one .
It 's a rather obvious observation , in any case , that adding extra " whitespace " around keys would reduce the chance of mis-strikes.I also do n't grok the whining about his not being able to fully integrate it into the iPhone .
I have several third-party virtual keyboards for my Pocket PC ( Windows Mobile ) , and I can select and use whichever one I want , and do so across all applications , as well as be able to switch between them at will .
You mean the same capability does n't exist in the iPhone ?</tokentext>
<sentencetext>... has pretty consistently been toward smaller and smaller keyboards, this is probably doomed to failure even though it's a virtual one.
It's a rather obvious observation, in any case, that adding extra "whitespace" around keys would reduce the chance of mis-strikes.I also don't grok the whining about his not being able to fully integrate it into the iPhone.
I have several third-party virtual keyboards for my Pocket PC (Windows Mobile), and I can select and use whichever one I want, and do so across all applications, as well as be able to switch between them at will.
You mean the same capability doesn't exist in the iPhone?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569</id>
	<title>Re:The Best Thing To Do</title>
	<author>sakdoctor</author>
	<datestamp>1243966500000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>The Logitech wave keyboard has a little "moat" around Capslock and Numlock keys, making them far less easy to accidentally press.<br>You can also disable those keys in software, which I did straight away.</p><p>Best keyboard I've ever owned.</p></htmltext>
<tokenext>The Logitech wave keyboard has a little " moat " around Capslock and Numlock keys , making them far less easy to accidentally press.You can also disable those keys in software , which I did straight away.Best keyboard I 've ever owned .</tokentext>
<sentencetext>The Logitech wave keyboard has a little "moat" around Capslock and Numlock keys, making them far less easy to accidentally press.You can also disable those keys in software, which I did straight away.Best keyboard I've ever owned.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621</id>
	<title>Re:The Best Thing To Do</title>
	<author>Anonymous</author>
	<datestamp>1243966740000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>As someone who sues it, I would say do NOT remove the caps lock. kthxby.<br>In fact, serious data entry users use it regularly.</p></htmltext>
<tokenext>As someone who sues it , I would say do NOT remove the caps lock .
kthxby.In fact , serious data entry users use it regularly .</tokentext>
<sentencetext>As someone who sues it, I would say do NOT remove the caps lock.
kthxby.In fact, serious data entry users use it regularly.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184855</id>
	<title>Re:The Best Thing To Do</title>
	<author>Anonymous</author>
	<datestamp>1243967640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>NO, I VOTE not TO GET RID OF THE CAPSLOCK KEY
</p><p>
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</p></htmltext>
<tokenext>NO , I VOTE not TO GET RID OF THE CAPSLOCK KEY Lorem ipsum dolor sit amet , consectetur adipisicing elit , sed do eiusmod tempor incididunt ut labore et dolore magna aliqua .
Ut enim ad minim veniam , quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat .
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur .
Excepteur sint occaecat cupidatat non proident , sunt in culpa qui officia deserunt mollit anim id est laborum .</tokentext>
<sentencetext>NO, I VOTE not TO GET RID OF THE CAPSLOCK KEY

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185695</id>
	<title>It may not be, it isn't approved</title>
	<author>Kupfernigk</author>
	<datestamp>1243971300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It's only an application, you have plenty of time to object.</htmltext>
<tokenext>It 's only an application , you have plenty of time to object .</tokentext>
<sentencetext>It's only an application, you have plenty of time to object.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185305</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185385</id>
	<title>Re:If triangles are good...</title>
	<author>bgray54</author>
	<datestamp>1243969920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Ooh, and then we could rotate those diamonds 45 degrees and have squares!</htmltext>
<tokenext>Ooh , and then we could rotate those diamonds 45 degrees and have squares !</tokentext>
<sentencetext>Ooh, and then we could rotate those diamonds 45 degrees and have squares!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185685</id>
	<title>I stil won't buy a device without real keys.</title>
	<author>Hurricane78</author>
	<datestamp>1243971240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I hope someone comes up with a deformable screen, that allows tactile responses. I hate looking at a keyboard while typing.</p><p>Oh, and it took me five seconds, to come up with a better design. I noticed that the space around the keys is, so you do not accidentially hit other keys. Well, wanna know what else prevents that? <em>Bigger keys!</em> ^^</p><p>So essentially, they are just making the keys bigger, but not all of it touchable. I would make the triangles point upwards, and fill a third of the empty spaces too. But still only react when touching the inner, downwards pointing triangle. And enforce minimum sizes for both triangle areas, in the patent license.</p><p>Because with those keys, companies will just try to fit more keys onto the screen, until you can't hit them properly again. Which was the source of the problem in the first place.<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>I hope someone comes up with a deformable screen , that allows tactile responses .
I hate looking at a keyboard while typing.Oh , and it took me five seconds , to come up with a better design .
I noticed that the space around the keys is , so you do not accidentially hit other keys .
Well , wan na know what else prevents that ?
Bigger keys !
^ ^ So essentially , they are just making the keys bigger , but not all of it touchable .
I would make the triangles point upwards , and fill a third of the empty spaces too .
But still only react when touching the inner , downwards pointing triangle .
And enforce minimum sizes for both triangle areas , in the patent license.Because with those keys , companies will just try to fit more keys onto the screen , until you ca n't hit them properly again .
Which was the source of the problem in the first place .
: )</tokentext>
<sentencetext>I hope someone comes up with a deformable screen, that allows tactile responses.
I hate looking at a keyboard while typing.Oh, and it took me five seconds, to come up with a better design.
I noticed that the space around the keys is, so you do not accidentially hit other keys.
Well, wanna know what else prevents that?
Bigger keys!
^^So essentially, they are just making the keys bigger, but not all of it touchable.
I would make the triangles point upwards, and fill a third of the empty spaces too.
But still only react when touching the inner, downwards pointing triangle.
And enforce minimum sizes for both triangle areas, in the patent license.Because with those keys, companies will just try to fit more keys onto the screen, until you can't hit them properly again.
Which was the source of the problem in the first place.
:)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186515</id>
	<title>Re:Missing the points</title>
	<author>Anonymous</author>
	<datestamp>1243974840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>0.  The phone figures out where the *center* of your finger is, something a physical keyboard can't do.  And any mistakes get autocorrected gracefully.</p><p>1.  As you type, the letters pop up above your finger so you can see it.  And you can slide around to adjust if you're slightly off.</p><p>2.  Yes.  You will more mistakes with a non-tactile keyboard, but they will be autocorrected.</p><p>Try an iPhone for a bit.  Or watch <a href="http://www.apple.com/iphone/features/keyboard.html" title="apple.com">this video</a> [apple.com].  What the iPhone lacks in tactile response compared to a Blackberry, it more than makes up for in brains.</p><p>And watch the foreign-language tricks in the latter part of that video.  Can't do *that* with a Blackberry!</p></htmltext>
<tokenext>0 .
The phone figures out where the * center * of your finger is , something a physical keyboard ca n't do .
And any mistakes get autocorrected gracefully.1 .
As you type , the letters pop up above your finger so you can see it .
And you can slide around to adjust if you 're slightly off.2 .
Yes. You will more mistakes with a non-tactile keyboard , but they will be autocorrected.Try an iPhone for a bit .
Or watch this video [ apple.com ] .
What the iPhone lacks in tactile response compared to a Blackberry , it more than makes up for in brains.And watch the foreign-language tricks in the latter part of that video .
Ca n't do * that * with a Blackberry !</tokentext>
<sentencetext>0.
The phone figures out where the *center* of your finger is, something a physical keyboard can't do.
And any mistakes get autocorrected gracefully.1.
As you type, the letters pop up above your finger so you can see it.
And you can slide around to adjust if you're slightly off.2.
Yes.  You will more mistakes with a non-tactile keyboard, but they will be autocorrected.Try an iPhone for a bit.
Or watch this video [apple.com].
What the iPhone lacks in tactile response compared to a Blackberry, it more than makes up for in brains.And watch the foreign-language tricks in the latter part of that video.
Can't do *that* with a Blackberry!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185181</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185399</id>
	<title>Dasher!</title>
	<author>danuker</author>
	<datestamp>1243969980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p> Triangular Buttons Make On-Screen Keyboards More Usable</p> </div><p>Dasher Makes On-Screen Input More Usable</p></div>
	</htmltext>
<tokenext>Triangular Buttons Make On-Screen Keyboards More Usable Dasher Makes On-Screen Input More Usable</tokentext>
<sentencetext> Triangular Buttons Make On-Screen Keyboards More Usable Dasher Makes On-Screen Input More Usable
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186107</id>
	<title>Re:Klingon Keyboard? And other aliens as well</title>
	<author>davidsyes</author>
	<datestamp>1243973040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"Pen Pals"?<br><a href="http://en.wikipedia.org/wiki/Pen\_Pals\_(Star\_Trek:\_The\_Next\_Generation)" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Pen\_Pals\_(Star\_Trek:\_The\_Next\_Generation)</a> [wikipedia.org]</p><p>I'm recalling an episode or two in Trek where various alien control consoles had triangular keyboards. How anyone can get a patent will be interesting...</p><p>But, even if not (episode, or patent interests...), here are some Trek and other Sci-Fi alien writing fonts...</p><p><a href="http://www.geocities.com/TimesSquare/4965/tfont.html" title="geocities.com" rel="nofollow">http://www.geocities.com/TimesSquare/4965/tfont.html</a> [geocities.com]</p><p><a href="http://www.geocities.com/TimesSquare/4965/tfont.html#kazonf" title="geocities.com" rel="nofollow">http://www.geocities.com/TimesSquare/4965/tfont.html#kazonf</a> [geocities.com]</p></htmltext>
<tokenext>" Pen Pals " ? http : //en.wikipedia.org/wiki/Pen \ _Pals \ _ ( Star \ _Trek : \ _The \ _Next \ _Generation ) [ wikipedia.org ] I 'm recalling an episode or two in Trek where various alien control consoles had triangular keyboards .
How anyone can get a patent will be interesting...But , even if not ( episode , or patent interests... ) , here are some Trek and other Sci-Fi alien writing fonts...http : //www.geocities.com/TimesSquare/4965/tfont.html [ geocities.com ] http : //www.geocities.com/TimesSquare/4965/tfont.html # kazonf [ geocities.com ]</tokentext>
<sentencetext>"Pen Pals"?http://en.wikipedia.org/wiki/Pen\_Pals\_(Star\_Trek:\_The\_Next\_Generation) [wikipedia.org]I'm recalling an episode or two in Trek where various alien control consoles had triangular keyboards.
How anyone can get a patent will be interesting...But, even if not (episode, or patent interests...), here are some Trek and other Sci-Fi alien writing fonts...http://www.geocities.com/TimesSquare/4965/tfont.html [geocities.com]http://www.geocities.com/TimesSquare/4965/tfont.html#kazonf [geocities.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185165</id>
	<title>Re:The Best Thing To Do</title>
	<author>commodoresloat</author>
	<datestamp>1243968840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"You" don't.  That's what Apple's legal department is for.  Believe me, if this keyboard outshines the iPhone keyboard, they'll find a way<nobr> <wbr></nobr>;)</p></htmltext>
<tokenext>" You " do n't .
That 's what Apple 's legal department is for .
Believe me , if this keyboard outshines the iPhone keyboard , they 'll find a way ; )</tokentext>
<sentencetext>"You" don't.
That's what Apple's legal department is for.
Believe me, if this keyboard outshines the iPhone keyboard, they'll find a way ;)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184755</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28190271</id>
	<title>Re:Klingon Keyboard?</title>
	<author>neonsignal</author>
	<datestamp>1243950000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>
You need a fair bit of dead space when you are using your fists to type with.
</p><p>
<i>cha yIbaH qara'DI'!</i></p></htmltext>
<tokenext>You need a fair bit of dead space when you are using your fists to type with .
cha yIbaH qara'DI ' !</tokentext>
<sentencetext>
You need a fair bit of dead space when you are using your fists to type with.
cha yIbaH qara'DI'!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186241</id>
	<title>Re:Apple is, or should be, FAR ahead of this...</title>
	<author>ByteSlicer</author>
	<datestamp>1243973700000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>Just don't try high-intensity vi work</p></div></blockquote><p>
No problemo. I'll just use emacs then.</p></div>
	</htmltext>
<tokenext>Just do n't try high-intensity vi work No problemo .
I 'll just use emacs then .</tokentext>
<sentencetext>Just don't try high-intensity vi work
No problemo.
I'll just use emacs then.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185119</id>
	<title>Re:The Best Thing To Do</title>
	<author>Anonymous</author>
	<datestamp>1243968660000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>Serious data entry?</p><p>You'll be hearing from the clown school of administrative assistants for your discriminatory language .</p></htmltext>
<tokenext>Serious data entry ? You 'll be hearing from the clown school of administrative assistants for your discriminatory language .</tokentext>
<sentencetext>Serious data entry?You'll be hearing from the clown school of administrative assistants for your discriminatory language .</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185465</id>
	<title>Re:Hah!</title>
	<author>aaarrrgggh</author>
	<datestamp>1243970220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I think that was fixed in the first OS update; the proximity sensor by the earpiece de-activates the touchscreen...</p></htmltext>
<tokenext>I think that was fixed in the first OS update ; the proximity sensor by the earpiece de-activates the touchscreen.. .</tokentext>
<sentencetext>I think that was fixed in the first OS update; the proximity sensor by the earpiece de-activates the touchscreen...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184833</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563</id>
	<title>Apple is, or should be, FAR ahead of this...</title>
	<author>jeffb (2.718)</author>
	<datestamp>1243966500000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>...based on the IP they acquired from <a href="http://www.fingerworks.com/faq.html#multi" title="fingerworks.com">FingerWorks</a> [fingerworks.com].  You can do really sophisticated error-correction if you're getting not only a stream of characters, but the exact location of the press, contact area, dwell time, and possibly more.  So, with a virtual multi-touch keyboard, you can say "Okay, that looked like an R, but the contact was actually most of the way over toward E, and the previous two letters were T-H, so I'm going to go ahead and make it an E."</p><p>I know it'll rankle the manual-transmission crowd, but I've been using a FingerWorks keyboard for years, and most of the time, it's absolutely spooky how well the autocorrect works.  (Just don't try high-intensity <tt>vi</tt> work.)</p></htmltext>
<tokenext>...based on the IP they acquired from FingerWorks [ fingerworks.com ] .
You can do really sophisticated error-correction if you 're getting not only a stream of characters , but the exact location of the press , contact area , dwell time , and possibly more .
So , with a virtual multi-touch keyboard , you can say " Okay , that looked like an R , but the contact was actually most of the way over toward E , and the previous two letters were T-H , so I 'm going to go ahead and make it an E. " I know it 'll rankle the manual-transmission crowd , but I 've been using a FingerWorks keyboard for years , and most of the time , it 's absolutely spooky how well the autocorrect works .
( Just do n't try high-intensity vi work .
)</tokentext>
<sentencetext>...based on the IP they acquired from FingerWorks [fingerworks.com].
You can do really sophisticated error-correction if you're getting not only a stream of characters, but the exact location of the press, contact area, dwell time, and possibly more.
So, with a virtual multi-touch keyboard, you can say "Okay, that looked like an R, but the contact was actually most of the way over toward E, and the previous two letters were T-H, so I'm going to go ahead and make it an E."I know it'll rankle the manual-transmission crowd, but I've been using a FingerWorks keyboard for years, and most of the time, it's absolutely spooky how well the autocorrect works.
(Just don't try high-intensity vi work.
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184773</id>
	<title>Re:The Best Thing To Do</title>
	<author>princessproton</author>
	<datestamp>1243967220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Chevron Seven, locked.</p></htmltext>
<tokenext>Chevron Seven , locked .</tokentext>
<sentencetext>Chevron Seven, locked.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186821</id>
	<title>Re:The Best Thing To Do</title>
	<author>wastedlife</author>
	<datestamp>1243976160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It looks like the keys are pretty much the same size as what the iphone normally has, but with more dead space between the keys due to using the triangle shaped keys. Your fingers are round, not square, so if you have fat fingers it is easy to hit keys you didn't plan on by accident with the normal keyboard. With this layout, it is a bit more difficult to hit the wrong keys. Circular keys might work the best for this, but then the software needs to calculate round input areas, likely creating significantly higher performance costs. It does double the screen real-estate consumed by dead space, but unless you are typing with a stylus it shouldn't matter on a keyboard that is only out when you need it.</p></htmltext>
<tokenext>It looks like the keys are pretty much the same size as what the iphone normally has , but with more dead space between the keys due to using the triangle shaped keys .
Your fingers are round , not square , so if you have fat fingers it is easy to hit keys you did n't plan on by accident with the normal keyboard .
With this layout , it is a bit more difficult to hit the wrong keys .
Circular keys might work the best for this , but then the software needs to calculate round input areas , likely creating significantly higher performance costs .
It does double the screen real-estate consumed by dead space , but unless you are typing with a stylus it should n't matter on a keyboard that is only out when you need it .</tokentext>
<sentencetext>It looks like the keys are pretty much the same size as what the iphone normally has, but with more dead space between the keys due to using the triangle shaped keys.
Your fingers are round, not square, so if you have fat fingers it is easy to hit keys you didn't plan on by accident with the normal keyboard.
With this layout, it is a bit more difficult to hit the wrong keys.
Circular keys might work the best for this, but then the software needs to calculate round input areas, likely creating significantly higher performance costs.
It does double the screen real-estate consumed by dead space, but unless you are typing with a stylus it shouldn't matter on a keyboard that is only out when you need it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188313</id>
	<title>The secret is in the label position</title>
	<author>wiredlogic</author>
	<datestamp>1243939140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The one thing I consistently see wrong with touch interfaces is that they are all implemented as if they were a conventional GUI to be used with a mouse cursor. Unlike a tiny mouse cursor, when you are pressing a non-tactile screen with a finger you can't see or feel what it is your finger is pressing on. The only time I have seen this accounted for is with the touch interfaces for the more recent Tektronix oscilloscopes. The buttons are purposely kept large and their labels are kept at the top edge rather than the center so that you can read the text while you have your finger in the way.</p><p>Another peeve for lefty's in particular is right side scrollbars. These suck when you want to scroll with your left hand and end up blocking what it is you're trying to scroll through. It's unfortunate that Palm never got this right (there were hacks to fix it up to OS3) and no other PDA manufacturer has gotten clued into the need for configurable vertical scrollbar positioning.</p></htmltext>
<tokenext>The one thing I consistently see wrong with touch interfaces is that they are all implemented as if they were a conventional GUI to be used with a mouse cursor .
Unlike a tiny mouse cursor , when you are pressing a non-tactile screen with a finger you ca n't see or feel what it is your finger is pressing on .
The only time I have seen this accounted for is with the touch interfaces for the more recent Tektronix oscilloscopes .
The buttons are purposely kept large and their labels are kept at the top edge rather than the center so that you can read the text while you have your finger in the way.Another peeve for lefty 's in particular is right side scrollbars .
These suck when you want to scroll with your left hand and end up blocking what it is you 're trying to scroll through .
It 's unfortunate that Palm never got this right ( there were hacks to fix it up to OS3 ) and no other PDA manufacturer has gotten clued into the need for configurable vertical scrollbar positioning .</tokentext>
<sentencetext>The one thing I consistently see wrong with touch interfaces is that they are all implemented as if they were a conventional GUI to be used with a mouse cursor.
Unlike a tiny mouse cursor, when you are pressing a non-tactile screen with a finger you can't see or feel what it is your finger is pressing on.
The only time I have seen this accounted for is with the touch interfaces for the more recent Tektronix oscilloscopes.
The buttons are purposely kept large and their labels are kept at the top edge rather than the center so that you can read the text while you have your finger in the way.Another peeve for lefty's in particular is right side scrollbars.
These suck when you want to scroll with your left hand and end up blocking what it is you're trying to scroll through.
It's unfortunate that Palm never got this right (there were hacks to fix it up to OS3) and no other PDA manufacturer has gotten clued into the need for configurable vertical scrollbar positioning.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186579</id>
	<title>Re:Training to make unaware mistakes?</title>
	<author>jeffb (2.718)</author>
	<datestamp>1243975080000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>Does using such an auto-correcting keyboard make it harder to type correctly when you move to a "normal" keyboard?  Something bothers me about devices that train me to make more unaware mistakes.</p></div><p>A little.  But it's completely overwhelmed by the rich tactile feedback that you get from a physical keyboard.  Without that tactile feedback, even the recovered-from-alien-spacecraft-level intelligence in the FingerWorks TouchStream keyboard only gets you up to about half the typing speed you see on a conventional keyboard; that, and the $300-400 price tag, made it a commercial failure.</p><p>But I'm much happier typing half as fast and having zero wrist pain.  (No reaching for the mouse or modifier keys; they're both gestures, and don't even require you to move from the home position.)</p><p>When I do go back to a conventional keyboard, I sometimes make a few autocorrect-worthy mistakes in the first few minutes, but then I shift back into non-zero-force mode and they go away.  My speed and accuracy on a conventional keyboard, while it's always been substandard, hasn't dropped since I've been using the TouchStream.</p></div>
	</htmltext>
<tokenext>Does using such an auto-correcting keyboard make it harder to type correctly when you move to a " normal " keyboard ?
Something bothers me about devices that train me to make more unaware mistakes.A little .
But it 's completely overwhelmed by the rich tactile feedback that you get from a physical keyboard .
Without that tactile feedback , even the recovered-from-alien-spacecraft-level intelligence in the FingerWorks TouchStream keyboard only gets you up to about half the typing speed you see on a conventional keyboard ; that , and the $ 300-400 price tag , made it a commercial failure.But I 'm much happier typing half as fast and having zero wrist pain .
( No reaching for the mouse or modifier keys ; they 're both gestures , and do n't even require you to move from the home position .
) When I do go back to a conventional keyboard , I sometimes make a few autocorrect-worthy mistakes in the first few minutes , but then I shift back into non-zero-force mode and they go away .
My speed and accuracy on a conventional keyboard , while it 's always been substandard , has n't dropped since I 've been using the TouchStream .</tokentext>
<sentencetext>Does using such an auto-correcting keyboard make it harder to type correctly when you move to a "normal" keyboard?
Something bothers me about devices that train me to make more unaware mistakes.A little.
But it's completely overwhelmed by the rich tactile feedback that you get from a physical keyboard.
Without that tactile feedback, even the recovered-from-alien-spacecraft-level intelligence in the FingerWorks TouchStream keyboard only gets you up to about half the typing speed you see on a conventional keyboard; that, and the $300-400 price tag, made it a commercial failure.But I'm much happier typing half as fast and having zero wrist pain.
(No reaching for the mouse or modifier keys; they're both gestures, and don't even require you to move from the home position.
)When I do go back to a conventional keyboard, I sometimes make a few autocorrect-worthy mistakes in the first few minutes, but then I shift back into non-zero-force mode and they go away.
My speed and accuracy on a conventional keyboard, while it's always been substandard, hasn't dropped since I've been using the TouchStream.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185457</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188723</id>
	<title>Re:Missing the points</title>
	<author>zippthorne</author>
	<datestamp>1243940880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>So, basically, what you're saying is that people who have tiny-key keyboards will be prejudiced against soft-keyboards until they try one, at which point they'll either shut up about it or continue to bitch while secretly pining for a soft keyboard in the future?</p><p>Because let me tell you, my use experience with tiny keyboards goes back to the <em>original</em> wizard, and even at that size, they were stupidly small.  Palm was a significant improvement that the market clearly favored until they forgot about moore's law and kept trying to sell $500 organizers.</p><p>Soft keys are superior in every way, not the least because instead of dividing your device's face, you divide its time.  You get more screen space for everything, and a bigger keyboard when you need one.  Now, if apple would just make a multitouch version of graffiti (i.e. one that wasn't so awkward), we'd have something to debate...</p></htmltext>
<tokenext>So , basically , what you 're saying is that people who have tiny-key keyboards will be prejudiced against soft-keyboards until they try one , at which point they 'll either shut up about it or continue to bitch while secretly pining for a soft keyboard in the future ? Because let me tell you , my use experience with tiny keyboards goes back to the original wizard , and even at that size , they were stupidly small .
Palm was a significant improvement that the market clearly favored until they forgot about moore 's law and kept trying to sell $ 500 organizers.Soft keys are superior in every way , not the least because instead of dividing your device 's face , you divide its time .
You get more screen space for everything , and a bigger keyboard when you need one .
Now , if apple would just make a multitouch version of graffiti ( i.e .
one that was n't so awkward ) , we 'd have something to debate.. .</tokentext>
<sentencetext>So, basically, what you're saying is that people who have tiny-key keyboards will be prejudiced against soft-keyboards until they try one, at which point they'll either shut up about it or continue to bitch while secretly pining for a soft keyboard in the future?Because let me tell you, my use experience with tiny keyboards goes back to the original wizard, and even at that size, they were stupidly small.
Palm was a significant improvement that the market clearly favored until they forgot about moore's law and kept trying to sell $500 organizers.Soft keys are superior in every way, not the least because instead of dividing your device's face, you divide its time.
You get more screen space for everything, and a bigger keyboard when you need one.
Now, if apple would just make a multitouch version of graffiti (i.e.
one that wasn't so awkward), we'd have something to debate...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185181</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28192669</id>
	<title>Re:The Best Thing To Do</title>
	<author>supernova\_hq</author>
	<datestamp>1244060220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Don't think of it as making bigger buttons, instead think of it as shaving the bottom corners off of them. You finger still easily hits the middle or bottom of the key, but you no longer accidentally hit the one beside it at the same time!
<br> <br>
In fact, come to think if it, it actually is a pretty ingenious design idea!</htmltext>
<tokenext>Do n't think of it as making bigger buttons , instead think of it as shaving the bottom corners off of them .
You finger still easily hits the middle or bottom of the key , but you no longer accidentally hit the one beside it at the same time !
In fact , come to think if it , it actually is a pretty ingenious design idea !</tokentext>
<sentencetext>Don't think of it as making bigger buttons, instead think of it as shaving the bottom corners off of them.
You finger still easily hits the middle or bottom of the key, but you no longer accidentally hit the one beside it at the same time!
In fact, come to think if it, it actually is a pretty ingenious design idea!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186681</id>
	<title>Re:The Best Thing To Do</title>
	<author>Thinboy00</author>
	<datestamp>1243975500000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p><div class="quote"><p>How do you shout without a caps lock key?</p></div><p> <a href="http://bash.org/?835030" title="bash.org">Like this</a> [bash.org].</p></div>
	</htmltext>
<tokenext>How do you shout without a caps lock key ?
Like this [ bash.org ] .</tokentext>
<sentencetext>How do you shout without a caps lock key?
Like this [bash.org].
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185207</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185301</id>
	<title>Re:The Best Thing To Do</title>
	<author>PitaBred</author>
	<datestamp>1243969620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>And if you aren't a serious data entry user and usually type up emails and documents, it just gets in the way. Did it ever occur to you that other people use computers differently than you do? I disable capslock on every keyboard I own (and my business machine) because that's what's most useful to me. Especially on a virtual keyboard for a mobile device... there's almost no case where CapsLock would be a good idea.</htmltext>
<tokenext>And if you are n't a serious data entry user and usually type up emails and documents , it just gets in the way .
Did it ever occur to you that other people use computers differently than you do ?
I disable capslock on every keyboard I own ( and my business machine ) because that 's what 's most useful to me .
Especially on a virtual keyboard for a mobile device... there 's almost no case where CapsLock would be a good idea .</tokentext>
<sentencetext>And if you aren't a serious data entry user and usually type up emails and documents, it just gets in the way.
Did it ever occur to you that other people use computers differently than you do?
I disable capslock on every keyboard I own (and my business machine) because that's what's most useful to me.
Especially on a virtual keyboard for a mobile device... there's almost no case where CapsLock would be a good idea.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28190081</id>
	<title>Re:The Best Thing To Do</title>
	<author>Anonymous</author>
	<datestamp>1243948620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>How is this insightful? The "screenshot" is proof of concept only. There's no reason why this can't be done with the same size virtual keyboard that is already on smartphones.</p></htmltext>
<tokenext>How is this insightful ?
The " screenshot " is proof of concept only .
There 's no reason why this ca n't be done with the same size virtual keyboard that is already on smartphones .</tokentext>
<sentencetext>How is this insightful?
The "screenshot" is proof of concept only.
There's no reason why this can't be done with the same size virtual keyboard that is already on smartphones.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28204877</id>
	<title>A Better and "Patentable" Keyboard?</title>
	<author>hutsell</author>
	<datestamp>1244041620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Is this idea better than a design -- and -- new and useful (for regular keyboards)? Keep the raised squares and the angled edge on all four sides without printing the characters on the top of the key. Then, using an application to reprogram the position of the characters into any sequence the typist desires, the mechanical redesign would have the characters appear in a electronic display on the bottom angled edge (or the pad or lower half, etc., and viewable by the typist), perhaps being on a small screen (lcd or something better?) and capable of being "lit up".

So, for example, you may want to reposition the alphabet (based on your language) to be left-to-right or right-to-left and top-to-bottom or bottom-to-top; or the vowels in one location and the consonants in another; or, perhaps they could be positioned by letter usage, say from highest to lowest (in English, it's probably e,t,a,i,o,n,); or a trained traditionalist would leave it alone, since viewing the keyboard is unnecessary. And so on. And of course, those who prefer to hunt-and-peck could either have a field-day or leave it as-is.

After all, the days of using the qwerty format to slow down the typist due to mechanical limitations existing in the original type-writer are over. It remains mostly because of tradition and the hassle of making the change to a better or faster format now allowed by electronic keyboards. This might be a solution that would make it easier to make the change.

So what is missing here possibly making me be: clueless? Has it already been tried and found impractical; or is it on the market at a prohibitive price? However, if not and there is general agreement this does have potential, I realize putting it in the public domain by posting it here on Slashdot has nullfied any chance of making an original claim.</htmltext>
<tokenext>Is this idea better than a design -- and -- new and useful ( for regular keyboards ) ?
Keep the raised squares and the angled edge on all four sides without printing the characters on the top of the key .
Then , using an application to reprogram the position of the characters into any sequence the typist desires , the mechanical redesign would have the characters appear in a electronic display on the bottom angled edge ( or the pad or lower half , etc. , and viewable by the typist ) , perhaps being on a small screen ( lcd or something better ?
) and capable of being " lit up " .
So , for example , you may want to reposition the alphabet ( based on your language ) to be left-to-right or right-to-left and top-to-bottom or bottom-to-top ; or the vowels in one location and the consonants in another ; or , perhaps they could be positioned by letter usage , say from highest to lowest ( in English , it 's probably e,t,a,i,o,n , ) ; or a trained traditionalist would leave it alone , since viewing the keyboard is unnecessary .
And so on .
And of course , those who prefer to hunt-and-peck could either have a field-day or leave it as-is .
After all , the days of using the qwerty format to slow down the typist due to mechanical limitations existing in the original type-writer are over .
It remains mostly because of tradition and the hassle of making the change to a better or faster format now allowed by electronic keyboards .
This might be a solution that would make it easier to make the change .
So what is missing here possibly making me be : clueless ?
Has it already been tried and found impractical ; or is it on the market at a prohibitive price ?
However , if not and there is general agreement this does have potential , I realize putting it in the public domain by posting it here on Slashdot has nullfied any chance of making an original claim .</tokentext>
<sentencetext>Is this idea better than a design -- and -- new and useful (for regular keyboards)?
Keep the raised squares and the angled edge on all four sides without printing the characters on the top of the key.
Then, using an application to reprogram the position of the characters into any sequence the typist desires, the mechanical redesign would have the characters appear in a electronic display on the bottom angled edge (or the pad or lower half, etc., and viewable by the typist), perhaps being on a small screen (lcd or something better?
) and capable of being "lit up".
So, for example, you may want to reposition the alphabet (based on your language) to be left-to-right or right-to-left and top-to-bottom or bottom-to-top; or the vowels in one location and the consonants in another; or, perhaps they could be positioned by letter usage, say from highest to lowest (in English, it's probably e,t,a,i,o,n,); or a trained traditionalist would leave it alone, since viewing the keyboard is unnecessary.
And so on.
And of course, those who prefer to hunt-and-peck could either have a field-day or leave it as-is.
After all, the days of using the qwerty format to slow down the typist due to mechanical limitations existing in the original type-writer are over.
It remains mostly because of tradition and the hassle of making the change to a better or faster format now allowed by electronic keyboards.
This might be a solution that would make it easier to make the change.
So what is missing here possibly making me be: clueless?
Has it already been tried and found impractical; or is it on the market at a prohibitive price?
However, if not and there is general agreement this does have potential, I realize putting it in the public domain by posting it here on Slashdot has nullfied any chance of making an original claim.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184421</id>
	<title>Maybe</title>
	<author>Anonymous</author>
	<datestamp>1243966020000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>Illt maek wruting furst psost easzier</htmltext>
<tokenext>Illt maek wruting furst psost easzier</tokentext>
<sentencetext>Illt maek wruting furst psost easzier</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185305</id>
	<title>Not a patent...</title>
	<author>spire3661</author>
	<datestamp>1243969620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Seriously, this shouldnt not be considered a patentable design.</p></htmltext>
<tokenext>Seriously , this shouldnt not be considered a patentable design .</tokentext>
<sentencetext>Seriously, this shouldnt not be considered a patentable design.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184913</id>
	<title>Re:The Best Thing To Do</title>
	<author>Krneki</author>
	<datestamp>1243967880000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>The ultimate PC fanatic, staring at the screen without moving for several hours.<br><br>The idea is so wrong, but I like it.<nobr> <wbr></nobr>:)</htmltext>
<tokenext>The ultimate PC fanatic , staring at the screen without moving for several hours.The idea is so wrong , but I like it .
: )</tokentext>
<sentencetext>The ultimate PC fanatic, staring at the screen without moving for several hours.The idea is so wrong, but I like it.
:)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184769</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184781</id>
	<title>?? On touchscreens..</title>
	<author>dbcad7</author>
	<datestamp>1243967280000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>Is the area designated as a button always the same size as the graphic of the button ?<nobr> <wbr></nobr>.. why couldn't you do the same thing showing square buttons but sensing triangular or smaller circular areas ?<nobr> <wbr></nobr>.. You could also use color in the button graphic to target the hotspot, fading to the buttton edges.</htmltext>
<tokenext>Is the area designated as a button always the same size as the graphic of the button ?
.. why could n't you do the same thing showing square buttons but sensing triangular or smaller circular areas ?
.. You could also use color in the button graphic to target the hotspot , fading to the buttton edges .</tokentext>
<sentencetext>Is the area designated as a button always the same size as the graphic of the button ?
.. why couldn't you do the same thing showing square buttons but sensing triangular or smaller circular areas ?
.. You could also use color in the button graphic to target the hotspot, fading to the buttton edges.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188227</id>
	<title>Re:The Best Thing To Do</title>
	<author>hosecoat</author>
	<datestamp>1243938780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Now, If we invert the alternate rows and get rid of the dead space, we can make a really small keyboard, fraught with peril for fat bottomed girls.</htmltext>
<tokenext>Now , If we invert the alternate rows and get rid of the dead space , we can make a really small keyboard , fraught with peril for fat bottomed girls .</tokentext>
<sentencetext>Now, If we invert the alternate rows and get rid of the dead space, we can make a really small keyboard, fraught with peril for fat bottomed girls.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28187389</id>
	<title>Re:The Best Thing To Do</title>
	<author>Anonymous</author>
	<datestamp>1243935420000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>Seriously, I'd like a keyboard that reads my mind</i> </p><p>dude, that is so yesterday. I'm using (blowjob) on of those key(nice tits) boards right now. I (69) highly reco(tap that)mmend that you go (damn, lookat that ass) out and get one (hot lesbian action) for yourself. They are (I'd like to bend her over) not that ex(she's gotta be 18)pensive.....</p><p>you know, on second thought, not such a good idea.</p></htmltext>
<tokenext>Seriously , I 'd like a keyboard that reads my mind dude , that is so yesterday .
I 'm using ( blowjob ) on of those key ( nice tits ) boards right now .
I ( 69 ) highly reco ( tap that ) mmend that you go ( damn , lookat that ass ) out and get one ( hot lesbian action ) for yourself .
They are ( I 'd like to bend her over ) not that ex ( she 's got ta be 18 ) pensive.....you know , on second thought , not such a good idea .</tokentext>
<sentencetext>Seriously, I'd like a keyboard that reads my mind dude, that is so yesterday.
I'm using (blowjob) on of those key(nice tits) boards right now.
I (69) highly reco(tap that)mmend that you go (damn, lookat that ass) out and get one (hot lesbian action) for yourself.
They are (I'd like to bend her over) not that ex(she's gotta be 18)pensive.....you know, on second thought, not such a good idea.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184769</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825</id>
	<title>Re:The Best Thing To Do</title>
	<author>spydabyte</author>
	<datestamp>1243967460000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p><div class="quote"><p>Baker told Register Hardware today that each triangular key has significantly more dead space around it than you&#226;(TM)d find on a standard Qwerty layout. Consequently, users are more likely to press the correct key each time they tap.</p> </div><p>Significantly more is right. It's about the same size as the buttons themselves, doubling screen real-estate.<br> <br>From my minimalistic POV, that's horrid.</p></div>
	</htmltext>
<tokenext>Baker told Register Hardware today that each triangular key has significantly more dead space around it than you   ( TM ) d find on a standard Qwerty layout .
Consequently , users are more likely to press the correct key each time they tap .
Significantly more is right .
It 's about the same size as the buttons themselves , doubling screen real-estate .
From my minimalistic POV , that 's horrid .</tokentext>
<sentencetext>Baker told Register Hardware today that each triangular key has significantly more dead space around it than youâ(TM)d find on a standard Qwerty layout.
Consequently, users are more likely to press the correct key each time they tap.
Significantly more is right.
It's about the same size as the buttons themselves, doubling screen real-estate.
From my minimalistic POV, that's horrid.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185051</id>
	<title>Re:Apple is, or should be, FAR ahead of this...</title>
	<author>C10H14N2</author>
	<datestamp>1243968420000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p><i>most of the way over toward E, and the previous two letters were T-H, so I'm going to go ahead and make it an E.</i></p><p>That is the single most aggravating "feature" of the iPhone keyboard. To he'll with that ducking shot.</p></htmltext>
<tokenext>most of the way over toward E , and the previous two letters were T-H , so I 'm going to go ahead and make it an E.That is the single most aggravating " feature " of the iPhone keyboard .
To he 'll with that ducking shot .</tokentext>
<sentencetext>most of the way over toward E, and the previous two letters were T-H, so I'm going to go ahead and make it an E.That is the single most aggravating "feature" of the iPhone keyboard.
To he'll with that ducking shot.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184697</id>
	<title>Re:The Best Thing To Do</title>
	<author>hoytak</author>
	<datestamp>1243966980000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>I thought the caps lock key made things easier? <a href="http://www.bash.org/?835030" title="bash.org" rel="nofollow">http://www.bash.org/?835030</a> [bash.org]</p></htmltext>
<tokenext>I thought the caps lock key made things easier ?
http : //www.bash.org/ ? 835030 [ bash.org ]</tokentext>
<sentencetext>I thought the caps lock key made things easier?
http://www.bash.org/?835030 [bash.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186297</id>
	<title>Even Better Way: Voice Recognition</title>
	<author>BarefootClown</author>
	<datestamp>1243973940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I've seen posters talking about combining this with predictive text, but what about using voice recognition instead?  A little software magic, a good dictionary, and you could dictate the thing without having to worry about mashing the wrong key.</p><p>Throw in a text-to-speech interface on the other end and it would be that much easier!</p></htmltext>
<tokenext>I 've seen posters talking about combining this with predictive text , but what about using voice recognition instead ?
A little software magic , a good dictionary , and you could dictate the thing without having to worry about mashing the wrong key.Throw in a text-to-speech interface on the other end and it would be that much easier !</tokentext>
<sentencetext>I've seen posters talking about combining this with predictive text, but what about using voice recognition instead?
A little software magic, a good dictionary, and you could dictate the thing without having to worry about mashing the wrong key.Throw in a text-to-speech interface on the other end and it would be that much easier!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184605</id>
	<title>Re:The Best Thing To Do</title>
	<author>Mordok-DestroyerOfWo</author>
	<datestamp>1243966620000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext>So now one can patent shapes?  I need to get the paperwork rolling on a new idea I have for a tetrahedron mouse!</htmltext>
<tokenext>So now one can patent shapes ?
I need to get the paperwork rolling on a new idea I have for a tetrahedron mouse !</tokentext>
<sentencetext>So now one can patent shapes?
I need to get the paperwork rolling on a new idea I have for a tetrahedron mouse!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28198071</id>
	<title>Re:The Best Thing To Do</title>
	<author>MoogMan</author>
	<datestamp>1244053140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You can also disable <b>any</b> keys on <b>any</b> with hardware (or: screwdriver)</p></htmltext>
<tokenext>You can also disable any keys on any with hardware ( or : screwdriver )</tokentext>
<sentencetext>You can also disable any keys on any with hardware (or: screwdriver)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185241</id>
	<title>Re:The Best Thing To Do</title>
	<author>Hadlock</author>
	<datestamp>1243969260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You can also disable those keys in hardware, on practically any keyboard ever. Wedge anything from a pen cap to a screwdriver under one edge of the offending key and pry it off. My 108-key keyboard is now a 101 (well actually 100 - its missing the caps lock key)-key keyboard.</p></htmltext>
<tokenext>You can also disable those keys in hardware , on practically any keyboard ever .
Wedge anything from a pen cap to a screwdriver under one edge of the offending key and pry it off .
My 108-key keyboard is now a 101 ( well actually 100 - its missing the caps lock key ) -key keyboard .</tokentext>
<sentencetext>You can also disable those keys in hardware, on practically any keyboard ever.
Wedge anything from a pen cap to a screwdriver under one edge of the offending key and pry it off.
My 108-key keyboard is now a 101 (well actually 100 - its missing the caps lock key)-key keyboard.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185691</id>
	<title>Re:The Best Thing To Do</title>
	<author>ExploHD</author>
	<datestamp>1243971240000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>The Logitech wave keyboard has a little "moat" around Capslock and Numlock keys, making them far less easy to accidentally press.</p></div><p>Plus it kept the Black Knight at bay!</p></div>
	</htmltext>
<tokenext>The Logitech wave keyboard has a little " moat " around Capslock and Numlock keys , making them far less easy to accidentally press.Plus it kept the Black Knight at bay !</tokentext>
<sentencetext>The Logitech wave keyboard has a little "moat" around Capslock and Numlock keys, making them far less easy to accidentally press.Plus it kept the Black Knight at bay!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28196995</id>
	<title>Re:Maybe</title>
	<author>1\_brown\_mouse</author>
	<datestamp>1244049060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You win 1 Free! Internets.</p><p>Good jorb on the snicker.</p></htmltext>
<tokenext>You win 1 Free !
Internets.Good jorb on the snicker .</tokentext>
<sentencetext>You win 1 Free!
Internets.Good jorb on the snicker.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184421</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185853</id>
	<title>Re:If triangles are good...</title>
	<author>Anonymous</author>
	<datestamp>1243971960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>... wouldn't diamonds be better?</p></div><p>No. He took something that was traditionally 4-sided and made it 3-sided. The only way to further improve on this design is to eliminate yet another side.</p><p>So, one pixel wide lines would be the next obvious increment to this idea. And, if you want to go all out and make the ultimate easy-to-use touchscreen virtual keyboard, go with single pixels.</p></div>
	</htmltext>
<tokenext>... would n't diamonds be better ? No .
He took something that was traditionally 4-sided and made it 3-sided .
The only way to further improve on this design is to eliminate yet another side.So , one pixel wide lines would be the next obvious increment to this idea .
And , if you want to go all out and make the ultimate easy-to-use touchscreen virtual keyboard , go with single pixels .</tokentext>
<sentencetext>... wouldn't diamonds be better?No.
He took something that was traditionally 4-sided and made it 3-sided.
The only way to further improve on this design is to eliminate yet another side.So, one pixel wide lines would be the next obvious increment to this idea.
And, if you want to go all out and make the ultimate easy-to-use touchscreen virtual keyboard, go with single pixels.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28187667</id>
	<title>He can do it on the iPhone</title>
	<author>x102output</author>
	<datestamp>1243936500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The inventor commented on how he would like to do that with the iPhone, but then said it would be hard to get the cooperation from Apple.

<br> <br>
I suggest he look into the jailbreaking dev community.   There are already a few dozen custom keyboards you can put on your iPhone that will fully replace the keyboard and is universal for all apps.  I believe there is a jailbreak app specifically for this that uses plugin-based keyboard themes.  I can't remember the name off the top of my head, but it's there.</htmltext>
<tokenext>The inventor commented on how he would like to do that with the iPhone , but then said it would be hard to get the cooperation from Apple .
I suggest he look into the jailbreaking dev community .
There are already a few dozen custom keyboards you can put on your iPhone that will fully replace the keyboard and is universal for all apps .
I believe there is a jailbreak app specifically for this that uses plugin-based keyboard themes .
I ca n't remember the name off the top of my head , but it 's there .</tokentext>
<sentencetext>The inventor commented on how he would like to do that with the iPhone, but then said it would be hard to get the cooperation from Apple.
I suggest he look into the jailbreaking dev community.
There are already a few dozen custom keyboards you can put on your iPhone that will fully replace the keyboard and is universal for all apps.
I believe there is a jailbreak app specifically for this that uses plugin-based keyboard themes.
I can't remember the name off the top of my head, but it's there.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185681</id>
	<title>Re:The Best Thing To Do</title>
	<author>Anonymous</author>
	<datestamp>1243971180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>A keyboard with a crippled ins/del/home/end/pgup/pgdn block and a 3by3 grouping of F-keys is the best keyboard you've ever owned? I mean I love the Logitech keyboard's touch (own a G15 myself) but that layout is just horrid!</p></htmltext>
<tokenext>A keyboard with a crippled ins/del/home/end/pgup/pgdn block and a 3by3 grouping of F-keys is the best keyboard you 've ever owned ?
I mean I love the Logitech keyboard 's touch ( own a G15 myself ) but that layout is just horrid !</tokentext>
<sentencetext>A keyboard with a crippled ins/del/home/end/pgup/pgdn block and a 3by3 grouping of F-keys is the best keyboard you've ever owned?
I mean I love the Logitech keyboard's touch (own a G15 myself) but that layout is just horrid!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188165</id>
	<title>Re:The Best Thing To Do</title>
	<author>AnAdventurer</author>
	<datestamp>1243938540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Use alligators, they are easier to get a hold in north America. I can get you some at half price, I have  cousin in Miami.</htmltext>
<tokenext>Use alligators , they are easier to get a hold in north America .
I can get you some at half price , I have cousin in Miami .</tokentext>
<sentencetext>Use alligators, they are easier to get a hold in north America.
I can get you some at half price, I have  cousin in Miami.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185139</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184935</id>
	<title>Re:The Best Thing To Do</title>
	<author>twoDigitIq</author>
	<datestamp>1243967940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Or you could just pry those keys off, like I've done on every keyboard I've ever owned</htmltext>
<tokenext>Or you could just pry those keys off , like I 've done on every keyboard I 've ever owned</tokentext>
<sentencetext>Or you could just pry those keys off, like I've done on every keyboard I've ever owned</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188919</id>
	<title>Not useful for touch screens</title>
	<author>Anonymous</author>
	<datestamp>1243941840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Although this seems like it might be useful on a physical keypad, TFA talks mainly about using it on the iphone.</p><p>I can't imagine how this would help for the iphone because as stated the keys still occupy the same amount of space. This being added to a touch screen would make things worse in the sense that you would be hitting blank space instead or the wrong key instead of just the wrong key. The only added benifit might be a placebo effect of making users more accurate of where they touch their fingers by making the target appear smaller.</p></htmltext>
<tokenext>Although this seems like it might be useful on a physical keypad , TFA talks mainly about using it on the iphone.I ca n't imagine how this would help for the iphone because as stated the keys still occupy the same amount of space .
This being added to a touch screen would make things worse in the sense that you would be hitting blank space instead or the wrong key instead of just the wrong key .
The only added benifit might be a placebo effect of making users more accurate of where they touch their fingers by making the target appear smaller .</tokentext>
<sentencetext>Although this seems like it might be useful on a physical keypad, TFA talks mainly about using it on the iphone.I can't imagine how this would help for the iphone because as stated the keys still occupy the same amount of space.
This being added to a touch screen would make things worse in the sense that you would be hitting blank space instead or the wrong key instead of just the wrong key.
The only added benifit might be a placebo effect of making users more accurate of where they touch their fingers by making the target appear smaller.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186001</id>
	<title>Re:For the iPhone, doesn't make sense</title>
	<author>phreakhead</author>
	<datestamp>1243972560000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>0</modscore>
	<htmltext><p>His point is that the iPhone software isn't sophisticated enough to detect "which one you were actually closer to." I've tried typing on my friend's iPhone before, and it's horrible. I'm sure all the fanboys will scoff because they've trained themselves to be much more precise (in fact I learned quickly that it's all about the lift-off, not the push-on: you just slap your finger down haphazardly but then slide it to where the correct key is selected before you take it off), but this keyboard has a better design so you don't need to correct it in software. That's something I think Apple would jizz their pants over and so I hope to see this guy making money soon.</p></htmltext>
<tokenext>His point is that the iPhone software is n't sophisticated enough to detect " which one you were actually closer to .
" I 've tried typing on my friend 's iPhone before , and it 's horrible .
I 'm sure all the fanboys will scoff because they 've trained themselves to be much more precise ( in fact I learned quickly that it 's all about the lift-off , not the push-on : you just slap your finger down haphazardly but then slide it to where the correct key is selected before you take it off ) , but this keyboard has a better design so you do n't need to correct it in software .
That 's something I think Apple would jizz their pants over and so I hope to see this guy making money soon .</tokentext>
<sentencetext>His point is that the iPhone software isn't sophisticated enough to detect "which one you were actually closer to.
" I've tried typing on my friend's iPhone before, and it's horrible.
I'm sure all the fanboys will scoff because they've trained themselves to be much more precise (in fact I learned quickly that it's all about the lift-off, not the push-on: you just slap your finger down haphazardly but then slide it to where the correct key is selected before you take it off), but this keyboard has a better design so you don't need to correct it in software.
That's something I think Apple would jizz their pants over and so I hope to see this guy making money soon.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185139</id>
	<title>Re:The Best Thing To Do</title>
	<author>CarpetShark</author>
	<datestamp>1243968780000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><blockquote><div><p>The Logitech wave keyboard has a little "moat" around Capslock and Numlock keys</p></div></blockquote><p>Excellent.  So then, the formula I need will be:</p><p>(num\_users * keyboard\_price) + (num\_users * large\_reptile\_price * crocodiles\_per\_moat)</p><p>?</p></div>
	</htmltext>
<tokenext>The Logitech wave keyboard has a little " moat " around Capslock and Numlock keysExcellent .
So then , the formula I need will be : ( num \ _users * keyboard \ _price ) + ( num \ _users * large \ _reptile \ _price * crocodiles \ _per \ _moat ) ?</tokentext>
<sentencetext>The Logitech wave keyboard has a little "moat" around Capslock and Numlock keysExcellent.
So then, the formula I need will be:(num\_users * keyboard\_price) + (num\_users * large\_reptile\_price * crocodiles\_per\_moat)?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28190683</id>
	<title>DVORAK anyone?</title>
	<author>Anonymous</author>
	<datestamp>1243953600000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'm surprised no one has picked up on QWERTY being deliberately designed to slow down typing.<br>Best way to speed it up is to switch to DVORAK.<br>Nice idea though.</p></htmltext>
<tokenext>I 'm surprised no one has picked up on QWERTY being deliberately designed to slow down typing.Best way to speed it up is to switch to DVORAK.Nice idea though .</tokentext>
<sentencetext>I'm surprised no one has picked up on QWERTY being deliberately designed to slow down typing.Best way to speed it up is to switch to DVORAK.Nice idea though.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186239</id>
	<title>Re:Apple is, or should be, FAR ahead of this...</title>
	<author>goodmanj</author>
	<datestamp>1243973700000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>Agree.  Anyone who thinks this is a cool idea hasn't used an iPhone keypad much.</p><p>The inventor's still stuck on the notion that each keypress must map onto a single character somehow, but the iPhone is smarter than that.  It resolves ambiguous keypresses based on the letters that came before, and *also* the ones that came after.  For instance, typing "THI", it assumes I'm on my way to "this", "thin", or "thick", but if I follow it up with "MAS", it changes the I to an O for "THOMAS".</p><p>And if I really did want to type the unusual name "Thimas", I just hit the little cancel-autocorrect x-box on the screen.</p></htmltext>
<tokenext>Agree .
Anyone who thinks this is a cool idea has n't used an iPhone keypad much.The inventor 's still stuck on the notion that each keypress must map onto a single character somehow , but the iPhone is smarter than that .
It resolves ambiguous keypresses based on the letters that came before , and * also * the ones that came after .
For instance , typing " THI " , it assumes I 'm on my way to " this " , " thin " , or " thick " , but if I follow it up with " MAS " , it changes the I to an O for " THOMAS " .And if I really did want to type the unusual name " Thimas " , I just hit the little cancel-autocorrect x-box on the screen .</tokentext>
<sentencetext>Agree.
Anyone who thinks this is a cool idea hasn't used an iPhone keypad much.The inventor's still stuck on the notion that each keypress must map onto a single character somehow, but the iPhone is smarter than that.
It resolves ambiguous keypresses based on the letters that came before, and *also* the ones that came after.
For instance, typing "THI", it assumes I'm on my way to "this", "thin", or "thick", but if I follow it up with "MAS", it changes the I to an O for "THOMAS".And if I really did want to type the unusual name "Thimas", I just hit the little cancel-autocorrect x-box on the screen.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184911</id>
	<title>If triangles are good...</title>
	<author>frank\_adrian314159</author>
	<datestamp>1243967880000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>... wouldn't diamonds be better?</p></htmltext>
<tokenext>... would n't diamonds be better ?</tokentext>
<sentencetext>... wouldn't diamonds be better?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185439</id>
	<title>not convincing</title>
	<author>Tom</author>
	<datestamp>1243970100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If it's just for the deadspace, then smaller keys should work the same, right? So what's special about the <i>form</i> of triangles? The article doesn't mention that. Also not how the odd layout comes about. With a triangle layout, I would've expected them to have alternating directions, because only then is is really less likely to hit the other key, because the broad end you're trying to hit would be bordering small ends, if you get what I mean.</p></htmltext>
<tokenext>If it 's just for the deadspace , then smaller keys should work the same , right ?
So what 's special about the form of triangles ?
The article does n't mention that .
Also not how the odd layout comes about .
With a triangle layout , I would 've expected them to have alternating directions , because only then is is really less likely to hit the other key , because the broad end you 're trying to hit would be bordering small ends , if you get what I mean .</tokentext>
<sentencetext>If it's just for the deadspace, then smaller keys should work the same, right?
So what's special about the form of triangles?
The article doesn't mention that.
Also not how the odd layout comes about.
With a triangle layout, I would've expected them to have alternating directions, because only then is is really less likely to hit the other key, because the broad end you're trying to hit would be bordering small ends, if you get what I mean.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185237</id>
	<title>But will it stop me from doing this...</title>
	<author>geeper</author>
	<datestamp>1243969260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Select * form<nobr> <wbr></nobr>....

I must do that 100 times a day!!!</htmltext>
<tokenext>Select * form ... . I must do that 100 times a day ! !
!</tokentext>
<sentencetext>Select * form ....

I must do that 100 times a day!!
!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185115</id>
	<title>I'm more upset...</title>
	<author>PJ1216</author>
	<datestamp>1243968660000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>I'm more upset that he got a patent for changing the shapes from square to a triangle. This doesn't show any real creativity to even constitute a design patent. Its like a themed keyboard. Like if someone decided to make a keyboard using various shapes just for style. I doubt that could be patented either.</htmltext>
<tokenext>I 'm more upset that he got a patent for changing the shapes from square to a triangle .
This does n't show any real creativity to even constitute a design patent .
Its like a themed keyboard .
Like if someone decided to make a keyboard using various shapes just for style .
I doubt that could be patented either .</tokentext>
<sentencetext>I'm more upset that he got a patent for changing the shapes from square to a triangle.
This doesn't show any real creativity to even constitute a design patent.
Its like a themed keyboard.
Like if someone decided to make a keyboard using various shapes just for style.
I doubt that could be patented either.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185951</id>
	<title>Re:The Best Thing To Do</title>
	<author>asCii88</author>
	<datestamp>1243972320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I, instead, know people who activate CapsLock for even one letter.</htmltext>
<tokenext>I , instead , know people who activate CapsLock for even one letter .</tokentext>
<sentencetext>I, instead, know people who activate CapsLock for even one letter.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185301</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28233099</id>
	<title>Give us stars!</title>
	<author>DanielSmedegaardBuus</author>
	<datestamp>1244304300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I want them star-shaped, with one of Elton John's eyes in the center of each. That'll make typing a fun activity for the kids, promote literacy.</htmltext>
<tokenext>I want them star-shaped , with one of Elton John 's eyes in the center of each .
That 'll make typing a fun activity for the kids , promote literacy .</tokentext>
<sentencetext>I want them star-shaped, with one of Elton John's eyes in the center of each.
That'll make typing a fun activity for the kids, promote literacy.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28192193</id>
	<title>better triangular keyboard</title>
	<author>theculprit</author>
	<datestamp>1243968000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>funny, when i saw the screenshot it wasn't what i had pictured in my head. seems more obvious to me to have the keys alternating between triangles pointing up and triangles pointing down. that would be a more efficient layout imho. since ppl would be drawn towards pressing at the base of the triangle, so it should reduce typing errors. just my 2c...</htmltext>
<tokenext>funny , when i saw the screenshot it was n't what i had pictured in my head .
seems more obvious to me to have the keys alternating between triangles pointing up and triangles pointing down .
that would be a more efficient layout imho .
since ppl would be drawn towards pressing at the base of the triangle , so it should reduce typing errors .
just my 2c.. .</tokentext>
<sentencetext>funny, when i saw the screenshot it wasn't what i had pictured in my head.
seems more obvious to me to have the keys alternating between triangles pointing up and triangles pointing down.
that would be a more efficient layout imho.
since ppl would be drawn towards pressing at the base of the triangle, so it should reduce typing errors.
just my 2c...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28198111</id>
	<title>Re:Apple is, or should be, FAR ahead of this...</title>
	<author>Wolfrider</author>
	<datestamp>1244053320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>--That's going to be a real PITA if you're trying to type Throughput, or Thread, or Thrust, or...</p></htmltext>
<tokenext>--That 's going to be a real PITA if you 're trying to type Throughput , or Thread , or Thrust , or.. .</tokentext>
<sentencetext>--That's going to be a real PITA if you're trying to type Throughput, or Thread, or Thrust, or...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186773</id>
	<title>Re:Klingon Keyboard?</title>
	<author>K. S. Kyosuke</author>
	<datestamp>1243976040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><a href="http://tng.trekcore.com/gallery/albums/s2/2x11/contagion270.jpg" title="trekcore.com">Iconians</a> [trekcore.com] used that as well.<nobr> <wbr></nobr>:-)</htmltext>
<tokenext>Iconians [ trekcore.com ] used that as well .
: - )</tokentext>
<sentencetext>Iconians [trekcore.com] used that as well.
:-)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186787</id>
	<title>Re:The Best Thing To Do</title>
	<author>slinches</author>
	<datestamp>1243976040000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>Significantly more is right. It's about the same size as the buttons themselves, doubling screen real-estate.</p></div><p>From the picture, it looks like this could be done in the same screen area if the width and height of the triangular keys remained the same as their square counterparts.  This would cause each key to be smaller in area though, so I'm not sure if it would be any better due to more frequent misses.</p></div>
	</htmltext>
<tokenext>Significantly more is right .
It 's about the same size as the buttons themselves , doubling screen real-estate.From the picture , it looks like this could be done in the same screen area if the width and height of the triangular keys remained the same as their square counterparts .
This would cause each key to be smaller in area though , so I 'm not sure if it would be any better due to more frequent misses .</tokentext>
<sentencetext>Significantly more is right.
It's about the same size as the buttons themselves, doubling screen real-estate.From the picture, it looks like this could be done in the same screen area if the width and height of the triangular keys remained the same as their square counterparts.
This would cause each key to be smaller in area though, so I'm not sure if it would be any better due to more frequent misses.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185209</id>
	<title>frost pi52t</title>
	<author>Anonymous</author>
	<datestamp>1243969080000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext>lost its earlier the facts and our chances community. The to have regular continues to lose to the crowd in the chhosing on 8y Pentium Pro Romeo and Juliet Ink splashes across While the project Series of internal you are a screaming However I don't prima donnas, and support GNAA,</htmltext>
<tokenext>lost its earlier the facts and our chances community .
The to have regular continues to lose to the crowd in the chhosing on 8y Pentium Pro Romeo and Juliet Ink splashes across While the project Series of internal you are a screaming However I do n't prima donnas , and support GNAA,</tokentext>
<sentencetext>lost its earlier the facts and our chances community.
The to have regular continues to lose to the crowd in the chhosing on 8y Pentium Pro Romeo and Juliet Ink splashes across While the project Series of internal you are a screaming However I don't prima donnas, and support GNAA,</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28187165</id>
	<title>Move in the right direction.</title>
	<author>Penguinoflight</author>
	<datestamp>1243934520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Look around your office, you'll probably find lots of keyboards with concave keys.  While that may have been necessary with mechanical IBM's, it's counterproductive today.  Flat keys are excellent, and avoid lots of the accidental double key presses that normally happen when you touch the edge of a concave key.  Without that sharp edge on the side, there's nothing pushing your finger into the adjacent key.  I have somewhat large fingers, and find that slightly convex keys (like on the z-board for example) are more comfortable because the impact of each key is spread over a larger surface of the finger tip.</p><p>I don't expect a a pointed design to catch on, or even work well.  If a poor design inspires real designs I don't see it hurting however.</p></htmltext>
<tokenext>Look around your office , you 'll probably find lots of keyboards with concave keys .
While that may have been necessary with mechanical IBM 's , it 's counterproductive today .
Flat keys are excellent , and avoid lots of the accidental double key presses that normally happen when you touch the edge of a concave key .
Without that sharp edge on the side , there 's nothing pushing your finger into the adjacent key .
I have somewhat large fingers , and find that slightly convex keys ( like on the z-board for example ) are more comfortable because the impact of each key is spread over a larger surface of the finger tip.I do n't expect a a pointed design to catch on , or even work well .
If a poor design inspires real designs I do n't see it hurting however .</tokentext>
<sentencetext>Look around your office, you'll probably find lots of keyboards with concave keys.
While that may have been necessary with mechanical IBM's, it's counterproductive today.
Flat keys are excellent, and avoid lots of the accidental double key presses that normally happen when you touch the edge of a concave key.
Without that sharp edge on the side, there's nothing pushing your finger into the adjacent key.
I have somewhat large fingers, and find that slightly convex keys (like on the z-board for example) are more comfortable because the impact of each key is spread over a larger surface of the finger tip.I don't expect a a pointed design to catch on, or even work well.
If a poor design inspires real designs I don't see it hurting however.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185359</id>
	<title>Re:For the iPhone, doesn't make sense</title>
	<author>burris</author>
	<datestamp>1243969800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You get tactile feedback on a touchscreen when you touch it.</p></htmltext>
<tokenext>You get tactile feedback on a touchscreen when you touch it .</tokentext>
<sentencetext>You get tactile feedback on a touchscreen when you touch it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186379</id>
	<title>Triangles?</title>
	<author>S77IM</author>
	<datestamp>1243974360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Why triangles?  Why not circles or small squares, just with more dead space between keys than usual?</p></htmltext>
<tokenext>Why triangles ?
Why not circles or small squares , just with more dead space between keys than usual ?</tokentext>
<sentencetext>Why triangles?
Why not circles or small squares, just with more dead space between keys than usual?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186111</id>
	<title>Strength</title>
	<author>BGrif</author>
	<datestamp>1243973040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Because the triangle is one of the strongest shapes and distributes weight very well, it would be a very strong keyboard.</htmltext>
<tokenext>Because the triangle is one of the strongest shapes and distributes weight very well , it would be a very strong keyboard .</tokentext>
<sentencetext>Because the triangle is one of the strongest shapes and distributes weight very well, it would be a very strong keyboard.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185457</id>
	<title>Training to make unaware mistakes?</title>
	<author>el\_gato\_borracho</author>
	<datestamp>1243970220000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>Does using such an auto-correcting keyboard make it harder to type correctly when you move to a "normal" keyboard?  Something bothers me about devices that train me to make more unaware mistakes.</htmltext>
<tokenext>Does using such an auto-correcting keyboard make it harder to type correctly when you move to a " normal " keyboard ?
Something bothers me about devices that train me to make more unaware mistakes .</tokentext>
<sentencetext>Does using such an auto-correcting keyboard make it harder to type correctly when you move to a "normal" keyboard?
Something bothers me about devices that train me to make more unaware mistakes.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185181</id>
	<title>Missing the points</title>
	<author>192939495969798999</author>
	<datestamp>1243968960000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>This has nothing to do with the main reasons that people like me cannot use tiny keyboards.<br>0.  When I press down, my finger pad overlaps way more than one key.  therefore, I am prone to make mistakes.<br>1.  I can't see through my finger to the keyboard if my finger covers 2 or more keys, therefore I am prone to make some more mistakes.<br>2.  No, I don't need to see the keys, but I at least need to be able to feel their delineations in lieu of that, and since the thing has no tactile measurable quality like a real keyboard, I am prone to make yet more mistakes.</p><p>I can work a blackberry keyboard a little because at least i can feel the difference in the keys vs. spaces.  Without some physical delineation or press-from-behind type capacity, I don't think any tiny touchscreen keyboard will be any more for me usable than any other one.</p></htmltext>
<tokenext>This has nothing to do with the main reasons that people like me can not use tiny keyboards.0 .
When I press down , my finger pad overlaps way more than one key .
therefore , I am prone to make mistakes.1 .
I ca n't see through my finger to the keyboard if my finger covers 2 or more keys , therefore I am prone to make some more mistakes.2 .
No , I do n't need to see the keys , but I at least need to be able to feel their delineations in lieu of that , and since the thing has no tactile measurable quality like a real keyboard , I am prone to make yet more mistakes.I can work a blackberry keyboard a little because at least i can feel the difference in the keys vs. spaces. Without some physical delineation or press-from-behind type capacity , I do n't think any tiny touchscreen keyboard will be any more for me usable than any other one .</tokentext>
<sentencetext>This has nothing to do with the main reasons that people like me cannot use tiny keyboards.0.
When I press down, my finger pad overlaps way more than one key.
therefore, I am prone to make mistakes.1.
I can't see through my finger to the keyboard if my finger covers 2 or more keys, therefore I am prone to make some more mistakes.2.
No, I don't need to see the keys, but I at least need to be able to feel their delineations in lieu of that, and since the thing has no tactile measurable quality like a real keyboard, I am prone to make yet more mistakes.I can work a blackberry keyboard a little because at least i can feel the difference in the keys vs. spaces.  Without some physical delineation or press-from-behind type capacity, I don't think any tiny touchscreen keyboard will be any more for me usable than any other one.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184947</id>
	<title>Sceptical</title>
	<author>dethndrek</author>
	<datestamp>1243968000000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>As a programmer, any time I hear hype like this ". .<nobr> <wbr></nobr>.could spell the end for accidental key presses." I laugh a little.</p><p>We will NEVER spell the end for accidental use of technology by using more technology.</p><p>It kind of falls into the old maxim "Try to make anything idiot proof, and the world with generate bigger idiots".</p></htmltext>
<tokenext>As a programmer , any time I hear hype like this " .
. .could spell the end for accidental key presses .
" I laugh a little.We will NEVER spell the end for accidental use of technology by using more technology.It kind of falls into the old maxim " Try to make anything idiot proof , and the world with generate bigger idiots " .</tokentext>
<sentencetext>As a programmer, any time I hear hype like this ".
. .could spell the end for accidental key presses.
" I laugh a little.We will NEVER spell the end for accidental use of technology by using more technology.It kind of falls into the old maxim "Try to make anything idiot proof, and the world with generate bigger idiots".</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184891</id>
	<title>Re:Apple is, or should be, FAR ahead of this...</title>
	<author>moon3</author>
	<datestamp>1243967820000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext>Also contrary to all the claims, you can't mistype on iPhone virtual keyboard, once you learn that release-key trick, you just can't. Lots of people is under-informed about this. I do not need 'real' keyboard on the phone anymore, even I thought iPhone virtual keyboard would be pain and useless.. well, I was wrong.</htmltext>
<tokenext>Also contrary to all the claims , you ca n't mistype on iPhone virtual keyboard , once you learn that release-key trick , you just ca n't .
Lots of people is under-informed about this .
I do not need 'real ' keyboard on the phone anymore , even I thought iPhone virtual keyboard would be pain and useless.. well , I was wrong .</tokentext>
<sentencetext>Also contrary to all the claims, you can't mistype on iPhone virtual keyboard, once you learn that release-key trick, you just can't.
Lots of people is under-informed about this.
I do not need 'real' keyboard on the phone anymore, even I thought iPhone virtual keyboard would be pain and useless.. well, I was wrong.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186345</id>
	<title>Re:?? On touchscreens..</title>
	<author>goodmanj</author>
	<datestamp>1243974180000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>That's exactly what the iPhone does.  You can be really sloppy when typing common letters like "S", but you have to be more precise for nearby uncommon letters like "Z".  Not that that's a problem, it'll autocorrect if you miss.</p><p>Supposedly the sizes of these sensitive areas can change based on what you're in the process of typing, but I can't tell if it's actually doing that.</p></htmltext>
<tokenext>That 's exactly what the iPhone does .
You can be really sloppy when typing common letters like " S " , but you have to be more precise for nearby uncommon letters like " Z " .
Not that that 's a problem , it 'll autocorrect if you miss.Supposedly the sizes of these sensitive areas can change based on what you 're in the process of typing , but I ca n't tell if it 's actually doing that .</tokentext>
<sentencetext>That's exactly what the iPhone does.
You can be really sloppy when typing common letters like "S", but you have to be more precise for nearby uncommon letters like "Z".
Not that that's a problem, it'll autocorrect if you miss.Supposedly the sizes of these sensitive areas can change based on what you're in the process of typing, but I can't tell if it's actually doing that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184781</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28203369</id>
	<title>Make it for Android</title>
	<author>Vitriolix</author>
	<datestamp>1244031480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That's one of the really nice things about Android... the soft keyboard uses a totally open API that any 3rd party can develop too and give the user the choice to use.</p></htmltext>
<tokenext>That 's one of the really nice things about Android... the soft keyboard uses a totally open API that any 3rd party can develop too and give the user the choice to use .</tokentext>
<sentencetext>That's one of the really nice things about Android... the soft keyboard uses a totally open API that any 3rd party can develop too and give the user the choice to use.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184535</id>
	<title>Re:The Best Thing To Do</title>
	<author>Anonymous</author>
	<datestamp>1243966320000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p><div class="quote"><p>As for the keyboard itself, seems I've seen that in some si-fi movie.</p></div><p>The new term is <b> <a href="http://syfy.com/" title="syfy.com" rel="nofollow">SyFy</a> [syfy.com] </b>.</p></div>
	</htmltext>
<tokenext>As for the keyboard itself , seems I 've seen that in some si-fi movie.The new term is SyFy [ syfy.com ] .</tokentext>
<sentencetext>As for the keyboard itself, seems I've seen that in some si-fi movie.The new term is  SyFy [syfy.com] .
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28200665</id>
	<title>In theory</title>
	<author>z0mbie byte</author>
	<datestamp>1244021460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Baker told Register Hardware today that each triangular key has significantly more dead space around it than you&#195;(TM)d find on a standard Qwerty layout. Consequently, users are more likely to press the correct key each time they tap.</p></div><p>So, if the keys were tiny little dots, in theory, less spelling errors?
wtf.</p></div>
	</htmltext>
<tokenext>Baker told Register Hardware today that each triangular key has significantly more dead space around it than you   ( TM ) d find on a standard Qwerty layout .
Consequently , users are more likely to press the correct key each time they tap.So , if the keys were tiny little dots , in theory , less spelling errors ?
wtf .</tokentext>
<sentencetext>Baker told Register Hardware today that each triangular key has significantly more dead space around it than youÃ(TM)d find on a standard Qwerty layout.
Consequently, users are more likely to press the correct key each time they tap.So, if the keys were tiny little dots, in theory, less spelling errors?
wtf.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184895</id>
	<title>Klingon Keyboard?</title>
	<author>Anonymous</author>
	<datestamp>1243967820000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>This reminds me of the klingon displays from startrek</htmltext>
<tokenext>This reminds me of the klingon displays from startrek</tokentext>
<sentencetext>This reminds me of the klingon displays from startrek</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186611</id>
	<title>Re:For the iPhone, doesn't make sense</title>
	<author>Anonymous</author>
	<datestamp>1243975260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Yep,for iphone there are more usefull solutions like fastmail app.</p></htmltext>
<tokenext>Yep,for iphone there are more usefull solutions like fastmail app .</tokentext>
<sentencetext>Yep,for iphone there are more usefull solutions like fastmail app.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184999</id>
	<title>How about no shape?</title>
	<author>Anonymous</author>
	<datestamp>1243968240000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Lay out the letters.  Don't put a border around it.  It's a touchscreen keyboard, so unless you embed something similar to a digital braille printer to it, I don't see the point in making virtual keys into any shape.</p></htmltext>
<tokenext>Lay out the letters .
Do n't put a border around it .
It 's a touchscreen keyboard , so unless you embed something similar to a digital braille printer to it , I do n't see the point in making virtual keys into any shape .</tokentext>
<sentencetext>Lay out the letters.
Don't put a border around it.
It's a touchscreen keyboard, so unless you embed something similar to a digital braille printer to it, I don't see the point in making virtual keys into any shape.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28193219</id>
	<title>Re:Sceptical</title>
	<author>Anonymous</author>
	<datestamp>1244023980000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>We will NEVER spell the end for accidental use of technology by using more technology.</p></div><p>Well, we would be able to spell it, if only we wouldn't keep making all these typos.</p></div>
	</htmltext>
<tokenext>We will NEVER spell the end for accidental use of technology by using more technology.Well , we would be able to spell it , if only we would n't keep making all these typos .</tokentext>
<sentencetext>We will NEVER spell the end for accidental use of technology by using more technology.Well, we would be able to spell it, if only we wouldn't keep making all these typos.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184947</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185207</id>
	<title>Re:The Best Thing To Do</title>
	<author>Anonymous</author>
	<datestamp>1243969080000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>How do you shout without a caps lock key?</p></htmltext>
<tokenext>How do you shout without a caps lock key ?</tokentext>
<sentencetext>How do you shout without a caps lock key?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28187899</id>
	<title>Kinda obvious, isn't it?</title>
	<author>rsmith</author>
	<datestamp>1243937280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The core of this invention seems to be that an on-screen keyboard with more space between the keys leads to less typing errors.</p><p>Well, duh!</p><p>&lt;sarcasm&gt;</p><p>I've got an "invention" too! (written in English, because I don't speak Patentese):</p><ol> <li>A keyboard where the width and height of every key is at least as large as the diameter of an average human finger.</li><li>The horizontal and vertical distance between keys is half the width or height respectively.</li></ol><p>&lt;/sarcasm&gt;</p></htmltext>
<tokenext>The core of this invention seems to be that an on-screen keyboard with more space between the keys leads to less typing errors.Well , duh ! I 've got an " invention " too !
( written in English , because I do n't speak Patentese ) : A keyboard where the width and height of every key is at least as large as the diameter of an average human finger.The horizontal and vertical distance between keys is half the width or height respectively .</tokentext>
<sentencetext>The core of this invention seems to be that an on-screen keyboard with more space between the keys leads to less typing errors.Well, duh!I've got an "invention" too!
(written in English, because I don't speak Patentese): A keyboard where the width and height of every key is at least as large as the diameter of an average human finger.The horizontal and vertical distance between keys is half the width or height respectively.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184755</id>
	<title>Re:The Best Thing To Do</title>
	<author>Anonymous</author>
	<datestamp>1243967220000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p><div class="quote"><p>As someone who sues it</p></div><p>How exactly do you sue a keyboard key?</p></div>
	</htmltext>
<tokenext>As someone who sues itHow exactly do you sue a keyboard key ?</tokentext>
<sentencetext>As someone who sues itHow exactly do you sue a keyboard key?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184769</id>
	<title>Re:The Best Thing To Do</title>
	<author>MaerD</author>
	<datestamp>1243967220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>We would hate to remove your revenue stream by not allowing you to sue keys on the keyboard<nobr> <wbr></nobr>:)

<br> <br>
Seriously, I'd like a keyboard that reads my mind and knows what I'm typing... although it would fail miserably in high-schools across the country.</htmltext>
<tokenext>We would hate to remove your revenue stream by not allowing you to sue keys on the keyboard : ) Seriously , I 'd like a keyboard that reads my mind and knows what I 'm typing... although it would fail miserably in high-schools across the country .</tokentext>
<sentencetext>We would hate to remove your revenue stream by not allowing you to sue keys on the keyboard :)

 
Seriously, I'd like a keyboard that reads my mind and knows what I'm typing... although it would fail miserably in high-schools across the country.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185159</id>
	<title>Lazy programmer</title>
	<author>Guysmiley777</author>
	<datestamp>1243968840000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>Interesting idea until a lazy programmer decides that detecting a triangular shaped area from a set of coordinates is too fussy and just divides the key areas up into boxes.</htmltext>
<tokenext>Interesting idea until a lazy programmer decides that detecting a triangular shaped area from a set of coordinates is too fussy and just divides the key areas up into boxes .</tokentext>
<sentencetext>Interesting idea until a lazy programmer decides that detecting a triangular shaped area from a set of coordinates is too fussy and just divides the key areas up into boxes.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28190811</id>
	<title>Re:With all that space between keys...</title>
	<author>ozbird</author>
	<datestamp>1243954380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>With all that space between the keys, there's room for even more buttons!</p></div></blockquote><p>A SHIFT KEY WOULD BE NICE</p></div>
	</htmltext>
<tokenext>With all that space between the keys , there 's room for even more buttons ! A SHIFT KEY WOULD BE NICE</tokentext>
<sentencetext>With all that space between the keys, there's room for even more buttons!A SHIFT KEY WOULD BE NICE
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184857</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184745</id>
	<title>For the iPhone, doesn't make sense</title>
	<author>Chris Pimlott</author>
	<datestamp>1243967160000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>For a physical keyboard, this seems reasonable - if you eliminate edges where the keys touch, each other, then you're less likely to accidentally press two keys at once.  But for a virtual keyboard like on the iPod, it doesn't matter if you "touch" two keys at once with your finger - the software can determine which one you were actually closer to, and only register that.</p><p>While there are certainly drawbacks to a touchscreen, such as lack of tactile feedback, this is one area where they have an advantage - a larger percentage of usuable surface area, as touches that would be a multiple button mash on physical keyboards can be unambiguously mapped to a single key in software.</p></htmltext>
<tokenext>For a physical keyboard , this seems reasonable - if you eliminate edges where the keys touch , each other , then you 're less likely to accidentally press two keys at once .
But for a virtual keyboard like on the iPod , it does n't matter if you " touch " two keys at once with your finger - the software can determine which one you were actually closer to , and only register that.While there are certainly drawbacks to a touchscreen , such as lack of tactile feedback , this is one area where they have an advantage - a larger percentage of usuable surface area , as touches that would be a multiple button mash on physical keyboards can be unambiguously mapped to a single key in software .</tokentext>
<sentencetext>For a physical keyboard, this seems reasonable - if you eliminate edges where the keys touch, each other, then you're less likely to accidentally press two keys at once.
But for a virtual keyboard like on the iPod, it doesn't matter if you "touch" two keys at once with your finger - the software can determine which one you were actually closer to, and only register that.While there are certainly drawbacks to a touchscreen, such as lack of tactile feedback, this is one area where they have an advantage - a larger percentage of usuable surface area, as touches that would be a multiple button mash on physical keyboards can be unambiguously mapped to a single key in software.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186265</id>
	<title>Re:The Best Thing To Do</title>
	<author>Anonymous</author>
	<datestamp>1243973820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Most lawyers these days are crazy in regards to what they're willing to litigate. They don't give a darn as to how valid the suit is, as long as there's enough money involved. They're greedy like that.</p><p>He might have a <i>case</i>, but I'm not sure if it merits <i>capital</i> <i>pun</i>ishment.</p><p>In regards to the main article: How long will it be before someone does what looks like a standard staggered QWERTY, but makes the hit detection areas into the same triangles without being visibly so? And how would anyone really know? (Seems like the design patent would be a little flawed in that regard.)</p></htmltext>
<tokenext>Most lawyers these days are crazy in regards to what they 're willing to litigate .
They do n't give a darn as to how valid the suit is , as long as there 's enough money involved .
They 're greedy like that.He might have a case , but I 'm not sure if it merits capital punishment.In regards to the main article : How long will it be before someone does what looks like a standard staggered QWERTY , but makes the hit detection areas into the same triangles without being visibly so ?
And how would anyone really know ?
( Seems like the design patent would be a little flawed in that regard .
)</tokentext>
<sentencetext>Most lawyers these days are crazy in regards to what they're willing to litigate.
They don't give a darn as to how valid the suit is, as long as there's enough money involved.
They're greedy like that.He might have a case, but I'm not sure if it merits capital punishment.In regards to the main article: How long will it be before someone does what looks like a standard staggered QWERTY, but makes the hit detection areas into the same triangles without being visibly so?
And how would anyone really know?
(Seems like the design patent would be a little flawed in that regard.
)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184755</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186787
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186265
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184755
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186821
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184707
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184535
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185165
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184755
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185385
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28187389
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184769
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185119
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184773
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28190271
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184895
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28193219
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184947
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186241
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184913
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184769
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186239
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184855
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186345
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184781
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186365
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185051
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186611
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184745
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185241
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184697
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185465
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184833
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185853
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184605
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185695
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185305
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186773
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184895
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28198111
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185681
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28190811
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184857
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184891
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185951
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185301
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28196995
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184421
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28198071
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188723
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185181
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186107
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184895
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184935
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28190081
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186001
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184745
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28192669
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188227
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185359
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184745
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186579
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185457
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186681
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185207
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188165
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185139
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_02_1647213_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186515
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185181
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184563
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28198111
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186241
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186239
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185051
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186365
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184891
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185457
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186579
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184565
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185115
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184425
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184535
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184707
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184569
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28198071
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185691
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185139
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188165
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185241
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185681
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184935
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184825
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188227
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186787
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186821
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28190081
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28192669
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184697
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184773
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184855
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184605
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184621
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184769
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28187389
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184913
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185207
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186681
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185119
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185301
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185951
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184755
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186265
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185165
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184917
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184833
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185465
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184895
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28190271
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186107
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186773
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28190683
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188919
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185159
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184947
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28193219
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185181
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28188723
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186515
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185305
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185695
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184911
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185385
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185853
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184421
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28196995
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184781
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186345
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184745
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186611
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28185359
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28186001
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_02_1647213.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28184857
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_02_1647213.28190811
</commentlist>
</conversation>
