<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_11_24_1557239</id>
	<title>Giving Touch-Screen Buttons Depth and Height With Pneumatics</title>
	<author>timothy</author>
	<datestamp>1259079240000</datestamp>
	<htmltext>blee37 writes <i>"Researchers at Carnegie Mellon demonstrate <a href="http://scitedaily.wordpress.com/2009/11/24/unflattening-the-touch-screen/">'popping out' touch screen buttons to become physical buttons</a> using pneumatics.  The idea is to combine the dynamic reconfigurability of touch screen buttons with the tactile feedback of real buttons.  The technology could be applied where tactile feedback is currently lacking, such as in car navigation systems, ATMs, or cell phones."</i></htmltext>
<tokenext>blee37 writes " Researchers at Carnegie Mellon demonstrate 'popping out ' touch screen buttons to become physical buttons using pneumatics .
The idea is to combine the dynamic reconfigurability of touch screen buttons with the tactile feedback of real buttons .
The technology could be applied where tactile feedback is currently lacking , such as in car navigation systems , ATMs , or cell phones .
"</tokentext>
<sentencetext>blee37 writes "Researchers at Carnegie Mellon demonstrate 'popping out' touch screen buttons to become physical buttons using pneumatics.
The idea is to combine the dynamic reconfigurability of touch screen buttons with the tactile feedback of real buttons.
The technology could be applied where tactile feedback is currently lacking, such as in car navigation systems, ATMs, or cell phones.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217458</id>
	<title>Resistive</title>
	<author>Anonymous</author>
	<datestamp>1259094900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Don't resistive TSs have "feedback" in the form of the two layers touching?</htmltext>
<tokenext>Do n't resistive TSs have " feedback " in the form of the two layers touching ?</tokentext>
<sentencetext>Don't resistive TSs have "feedback" in the form of the two layers touching?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217480</id>
	<title>Re:Why Not...</title>
	<author>Origimist</author>
	<datestamp>1259094960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>...Or am I completely missing the point?</p></div><p>Missing the point.  The point is to reconfigure the screen on the fly.  Imagine if your touch phone could pop up a physical 10 digit numerical keypad when in call mode, then a 30 button qwerty keyboard when in text/email mode, then play/pause/stop/next track buttons when in music mode, etc.

One screen, many possible interfaces depending on application, but with tactile feedback.</p></div>
	</htmltext>
<tokenext>...Or am I completely missing the point ? Missing the point .
The point is to reconfigure the screen on the fly .
Imagine if your touch phone could pop up a physical 10 digit numerical keypad when in call mode , then a 30 button qwerty keyboard when in text/email mode , then play/pause/stop/next track buttons when in music mode , etc .
One screen , many possible interfaces depending on application , but with tactile feedback .</tokentext>
<sentencetext>...Or am I completely missing the point?Missing the point.
The point is to reconfigure the screen on the fly.
Imagine if your touch phone could pop up a physical 10 digit numerical keypad when in call mode, then a 30 button qwerty keyboard when in text/email mode, then play/pause/stop/next track buttons when in music mode, etc.
One screen, many possible interfaces depending on application, but with tactile feedback.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216516</id>
	<title>Re:Why Not...</title>
	<author>ubercam</author>
	<datestamp>1259090100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Ever use a Blackberry Storm 9500/9530? It's a touch screen/giant button. There's one button behind the screen and you have to click it down to register a button press. It works ok, but apparently the Storm 2 (9520/9550) is much better in that regard. There are apparently 4 screen buttons, one in each corner and it allows multiple simultaneous button presses, making it much easier to type. The first iteration only allows one at a time. You can do multitouch for things like selecting text, and there used to be a flick-scrolling bug in one of the earlier OS 5.0 leaks that let you scroll down a page about half way if you held 2 fingers on the screen for a moment, but that's been fixed in the official 5.0 release. It was awesome for zipping to the bottom of EULAs hehe.</p><p>That being said, I've never used or seen a Storm 2 and I own a Storm 1. It's hard to type without looking, but I'm getting the hang of it. When it comes time to upgrade it, I'm going with a keyboard device, likely the latest version of the Bold or whatever's best at the time. My buddy has a Bold 9000 and it's really nice. I like buttons. Another friend is debating getting a Blackberry and I've recommended against the Storm in favour of a model with a keyboard, like a Curve, Bold or Tour, depending on the operator he chooses. The ones with the new optical trackpads are fantastic.</p><p>Sorry if that sounds fanboi-ish but I happen to really like Blackberries and I'm happy I have one, despite the ridiculous monthly bill.</p></htmltext>
<tokenext>Ever use a Blackberry Storm 9500/9530 ?
It 's a touch screen/giant button .
There 's one button behind the screen and you have to click it down to register a button press .
It works ok , but apparently the Storm 2 ( 9520/9550 ) is much better in that regard .
There are apparently 4 screen buttons , one in each corner and it allows multiple simultaneous button presses , making it much easier to type .
The first iteration only allows one at a time .
You can do multitouch for things like selecting text , and there used to be a flick-scrolling bug in one of the earlier OS 5.0 leaks that let you scroll down a page about half way if you held 2 fingers on the screen for a moment , but that 's been fixed in the official 5.0 release .
It was awesome for zipping to the bottom of EULAs hehe.That being said , I 've never used or seen a Storm 2 and I own a Storm 1 .
It 's hard to type without looking , but I 'm getting the hang of it .
When it comes time to upgrade it , I 'm going with a keyboard device , likely the latest version of the Bold or whatever 's best at the time .
My buddy has a Bold 9000 and it 's really nice .
I like buttons .
Another friend is debating getting a Blackberry and I 've recommended against the Storm in favour of a model with a keyboard , like a Curve , Bold or Tour , depending on the operator he chooses .
The ones with the new optical trackpads are fantastic.Sorry if that sounds fanboi-ish but I happen to really like Blackberries and I 'm happy I have one , despite the ridiculous monthly bill .</tokentext>
<sentencetext>Ever use a Blackberry Storm 9500/9530?
It's a touch screen/giant button.
There's one button behind the screen and you have to click it down to register a button press.
It works ok, but apparently the Storm 2 (9520/9550) is much better in that regard.
There are apparently 4 screen buttons, one in each corner and it allows multiple simultaneous button presses, making it much easier to type.
The first iteration only allows one at a time.
You can do multitouch for things like selecting text, and there used to be a flick-scrolling bug in one of the earlier OS 5.0 leaks that let you scroll down a page about half way if you held 2 fingers on the screen for a moment, but that's been fixed in the official 5.0 release.
It was awesome for zipping to the bottom of EULAs hehe.That being said, I've never used or seen a Storm 2 and I own a Storm 1.
It's hard to type without looking, but I'm getting the hang of it.
When it comes time to upgrade it, I'm going with a keyboard device, likely the latest version of the Bold or whatever's best at the time.
My buddy has a Bold 9000 and it's really nice.
I like buttons.
Another friend is debating getting a Blackberry and I've recommended against the Storm in favour of a model with a keyboard, like a Curve, Bold or Tour, depending on the operator he chooses.
The ones with the new optical trackpads are fantastic.Sorry if that sounds fanboi-ish but I happen to really like Blackberries and I'm happy I have one, despite the ridiculous monthly bill.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215086</id>
	<title>Re:Oh no...</title>
	<author>Anonymous</author>
	<datestamp>1259083740000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>It will be great for people who can't drive.  Like the blind or those with limited vision.</htmltext>
<tokenext>It will be great for people who ca n't drive .
Like the blind or those with limited vision .</tokentext>
<sentencetext>It will be great for people who can't drive.
Like the blind or those with limited vision.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216452</id>
	<title>Re:Visual feedback</title>
	<author>Anonymous</author>
	<datestamp>1259089740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I used to touch-type all the time without looking at the phone - until I started using a phone with a touch screen.  You can't imagine many scenarios where you wouldn't be looking at the screen, but it's because it seems clear you haven't used other phones that present this as a plausible scenario.  Your signature implies a certain bias as well.</p></htmltext>
<tokenext>I used to touch-type all the time without looking at the phone - until I started using a phone with a touch screen .
You ca n't imagine many scenarios where you would n't be looking at the screen , but it 's because it seems clear you have n't used other phones that present this as a plausible scenario .
Your signature implies a certain bias as well .</tokentext>
<sentencetext>I used to touch-type all the time without looking at the phone - until I started using a phone with a touch screen.
You can't imagine many scenarios where you wouldn't be looking at the screen, but it's because it seems clear you haven't used other phones that present this as a plausible scenario.
Your signature implies a certain bias as well.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214992</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216542</id>
	<title>Re:Visual feedback</title>
	<author>StikyPad</author>
	<datestamp>1259090280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Hmm.. I still have issues with the touch keyboard, even after a year+.  Especially annoying is typing in portrait mode, followed closely by top-row typing where I accidentally move the cursor (touch the text display area) instead of hitting the key I intended, followed next by inadvertent Space or Enter keypresses.  Hitting the wrong key is something that happens even on a full-size keyboard, but it's pretty rare that I inadvertently do any of the above.  If the iPhone had a model with a slide-out keyboard, I'd be all over it like smears on a touchscreen.</p></htmltext>
<tokenext>Hmm.. I still have issues with the touch keyboard , even after a year + .
Especially annoying is typing in portrait mode , followed closely by top-row typing where I accidentally move the cursor ( touch the text display area ) instead of hitting the key I intended , followed next by inadvertent Space or Enter keypresses .
Hitting the wrong key is something that happens even on a full-size keyboard , but it 's pretty rare that I inadvertently do any of the above .
If the iPhone had a model with a slide-out keyboard , I 'd be all over it like smears on a touchscreen .</tokentext>
<sentencetext>Hmm.. I still have issues with the touch keyboard, even after a year+.
Especially annoying is typing in portrait mode, followed closely by top-row typing where I accidentally move the cursor (touch the text display area) instead of hitting the key I intended, followed next by inadvertent Space or Enter keypresses.
Hitting the wrong key is something that happens even on a full-size keyboard, but it's pretty rare that I inadvertently do any of the above.
If the iPhone had a model with a slide-out keyboard, I'd be all over it like smears on a touchscreen.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214992</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215442</id>
	<title>Re:Oh no...</title>
	<author>KneelBeforeZod</author>
	<datestamp>1259085180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>exactly!  I'd say more research is required so we can give the blind more access to info tech.</htmltext>
