<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_06_22_2328203</id>
	<title>An Experiment In BlackBerry Development</title>
	<author>kdawson</author>
	<datestamp>1245675780000</datestamp>
	<htmltext>ballwall writes <i>"We've all read the stories about how lucrative selling apps on the iPhone can be (<a href="http://tech.slashdot.org/story/09/03/10/0157221/The-Realities-of-Selling-On-Apples-App-Store">or not</a>), but what about other platforms? BlackBerry accounts for twice as many handsets shipped as Apple, <a href="http://www.gartner.com/it/page.jsp?id=985912">according to Gartner</a>, so I decided to find out. I wrote about my <a href="http://www.versatilemonkey.com/story.html">experiences developing my first BlackBerry application</a> including sales, platform issues, and a bunch of other things I thought new mobile developers might want to know about."</i></htmltext>
<tokenext>ballwall writes " We 've all read the stories about how lucrative selling apps on the iPhone can be ( or not ) , but what about other platforms ?
BlackBerry accounts for twice as many handsets shipped as Apple , according to Gartner , so I decided to find out .
I wrote about my experiences developing my first BlackBerry application including sales , platform issues , and a bunch of other things I thought new mobile developers might want to know about .
"</tokentext>
<sentencetext>ballwall writes "We've all read the stories about how lucrative selling apps on the iPhone can be (or not), but what about other platforms?
BlackBerry accounts for twice as many handsets shipped as Apple, according to Gartner, so I decided to find out.
I wrote about my experiences developing my first BlackBerry application including sales, platform issues, and a bunch of other things I thought new mobile developers might want to know about.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28439019</id>
	<title>Re:Thank you</title>
	<author>Anonymous</author>
	<datestamp>1245772560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>What on earth are you talking about?  The only software BES needs to integrate with exchange is<nobr> <wbr></nobr>... sql server, exchange, and BES.  Nothing third party.  You don't even need sql server if you have a small shop and want to use msde/sql server express.</p></htmltext>
<tokenext>What on earth are you talking about ?
The only software BES needs to integrate with exchange is ... sql server , exchange , and BES .
Nothing third party .
You do n't even need sql server if you have a small shop and want to use msde/sql server express .</tokentext>
<sentencetext>What on earth are you talking about?
The only software BES needs to integrate with exchange is ... sql server, exchange, and BES.
Nothing third party.
You don't even need sql server if you have a small shop and want to use msde/sql server express.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432901</id>
	<title>smartphone masturbation</title>
	<author>Gothmolly</author>
	<datestamp>1245680940000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext><p>So you spend $100 a month on a freaking phone, and then its really no cooler than your old phone, so you spend more money to listen to other people stroke on and on about how THEIR phones are cool, instead of working, hanging out with your SO, your kids, or your pets.</p><p>wtf is wrong with people</p></htmltext>
<tokenext>So you spend $ 100 a month on a freaking phone , and then its really no cooler than your old phone , so you spend more money to listen to other people stroke on and on about how THEIR phones are cool , instead of working , hanging out with your SO , your kids , or your pets.wtf is wrong with people</tokentext>
<sentencetext>So you spend $100 a month on a freaking phone, and then its really no cooler than your old phone, so you spend more money to listen to other people stroke on and on about how THEIR phones are cool, instead of working, hanging out with your SO, your kids, or your pets.wtf is wrong with people</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432873</id>
	<title>You forgot the most important thing...</title>
	<author>Anonymous</author>
	<datestamp>1245680760000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>Iphone users are fascinated by crappy, shiny things, so they are likely to buy any old app with good marketing.</p><p>On the other hand, blackberry users will soberly do a cost-benefit analysis before buying an app, so you're much less likely to sell.</p><p>Therefor iphone apps will make more sales.</p><p>(ok, mod me down already!)</p></htmltext>
