<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article10_01_11_1411200</id>
	<title>Droid Touchscreen Less Accurate Than iPhone's</title>
	<author>CmdrTaco</author>
	<datestamp>1263220800000</datestamp>
	<htmltext>gyrogeerloose writes <i>"A test published by MOTO labs <a href="http://labs.moto.com/diy-touchscreen-analysis/">comparing the accuracy and sensitivity of smartphone touchscreens</a> among various makers gave the iPhone top marks ahead of HTC's Droid Eris, the Google-branded Nexus One and the Motorola Droid. The test was conducted within a drawing program using a finger to trace straight diagonal lines across the screens and then comparing the results. While it's not likely that a smart phone user is going to draw a lot of lines, the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser."</i></htmltext>
<tokenext>gyrogeerloose writes " A test published by MOTO labs comparing the accuracy and sensitivity of smartphone touchscreens among various makers gave the iPhone top marks ahead of HTC 's Droid Eris , the Google-branded Nexus One and the Motorola Droid .
The test was conducted within a drawing program using a finger to trace straight diagonal lines across the screens and then comparing the results .
While it 's not likely that a smart phone user is going to draw a lot of lines , the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser .
"</tokentext>
<sentencetext>gyrogeerloose writes "A test published by MOTO labs comparing the accuracy and sensitivity of smartphone touchscreens among various makers gave the iPhone top marks ahead of HTC's Droid Eris, the Google-branded Nexus One and the Motorola Droid.
The test was conducted within a drawing program using a finger to trace straight diagonal lines across the screens and then comparing the results.
While it's not likely that a smart phone user is going to draw a lot of lines, the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724090</id>
	<title>Well..</title>
	<author>demonlapin</author>
	<datestamp>1263230040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Software &gt;&gt; hardware.<br> <br>  I have a Droid. The browser always seems to click the wrong link - usually too low.  The Android keyboard was marginal. The HTC keyboard was better. Swype is perfect.  Most of the other apps are pretty accurate.  I downloaded a drawing app and got nice straight lines.  Given the amount of effort Apple put into the iPhone OS, it's not surprising that they have a better UI.  I wouldn't be surprised to find that the curvature at the edges of the iPhone screen is an intentional effect given the shape that fingers assume when they get to the edge of the screen.</htmltext>
<tokenext>Software &gt; &gt; hardware .
I have a Droid .
The browser always seems to click the wrong link - usually too low .
The Android keyboard was marginal .
The HTC keyboard was better .
Swype is perfect .
Most of the other apps are pretty accurate .
I downloaded a drawing app and got nice straight lines .
Given the amount of effort Apple put into the iPhone OS , it 's not surprising that they have a better UI .
I would n't be surprised to find that the curvature at the edges of the iPhone screen is an intentional effect given the shape that fingers assume when they get to the edge of the screen .</tokentext>
<sentencetext>Software &gt;&gt; hardware.
I have a Droid.
The browser always seems to click the wrong link - usually too low.
The Android keyboard was marginal.
The HTC keyboard was better.
Swype is perfect.
Most of the other apps are pretty accurate.
I downloaded a drawing app and got nice straight lines.
Given the amount of effort Apple put into the iPhone OS, it's not surprising that they have a better UI.
I wouldn't be surprised to find that the curvature at the edges of the iPhone screen is an intentional effect given the shape that fingers assume when they get to the edge of the screen.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723604</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>psm321</author>
	<datestamp>1263227700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I know my MyTouch 3G also has poor detection along the edges... hitting the keys on the far left or right of the virtual keyboard is much harder than those in the center.  That's one application where there are UI elements right at the edge.</p></htmltext>
<tokenext>I know my MyTouch 3G also has poor detection along the edges... hitting the keys on the far left or right of the virtual keyboard is much harder than those in the center .
That 's one application where there are UI elements right at the edge .</tokentext>
<sentencetext>I know my MyTouch 3G also has poor detection along the edges... hitting the keys on the far left or right of the virtual keyboard is much harder than those in the center.
That's one application where there are UI elements right at the edge.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723190</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723518</id>
	<title>Re:Well of course drawing lines is important</title>
	<author>MBGMorden</author>
	<datestamp>1263227280000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>This is my biggest problem with my phone (a Moto Krave ZN4).  I already had an iPod Touch, so figured "Hey, this touch screen thing is pretty cool. - I'll get one for my phone.".  Didn't work out so great.  While I can type away just fine on the iPod (I've started leaving my laptop home most of the time now since if I'm near a hotspot my iPod Touch does 98\% of what I want to do on a laptop), on the Krave trying to do a text message on the onscreen QWERTY keyboard is just painful.  Try to press one key - it registers the one beside it. Try to hit backspace.  It registers a letter instead.  Finally backspace across the two bad letters.  Ok, now CAREFULLY try to press the letter I want.  Nope, grabs the key beside it again.  Not to mention the contacts list.  I've just gotten used to apologizing to people because half the time when I tap a contact to call it calls the person next to them.  This was particularly embarrassing when I was trying to call my brother at 4am over Christmas break because he overslept to go duck hunting - it the phone dialed one of the department directors at work which happens to be right next time him.  After that I started prefixing all work contacts with #'s just so they'd stay away from my personal contacts on the list.</p><p>I'm not buying another touch screen phone now without testing it in person first to make sure it feels right.</p><p>PS Yes, I know the obvious answer would be to just get an iPhone but AT&amp;T nor any other GSM carrier gets signal where I live.</p></htmltext>
<tokenext>This is my biggest problem with my phone ( a Moto Krave ZN4 ) .
I already had an iPod Touch , so figured " Hey , this touch screen thing is pretty cool .
- I 'll get one for my phone. " .
Did n't work out so great .
While I can type away just fine on the iPod ( I 've started leaving my laptop home most of the time now since if I 'm near a hotspot my iPod Touch does 98 \ % of what I want to do on a laptop ) , on the Krave trying to do a text message on the onscreen QWERTY keyboard is just painful .
Try to press one key - it registers the one beside it .
Try to hit backspace .
It registers a letter instead .
Finally backspace across the two bad letters .
Ok , now CAREFULLY try to press the letter I want .
Nope , grabs the key beside it again .
Not to mention the contacts list .
I 've just gotten used to apologizing to people because half the time when I tap a contact to call it calls the person next to them .
This was particularly embarrassing when I was trying to call my brother at 4am over Christmas break because he overslept to go duck hunting - it the phone dialed one of the department directors at work which happens to be right next time him .
After that I started prefixing all work contacts with # 's just so they 'd stay away from my personal contacts on the list.I 'm not buying another touch screen phone now without testing it in person first to make sure it feels right.PS Yes , I know the obvious answer would be to just get an iPhone but AT&amp;T nor any other GSM carrier gets signal where I live .</tokentext>
<sentencetext>This is my biggest problem with my phone (a Moto Krave ZN4).
I already had an iPod Touch, so figured "Hey, this touch screen thing is pretty cool.
- I'll get one for my phone.".
Didn't work out so great.
While I can type away just fine on the iPod (I've started leaving my laptop home most of the time now since if I'm near a hotspot my iPod Touch does 98\% of what I want to do on a laptop), on the Krave trying to do a text message on the onscreen QWERTY keyboard is just painful.
Try to press one key - it registers the one beside it.
Try to hit backspace.
It registers a letter instead.
Finally backspace across the two bad letters.
Ok, now CAREFULLY try to press the letter I want.
Nope, grabs the key beside it again.
Not to mention the contacts list.
I've just gotten used to apologizing to people because half the time when I tap a contact to call it calls the person next to them.
This was particularly embarrassing when I was trying to call my brother at 4am over Christmas break because he overslept to go duck hunting - it the phone dialed one of the department directors at work which happens to be right next time him.
After that I started prefixing all work contacts with #'s just so they'd stay away from my personal contacts on the list.I'm not buying another touch screen phone now without testing it in person first to make sure it feels right.PS Yes, I know the obvious answer would be to just get an iPhone but AT&amp;T nor any other GSM carrier gets signal where I live.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723062</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723928</id>
	<title>Re:Silly test results...</title>
	<author>demonlapin</author>
	<datestamp>1263229200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It appears to be app-dependent. My Droid always seems to click just below where I touch on web pages, but the painting app I downloaded could draw very, very straight lines.  The pinch-zoom browser from the Milestone has helped, and the leaked Swype beta is perfect.</htmltext>
<tokenext>It appears to be app-dependent .
My Droid always seems to click just below where I touch on web pages , but the painting app I downloaded could draw very , very straight lines .
The pinch-zoom browser from the Milestone has helped , and the leaked Swype beta is perfect .</tokentext>
<sentencetext>It appears to be app-dependent.
My Droid always seems to click just below where I touch on web pages, but the painting app I downloaded could draw very, very straight lines.
The pinch-zoom browser from the Milestone has helped, and the leaked Swype beta is perfect.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723502</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30737196</id>
	<title>Re:Ah, groupthink</title>
	<author>mdwh2</author>
	<datestamp>1263312060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>we'd have had a flurry of posts talking about how the iPhone is an overpriced and inferior option.</i></p><p>To be fair, we'd have a flurry of posts dismissing the article as "grumpy featurism" or handwaving it away with "it doesn't matter it looks bad in a test, you have to use it to see how it's better".</p><p>Posts like yours a reasonable, but we never seem to have these honest admissions about Iphone flaws any other time...</p></htmltext>
<tokenext>we 'd have had a flurry of posts talking about how the iPhone is an overpriced and inferior option.To be fair , we 'd have a flurry of posts dismissing the article as " grumpy featurism " or handwaving it away with " it does n't matter it looks bad in a test , you have to use it to see how it 's better " .Posts like yours a reasonable , but we never seem to have these honest admissions about Iphone flaws any other time.. .</tokentext>
<sentencetext>we'd have had a flurry of posts talking about how the iPhone is an overpriced and inferior option.To be fair, we'd have a flurry of posts dismissing the article as "grumpy featurism" or handwaving it away with "it doesn't matter it looks bad in a test, you have to use it to see how it's better".Posts like yours a reasonable, but we never seem to have these honest admissions about Iphone flaws any other time...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724564</id>
	<title>Re:Silly test results...</title>
	<author>kannibal\_klown</author>
	<datestamp>1263232380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>"While it's not likely that a smart phone user is going to draw a lot of lines, the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser."  I don't suppose they considered instead testing which phones properly respond to clicking on links in Web browsers?</p></div><p>That's harder to test reliably.</p><p>Is the user used to a particular device?  I'm noticing different systems have different learning curves for aiming.</p><p>I'm used to my iPhone 3Gs that I got at release.  It took a few days to get accustomed to typing/licking but afterward I was able to use that like a champ.  I have big fingers, but once I learned where to click I can click on even small web links.</p><p>Recently I tried using a Nexus One and I'm kind of starting at square one such as when I first tried the iPhone.  Using my "iPhone training" it looks like I'm aiming a little off on the y-axis.  If I try clicking a link, I'm actually clicking the link above it.</p><p>Plus with the used method you're at least focusing on the phone itself, all-be-it a mix of hardware and painting application.  Going your suggested way, the human factor winds up being too much of a variable.</p><p>There are other things that would make it difficult that I don't feel like listing, or can't even think of.</p><p>In short, this test could've been done in a more scientific way.  But simply saying "have someone try clicking on links and typing between the different machines" isn't much better than what they posted.  At least here they demonstrated the tracking</p></div>
	</htmltext>
<tokenext>" While it 's not likely that a smart phone user is going to draw a lot of lines , the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser .
" I do n't suppose they considered instead testing which phones properly respond to clicking on links in Web browsers ? That 's harder to test reliably.Is the user used to a particular device ?
I 'm noticing different systems have different learning curves for aiming.I 'm used to my iPhone 3Gs that I got at release .
It took a few days to get accustomed to typing/licking but afterward I was able to use that like a champ .
I have big fingers , but once I learned where to click I can click on even small web links.Recently I tried using a Nexus One and I 'm kind of starting at square one such as when I first tried the iPhone .
Using my " iPhone training " it looks like I 'm aiming a little off on the y-axis .
If I try clicking a link , I 'm actually clicking the link above it.Plus with the used method you 're at least focusing on the phone itself , all-be-it a mix of hardware and painting application .
Going your suggested way , the human factor winds up being too much of a variable.There are other things that would make it difficult that I do n't feel like listing , or ca n't even think of.In short , this test could 've been done in a more scientific way .
But simply saying " have someone try clicking on links and typing between the different machines " is n't much better than what they posted .
At least here they demonstrated the tracking</tokentext>
<sentencetext>"While it's not likely that a smart phone user is going to draw a lot of lines, the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser.
"  I don't suppose they considered instead testing which phones properly respond to clicking on links in Web browsers?That's harder to test reliably.Is the user used to a particular device?
I'm noticing different systems have different learning curves for aiming.I'm used to my iPhone 3Gs that I got at release.
It took a few days to get accustomed to typing/licking but afterward I was able to use that like a champ.
I have big fingers, but once I learned where to click I can click on even small web links.Recently I tried using a Nexus One and I'm kind of starting at square one such as when I first tried the iPhone.
Using my "iPhone training" it looks like I'm aiming a little off on the y-axis.
If I try clicking a link, I'm actually clicking the link above it.Plus with the used method you're at least focusing on the phone itself, all-be-it a mix of hardware and painting application.
Going your suggested way, the human factor winds up being too much of a variable.There are other things that would make it difficult that I don't feel like listing, or can't even think of.In short, this test could've been done in a more scientific way.
But simply saying "have someone try clicking on links and typing between the different machines" isn't much better than what they posted.
At least here they demonstrated the tracking
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723502</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30737074</id>
	<title>Re:Ah, groupthink</title>
	<author>mdwh2</author>
	<datestamp>1263311640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The problem is more that we have an article everytime there's something that shows the Iphone come out top compared with a hand picked selection of competitors - yet we never seem to have articles that point out the ways that other phones do better, such as the things you list (I was astonished when I heard about copy/paste - surely it's meant to be a smart phone? Even non-smart phones can do that), or any other area they do better.</p><p><i>why don't you just admit that it has a flaw and deal with it</i></p><p>Well indeed, we could just copy and paste (if you're able) the standard boilerplate reponse for any Iphone criticisms: "It doesn't matter that my phone doesn't look as good <i>on paper</i>, it still works better, even though I can't explain why". If necessary, dismiss the claims in this article as "grumpy featurism".</p></htmltext>