<tokenext>exactly !
I 'd say more research is required so we can give the blind more access to info tech .</tokentext>
<sentencetext>exactly!
I'd say more research is required so we can give the blind more access to info tech.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215086</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215010</id>
	<title>Re-post?</title>
	<author>Anonymous</author>
	<datestamp>1259083500000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>I could swear I read about this on<nobr> <wbr></nobr>/. several months ago... at the very least, this story is OLD. Looks like some blogger just rehashed it from back in April (link is not<nobr> <wbr></nobr>/., obviously).</p><p>http://www.engadget.com/2009/04/28/carnegie-mellon-morphs-pop-up-buttons-onto-multi-touch-display</p></htmltext>
<tokenext>I could swear I read about this on / .
several months ago... at the very least , this story is OLD .
Looks like some blogger just rehashed it from back in April ( link is not /. , obviously ) .http : //www.engadget.com/2009/04/28/carnegie-mellon-morphs-pop-up-buttons-onto-multi-touch-display</tokentext>
<sentencetext>I could swear I read about this on /.
several months ago... at the very least, this story is OLD.
Looks like some blogger just rehashed it from back in April (link is not /., obviously).http://www.engadget.com/2009/04/28/carnegie-mellon-morphs-pop-up-buttons-onto-multi-touch-display</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217110</id>
	<title>Re:Oh no...</title>
	<author>orgelspieler</author>
	<datestamp>1259093040000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>Actually, several of these nav systems have mode to get directions when walking about. So I don't see why it would be a bad idea to make this more accessible for blind people. Providing a touchable map of the area could prove quite useful. Also, raised buttons would let them know where to press.</htmltext>
<tokenext>Actually , several of these nav systems have mode to get directions when walking about .
So I do n't see why it would be a bad idea to make this more accessible for blind people .
Providing a touchable map of the area could prove quite useful .
Also , raised buttons would let them know where to press .</tokentext>
<sentencetext>Actually, several of these nav systems have mode to get directions when walking about.
So I don't see why it would be a bad idea to make this more accessible for blind people.
Providing a touchable map of the area could prove quite useful.
Also, raised buttons would let them know where to press.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215086</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30220908</id>
	<title>Re:Why Not...</title>
	<author>Idiomatick</author>
	<datestamp>1259067900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Totally. " dynamic reconfigurability"</htmltext>
<tokenext>Totally .
" dynamic reconfigurability "</tokentext>
<sentencetext>Totally.
" dynamic reconfigurability"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216354</id>
	<title>Re:Er</title>
	<author>StikyPad</author>
	<datestamp>1259089380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What's your weight got to do with it?</p><p>Ba-dum pshh.</p></htmltext>
<tokenext>What 's your weight got to do with it ? Ba-dum pshh .</tokentext>
<sentencetext>What's your weight got to do with it?Ba-dum pshh.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215218</id>
	<title>Electroactive polymers?</title>
	<author>Abcd1234</author>
	<datestamp>1259084280000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>I thought people were already trying to do this sort of thing using <a href="http://en.wikipedia.org/wiki/Electroactive\_polymers" title="wikipedia.org">electroactive polymers</a> [wikipedia.org].  Certainly there seems to be a <a href="http://www.freepatentsonline.com/7511706.html" title="freepatentsonline.com">couple</a> [freepatentsonline.com] <a href="http://www.patentstorm.us/patents/7339572/claims.html" title="patentstorm.us">patents</a> [patentstorm.us] on the <a href="http://www.faqs.org/patents/app/20090001855" title="faqs.org">idea</a> [faqs.org], not to mention someone who thinks the technology could be used to make <a href="http://www.popsci.com/scitech/article/2009-08/iphones-blind" title="popsci.com">braille-capable touchscreens</a> [popsci.com].</p></htmltext>
<tokenext>I thought people were already trying to do this sort of thing using electroactive polymers [ wikipedia.org ] .
Certainly there seems to be a couple [ freepatentsonline.com ] patents [ patentstorm.us ] on the idea [ faqs.org ] , not to mention someone who thinks the technology could be used to make braille-capable touchscreens [ popsci.com ] .</tokentext>
<sentencetext>I thought people were already trying to do this sort of thing using electroactive polymers [wikipedia.org].
Certainly there seems to be a couple [freepatentsonline.com] patents [patentstorm.us] on the idea [faqs.org], not to mention someone who thinks the technology could be used to make braille-capable touchscreens [popsci.com].</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30221264</id>
	<title>Re:Why Not...</title>
	<author>Anonymous</author>
	<datestamp>1259070060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This tech would be extremely useful for the blind.  Imagine a deaf/blind person being able to use a cellphone to send/receive messages.... of course, they probably don't have the tech to the point where it can make dots small enough to represent braille, but I still think it's a cool idea.</p></htmltext>
<tokenext>This tech would be extremely useful for the blind .
Imagine a deaf/blind person being able to use a cellphone to send/receive messages.... of course , they probably do n't have the tech to the point where it can make dots small enough to represent braille , but I still think it 's a cool idea .</tokentext>
<sentencetext>This tech would be extremely useful for the blind.
Imagine a deaf/blind person being able to use a cellphone to send/receive messages.... of course, they probably don't have the tech to the point where it can make dots small enough to represent braille, but I still think it's a cool idea.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216368</id>
	<title>Re:Why Not...</title>
	<author>Hurricane78</author>
	<datestamp>1259089380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The idea is to make it possible to *change* the layout! Unless you have single-pixel buttons that are electronically raisable, you can&rsquo;t do that with buttons.</p><p>Imagine a big red button that says *NUKE* and a load of info displays and buttons on a surface that lies in the location of your keyboard, when playing your mech game. (Mechwarrior was famous for needing a mouse, a joystick *and* a keyboard to properly play it. And I *loved* it for the ability to look, move and shoot in 3 different directions!<nobr> <wbr></nobr>:D)</p></htmltext>
<tokenext>The idea is to make it possible to * change * the layout !
Unless you have single-pixel buttons that are electronically raisable , you can    t do that with buttons.Imagine a big red button that says * NUKE * and a load of info displays and buttons on a surface that lies in the location of your keyboard , when playing your mech game .
( Mechwarrior was famous for needing a mouse , a joystick * and * a keyboard to properly play it .
And I * loved * it for the ability to look , move and shoot in 3 different directions !
: D )</tokentext>
<sentencetext>The idea is to make it possible to *change* the layout!
Unless you have single-pixel buttons that are electronically raisable, you can’t do that with buttons.Imagine a big red button that says *NUKE* and a load of info displays and buttons on a surface that lies in the location of your keyboard, when playing your mech game.
(Mechwarrior was famous for needing a mouse, a joystick *and* a keyboard to properly play it.
And I *loved* it for the ability to look, move and shoot in 3 different directions!
:D)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216070</id>
	<title>I'd like to see ...</title>
	<author>PPH</author>
	<datestamp>1259088120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>... the obligatory Rule 34 implementation. Well, maybe not just <b>see</b> it<nobr> <wbr></nobr>......</htmltext>