<tokenext>Iphone users are fascinated by crappy , shiny things , so they are likely to buy any old app with good marketing.On the other hand , blackberry users will soberly do a cost-benefit analysis before buying an app , so you 're much less likely to sell.Therefor iphone apps will make more sales .
( ok , mod me down already !
)</tokentext>
<sentencetext>Iphone users are fascinated by crappy, shiny things, so they are likely to buy any old app with good marketing.On the other hand, blackberry users will soberly do a cost-benefit analysis before buying an app, so you're much less likely to sell.Therefor iphone apps will make more sales.
(ok, mod me down already!
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434683</id>
	<title>Re:You forgot the most important thing...</title>
	<author>Concerned Onlooker</author>
	<datestamp>1245691680000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>On what do you base this?  It sounds more like a jealous rant than anything else.  iPhones work very, very well and have a terrific interface.  I have purchased a few really great apps for it and the only marketing needed was me looking for something I needed on the App Store.</p><p>As for your blackberry users doing a "cost-benefit analysis before buying an app" I would say they'd better.  The article mentions that most handheld apps that go on the Blackberry are around $30.  The apps available for the iPhone are anywhere from 99 cents to a few dollars so it's inexpensive to try out a few of them.  For instance, I have 2 ssh clients for less than half the price of a typical app that would run on a Blackberry.  Add in the killer programmable calculator I got and it's all still below the price point of one Blackberry app.</p></htmltext>
<tokenext>On what do you base this ?
It sounds more like a jealous rant than anything else .
iPhones work very , very well and have a terrific interface .
I have purchased a few really great apps for it and the only marketing needed was me looking for something I needed on the App Store.As for your blackberry users doing a " cost-benefit analysis before buying an app " I would say they 'd better .
The article mentions that most handheld apps that go on the Blackberry are around $ 30 .
The apps available for the iPhone are anywhere from 99 cents to a few dollars so it 's inexpensive to try out a few of them .
For instance , I have 2 ssh clients for less than half the price of a typical app that would run on a Blackberry .
Add in the killer programmable calculator I got and it 's all still below the price point of one Blackberry app .</tokentext>
<sentencetext>On what do you base this?
It sounds more like a jealous rant than anything else.
iPhones work very, very well and have a terrific interface.
I have purchased a few really great apps for it and the only marketing needed was me looking for something I needed on the App Store.As for your blackberry users doing a "cost-benefit analysis before buying an app" I would say they'd better.
The article mentions that most handheld apps that go on the Blackberry are around $30.
The apps available for the iPhone are anywhere from 99 cents to a few dollars so it's inexpensive to try out a few of them.
For instance, I have 2 ssh clients for less than half the price of a typical app that would run on a Blackberry.
Add in the killer programmable calculator I got and it's all still below the price point of one Blackberry app.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432873</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434789</id>
	<title>Re:Thank you</title>
	<author>spazimodo</author>
	<datestamp>1245692580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I have not worked with BES 5, but it was certainly commonplace on 2.2, 3.6, and 4.0 to have to reset the devices on occasion because they would just stop syncing. I was present for numerous calls involving a help desk person, RIM support, and the carrier to try to get some traveling exec's blackberry working.</p><p>The BES is a steaming pile of shit layered upon several other steaming piles of shit. It hammers the crap out of mail servers. The install process involves magical incantations and occasionally modifying the AD schema (this one admittedly is the fault of MS and lazy admins who use domain admin accounts for their mail.) The upgrade process involves something called a "knife edge cutover" I think because slitting your wrists can seem like a practical alternative.  There's no reason removing a user from the server and then adding him again should require mucking with the DB tables directly with osql, yet that was the recommended procedure for a while. Wireless activation was a total game of chance well into when activating a Activesync device took a couple minutes and then it never had to be looked at again.</p><p>RIM's architecture made sense in 1999 when you couldn't get Internet access via cell. At this point though its an anachronism. I can appreciate the security features and policy management, but there's zero reason that this huge extra infrastructure be required in the days of unlimited mobile Internet access. Why install a BES, an MDS, a bb router, only to send your traffic to RIMs network (which has suffered several outages recently) which then goes to the carriers and to the devices?</p><p>BIS pisses me off even more. Why provide an IMAP client when you can force people to provide their login credentials to their honest and trustworthy cell phone carrier? Not to mention that well into 2008 the idea of syncing e-mail (as opposed to POP3 download) was looked at as some sort of freak request. It's not like anyone would want to get their mail from both their phone AND their PC.</p></htmltext>
<tokenext>I have not worked with BES 5 , but it was certainly commonplace on 2.2 , 3.6 , and 4.0 to have to reset the devices on occasion because they would just stop syncing .
I was present for numerous calls involving a help desk person , RIM support , and the carrier to try to get some traveling exec 's blackberry working.The BES is a steaming pile of shit layered upon several other steaming piles of shit .
It hammers the crap out of mail servers .
The install process involves magical incantations and occasionally modifying the AD schema ( this one admittedly is the fault of MS and lazy admins who use domain admin accounts for their mail .
) The upgrade process involves something called a " knife edge cutover " I think because slitting your wrists can seem like a practical alternative .
There 's no reason removing a user from the server and then adding him again should require mucking with the DB tables directly with osql , yet that was the recommended procedure for a while .
Wireless activation was a total game of chance well into when activating a Activesync device took a couple minutes and then it never had to be looked at again.RIM 's architecture made sense in 1999 when you could n't get Internet access via cell .
At this point though its an anachronism .
I can appreciate the security features and policy management , but there 's zero reason that this huge extra infrastructure be required in the days of unlimited mobile Internet access .
Why install a BES , an MDS , a bb router , only to send your traffic to RIMs network ( which has suffered several outages recently ) which then goes to the carriers and to the devices ? BIS pisses me off even more .
Why provide an IMAP client when you can force people to provide their login credentials to their honest and trustworthy cell phone carrier ?
Not to mention that well into 2008 the idea of syncing e-mail ( as opposed to POP3 download ) was looked at as some sort of freak request .
It 's not like anyone would want to get their mail from both their phone AND their PC .</tokentext>
<sentencetext>I have not worked with BES 5, but it was certainly commonplace on 2.2, 3.6, and 4.0 to have to reset the devices on occasion because they would just stop syncing.
I was present for numerous calls involving a help desk person, RIM support, and the carrier to try to get some traveling exec's blackberry working.The BES is a steaming pile of shit layered upon several other steaming piles of shit.
It hammers the crap out of mail servers.
The install process involves magical incantations and occasionally modifying the AD schema (this one admittedly is the fault of MS and lazy admins who use domain admin accounts for their mail.
) The upgrade process involves something called a "knife edge cutover" I think because slitting your wrists can seem like a practical alternative.
There's no reason removing a user from the server and then adding him again should require mucking with the DB tables directly with osql, yet that was the recommended procedure for a while.
Wireless activation was a total game of chance well into when activating a Activesync device took a couple minutes and then it never had to be looked at again.RIM's architecture made sense in 1999 when you couldn't get Internet access via cell.
At this point though its an anachronism.
I can appreciate the security features and policy management, but there's zero reason that this huge extra infrastructure be required in the days of unlimited mobile Internet access.
Why install a BES, an MDS, a bb router, only to send your traffic to RIMs network (which has suffered several outages recently) which then goes to the carriers and to the devices?BIS pisses me off even more.
Why provide an IMAP client when you can force people to provide their login credentials to their honest and trustworthy cell phone carrier?
Not to mention that well into 2008 the idea of syncing e-mail (as opposed to POP3 download) was looked at as some sort of freak request.
It's not like anyone would want to get their mail from both their phone AND their PC.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433103</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434047</id>
	<title>Re:Total</title>
	<author>baldusi</author>
	<datestamp>1245687480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Please do a follow up on what was the effect of the slashdot effect.</p></htmltext>
<tokenext>Please do a follow up on what was the effect of the slashdot effect .</tokentext>
<sentencetext>Please do a follow up on what was the effect of the slashdot effect.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433023</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435341</id>
	<title>Re:Thank you</title>
	<author>RAMMS+EIN</author>
	<datestamp>1245697980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>``Making them work as a mobile email device tied to Exchange requires a shiat-ton of ugly third party software.''</p><p>Exchange is a shiat-ton of ugly proprietary software. It does not surprise me that any product would have trouble working with it. Especially if the product is from a different vendor.</p><p>Whatever else you can fault Blackberries for, subobtimal integration with Exchange is something you can thank Microsoft for. If they wouldn't hold Exchange's protocols under tight wraps, I'm sure RIM and many others would race to provide better integration with it. Of course, that would diminish Microsoft's competitive advantage, so it is unlikely to happen, barring government intervention.</p></htmltext>
<tokenext>` ` Making them work as a mobile email device tied to Exchange requires a shiat-ton of ugly third party software .
''Exchange is a shiat-ton of ugly proprietary software .
It does not surprise me that any product would have trouble working with it .
Especially if the product is from a different vendor.Whatever else you can fault Blackberries for , subobtimal integration with Exchange is something you can thank Microsoft for .
If they would n't hold Exchange 's protocols under tight wraps , I 'm sure RIM and many others would race to provide better integration with it .
Of course , that would diminish Microsoft 's competitive advantage , so it is unlikely to happen , barring government intervention .</tokentext>
<sentencetext>``Making them work as a mobile email device tied to Exchange requires a shiat-ton of ugly third party software.
''Exchange is a shiat-ton of ugly proprietary software.
It does not surprise me that any product would have trouble working with it.
Especially if the product is from a different vendor.Whatever else you can fault Blackberries for, subobtimal integration with Exchange is something you can thank Microsoft for.
If they wouldn't hold Exchange's protocols under tight wraps, I'm sure RIM and many others would race to provide better integration with it.
Of course, that would diminish Microsoft's competitive advantage, so it is unlikely to happen, barring government intervention.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434437</id>
	<title>Re:You forgot the most important thing...</title>
	<author>NicknamesAreStupid</author>
	<datestamp>1245689700000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>0</modscore>
	<htmltext>PT Barnum would have developed software for the iPhone.  His customers would probably would have developed software for the Blackberry.</htmltext>
<tokenext>PT Barnum would have developed software for the iPhone .
His customers would probably would have developed software for the Blackberry .</tokentext>
<sentencetext>PT Barnum would have developed software for the iPhone.
His customers would probably would have developed software for the Blackberry.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432873</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434887</id>
	<title>Re:Sure there are more blackberries</title>
	<author>Anonymous</author>
	<datestamp>1245693420000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>Might be modded offtopic, but, can you play any decent games on the BlackBerry?</p><p>Or is Windows Mobile or the Iphone better for that? Absolutely necessary for those long lines at the DMV </p></htmltext>
<tokenext>Might be modded offtopic , but , can you play any decent games on the BlackBerry ? Or is Windows Mobile or the Iphone better for that ?
Absolutely necessary for those long lines at the DMV</tokentext>
<sentencetext>Might be modded offtopic, but, can you play any decent games on the BlackBerry?Or is Windows Mobile or the Iphone better for that?
Absolutely necessary for those long lines at the DMV </sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432633</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433103</id>
	<title>Re:Thank you</title>
	<author>growse</author>
	<datestamp>1245681900000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext>If you run an infrastructure with clients who frequently need factory resets and re-activations, either you've just stumbled across a huge batch of faulty devices, or you're doing it wrong.
<br>
<br>
Lets not allow an incompetent sysadmin get in the way of trashing a platform that works great for millions though. Right?</htmltext>
<tokenext>If you run an infrastructure with clients who frequently need factory resets and re-activations , either you 've just stumbled across a huge batch of faulty devices , or you 're doing it wrong .
Lets not allow an incompetent sysadmin get in the way of trashing a platform that works great for millions though .
Right ?</tokentext>
<sentencetext>If you run an infrastructure with clients who frequently need factory resets and re-activations, either you've just stumbled across a huge batch of faulty devices, or you're doing it wrong.
Lets not allow an incompetent sysadmin get in the way of trashing a platform that works great for millions though.
Right?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433913</id>
	<title>Re:Thank you</title>
	<author>Naurgrim</author>
	<datestamp>1245686760000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p> <i>Ummm, not true. BES has supported 64-bit windows and 64-bit databases for quite a long time.</i> </p><p>OK, I'll look into that.</p><p> <i>Well, then you &amp; your clients don't know how to administer a BES &amp; blackberries. The devices are extremely solid, and almost never need a factory wipe. Of course, most problems will be resolved by a factory wipe &amp; reactivating, but there is almost always a far easier &amp; faster way to resolve the issue, but it seems you don't know that.</i> </p><p>Well. since you are posting AC, I've no problem showing my claws on this response. If you are going to say I don't know what I'm doing, have the courage to state your slashdot ID, at the least.</p><p> <i>When something goes wrong with a windows pc, do you wipe your hard disk &amp; reinstall every time? That will resolve the issue, but there is almost always a simpler, easier &amp; faster solution.</i> </p><p>Seems to be the one of the most common solutions in "enterprise" situations.</p><p> <i>Reactivating a blackberry user on a BES is REALLY HARD! How hard is it? On the BES 4 series, you run the BES console, find the user, right-click on the user, and set the activation password to whatever you like. Then, on the blackberry, go to options, advanced options, enterprise activation, enter your email address, enter the activation password you just set, and click activate. Wasn't that hard?</i> </p><p>Not hard for me, but please see my above reply to Growse detailing the realities of what I do and where I live.</p><p> <i>Frankly, if your clients can't activate a blackberry by themselves, then maybe they aren't smart enough to use email.</i> </p><p>Recent case - end user bought a new blackberry on a whim. No idea what the monkeys at the verizon store did, no idea what the end user did prior to calling me. Had to walk the end user thru inserting the SIM card right side up over the phone. Given the above, first action = factory reset.</p><p>Yes, this end user is barely able to use email. Yes, the office manager at my client was concerned about my cost to get him working. So, keeping cost down for my customer = factory reset.</p><p> <i>Better? How many other solutions have real push email? None (windows mobile comes close with their fake push). How many other mobile email solutions have remote lock, remote unlock, remote wipe, solid AES encryption, certification by many governments [blackberry.com] and other agencies?. Can you force your users to have a password? Can you force your users to always encrypt the blackberry contents? Does your iphone overwrite freed memory so that the contents can't be read by disassembling the device? Nope.</i> </p><p> <i>Do you need to restrict your user from browsing the web? Do you need to centrally track SMS, email &amp; phone calls? All this is easy on the BES.</i> </p><p>These do not apply to me or my customers. See my reply to Growse above before you flame me.</p><p>As previously mentioned, I should have included details of what I do and what my customers do and need. Bottom line for me and mine is that while BES/blackberry is fine for large deployments and has all sort of features for regulatory compliance, etc. in the SMB space, they are not, IMHO the best option.</p></htmltext>
<tokenext>Ummm , not true .
BES has supported 64-bit windows and 64-bit databases for quite a long time .
OK , I 'll look into that .
Well , then you &amp; your clients do n't know how to administer a BES &amp; blackberries .
The devices are extremely solid , and almost never need a factory wipe .
Of course , most problems will be resolved by a factory wipe &amp; reactivating , but there is almost always a far easier &amp; faster way to resolve the issue , but it seems you do n't know that .
Well. since you are posting AC , I 've no problem showing my claws on this response .
If you are going to say I do n't know what I 'm doing , have the courage to state your slashdot ID , at the least .
When something goes wrong with a windows pc , do you wipe your hard disk &amp; reinstall every time ?
That will resolve the issue , but there is almost always a simpler , easier &amp; faster solution .
Seems to be the one of the most common solutions in " enterprise " situations .
Reactivating a blackberry user on a BES is REALLY HARD !
How hard is it ?
On the BES 4 series , you run the BES console , find the user , right-click on the user , and set the activation password to whatever you like .
Then , on the blackberry , go to options , advanced options , enterprise activation , enter your email address , enter the activation password you just set , and click activate .
Was n't that hard ?
Not hard for me , but please see my above reply to Growse detailing the realities of what I do and where I live .
Frankly , if your clients ca n't activate a blackberry by themselves , then maybe they are n't smart enough to use email .
Recent case - end user bought a new blackberry on a whim .
No idea what the monkeys at the verizon store did , no idea what the end user did prior to calling me .
Had to walk the end user thru inserting the SIM card right side up over the phone .
Given the above , first action = factory reset.Yes , this end user is barely able to use email .
Yes , the office manager at my client was concerned about my cost to get him working .
So , keeping cost down for my customer = factory reset .
Better ? How many other solutions have real push email ?
None ( windows mobile comes close with their fake push ) .
How many other mobile email solutions have remote lock , remote unlock , remote wipe , solid AES encryption , certification by many governments [ blackberry.com ] and other agencies ? .
Can you force your users to have a password ?
Can you force your users to always encrypt the blackberry contents ?
Does your iphone overwrite freed memory so that the contents ca n't be read by disassembling the device ?
Nope. Do you need to restrict your user from browsing the web ?
Do you need to centrally track SMS , email &amp; phone calls ?
All this is easy on the BES .
These do not apply to me or my customers .
See my reply to Growse above before you flame me.As previously mentioned , I should have included details of what I do and what my customers do and need .
Bottom line for me and mine is that while BES/blackberry is fine for large deployments and has all sort of features for regulatory compliance , etc .
in the SMB space , they are not , IMHO the best option .</tokentext>
<sentencetext> Ummm, not true.
BES has supported 64-bit windows and 64-bit databases for quite a long time.
OK, I'll look into that.
Well, then you &amp; your clients don't know how to administer a BES &amp; blackberries.
The devices are extremely solid, and almost never need a factory wipe.
Of course, most problems will be resolved by a factory wipe &amp; reactivating, but there is almost always a far easier &amp; faster way to resolve the issue, but it seems you don't know that.
Well. since you are posting AC, I've no problem showing my claws on this response.
If you are going to say I don't know what I'm doing, have the courage to state your slashdot ID, at the least.
When something goes wrong with a windows pc, do you wipe your hard disk &amp; reinstall every time?
That will resolve the issue, but there is almost always a simpler, easier &amp; faster solution.
Seems to be the one of the most common solutions in "enterprise" situations.
Reactivating a blackberry user on a BES is REALLY HARD!
How hard is it?
On the BES 4 series, you run the BES console, find the user, right-click on the user, and set the activation password to whatever you like.
Then, on the blackberry, go to options, advanced options, enterprise activation, enter your email address, enter the activation password you just set, and click activate.
Wasn't that hard?
Not hard for me, but please see my above reply to Growse detailing the realities of what I do and where I live.
Frankly, if your clients can't activate a blackberry by themselves, then maybe they aren't smart enough to use email.
Recent case - end user bought a new blackberry on a whim.
No idea what the monkeys at the verizon store did, no idea what the end user did prior to calling me.
Had to walk the end user thru inserting the SIM card right side up over the phone.
Given the above, first action = factory reset.Yes, this end user is barely able to use email.
Yes, the office manager at my client was concerned about my cost to get him working.
So, keeping cost down for my customer = factory reset.
Better? How many other solutions have real push email?
None (windows mobile comes close with their fake push).
How many other mobile email solutions have remote lock, remote unlock, remote wipe, solid AES encryption, certification by many governments [blackberry.com] and other agencies?.
Can you force your users to have a password?
Can you force your users to always encrypt the blackberry contents?
Does your iphone overwrite freed memory so that the contents can't be read by disassembling the device?
Nope.  Do you need to restrict your user from browsing the web?
Do you need to centrally track SMS, email &amp; phone calls?
All this is easy on the BES.
These do not apply to me or my customers.
See my reply to Growse above before you flame me.As previously mentioned, I should have included details of what I do and what my customers do and need.
Bottom line for me and mine is that while BES/blackberry is fine for large deployments and has all sort of features for regulatory compliance, etc.
in the SMB space, they are not, IMHO the best option.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433327</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436907</id>
	<title>Re:Bad UI library</title>
	<author>Anonymous</author>
	<datestamp>1245759180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>he's made some god-awful design choices and should have a designer to help with that. RIM provide an extensive API for creating interfaces - all he needs to do is research the API, there's a Field class anyone can extend and create their own interface elements. It's a bloody simple and elegant API as well.</p><p>And no - apps that look good DO NOT use custom drawing engines. They extend native classes. Apps that DO use custom drawing engines are slow and sluggish and do not feel like native BlackBerry applications. Apps that succeed on BlackBerry have the same interface experience as the native applications - so the user knows where everything will be. Apps that depart from this are frustrating to use, the reason so many BlackBerry apps look shit is simply because the developers don't know what they're doing AND there's no draconian style guideline that must be adhered to - you're free to make ugly-ass apps.</p><p>What iPhone has is a static target, BlackBerry has several different screensizes, each device is unique - the API handles this beautifully but you do need to go slightly lower level. Android doesn't have this issue only because there's a couple of devices in the market.</p><p>Reading TFA it's clear he's not fully comfortable with the API and should maybe have spent another couple of months getting to grips with it before writing it. Many things he criticises are actually strengths not found on any other platform (Plethora network connection options for example) but you need to understand them at a low level to see why RIM have done things the way they have.</p></htmltext>
<tokenext>he 's made some god-awful design choices and should have a designer to help with that .
RIM provide an extensive API for creating interfaces - all he needs to do is research the API , there 's a Field class anyone can extend and create their own interface elements .
It 's a bloody simple and elegant API as well.And no - apps that look good DO NOT use custom drawing engines .
They extend native classes .
Apps that DO use custom drawing engines are slow and sluggish and do not feel like native BlackBerry applications .
Apps that succeed on BlackBerry have the same interface experience as the native applications - so the user knows where everything will be .
Apps that depart from this are frustrating to use , the reason so many BlackBerry apps look shit is simply because the developers do n't know what they 're doing AND there 's no draconian style guideline that must be adhered to - you 're free to make ugly-ass apps.What iPhone has is a static target , BlackBerry has several different screensizes , each device is unique - the API handles this beautifully but you do need to go slightly lower level .
Android does n't have this issue only because there 's a couple of devices in the market.Reading TFA it 's clear he 's not fully comfortable with the API and should maybe have spent another couple of months getting to grips with it before writing it .
Many things he criticises are actually strengths not found on any other platform ( Plethora network connection options for example ) but you need to understand them at a low level to see why RIM have done things the way they have .</tokentext>
<sentencetext>he's made some god-awful design choices and should have a designer to help with that.
RIM provide an extensive API for creating interfaces - all he needs to do is research the API, there's a Field class anyone can extend and create their own interface elements.
It's a bloody simple and elegant API as well.And no - apps that look good DO NOT use custom drawing engines.
They extend native classes.
Apps that DO use custom drawing engines are slow and sluggish and do not feel like native BlackBerry applications.
Apps that succeed on BlackBerry have the same interface experience as the native applications - so the user knows where everything will be.
Apps that depart from this are frustrating to use, the reason so many BlackBerry apps look shit is simply because the developers don't know what they're doing AND there's no draconian style guideline that must be adhered to - you're free to make ugly-ass apps.What iPhone has is a static target, BlackBerry has several different screensizes, each device is unique - the API handles this beautifully but you do need to go slightly lower level.
Android doesn't have this issue only because there's a couple of devices in the market.Reading TFA it's clear he's not fully comfortable with the API and should maybe have spent another couple of months getting to grips with it before writing it.
Many things he criticises are actually strengths not found on any other platform (Plethora network connection options for example) but you need to understand them at a low level to see why RIM have done things the way they have.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433009</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432811</id>
	<title>Blackberry's problem</title>
	<author>Anonymous</author>
	<datestamp>1245680520000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>RIM needs to open the platform up. Nothing more nothing less.</htmltext>
<tokenext>RIM needs to open the platform up .
Nothing more nothing less .</tokentext>
<sentencetext>RIM needs to open the platform up.
Nothing more nothing less.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28439975</id>
	<title>Re:Thank you</title>
	<author>0xdeadbeef</author>
	<datestamp>1245776280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>The blackberry requires all your corporate communications to go through their third party server.</i></p><p>Don't forget the third party called your cell phone company and every freaking router on the Internet.</p><p>I bet all of the people going "ZOMG all my emails go through Canada!" use unencrypted IMAP on their iPhones knowing full well that AT&amp;T snoops on email for the government.</p></htmltext>
<tokenext>The blackberry requires all your corporate communications to go through their third party server.Do n't forget the third party called your cell phone company and every freaking router on the Internet.I bet all of the people going " ZOMG all my emails go through Canada !
" use unencrypted IMAP on their iPhones knowing full well that AT&amp;T snoops on email for the government .</tokentext>
<sentencetext>The blackberry requires all your corporate communications to go through their third party server.Don't forget the third party called your cell phone company and every freaking router on the Internet.I bet all of the people going "ZOMG all my emails go through Canada!
" use unencrypted IMAP on their iPhones knowing full well that AT&amp;T snoops on email for the government.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436305</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28442265</id>
	<title>Re:Thank you</title>
	<author>Anonymous</author>
	<datestamp>1245784260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I call bullshit!<br>I have twice installed the Blackberry Enterprise Server on my organization's Exchange server from scratch in under 1/2 day and had all handhelds syncing wirelessly with Exchange that same day.  At the last place I worked Exchange wasn't running RPC over HTTP(S) and therefore the iPhone would NOT sync with exchange properly.  Plus, when compared to the iPhone the Blackberry's capability as a phone (ignoring all of the other features of the two devices) is superior.  This is based on the opinion of a brilliant friend of mine who has used both in a corporate environment and is someone who travels 75\% of the time for his job.</p></htmltext>
<tokenext>I call bullshit ! I have twice installed the Blackberry Enterprise Server on my organization 's Exchange server from scratch in under 1/2 day and had all handhelds syncing wirelessly with Exchange that same day .
At the last place I worked Exchange was n't running RPC over HTTP ( S ) and therefore the iPhone would NOT sync with exchange properly .
Plus , when compared to the iPhone the Blackberry 's capability as a phone ( ignoring all of the other features of the two devices ) is superior .
This is based on the opinion of a brilliant friend of mine who has used both in a corporate environment and is someone who travels 75 \ % of the time for his job .</tokentext>
<sentencetext>I call bullshit!I have twice installed the Blackberry Enterprise Server on my organization's Exchange server from scratch in under 1/2 day and had all handhelds syncing wirelessly with Exchange that same day.
At the last place I worked Exchange wasn't running RPC over HTTP(S) and therefore the iPhone would NOT sync with exchange properly.
Plus, when compared to the iPhone the Blackberry's capability as a phone (ignoring all of the other features of the two devices) is superior.
This is based on the opinion of a brilliant friend of mine who has used both in a corporate environment and is someone who travels 75\% of the time for his job.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433705</id>
	<title>Re:Thank you</title>
	<author>Corporate T00l</author>
	<datestamp>1245685440000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>I worked for a small company that subscribed to an outsourced BES+Exchange hosting service on a per-user subscription basis.</p><p>I have to say, my experience as a user was fabulous. The syncing across calendar, mail, and contacts "just worked". Most sync tools have hidden reset options to clear you local version and restore from remote, clear the remote version and restore from local, or some kind of complex manual conflict reconcilation mechanism.</p><p>With BES, there are no such options, and you don't need them. The system just works. Nothing weird happened if I tried to erase a contact from my blackberry and my Outlook at the same time or added a calendar entry from one and then moved it on the other. Everything was push based, so changes got propagated out instantly, rather than on some kind of 1 hour poll interval. I could send out multi-person invites just using the blackberry, and other people would get them just as if I'd sent them from Outlook. In fact, the BB was often more reliable than Outlook since it dealt better with network flakiness/slowness.</p><p>But then, my company got acquired by a company that didn't use Exchange, had no BES, but had standardized on BB and iPhone. In this environment, things were radically different. Without the BES+Exchange combo, you need to use a 3rd party clunky app (possibly more than 1 depending on your setup) and you can forget about real-time anything. Everything is on at least 5 minute delay or worse (calendar and contacts are on like, 2 hour delay).</p><p>5 minute delay doesn't sound like much, but with the Exchange+BES combo, BB wielders got used to e-mailing each other as if it were IM and having a stream of 1 line conversations with each other. Now, we need to consider what we want to say and switch to SMS if we want to converse with faster turnaround (at the cost of having to cmprss r words to sub 160 chr bites).</p></htmltext>
<tokenext>I worked for a small company that subscribed to an outsourced BES + Exchange hosting service on a per-user subscription basis.I have to say , my experience as a user was fabulous .
The syncing across calendar , mail , and contacts " just worked " .
Most sync tools have hidden reset options to clear you local version and restore from remote , clear the remote version and restore from local , or some kind of complex manual conflict reconcilation mechanism.With BES , there are no such options , and you do n't need them .
The system just works .
Nothing weird happened if I tried to erase a contact from my blackberry and my Outlook at the same time or added a calendar entry from one and then moved it on the other .
Everything was push based , so changes got propagated out instantly , rather than on some kind of 1 hour poll interval .
I could send out multi-person invites just using the blackberry , and other people would get them just as if I 'd sent them from Outlook .
In fact , the BB was often more reliable than Outlook since it dealt better with network flakiness/slowness.But then , my company got acquired by a company that did n't use Exchange , had no BES , but had standardized on BB and iPhone .
In this environment , things were radically different .
Without the BES + Exchange combo , you need to use a 3rd party clunky app ( possibly more than 1 depending on your setup ) and you can forget about real-time anything .
Everything is on at least 5 minute delay or worse ( calendar and contacts are on like , 2 hour delay ) .5 minute delay does n't sound like much , but with the Exchange + BES combo , BB wielders got used to e-mailing each other as if it were IM and having a stream of 1 line conversations with each other .
Now , we need to consider what we want to say and switch to SMS if we want to converse with faster turnaround ( at the cost of having to cmprss r words to sub 160 chr bites ) .</tokentext>
<sentencetext>I worked for a small company that subscribed to an outsourced BES+Exchange hosting service on a per-user subscription basis.I have to say, my experience as a user was fabulous.
The syncing across calendar, mail, and contacts "just worked".
Most sync tools have hidden reset options to clear you local version and restore from remote, clear the remote version and restore from local, or some kind of complex manual conflict reconcilation mechanism.With BES, there are no such options, and you don't need them.
The system just works.
Nothing weird happened if I tried to erase a contact from my blackberry and my Outlook at the same time or added a calendar entry from one and then moved it on the other.
Everything was push based, so changes got propagated out instantly, rather than on some kind of 1 hour poll interval.
I could send out multi-person invites just using the blackberry, and other people would get them just as if I'd sent them from Outlook.
In fact, the BB was often more reliable than Outlook since it dealt better with network flakiness/slowness.But then, my company got acquired by a company that didn't use Exchange, had no BES, but had standardized on BB and iPhone.
In this environment, things were radically different.
Without the BES+Exchange combo, you need to use a 3rd party clunky app (possibly more than 1 depending on your setup) and you can forget about real-time anything.
Everything is on at least 5 minute delay or worse (calendar and contacts are on like, 2 hour delay).5 minute delay doesn't sound like much, but with the Exchange+BES combo, BB wielders got used to e-mailing each other as if it were IM and having a stream of 1 line conversations with each other.
Now, we need to consider what we want to say and switch to SMS if we want to converse with faster turnaround (at the cost of having to cmprss r words to sub 160 chr bites).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433327</id>
	<title>Re:Thank you</title>
	<author>Anonymous</author>
	<datestamp>1245683100000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p><i>BES is, IMHO, a steaming pile - java, dot.net,</i></p><p>Ok, BES does use many technologies. The new BES 5 even requires activeX plugins for some web-based admin tools.</p><p><i>32-bit only. Feh.</i></p><p>Ummm, not true. BES has supported 64-bit windows and 64-bit databases for quite a long time.</p><p><i>Recent iPhones handle active sync nicely and don't bitch about self-signed certs.</i></p><p>Ummm, that's called a <b>security flaw</b> by most competent admins. Frankly, if you can't afford $12.99/year (with coupon code) to get a godaddy signed certificate, maybe security isn't what you're looking for. Is it possible to install your own certificate authority on iphone (or is it that apple doesn't let you)? You can install your own certificates on blackberry, and even manage them all centrally on the BES. You can even use S/MIME &amp; PGP for additional email encryption.</p><p><i>My clients pay $$ for BES CALs, the devices get stupid and need to be factory reset often and re-activated, costing my client more $$ for my time.</i></p><p>Well, then you &amp; your clients don't know how to administer a BES &amp; blackberries. The devices are extremely solid, and almost never need a factory wipe. Of course, most problems will be resolved by a factory wipe &amp; reactivating, but there is almost always a far easier &amp; faster way to resolve the issue, but it seems you don't know that.</p><p>When something goes wrong with a windows pc, do you wipe your hard disk &amp; reinstall every time? That will resolve the issue, but there is almost always a simpler, easier &amp; faster solution.</p><p><b>Reactivating a blackberry user on a BES is REALLY HARD!</b> How hard is it? On the BES 4 series, you run the BES console, find the user, right-click on the user, and set the activation password to whatever you like. Then, on the blackberry, go to options, advanced options, enterprise activation, enter your email address, enter the activation password you just set, and click activate.  Wasn't that hard?</p><p>Frankly, if your clients can't activate a blackberry by themselves, then maybe they aren't smart enough to use email.</p><p><i>I honestly cannot see the attraction when there are better solutions to talk to an Exchange server</i></p><p>Better? How many other solutions have real push email? None (windows mobile comes close with their fake push). How many other mobile email solutions have remote lock, remote unlock, remote wipe, solid AES encryption, certification by <a href="http://na.blackberry.com/eng/ataglance/security/certifications.jsp" title="blackberry.com" rel="nofollow">many governments</a> [blackberry.com] and other agencies?. Can you force your users to have a password? Can you force your users to always encrypt the blackberry contents? Does your iphone overwrite freed memory so that the contents can't be read by disassembling the device? Nope.</p><p>Do you need to restrict your user from browsing the web? Do you need to centrally track SMS, email &amp; phone calls? All this is easy on the BES.</p><p><i>iPhones, WinMobile or a laptop with RPC over HTTP(S) all work more simply</i></p><p>Ok, that's true. The BES platform is complex, but that is because it does so much.</p><p>Look, BES isn't for everyone - there is a lot of complexity &amp; a lot to learn. You may be better off with an outsourced BES provider (there are many). Or choose the Blackberry Professional Software (BPS), which is a simpler, easier to use BES-lite.</p></htmltext>