<tokenext>The problem is more that we have an article everytime there 's something that shows the Iphone come out top compared with a hand picked selection of competitors - yet we never seem to have articles that point out the ways that other phones do better , such as the things you list ( I was astonished when I heard about copy/paste - surely it 's meant to be a smart phone ?
Even non-smart phones can do that ) , or any other area they do better.why do n't you just admit that it has a flaw and deal with itWell indeed , we could just copy and paste ( if you 're able ) the standard boilerplate reponse for any Iphone criticisms : " It does n't matter that my phone does n't look as good on paper , it still works better , even though I ca n't explain why " .
If necessary , dismiss the claims in this article as " grumpy featurism " .</tokentext>
<sentencetext>The problem is more that we have an article everytime there's something that shows the Iphone come out top compared with a hand picked selection of competitors - yet we never seem to have articles that point out the ways that other phones do better, such as the things you list (I was astonished when I heard about copy/paste - surely it's meant to be a smart phone?
Even non-smart phones can do that), or any other area they do better.why don't you just admit that it has a flaw and deal with itWell indeed, we could just copy and paste (if you're able) the standard boilerplate reponse for any Iphone criticisms: "It doesn't matter that my phone doesn't look as good on paper, it still works better, even though I can't explain why".
If necessary, dismiss the claims in this article as "grumpy featurism".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724918</id>
	<title>Higher accuracy causes jaggies</title>
	<author>Anonymous</author>
	<datestamp>1263233640000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>If you up the accuracy of an input device in time and space, you end up with jaggies, because your finger/mouse/etc didn't smoothly travel over the surface.</p><p>Drawing software compensates for this by "smoothing" out arcs, and not paying attention to every location the input device feeds them.  It guesses that you really didn't mean (1,1), (1,2), (2,2), but rather meant (1,1), (2,2), with the (1,2) being an artefact of sampling at a rate higher than the user's intentions.</p><p>In short, a complete lack of waviness makes me doubt that the interface is actually displaying what the finger did.  Even the breaks in the line might happen because the user actually did lift their finger up when crossing the screen.  The pad can "lie" and pretend "that wasn't really leaving the screen", or "they didn't intend to be all wavey".</p><p>As an amusing side effect, the inability to have bracketing points to interpolate around would cause the points near the 'end' of the arc to act strangely... which is exactly what the apple iPhone images do.</p><p>My theory that it isn't as much the quality of the touch screen, as it is the higher degree of post-processing going on.  This might be in the iPhone software, or in the software of the application in question.</p></htmltext>
<tokenext>If you up the accuracy of an input device in time and space , you end up with jaggies , because your finger/mouse/etc did n't smoothly travel over the surface.Drawing software compensates for this by " smoothing " out arcs , and not paying attention to every location the input device feeds them .
It guesses that you really did n't mean ( 1,1 ) , ( 1,2 ) , ( 2,2 ) , but rather meant ( 1,1 ) , ( 2,2 ) , with the ( 1,2 ) being an artefact of sampling at a rate higher than the user 's intentions.In short , a complete lack of waviness makes me doubt that the interface is actually displaying what the finger did .
Even the breaks in the line might happen because the user actually did lift their finger up when crossing the screen .
The pad can " lie " and pretend " that was n't really leaving the screen " , or " they did n't intend to be all wavey " .As an amusing side effect , the inability to have bracketing points to interpolate around would cause the points near the 'end ' of the arc to act strangely... which is exactly what the apple iPhone images do.My theory that it is n't as much the quality of the touch screen , as it is the higher degree of post-processing going on .
This might be in the iPhone software , or in the software of the application in question .</tokentext>
<sentencetext>If you up the accuracy of an input device in time and space, you end up with jaggies, because your finger/mouse/etc didn't smoothly travel over the surface.Drawing software compensates for this by "smoothing" out arcs, and not paying attention to every location the input device feeds them.
It guesses that you really didn't mean (1,1), (1,2), (2,2), but rather meant (1,1), (2,2), with the (1,2) being an artefact of sampling at a rate higher than the user's intentions.In short, a complete lack of waviness makes me doubt that the interface is actually displaying what the finger did.
Even the breaks in the line might happen because the user actually did lift their finger up when crossing the screen.
The pad can "lie" and pretend "that wasn't really leaving the screen", or "they didn't intend to be all wavey".As an amusing side effect, the inability to have bracketing points to interpolate around would cause the points near the 'end' of the arc to act strangely... which is exactly what the apple iPhone images do.My theory that it isn't as much the quality of the touch screen, as it is the higher degree of post-processing going on.
This might be in the iPhone software, or in the software of the application in question.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724100</id>
	<title>Obviously inferior!</title>
	<author>Anonymous</author>
	<datestamp>1263230040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Because drawing programs are the 'killer ap' for smart phones.</p></htmltext>
<tokenext>Because drawing programs are the 'killer ap ' for smart phones .</tokentext>
<sentencetext>Because drawing programs are the 'killer ap' for smart phones.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30729722</id>
	<title>Droid touchsceen only sucks with screen protector</title>
	<author>Zymophideth</author>
	<datestamp>1263208140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I have the droid and the touchscreen was awesome until I put their surprisingly thick screen protector on. Sensitivity is much worse and sometimes it feels like there are "dead" spots on the screen. I'd prefer a thinner DS style screen protector.</htmltext>
<tokenext>I have the droid and the touchscreen was awesome until I put their surprisingly thick screen protector on .
Sensitivity is much worse and sometimes it feels like there are " dead " spots on the screen .
I 'd prefer a thinner DS style screen protector .</tokentext>
<sentencetext>I have the droid and the touchscreen was awesome until I put their surprisingly thick screen protector on.
Sensitivity is much worse and sometimes it feels like there are "dead" spots on the screen.
I'd prefer a thinner DS style screen protector.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725836</id>
	<title>Re:Ah, groupthink</title>
	<author>radish</author>
	<datestamp>1263237300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>annoyance that you have to manually disable wifi if are trying to use 3G in an area with a hotspot</p></div></blockquote><p>You can disable the auto-join for unknown networks, then it will only switch to Wifi if it sees a network you already have configured.</p></div>
	</htmltext>
<tokenext>annoyance that you have to manually disable wifi if are trying to use 3G in an area with a hotspotYou can disable the auto-join for unknown networks , then it will only switch to Wifi if it sees a network you already have configured .</tokentext>
<sentencetext>annoyance that you have to manually disable wifi if are trying to use 3G in an area with a hotspotYou can disable the auto-join for unknown networks, then it will only switch to Wifi if it sees a network you already have configured.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723270</id>
	<title>haha</title>
	<author>Anonymous</author>
	<datestamp>1263225960000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Any win for Apple provokes this knee-jerk reaction on slashdot. You guys never fail to conform.</p></htmltext>
<tokenext>Any win for Apple provokes this knee-jerk reaction on slashdot .
You guys never fail to conform .</tokentext>
<sentencetext>Any win for Apple provokes this knee-jerk reaction on slashdot.
You guys never fail to conform.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727412</id>
	<title>Re:Ah, groupthink</title>
	<author>sootman</author>
	<datestamp>1263243300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>&gt; It seems like droid users are just as zealous about their phones as they accuse iPhone users of being.</p><p>The only thing worse than fanbois are haters.</p></htmltext>
<tokenext>&gt; It seems like droid users are just as zealous about their phones as they accuse iPhone users of being.The only thing worse than fanbois are haters .</tokentext>
<sentencetext>&gt; It seems like droid users are just as zealous about their phones as they accuse iPhone users of being.The only thing worse than fanbois are haters.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30728844</id>
	<title>Re:Used "a program" ?</title>
	<author>abhi\_beckert</author>
	<datestamp>1263204900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What "quality"? This is essentially the whole app:</p><p>oldPoint = getFingerPosition()<br>while (true and fingerTouchingScreen()) {<br>
&nbsp; &nbsp; point = getFingerPosition()<br>
&nbsp; &nbsp; drawLine(oldPoint, point)</p><p>
&nbsp; &nbsp; oldPoint = point;<br>}</p></htmltext>
<tokenext>What " quality " ?
This is essentially the whole app : oldPoint = getFingerPosition ( ) while ( true and fingerTouchingScreen ( ) ) {     point = getFingerPosition ( )     drawLine ( oldPoint , point )     oldPoint = point ; }</tokentext>
<sentencetext>What "quality"?
This is essentially the whole app:oldPoint = getFingerPosition()while (true and fingerTouchingScreen()) {
    point = getFingerPosition()
    drawLine(oldPoint, point)
    oldPoint = point;}</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723058</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724222</id>
	<title>A Little Disappointing</title>
	<author>noc007</author>
	<datestamp>1263230760000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>The legitimacy or how real world it applies aside, I'm disappointed with Motorola on this one. The Droid is an expensive device from a brand name manufacturer made in 2009. I expect a level of build quality, feature set, and accuracy. For a capacitance touch screen released in 2009, I would expect a level of accuracy that's at least comparable to the last generation of the iPhone, not accuracy that's poorer than a first gen iPhone.</p><p>Coming from resistive touchscreens on Windows Mobile and Palm devices and the device in general, I am overall pretty happy with my Droid. I do have inaccuracies from time to time, but it's ok. Using the onscreen keyboard has been pretty accurate; most of my errors I have attributed to my finger being in the wrong place. Sadly, this is another weapon for the annoying Apple fanboy; pissing contests are annoying and the constant Apple fanboy counter argument of being about to talk and do data at the same time is getting really old and doesn't apply to how I generally use the device.</p></htmltext>
<tokenext>The legitimacy or how real world it applies aside , I 'm disappointed with Motorola on this one .
The Droid is an expensive device from a brand name manufacturer made in 2009 .
I expect a level of build quality , feature set , and accuracy .
For a capacitance touch screen released in 2009 , I would expect a level of accuracy that 's at least comparable to the last generation of the iPhone , not accuracy that 's poorer than a first gen iPhone.Coming from resistive touchscreens on Windows Mobile and Palm devices and the device in general , I am overall pretty happy with my Droid .
I do have inaccuracies from time to time , but it 's ok. Using the onscreen keyboard has been pretty accurate ; most of my errors I have attributed to my finger being in the wrong place .
Sadly , this is another weapon for the annoying Apple fanboy ; pissing contests are annoying and the constant Apple fanboy counter argument of being about to talk and do data at the same time is getting really old and does n't apply to how I generally use the device .</tokentext>
<sentencetext>The legitimacy or how real world it applies aside, I'm disappointed with Motorola on this one.
The Droid is an expensive device from a brand name manufacturer made in 2009.
I expect a level of build quality, feature set, and accuracy.
For a capacitance touch screen released in 2009, I would expect a level of accuracy that's at least comparable to the last generation of the iPhone, not accuracy that's poorer than a first gen iPhone.Coming from resistive touchscreens on Windows Mobile and Palm devices and the device in general, I am overall pretty happy with my Droid.
I do have inaccuracies from time to time, but it's ok. Using the onscreen keyboard has been pretty accurate; most of my errors I have attributed to my finger being in the wrong place.
Sadly, this is another weapon for the annoying Apple fanboy; pissing contests are annoying and the constant Apple fanboy counter argument of being about to talk and do data at the same time is getting really old and doesn't apply to how I generally use the device.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723072</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>Anonymous</author>
	<datestamp>1263225060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>How would it NOT be fair to compare current phones to current phones?</p><p>I think future generations of the iPhone will make my [noun] [adjective]. Should we just go ahead and say it's a feature today?</p></htmltext>
<tokenext>How would it NOT be fair to compare current phones to current phones ? I think future generations of the iPhone will make my [ noun ] [ adjective ] .
Should we just go ahead and say it 's a feature today ?</tokentext>
<sentencetext>How would it NOT be fair to compare current phones to current phones?I think future generations of the iPhone will make my [noun] [adjective].
Should we just go ahead and say it's a feature today?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723168</id>
	<title>What's important</title>
	<author>electricbern</author>
	<datestamp>1263225540000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext>Although drawling lines might be important to some, what really matters to most smartphone users is how the phone responds to misclicks. Is it able to detect it and adjust accordingly? There is more to it then the accuracy of the screen. You are using your phone while standing or walking so even if the screen is 100\% accurate you probably won't be. What kind of correction algorithm the phone has to compensate for that?<br>
Of course creating a considerate test is too much trouble and just saying that the iPhone touchscreen is more accurate then Google's scores you plenty of apple-love.</htmltext>
<tokenext>Although drawling lines might be important to some , what really matters to most smartphone users is how the phone responds to misclicks .
Is it able to detect it and adjust accordingly ?
There is more to it then the accuracy of the screen .
You are using your phone while standing or walking so even if the screen is 100 \ % accurate you probably wo n't be .
What kind of correction algorithm the phone has to compensate for that ?
Of course creating a considerate test is too much trouble and just saying that the iPhone touchscreen is more accurate then Google 's scores you plenty of apple-love .</tokentext>
<sentencetext>Although drawling lines might be important to some, what really matters to most smartphone users is how the phone responds to misclicks.
Is it able to detect it and adjust accordingly?
There is more to it then the accuracy of the screen.
You are using your phone while standing or walking so even if the screen is 100\% accurate you probably won't be.
What kind of correction algorithm the phone has to compensate for that?
Of course creating a considerate test is too much trouble and just saying that the iPhone touchscreen is more accurate then Google's scores you plenty of apple-love.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723868</id>
	<title>Diminishing Returns</title>
	<author>stewbacca</author>
	<datestamp>1263228900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Much like the FPS discussion in video games from last week, there comes a point where being super-extra-accurate doesn't matter, and this is one of them.</p></htmltext>
<tokenext>Much like the FPS discussion in video games from last week , there comes a point where being super-extra-accurate does n't matter , and this is one of them .</tokentext>
<sentencetext>Much like the FPS discussion in video games from last week, there comes a point where being super-extra-accurate doesn't matter, and this is one of them.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723062</id>
	<title>Well of course drawing lines is important</title>
	<author>Anonymous</author>
	<datestamp>1263225060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>0</modscore>
	<htmltext><p>If you can't even draw a straight line, or the line is offset by a certain amount of pixels, the user is going to have a hell of a time clicking on links, presings tiny buttons, typing with an on-screen keyboard, etc, so not only would he have problems actually "drawing a picture" with his finger. This was actually a very good test.</p><p>I own an iPhone, and I can draw complex images with my finger, scrult a 3D sculpture with a particular program I have, and accurately type and click. I have nothing to compare it to but i know how accurate the iPhone is.</p></htmltext>
<tokenext>If you ca n't even draw a straight line , or the line is offset by a certain amount of pixels , the user is going to have a hell of a time clicking on links , presings tiny buttons , typing with an on-screen keyboard , etc , so not only would he have problems actually " drawing a picture " with his finger .
This was actually a very good test.I own an iPhone , and I can draw complex images with my finger , scrult a 3D sculpture with a particular program I have , and accurately type and click .
I have nothing to compare it to but i know how accurate the iPhone is .</tokentext>
<sentencetext>If you can't even draw a straight line, or the line is offset by a certain amount of pixels, the user is going to have a hell of a time clicking on links, presings tiny buttons, typing with an on-screen keyboard, etc, so not only would he have problems actually "drawing a picture" with his finger.
This was actually a very good test.I own an iPhone, and I can draw complex images with my finger, scrult a 3D sculpture with a particular program I have, and accurately type and click.
I have nothing to compare it to but i know how accurate the iPhone is.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725316</id>
	<title>Re:Silly test results...</title>
	<author>Lars T.</author>
	<datestamp>1263235140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>"Although we usually use sophisticated tools to test touch screen accuracy, MOTO has also developed a simple technique anyone can use to evaluate the resolution and accuracy of a touchscreen device. "<p>