<tokenext>... the obligatory Rule 34 implementation .
Well , maybe not just see it ..... .</tokentext>
<sentencetext>... the obligatory Rule 34 implementation.
Well, maybe not just see it ......</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217398</id>
	<title>Re:Er</title>
	<author>pete-classic</author>
	<datestamp>1259094600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I had the same concern before I bought an iPhone.  (And I was <a href="http://apple.slashdot.org/comments.pl?sid=158849&amp;cid=13306032" title="slashdot.org" rel="nofollow">mildly</a> [slashdot.org] <a href="http://apple.slashdot.org/comments.pl?sid=114729&amp;cid=9717224" title="slashdot.org" rel="nofollow">anti-Apple</a> [slashdot.org] at the time.  I'm now a Mac convert.)</p><p>The advantages of the fully re-configurable UI outweigh the advantages of tactile buttons by leaps and bounds.  For me anyway.  I'd welcome the addition of configurable tactile buttons on top of a dynamic visual UI, but, given the choice, there's no question in my mind.</p><p>Of course, this assumes a complex device like a smartphone.  The GUI gives no advantage -- and the advantage of hard buttons come to the fore -- with a simple device like the single-function candybar phone I was using ten years ago.</p><p>-Peter</p></htmltext>
<tokenext>I had the same concern before I bought an iPhone .
( And I was mildly [ slashdot.org ] anti-Apple [ slashdot.org ] at the time .
I 'm now a Mac convert .
) The advantages of the fully re-configurable UI outweigh the advantages of tactile buttons by leaps and bounds .
For me anyway .
I 'd welcome the addition of configurable tactile buttons on top of a dynamic visual UI , but , given the choice , there 's no question in my mind.Of course , this assumes a complex device like a smartphone .
The GUI gives no advantage -- and the advantage of hard buttons come to the fore -- with a simple device like the single-function candybar phone I was using ten years ago.-Peter</tokentext>
<sentencetext>I had the same concern before I bought an iPhone.
(And I was mildly [slashdot.org] anti-Apple [slashdot.org] at the time.
I'm now a Mac convert.
)The advantages of the fully re-configurable UI outweigh the advantages of tactile buttons by leaps and bounds.
For me anyway.
I'd welcome the addition of configurable tactile buttons on top of a dynamic visual UI, but, given the choice, there's no question in my mind.Of course, this assumes a complex device like a smartphone.
The GUI gives no advantage -- and the advantage of hard buttons come to the fore -- with a simple device like the single-function candybar phone I was using ten years ago.-Peter</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216242</id>
	<title>Re:Pricetag? Reliability?</title>
	<author>IndustrialComplex</author>
	<datestamp>1259088960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>And what would be the actual pricetag of such a device? I understand that we use more and more electronics to simplify the mechanics behind our devices. Now, with a pump, you need to physically inject air under the screen, so you have moving parts, and they are usually costly... besides, what would be the reliability of such a thing? and could you get a "flat" screen?</i></p><p>Instead of air, Ferrofluids might be a solution.</p></htmltext>
<tokenext>And what would be the actual pricetag of such a device ?
I understand that we use more and more electronics to simplify the mechanics behind our devices .
Now , with a pump , you need to physically inject air under the screen , so you have moving parts , and they are usually costly... besides , what would be the reliability of such a thing ?
and could you get a " flat " screen ? Instead of air , Ferrofluids might be a solution .</tokentext>
<sentencetext>And what would be the actual pricetag of such a device?
I understand that we use more and more electronics to simplify the mechanics behind our devices.
Now, with a pump, you need to physically inject air under the screen, so you have moving parts, and they are usually costly... besides, what would be the reliability of such a thing?
and could you get a "flat" screen?Instead of air, Ferrofluids might be a solution.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215042</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30219518</id>
	<title>Re:killer app</title>
	<author>Anonymous</author>
	<datestamp>1259060940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>A T-1000 ?</htmltext>
<tokenext>A T-1000 ?</tokentext>
<sentencetext>A T-1000 ?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215226</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215438</id>
	<title>hmmm</title>
	<author>Anonymous</author>
	<datestamp>1259085180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Sounds like the BlackBerry Storm... but on a whole new level.</p></htmltext>
<tokenext>Sounds like the BlackBerry Storm... but on a whole new level .</tokentext>
<sentencetext>Sounds like the BlackBerry Storm... but on a whole new level.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216460</id>
	<title>Re:Er</title>
	<author>Quiet\_Desperation</author>
	<datestamp>1259089740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I get that- I wouldn't want to type all day on a touch keyboard, for example- but I find audio clues, like a click, to be almost as good with a display you only need to deal with on occasion. It's a tradeoff.</htmltext>
<tokenext>I get that- I would n't want to type all day on a touch keyboard , for example- but I find audio clues , like a click , to be almost as good with a display you only need to deal with on occasion .
It 's a tradeoff .</tokentext>
<sentencetext>I get that- I wouldn't want to type all day on a touch keyboard, for example- but I find audio clues, like a click, to be almost as good with a display you only need to deal with on occasion.
It's a tradeoff.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840</id>
	<title>Oh no...</title>
	<author>Anonymous</author>
	<datestamp>1259082960000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>This is a <b>BAD</b> idea for in-car SatNav/GPS.</p><p>Anything that might make drivers think they can set/adjust something by reaching and groping when they should be concentrating on driving will cause accidents.</p></htmltext>
<tokenext>This is a BAD idea for in-car SatNav/GPS.Anything that might make drivers think they can set/adjust something by reaching and groping when they should be concentrating on driving will cause accidents .</tokentext>
<sentencetext>This is a BAD idea for in-car SatNav/GPS.Anything that might make drivers think they can set/adjust something by reaching and groping when they should be concentrating on driving will cause accidents.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215144</id>
	<title>useless at this stage</title>
	<author>Tom</author>
	<datestamp>1259083920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>An unavoidable limitation is that the mask itself is static, meaning that new shapes cannot be created dynamically.  The technology only allows controlling whether the shapes pop in, pop out, or remain flat.</p></div><p>That makes it useless for all but a few uncommon use cases. But it may be the beginning of something, maybe another team will come up on a way to create a programmable mask.</p></div>
	</htmltext>
<tokenext>An unavoidable limitation is that the mask itself is static , meaning that new shapes can not be created dynamically .
The technology only allows controlling whether the shapes pop in , pop out , or remain flat.That makes it useless for all but a few uncommon use cases .
But it may be the beginning of something , maybe another team will come up on a way to create a programmable mask .</tokentext>
<sentencetext>An unavoidable limitation is that the mask itself is static, meaning that new shapes cannot be created dynamically.
The technology only allows controlling whether the shapes pop in, pop out, or remain flat.That makes it useless for all but a few uncommon use cases.
But it may be the beginning of something, maybe another team will come up on a way to create a programmable mask.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216148</id>
	<title>Re:Oh no...</title>
	<author>Hurricane78</author>
	<datestamp>1259088480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>But it&rsquo;s great for natural selection! Just stay off the roads for some weeks (don&rsquo;t forget friends and family), and let nature do its thing.<nobr> <wbr></nobr>:D</p></htmltext>
<tokenext>But it    s great for natural selection !
Just stay off the roads for some weeks ( don    t forget friends and family ) , and let nature do its thing .
: D</tokentext>
<sentencetext>But it’s great for natural selection!
Just stay off the roads for some weeks (don’t forget friends and family), and let nature do its thing.
:D</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215172</id>
	<title>Why?</title>
	<author>Anonymous</author>
	<datestamp>1259084040000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Weren't touch-screens the latest rage because.. you didn't have to.. push... buttons?</p></htmltext>
<tokenext>Were n't touch-screens the latest rage because.. you did n't have to.. push... buttons ?</tokentext>
<sentencetext>Weren't touch-screens the latest rage because.. you didn't have to.. push... buttons?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214890</id>
	<title>"a$$ and tittiez!"</title>
	<author>Anonymous</author>
	<datestamp>1259083080000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>0</modscore>
	<htmltext><p>So porn sites will be able to have interactive women in 3-d on touchscreens? SWEET!</p></htmltext>
<tokenext>So porn sites will be able to have interactive women in 3-d on touchscreens ?
SWEET !</tokentext>
<sentencetext>So porn sites will be able to have interactive women in 3-d on touchscreens?
SWEET!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30220238</id>
	<title>All i am thinking of...</title>
	<author>Anonymous</author>
	<datestamp>1259064300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>is how amazing if a bubble-wrap app was made with these buttons. (drools at thought of infinite bubble wrap)</p></htmltext>
<tokenext>is how amazing if a bubble-wrap app was made with these buttons .
( drools at thought of infinite bubble wrap )</tokentext>
<sentencetext>is how amazing if a bubble-wrap app was made with these buttons.
(drools at thought of infinite bubble wrap)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215364</id>
	<title>something about pizza</title>
	<author>metamechanical</author>
	<datestamp>1259084820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I feel like there is some sort of pertinent pizza-based analogy here... something about how when the crust has larger bubbles, it's a more rich and textural experience... I'm not sure though, as pizza-based analogies aren't really my expertise...</htmltext>
<tokenext>I feel like there is some sort of pertinent pizza-based analogy here... something about how when the crust has larger bubbles , it 's a more rich and textural experience... I 'm not sure though , as pizza-based analogies are n't really my expertise.. .</tokentext>
<sentencetext>I feel like there is some sort of pertinent pizza-based analogy here... something about how when the crust has larger bubbles, it's a more rich and textural experience... I'm not sure though, as pizza-based analogies aren't really my expertise...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216278</id>
	<title>Re:Er</title>
	<author>Hurricane78</author>
	<datestamp>1259089080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It always depends on if it&rsquo;s worth it. I think you can do pneumatics entierly without moving parts. Or if you have to, one single part. (I don't count the moving surface as a part.</p><p>On the other hand, the buttons on all old phones and the buttons that you used to type your comment, are moving parts. You don't see them falling apart, do you?</p><p>At least not until you replace them by something better anyway.</p><p>So all in all, oh yeah, I think it is worth a ton to finally have a real touch-typable keyboard, that you can also make into a dashboard with a big red button that says *nuke* for your next mech game.<nobr> <wbr></nobr>:D</p></htmltext>
<tokenext>It always depends on if it    s worth it .
I think you can do pneumatics entierly without moving parts .
Or if you have to , one single part .
( I do n't count the moving surface as a part.On the other hand , the buttons on all old phones and the buttons that you used to type your comment , are moving parts .
You do n't see them falling apart , do you ? At least not until you replace them by something better anyway.So all in all , oh yeah , I think it is worth a ton to finally have a real touch-typable keyboard , that you can also make into a dashboard with a big red button that says * nuke * for your next mech game .
: D</tokentext>
<sentencetext>It always depends on if it’s worth it.
I think you can do pneumatics entierly without moving parts.
Or if you have to, one single part.
(I don't count the moving surface as a part.On the other hand, the buttons on all old phones and the buttons that you used to type your comment, are moving parts.
You don't see them falling apart, do you?At least not until you replace them by something better anyway.So all in all, oh yeah, I think it is worth a ton to finally have a real touch-typable keyboard, that you can also make into a dashboard with a big red button that says *nuke* for your next mech game.
:D</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215288</id>
	<title>Immersion Corporation</title>
	<author>Anonymous</author>
	<datestamp>1259084520000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Immersion Corporation is a small technology company that is also providing haptic (touch) feedback for a variety of electronics, including touch screens. They have the technology to make a flat button on a touch screen feel like it is a 3-dimensional button being depressed and it isn't confined to a single configuration. Lg, Samsung, and Nokia already license Immersion's technology and mobile phones with touch feedback are already being sold in Asia. In my opinion, this latex button is a good idea but it won't catch on.</htmltext>
<tokenext>Immersion Corporation is a small technology company that is also providing haptic ( touch ) feedback for a variety of electronics , including touch screens .
They have the technology to make a flat button on a touch screen feel like it is a 3-dimensional button being depressed and it is n't confined to a single configuration .
Lg , Samsung , and Nokia already license Immersion 's technology and mobile phones with touch feedback are already being sold in Asia .
In my opinion , this latex button is a good idea but it wo n't catch on .</tokentext>
<sentencetext>Immersion Corporation is a small technology company that is also providing haptic (touch) feedback for a variety of electronics, including touch screens.
They have the technology to make a flat button on a touch screen feel like it is a 3-dimensional button being depressed and it isn't confined to a single configuration.
Lg, Samsung, and Nokia already license Immersion's technology and mobile phones with touch feedback are already being sold in Asia.
In my opinion, this latex button is a good idea but it won't catch on.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918</id>
	<title>Er</title>
	<author>Quiet\_Desperation</author>
	<datestamp>1259083140000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>Touch screens are nice because they can be programmed to display whatever controls you wish, but isn't the lack of moving parts another advantage? This seems like it would have MTBF issues.</htmltext>
<tokenext>Touch screens are nice because they can be programmed to display whatever controls you wish , but is n't the lack of moving parts another advantage ?
This seems like it would have MTBF issues .</tokentext>
<sentencetext>Touch screens are nice because they can be programmed to display whatever controls you wish, but isn't the lack of moving parts another advantage?
This seems like it would have MTBF issues.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216756</id>
	<title>Re:Oh no...</title>
	<author>Anonymous</author>
	<datestamp>1259091420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Most of the groping that Slashdot readers do in the car should really be done in private anyway</p></htmltext>
<tokenext>Most of the groping that Slashdot readers do in the car should really be done in private anyway</tokentext>
<sentencetext>Most of the groping that Slashdot readers do in the car should really be done in private anyway</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215980</id>
	<title>Re:Oh no...</title>
	<author>Thelasko</author>
	<datestamp>1259087580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It's also a <a href="http://hardware.slashdot.org/article.pl?sid=09/04/29/1516231" title="slashdot.org">dupe.</a> [slashdot.org]</htmltext>
<tokenext>It 's also a dupe .
[ slashdot.org ]</tokentext>
<sentencetext>It's also a dupe.
[slashdot.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215794</id>
	<title>Re:Oh no...</title>
	<author>royler</author>
	<datestamp>1259086740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>i strongly agree, having an iphone has completely killed the option of texting while driving and im safer for that.</htmltext>
<tokenext>i strongly agree , having an iphone has completely killed the option of texting while driving and im safer for that .</tokentext>
<sentencetext>i strongly agree, having an iphone has completely killed the option of texting while driving and im safer for that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215538</id>
	<title>Backwards?</title>
	<author>war4peace</author>
	<datestamp>1259085600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>So... first they struggled to create touch Screens so they can eliminate buttons altogether, and now they struggle to implement buttons on touch screens? Wow, well thought out!<br>
Although I agree that it would look cool and geeky, I do wonder what's wrong with buttons/keys featuring an OLED screen at the top. I know it wouldn't be such a versatile solution, but nevertheless it doesn't have to be implemented on a large scale.<br>
Seems to me like it's, again, proof of concept rather that something useful in the long term.</htmltext>
<tokenext>So... first they struggled to create touch Screens so they can eliminate buttons altogether , and now they struggle to implement buttons on touch screens ?
Wow , well thought out !
Although I agree that it would look cool and geeky , I do wonder what 's wrong with buttons/keys featuring an OLED screen at the top .
I know it would n't be such a versatile solution , but nevertheless it does n't have to be implemented on a large scale .
Seems to me like it 's , again , proof of concept rather that something useful in the long term .</tokentext>
<sentencetext>So... first they struggled to create touch Screens so they can eliminate buttons altogether, and now they struggle to implement buttons on touch screens?
Wow, well thought out!
Although I agree that it would look cool and geeky, I do wonder what's wrong with buttons/keys featuring an OLED screen at the top.
I know it wouldn't be such a versatile solution, but nevertheless it doesn't have to be implemented on a large scale.
Seems to me like it's, again, proof of concept rather that something useful in the long term.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215166</id>
	<title>Whack-a-mole!</title>
	<author>Anonymous</author>
	<datestamp>1259083980000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>Whack-a-mole! Now with a digital display and tactile feedback! imagine the possibilities!</p></htmltext>
<tokenext>Whack-a-mole !
Now with a digital display and tactile feedback !
imagine the possibilities !</tokentext>
<sentencetext>Whack-a-mole!
Now with a digital display and tactile feedback!
imagine the possibilities!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30220192</id>
	<title>Re:Er</title>
	<author>vakuona</author>
	<datestamp>1259064060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The tactile feedback is in you actually feeling the touch. You don't press, you touch. You don't need confirmation that you have touched hard enough. With buttons, you need feedback because you have to press them hard enough for the button press to register. So the feedback lets you know that you have pressed hard enough.</htmltext>
<tokenext>The tactile feedback is in you actually feeling the touch .
You do n't press , you touch .
You do n't need confirmation that you have touched hard enough .
With buttons , you need feedback because you have to press them hard enough for the button press to register .
So the feedback lets you know that you have pressed hard enough .</tokentext>
<sentencetext>The tactile feedback is in you actually feeling the touch.
You don't press, you touch.
You don't need confirmation that you have touched hard enough.
With buttons, you need feedback because you have to press them hard enough for the button press to register.
So the feedback lets you know that you have pressed hard enough.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216746</id>
	<title>My dream</title>
	<author>SwabTheDeck</author>
	<datestamp>1259091360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I was really hoping this was going to be a fully programmable system that would allow a programmer to dynamically elevate arbitrary parts of the screen, but it seems to be completely static, so I don't really see the point.  Ultimately, what I think people would want for devices like an iPhone would be to have fully dynamic "buttons" that are programmed using the windowing/widget API so that you maintain the application-specific dynamic UI that makes devices like the iPhone awesome while adding the tactile feedback that so many people seem to enjoy.  I think the requisite of a pneumatic or hydraulic pumping system would make it extremely difficult to get something like this into a small package, though.  Maybe there's a material that will expand suitably from electrical stimulation rather than pneumatics.</htmltext>
<tokenext>I was really hoping this was going to be a fully programmable system that would allow a programmer to dynamically elevate arbitrary parts of the screen , but it seems to be completely static , so I do n't really see the point .
Ultimately , what I think people would want for devices like an iPhone would be to have fully dynamic " buttons " that are programmed using the windowing/widget API so that you maintain the application-specific dynamic UI that makes devices like the iPhone awesome while adding the tactile feedback that so many people seem to enjoy .
I think the requisite of a pneumatic or hydraulic pumping system would make it extremely difficult to get something like this into a small package , though .
Maybe there 's a material that will expand suitably from electrical stimulation rather than pneumatics .</tokentext>
<sentencetext>I was really hoping this was going to be a fully programmable system that would allow a programmer to dynamically elevate arbitrary parts of the screen, but it seems to be completely static, so I don't really see the point.
Ultimately, what I think people would want for devices like an iPhone would be to have fully dynamic "buttons" that are programmed using the windowing/widget API so that you maintain the application-specific dynamic UI that makes devices like the iPhone awesome while adding the tactile feedback that so many people seem to enjoy.
I think the requisite of a pneumatic or hydraulic pumping system would make it extremely difficult to get something like this into a small package, though.
Maybe there's a material that will expand suitably from electrical stimulation rather than pneumatics.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304</id>
	<title>Re:Er</title>
	<author>damburger</author>
	<datestamp>1259084580000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Personally, I like having tactile feedback when i press buttons - and the lack of it has kept me away from a pure touchscreen device. I bought a HTC Dream instead of an iPhone for this reason (and the fact I'm not a massive Apple fanboy)</htmltext>
<tokenext>Personally , I like having tactile feedback when i press buttons - and the lack of it has kept me away from a pure touchscreen device .
I bought a HTC Dream instead of an iPhone for this reason ( and the fact I 'm not a massive Apple fanboy )</tokentext>
<sentencetext>Personally, I like having tactile feedback when i press buttons - and the lack of it has kept me away from a pure touchscreen device.
I bought a HTC Dream instead of an iPhone for this reason (and the fact I'm not a massive Apple fanboy)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216364</id>
	<title>Re:Er</title>
	<author>cowscows</author>
	<datestamp>1259089380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Another thing that's nice about touchscreens is that the relative sizes of various buttons can change on the fly. The iPhone virtual keyboard dynamically resizes the area of different letters depending on what letter proceeded it. For example, if you just typed the letter 'c', the next letter you want is much more likely to be 'a' than 'z', so the 'a' button area becomes larger and the 'z' gets smaller. It doesn't change the visual size of the button on screen, because that would undoubtedly be quite annoying, but the target area for more likely letters expands.</p></htmltext>
<tokenext>Another thing that 's nice about touchscreens is that the relative sizes of various buttons can change on the fly .
The iPhone virtual keyboard dynamically resizes the area of different letters depending on what letter proceeded it .
For example , if you just typed the letter 'c ' , the next letter you want is much more likely to be 'a ' than 'z ' , so the 'a ' button area becomes larger and the 'z ' gets smaller .
It does n't change the visual size of the button on screen , because that would undoubtedly be quite annoying , but the target area for more likely letters expands .</tokentext>
<sentencetext>Another thing that's nice about touchscreens is that the relative sizes of various buttons can change on the fly.
The iPhone virtual keyboard dynamically resizes the area of different letters depending on what letter proceeded it.
For example, if you just typed the letter 'c', the next letter you want is much more likely to be 'a' than 'z', so the 'a' button area becomes larger and the 'z' gets smaller.
It doesn't change the visual size of the button on screen, because that would undoubtedly be quite annoying, but the target area for more likely letters expands.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215878</id>
	<title>Vat-grown octopus skin will make this obsolete.</title>
	<author>jeffb (2.718)</author>
	<datestamp>1259087160000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Okay, maybe not octopus skin -- but in it, we have an existence proof for a surface that can display high-bandwidth color changes and slower, but quite elaborate, texture changes.  With all the progress being made with microfluidics and chip-scale effectors, why on Earth would anyone pursue a chugging, hissing, thermodynamically-disadvantaged <i>pneumatic</i> system for this?</p></htmltext>
<tokenext>Okay , maybe not octopus skin -- but in it , we have an existence proof for a surface that can display high-bandwidth color changes and slower , but quite elaborate , texture changes .
With all the progress being made with microfluidics and chip-scale effectors , why on Earth would anyone pursue a chugging , hissing , thermodynamically-disadvantaged pneumatic system for this ?</tokentext>
<sentencetext>Okay, maybe not octopus skin -- but in it, we have an existence proof for a surface that can display high-bandwidth color changes and slower, but quite elaborate, texture changes.
With all the progress being made with microfluidics and chip-scale effectors, why on Earth would anyone pursue a chugging, hissing, thermodynamically-disadvantaged pneumatic system for this?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214856</id>
	<title>Hmm.</title>
	<author>Anonymous</author>
	<datestamp>1259083020000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Yet when I want to touch little girls with my pneumatic rod I am labeled a "pedophile".</p></htmltext>
<tokenext>Yet when I want to touch little girls with my pneumatic rod I am labeled a " pedophile " .</tokentext>
<sentencetext>Yet when I want to touch little girls with my pneumatic rod I am labeled a "pedophile".</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215458</id>
	<title>Transformer blobs!</title>
	<author>macraig</author>
	<datestamp>1259085300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This reminds me of that bizarre "Transformer blob" video that was reported here some time ago.  I dunno if I want my touchscreens morphing on me when I'm not looking!</p></htmltext>
<tokenext>This reminds me of that bizarre " Transformer blob " video that was reported here some time ago .
I dunno if I want my touchscreens morphing on me when I 'm not looking !</tokentext>
<sentencetext>This reminds me of that bizarre "Transformer blob" video that was reported here some time ago.
I dunno if I want my touchscreens morphing on me when I'm not looking!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968</id>
	<title>Why Not...</title>
	<author>Monkeedude1212</author>
	<datestamp>1259083320000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Just make buttons that have a touch screen on them, thus you still have the scroll-ability and versatility of a touch screen, combined with the tacticle feedback of buttons when you want things to function like a button...</p><p>Or am I completely missing the point?</p></htmltext>
<tokenext>Just make buttons that have a touch screen on them , thus you still have the scroll-ability and versatility of a touch screen , combined with the tacticle feedback of buttons when you want things to function like a button...Or am I completely missing the point ?</tokentext>
<sentencetext>Just make buttons that have a touch screen on them, thus you still have the scroll-ability and versatility of a touch screen, combined with the tacticle feedback of buttons when you want things to function like a button...Or am I completely missing the point?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30222300</id>
	<title>Re:Visual feedback</title>
	<author>AmberBlackCat</author>
	<datestamp>1259078760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>I can't imagine many scenarios where I'd really ever text without looking just because there was some physical feedback.</p></div></blockquote><p>Imagine there are other uses for touchscreens besides text messages. Like remote controls, in which you look to the television for visual feedback and the last thing you need is to have to look at the remote too...</p></div>
	</htmltext>
<tokenext>I ca n't imagine many scenarios where I 'd really ever text without looking just because there was some physical feedback.Imagine there are other uses for touchscreens besides text messages .
Like remote controls , in which you look to the television for visual feedback and the last thing you need is to have to look at the remote too.. .</tokentext>
<sentencetext>I can't imagine many scenarios where I'd really ever text without looking just because there was some physical feedback.Imagine there are other uses for touchscreens besides text messages.
Like remote controls, in which you look to the television for visual feedback and the last thing you need is to have to look at the remote too...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214992</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215226</id>
	<title>killer app</title>
	<author>jjeffries</author>
	<datestamp>1259084280000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><tt>The killer app for this will of course be a Timex Sinclair 1000 emulator.</tt></htmltext>
<tokenext>The killer app for this will of course be a Timex Sinclair 1000 emulator .</tokentext>
<sentencetext>The killer app for this will of course be a Timex Sinclair 1000 emulator.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216074</id>
	<title>Multiple monitors for different apps???</title>
	<author>unixguy43</author>
	<datestamp>1259088120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The problem I see here is that you've now got a touch screen that is custom built for a specific, single-screen (or possibly dual-screen, since buttons can be concave or convex) application.  If you've looked at a restaurant console, there's multiple screens- not just one, so for each different application, there needs to be a different screen.  One to show the tables in the restaurant, one to place a kitchen order, one to place a bar order, one to generate the bill, and so on.  The advantage of the touch screen is that you can have the single monitor become a custom interface for any application.  It would seem to me that this air-bubble system removes that, unless there's cards that can be removed an inserted to provide the alternate interfaces in a single device.  Seems a little too cumbersome and rigid to be functional at this point.  If it was something that could be built to represent each individual pixel on the screen, so that the monitor could become a dynamically configurable device, as with the current touch screens, then it might potentially have some usability.</htmltext>
<tokenext>The problem I see here is that you 've now got a touch screen that is custom built for a specific , single-screen ( or possibly dual-screen , since buttons can be concave or convex ) application .
If you 've looked at a restaurant console , there 's multiple screens- not just one , so for each different application , there needs to be a different screen .
One to show the tables in the restaurant , one to place a kitchen order , one to place a bar order , one to generate the bill , and so on .
The advantage of the touch screen is that you can have the single monitor become a custom interface for any application .
It would seem to me that this air-bubble system removes that , unless there 's cards that can be removed an inserted to provide the alternate interfaces in a single device .
Seems a little too cumbersome and rigid to be functional at this point .
If it was something that could be built to represent each individual pixel on the screen , so that the monitor could become a dynamically configurable device , as with the current touch screens , then it might potentially have some usability .</tokentext>
<sentencetext>The problem I see here is that you've now got a touch screen that is custom built for a specific, single-screen (or possibly dual-screen, since buttons can be concave or convex) application.
If you've looked at a restaurant console, there's multiple screens- not just one, so for each different application, there needs to be a different screen.
One to show the tables in the restaurant, one to place a kitchen order, one to place a bar order, one to generate the bill, and so on.
The advantage of the touch screen is that you can have the single monitor become a custom interface for any application.
It would seem to me that this air-bubble system removes that, unless there's cards that can be removed an inserted to provide the alternate interfaces in a single device.
Seems a little too cumbersome and rigid to be functional at this point.
If it was something that could be built to represent each individual pixel on the screen, so that the monitor could become a dynamically configurable device, as with the current touch screens, then it might potentially have some usability.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215460</id>
	<title>Re:Er</title>
	<author>Anonymous</author>
	<datestamp>1259085300000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>What moving parts?  Did you even bother to read the article?  The screen just has a bunch of air pockets inside that react to positive or negative pressure changes within the screen.</htmltext>
<tokenext>What moving parts ?
Did you even bother to read the article ?
The screen just has a bunch of air pockets inside that react to positive or negative pressure changes within the screen .</tokentext>
<sentencetext>What moving parts?
Did you even bother to read the article?
The screen just has a bunch of air pockets inside that react to positive or negative pressure changes within the screen.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215924</id>
	<title>Repost from April</title>
	<author>EkriirkE</author>
	<datestamp>1259087340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This summary has a bit more info in it, too <br>
<a href="http://hardware.slashdot.org/story/09/04/29/1516231/A-Touch-Screen-With-Morphing-Buttons" title="slashdot.org">http://hardware.slashdot.org/story/09/04/29/1516231/A-Touch-Screen-With-Morphing-Buttons</a> [slashdot.org]</htmltext>
<tokenext>This summary has a bit more info in it , too http : //hardware.slashdot.org/story/09/04/29/1516231/A-Touch-Screen-With-Morphing-Buttons [ slashdot.org ]</tokentext>
<sentencetext>This summary has a bit more info in it, too 
http://hardware.slashdot.org/story/09/04/29/1516231/A-Touch-Screen-With-Morphing-Buttons [slashdot.org]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215596</id>
	<title>Re:Er</title>
	<author>Anonymous</author>
	<datestamp>1259085840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>yeah, that's a moving part.  Because it moves.</p></htmltext>
<tokenext>yeah , that 's a moving part .
Because it moves .</tokentext>
<sentencetext>yeah, that's a moving part.
Because it moves.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215460</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215006</id>
	<title>Better idea</title>
	<author>amplt1337</author>
	<datestamp>1259083500000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>Establish a grid of button surfaces, kind of like pixels, which can be dynamically re-grouped to merge them into larger buttons, and then put the display on that.</p><p>So, imagine you had a keyboard with essentially no gaps between the keys, and a screen on top of them.  You could make one button out of qwe, one button out of tgyh, etc., while displaying your graphics seamlessly.</p><p>Or you could just do what ATMs have already been doing for ages, which is have blank buttons beside the screen and add the labels.  But nooo, gotta be all fancy-like...</p></htmltext>
<tokenext>Establish a grid of button surfaces , kind of like pixels , which can be dynamically re-grouped to merge them into larger buttons , and then put the display on that.So , imagine you had a keyboard with essentially no gaps between the keys , and a screen on top of them .
You could make one button out of qwe , one button out of tgyh , etc. , while displaying your graphics seamlessly.Or you could just do what ATMs have already been doing for ages , which is have blank buttons beside the screen and add the labels .
But nooo , got ta be all fancy-like.. .</tokentext>
<sentencetext>Establish a grid of button surfaces, kind of like pixels, which can be dynamically re-grouped to merge them into larger buttons, and then put the display on that.So, imagine you had a keyboard with essentially no gaps between the keys, and a screen on top of them.
You could make one button out of qwe, one button out of tgyh, etc., while displaying your graphics seamlessly.Or you could just do what ATMs have already been doing for ages, which is have blank buttons beside the screen and add the labels.
But nooo, gotta be all fancy-like...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215572</id>
	<title>Blind</title>
	<author>selven</author>
	<datestamp>1259085720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This would be extremely effective in making touchscreen interfaces usable for the blind.</p></htmltext>
<tokenext>This would be extremely effective in making touchscreen interfaces usable for the blind .</tokentext>
<sentencetext>This would be extremely effective in making touchscreen interfaces usable for the blind.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30219432</id>
	<title>Re:Vat-grown octopus skin will make this obsolete.</title>
	<author>Anonymous</author>
	<datestamp>1259060580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>These will be great for internet-capable devices, as they could be powered off of any <a href="http://en.wikipedia.org/wiki/File:Rohrpoststation.jpg" title="wikipedia.org" rel="nofollow">standard router</a> [wikipedia.org].</p></htmltext>
<tokenext>These will be great for internet-capable devices , as they could be powered off of any standard router [ wikipedia.org ] .</tokentext>
<sentencetext>These will be great for internet-capable devices, as they could be powered off of any standard router [wikipedia.org].</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215878</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215294</id>
	<title>Pneumatics are lame</title>
	<author>MobyDisk</author>
	<datestamp>1259084520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I periodically read about demos of this technology using pneumatics, but it seems like a very limiting way to do it.  The article says:</p><p><div class="quote"><p>all the buttons must popped in or out at once...new shapes cannot be created dynamically</p></div><p>For this to ever become in general use, we need something pixel-addressable.  Seems like something that is piezoelectric or electrostatic is more likely to be successful that pneumatics.</p><p>I like the question posed in the article:</p><p><div class="quote"><p>When do you think pneumatic technology like this will turn the flat touch screen buttons on our phones into physical buttons?<br>
&nbsp; &nbsp; &nbsp; 1. 2 years<br>
&nbsp; &nbsp; &nbsp; 2. 5 years<br>
&nbsp; &nbsp; &nbsp; 3. 10+ years<br>
&nbsp; &nbsp; &nbsp; 4. Never</p></div><p>Probably never.  Had they asked "when will haptic technology turn the flat touch screen buttons..." instead of asking about the specific technology, then the answer would be different.</p><p>The other big limitation of any haptics approach is that most touch screen surfaces are glass, for durability.  Sitting next to me I have 4 touch screens, each with a different techology: resistive, capacitive, acoustic wave, and acoustic pulse recognition.  Each one has advantages and disadvantages, but I don't think any of these screens could be altered to support haptics.  Since they are used in restaurants and medical systems, they must be durable and sealed.  So there is definitely much more research involved in this other than hacking a cheesy pneumatic system into a touch screen and asking "when will this will take over the world?"</p></div>
	</htmltext>
<tokenext>I periodically read about demos of this technology using pneumatics , but it seems like a very limiting way to do it .
The article says : all the buttons must popped in or out at once...new shapes can not be created dynamicallyFor this to ever become in general use , we need something pixel-addressable .
Seems like something that is piezoelectric or electrostatic is more likely to be successful that pneumatics.I like the question posed in the article : When do you think pneumatic technology like this will turn the flat touch screen buttons on our phones into physical buttons ?
      1 .
2 years       2 .
5 years       3 .
10 + years       4 .
NeverProbably never .
Had they asked " when will haptic technology turn the flat touch screen buttons... " instead of asking about the specific technology , then the answer would be different.The other big limitation of any haptics approach is that most touch screen surfaces are glass , for durability .
Sitting next to me I have 4 touch screens , each with a different techology : resistive , capacitive , acoustic wave , and acoustic pulse recognition .
Each one has advantages and disadvantages , but I do n't think any of these screens could be altered to support haptics .
Since they are used in restaurants and medical systems , they must be durable and sealed .
So there is definitely much more research involved in this other than hacking a cheesy pneumatic system into a touch screen and asking " when will this will take over the world ?
"</tokentext>
<sentencetext>I periodically read about demos of this technology using pneumatics, but it seems like a very limiting way to do it.
The article says:all the buttons must popped in or out at once...new shapes cannot be created dynamicallyFor this to ever become in general use, we need something pixel-addressable.
Seems like something that is piezoelectric or electrostatic is more likely to be successful that pneumatics.I like the question posed in the article:When do you think pneumatic technology like this will turn the flat touch screen buttons on our phones into physical buttons?
      1.
2 years
      2.
5 years
      3.
10+ years
      4.
NeverProbably never.
Had they asked "when will haptic technology turn the flat touch screen buttons..." instead of asking about the specific technology, then the answer would be different.The other big limitation of any haptics approach is that most touch screen surfaces are glass, for durability.
Sitting next to me I have 4 touch screens, each with a different techology: resistive, capacitive, acoustic wave, and acoustic pulse recognition.
Each one has advantages and disadvantages, but I don't think any of these screens could be altered to support haptics.
Since they are used in restaurants and medical systems, they must be durable and sealed.
So there is definitely much more research involved in this other than hacking a cheesy pneumatic system into a touch screen and asking "when will this will take over the world?
"
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216466</id>
	<title>Re:Why Not...</title>
	<author>DerekLyons</author>
	<datestamp>1259089800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Just make buttons that have a touch screen on them, thus you still have the scroll-ability and versatility of a touch screen, combined with the tacticle feedback of buttons when you want things to function like a button...</p></div></blockquote><p>Heck, we had something like this when I was in the Navy.  Buttons that actually contained something like a miniature slide projector* that could display multiple messages.  I know these were first used in the 88/0 system which was first deployed in the late 60's, and they may even be older.<br>
&nbsp; <br>The Shuttle uses a system where the buttons ring the screen, and each button's function is displayed onscreen next to the button.  ISTR the Navy had systems that operated in the same general manner as early as the late 70's.  (I didn't work with any of those systems, just saw them at a distance.)<br>
&nbsp; <br>Given how small LCD screens are getting now a days, you could do all manner of interesting things.</p><p>*You had multiple lamps and a system of films with the messages on them, masks, and 'light pipes' so that only one message/image was displayed when the appropriate light was lit.</p></div>
	</htmltext>
<tokenext>Just make buttons that have a touch screen on them , thus you still have the scroll-ability and versatility of a touch screen , combined with the tacticle feedback of buttons when you want things to function like a button...Heck , we had something like this when I was in the Navy .
Buttons that actually contained something like a miniature slide projector * that could display multiple messages .
I know these were first used in the 88/0 system which was first deployed in the late 60 's , and they may even be older .
  The Shuttle uses a system where the buttons ring the screen , and each button 's function is displayed onscreen next to the button .
ISTR the Navy had systems that operated in the same general manner as early as the late 70 's .
( I did n't work with any of those systems , just saw them at a distance .
)   Given how small LCD screens are getting now a days , you could do all manner of interesting things .
* You had multiple lamps and a system of films with the messages on them , masks , and 'light pipes ' so that only one message/image was displayed when the appropriate light was lit .</tokentext>
<sentencetext>Just make buttons that have a touch screen on them, thus you still have the scroll-ability and versatility of a touch screen, combined with the tacticle feedback of buttons when you want things to function like a button...Heck, we had something like this when I was in the Navy.
Buttons that actually contained something like a miniature slide projector* that could display multiple messages.
I know these were first used in the 88/0 system which was first deployed in the late 60's, and they may even be older.
  The Shuttle uses a system where the buttons ring the screen, and each button's function is displayed onscreen next to the button.
ISTR the Navy had systems that operated in the same general manner as early as the late 70's.
(I didn't work with any of those systems, just saw them at a distance.
)
  Given how small LCD screens are getting now a days, you could do all manner of interesting things.
*You had multiple lamps and a system of films with the messages on them, masks, and 'light pipes' so that only one message/image was displayed when the appropriate light was lit.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215076</id>
	<title>Re:Why Not...</title>
	<author>maxume</author>
	<datestamp>1259083680000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>The assembly of something with 15 buttons using the linked idea would probably be quite a lot cheaper than the assembly of 15 separate buttons, and the electronics to drive it would probably be simpler.</p></htmltext>
<tokenext>The assembly of something with 15 buttons using the linked idea would probably be quite a lot cheaper than the assembly of 15 separate buttons , and the electronics to drive it would probably be simpler .</tokentext>
<sentencetext>The assembly of something with 15 buttons using the linked idea would probably be quite a lot cheaper than the assembly of 15 separate buttons, and the electronics to drive it would probably be simpler.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30220248</id>
	<title>Re:killer app</title>
	<author>Anonymous</author>
	<datestamp>1259064360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Figures this comment would come from one of those fixed width jerks.</p></htmltext>
<tokenext>Figures this comment would come from one of those fixed width jerks .</tokentext>
<sentencetext>Figures this comment would come from one of those fixed width jerks.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215226</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30222098</id>
	<title>Old, old news</title>
	<author>scdeimos</author>
	<datestamp>1259076780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>We've seen this story before. Even has some of the same pictures.
<a href="http://hardware.slashdot.org/article.pl?sid=09/04/29/1516231" title="slashdot.org">http://hardware.slashdot.org/article.pl?sid=09/04/29/1516231</a> [slashdot.org]</htmltext>
<tokenext>We 've seen this story before .
Even has some of the same pictures .
http : //hardware.slashdot.org/article.pl ? sid = 09/04/29/1516231 [ slashdot.org ]</tokentext>
<sentencetext>We've seen this story before.
Even has some of the same pictures.
http://hardware.slashdot.org/article.pl?sid=09/04/29/1516231 [slashdot.org]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215248</id>
	<title>Is that a pneumatically-inflatable touch screen</title>
	<author>idontgno</author>
	<datestamp>1259084340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>or are you just happy to see me?</htmltext>
<tokenext>or are you just happy to see me ?</tokentext>
<sentencetext>or are you just happy to see me?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216396</id>
	<title>Re:Visual feedback</title>
	<author>Hurricane78</author>
	<datestamp>1259089500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Yes, it requires I look when I text,</p></div><p>&ldquo;Getting-the-idea-FAIL&rdquo;!<nobr> <wbr></nobr>:D</p></div>
	</htmltext>
<tokenext>Yes , it requires I look when I text ,    Getting-the-idea-FAIL    !
: D</tokentext>
<sentencetext>Yes, it requires I look when I text,“Getting-the-idea-FAIL”!
:D
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214992</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215042</id>
	<title>Pricetag? Reliability?</title>
	<author>courteaudotbiz</author>
	<datestamp>1259083560000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext>And what would be the actual pricetag of such a device? I understand that we use more and more electronics to simplify the mechanics behind our devices. Now, with a pump, you need to physically inject air under the screen, so you have moving parts, and they are usually costly... besides, what would be the reliability of such a thing? and could you get a "flat" screen?</htmltext>
<tokenext>And what would be the actual pricetag of such a device ?
I understand that we use more and more electronics to simplify the mechanics behind our devices .
Now , with a pump , you need to physically inject air under the screen , so you have moving parts , and they are usually costly... besides , what would be the reliability of such a thing ?
and could you get a " flat " screen ?</tokentext>
<sentencetext>And what would be the actual pricetag of such a device?
I understand that we use more and more electronics to simplify the mechanics behind our devices.
Now, with a pump, you need to physically inject air under the screen, so you have moving parts, and they are usually costly... besides, what would be the reliability of such a thing?
and could you get a "flat" screen?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214928</id>
	<title>Convergence of smart phone and condoms...</title>
	<author>Delusion\_</author>
	<datestamp>1259083200000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>...ribbed, for her pleasure.</p></htmltext>
<tokenext>...ribbed , for her pleasure .</tokentext>
<sentencetext>...ribbed, for her pleasure.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215698</id>
	<title>call me pissy but</title>
	<author>nimbius</author>
	<datestamp>1259086260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>i cant stand the touchscreen interface...its a relic that persists because we are too lazy or stupid to grasp abstract concepts presented to us in the start of the 21st century.  We still want to shake, poke, bump, and twist our interfaces to make them do what we want.  Its just one more way to dumb-down information and technology as opposed to addressing the real issue:  education.</htmltext>
<tokenext>i cant stand the touchscreen interface...its a relic that persists because we are too lazy or stupid to grasp abstract concepts presented to us in the start of the 21st century .
We still want to shake , poke , bump , and twist our interfaces to make them do what we want .
Its just one more way to dumb-down information and technology as opposed to addressing the real issue : education .</tokentext>
<sentencetext>i cant stand the touchscreen interface...its a relic that persists because we are too lazy or stupid to grasp abstract concepts presented to us in the start of the 21st century.
We still want to shake, poke, bump, and twist our interfaces to make them do what we want.
Its just one more way to dumb-down information and technology as opposed to addressing the real issue:  education.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217356</id>
	<title>Re:Er</title>
	<author>Lockblade</author>
	<datestamp>1259094420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>So I guess an air pump doesn't count as a moving part?</htmltext>
<tokenext>So I guess an air pump does n't count as a moving part ?</tokentext>
<sentencetext>So I guess an air pump doesn't count as a moving part?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215460</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215300</id>
	<title>a safer future for your ex</title>
	<author>cashX3r0</author>
	<datestamp>1259084580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>instead of the cell phone filling the buttons with air, the owner of the phone should have to blow his cell phone up to use it.  with a breathalyzer installed in the cell phone, the phone would be disabled from making calls, which would end the "i'm drunk so i'm calling my ex" phenomenon.</htmltext>
<tokenext>instead of the cell phone filling the buttons with air , the owner of the phone should have to blow his cell phone up to use it .
with a breathalyzer installed in the cell phone , the phone would be disabled from making calls , which would end the " i 'm drunk so i 'm calling my ex " phenomenon .</tokentext>
<sentencetext>instead of the cell phone filling the buttons with air, the owner of the phone should have to blow his cell phone up to use it.
with a breathalyzer installed in the cell phone, the phone would be disabled from making calls, which would end the "i'm drunk so i'm calling my ex" phenomenon.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215738</id>
	<title>Re:This explains Star Trek</title>
	<author>mcgrew</author>
	<datestamp>1259086380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Actually, the "exploding work stations" comes from computers even more primitive than the real ones in the 1960s. Vacuum tubes consume large amounts of power (a filimant has to be heated, much like an incandescant light bulb), and if you have a physical short (like the first computer bug that was actually a moth that shorted out some wires) you often have a "POP!" and some smoke.</p></htmltext>
<tokenext>Actually , the " exploding work stations " comes from computers even more primitive than the real ones in the 1960s .
Vacuum tubes consume large amounts of power ( a filimant has to be heated , much like an incandescant light bulb ) , and if you have a physical short ( like the first computer bug that was actually a moth that shorted out some wires ) you often have a " POP !
" and some smoke .</tokentext>
<sentencetext>Actually, the "exploding work stations" comes from computers even more primitive than the real ones in the 1960s.
Vacuum tubes consume large amounts of power (a filimant has to be heated, much like an incandescant light bulb), and if you have a physical short (like the first computer bug that was actually a moth that shorted out some wires) you often have a "POP!
" and some smoke.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215256</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215874</id>
	<title>Re:Er</title>
	<author>Garble Snarky</author>
	<datestamp>1259087160000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>"An air chamber behind the backing can be pressurized or depressurized using pneumatic technology, in this case fan-based pumps."
<br> <br>
Fans generally move.</htmltext>
<tokenext>" An air chamber behind the backing can be pressurized or depressurized using pneumatic technology , in this case fan-based pumps .
" Fans generally move .</tokentext>
<sentencetext>"An air chamber behind the backing can be pressurized or depressurized using pneumatic technology, in this case fan-based pumps.
"
 
Fans generally move.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215460</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215256</id>
	<title>This explains Star Trek</title>
	<author>Shivetya</author>
	<datestamp>1259084400000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>and their exploding work stations.</p></htmltext>
<tokenext>and their exploding work stations .</tokentext>
<sentencetext>and their exploding work stations.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215074</id>
	<title>Having read TFA</title>
	<author>Anonymous</author>
	<datestamp>1259083680000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>I am left thinking "so what?". All they did was PROJECT graphics onto an inflatable surface, and used a camera and image recognition to determine which 'button' was being pressed.</p><p>I think it's a bit of a stretch to describe this as a 'touch screen'; the image is projected onto the surface (which could be true for ANY surface) and the surface itself does NOT detect touches. There is also no tactile feedback whatsoever. I might as well get one of those laser projection keyboards, set it up on the bonnet of my car and announce that I've made a "self-propelling air-conditioned touchscreen that seats four".</p></htmltext>
<tokenext>I am left thinking " so what ? " .
All they did was PROJECT graphics onto an inflatable surface , and used a camera and image recognition to determine which 'button ' was being pressed.I think it 's a bit of a stretch to describe this as a 'touch screen ' ; the image is projected onto the surface ( which could be true for ANY surface ) and the surface itself does NOT detect touches .
There is also no tactile feedback whatsoever .
I might as well get one of those laser projection keyboards , set it up on the bonnet of my car and announce that I 've made a " self-propelling air-conditioned touchscreen that seats four " .</tokentext>
<sentencetext>I am left thinking "so what?".
All they did was PROJECT graphics onto an inflatable surface, and used a camera and image recognition to determine which 'button' was being pressed.I think it's a bit of a stretch to describe this as a 'touch screen'; the image is projected onto the surface (which could be true for ANY surface) and the surface itself does NOT detect touches.
There is also no tactile feedback whatsoever.
I might as well get one of those laser projection keyboards, set it up on the bonnet of my car and announce that I've made a "self-propelling air-conditioned touchscreen that seats four".</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215964</id>
	<title>Refresh?</title>
	<author>hrimhari</author>
	<datestamp>1259087520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This sounds awfully familiar... Oh yeah, <a href="http://hardware.slashdot.org/article.pl?sid=09/04/29/1516231" title="slashdot.org" rel="nofollow">here</a> [slashdot.org].</p></htmltext>
<tokenext>This sounds awfully familiar... Oh yeah , here [ slashdot.org ] .</tokentext>
<sentencetext>This sounds awfully familiar... Oh yeah, here [slashdot.org].</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217690</id>
	<title>Re:Why Not...</title>
	<author>xonicx</author>
	<datestamp>1259095920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I always think of a keyboard with few touch screen buttons. Why to clutter the primary screen space with control buttons which can be shown dynamically on keyboard?</htmltext>
<tokenext>I always think of a keyboard with few touch screen buttons .
Why to clutter the primary screen space with control buttons which can be shown dynamically on keyboard ?</tokentext>
<sentencetext>I always think of a keyboard with few touch screen buttons.
Why to clutter the primary screen space with control buttons which can be shown dynamically on keyboard?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216394</id>
	<title>Re:Why?</title>
	<author>MobileTatsu-NJG</author>
	<datestamp>1259089500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Weren't touch-screens the latest rage because.. you didn't have to.. push... buttons?</p></div><p>No.  They're the 'latest rage' because you can have a simplified and optimized interface that changes based on the application.</p><p>Honestly dude, I'm not sure why you even asked that.  <i>"This button push is too much!"</i>  Seriously, have you not seen the progression of cell phones in the last 5 years?</p></div>
	</htmltext>
<tokenext>Were n't touch-screens the latest rage because.. you did n't have to.. push... buttons ? No .
They 're the 'latest rage ' because you can have a simplified and optimized interface that changes based on the application.Honestly dude , I 'm not sure why you even asked that .
" This button push is too much !
" Seriously , have you not seen the progression of cell phones in the last 5 years ?</tokentext>
<sentencetext>Weren't touch-screens the latest rage because.. you didn't have to.. push... buttons?No.
They're the 'latest rage' because you can have a simplified and optimized interface that changes based on the application.Honestly dude, I'm not sure why you even asked that.
"This button push is too much!
"  Seriously, have you not seen the progression of cell phones in the last 5 years?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215172</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214912</id>
	<title>Re:Oh no...</title>
	<author>Anonymous</author>
	<datestamp>1259083140000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>Like... a shifter?</p></htmltext>
<tokenext>Like... a shifter ?</tokentext>
<sentencetext>Like... a shifter?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215944</id>
	<title>Re:Oh no...</title>
	<author>Anonymous</author>
	<datestamp>1259087400000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I think the gradual lesson for cars is that we should limit their speeds to around 70kph and make them electric.  At low enough speeds and light enough vehicles, the risks are much easier to manage.  If you need to get somewhere faster or longer distance than such a vehicle can manage, trains can do that.</p><p>As for touch screens, they are popular because they seem futuristic.  They will eventually be seen similar to parachute pants ("it seemed like a good idea at the time").</p></htmltext>
<tokenext>I think the gradual lesson for cars is that we should limit their speeds to around 70kph and make them electric .
At low enough speeds and light enough vehicles , the risks are much easier to manage .
If you need to get somewhere faster or longer distance than such a vehicle can manage , trains can do that.As for touch screens , they are popular because they seem futuristic .
They will eventually be seen similar to parachute pants ( " it seemed like a good idea at the time " ) .</tokentext>
<sentencetext>I think the gradual lesson for cars is that we should limit their speeds to around 70kph and make them electric.
At low enough speeds and light enough vehicles, the risks are much easier to manage.
If you need to get somewhere faster or longer distance than such a vehicle can manage, trains can do that.As for touch screens, they are popular because they seem futuristic.
They will eventually be seen similar to parachute pants ("it seemed like a good idea at the time").</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215976</id>
	<title>I invented this two years ago...</title>
	<author>Hurricane78</author>
	<datestamp>1259087580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>...and discarded it because the screen itself is not flexible enough for serious dynamics (e.g. the form that your keyboard keys have), or if you use a second surface above it that you fill with the air, you get optical distortions.</p><p>My current concept is much cooler: Put pins in every spot between 4 pixels (on the corners), and use small magnetic actuators (like speakers) behind the screen, to drive the pins up and down. then attach a flexible foil on the top of the pins. now you can create very nice, fast and detailed tactile surfaces.</p><p>If you want to develop this (I haven&rsquo;t got the time for it, since I'm already trying to make some other inventions reality<nobr> <wbr></nobr>:), just mention that you got the idea from me and send me a free product with lifetime replacement guarantee, and we&rsquo;re good.<nobr> <wbr></nobr>:) I just want to use it, tell everybody how cool it is (advertisement for you), and have made the world a bit better.</p></htmltext>
<tokenext>...and discarded it because the screen itself is not flexible enough for serious dynamics ( e.g .
the form that your keyboard keys have ) , or if you use a second surface above it that you fill with the air , you get optical distortions.My current concept is much cooler : Put pins in every spot between 4 pixels ( on the corners ) , and use small magnetic actuators ( like speakers ) behind the screen , to drive the pins up and down .
then attach a flexible foil on the top of the pins .
now you can create very nice , fast and detailed tactile surfaces.If you want to develop this ( I haven    t got the time for it , since I 'm already trying to make some other inventions reality : ) , just mention that you got the idea from me and send me a free product with lifetime replacement guarantee , and we    re good .
: ) I just want to use it , tell everybody how cool it is ( advertisement for you ) , and have made the world a bit better .</tokentext>
<sentencetext>...and discarded it because the screen itself is not flexible enough for serious dynamics (e.g.
the form that your keyboard keys have), or if you use a second surface above it that you fill with the air, you get optical distortions.My current concept is much cooler: Put pins in every spot between 4 pixels (on the corners), and use small magnetic actuators (like speakers) behind the screen, to drive the pins up and down.
then attach a flexible foil on the top of the pins.
now you can create very nice, fast and detailed tactile surfaces.If you want to develop this (I haven’t got the time for it, since I'm already trying to make some other inventions reality :), just mention that you got the idea from me and send me a free product with lifetime replacement guarantee, and we’re good.
:) I just want to use it, tell everybody how cool it is (advertisement for you), and have made the world a bit better.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214926</id>
	<title>SO COOL...</title>
	<author>Anonymous</author>
	<datestamp>1259083200000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p>I think I speak for everyone on this site when I say that this is REALLY COOL. I kind of want to go work on making a dynamic version right now. The technology shown here is cool but the concept of a dynamic surface that can re-shape is a great one and something that would should work on. Can you imagine how much better your phone/monitor/keypad would be if you could re-shape it as you needed?</p></htmltext>
<tokenext>I think I speak for everyone on this site when I say that this is REALLY COOL .
I kind of want to go work on making a dynamic version right now .
The technology shown here is cool but the concept of a dynamic surface that can re-shape is a great one and something that would should work on .
Can you imagine how much better your phone/monitor/keypad would be if you could re-shape it as you needed ?</tokentext>
<sentencetext>I think I speak for everyone on this site when I say that this is REALLY COOL.
I kind of want to go work on making a dynamic version right now.
The technology shown here is cool but the concept of a dynamic surface that can re-shape is a great one and something that would should work on.
Can you imagine how much better your phone/monitor/keypad would be if you could re-shape it as you needed?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30231056</id>
	<title>Re:Er</title>
	<author>Anonymous</author>
	<datestamp>1257159600000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Get an iphone u twit</p></htmltext>
<tokenext>Get an iphone u twit</tokentext>
<sentencetext>Get an iphone u twit</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214902</id>
	<title>pistons!</title>
	<author>cashX3r0</author>
	<datestamp>1259083140000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>so there are pistons within the cell phone of the future?  batteries don't stand a chance.  and then you have to oil your phone.</htmltext>
<tokenext>so there are pistons within the cell phone of the future ?
batteries do n't stand a chance .
and then you have to oil your phone .</tokentext>
<sentencetext>so there are pistons within the cell phone of the future?
batteries don't stand a chance.
and then you have to oil your phone.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215346</id>
	<title>Piezoelectric layer</title>
	<author>Anonymous</author>
	<datestamp>1259084700000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>Wouldn't it be easier to just add a piezoelectric layer to the screen and add haptic feedback that way?</p></htmltext>
<tokenext>Would n't it be easier to just add a piezoelectric layer to the screen and add haptic feedback that way ?</tokentext>
<sentencetext>Wouldn't it be easier to just add a piezoelectric layer to the screen and add haptic feedback that way?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30222572</id>
	<title>Can't dynamically change</title>
	<author>DrZook</author>
	<datestamp>1259081340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>In how many scenarios will a piston/compressor driven air-filled system that can't be dynamically configured to show different elements be useful?(the only 'pop out' you'll ever have on your Pneumatic phone is for the numeric keypad, for instance)
And this is without even going into the bulkiness and battery life issues.</htmltext>
<tokenext>In how many scenarios will a piston/compressor driven air-filled system that ca n't be dynamically configured to show different elements be useful ?
( the only 'pop out ' you 'll ever have on your Pneumatic phone is for the numeric keypad , for instance ) And this is without even going into the bulkiness and battery life issues .</tokentext>
<sentencetext>In how many scenarios will a piston/compressor driven air-filled system that can't be dynamically configured to show different elements be useful?
(the only 'pop out' you'll ever have on your Pneumatic phone is for the numeric keypad, for instance)
And this is without even going into the bulkiness and battery life issues.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214992</id>
	<title>Visual feedback</title>
	<author>Enderandrew</author>
	<datestamp>1259083380000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>I assumed I'd have issue with the touch keyboard on the iPhone. However, when I press a key, that key is highlighted and enlarges. I receive visual feedback of the key I pressed, even if I don't have physical feedback. Yes, it requires I look when I text, but I can't imagine many scenarios where I'd really ever text without looking just because there was some physical feedback.</p><p>I'll take the lack of moving parts over the physical feedback, especially given how often I've dropped my phone.</p></htmltext>
<tokenext>I assumed I 'd have issue with the touch keyboard on the iPhone .
However , when I press a key , that key is highlighted and enlarges .
I receive visual feedback of the key I pressed , even if I do n't have physical feedback .
Yes , it requires I look when I text , but I ca n't imagine many scenarios where I 'd really ever text without looking just because there was some physical feedback.I 'll take the lack of moving parts over the physical feedback , especially given how often I 've dropped my phone .</tokentext>
<sentencetext>I assumed I'd have issue with the touch keyboard on the iPhone.
However, when I press a key, that key is highlighted and enlarges.
I receive visual feedback of the key I pressed, even if I don't have physical feedback.
Yes, it requires I look when I text, but I can't imagine many scenarios where I'd really ever text without looking just because there was some physical feedback.I'll take the lack of moving parts over the physical feedback, especially given how often I've dropped my phone.</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216364
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217690
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216278
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30222300
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214992
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216756
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216466
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30219518
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215226
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30220248
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215226
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215172
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217398
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216452
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214992
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215738
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215256
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216148
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217356
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215460
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216516
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214912
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215980
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216242
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215042
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217110
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215086
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215076
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216542
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214992
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216460
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215874
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215460
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30231056
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216396
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214992
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215944
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215794
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215442
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215086
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30221264
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30219432
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215878
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215596
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215460
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216368
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216354
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217480
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30220192
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_24_1557239_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30220908
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215010
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215074
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215364
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215538
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214926
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215226
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30220248
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30219518
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215698
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214840
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216756
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215086
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217110
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215442
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215794
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214912
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215980
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215944
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216148
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214918
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216278
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215460
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215874
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217356
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215596
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215304
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30231056
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30220192
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217398
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216354
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216460
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216364
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214968
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216466
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30220908
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30221264
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215076
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216368
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217690
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216516
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30217480
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30214992
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216452
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216542
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216396
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30222300
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215144
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215288
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215172
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216394
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215218
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215006
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215042
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30216242
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215256
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215738
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215878
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30219432
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_24_1557239.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_24_1557239.30215346
</commentlist>
</conversation>