<tokenext>BES is , IMHO , a steaming pile - java , dot.net,Ok , BES does use many technologies .
The new BES 5 even requires activeX plugins for some web-based admin tools.32-bit only .
Feh.Ummm , not true .
BES has supported 64-bit windows and 64-bit databases for quite a long time.Recent iPhones handle active sync nicely and do n't bitch about self-signed certs.Ummm , that 's called a security flaw by most competent admins .
Frankly , if you ca n't afford $ 12.99/year ( with coupon code ) to get a godaddy signed certificate , maybe security is n't what you 're looking for .
Is it possible to install your own certificate authority on iphone ( or is it that apple does n't let you ) ?
You can install your own certificates on blackberry , and even manage them all centrally on the BES .
You can even use S/MIME &amp; PGP for additional email encryption.My clients pay $ $ for BES CALs , the devices get stupid and need to be factory reset often and re-activated , costing my client more $ $ for my time.Well , then you &amp; your clients do n't know how to administer a BES &amp; blackberries .
The devices are extremely solid , and almost never need a factory wipe .
Of course , most problems will be resolved by a factory wipe &amp; reactivating , but there is almost always a far easier &amp; faster way to resolve the issue , but it seems you do n't know that.When something goes wrong with a windows pc , do you wipe your hard disk &amp; reinstall every time ?
That will resolve the issue , but there is almost always a simpler , easier &amp; faster solution.Reactivating a blackberry user on a BES is REALLY HARD !
How hard is it ?
On the BES 4 series , you run the BES console , find the user , right-click on the user , and set the activation password to whatever you like .
Then , on the blackberry , go to options , advanced options , enterprise activation , enter your email address , enter the activation password you just set , and click activate .
Was n't that hard ? Frankly , if your clients ca n't activate a blackberry by themselves , then maybe they are n't smart enough to use email.I honestly can not see the attraction when there are better solutions to talk to an Exchange serverBetter ?
How many other solutions have real push email ?
None ( windows mobile comes close with their fake push ) .
How many other mobile email solutions have remote lock , remote unlock , remote wipe , solid AES encryption , certification by many governments [ blackberry.com ] and other agencies ? .
Can you force your users to have a password ?
Can you force your users to always encrypt the blackberry contents ?
Does your iphone overwrite freed memory so that the contents ca n't be read by disassembling the device ?
Nope.Do you need to restrict your user from browsing the web ?
Do you need to centrally track SMS , email &amp; phone calls ?
All this is easy on the BES.iPhones , WinMobile or a laptop with RPC over HTTP ( S ) all work more simplyOk , that 's true .
The BES platform is complex , but that is because it does so much.Look , BES is n't for everyone - there is a lot of complexity &amp; a lot to learn .
You may be better off with an outsourced BES provider ( there are many ) .
Or choose the Blackberry Professional Software ( BPS ) , which is a simpler , easier to use BES-lite .</tokentext>
<sentencetext>BES is, IMHO, a steaming pile - java, dot.net,Ok, BES does use many technologies.
The new BES 5 even requires activeX plugins for some web-based admin tools.32-bit only.
Feh.Ummm, not true.
BES has supported 64-bit windows and 64-bit databases for quite a long time.Recent iPhones handle active sync nicely and don't bitch about self-signed certs.Ummm, that's called a security flaw by most competent admins.
Frankly, if you can't afford $12.99/year (with coupon code) to get a godaddy signed certificate, maybe security isn't what you're looking for.
Is it possible to install your own certificate authority on iphone (or is it that apple doesn't let you)?
You can install your own certificates on blackberry, and even manage them all centrally on the BES.
You can even use S/MIME &amp; PGP for additional email encryption.My clients pay $$ for BES CALs, the devices get stupid and need to be factory reset often and re-activated, costing my client more $$ for my time.Well, then you &amp; your clients don't know how to administer a BES &amp; blackberries.
The devices are extremely solid, and almost never need a factory wipe.
Of course, most problems will be resolved by a factory wipe &amp; reactivating, but there is almost always a far easier &amp; faster way to resolve the issue, but it seems you don't know that.When something goes wrong with a windows pc, do you wipe your hard disk &amp; reinstall every time?
That will resolve the issue, but there is almost always a simpler, easier &amp; faster solution.Reactivating a blackberry user on a BES is REALLY HARD!
How hard is it?
On the BES 4 series, you run the BES console, find the user, right-click on the user, and set the activation password to whatever you like.
Then, on the blackberry, go to options, advanced options, enterprise activation, enter your email address, enter the activation password you just set, and click activate.
Wasn't that hard?Frankly, if your clients can't activate a blackberry by themselves, then maybe they aren't smart enough to use email.I honestly cannot see the attraction when there are better solutions to talk to an Exchange serverBetter?
How many other solutions have real push email?
None (windows mobile comes close with their fake push).
How many other mobile email solutions have remote lock, remote unlock, remote wipe, solid AES encryption, certification by many governments [blackberry.com] and other agencies?.
Can you force your users to have a password?
Can you force your users to always encrypt the blackberry contents?
Does your iphone overwrite freed memory so that the contents can't be read by disassembling the device?
Nope.Do you need to restrict your user from browsing the web?
Do you need to centrally track SMS, email &amp; phone calls?
All this is easy on the BES.iPhones, WinMobile or a laptop with RPC over HTTP(S) all work more simplyOk, that's true.
The BES platform is complex, but that is because it does so much.Look, BES isn't for everyone - there is a lot of complexity &amp; a lot to learn.
You may be better off with an outsourced BES provider (there are many).
Or choose the Blackberry Professional Software (BPS), which is a simpler, easier to use BES-lite.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435363</id>
	<title>Re:Sure there are more blackberries</title>
	<author>ballwall</author>
	<datestamp>1245698100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Depends largely on the game, I think. As far as I know there's no graphic or 3d acceleration available on any of the BlackBerry devices.</p></htmltext>
<tokenext>Depends largely on the game , I think .
As far as I know there 's no graphic or 3d acceleration available on any of the BlackBerry devices .</tokentext>
<sentencetext>Depends largely on the game, I think.
As far as I know there's no graphic or 3d acceleration available on any of the BlackBerry devices.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434887</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28438523</id>
	<title>Great read</title>
	<author>thePowerOfGrayskull</author>
	<datestamp>1245770460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>As someone starting to develop a BB app for app world et al  myself, I just wanted to thank you for taking the time to write that article. That was an excellent read, and very helpful.</htmltext>
<tokenext>As someone starting to develop a BB app for app world et al myself , I just wanted to thank you for taking the time to write that article .
That was an excellent read , and very helpful .</tokentext>
<sentencetext>As someone starting to develop a BB app for app world et al  myself, I just wanted to thank you for taking the time to write that article.
That was an excellent read, and very helpful.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434091</id>
	<title>BB vs Windows Mobile</title>
	<author>raind</author>
	<datestamp>1245687720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>No way have I found a BB device less painful to support than a Windows Mobile phone. Both have there problems, most time it's the provider or user. If you have a good running Exchange server(s) I'll take a BB everytime.</p></htmltext>
<tokenext>No way have I found a BB device less painful to support than a Windows Mobile phone .
Both have there problems , most time it 's the provider or user .
If you have a good running Exchange server ( s ) I 'll take a BB everytime .</tokentext>
<sentencetext>No way have I found a BB device less painful to support than a Windows Mobile phone.
Both have there problems, most time it's the provider or user.
If you have a good running Exchange server(s) I'll take a BB everytime.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434761</id>
	<title>Re:Thank you</title>
	<author>dark42</author>
	<datestamp>1245692340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>iPhones have had remote wipe for a year now, since the 2.0 update.</p></htmltext>
<tokenext>iPhones have had remote wipe for a year now , since the 2.0 update .</tokentext>
<sentencetext>iPhones have had remote wipe for a year now, since the 2.0 update.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435019</id>
	<title>Re:Thank you</title>
	<author>IceCreamGuy</author>
	<datestamp>1245694680000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p><div class="quote"><p>Blackberries on BES offer enterprise features simply unheard of with Winmobile or iphone devices.</p> </div><p>Maybe unheard of to <i>you</i>. <a href="http://technet.microsoft.com/en-us/library/bb123484.aspx" title="microsoft.com">http://technet.microsoft.com/en-us/library/bb123484.aspx</a> [microsoft.com] I count well over 100 group policy settings that can be applied through Activesync to a Windows Mobile 6.1 device. Some of these actually do work on an iPhone as well, such as the password and phone lock policies.</p><p><div class="quote"><p>Windows mobile only recently got the much needed security features such as remote device deactivation and wiping.</p></div><p>Windows Mobile + Exchange 2003/2007 have had this functionality since 2005 at the release of Exchange 2003 SP2 <a href="http://www.microsoft.com/DOWNLOADS/details.aspx?familyid=535BEF85-3096-45F8-AA43-60F1F58B3C40&amp;displaylang=en" title="microsoft.com">http://www.microsoft.com/DOWNLOADS/details.aspx?familyid=535BEF85-3096-45F8-AA43-60F1F58B3C40&amp;displaylang=en</a> [microsoft.com]. It even works on an iPhone. I'd hardly call 2005 "recent" in the IT world.</p></div>
	</htmltext>
<tokenext>Blackberries on BES offer enterprise features simply unheard of with Winmobile or iphone devices .
Maybe unheard of to you .
http : //technet.microsoft.com/en-us/library/bb123484.aspx [ microsoft.com ] I count well over 100 group policy settings that can be applied through Activesync to a Windows Mobile 6.1 device .
Some of these actually do work on an iPhone as well , such as the password and phone lock policies.Windows mobile only recently got the much needed security features such as remote device deactivation and wiping.Windows Mobile + Exchange 2003/2007 have had this functionality since 2005 at the release of Exchange 2003 SP2 http : //www.microsoft.com/DOWNLOADS/details.aspx ? familyid = 535BEF85-3096-45F8-AA43-60F1F58B3C40&amp;displaylang = en [ microsoft.com ] .
It even works on an iPhone .
I 'd hardly call 2005 " recent " in the IT world .</tokentext>
<sentencetext>Blackberries on BES offer enterprise features simply unheard of with Winmobile or iphone devices.
Maybe unheard of to you.
http://technet.microsoft.com/en-us/library/bb123484.aspx [microsoft.com] I count well over 100 group policy settings that can be applied through Activesync to a Windows Mobile 6.1 device.
Some of these actually do work on an iPhone as well, such as the password and phone lock policies.Windows mobile only recently got the much needed security features such as remote device deactivation and wiping.Windows Mobile + Exchange 2003/2007 have had this functionality since 2005 at the release of Exchange 2003 SP2 http://www.microsoft.com/DOWNLOADS/details.aspx?familyid=535BEF85-3096-45F8-AA43-60F1F58B3C40&amp;displaylang=en [microsoft.com].
It even works on an iPhone.
I'd hardly call 2005 "recent" in the IT world.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435313</id>
	<title>Re:Thank you</title>
	<author>gemada</author>
	<datestamp>1245697740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>My experience as a sysadmin is the exact opposite of yours. Having rolled out over 30 BES implementations, they tend to work almost flawlessly and require no 3rd party software to work with Exchange, since that is the whole point of a BES. The BB, BES combo is robust and reliable. The CAL' s are cheap, certs are not required for security as on a WInMo or iPhone and BB's rarely need to get reset unlike the steaming pile that is WinMo. iPhones are nice for home users but activesync just doesn't have the functionality of BES (and activesync pounds away on a server like there is no tomorrow). Your post seems like complete FUD, or you don't know how to setup and manage BES/BB implementations, and has not been the experience of myself or any other BES admins i know. BB's "just work", unlike WinMo.</htmltext>
<tokenext>My experience as a sysadmin is the exact opposite of yours .
Having rolled out over 30 BES implementations , they tend to work almost flawlessly and require no 3rd party software to work with Exchange , since that is the whole point of a BES .
The BB , BES combo is robust and reliable .
The CAL ' s are cheap , certs are not required for security as on a WInMo or iPhone and BB 's rarely need to get reset unlike the steaming pile that is WinMo .
iPhones are nice for home users but activesync just does n't have the functionality of BES ( and activesync pounds away on a server like there is no tomorrow ) .
Your post seems like complete FUD , or you do n't know how to setup and manage BES/BB implementations , and has not been the experience of myself or any other BES admins i know .
BB 's " just work " , unlike WinMo .</tokentext>
<sentencetext>My experience as a sysadmin is the exact opposite of yours.
Having rolled out over 30 BES implementations, they tend to work almost flawlessly and require no 3rd party software to work with Exchange, since that is the whole point of a BES.
The BB, BES combo is robust and reliable.
The CAL' s are cheap, certs are not required for security as on a WInMo or iPhone and BB's rarely need to get reset unlike the steaming pile that is WinMo.
iPhones are nice for home users but activesync just doesn't have the functionality of BES (and activesync pounds away on a server like there is no tomorrow).
Your post seems like complete FUD, or you don't know how to setup and manage BES/BB implementations, and has not been the experience of myself or any other BES admins i know.
BB's "just work", unlike WinMo.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28437963</id>
	<title>Re:Thank you</title>
	<author>(arg!)Styopa</author>
	<datestamp>1245767580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Sounds like most of the 'features' you recommend are the reason most business users think that their admins are Nazis.</p><p>Google Maps?  (a *far* better app than the shitty garbage installed by default on BBs)  Sorry, no installs allowed.<br>Ebook reader for all those hours I spend in airports traveling for your goddamned company?  Sorry, no installs allowed.<br>Opera, so I can make more business flight arrangements reasonably easily, instead of the crappy BB default browser?</p><p>As an email reader, it's the bomb.  As a 'multifunction' device - entirely due to FASCIST IT departments - my BB is nearly worthless.</p><p>As I've seen more devices proliferate that will do the 'email synch' thing as well or better than BB, I'm delightedly looking forward to the expiry of my BB so I can hurl it in the trash.</p><p>(And by the way, I entirely understand that businesses don't necessarily want their staff filling the BB's with dodgy grey-market apps that end up locking the BB and causing the IT dept more hours supporting them.  I get it.  But the BES is *so* easy for lazy IT depts to totally lockdown without any consideration that there ARE useful external apps, THAT is what I object to.  BES is like the electronic version of The Stanford Expiriment, where we get to see the 'Closet Commissar' lurking in the heart of every Dew-swilling IT manager.)</p></htmltext>
<tokenext>Sounds like most of the 'features ' you recommend are the reason most business users think that their admins are Nazis.Google Maps ?
( a * far * better app than the shitty garbage installed by default on BBs ) Sorry , no installs allowed.Ebook reader for all those hours I spend in airports traveling for your goddamned company ?
Sorry , no installs allowed.Opera , so I can make more business flight arrangements reasonably easily , instead of the crappy BB default browser ? As an email reader , it 's the bomb .
As a 'multifunction ' device - entirely due to FASCIST IT departments - my BB is nearly worthless.As I 've seen more devices proliferate that will do the 'email synch ' thing as well or better than BB , I 'm delightedly looking forward to the expiry of my BB so I can hurl it in the trash .
( And by the way , I entirely understand that businesses do n't necessarily want their staff filling the BB 's with dodgy grey-market apps that end up locking the BB and causing the IT dept more hours supporting them .
I get it .
But the BES is * so * easy for lazy IT depts to totally lockdown without any consideration that there ARE useful external apps , THAT is what I object to .
BES is like the electronic version of The Stanford Expiriment , where we get to see the 'Closet Commissar ' lurking in the heart of every Dew-swilling IT manager .
)</tokentext>
<sentencetext>Sounds like most of the 'features' you recommend are the reason most business users think that their admins are Nazis.Google Maps?
(a *far* better app than the shitty garbage installed by default on BBs)  Sorry, no installs allowed.Ebook reader for all those hours I spend in airports traveling for your goddamned company?
Sorry, no installs allowed.Opera, so I can make more business flight arrangements reasonably easily, instead of the crappy BB default browser?As an email reader, it's the bomb.
As a 'multifunction' device - entirely due to FASCIST IT departments - my BB is nearly worthless.As I've seen more devices proliferate that will do the 'email synch' thing as well or better than BB, I'm delightedly looking forward to the expiry of my BB so I can hurl it in the trash.
(And by the way, I entirely understand that businesses don't necessarily want their staff filling the BB's with dodgy grey-market apps that end up locking the BB and causing the IT dept more hours supporting them.
I get it.
But the BES is *so* easy for lazy IT depts to totally lockdown without any consideration that there ARE useful external apps, THAT is what I object to.
BES is like the electronic version of The Stanford Expiriment, where we get to see the 'Closet Commissar' lurking in the heart of every Dew-swilling IT manager.
)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433593</id>
	<title>Re:Blackberry's problem</title>
	<author>Corporate T00l</author>
	<datestamp>1245684840000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>From the article, it seems like the platform already is pretty open:

<ul>
<li>No talk about complexities having to buy an SDK</li>
<li>No issues trying to become an "approved" developer</li>
<li>No need for an approval committee to decide if your app is worthy for the device</li>
</ul><p>

The main complexities seem to have to do with the sheer diversity related to the multi-carrier and multi-hardware aspects of the BB platform (e.g. the author mentions 10 different ways of getting a network connection and shortcomings of the built-in SDK UI widgets).</p></htmltext>
<tokenext>From the article , it seems like the platform already is pretty open : No talk about complexities having to buy an SDK No issues trying to become an " approved " developer No need for an approval committee to decide if your app is worthy for the device The main complexities seem to have to do with the sheer diversity related to the multi-carrier and multi-hardware aspects of the BB platform ( e.g .
the author mentions 10 different ways of getting a network connection and shortcomings of the built-in SDK UI widgets ) .</tokentext>
<sentencetext>From the article, it seems like the platform already is pretty open:


No talk about complexities having to buy an SDK
No issues trying to become an "approved" developer
No need for an approval committee to decide if your app is worthy for the device


The main complexities seem to have to do with the sheer diversity related to the multi-carrier and multi-hardware aspects of the BB platform (e.g.
the author mentions 10 different ways of getting a network connection and shortcomings of the built-in SDK UI widgets).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432811</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433511</id>
	<title>Re:Bad UI library</title>
	<author>Anonymous</author>
	<datestamp>1245684360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You can use <a href="https://lwuit.dev.java.net/" title="java.net" rel="nofollow">lwuit</a> [java.net] on the blackberry. This can provide a nice UI to J2ME applications.</p></htmltext>
<tokenext>You can use lwuit [ java.net ] on the blackberry .
This can provide a nice UI to J2ME applications .</tokentext>
<sentencetext>You can use lwuit [java.net] on the blackberry.
This can provide a nice UI to J2ME applications.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433009</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435397</id>
	<title>Re:Thank you</title>
	<author>Anne Thwacks</author>
	<datestamp>1245698400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><i>as a SysAdmin<nobr> <wbr></nobr>... iPhone first, WinMobile second, blackberry distant third.</i> <p>
Well, as a user, business or otherwise, Winmobile over my dead body.</p><p>
Seriously, I love my BB, while Winmobile crashed several times a day, usually using all my apps and data. That is "Goods not of merchandisable quality" in my estimation, and the H/W manufactuers did not even allow a <b> paid</b> upgrade when a new version of the OS came out. </p><p>
I am not saying BB is perfect, but IPhone is not for me, and BB works. (I really wanted an upgrade of my Sony Ericsson P1i, with accelerometers, GPS and Android, but SE dont seem to care what customers want.)</p></htmltext>
<tokenext>as a SysAdmin ... iPhone first , WinMobile second , blackberry distant third .
Well , as a user , business or otherwise , Winmobile over my dead body .
Seriously , I love my BB , while Winmobile crashed several times a day , usually using all my apps and data .
That is " Goods not of merchandisable quality " in my estimation , and the H/W manufactuers did not even allow a paid upgrade when a new version of the OS came out .
I am not saying BB is perfect , but IPhone is not for me , and BB works .
( I really wanted an upgrade of my Sony Ericsson P1i , with accelerometers , GPS and Android , but SE dont seem to care what customers want .
)</tokentext>
<sentencetext>as a SysAdmin ... iPhone first, WinMobile second, blackberry distant third.
Well, as a user, business or otherwise, Winmobile over my dead body.
Seriously, I love my BB, while Winmobile crashed several times a day, usually using all my apps and data.
That is "Goods not of merchandisable quality" in my estimation, and the H/W manufactuers did not even allow a  paid upgrade when a new version of the OS came out.
I am not saying BB is perfect, but IPhone is not for me, and BB works.
(I really wanted an upgrade of my Sony Ericsson P1i, with accelerometers, GPS and Android, but SE dont seem to care what customers want.
)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28437625</id>
	<title>You know, the first FREE app and you're history</title>
	<author>Anonymous</author>
	<datestamp>1245765720000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>It won't be long.  Then what?</p></htmltext>
<tokenext>It wo n't be long .
Then what ?</tokentext>
<sentencetext>It won't be long.
Then what?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433023</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436305</id>
	<title>Re:Thank you</title>
	<author>Anonymous</author>
	<datestamp>1245751860000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>I'm sorry, are you kidding me?  The blackberry requires all your corporate communications to go through their third party server.  That's the big security hole you need to be worried about, right there.</p></htmltext>
<tokenext>I 'm sorry , are you kidding me ?
The blackberry requires all your corporate communications to go through their third party server .
That 's the big security hole you need to be worried about , right there .</tokentext>
<sentencetext>I'm sorry, are you kidding me?
The blackberry requires all your corporate communications to go through their third party server.
That's the big security hole you need to be worried about, right there.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434239</id>
	<title>Re:Thank you</title>
	<author>BSDevil</author>
	<datestamp>1245688440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p> Making them work as a mobile email device tied to Exchange requires a shiat-ton of ugly third party software.</p></div><p>Or you need better support/training. Or you're just biased against the BES system. Yeah, it's got its quirks (like most pieces of software that size), but once you figure it out it's not especially difficult, and takes about a minute to create a new user and provision the device.</p><p>Also may have been that the guy that taught me how to do it used to do BES SV&amp;V at RIM until he decided he didn't like living in Kitchener-Waterloo any more.</p></div>
	</htmltext>
<tokenext>Making them work as a mobile email device tied to Exchange requires a shiat-ton of ugly third party software.Or you need better support/training .
Or you 're just biased against the BES system .
Yeah , it 's got its quirks ( like most pieces of software that size ) , but once you figure it out it 's not especially difficult , and takes about a minute to create a new user and provision the device.Also may have been that the guy that taught me how to do it used to do BES SV&amp;V at RIM until he decided he did n't like living in Kitchener-Waterloo any more .</tokentext>
<sentencetext> Making them work as a mobile email device tied to Exchange requires a shiat-ton of ugly third party software.Or you need better support/training.
Or you're just biased against the BES system.
Yeah, it's got its quirks (like most pieces of software that size), but once you figure it out it's not especially difficult, and takes about a minute to create a new user and provision the device.Also may have been that the guy that taught me how to do it used to do BES SV&amp;V at RIM until he decided he didn't like living in Kitchener-Waterloo any more.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433333</id>
	<title>Re:You forgot the most important thing...</title>
	<author>Anonymous</author>
	<datestamp>1245683220000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>Iphone users are fascinated by crappy, shiny things, so they are likely to buy any old app with good marketing.</p><p>On the other hand, blackberry users will soberly do a cost-benefit analysis before buying an app, so you're much less likely to sell.</p></div></blockquote><p>Except for the fact that you didn't RTFA, where he *said* that marketing ended up being a very important part of the process.</p></div>
	</htmltext>
<tokenext>Iphone users are fascinated by crappy , shiny things , so they are likely to buy any old app with good marketing.On the other hand , blackberry users will soberly do a cost-benefit analysis before buying an app , so you 're much less likely to sell.Except for the fact that you did n't RTFA , where he * said * that marketing ended up being a very important part of the process .</tokentext>
<sentencetext>Iphone users are fascinated by crappy, shiny things, so they are likely to buy any old app with good marketing.On the other hand, blackberry users will soberly do a cost-benefit analysis before buying an app, so you're much less likely to sell.Except for the fact that you didn't RTFA, where he *said* that marketing ended up being a very important part of the process.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432873</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28438763</id>
	<title>Re:Thank you</title>
	<author>epiphani</author>
	<datestamp>1245771540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Eh, yeah.  But it is encrypted at your site straight down to your device.  The encryption keys are specific to your BES and your device, and RIM doesn't have any visibility into them.  So it's far more secure than anything else out there.</p></htmltext>
<tokenext>Eh , yeah .
But it is encrypted at your site straight down to your device .
The encryption keys are specific to your BES and your device , and RIM does n't have any visibility into them .
So it 's far more secure than anything else out there .</tokentext>
<sentencetext>Eh, yeah.
But it is encrypted at your site straight down to your device.
The encryption keys are specific to your BES and your device, and RIM doesn't have any visibility into them.
So it's far more secure than anything else out there.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436305</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432633</id>
	<title>Sure there are more blackberries</title>
	<author>nurb432</author>
	<datestamp>1245679620000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>But, there more are corporate users without the right to install anything...</p></htmltext>
<tokenext>But , there more are corporate users without the right to install anything.. .</tokentext>
<sentencetext>But, there more are corporate users without the right to install anything...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433431</id>
	<title>Re:Thank you</title>
	<author>TheRealSlimShady</author>
	<datestamp>1245683880000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>You know, bitching about self signed certs is actually a Good Thing.  I'd rather my device/client told me that a cert is only self signed, then that gives me an indication of the level of trust (a self signed certificate just says "i'm ok, trust me").</p></htmltext>
<tokenext>You know , bitching about self signed certs is actually a Good Thing .
I 'd rather my device/client told me that a cert is only self signed , then that gives me an indication of the level of trust ( a self signed certificate just says " i 'm ok , trust me " ) .</tokentext>
<sentencetext>You know, bitching about self signed certs is actually a Good Thing.
I'd rather my device/client told me that a cert is only self signed, then that gives me an indication of the level of trust (a self signed certificate just says "i'm ok, trust me").</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433009</id>
	<title>Bad UI library</title>
	<author>Anonymous</author>
	<datestamp>1245681480000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>He's certainly right about one thing: his app has an ass UI.  It's RIM's fault, of course.  On the Palm, Android, or iPhone platforms even "hello, world!" looks great.  On BlackBerry it's impossible to get even a simple app to look good.  All apps on BlackBerry that do, in fact, look good are using full-custom drawing engines.  See Bloomberg, Facebook, etc.  For the small developer, doing your own custom drawing is a huge undertaking assuming you have any visual design talent to speak of.</htmltext>
<tokenext>He 's certainly right about one thing : his app has an ass UI .
It 's RIM 's fault , of course .
On the Palm , Android , or iPhone platforms even " hello , world !
" looks great .
On BlackBerry it 's impossible to get even a simple app to look good .
All apps on BlackBerry that do , in fact , look good are using full-custom drawing engines .
See Bloomberg , Facebook , etc .
For the small developer , doing your own custom drawing is a huge undertaking assuming you have any visual design talent to speak of .</tokentext>
<sentencetext>He's certainly right about one thing: his app has an ass UI.
It's RIM's fault, of course.
On the Palm, Android, or iPhone platforms even "hello, world!
" looks great.
On BlackBerry it's impossible to get even a simple app to look good.
All apps on BlackBerry that do, in fact, look good are using full-custom drawing engines.
See Bloomberg, Facebook, etc.
For the small developer, doing your own custom drawing is a huge undertaking assuming you have any visual design talent to speak of.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081</id>
	<title>Re:Thank you</title>
	<author>gotpaint32</author>
	<datestamp>1245681780000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>Blackberries on BES offer enterprise features simply unheard of with Winmobile or iphone devices. Windows mobile only recently got the much needed security features such as remote device deactivation and wiping. Blackberries simply offer more for the enterprise such as a slew of custom encryption features, mds for intranet based apps, web proxy features so you can control user's network browsing, full featured logging (down to the phone calls you make) fully customizable IT and security policies, and I'm sure I'm missing a ton of other features that Blackberry offers that has not even been contemplated for Winmobile much less iphones.

Maybe you should be offering your customers reasons to use Blackberries and not reasons to make your job easier. You never know, they may think that one of those features you don't care too much about is pretty nifty...</htmltext>
<tokenext>Blackberries on BES offer enterprise features simply unheard of with Winmobile or iphone devices .
Windows mobile only recently got the much needed security features such as remote device deactivation and wiping .
Blackberries simply offer more for the enterprise such as a slew of custom encryption features , mds for intranet based apps , web proxy features so you can control user 's network browsing , full featured logging ( down to the phone calls you make ) fully customizable IT and security policies , and I 'm sure I 'm missing a ton of other features that Blackberry offers that has not even been contemplated for Winmobile much less iphones .
Maybe you should be offering your customers reasons to use Blackberries and not reasons to make your job easier .
You never know , they may think that one of those features you do n't care too much about is pretty nifty.. .</tokentext>
<sentencetext>Blackberries on BES offer enterprise features simply unheard of with Winmobile or iphone devices.
Windows mobile only recently got the much needed security features such as remote device deactivation and wiping.
Blackberries simply offer more for the enterprise such as a slew of custom encryption features, mds for intranet based apps, web proxy features so you can control user's network browsing, full featured logging (down to the phone calls you make) fully customizable IT and security policies, and I'm sure I'm missing a ton of other features that Blackberry offers that has not even been contemplated for Winmobile much less iphones.
Maybe you should be offering your customers reasons to use Blackberries and not reasons to make your job easier.
You never know, they may think that one of those features you don't care too much about is pretty nifty...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28438001</id>
	<title>Re:smartphone masturbation</title>
	<author>thePowerOfGrayskull</author>
	<datestamp>1245767820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Did somebody's widdle Blackberry abandon him as a child? Hmmmm? Myes, I know it did, yes it diddums....</htmltext>
<tokenext>Did somebody 's widdle Blackberry abandon him as a child ?
Hmmmm ? Myes , I know it did , yes it diddums... .</tokentext>
<sentencetext>Did somebody's widdle Blackberry abandon him as a child?
Hmmmm? Myes, I know it did, yes it diddums....</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432901</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28438577</id>
	<title>Why Audible isn't calling you...</title>
	<author>eyal0</author>
	<datestamp>1245770640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I admit no knowledge of Blackberry phones or their apps.  Your detailed account of development was super-interesting and I wish you the best of luck.  Just one comment:</p><p>You've been trying to contact Audible but they're not returning your calls.  Reminds me of this:</p><p><a href="http://www.joelonsoftware.com/items/2009/06/10c.html" title="joelonsoftware.com" rel="nofollow">http://www.joelonsoftware.com/items/2009/06/10c.html</a> [joelonsoftware.com]</p><p>Maybe Audible doesn't want to help you because they want to implement what you've already done?</p></htmltext>
<tokenext>I admit no knowledge of Blackberry phones or their apps .
Your detailed account of development was super-interesting and I wish you the best of luck .
Just one comment : You 've been trying to contact Audible but they 're not returning your calls .
Reminds me of this : http : //www.joelonsoftware.com/items/2009/06/10c.html [ joelonsoftware.com ] Maybe Audible does n't want to help you because they want to implement what you 've already done ?</tokentext>
<sentencetext>I admit no knowledge of Blackberry phones or their apps.
Your detailed account of development was super-interesting and I wish you the best of luck.
Just one comment:You've been trying to contact Audible but they're not returning your calls.
Reminds me of this:http://www.joelonsoftware.com/items/2009/06/10c.html [joelonsoftware.com]Maybe Audible doesn't want to help you because they want to implement what you've already done?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434325</id>
	<title>Re:Bad UI library</title>
	<author>jcr</author>
	<datestamp>1245688920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>his app has an ass UI. It's RIM's fault, of course.</i></p><p>RIM may not be helping much, but that doesn't make it their fault.  A developer certainly has the option of implementing their own UI.</p><p>-jcr</p></htmltext>
<tokenext>his app has an ass UI .
It 's RIM 's fault , of course.RIM may not be helping much , but that does n't make it their fault .
A developer certainly has the option of implementing their own UI.-jcr</tokentext>
<sentencetext>his app has an ass UI.
It's RIM's fault, of course.RIM may not be helping much, but that doesn't make it their fault.
A developer certainly has the option of implementing their own UI.-jcr</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433009</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432933</id>
	<title>Re:Blackberry's problem</title>
	<author>Anonymous</author>
	<datestamp>1245681060000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><blockquote><div><p> <i>
RIM needs to open the platform up. Nothing more nothing less.</i></p></div> </blockquote><p>
I thought Java was already quite open.
</p><p>
Doesn't mean it's easy.  But it's open.</p></div>
	</htmltext>
<tokenext>RIM needs to open the platform up .
Nothing more nothing less .
I thought Java was already quite open .
Does n't mean it 's easy .
But it 's open .</tokentext>
<sentencetext> 
RIM needs to open the platform up.
Nothing more nothing less.
I thought Java was already quite open.
Doesn't mean it's easy.
But it's open.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432811</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434083</id>
	<title>Re:Thank you</title>
	<author>Hurricane78</author>
	<datestamp>1245687600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The obvious error here, is that you have to use Exchange as the e-mail server (if you can still call that e-mail). ^^</p><p>Put some CourierIMAPS on there, if you can.</p></htmltext>
<tokenext>The obvious error here , is that you have to use Exchange as the e-mail server ( if you can still call that e-mail ) .
^ ^ Put some CourierIMAPS on there , if you can .</tokentext>
<sentencetext>The obvious error here, is that you have to use Exchange as the e-mail server (if you can still call that e-mail).
^^Put some CourierIMAPS on there, if you can.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432947</id>
	<title>Total</title>
	<author>Anonymous</author>
	<datestamp>1245681120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>No total sales overall graph, only moving averages of dsales/dt?</p></htmltext>
<tokenext>No total sales overall graph , only moving averages of dsales/dt ?</tokentext>
<sentencetext>No total sales overall graph, only moving averages of dsales/dt?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436789</id>
	<title>Re:You forgot the most important thing...</title>
	<author>MrCrassic</author>
	<datestamp>1245757500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Add in the fact that <b>there is no decent SSH client for the Blackberry,</b> and that makes your argument even more valid.</htmltext>
<tokenext>Add in the fact that there is no decent SSH client for the Blackberry , and that makes your argument even more valid .</tokentext>
<sentencetext>Add in the fact that there is no decent SSH client for the Blackberry, and that makes your argument even more valid.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434683</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434543</id>
	<title>Re:Thank you</title>
	<author>pasamio</author>
	<datestamp>1245690420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Reminds me of the week when we had all sorts of "issues" with our blackberry server. We had a tech who rebuilt our BES system three times in the week only to find out that after the week long blaming of us it was actually a problem on their end. First they claimed it wouldn't work in a whole heap of situations, claimed we didn't build the server right and then claimed that it wouldn't work properly in a virtual machine. This is after we'd had it running smoothly for a few months. Turns out they had a fault network card on one of their authentication servers that you need to talk to otherwise it locks you out of your device which randomly killed our BES servers. Yes, works great for millions. There are other issues with servers dying around the world and taking blackberry devices with them, the last organisation I was with almost always had one device that was being shipped to the manufacturer - perhaps you haven't had enough devices yourself or always received good batches?</p></htmltext>
<tokenext>Reminds me of the week when we had all sorts of " issues " with our blackberry server .
We had a tech who rebuilt our BES system three times in the week only to find out that after the week long blaming of us it was actually a problem on their end .
First they claimed it would n't work in a whole heap of situations , claimed we did n't build the server right and then claimed that it would n't work properly in a virtual machine .
This is after we 'd had it running smoothly for a few months .
Turns out they had a fault network card on one of their authentication servers that you need to talk to otherwise it locks you out of your device which randomly killed our BES servers .
Yes , works great for millions .
There are other issues with servers dying around the world and taking blackberry devices with them , the last organisation I was with almost always had one device that was being shipped to the manufacturer - perhaps you have n't had enough devices yourself or always received good batches ?</tokentext>
<sentencetext>Reminds me of the week when we had all sorts of "issues" with our blackberry server.
We had a tech who rebuilt our BES system three times in the week only to find out that after the week long blaming of us it was actually a problem on their end.
First they claimed it wouldn't work in a whole heap of situations, claimed we didn't build the server right and then claimed that it wouldn't work properly in a virtual machine.
This is after we'd had it running smoothly for a few months.
Turns out they had a fault network card on one of their authentication servers that you need to talk to otherwise it locks you out of your device which randomly killed our BES servers.
Yes, works great for millions.
There are other issues with servers dying around the world and taking blackberry devices with them, the last organisation I was with almost always had one device that was being shipped to the manufacturer - perhaps you haven't had enough devices yourself or always received good batches?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433103</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436079</id>
	<title>Nice article, but...</title>
	<author>Renderer of Evil</author>
	<datestamp>1245748920000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>0</modscore>
	<htmltext><p>I enjoyed reading the analysis and the breakdown of converted trial users, but I must say, the application looks like shit. The typography is horrendous, the colors are all wrong, and the interface looks like something out of 80's or designed in MS Paint. The tagline on the app site is "Not pretty. Functional." What makes iPhone remarkable is that it demonstrated that you can have both pretty and functional. It's not an either/or proposition anymore. RIM/Nokia/Microsoft no longer have an excuse to say that in order for something to be functional it must conform to the lowest common denominator.</p><p>Contrary to popular opinion, the unwashed masses <strong>do appreciate</strong> well-designed, well-planned, and well-implemented products if it is within their price range. There is a reason why Pontiac Aztec failed in such a spectacular fashion.</p></htmltext>
<tokenext>I enjoyed reading the analysis and the breakdown of converted trial users , but I must say , the application looks like shit .
The typography is horrendous , the colors are all wrong , and the interface looks like something out of 80 's or designed in MS Paint .
The tagline on the app site is " Not pretty .
Functional. " What makes iPhone remarkable is that it demonstrated that you can have both pretty and functional .
It 's not an either/or proposition anymore .
RIM/Nokia/Microsoft no longer have an excuse to say that in order for something to be functional it must conform to the lowest common denominator.Contrary to popular opinion , the unwashed masses do appreciate well-designed , well-planned , and well-implemented products if it is within their price range .
There is a reason why Pontiac Aztec failed in such a spectacular fashion .</tokentext>
<sentencetext>I enjoyed reading the analysis and the breakdown of converted trial users, but I must say, the application looks like shit.
The typography is horrendous, the colors are all wrong, and the interface looks like something out of 80's or designed in MS Paint.
The tagline on the app site is "Not pretty.
Functional." What makes iPhone remarkable is that it demonstrated that you can have both pretty and functional.
It's not an either/or proposition anymore.
RIM/Nokia/Microsoft no longer have an excuse to say that in order for something to be functional it must conform to the lowest common denominator.Contrary to popular opinion, the unwashed masses do appreciate well-designed, well-planned, and well-implemented products if it is within their price range.
There is a reason why Pontiac Aztec failed in such a spectacular fashion.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432605</id>
	<title>So</title>
	<author>oldhack</author>
	<datestamp>1245679500000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext>So yeah, what about it?</htmltext>
<tokenext>So yeah , what about it ?</tokentext>
<sentencetext>So yeah, what about it?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435277</id>
	<title>Re:Sure there are more blackberries</title>
	<author>Anonymous</author>
	<datestamp>1245697320000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>You <i>almost</i> hit the nail on the head.  My company decided to go with iPhone development rather than Blackberry development for the simple reason that our target demographic enjoys iPhones for personal use and only carries Blackberries if their management requires/provides them.  With that kind of a trend, and with users willing to use their personal devices for work, it makes much more sense to go the Apple route.  It didn't really help that RIM's people were aggressive and obnoxious on a conference call with our president, though...</p></htmltext>
<tokenext>You almost hit the nail on the head .
My company decided to go with iPhone development rather than Blackberry development for the simple reason that our target demographic enjoys iPhones for personal use and only carries Blackberries if their management requires/provides them .
With that kind of a trend , and with users willing to use their personal devices for work , it makes much more sense to go the Apple route .
It did n't really help that RIM 's people were aggressive and obnoxious on a conference call with our president , though.. .</tokentext>
<sentencetext>You almost hit the nail on the head.
My company decided to go with iPhone development rather than Blackberry development for the simple reason that our target demographic enjoys iPhones for personal use and only carries Blackberries if their management requires/provides them.
With that kind of a trend, and with users willing to use their personal devices for work, it makes much more sense to go the Apple route.
It didn't really help that RIM's people were aggressive and obnoxious on a conference call with our president, though...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432633</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433023</id>
	<title>Re:Total</title>
	<author>ballwall</author>
	<datestamp>1245681540000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>Whoops, oversight on my part. Total sales stand at 2382 copies as of the data in the article (at an average net of $8.50 per sale I've made just over $20k). Thanks for pointing that out. I'd update the site but I'm afraid to break at the moment.</p></htmltext>
<tokenext>Whoops , oversight on my part .
Total sales stand at 2382 copies as of the data in the article ( at an average net of $ 8.50 per sale I 've made just over $ 20k ) .
Thanks for pointing that out .
I 'd update the site but I 'm afraid to break at the moment .</tokentext>
<sentencetext>Whoops, oversight on my part.
Total sales stand at 2382 copies as of the data in the article (at an average net of $8.50 per sale I've made just over $20k).
Thanks for pointing that out.
I'd update the site but I'm afraid to break at the moment.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432947</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28444527</id>
	<title>Re:Thank you</title>
	<author>Anonymous</author>
	<datestamp>1245748920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>...blackberries (I refuse to capitalize)...</p></div><p>Yay! Finally there is somebody willing to stand up to stupid capitalization schemes and case letters the way they should be!  Stay strong, don't let the marketing drones win!</p><p><div class="quote"><p>...I tell them iPhone...</p></div><p>D'oh!</p></div>
	</htmltext>
<tokenext>...blackberries ( I refuse to capitalize ) ...Yay !
Finally there is somebody willing to stand up to stupid capitalization schemes and case letters the way they should be !
Stay strong , do n't let the marketing drones win ! ...I tell them iPhone...D'oh !</tokentext>
<sentencetext>...blackberries (I refuse to capitalize)...Yay!
Finally there is somebody willing to stand up to stupid capitalization schemes and case letters the way they should be!
Stay strong, don't let the marketing drones win!...I tell them iPhone...D'oh!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28438525</id>
	<title>Location based services are hell on BB</title>
	<author>technopinion</author>
	<datestamp>1245770520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Wait until you try programming a GPS app. Every different telecom has different settings needed to get the GPS to work at all (even when they allow you to use the GPS without having to get special permission, like Verizon). Many of the documented API settings *don't* work, particulary on CDMA blackberries. Some telecoms have disabled BlackBerry Maps because they want you to buy their gps nav application, so you can't count on it being available, or even installable, and even the built-in map objects that you can in theory use inside your apps on OS 4.5 or greater relies on BlackBerry Maps being installed, so you can't rely on that either.</p></htmltext>
<tokenext>Wait until you try programming a GPS app .
Every different telecom has different settings needed to get the GPS to work at all ( even when they allow you to use the GPS without having to get special permission , like Verizon ) .
Many of the documented API settings * do n't * work , particulary on CDMA blackberries .
Some telecoms have disabled BlackBerry Maps because they want you to buy their gps nav application , so you ca n't count on it being available , or even installable , and even the built-in map objects that you can in theory use inside your apps on OS 4.5 or greater relies on BlackBerry Maps being installed , so you ca n't rely on that either .</tokentext>
<sentencetext>Wait until you try programming a GPS app.
Every different telecom has different settings needed to get the GPS to work at all (even when they allow you to use the GPS without having to get special permission, like Verizon).
Many of the documented API settings *don't* work, particulary on CDMA blackberries.
Some telecoms have disabled BlackBerry Maps because they want you to buy their gps nav application, so you can't count on it being available, or even installable, and even the built-in map objects that you can in theory use inside your apps on OS 4.5 or greater relies on BlackBerry Maps being installed, so you can't rely on that either.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435221</id>
	<title>My experiences developing on the BlackBerry.</title>
	<author>rgelb1</author>
	<datestamp>1245696840000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>I actually have a free application on the BlackBerry App World called HP Printer Fun, which lets users mess with the LED screens on the HP Laser Jet printers (plus some inkjet ones too) for fun.</p><p>I've written some other apps as well and the experience is not so great.  My gripes are as follows:</p><ul><li>Java is limited to an ancient version (e.g. no generics or other recent goodness)</li><li>Very weak debugging support (compared to say, Android)</li><li>When the emulator is running, your app is basically locked.  In other words, you have to restart the emulator each time you make a change to the code - which takes 1-3 minutes depending on your config.</li><li>The looks of the IDE make Windows 3.1 seem modern.</li><li>No support for modern programming fonts, for instance Consolas</li></ul><p>On the other hand, the docs are pretty good. The support group at BlackBerry dev site is simple superb.  Examples are plenty and the API just freaking makes a massive amount of sense. And for the adventurous, you could use a beta version (might be released by now) of an Eclipse plugin.</p></htmltext>
<tokenext>I actually have a free application on the BlackBerry App World called HP Printer Fun , which lets users mess with the LED screens on the HP Laser Jet printers ( plus some inkjet ones too ) for fun.I 've written some other apps as well and the experience is not so great .
My gripes are as follows : Java is limited to an ancient version ( e.g .
no generics or other recent goodness ) Very weak debugging support ( compared to say , Android ) When the emulator is running , your app is basically locked .
In other words , you have to restart the emulator each time you make a change to the code - which takes 1-3 minutes depending on your config.The looks of the IDE make Windows 3.1 seem modern.No support for modern programming fonts , for instance ConsolasOn the other hand , the docs are pretty good .
The support group at BlackBerry dev site is simple superb .
Examples are plenty and the API just freaking makes a massive amount of sense .
And for the adventurous , you could use a beta version ( might be released by now ) of an Eclipse plugin .</tokentext>
<sentencetext>I actually have a free application on the BlackBerry App World called HP Printer Fun, which lets users mess with the LED screens on the HP Laser Jet printers (plus some inkjet ones too) for fun.I've written some other apps as well and the experience is not so great.
My gripes are as follows:Java is limited to an ancient version (e.g.
no generics or other recent goodness)Very weak debugging support (compared to say, Android)When the emulator is running, your app is basically locked.
In other words, you have to restart the emulator each time you make a change to the code - which takes 1-3 minutes depending on your config.The looks of the IDE make Windows 3.1 seem modern.No support for modern programming fonts, for instance ConsolasOn the other hand, the docs are pretty good.
The support group at BlackBerry dev site is simple superb.
Examples are plenty and the API just freaking makes a massive amount of sense.
And for the adventurous, you could use a beta version (might be released by now) of an Eclipse plugin.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432931</id>
	<title>Stay away! Far far away!</title>
	<author>blogger11</author>
	<datestamp>1245681060000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext>Well I haven't developed any native blackberry software myself.  I have however worked on many web sites with mobile front ends.  Doing web dev for blackberry devices can be a real pain.  First off, most RIM devices have very small screens and secondly, their browsers are much less polished then their competitor the iPhone's.  If anyone here is willing to take my advice, I suggest that you forget that RIM exists and stick with more modern operating systems such as Google Android and the iPhone's "osx".
<br> <br>

<a href="http://www.sitelist.ca/" title="sitelist.ca" rel="nofollow">SiteList</a> [sitelist.ca] - The Open Web Directory... Add your favorite sites today!</htmltext>
<tokenext>Well I have n't developed any native blackberry software myself .
I have however worked on many web sites with mobile front ends .
Doing web dev for blackberry devices can be a real pain .
First off , most RIM devices have very small screens and secondly , their browsers are much less polished then their competitor the iPhone 's .
If anyone here is willing to take my advice , I suggest that you forget that RIM exists and stick with more modern operating systems such as Google Android and the iPhone 's " osx " .
SiteList [ sitelist.ca ] - The Open Web Directory... Add your favorite sites today !</tokentext>
<sentencetext>Well I haven't developed any native blackberry software myself.
I have however worked on many web sites with mobile front ends.
Doing web dev for blackberry devices can be a real pain.
First off, most RIM devices have very small screens and secondly, their browsers are much less polished then their competitor the iPhone's.
If anyone here is willing to take my advice, I suggest that you forget that RIM exists and stick with more modern operating systems such as Google Android and the iPhone's "osx".
SiteList [sitelist.ca] - The Open Web Directory... Add your favorite sites today!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435033</id>
	<title>Re:Thank you</title>
	<author>wzinc</author>
	<datestamp>1245694740000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>I'm pretty sure iPhones can do all of this... I own one.<br>- remote wipe - through exchange and MobileMe<br>- full data encryption<br>- proxies<br>- security policies, including what apps you can / can't have<br>- even throw-away phones do "logging," as in recent calls - I'm sure there's some way to save that list - worst case-scenario, look at the itemized bill. The iPhone does log time-usage for sure.</p><p>Although: MDS; I don't know what that is...</p><p>Also, the iPhone does not feature:<br>- a Perl trackball or that awful "are you sure?" on every menu option scroll / click wheel on the side<br>- the need for an intermediate push server<br>- a UI that makes WinMo look good</p></htmltext>
<tokenext>I 'm pretty sure iPhones can do all of this... I own one.- remote wipe - through exchange and MobileMe- full data encryption- proxies- security policies , including what apps you can / ca n't have- even throw-away phones do " logging , " as in recent calls - I 'm sure there 's some way to save that list - worst case-scenario , look at the itemized bill .
The iPhone does log time-usage for sure.Although : MDS ; I do n't know what that is...Also , the iPhone does not feature : - a Perl trackball or that awful " are you sure ?
" on every menu option scroll / click wheel on the side- the need for an intermediate push server- a UI that makes WinMo look good</tokentext>
<sentencetext>I'm pretty sure iPhones can do all of this... I own one.- remote wipe - through exchange and MobileMe- full data encryption- proxies- security policies, including what apps you can / can't have- even throw-away phones do "logging," as in recent calls - I'm sure there's some way to save that list - worst case-scenario, look at the itemized bill.
The iPhone does log time-usage for sure.Although: MDS; I don't know what that is...Also, the iPhone does not feature:- a Perl trackball or that awful "are you sure?
" on every menu option scroll / click wheel on the side- the need for an intermediate push server- a UI that makes WinMo look good</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436581</id>
	<title>Re:You forgot the most important thing...</title>
	<author>Anonymous</author>
	<datestamp>1245755160000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The thing to remember is that the prices on the iPhone are artificially low. A developer (I am one) just can't pay the bills on anything but a massive number of $1.99 sales.</p></htmltext>
<tokenext>The thing to remember is that the prices on the iPhone are artificially low .
A developer ( I am one ) just ca n't pay the bills on anything but a massive number of $ 1.99 sales .</tokentext>
<sentencetext>The thing to remember is that the prices on the iPhone are artificially low.
A developer (I am one) just can't pay the bills on anything but a massive number of $1.99 sales.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434683</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911</id>
	<title>Thank you</title>
	<author>Naurgrim</author>
	<datestamp>1245680940000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Interesting read, ballwall, and I truly wish you luck with your efforts.</p><p>I'm not much of a programmer, but as a SysAdmin (*nix by preference, win* by necessity) I was struck by some parallels I've observed. I find blackberries to be painful. Making them work as a mobile email device tied to Exchange requires a shiat-ton of ugly third party software.</p><p>If a client bothers to ask, (and they don't), I tell them iPhone first, WinMobile second, blackberry distant third.</p><p>BES is, IMHO, a steaming pile - java, dot.net, 32-bit only. Feh. Recent iPhones handle active sync nicely and don't bitch about self-signed certs. WinMobile is a bit harder, but install your certs and you're done. blackberries (I refuse to capitalize) give me pain.</p><p>My clients pay $$ for BES CALs, the devices get stupid and need to be factory reset often and re-activated, costing my client more $$ for my time.</p><p>A colleague says "blackberries are great, they help me spot THOSE people". I tend to agree. I honestly cannot see the attraction when there are better solutions to talk to an Exchange server - previously mentioned iPhones, WinMobile or a laptop with RPC over HTTP(S) all work more simply and more reliably, and I tell my clients so. Nevertheless, I still hear "but I've got to have a blackberry"!</p></htmltext>
<tokenext>Interesting read , ballwall , and I truly wish you luck with your efforts.I 'm not much of a programmer , but as a SysAdmin ( * nix by preference , win * by necessity ) I was struck by some parallels I 've observed .
I find blackberries to be painful .
Making them work as a mobile email device tied to Exchange requires a shiat-ton of ugly third party software.If a client bothers to ask , ( and they do n't ) , I tell them iPhone first , WinMobile second , blackberry distant third.BES is , IMHO , a steaming pile - java , dot.net , 32-bit only .
Feh. Recent iPhones handle active sync nicely and do n't bitch about self-signed certs .
WinMobile is a bit harder , but install your certs and you 're done .
blackberries ( I refuse to capitalize ) give me pain.My clients pay $ $ for BES CALs , the devices get stupid and need to be factory reset often and re-activated , costing my client more $ $ for my time.A colleague says " blackberries are great , they help me spot THOSE people " .
I tend to agree .
I honestly can not see the attraction when there are better solutions to talk to an Exchange server - previously mentioned iPhones , WinMobile or a laptop with RPC over HTTP ( S ) all work more simply and more reliably , and I tell my clients so .
Nevertheless , I still hear " but I 've got to have a blackberry " !</tokentext>
<sentencetext>Interesting read, ballwall, and I truly wish you luck with your efforts.I'm not much of a programmer, but as a SysAdmin (*nix by preference, win* by necessity) I was struck by some parallels I've observed.
I find blackberries to be painful.
Making them work as a mobile email device tied to Exchange requires a shiat-ton of ugly third party software.If a client bothers to ask, (and they don't), I tell them iPhone first, WinMobile second, blackberry distant third.BES is, IMHO, a steaming pile - java, dot.net, 32-bit only.
Feh. Recent iPhones handle active sync nicely and don't bitch about self-signed certs.
WinMobile is a bit harder, but install your certs and you're done.
blackberries (I refuse to capitalize) give me pain.My clients pay $$ for BES CALs, the devices get stupid and need to be factory reset often and re-activated, costing my client more $$ for my time.A colleague says "blackberries are great, they help me spot THOSE people".
I tend to agree.
I honestly cannot see the attraction when there are better solutions to talk to an Exchange server - previously mentioned iPhones, WinMobile or a laptop with RPC over HTTP(S) all work more simply and more reliably, and I tell my clients so.
Nevertheless, I still hear "but I've got to have a blackberry"!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28438045</id>
	<title>Yep, BlackBerry development with Java on Eclipse</title>
	<author>Cris Malinescu</author>
	<datestamp>1245768060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Just check here:

<a href="http://na.blackberry.com/eng/developers/javaappdev/javaeclipseplug.jsp" title="blackberry.com" rel="nofollow">http://na.blackberry.com/eng/developers/javaappdev/javaeclipseplug.jsp</a> [blackberry.com]

Free Plug-In for BlackBerry Java Development with Eclipse!

Cheers,
Cris</htmltext>
<tokenext>Just check here : http : //na.blackberry.com/eng/developers/javaappdev/javaeclipseplug.jsp [ blackberry.com ] Free Plug-In for BlackBerry Java Development with Eclipse !
Cheers , Cris</tokentext>
<sentencetext>Just check here:

http://na.blackberry.com/eng/developers/javaappdev/javaeclipseplug.jsp [blackberry.com]

Free Plug-In for BlackBerry Java Development with Eclipse!
Cheers,
Cris</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432933
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432811
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28437963
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28439019
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435033
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434083
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433705
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435397
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28439975
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436305
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435363
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434887
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432633
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436789
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434683
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432873
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436907
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433009
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433593
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432811
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434543
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433103
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435277
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432633
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434047
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433023
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432947
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28438001
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432901
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434761
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436581
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434683
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432873
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433511
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433009
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435019
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28442265
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434437
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432873
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434325
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433009
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435313
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433333
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432873
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28437625
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433023
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432947
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28438763
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436305
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434789
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433103
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433431
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433913
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433327
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28444527
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_22_2328203_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434239
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_22_2328203.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432947
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433023
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28437625
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434047
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_22_2328203.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432911
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433705
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28444527
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435397
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28442265
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433327
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433913
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435341
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434083
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434091
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28439019
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433103
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434543
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434789
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433081
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434761
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435019
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436305
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28438763
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28439975
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435033
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28437963
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433431
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434239
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435313
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_22_2328203.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432811
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432933
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433593
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_22_2328203.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432633
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434887
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435363
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435277
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_22_2328203.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432605
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_22_2328203.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432873
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434683
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436789
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436581
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434437
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433333
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_22_2328203.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433009
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28436907
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28434325
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28433511
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_22_2328203.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28432901
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28438001
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_22_2328203.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_22_2328203.28435221
</commentlist>
</conversation>