No, I guess they didn't.</p></htmltext>
<tokenext>" Although we usually use sophisticated tools to test touch screen accuracy , MOTO has also developed a simple technique anyone can use to evaluate the resolution and accuracy of a touchscreen device .
" No , I guess they did n't .</tokentext>
<sentencetext>"Although we usually use sophisticated tools to test touch screen accuracy, MOTO has also developed a simple technique anyone can use to evaluate the resolution and accuracy of a touchscreen device.
"
No, I guess they didn't.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723502</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724180</id>
	<title>Different results from this guy</title>
	<author>Jeffrey Baker</author>
	<datestamp>1263230460000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>I don't have a droid so I can't confirm, but this flickr user seems to have replicated the test on the Droid with far different results:</p><p><a href="http://www.flickr.com/photos/42580856@N08/4264037413/" title="flickr.com">http://www.flickr.com/photos/42580856@N08/4264037413/</a> [flickr.com]</p></htmltext>
<tokenext>I do n't have a droid so I ca n't confirm , but this flickr user seems to have replicated the test on the Droid with far different results : http : //www.flickr.com/photos/42580856 @ N08/4264037413/ [ flickr.com ]</tokentext>
<sentencetext>I don't have a droid so I can't confirm, but this flickr user seems to have replicated the test on the Droid with far different results:http://www.flickr.com/photos/42580856@N08/4264037413/ [flickr.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724906</id>
	<title>The test is biased</title>
	<author>Anonymous</author>
	<datestamp>1263233580000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>[disclamer: i'm working in touch-screen business but not for apple/cellphone company]</p><p>This test is biased as:<br>- user perfomed, we use robot for this kind of qualification (but you can still get an overview if you use jigs)<br>- strait lines are not the best to see if some king of trajectory filtering is done by the OS: use curve lines, or corners (to see over/undershoot)<br>- to check if the border effect will affect the point perfomance, touch the screen at regularly spaced points (use a transparent plastic with dots printed on it)<br>- it would be interesting to get the raw data sent from the touch sensor to check sampling rate &amp; multi touch tracking (and thus removing, the OS and software filtering)</p><p>That said, when you are in front of a new touch sensor, the strait lines test on the border is a 'universal' benchmark performed by everyone in the field...</p><p>
&nbsp;</p></htmltext>
<tokenext>[ disclamer : i 'm working in touch-screen business but not for apple/cellphone company ] This test is biased as : - user perfomed , we use robot for this kind of qualification ( but you can still get an overview if you use jigs ) - strait lines are not the best to see if some king of trajectory filtering is done by the OS : use curve lines , or corners ( to see over/undershoot ) - to check if the border effect will affect the point perfomance , touch the screen at regularly spaced points ( use a transparent plastic with dots printed on it ) - it would be interesting to get the raw data sent from the touch sensor to check sampling rate &amp; multi touch tracking ( and thus removing , the OS and software filtering ) That said , when you are in front of a new touch sensor , the strait lines test on the border is a 'universal ' benchmark performed by everyone in the field.. .  </tokentext>
<sentencetext>[disclamer: i'm working in touch-screen business but not for apple/cellphone company]This test is biased as:- user perfomed, we use robot for this kind of qualification (but you can still get an overview if you use jigs)- strait lines are not the best to see if some king of trajectory filtering is done by the OS: use curve lines, or corners (to see over/undershoot)- to check if the border effect will affect the point perfomance, touch the screen at regularly spaced points (use a transparent plastic with dots printed on it)- it would be interesting to get the raw data sent from the touch sensor to check sampling rate &amp; multi touch tracking (and thus removing, the OS and software filtering)That said, when you are in front of a new touch sensor, the strait lines test on the border is a 'universal' benchmark performed by everyone in the field...
 </sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725644</id>
	<title>Re:Ah, groupthink</title>
	<author>WiiVault</author>
	<datestamp>1263236460000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>Yeah and look at the tags: applesucks and applefud. Both of which make no sense considering Apple has nothing to do with this outfit or its results, which happen to favor their "sucky" product. Hate Apple for all they shit they actually do, not just because they may have a slightly better touch accuracy on their phone.</htmltext>
<tokenext>Yeah and look at the tags : applesucks and applefud .
Both of which make no sense considering Apple has nothing to do with this outfit or its results , which happen to favor their " sucky " product .
Hate Apple for all they shit they actually do , not just because they may have a slightly better touch accuracy on their phone .</tokentext>
<sentencetext>Yeah and look at the tags: applesucks and applefud.
Both of which make no sense considering Apple has nothing to do with this outfit or its results, which happen to favor their "sucky" product.
Hate Apple for all they shit they actually do, not just because they may have a slightly better touch accuracy on their phone.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723192</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>Anonymous</author>
	<datestamp>1263225600000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p><div class="quote"><p>Is it fair to compare the third generation of a product to new products out there right away ?</p></div><p>Fairess isn't an issue. Consumers are presented with various options today. They need to compare them today. We don't have to be worried about hurting the poor phones' (or manufacturers') feelings with the unfairness of it all.</p></div>
	</htmltext>
<tokenext>Is it fair to compare the third generation of a product to new products out there right away ? Fairess is n't an issue .
Consumers are presented with various options today .
They need to compare them today .
We do n't have to be worried about hurting the poor phones ' ( or manufacturers ' ) feelings with the unfairness of it all .</tokentext>
<sentencetext>Is it fair to compare the third generation of a product to new products out there right away ?Fairess isn't an issue.
Consumers are presented with various options today.
They need to compare them today.
We don't have to be worried about hurting the poor phones' (or manufacturers') feelings with the unfairness of it all.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725218</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>Sloppy</author>
	<datestamp>1263234720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Is it fair to compare the third generation of a product to new products out there right away</p></div></blockquote><p>Yes, it's fair to compare a 2009 product to a 2009 product.</p></div>
	</htmltext>
<tokenext>Is it fair to compare the third generation of a product to new products out there right awayYes , it 's fair to compare a 2009 product to a 2009 product .</tokentext>
<sentencetext>Is it fair to compare the third generation of a product to new products out there right awayYes, it's fair to compare a 2009 product to a 2009 product.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30722978</id>
	<title>Obviously...</title>
	<author>Anonymous</author>
	<datestamp>1263224520000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>This is not the droid you're looking for.</p></htmltext>
<tokenext>This is not the droid you 're looking for .</tokentext>
<sentencetext>This is not the droid you're looking for.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723232</id>
	<title>Not sure why this is supposed to be a problem</title>
	<author>Anonymous</author>
	<datestamp>1263225840000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>I have a Droid and I just tried drawing diagonals in a paint program on the phone. Yes, I did get the waviness. All that means, though, is that the Droid is not a good choice for a phone if you want to draw on it. I am still able to use the on-screen keyboard just fine and even in a web browser I never have problems tapping a link no matter how far I am zoomed out. This is definitely not a deal-breaker for me. That said, the only reason why I have a Droid is because of the physical keyboard and a pretty decent free ssh client. The kids draw on it but they couldn't care less how straight the lines are or not.</htmltext>
<tokenext>I have a Droid and I just tried drawing diagonals in a paint program on the phone .
Yes , I did get the waviness .
All that means , though , is that the Droid is not a good choice for a phone if you want to draw on it .
I am still able to use the on-screen keyboard just fine and even in a web browser I never have problems tapping a link no matter how far I am zoomed out .
This is definitely not a deal-breaker for me .
That said , the only reason why I have a Droid is because of the physical keyboard and a pretty decent free ssh client .
The kids draw on it but they could n't care less how straight the lines are or not .</tokentext>
<sentencetext>I have a Droid and I just tried drawing diagonals in a paint program on the phone.
Yes, I did get the waviness.
All that means, though, is that the Droid is not a good choice for a phone if you want to draw on it.
I am still able to use the on-screen keyboard just fine and even in a web browser I never have problems tapping a link no matter how far I am zoomed out.
This is definitely not a deal-breaker for me.
That said, the only reason why I have a Droid is because of the physical keyboard and a pretty decent free ssh client.
The kids draw on it but they couldn't care less how straight the lines are or not.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723058</id>
	<title>Used "a program" ?</title>
	<author>Anonymous</author>
	<datestamp>1263225000000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>Was the program written to the same quality in all platforms? Or did they just slap together one quickly to get some juicy headline out? A more worthwhile test would be to go to the same websites in the same stock browsers and log the number of error clicks. Blah.</p></htmltext>
<tokenext>Was the program written to the same quality in all platforms ?
Or did they just slap together one quickly to get some juicy headline out ?
A more worthwhile test would be to go to the same websites in the same stock browsers and log the number of error clicks .
Blah .</tokentext>
<sentencetext>Was the program written to the same quality in all platforms?
Or did they just slap together one quickly to get some juicy headline out?
A more worthwhile test would be to go to the same websites in the same stock browsers and log the number of error clicks.
Blah.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876</id>
	<title>Re:Ah, groupthink</title>
	<author>jo\_ham</author>
	<datestamp>1263228900000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>I was thinking the exact same thing, and if the results had been reversed and the Droid had been on top, we'd have had a flurry of posts talking about how the iPhone is an overpriced and inferior option.</p><p>I also have issues with my iPhone (lack of built in MMS initially, lack of cut and paste until recently, annoyance that you still can't sync up your ToDo items from iCal with the built in calendar app and have to rely on third party apps, annoyance that you have to manually disable wifi if are trying to use 3G in an area with a hotspot, where it will try to use that wifi, even if you don't have a password for it, or its one of those web login ones).</p><p>What's wrong with saying "the droid's touch sensitivity is less effective than I'd like"? It seems like droid users are just as zealous about their phones as they accuse iPhone users of being.</p></htmltext>
<tokenext>I was thinking the exact same thing , and if the results had been reversed and the Droid had been on top , we 'd have had a flurry of posts talking about how the iPhone is an overpriced and inferior option.I also have issues with my iPhone ( lack of built in MMS initially , lack of cut and paste until recently , annoyance that you still ca n't sync up your ToDo items from iCal with the built in calendar app and have to rely on third party apps , annoyance that you have to manually disable wifi if are trying to use 3G in an area with a hotspot , where it will try to use that wifi , even if you do n't have a password for it , or its one of those web login ones ) .What 's wrong with saying " the droid 's touch sensitivity is less effective than I 'd like " ?
It seems like droid users are just as zealous about their phones as they accuse iPhone users of being .</tokentext>
<sentencetext>I was thinking the exact same thing, and if the results had been reversed and the Droid had been on top, we'd have had a flurry of posts talking about how the iPhone is an overpriced and inferior option.I also have issues with my iPhone (lack of built in MMS initially, lack of cut and paste until recently, annoyance that you still can't sync up your ToDo items from iCal with the built in calendar app and have to rely on third party apps, annoyance that you have to manually disable wifi if are trying to use 3G in an area with a hotspot, where it will try to use that wifi, even if you don't have a password for it, or its one of those web login ones).What's wrong with saying "the droid's touch sensitivity is less effective than I'd like"?
It seems like droid users are just as zealous about their phones as they accuse iPhone users of being.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723586</id>
	<title>Is this why the commercials show a robot using it?</title>
	<author>Lightborn</author>
	<datestamp>1263227580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Maybe they're letting us know that it requires more precision...</p></htmltext>
<tokenext>Maybe they 're letting us know that it requires more precision.. .</tokentext>
<sentencetext>Maybe they're letting us know that it requires more precision...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724256</id>
	<title>Couldn't repeat</title>
	<author>Anonymous</author>
	<datestamp>1263230940000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>First off, I have both a Droid and a 32GB iPod Touch.  Frankly, I like the touch on the Droid better than the iPod - I find it more responsive and more accurate when playing the same game or browsing the web on both devices.  It may just be my perception, but I simply find myself becoming less aggravated with the Droid's touch screen than the iPod's.<br> <br>While I don't have the iPod with me right now, I do have my Droid and was able to try this experiment.  I used an app called 'Simply Draw' and was not able to repeat their results.  Every time I try, I get lines that are as straight as my finger can make them.  I have yet to produce lines like those in the article no matter how hard I try - even using multi-touch to draw 2 lines at once works perfectly.<br> <br>One problem I have noticed with the Droid that may be the cause here is the touchscreen is very sensitive to noisy power supplies.  Using a cheap wall charger has a HUGE impact on the accuracy of the touch screen.  I'm guessing Motorola didn't use any ferrites on the USB signals, allowing high frequency noise from an external supply to negatively impact the device.  I suspect placing a ferrite on the USB cable near the phone end would minimize this issue, but have yet to try it myself.  Instead, I just use quality chargers.</htmltext>
<tokenext>First off , I have both a Droid and a 32GB iPod Touch .
Frankly , I like the touch on the Droid better than the iPod - I find it more responsive and more accurate when playing the same game or browsing the web on both devices .
It may just be my perception , but I simply find myself becoming less aggravated with the Droid 's touch screen than the iPod 's .
While I do n't have the iPod with me right now , I do have my Droid and was able to try this experiment .
I used an app called 'Simply Draw ' and was not able to repeat their results .
Every time I try , I get lines that are as straight as my finger can make them .
I have yet to produce lines like those in the article no matter how hard I try - even using multi-touch to draw 2 lines at once works perfectly .
One problem I have noticed with the Droid that may be the cause here is the touchscreen is very sensitive to noisy power supplies .
Using a cheap wall charger has a HUGE impact on the accuracy of the touch screen .
I 'm guessing Motorola did n't use any ferrites on the USB signals , allowing high frequency noise from an external supply to negatively impact the device .
I suspect placing a ferrite on the USB cable near the phone end would minimize this issue , but have yet to try it myself .
Instead , I just use quality chargers .</tokentext>
<sentencetext>First off, I have both a Droid and a 32GB iPod Touch.
Frankly, I like the touch on the Droid better than the iPod - I find it more responsive and more accurate when playing the same game or browsing the web on both devices.
It may just be my perception, but I simply find myself becoming less aggravated with the Droid's touch screen than the iPod's.
While I don't have the iPod with me right now, I do have my Droid and was able to try this experiment.
I used an app called 'Simply Draw' and was not able to repeat their results.
Every time I try, I get lines that are as straight as my finger can make them.
I have yet to produce lines like those in the article no matter how hard I try - even using multi-touch to draw 2 lines at once works perfectly.
One problem I have noticed with the Droid that may be the cause here is the touchscreen is very sensitive to noisy power supplies.
Using a cheap wall charger has a HUGE impact on the accuracy of the touch screen.
I'm guessing Motorola didn't use any ferrites on the USB signals, allowing high frequency noise from an external supply to negatively impact the device.
I suspect placing a ferrite on the USB cable near the phone end would minimize this issue, but have yet to try it myself.
Instead, I just use quality chargers.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723426</id>
	<title>Mechanical versus human testing...</title>
	<author>Anonymous</author>
	<datestamp>1263226860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>A more accurate way of testing this would be to use an x-y positioning device and test hitting specific areas of the screen and report back the x-y coordinates that were hit.  Repeat over a few thousand points. Test for line drawing; view with optical scanner. Repeat test for equivalent of 3 years usage.</p><p>This would give you a valid measure of the accuracy of the screen decection and it's longevity.  On wait a minute, the iPhone can't use a mechanical device but relies on the capacitance of the pointing device.  Guess you'd need to build something fancier.</p><p>What ever happened to solid scientific testing?</p></htmltext>
<tokenext>A more accurate way of testing this would be to use an x-y positioning device and test hitting specific areas of the screen and report back the x-y coordinates that were hit .
Repeat over a few thousand points .
Test for line drawing ; view with optical scanner .
Repeat test for equivalent of 3 years usage.This would give you a valid measure of the accuracy of the screen decection and it 's longevity .
On wait a minute , the iPhone ca n't use a mechanical device but relies on the capacitance of the pointing device .
Guess you 'd need to build something fancier.What ever happened to solid scientific testing ?</tokentext>
<sentencetext>A more accurate way of testing this would be to use an x-y positioning device and test hitting specific areas of the screen and report back the x-y coordinates that were hit.
Repeat over a few thousand points.
Test for line drawing; view with optical scanner.
Repeat test for equivalent of 3 years usage.This would give you a valid measure of the accuracy of the screen decection and it's longevity.
On wait a minute, the iPhone can't use a mechanical device but relies on the capacitance of the pointing device.
Guess you'd need to build something fancier.What ever happened to solid scientific testing?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723190</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723156</id>
	<title>So, restricted to capacitive screens</title>
	<author>Eunuchswear</author>
	<datestamp>1263225480000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>No mention of the N900.</p><p><a href="http://mynokiablog.com/2010/01/06/avatar-on-the-n900-sketch-app-sketching-on-n900" title="mynokiablog.com">Drawn on N900. LOL...I cringe at how bad this looks (though it is unfinished)</a> [mynokiablog.com]</p></htmltext>
<tokenext>No mention of the N900.Drawn on N900 .
LOL...I cringe at how bad this looks ( though it is unfinished ) [ mynokiablog.com ]</tokentext>
<sentencetext>No mention of the N900.Drawn on N900.
LOL...I cringe at how bad this looks (though it is unfinished) [mynokiablog.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724082</id>
	<title>Re:Ah, groupthink</title>
	<author>DeadCatX2</author>
	<datestamp>1263229980000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>One human drags his finger around a few touch screen cell phones and starts making what appears to be "statements of fact" about the quality and accuracy of those phones.  Excuse me if I don't consider the results to be rigorous.</p><p>Look at how loaded the headline is.  It definitely deserves to be here on slashdot, that's for sure.  Go look for topics where the Droid beats the iPhone and you see the exact opposite in effect; people offering apologies for the iPhone or denigrating, etc.</p><p>The guy in the linked article goes on about the quality of the construction of the touch screen.  Since he's feeling ambitious, he should try the scratch test, to see how easy it is to scratch the various screens.  I remember reading that Moto put a lot of money into making a quality screen that is very difficult to scratch...I wonder if that screen is partially responsible for the wavy lines.  But due to lack of rigor, I don't think we'll know...</p></htmltext>
<tokenext>One human drags his finger around a few touch screen cell phones and starts making what appears to be " statements of fact " about the quality and accuracy of those phones .
Excuse me if I do n't consider the results to be rigorous.Look at how loaded the headline is .
It definitely deserves to be here on slashdot , that 's for sure .
Go look for topics where the Droid beats the iPhone and you see the exact opposite in effect ; people offering apologies for the iPhone or denigrating , etc.The guy in the linked article goes on about the quality of the construction of the touch screen .
Since he 's feeling ambitious , he should try the scratch test , to see how easy it is to scratch the various screens .
I remember reading that Moto put a lot of money into making a quality screen that is very difficult to scratch...I wonder if that screen is partially responsible for the wavy lines .
But due to lack of rigor , I do n't think we 'll know.. .</tokentext>
<sentencetext>One human drags his finger around a few touch screen cell phones and starts making what appears to be "statements of fact" about the quality and accuracy of those phones.
Excuse me if I don't consider the results to be rigorous.Look at how loaded the headline is.
It definitely deserves to be here on slashdot, that's for sure.
Go look for topics where the Droid beats the iPhone and you see the exact opposite in effect; people offering apologies for the iPhone or denigrating, etc.The guy in the linked article goes on about the quality of the construction of the touch screen.
Since he's feeling ambitious, he should try the scratch test, to see how easy it is to scratch the various screens.
I remember reading that Moto put a lot of money into making a quality screen that is very difficult to scratch...I wonder if that screen is partially responsible for the wavy lines.
But due to lack of rigor, I don't think we'll know...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30726708</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>nazsco</author>
	<datestamp>1263241200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>mod parent up.</p><p>the droid has more CPU, but the lines were laging behind. I bet the app he used was not as 'native' as the other phone's (maybe a test showing the drag of a icon, see if it jitters)</p><p>And since he used different stock aplications there's no way to know if they were tweaked to draw better curves and hence did that crap.</p></htmltext>
<tokenext>mod parent up.the droid has more CPU , but the lines were laging behind .
I bet the app he used was not as 'native ' as the other phone 's ( maybe a test showing the drag of a icon , see if it jitters ) And since he used different stock aplications there 's no way to know if they were tweaked to draw better curves and hence did that crap .</tokentext>
<sentencetext>mod parent up.the droid has more CPU, but the lines were laging behind.
I bet the app he used was not as 'native' as the other phone's (maybe a test showing the drag of a icon, see if it jitters)And since he used different stock aplications there's no way to know if they were tweaked to draw better curves and hence did that crap.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723190</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724928</id>
	<title>Re:Ah, groupthink</title>
	<author>Anonymous</author>
	<datestamp>1263233700000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>The iphone fanboys vastly outnumber the 'droid ones, so had the results been the opposite, we'd have a flurry of posts claiming that the test was bullshit instead.</p><p>I wouldn't be able to disagree with them too strongly either, I don't think dragging your finger across the screen in a drawing app produces an accurate representation of the overall accuracy or quality of the screen, or the real world implications besides those of drawing diagonal lines.</p><p>-mobby\_6kl</p></htmltext>
<tokenext>The iphone fanboys vastly outnumber the 'droid ones , so had the results been the opposite , we 'd have a flurry of posts claiming that the test was bullshit instead.I would n't be able to disagree with them too strongly either , I do n't think dragging your finger across the screen in a drawing app produces an accurate representation of the overall accuracy or quality of the screen , or the real world implications besides those of drawing diagonal lines.-mobby \ _6kl</tokentext>
<sentencetext>The iphone fanboys vastly outnumber the 'droid ones, so had the results been the opposite, we'd have a flurry of posts claiming that the test was bullshit instead.I wouldn't be able to disagree with them too strongly either, I don't think dragging your finger across the screen in a drawing app produces an accurate representation of the overall accuracy or quality of the screen, or the real world implications besides those of drawing diagonal lines.-mobby\_6kl</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723510</id>
	<title>Re:As a G1 user...</title>
	<author>Dr. Evil</author>
	<datestamp>1263227280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The iPhone UI is so robust and responsive that it is *fun* to play with.  No other phone I've seen so far comes close to that.</p></htmltext>
<tokenext>The iPhone UI is so robust and responsive that it is * fun * to play with .
No other phone I 've seen so far comes close to that .</tokentext>
<sentencetext>The iPhone UI is so robust and responsive that it is *fun* to play with.
No other phone I've seen so far comes close to that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723102</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723454</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>Anonymous</author>
	<datestamp>1263227040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Let's see... Apple developed the Newton and has offered handwriting and gesture recognition built into OS X for many years now.  Ya think that maybe Apple figured from previous experience that accurate tracking might be important in the case of the iPhone's touch screen, seeing how it's integral to the interface API, and made the effort to be sure it was done properly from the start?</p><p>As fot the Future Generations... The test is for what's current, not the next generation. Obligatory car analogy: if you're buying a car this week, next year's model isn't going to play much of a role in deciding what you buy.</p></htmltext>
<tokenext>Let 's see... Apple developed the Newton and has offered handwriting and gesture recognition built into OS X for many years now .
Ya think that maybe Apple figured from previous experience that accurate tracking might be important in the case of the iPhone 's touch screen , seeing how it 's integral to the interface API , and made the effort to be sure it was done properly from the start ? As fot the Future Generations... The test is for what 's current , not the next generation .
Obligatory car analogy : if you 're buying a car this week , next year 's model is n't going to play much of a role in deciding what you buy .</tokentext>
<sentencetext>Let's see... Apple developed the Newton and has offered handwriting and gesture recognition built into OS X for many years now.
Ya think that maybe Apple figured from previous experience that accurate tracking might be important in the case of the iPhone's touch screen, seeing how it's integral to the interface API, and made the effort to be sure it was done properly from the start?As fot the Future Generations... The test is for what's current, not the next generation.
Obligatory car analogy: if you're buying a car this week, next year's model isn't going to play much of a role in deciding what you buy.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725856</id>
	<title>Re:Couldn't repeat</title>
	<author>Anonymous</author>
	<datestamp>1263237420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Seconded.  I had to toss a cheap wall power supply due to this problem.  My droid was actually reacting so strongly that it was going apeshit in the middle of the night and sending totally incoherent text messages to my contacts while I slept.</p><p>Made for some entertaining conversations the next day, but certainly not very helpful.</p></htmltext>
<tokenext>Seconded .
I had to toss a cheap wall power supply due to this problem .
My droid was actually reacting so strongly that it was going apeshit in the middle of the night and sending totally incoherent text messages to my contacts while I slept.Made for some entertaining conversations the next day , but certainly not very helpful .</tokentext>
<sentencetext>Seconded.
I had to toss a cheap wall power supply due to this problem.
My droid was actually reacting so strongly that it was going apeshit in the middle of the night and sending totally incoherent text messages to my contacts while I slept.Made for some entertaining conversations the next day, but certainly not very helpful.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724256</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723646</id>
	<title>Re:Mechanical versus human testing...</title>
	<author>larry bagina</author>
	<datestamp>1263227940000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Keep in mind, when you touch a touchscreen with your finger, the contact point is not where you think you're touching.</htmltext>
<tokenext>Keep in mind , when you touch a touchscreen with your finger , the contact point is not where you think you 're touching .</tokentext>
<sentencetext>Keep in mind, when you touch a touchscreen with your finger, the contact point is not where you think you're touching.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723426</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723654</id>
	<title>Re:Not sure why this is supposed to be a problem</title>
	<author>ShakaUVM</author>
	<datestamp>1263227940000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Eh, I have a Droid and I hate the physical keyboard. The keys are just too tiny - the on-screen keyboard keys are actually easier to hit.</p><p>I have an iPod Touch, too, and I'd agree that the iPod's screen is better. Just in terms of overall feel - the droid is actually more accurate when using the on-screen keyboard, but it's way too eager to click instead of scroll, meaning that when you're paging around through your contacts you'll accidentally dial people, and when dragging around inside of the browser, you'll accidentally follow links, etc.</p><p>It's annoying, but I like the Droid anyway.</p></htmltext>
<tokenext>Eh , I have a Droid and I hate the physical keyboard .
The keys are just too tiny - the on-screen keyboard keys are actually easier to hit.I have an iPod Touch , too , and I 'd agree that the iPod 's screen is better .
Just in terms of overall feel - the droid is actually more accurate when using the on-screen keyboard , but it 's way too eager to click instead of scroll , meaning that when you 're paging around through your contacts you 'll accidentally dial people , and when dragging around inside of the browser , you 'll accidentally follow links , etc.It 's annoying , but I like the Droid anyway .</tokentext>
<sentencetext>Eh, I have a Droid and I hate the physical keyboard.
The keys are just too tiny - the on-screen keyboard keys are actually easier to hit.I have an iPod Touch, too, and I'd agree that the iPod's screen is better.
Just in terms of overall feel - the droid is actually more accurate when using the on-screen keyboard, but it's way too eager to click instead of scroll, meaning that when you're paging around through your contacts you'll accidentally dial people, and when dragging around inside of the browser, you'll accidentally follow links, etc.It's annoying, but I like the Droid anyway.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723232</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723190</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>icegreentea</author>
	<datestamp>1263225600000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext>They are testing a first generation iPhone. This test is interesting, but not really useful. As some of the comments point out, diagonal lines really aren't the best indicator for accuracy when hitting links or whatever. As usual, the lack of consistency that comes from using a single human being comes into play. While you don't need a machine that always draws perfectly straight lines, you need a machine (or guide) that draws the same lines for each phone.<br><br>Some extra detail from the story. The iPhone has poor detection along the edges (basically flattens out diagonals into vertical or horizontal lines), the Nexus One has the best. Not that important as most UI elements aren't right at the edge anyways. The waviness in some of the tests suggests that the sensors or algorithms may be biased into vertical/horizontal motions (makes sense from a gesturing point of view).<br><br>If they really wanted to test how well the touchscreen reacts to hitting links and stuff, I don't see why they just don't go test that. Load up the same sites and keep track of how well it reacts to you hitting links. At the very least, if they wanted to do the drawing program test, it would make more sense to test what happens when you try to hit points, instead of drawing lines. So you could put some magic marker dots on the screen, and have the user hit them and look for the overlap or something.<br><br>All in all... shows off some interesting stuff. Suggests some interesting things about the behavior of the different touchscreens, but really not all too conclusive, and really points to further testing/refinement of procedure.</htmltext>
<tokenext>They are testing a first generation iPhone .
This test is interesting , but not really useful .
As some of the comments point out , diagonal lines really are n't the best indicator for accuracy when hitting links or whatever .
As usual , the lack of consistency that comes from using a single human being comes into play .
While you do n't need a machine that always draws perfectly straight lines , you need a machine ( or guide ) that draws the same lines for each phone.Some extra detail from the story .
The iPhone has poor detection along the edges ( basically flattens out diagonals into vertical or horizontal lines ) , the Nexus One has the best .
Not that important as most UI elements are n't right at the edge anyways .
The waviness in some of the tests suggests that the sensors or algorithms may be biased into vertical/horizontal motions ( makes sense from a gesturing point of view ) .If they really wanted to test how well the touchscreen reacts to hitting links and stuff , I do n't see why they just do n't go test that .
Load up the same sites and keep track of how well it reacts to you hitting links .
At the very least , if they wanted to do the drawing program test , it would make more sense to test what happens when you try to hit points , instead of drawing lines .
So you could put some magic marker dots on the screen , and have the user hit them and look for the overlap or something.All in all... shows off some interesting stuff .
Suggests some interesting things about the behavior of the different touchscreens , but really not all too conclusive , and really points to further testing/refinement of procedure .</tokentext>
<sentencetext>They are testing a first generation iPhone.
This test is interesting, but not really useful.
As some of the comments point out, diagonal lines really aren't the best indicator for accuracy when hitting links or whatever.
As usual, the lack of consistency that comes from using a single human being comes into play.
While you don't need a machine that always draws perfectly straight lines, you need a machine (or guide) that draws the same lines for each phone.Some extra detail from the story.
The iPhone has poor detection along the edges (basically flattens out diagonals into vertical or horizontal lines), the Nexus One has the best.
Not that important as most UI elements aren't right at the edge anyways.
The waviness in some of the tests suggests that the sensors or algorithms may be biased into vertical/horizontal motions (makes sense from a gesturing point of view).If they really wanted to test how well the touchscreen reacts to hitting links and stuff, I don't see why they just don't go test that.
Load up the same sites and keep track of how well it reacts to you hitting links.
At the very least, if they wanted to do the drawing program test, it would make more sense to test what happens when you try to hit points, instead of drawing lines.
So you could put some magic marker dots on the screen, and have the user hit them and look for the overlap or something.All in all... shows off some interesting stuff.
Suggests some interesting things about the behavior of the different touchscreens, but really not all too conclusive, and really points to further testing/refinement of procedure.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723336</id>
	<title>Re:Not sure why this is supposed to be a problem</title>
	<author>darjen</author>
	<datestamp>1263226440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>yep, I feel the same way about my Droid. works fine, imho. this "test" has nothing to do with real life.</p></htmltext>
<tokenext>yep , I feel the same way about my Droid .
works fine , imho .
this " test " has nothing to do with real life .</tokentext>
<sentencetext>yep, I feel the same way about my Droid.
works fine, imho.
this "test" has nothing to do with real life.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723232</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30733986</id>
	<title>Re:Couldn't repeat</title>
	<author>adolf</author>
	<datestamp>1263238800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'd like to second these comments:</p><p>Moving my finger fast, in a straight line in any direction (using a straightedge), things look fine on my Droid.</p><p>I haven't R'd the FA, but moving my finger slowly across the Droid's screen shows a whole bunch of significant waviness that just shouldn't be there, and indeed is <b>not</b> there when doing the same sort of motion on my first-gen iPod Touch.  (All devices running recent firmware, the Droid at 2.0.1 and the iPod at 3.1.something, IIRC.)</p><p>So, it's obviously imperfect.</p><p>Is it a problem?  Not for me.  I carry my laptop with me everywhere, along with a decent Bluetooth mouse, so if I really need an accurate sketch, this isn't going to affect me.  I also, for now at least, carry the iPod Touch, but I've never been inclined to draw on it in any serious capacity.</p><p>In terms of how I actually use the two devices:  The Droid consistently does a better job of picking out the correct link on a fine-print website than the iPod does.  Typing on the touchscreen keyboard of either device feels about the same, to me, with neither one being very accurate without automatic spelling correction fixing my entries.</p><p>Like many people here, I used to carry a Palm device (first a Visor Deluxe, then a Zire 71, then back to the Visor when replacing the lithium battery on the Zire went all wrong).  Unlike many people here, I'm writing this on a very nice Elo-modified NEC LCD surface acoustic wave touchscreen monitor.  I am very used to having rather good accuracy in pointing with stylus- and finger-based touch devices.</p><p>But with these modern(ish) handhelds, I guess I just don't care much.  Both the Droid and the iPod Touch do a perfectly OK job of the stuff that I expect them to do.  Frankly, they both amaze me in their ability to determine the exact point that my blunt fingertip is pointing at.</p><p>Therefore, I say they both win.</p></htmltext>
<tokenext>I 'd like to second these comments : Moving my finger fast , in a straight line in any direction ( using a straightedge ) , things look fine on my Droid.I have n't R 'd the FA , but moving my finger slowly across the Droid 's screen shows a whole bunch of significant waviness that just should n't be there , and indeed is not there when doing the same sort of motion on my first-gen iPod Touch .
( All devices running recent firmware , the Droid at 2.0.1 and the iPod at 3.1.something , IIRC .
) So , it 's obviously imperfect.Is it a problem ?
Not for me .
I carry my laptop with me everywhere , along with a decent Bluetooth mouse , so if I really need an accurate sketch , this is n't going to affect me .
I also , for now at least , carry the iPod Touch , but I 've never been inclined to draw on it in any serious capacity.In terms of how I actually use the two devices : The Droid consistently does a better job of picking out the correct link on a fine-print website than the iPod does .
Typing on the touchscreen keyboard of either device feels about the same , to me , with neither one being very accurate without automatic spelling correction fixing my entries.Like many people here , I used to carry a Palm device ( first a Visor Deluxe , then a Zire 71 , then back to the Visor when replacing the lithium battery on the Zire went all wrong ) .
Unlike many people here , I 'm writing this on a very nice Elo-modified NEC LCD surface acoustic wave touchscreen monitor .
I am very used to having rather good accuracy in pointing with stylus- and finger-based touch devices.But with these modern ( ish ) handhelds , I guess I just do n't care much .
Both the Droid and the iPod Touch do a perfectly OK job of the stuff that I expect them to do .
Frankly , they both amaze me in their ability to determine the exact point that my blunt fingertip is pointing at.Therefore , I say they both win .</tokentext>
<sentencetext>I'd like to second these comments:Moving my finger fast, in a straight line in any direction (using a straightedge), things look fine on my Droid.I haven't R'd the FA, but moving my finger slowly across the Droid's screen shows a whole bunch of significant waviness that just shouldn't be there, and indeed is not there when doing the same sort of motion on my first-gen iPod Touch.
(All devices running recent firmware, the Droid at 2.0.1 and the iPod at 3.1.something, IIRC.
)So, it's obviously imperfect.Is it a problem?
Not for me.
I carry my laptop with me everywhere, along with a decent Bluetooth mouse, so if I really need an accurate sketch, this isn't going to affect me.
I also, for now at least, carry the iPod Touch, but I've never been inclined to draw on it in any serious capacity.In terms of how I actually use the two devices:  The Droid consistently does a better job of picking out the correct link on a fine-print website than the iPod does.
Typing on the touchscreen keyboard of either device feels about the same, to me, with neither one being very accurate without automatic spelling correction fixing my entries.Like many people here, I used to carry a Palm device (first a Visor Deluxe, then a Zire 71, then back to the Visor when replacing the lithium battery on the Zire went all wrong).
Unlike many people here, I'm writing this on a very nice Elo-modified NEC LCD surface acoustic wave touchscreen monitor.
I am very used to having rather good accuracy in pointing with stylus- and finger-based touch devices.But with these modern(ish) handhelds, I guess I just don't care much.
Both the Droid and the iPod Touch do a perfectly OK job of the stuff that I expect them to do.
Frankly, they both amaze me in their ability to determine the exact point that my blunt fingertip is pointing at.Therefore, I say they both win.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727660</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725206</id>
	<title>Re:Ah, groupthink</title>
	<author>Graff</author>
	<datestamp>1263234720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>If you spent five minutes looking at this outfit's methodology you'd realize that the test is sound, though perhaps a little exacting compared to real-world use cases.</p></div><p>It's not really that great of a methodology. First of all it depends on something that is very difficult to get right, consistency in pressure and accuracy of a human finger. Changing the pressure, position, or angle of your finger can drastically change which capacitive element is triggered on the screen. It becomes difficult to separate errors in the touchscreen from the inaccuracy of the tester's finger.</p><p>Secondly, there could be algorithms that account for the motion of the touch in order to predict the next position. If you move across the screen at a certain velocity then it's likely that the next position will be along that line. A good algorithm will take this into account and adjust the position accordingly, resulting in smoother lines. Since the test uses motion this could introduce another variable and confuse the issue.</p><p>A better test would be to get one of the styluses that are made for capacitive touchscreens and use some sort of x-y table to move either the stylus or the device. At certain positions you lower the stylus to touch at one point. Repeat this many times and then look at the results.</p><p>This sort of test is a much better way to test the true accuracy and precision of these devices. Still, the article does show that there is some sort of effect going on here and that certain devices are most likely more accurate and precise at predicting the true position of a finger on their screen.</p></div>
	</htmltext>
<tokenext>If you spent five minutes looking at this outfit 's methodology you 'd realize that the test is sound , though perhaps a little exacting compared to real-world use cases.It 's not really that great of a methodology .
First of all it depends on something that is very difficult to get right , consistency in pressure and accuracy of a human finger .
Changing the pressure , position , or angle of your finger can drastically change which capacitive element is triggered on the screen .
It becomes difficult to separate errors in the touchscreen from the inaccuracy of the tester 's finger.Secondly , there could be algorithms that account for the motion of the touch in order to predict the next position .
If you move across the screen at a certain velocity then it 's likely that the next position will be along that line .
A good algorithm will take this into account and adjust the position accordingly , resulting in smoother lines .
Since the test uses motion this could introduce another variable and confuse the issue.A better test would be to get one of the styluses that are made for capacitive touchscreens and use some sort of x-y table to move either the stylus or the device .
At certain positions you lower the stylus to touch at one point .
Repeat this many times and then look at the results.This sort of test is a much better way to test the true accuracy and precision of these devices .
Still , the article does show that there is some sort of effect going on here and that certain devices are most likely more accurate and precise at predicting the true position of a finger on their screen .</tokentext>
<sentencetext>If you spent five minutes looking at this outfit's methodology you'd realize that the test is sound, though perhaps a little exacting compared to real-world use cases.It's not really that great of a methodology.
First of all it depends on something that is very difficult to get right, consistency in pressure and accuracy of a human finger.
Changing the pressure, position, or angle of your finger can drastically change which capacitive element is triggered on the screen.
It becomes difficult to separate errors in the touchscreen from the inaccuracy of the tester's finger.Secondly, there could be algorithms that account for the motion of the touch in order to predict the next position.
If you move across the screen at a certain velocity then it's likely that the next position will be along that line.
A good algorithm will take this into account and adjust the position accordingly, resulting in smoother lines.
Since the test uses motion this could introduce another variable and confuse the issue.A better test would be to get one of the styluses that are made for capacitive touchscreens and use some sort of x-y table to move either the stylus or the device.
At certain positions you lower the stylus to touch at one point.
Repeat this many times and then look at the results.This sort of test is a much better way to test the true accuracy and precision of these devices.
Still, the article does show that there is some sort of effect going on here and that certain devices are most likely more accurate and precise at predicting the true position of a finger on their screen.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434</id>
	<title>Ah, groupthink</title>
	<author>Anonymous</author>
	<datestamp>1263226920000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>If you spent five minutes looking at this outfit's methodology you'd realize that the test is sound, though perhaps a little exacting compared to real-world use cases. But what I love is that the first twenty posts or so basically all offered apologies for the Android phones and denigrated the significance of the test. They couldn't be better PR responses if Google and Motorola had drafted them. If you happen to use and like an Android device, why don't you just admit that it has a flaw and deal with it? God knows it probably isn't going to affect you under most usual circumstances.</p><p>I can't tell you for how long I was and still am pissed off about various missing features on the iPhone  (auto-SMS, copy/paste, etc.) but I still like the device overall and use it. You don't have to hold this borderline view of the world in which computing devices are either God's work on Earth or Satan's playthings.</p></htmltext>
<tokenext>If you spent five minutes looking at this outfit 's methodology you 'd realize that the test is sound , though perhaps a little exacting compared to real-world use cases .
But what I love is that the first twenty posts or so basically all offered apologies for the Android phones and denigrated the significance of the test .
They could n't be better PR responses if Google and Motorola had drafted them .
If you happen to use and like an Android device , why do n't you just admit that it has a flaw and deal with it ?
God knows it probably is n't going to affect you under most usual circumstances.I ca n't tell you for how long I was and still am pissed off about various missing features on the iPhone ( auto-SMS , copy/paste , etc .
) but I still like the device overall and use it .
You do n't have to hold this borderline view of the world in which computing devices are either God 's work on Earth or Satan 's playthings .</tokentext>
<sentencetext>If you spent five minutes looking at this outfit's methodology you'd realize that the test is sound, though perhaps a little exacting compared to real-world use cases.
But what I love is that the first twenty posts or so basically all offered apologies for the Android phones and denigrated the significance of the test.
They couldn't be better PR responses if Google and Motorola had drafted them.
If you happen to use and like an Android device, why don't you just admit that it has a flaw and deal with it?
God knows it probably isn't going to affect you under most usual circumstances.I can't tell you for how long I was and still am pissed off about various missing features on the iPhone  (auto-SMS, copy/paste, etc.
) but I still like the device overall and use it.
You don't have to hold this borderline view of the world in which computing devices are either God's work on Earth or Satan's playthings.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30743680</id>
	<title>Re:Obviously...</title>
	<author>BCs7</author>
	<datestamp>1263295380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This would be an awesome and thorough test, except for the fact that the premise is completely and utterly flawed and bogus. This in NO way tests the capabilities of the hardware touchscreen, all this is testing is the sensitivity and precision of whatever cobbled together drawing program you happen to be using on whatever platform.
Im not saying the Droid isnt the worst, i am saying that this is not a good way to test this.
Try again.</htmltext>
<tokenext>This would be an awesome and thorough test , except for the fact that the premise is completely and utterly flawed and bogus .
This in NO way tests the capabilities of the hardware touchscreen , all this is testing is the sensitivity and precision of whatever cobbled together drawing program you happen to be using on whatever platform .
Im not saying the Droid isnt the worst , i am saying that this is not a good way to test this .
Try again .</tokentext>
<sentencetext>This would be an awesome and thorough test, except for the fact that the premise is completely and utterly flawed and bogus.
This in NO way tests the capabilities of the hardware touchscreen, all this is testing is the sensitivity and precision of whatever cobbled together drawing program you happen to be using on whatever platform.
Im not saying the Droid isnt the worst, i am saying that this is not a good way to test this.
Try again.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30722978</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723164</id>
	<title>Re:Used "a program" ?</title>
	<author>Anonymous</author>
	<datestamp>1263225540000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>"These aren't the results I wanted to see, therefore the methodology is flawed!"</p></htmltext>
<tokenext>" These are n't the results I wanted to see , therefore the methodology is flawed !
"</tokentext>
<sentencetext>"These aren't the results I wanted to see, therefore the methodology is flawed!
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723058</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723360</id>
	<title>This has nearly nothing to do with click quality</title>
	<author>barfy</author>
	<datestamp>1263226560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>There is a ton of code in both the Iphone OS and the browser to improve click "quality" of links and buttons and stuff in the product.</p><p>They do this, because this is NOT a stylus product, but a product used with fingers.    There is even code, that takes account of the consistent errors that YOU, the registered user, make.</p><p>They may or may not do this in android.</p><p>But at the end of the day, this is not anywhere near the test, nor the conclusions you should be drawing from the test.</p></htmltext>
<tokenext>There is a ton of code in both the Iphone OS and the browser to improve click " quality " of links and buttons and stuff in the product.They do this , because this is NOT a stylus product , but a product used with fingers .
There is even code , that takes account of the consistent errors that YOU , the registered user , make.They may or may not do this in android.But at the end of the day , this is not anywhere near the test , nor the conclusions you should be drawing from the test .</tokentext>
<sentencetext>There is a ton of code in both the Iphone OS and the browser to improve click "quality" of links and buttons and stuff in the product.They do this, because this is NOT a stylus product, but a product used with fingers.
There is even code, that takes account of the consistent errors that YOU, the registered user, make.They may or may not do this in android.But at the end of the day, this is not anywhere near the test, nor the conclusions you should be drawing from the test.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723082</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>Anonymous</author>
	<datestamp>1263225060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Yes it is fair. This is only information. A consumer only cares about how the current product works.</p></htmltext>
<tokenext>Yes it is fair .
This is only information .
A consumer only cares about how the current product works .</tokentext>
<sentencetext>Yes it is fair.
This is only information.
A consumer only cares about how the current product works.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30728752</id>
	<title>Re:Couldn't repeat</title>
	<author>Anonymous</author>
	<datestamp>1263204540000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>It might help to keep in mind that it's "The Unofficial Apple Weblog" doing this experiment.</p><p>"Astroturfers" or "fanbois" comes to my mind immediately. Were it coming from a unbiased source, I might give a shit what they say. As is, I ain't buyin it.</p></htmltext>
<tokenext>It might help to keep in mind that it 's " The Unofficial Apple Weblog " doing this experiment .
" Astroturfers " or " fanbois " comes to my mind immediately .
Were it coming from a unbiased source , I might give a shit what they say .
As is , I ai n't buyin it .</tokentext>
<sentencetext>It might help to keep in mind that it's "The Unofficial Apple Weblog" doing this experiment.
"Astroturfers" or "fanbois" comes to my mind immediately.
Were it coming from a unbiased source, I might give a shit what they say.
As is, I ain't buyin it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724256</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724128</id>
	<title>Re:Ah, groupthink</title>
	<author>Anonymous</author>
	<datestamp>1263230280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It's called the Stockholm Syndrom</p></htmltext>
<tokenext>It 's called the Stockholm Syndrom</tokentext>
<sentencetext>It's called the Stockholm Syndrom</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30731984</id>
	<title>Re:Well of course drawing lines is important</title>
	<author>midascheeley</author>
	<datestamp>1263220200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I never thought I would be so good with a qwerty keyboard, but my droid is pretty accurate as far as that goes.  It is a little awkward with the web browsing and trying to click links, but as far as the contacts and texting, it's pretty awesome.  I haven't used an iPhone too much, just played around with one a couple times but I think I would prefer my droid for sure.</htmltext>
<tokenext>I never thought I would be so good with a qwerty keyboard , but my droid is pretty accurate as far as that goes .
It is a little awkward with the web browsing and trying to click links , but as far as the contacts and texting , it 's pretty awesome .
I have n't used an iPhone too much , just played around with one a couple times but I think I would prefer my droid for sure .</tokentext>
<sentencetext>I never thought I would be so good with a qwerty keyboard, but my droid is pretty accurate as far as that goes.
It is a little awkward with the web browsing and trying to click links, but as far as the contacts and texting, it's pretty awesome.
I haven't used an iPhone too much, just played around with one a couple times but I think I would prefer my droid for sure.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723518</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723550</id>
	<title>Re:This has nearly nothing to do with click qualit</title>
	<author>NameIsDavid</author>
	<datestamp>1263227460000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>

This test is the result of the combined hardware-software system that results, at the end of the chain, in the API providing the app with a position. This is what the test ought to show. It doesn't matter if Apple's hardware or software takes the credit for the improved positional accuracy since the end result is what counts. What it does mean is that if the benefits stem from the post-touch processing in software, Android ought to be able to make the required changes to improve things. Until then, though, this is a test of how things currently stand (for what it's worth<nobr> <wbr></nobr>... I agree that there could be different algorithms at play for resolving distinct touches or identifying the targets of those touches compared with line-drawing accuracy).</htmltext>
<tokenext>This test is the result of the combined hardware-software system that results , at the end of the chain , in the API providing the app with a position .
This is what the test ought to show .
It does n't matter if Apple 's hardware or software takes the credit for the improved positional accuracy since the end result is what counts .
What it does mean is that if the benefits stem from the post-touch processing in software , Android ought to be able to make the required changes to improve things .
Until then , though , this is a test of how things currently stand ( for what it 's worth ... I agree that there could be different algorithms at play for resolving distinct touches or identifying the targets of those touches compared with line-drawing accuracy ) .</tokentext>
<sentencetext>

This test is the result of the combined hardware-software system that results, at the end of the chain, in the API providing the app with a position.
This is what the test ought to show.
It doesn't matter if Apple's hardware or software takes the credit for the improved positional accuracy since the end result is what counts.
What it does mean is that if the benefits stem from the post-touch processing in software, Android ought to be able to make the required changes to improve things.
Until then, though, this is a test of how things currently stand (for what it's worth ... I agree that there could be different algorithms at play for resolving distinct touches or identifying the targets of those touches compared with line-drawing accuracy).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723360</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727224</id>
	<title>interpolation</title>
	<author>Anonymous</author>
	<datestamp>1263242760000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>It's a DRAWING PROGRAM<nobr> <wbr></nobr>... a stream of points.</p></div><p>and you're so sure it doesn't apply interpolation and smoothing algorithms of various sophistication because?..</p></div>
	</htmltext>
<tokenext>It 's a DRAWING PROGRAM ... a stream of points.and you 're so sure it does n't apply interpolation and smoothing algorithms of various sophistication because ? . .</tokentext>
<sentencetext>It's a DRAWING PROGRAM ... a stream of points.and you're so sure it doesn't apply interpolation and smoothing algorithms of various sophistication because?..
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724186</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723108</id>
	<title>So what?</title>
	<author>MrEricSir</author>
	<datestamp>1263225240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Does whether or not you can draw diagonal lines on a screen really make a difference?  As long as you can still click web links and the on-screen keyboard (where applicable) then who cares?</p></htmltext>
<tokenext>Does whether or not you can draw diagonal lines on a screen really make a difference ?
As long as you can still click web links and the on-screen keyboard ( where applicable ) then who cares ?</tokentext>
<sentencetext>Does whether or not you can draw diagonal lines on a screen really make a difference?
As long as you can still click web links and the on-screen keyboard (where applicable) then who cares?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723340</id>
	<title>Resolution?</title>
	<author>Anonymous</author>
	<datestamp>1263226500000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext>What effect does the fact that the iPhone has a vastly lower resolution screen play in this accuracy "test"?  Seems it would make it easier to be more accurate.</htmltext>
<tokenext>What effect does the fact that the iPhone has a vastly lower resolution screen play in this accuracy " test " ?
Seems it would make it easier to be more accurate .</tokentext>
<sentencetext>What effect does the fact that the iPhone has a vastly lower resolution screen play in this accuracy "test"?
Seems it would make it easier to be more accurate.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723276</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>riegel</author>
	<datestamp>1263226020000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>I would guess that the 1st gen was/is just as accurate as the 3rd gen.<br>But you can build your straw man. They are easier to tear down that way.</htmltext>
<tokenext>I would guess that the 1st gen was/is just as accurate as the 3rd gen.But you can build your straw man .
They are easier to tear down that way .</tokentext>
<sentencetext>I would guess that the 1st gen was/is just as accurate as the 3rd gen.But you can build your straw man.
They are easier to tear down that way.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723994</id>
	<title>Re:Not sure why this is supposed to be a problem</title>
	<author>mewsenews</author>
	<datestamp>1263229560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>That said, the only reason why I have a Droid is because of the physical keyboard and a pretty decent free ssh client.</p></div></blockquote><p>Do you happen to have any links illustrating the ssh client you mentioned? Sounds interesting.</p></div>
	</htmltext>
<tokenext>That said , the only reason why I have a Droid is because of the physical keyboard and a pretty decent free ssh client.Do you happen to have any links illustrating the ssh client you mentioned ?
Sounds interesting .</tokentext>
<sentencetext>That said, the only reason why I have a Droid is because of the physical keyboard and a pretty decent free ssh client.Do you happen to have any links illustrating the ssh client you mentioned?
Sounds interesting.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723232</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724094</id>
	<title>Test Results</title>
	<author>derrickh</author>
	<datestamp>1263230040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If they wanted to test the accuracy of clicking links in a webpage, wouldn't they have tested it by clicking links in a webpage?</p></htmltext>
<tokenext>If they wanted to test the accuracy of clicking links in a webpage , would n't they have tested it by clicking links in a webpage ?</tokentext>
<sentencetext>If they wanted to test the accuracy of clicking links in a webpage, wouldn't they have tested it by clicking links in a webpage?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727976</id>
	<title>Re:Obviously...</title>
	<author>Anonymous</author>
	<datestamp>1263201900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This article reflects the negatives of not performing tests scientifically, with precision by removing human errors of method and thinking critically.</p></htmltext>
<tokenext>This article reflects the negatives of not performing tests scientifically , with precision by removing human errors of method and thinking critically .</tokentext>
<sentencetext>This article reflects the negatives of not performing tests scientifically, with precision by removing human errors of method and thinking critically.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30722978</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30729866</id>
	<title>Re:Their conclusion is illogical.</title>
	<author>amRadioHed</author>
	<datestamp>1263208680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It has nothing to do with accuracy degrading over time. When I do the test on my Nexus, I get a wavy line from the start.</p><p>Even if that was a factor it would still be relevant in the real world since scrolling around a web browser requires a lot of screen contact.</p></htmltext>
<tokenext>It has nothing to do with accuracy degrading over time .
When I do the test on my Nexus , I get a wavy line from the start.Even if that was a factor it would still be relevant in the real world since scrolling around a web browser requires a lot of screen contact .</tokentext>
<sentencetext>It has nothing to do with accuracy degrading over time.
When I do the test on my Nexus, I get a wavy line from the start.Even if that was a factor it would still be relevant in the real world since scrolling around a web browser requires a lot of screen contact.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723182</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723266</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>obarthelemy</author>
	<datestamp>1263225960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>it is fair to compare products available now that represent the best and brightest of what I can buy with my money.</p></htmltext>
<tokenext>it is fair to compare products available now that represent the best and brightest of what I can buy with my money .</tokentext>
<sentencetext>it is fair to compare products available now that represent the best and brightest of what I can buy with my money.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723456</id>
	<title>Re:Used "a program" ?</title>
	<author>Anonymous</author>
	<datestamp>1263227040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The methodology used wasn't documented sufficiently, from what we can see about the methodology we can conclude that it's sloppy and he didn't double-blind or collect enough data to do the proper statistics. And even if the data collected is valid, the conclusion he tries to draw isn't supported by it.</p></htmltext>
<tokenext>The methodology used was n't documented sufficiently , from what we can see about the methodology we can conclude that it 's sloppy and he did n't double-blind or collect enough data to do the proper statistics .
And even if the data collected is valid , the conclusion he tries to draw is n't supported by it .</tokentext>
<sentencetext>The methodology used wasn't documented sufficiently, from what we can see about the methodology we can conclude that it's sloppy and he didn't double-blind or collect enough data to do the proper statistics.
And even if the data collected is valid, the conclusion he tries to draw isn't supported by it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723058</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727584</id>
	<title>Hmmm.</title>
	<author>weston</author>
	<datestamp>1263200520000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p><i>All that means, though, is that the Droid is not a good choice for a phone if you want to draw on it. I am still able to use the on-screen keyboard just fine and even in a web browser I never have problems tapping a link no matter how far I am zoomed out. This is definitely not a deal-breaker for me</i></p><p>So, in other words, you've figured out which features are important to you, which are less important to you, and a lack in a feature that isn't important to you.... doesn't make the product worth less over to you.</p><p>That's a pretty smart point of view.</p><p>Might even be why you're the kind of person who owns a Droid, unlike those stupid iPhone sheeple blinded by Apple's shiny marketing into buying a phone that has a locked-down app store and no tethering or hardware keyboard.</p></htmltext>
<tokenext>All that means , though , is that the Droid is not a good choice for a phone if you want to draw on it .
I am still able to use the on-screen keyboard just fine and even in a web browser I never have problems tapping a link no matter how far I am zoomed out .
This is definitely not a deal-breaker for meSo , in other words , you 've figured out which features are important to you , which are less important to you , and a lack in a feature that is n't important to you.... does n't make the product worth less over to you.That 's a pretty smart point of view.Might even be why you 're the kind of person who owns a Droid , unlike those stupid iPhone sheeple blinded by Apple 's shiny marketing into buying a phone that has a locked-down app store and no tethering or hardware keyboard .</tokentext>
<sentencetext>All that means, though, is that the Droid is not a good choice for a phone if you want to draw on it.
I am still able to use the on-screen keyboard just fine and even in a web browser I never have problems tapping a link no matter how far I am zoomed out.
This is definitely not a deal-breaker for meSo, in other words, you've figured out which features are important to you, which are less important to you, and a lack in a feature that isn't important to you.... doesn't make the product worth less over to you.That's a pretty smart point of view.Might even be why you're the kind of person who owns a Droid, unlike those stupid iPhone sheeple blinded by Apple's shiny marketing into buying a phone that has a locked-down app store and no tethering or hardware keyboard.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723232</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725820</id>
	<title>Re:Ah, groupthink</title>
	<author>0xdeadbeef</author>
	<datestamp>1263237180000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p><i>If you spent five minutes looking at this outfit's methodology you'd realize that the test is sound</i></p><p>I spent less than five minutes watching the video and I realized I had been wasting my time, because this "test" is an absolute joke. He isn't balancing his finger against a straight edge, he isn't moving it at a constant rate, and the results in the video don't correspond to the images on the web site.</p><p>Before I watched the video, I thought it had some legitimacy, as I got wavy lines when I drew on my Nexus One. But then I tried it with my finger against a pen laid diagonally across the screen, and it produced a perfect straight line, at every speed. The whole article is a fanboy blowing smoke, relying on the twitchy human nervous system.</p><p>I think Martin Sheen said it best:</p><blockquote><div><p>Willard: They told me that you had gone totally insane, and that your methods were unsound.<br>Kurtz: Are my methods unsound?<br>Willard: I don't see any method at all, sir.</p></div> </blockquote></div>
	</htmltext>
<tokenext>If you spent five minutes looking at this outfit 's methodology you 'd realize that the test is soundI spent less than five minutes watching the video and I realized I had been wasting my time , because this " test " is an absolute joke .
He is n't balancing his finger against a straight edge , he is n't moving it at a constant rate , and the results in the video do n't correspond to the images on the web site.Before I watched the video , I thought it had some legitimacy , as I got wavy lines when I drew on my Nexus One .
But then I tried it with my finger against a pen laid diagonally across the screen , and it produced a perfect straight line , at every speed .
The whole article is a fanboy blowing smoke , relying on the twitchy human nervous system.I think Martin Sheen said it best : Willard : They told me that you had gone totally insane , and that your methods were unsound.Kurtz : Are my methods unsound ? Willard : I do n't see any method at all , sir .</tokentext>
<sentencetext>If you spent five minutes looking at this outfit's methodology you'd realize that the test is soundI spent less than five minutes watching the video and I realized I had been wasting my time, because this "test" is an absolute joke.
He isn't balancing his finger against a straight edge, he isn't moving it at a constant rate, and the results in the video don't correspond to the images on the web site.Before I watched the video, I thought it had some legitimacy, as I got wavy lines when I drew on my Nexus One.
But then I tried it with my finger against a pen laid diagonally across the screen, and it produced a perfect straight line, at every speed.
The whole article is a fanboy blowing smoke, relying on the twitchy human nervous system.I think Martin Sheen said it best:Willard: They told me that you had gone totally insane, and that your methods were unsound.Kurtz: Are my methods unsound?Willard: I don't see any method at all, sir. 
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723382</id>
	<title>What would be intersesting to know...</title>
	<author>fuzzyfuzzyfungus</author>
	<datestamp>1263226620000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>Is whether other flavors of applications do their own "cheating" to compensate for this.<br> <br>

In the classic desktop keyboard/mouse arrangement, it is more or less taken for granted that the user will be able to accurately press any button, and put the mouse within a couple pixels of any target(with the exception of somewhat disabled users).<br> <br>
Phones with hard buttons and resistive/stylus touch screens more or less closely approximate this.<br> <br>

Capacitive screens, by contrast, are better for finger work; but rather less precise. This creates a strong incentive to write the software to be as silently forgiving of certain errors as possible. Drawing programs are hard, since there is basically no way(short of an artistic AI) to infer the user's desire. You pretty much have to make do with the best your screen can give you. With a web browser, say, you can fairly strongly assume that users are intersted in clicking on links, rather than just jabbing at inert text, and expand the link target area appropriately. Same thing with all the tricks that touchscreen keyboards use, silently expanding target areas in order to augment accuracy.<br> <br>

It is definitely useful to know how good the raw input is, and more accurate is of course better; but in a class of devices defined by fairly inaccurate input devices, the real question is how good the software's intepretation of the input will be.</htmltext>
<tokenext>Is whether other flavors of applications do their own " cheating " to compensate for this .
In the classic desktop keyboard/mouse arrangement , it is more or less taken for granted that the user will be able to accurately press any button , and put the mouse within a couple pixels of any target ( with the exception of somewhat disabled users ) .
Phones with hard buttons and resistive/stylus touch screens more or less closely approximate this .
Capacitive screens , by contrast , are better for finger work ; but rather less precise .
This creates a strong incentive to write the software to be as silently forgiving of certain errors as possible .
Drawing programs are hard , since there is basically no way ( short of an artistic AI ) to infer the user 's desire .
You pretty much have to make do with the best your screen can give you .
With a web browser , say , you can fairly strongly assume that users are intersted in clicking on links , rather than just jabbing at inert text , and expand the link target area appropriately .
Same thing with all the tricks that touchscreen keyboards use , silently expanding target areas in order to augment accuracy .
It is definitely useful to know how good the raw input is , and more accurate is of course better ; but in a class of devices defined by fairly inaccurate input devices , the real question is how good the software 's intepretation of the input will be .</tokentext>
<sentencetext>Is whether other flavors of applications do their own "cheating" to compensate for this.
In the classic desktop keyboard/mouse arrangement, it is more or less taken for granted that the user will be able to accurately press any button, and put the mouse within a couple pixels of any target(with the exception of somewhat disabled users).
Phones with hard buttons and resistive/stylus touch screens more or less closely approximate this.
Capacitive screens, by contrast, are better for finger work; but rather less precise.
This creates a strong incentive to write the software to be as silently forgiving of certain errors as possible.
Drawing programs are hard, since there is basically no way(short of an artistic AI) to infer the user's desire.
You pretty much have to make do with the best your screen can give you.
With a web browser, say, you can fairly strongly assume that users are intersted in clicking on links, rather than just jabbing at inert text, and expand the link target area appropriately.
Same thing with all the tricks that touchscreen keyboards use, silently expanding target areas in order to augment accuracy.
It is definitely useful to know how good the raw input is, and more accurate is of course better; but in a class of devices defined by fairly inaccurate input devices, the real question is how good the software's intepretation of the input will be.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30729224</id>
	<title>Less accurate, but is it usable?</title>
	<author>Trogre</author>
	<datestamp>1263206280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm not so concerned if it's slightly less accurate than the iphone.  I'm more interested in whether one can use it with a stylus or gloved hands.</p></htmltext>
<tokenext>I 'm not so concerned if it 's slightly less accurate than the iphone .
I 'm more interested in whether one can use it with a stylus or gloved hands .</tokentext>
<sentencetext>I'm not so concerned if it's slightly less accurate than the iphone.
I'm more interested in whether one can use it with a stylus or gloved hands.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724230</id>
	<title>In more recent news</title>
	<author>Requiem18th</author>
	<datestamp>1263230760000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p>iPod users have bigger dicks than Android users.</p><p>IPod users have smaller breasts than Android but only the male ones.</p></htmltext>
<tokenext>iPod users have bigger dicks than Android users.IPod users have smaller breasts than Android but only the male ones .</tokentext>
<sentencetext>iPod users have bigger dicks than Android users.IPod users have smaller breasts than Android but only the male ones.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723126</id>
	<title>Re:Obviously...</title>
	<author>Anonymous</author>
	<datestamp>1263225360000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Who'd have thought it - an FP that's actually funny!</p></htmltext>
<tokenext>Who 'd have thought it - an FP that 's actually funny !</tokentext>
<sentencetext>Who'd have thought it - an FP that's actually funny!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30722978</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724186</id>
	<title>Welcome to the world of the API</title>
	<author>SuperKendall</author>
	<datestamp>1263230520000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p><i>Was the program written to the same quality in all platforms?</i></p><p>It's a DRAWING PROGRAM.</p><p>As in, they take in whatever pixel input the system gives them and spit them out on the screen.  "Quality" does not enter into it, because they are all using the same API's that just have the OS feed them a stream of points.</p><p>It's representative of the quality of touch accuracy you will have in other apps because they, too, will just look at what points the OS is presenting the user as having touched.</p></htmltext>
<tokenext>Was the program written to the same quality in all platforms ? It 's a DRAWING PROGRAM.As in , they take in whatever pixel input the system gives them and spit them out on the screen .
" Quality " does not enter into it , because they are all using the same API 's that just have the OS feed them a stream of points.It 's representative of the quality of touch accuracy you will have in other apps because they , too , will just look at what points the OS is presenting the user as having touched .</tokentext>
<sentencetext>Was the program written to the same quality in all platforms?It's a DRAWING PROGRAM.As in, they take in whatever pixel input the system gives them and spit them out on the screen.
"Quality" does not enter into it, because they are all using the same API's that just have the OS feed them a stream of points.It's representative of the quality of touch accuracy you will have in other apps because they, too, will just look at what points the OS is presenting the user as having touched.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723058</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723102</id>
	<title>As a G1 user...</title>
	<author>foodnugget</author>
	<datestamp>1263225180000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>I have to admit that I am somewhat underwhelmed. I got the G1 shortly after it came out a year and a half or so ago, and the touchscreen definitely falls short of what it could be. It is FAR less responsive than the iphone's, and the accuracy could indeed be better. I was coming from a winmo 5 device, so i'm still incredibly happy with it, relatively speaking.
<br> <br>
So the big question is whether or not all the manufs of android devices are using the same screen/screen chips, or if android has a fundamental problem interpreting data off the screen?</htmltext>
<tokenext>I have to admit that I am somewhat underwhelmed .
I got the G1 shortly after it came out a year and a half or so ago , and the touchscreen definitely falls short of what it could be .
It is FAR less responsive than the iphone 's , and the accuracy could indeed be better .
I was coming from a winmo 5 device , so i 'm still incredibly happy with it , relatively speaking .
So the big question is whether or not all the manufs of android devices are using the same screen/screen chips , or if android has a fundamental problem interpreting data off the screen ?</tokentext>
<sentencetext>I have to admit that I am somewhat underwhelmed.
I got the G1 shortly after it came out a year and a half or so ago, and the touchscreen definitely falls short of what it could be.
It is FAR less responsive than the iphone's, and the accuracy could indeed be better.
I was coming from a winmo 5 device, so i'm still incredibly happy with it, relatively speaking.
So the big question is whether or not all the manufs of android devices are using the same screen/screen chips, or if android has a fundamental problem interpreting data off the screen?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724446</id>
	<title>Re:Ah, groupthink</title>
	<author>Anonymous</author>
	<datestamp>1263231900000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p><div class="quote"><p>You don't have to hold this borderline view of the world in which computing devices are either God's work on Earth or Satan's playthings.</p></div><p>You obviously don't know any Republicans.</p></div>
	</htmltext>
<tokenext>You do n't have to hold this borderline view of the world in which computing devices are either God 's work on Earth or Satan 's playthings.You obviously do n't know any Republicans .</tokentext>
<sentencetext>You don't have to hold this borderline view of the world in which computing devices are either God's work on Earth or Satan's playthings.You obviously don't know any Republicans.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30757612</id>
	<title>Let's face it. Chunky fingers fail on these device</title>
	<author>DomainDominator</author>
	<datestamp>1263383640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>These virtual keyboards are for thin-fingered meth addicts.</htmltext>
<tokenext>These virtual keyboards are for thin-fingered meth addicts .</tokentext>
<sentencetext>These virtual keyboards are for thin-fingered meth addicts.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723684</id>
	<title>Re:Mechanical versus human testing...</title>
	<author>icegreentea</author>
	<datestamp>1263228120000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>Actually, cap screens work with any conductor. I mean, hell, a hot dog works on a iPhone. You could use that in your mechanical device. Though a giant metal probe would also work. But the hot dog is more fun, and probably gives better results... a lot more like a finger.</htmltext>
<tokenext>Actually , cap screens work with any conductor .
I mean , hell , a hot dog works on a iPhone .
You could use that in your mechanical device .
Though a giant metal probe would also work .
But the hot dog is more fun , and probably gives better results... a lot more like a finger .</tokentext>
<sentencetext>Actually, cap screens work with any conductor.
I mean, hell, a hot dog works on a iPhone.
You could use that in your mechanical device.
Though a giant metal probe would also work.
But the hot dog is more fun, and probably gives better results... a lot more like a finger.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723426</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723992</id>
	<title>My observations of my new Nexus Phone</title>
	<author>laing</author>
	<datestamp>1263229560000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>My wife and kids all have Iphones and I've used them.  I just got a Nexus phone and I love it.  I agree with the summation that the screen is not as responsive as the Apple phone.  It took me a bit of trial and error but I discovered that you must tap quickly to get the phone to respond well.  If you are slow it often seems to ignore the input.  This may be a software issue.  I hope that it is, and that it will be fixed soon.
<p>
I haven't yet seen anybody else make the following observation so I wonder if it's just my phone, but the audio level that comes out of the Nexus is noticeably lower than what comes out of the Iphone.  I can turn the volume on the thing all the way up and it is still very weak in comparison.  This applies to both ring tones and multimedia audio.  This is more likely to be a hardware issue so I will not hold my breath waiting for a fix.</p></htmltext>
<tokenext>My wife and kids all have Iphones and I 've used them .
I just got a Nexus phone and I love it .
I agree with the summation that the screen is not as responsive as the Apple phone .
It took me a bit of trial and error but I discovered that you must tap quickly to get the phone to respond well .
If you are slow it often seems to ignore the input .
This may be a software issue .
I hope that it is , and that it will be fixed soon .
I have n't yet seen anybody else make the following observation so I wonder if it 's just my phone , but the audio level that comes out of the Nexus is noticeably lower than what comes out of the Iphone .
I can turn the volume on the thing all the way up and it is still very weak in comparison .
This applies to both ring tones and multimedia audio .
This is more likely to be a hardware issue so I will not hold my breath waiting for a fix .</tokentext>
<sentencetext>My wife and kids all have Iphones and I've used them.
I just got a Nexus phone and I love it.
I agree with the summation that the screen is not as responsive as the Apple phone.
It took me a bit of trial and error but I discovered that you must tap quickly to get the phone to respond well.
If you are slow it often seems to ignore the input.
This may be a software issue.
I hope that it is, and that it will be fixed soon.
I haven't yet seen anybody else make the following observation so I wonder if it's just my phone, but the audio level that comes out of the Nexus is noticeably lower than what comes out of the Iphone.
I can turn the volume on the thing all the way up and it is still very weak in comparison.
This applies to both ring tones and multimedia audio.
This is more likely to be a hardware issue so I will not hold my breath waiting for a fix.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723790</id>
	<title>Re:So, restricted to capacitive screens</title>
	<author>Anonymous</author>
	<datestamp>1263228540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Redraw that using your fingertips and then we can talk.</p></htmltext>
<tokenext>Redraw that using your fingertips and then we can talk .</tokentext>
<sentencetext>Redraw that using your fingertips and then we can talk.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723156</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724930</id>
	<title>Moto Droid t/s is not great either</title>
	<author>jddj</author>
	<datestamp>1263233700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I basically like my Droid, but it's not without numerable faults.</p><p>The touchscreen isn't great (even forgiving that it doesn't do multi-touch like iPod/iPhone). When you're browsing a regular web page (something the Droid is up to, with its nice screen and good browser), sometimes the links are just too close to resolve the difference between them. Lots of frustrating touch...back...touch...back action going on.</p></htmltext>
<tokenext>I basically like my Droid , but it 's not without numerable faults.The touchscreen is n't great ( even forgiving that it does n't do multi-touch like iPod/iPhone ) .
When you 're browsing a regular web page ( something the Droid is up to , with its nice screen and good browser ) , sometimes the links are just too close to resolve the difference between them .
Lots of frustrating touch...back...touch...back action going on .</tokentext>
<sentencetext>I basically like my Droid, but it's not without numerable faults.The touchscreen isn't great (even forgiving that it doesn't do multi-touch like iPod/iPhone).
When you're browsing a regular web page (something the Droid is up to, with its nice screen and good browser), sometimes the links are just too close to resolve the difference between them.
Lots of frustrating touch...back...touch...back action going on.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723102</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723906</id>
	<title>If I was going to test the screen</title>
	<author>twoDigitIq</author>
	<datestamp>1263229080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>I would make a web page with many links placed close together. Have the same user try clicking the links in a certain order on both devices and record the accuracy. Repeat with multiple users.<br> <br>

BTW I am a Droid owner who has also used iPhone. I've made mistakes "clicking" on both devices but admittedly probably more on the droid. But the fact that the display <i>looks</i> so much better on the droid makes up for the occasional misclick.</htmltext>
<tokenext>I would make a web page with many links placed close together .
Have the same user try clicking the links in a certain order on both devices and record the accuracy .
Repeat with multiple users .
BTW I am a Droid owner who has also used iPhone .
I 've made mistakes " clicking " on both devices but admittedly probably more on the droid .
But the fact that the display looks so much better on the droid makes up for the occasional misclick .</tokentext>
<sentencetext>I would make a web page with many links placed close together.
Have the same user try clicking the links in a certain order on both devices and record the accuracy.
Repeat with multiple users.
BTW I am a Droid owner who has also used iPhone.
I've made mistakes "clicking" on both devices but admittedly probably more on the droid.
But the fact that the display looks so much better on the droid makes up for the occasional misclick.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723066</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>sznupi</author>
	<datestamp>1263225060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>It's perfectly fair if that "3rd generation" product came out half a year <i>before</i> "disadvantaged" contenders.</p><p>BTW, why only big touchscreen devices? There were supposed to be, y'know, cheap ones with Android by now.</p></htmltext>
<tokenext>It 's perfectly fair if that " 3rd generation " product came out half a year before " disadvantaged " contenders.BTW , why only big touchscreen devices ?
There were supposed to be , y'know , cheap ones with Android by now .</tokentext>
<sentencetext>It's perfectly fair if that "3rd generation" product came out half a year before "disadvantaged" contenders.BTW, why only big touchscreen devices?
There were supposed to be, y'know, cheap ones with Android by now.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723884</id>
	<title>Re:Ah, groupthink</title>
	<author>stewbacca</author>
	<datestamp>1263228960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If you are still pissed of about features that are now available, then you are every company's worst-customer-scenario personified.</p></htmltext>
<tokenext>If you are still pissed of about features that are now available , then you are every company 's worst-customer-scenario personified .</tokentext>
<sentencetext>If you are still pissed of about features that are now available, then you are every company's worst-customer-scenario personified.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723124</id>
	<title>Maybe, maybe not.</title>
	<author>sseaman</author>
	<datestamp>1263225360000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>While it's not likely that a smart phone user is going to draw a lot of lines, the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser."</p></div><p>A "gaming-grade" mouse and surface might have better sensitivity but I won't likely see a difference in browsing.</p></div>
	</htmltext>
<tokenext>While it 's not likely that a smart phone user is going to draw a lot of lines , the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser .
" A " gaming-grade " mouse and surface might have better sensitivity but I wo n't likely see a difference in browsing .</tokentext>
<sentencetext>While it's not likely that a smart phone user is going to draw a lot of lines, the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser.
"A "gaming-grade" mouse and surface might have better sensitivity but I won't likely see a difference in browsing.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042</id>
	<title>What generation of Iphone is being compared here ?</title>
	<author>parallel\_prankster</author>
	<datestamp>1263224880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>They dont seem to mention the Iphone generation anywhere. Is it fair to compare the third  generation of a product to new products out there right away ? I think other phones can pick up on touch sensitivity etc in future generations.</htmltext>
<tokenext>They dont seem to mention the Iphone generation anywhere .
Is it fair to compare the third generation of a product to new products out there right away ?
I think other phones can pick up on touch sensitivity etc in future generations .</tokentext>
<sentencetext>They dont seem to mention the Iphone generation anywhere.
Is it fair to compare the third  generation of a product to new products out there right away ?
I think other phones can pick up on touch sensitivity etc in future generations.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723502</id>
	<title>Silly test results...</title>
	<author>Wint3rhart</author>
	<datestamp>1263227220000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>"While it's not likely that a smart phone user is going to draw a lot of lines, the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser."  I don't suppose they considered instead testing which phones properly respond to clicking on links in Web browsers?</htmltext>
<tokenext>" While it 's not likely that a smart phone user is going to draw a lot of lines , the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser .
" I do n't suppose they considered instead testing which phones properly respond to clicking on links in Web browsers ?</tokentext>
<sentencetext>"While it's not likely that a smart phone user is going to draw a lot of lines, the test does give some indication of which phones are most likely to properly respond to clicking on a link in a Web browser.
"  I don't suppose they considered instead testing which phones properly respond to clicking on links in Web browsers?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723182</id>
	<title>Their conclusion is illogical.</title>
	<author>onion2k</author>
	<datestamp>1263225600000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>It doesn't follow that a lack of accuracy from dragging in a painting app would affect click accuracy in a browser at all. For example, the accuracy could degrade the longer you hold your finger to the screen due to moisture building up on your fingertip or due to reduced capacitance as the blood flow is restricted.</p><p>If you want to test point accuracy then write an app to test that; don't test something completely different and then leap to a potentially inaccurate conclusion.</p></htmltext>
<tokenext>It does n't follow that a lack of accuracy from dragging in a painting app would affect click accuracy in a browser at all .
For example , the accuracy could degrade the longer you hold your finger to the screen due to moisture building up on your fingertip or due to reduced capacitance as the blood flow is restricted.If you want to test point accuracy then write an app to test that ; do n't test something completely different and then leap to a potentially inaccurate conclusion .</tokentext>
<sentencetext>It doesn't follow that a lack of accuracy from dragging in a painting app would affect click accuracy in a browser at all.
For example, the accuracy could degrade the longer you hold your finger to the screen due to moisture building up on your fingertip or due to reduced capacitance as the blood flow is restricted.If you want to test point accuracy then write an app to test that; don't test something completely different and then leap to a potentially inaccurate conclusion.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727660</id>
	<title>Re:Couldn't repeat</title>
	<author>MrSenile</author>
	<datestamp>1263200820000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>I could repeat the results provided in the article, but I noticed that how 'sweaty' or 'oily' your finger is effects the results, as well as how fast you move your finger.</p><p>If I move my finger lethargically slow it gets more wiggles.  If I zip my finger across the screen, the lines are nearly perfectly straight, every single time.  It seems to show that the Droid tends to have different algos for their autocorrection.  Maybe they have more corrections a second going on than the iphone.  No idea.  Hard to tell without ripping the logic of both the drivers to see how it does autocorrection.  But I think this may be more a software/driver issue than hardware.</p><p>It seems the results are baked entirely on how you happen to test it, just like any other statistic, it should be taken with a grain of salt.</p></htmltext>
<tokenext>I could repeat the results provided in the article , but I noticed that how 'sweaty ' or 'oily ' your finger is effects the results , as well as how fast you move your finger.If I move my finger lethargically slow it gets more wiggles .
If I zip my finger across the screen , the lines are nearly perfectly straight , every single time .
It seems to show that the Droid tends to have different algos for their autocorrection .
Maybe they have more corrections a second going on than the iphone .
No idea .
Hard to tell without ripping the logic of both the drivers to see how it does autocorrection .
But I think this may be more a software/driver issue than hardware.It seems the results are baked entirely on how you happen to test it , just like any other statistic , it should be taken with a grain of salt .</tokentext>
<sentencetext>I could repeat the results provided in the article, but I noticed that how 'sweaty' or 'oily' your finger is effects the results, as well as how fast you move your finger.If I move my finger lethargically slow it gets more wiggles.
If I zip my finger across the screen, the lines are nearly perfectly straight, every single time.
It seems to show that the Droid tends to have different algos for their autocorrection.
Maybe they have more corrections a second going on than the iphone.
No idea.
Hard to tell without ripping the logic of both the drivers to see how it does autocorrection.
But I think this may be more a software/driver issue than hardware.It seems the results are baked entirely on how you happen to test it, just like any other statistic, it should be taken with a grain of salt.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724256</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723296</id>
	<title>Non-Issue</title>
	<author>LinuxAndLube</author>
	<datestamp>1263226200000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext>This is obviously a non-issue. Just wiggle your finger a bit to draw straight lines.</htmltext>
<tokenext>This is obviously a non-issue .
Just wiggle your finger a bit to draw straight lines .</tokentext>
<sentencetext>This is obviously a non-issue.
Just wiggle your finger a bit to draw straight lines.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30729552</id>
	<title>Re:What generation of Iphone is being compared her</title>
	<author>amRadioHed</author>
	<datestamp>1263207480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>There are cheap android phones out there. The T-Mobile Pulse is available in Europe for free with a contract.</p></htmltext>
<tokenext>There are cheap android phones out there .
The T-Mobile Pulse is available in Europe for free with a contract .</tokentext>
<sentencetext>There are cheap android phones out there.
The T-Mobile Pulse is available in Europe for free with a contract.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723066</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723538</id>
	<title>YUO FAIL IT</title>
	<author>Anonymous</author>
	<datestamp>1263227400000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><A HREF="http://goat.cx/" title="goat.cx" rel="nofollow">gave the BSD troubles of Walnut which aalows</a> [goat.cx]</htmltext>
<tokenext>gave the BSD troubles of Walnut which aalows [ goat.cx ]</tokentext>
<sentencetext>gave the BSD troubles of Walnut which aalows [goat.cx]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30730612</id>
	<title>Shocking!</title>
	<author>stokessd</author>
	<datestamp>1263212100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Let me see if I have this right...</p><p>A company that strives to make high quality well-thought out expensive hardware has made high quality hardware.</p><p>Think what you will about apple, but the GUI and user experience has always been their strong suit and it shows in the subtleties of the iPhone.</p><p>Sheldon</p></htmltext>
<tokenext>Let me see if I have this right...A company that strives to make high quality well-thought out expensive hardware has made high quality hardware.Think what you will about apple , but the GUI and user experience has always been their strong suit and it shows in the subtleties of the iPhone.Sheldon</tokentext>
<sentencetext>Let me see if I have this right...A company that strives to make high quality well-thought out expensive hardware has made high quality hardware.Think what you will about apple, but the GUI and user experience has always been their strong suit and it shows in the subtleties of the iPhone.Sheldon</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723272</id>
	<title>thicker lines</title>
	<author>freetolio</author>
	<datestamp>1263225960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>A thicker line would exacerbate wave effects.</htmltext>
<tokenext>A thicker line would exacerbate wave effects .</tokentext>
<sentencetext>A thicker line would exacerbate wave effects.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724026</id>
	<title>Droid Eris User</title>
	<author>Odin\_Tiger</author>
	<datestamp>1263229740000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>I have a Droid Eris, and as a guy with bigger hands that usually has trouble with these kinds of devices, I have to say I'm very happy with the accuracy - I almost never make a mis-click, even typing quite fast on the touchscreen keyboard.  <br> <i>However</i>, I'm disappointed in responsiveness.  The interface reminds me of playing an online game on a shitty internet connection when your roommate is loading a new YouTube video ever few minutes - without warning, for no apparent reason, and rarely in doing the same action twice, a click / tap will take up to 2 or 3 seconds to register.  It's <i>accurate</i>, sure, but that's meaningless when I can't tell whether the thing is froze up or it just didn't detect my click, and don't dare click again for fear of accidentally clicking whatever happens to be in that same spot on the next page if the first click <i>did</i> register.</htmltext>
<tokenext>I have a Droid Eris , and as a guy with bigger hands that usually has trouble with these kinds of devices , I have to say I 'm very happy with the accuracy - I almost never make a mis-click , even typing quite fast on the touchscreen keyboard .
However , I 'm disappointed in responsiveness .
The interface reminds me of playing an online game on a shitty internet connection when your roommate is loading a new YouTube video ever few minutes - without warning , for no apparent reason , and rarely in doing the same action twice , a click / tap will take up to 2 or 3 seconds to register .
It 's accurate , sure , but that 's meaningless when I ca n't tell whether the thing is froze up or it just did n't detect my click , and do n't dare click again for fear of accidentally clicking whatever happens to be in that same spot on the next page if the first click did register .</tokentext>
<sentencetext>I have a Droid Eris, and as a guy with bigger hands that usually has trouble with these kinds of devices, I have to say I'm very happy with the accuracy - I almost never make a mis-click, even typing quite fast on the touchscreen keyboard.
However, I'm disappointed in responsiveness.
The interface reminds me of playing an online game on a shitty internet connection when your roommate is loading a new YouTube video ever few minutes - without warning, for no apparent reason, and rarely in doing the same action twice, a click / tap will take up to 2 or 3 seconds to register.
It's accurate, sure, but that's meaningless when I can't tell whether the thing is froze up or it just didn't detect my click, and don't dare click again for fear of accidentally clicking whatever happens to be in that same spot on the next page if the first click did register.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723286</id>
	<title>palm pre has a capacitive screen</title>
	<author>Anonymous</author>
	<datestamp>1263226080000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>but they left it out. I'm looking to move to verizon just to get one once the new pre++ or w/e comes out later this month.</htmltext>
<tokenext>but they left it out .
I 'm looking to move to verizon just to get one once the new pre + + or w/e comes out later this month .</tokentext>
<sentencetext>but they left it out.
I'm looking to move to verizon just to get one once the new pre++ or w/e comes out later this month.</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30728752
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724256
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723164
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723058
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30733986
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727660
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724256
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723276
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724928
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30728844
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723058
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724564
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723502
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723456
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723058
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723072
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30743680
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30722978
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723884
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723550
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723360
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723646
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723426
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723190
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724082
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723082
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30729866
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723182
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723266
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723654
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723232
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725206
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725316
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723502
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727412
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723510
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723102
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723994
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723232
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30726708
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723190
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725856
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724256
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724446
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30729552
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723066
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723192
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723454
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723684
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723426
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723190
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723336
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723232
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727976
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30722978
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725218
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723928
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723502
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723126
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30722978
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723604
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723190
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725836
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725820
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723790
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723156
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724128
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727224
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724186
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723058
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725644
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724930
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723102
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30737074
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30731984
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723518
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723062
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727584
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723232
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_11_1411200_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30737196
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724090
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724094
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724256
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727660
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30733986
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725856
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30728752
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30722978
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30743680
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727976
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723126
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723124
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723360
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723550
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723062
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723518
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30731984
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723232
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727584
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723994
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723336
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723654
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723168
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724180
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723058
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723456
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30728844
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723164
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724186
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727224
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723502
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723928
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724564
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725316
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724026
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723102
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723510
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724930
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723156
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723790
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723992
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723286
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724906
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723340
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723434
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724082
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724128
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723884
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725206
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723876
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724928
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725644
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30727412
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725836
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30737196
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725820
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30724446
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30737074
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723182
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30729866
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723042
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723066
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30729552
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723192
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723190
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723426
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723646
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723684
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723604
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30726708
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723082
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723266
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723276
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723454
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30725218
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723072
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723382
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_11_1411200.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_11_1411200.30723108
</commentlist>
</conversation>
