<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_10_25_1126210</id>
	<title>White House Website Switches To Open Source</title>
	<author>Soulskill</author>
	<datestamp>1256477220000</datestamp>
	<htmltext><a href="mailto:japerry.jademicrosystems@com" rel="nofollow">Falc0n</a> writes <i>"<a href="http://techpresident.com/blog-entry/whitehousegov-goes-drupal">WhiteHouse.gov has gone Drupal</a>. After months of planning, says an Obama Administration source, the White House has ditched the proprietary content management system that had been in place since the days of the Bush Administration in favor of the latest version of the open-source Drupal software.  Dries Buytaert reflected on this, adding: 'this is a clear sign that governments <a href="http://buytaert.net/whitehouse-gov-using-drupal">realize that Open Source does not pose additional risks</a> compared to proprietary software, and furthermore, that by moving away from proprietary software, they are not being locked into a particular technology, and that they can benefit from the innovation that is the result of thousands of developers collaborating on Drupal.'"</i></htmltext>
<tokenext>Falc0n writes " WhiteHouse.gov has gone Drupal .
After months of planning , says an Obama Administration source , the White House has ditched the proprietary content management system that had been in place since the days of the Bush Administration in favor of the latest version of the open-source Drupal software .
Dries Buytaert reflected on this , adding : 'this is a clear sign that governments realize that Open Source does not pose additional risks compared to proprietary software , and furthermore , that by moving away from proprietary software , they are not being locked into a particular technology , and that they can benefit from the innovation that is the result of thousands of developers collaborating on Drupal .
' "</tokentext>
<sentencetext>Falc0n writes "WhiteHouse.gov has gone Drupal.
After months of planning, says an Obama Administration source, the White House has ditched the proprietary content management system that had been in place since the days of the Bush Administration in favor of the latest version of the open-source Drupal software.
Dries Buytaert reflected on this, adding: 'this is a clear sign that governments realize that Open Source does not pose additional risks compared to proprietary software, and furthermore, that by moving away from proprietary software, they are not being locked into a particular technology, and that they can benefit from the innovation that is the result of thousands of developers collaborating on Drupal.
'"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864535</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Anonymous</author>
	<datestamp>1256485440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Wait, are you trying to say it might be possible that closed source might be safer than open source in some situation?</htmltext>
<tokenext>Wait , are you trying to say it might be possible that closed source might be safer than open source in some situation ?</tokentext>
<sentencetext>Wait, are you trying to say it might be possible that closed source might be safer than open source in some situation?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864437</id>
	<title>Re:Clearly</title>
	<author>A beautiful mind</author>
	<datestamp>1256484420000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><blockquote><div><p>Huh. Now to me, this is a clear sign that <b>they hired</b> a new web guy who happens to have experience with and a preference for Drupal. I don't think there's a necessarily a <b>political statement</b> here.</p></div></blockquote><p>

The top of the government and especially the president are HR people first and foremost. They don't do much personally, but act through the agents they select, rely on their judgement and trust them to condense issues of importance for them. Sure, they also get to make some decisions, but they decide based on the information fed to them and the decisions are broad, policy decisions in most cases.<br> <br>
The point is, they didn't make a policy decision that "zomg, F/OSS ftw!", but they hired the guy who hired the guy who hired the guy who hired the web guy and the web guy seems competent enough to pick a F/OSS solution.</p></div>
	</htmltext>
<tokenext>Huh .
Now to me , this is a clear sign that they hired a new web guy who happens to have experience with and a preference for Drupal .
I do n't think there 's a necessarily a political statement here .
The top of the government and especially the president are HR people first and foremost .
They do n't do much personally , but act through the agents they select , rely on their judgement and trust them to condense issues of importance for them .
Sure , they also get to make some decisions , but they decide based on the information fed to them and the decisions are broad , policy decisions in most cases .
The point is , they did n't make a policy decision that " zomg , F/OSS ftw !
" , but they hired the guy who hired the guy who hired the guy who hired the web guy and the web guy seems competent enough to pick a F/OSS solution .</tokentext>
<sentencetext>Huh.
Now to me, this is a clear sign that they hired a new web guy who happens to have experience with and a preference for Drupal.
I don't think there's a necessarily a political statement here.
The top of the government and especially the president are HR people first and foremost.
They don't do much personally, but act through the agents they select, rely on their judgement and trust them to condense issues of importance for them.
Sure, they also get to make some decisions, but they decide based on the information fed to them and the decisions are broad, policy decisions in most cases.
The point is, they didn't make a policy decision that "zomg, F/OSS ftw!
", but they hired the guy who hired the guy who hired the guy who hired the web guy and the web guy seems competent enough to pick a F/OSS solution.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864275</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864315</id>
	<title>Re:Great...</title>
	<author>aldld</author>
	<datestamp>1256483280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Hey, at least it's open source, so it must be a good thing!</htmltext>
<tokenext>Hey , at least it 's open source , so it must be a good thing !</tokentext>
<sentencetext>Hey, at least it's open source, so it must be a good thing!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864133</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864473</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>pjr.cc</author>
	<datestamp>1256484840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>well, drupal (so far) has been quite good at patching its own problems...</p><p>Modules on the other hand are a different beast (and in some ways the can be a pain with drupal) - some are coded by drupal them selves, some are not so your miliage can vary.</p><p>But this is where open source can actually benifit, cause if you do have access to coders (im sure the whitehouse does right?) you can fix it yourself (or at least get a work-around going for a short time).</p></htmltext>
<tokenext>well , drupal ( so far ) has been quite good at patching its own problems...Modules on the other hand are a different beast ( and in some ways the can be a pain with drupal ) - some are coded by drupal them selves , some are not so your miliage can vary.But this is where open source can actually benifit , cause if you do have access to coders ( im sure the whitehouse does right ?
) you can fix it yourself ( or at least get a work-around going for a short time ) .</tokentext>
<sentencetext>well, drupal (so far) has been quite good at patching its own problems...Modules on the other hand are a different beast (and in some ways the can be a pain with drupal) - some are coded by drupal them selves, some are not so your miliage can vary.But this is where open source can actually benifit, cause if you do have access to coders (im sure the whitehouse does right?
) you can fix it yourself (or at least get a work-around going for a short time).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29874979</id>
	<title>Re:Why CMS</title>
	<author>Anonymous</author>
	<datestamp>1256584080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Let me relate a recent situation that happened to me.  I was asked to come in and look at a proof-of-concept website that someone was designing for a customer.  It was a reasonably impressive website that he showed us.  He told us this POC took him about 100 hours to implement.  The customer asked how long it would take to add certain features, particularly the ability for his staff to create pages on the fly without having to download files, modify them, and FTP them into place, and was told several hundred more hours.</p><p>I suggested the site could be created using an existing CMS in significantly less time and with all the functionality they were looking for.  I was asked to develop a POC as well using Drupal.  I returned 48 hours later with a site that had everything the customer wanted, including the ability to easily add an ecommerce store at a later date.</p><p>Who do you think has the contract now to build the site?  Let me give you a hint... it isn't the guy who put 100 hours in.</p></htmltext>
<tokenext>Let me relate a recent situation that happened to me .
I was asked to come in and look at a proof-of-concept website that someone was designing for a customer .
It was a reasonably impressive website that he showed us .
He told us this POC took him about 100 hours to implement .
The customer asked how long it would take to add certain features , particularly the ability for his staff to create pages on the fly without having to download files , modify them , and FTP them into place , and was told several hundred more hours.I suggested the site could be created using an existing CMS in significantly less time and with all the functionality they were looking for .
I was asked to develop a POC as well using Drupal .
I returned 48 hours later with a site that had everything the customer wanted , including the ability to easily add an ecommerce store at a later date.Who do you think has the contract now to build the site ?
Let me give you a hint... it is n't the guy who put 100 hours in .</tokentext>
<sentencetext>Let me relate a recent situation that happened to me.
I was asked to come in and look at a proof-of-concept website that someone was designing for a customer.
It was a reasonably impressive website that he showed us.
He told us this POC took him about 100 hours to implement.
The customer asked how long it would take to add certain features, particularly the ability for his staff to create pages on the fly without having to download files, modify them, and FTP them into place, and was told several hundred more hours.I suggested the site could be created using an existing CMS in significantly less time and with all the functionality they were looking for.
I was asked to develop a POC as well using Drupal.
I returned 48 hours later with a site that had everything the customer wanted, including the ability to easily add an ecommerce store at a later date.Who do you think has the contract now to build the site?
Let me give you a hint... it isn't the guy who put 100 hours in.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866431</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>blakhol</author>
	<datestamp>1256501640000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>Security is most certainly not an afterthought for Drupal.</p><p>Up though version 6 you needed to turn on a module like Securepages module to enable SSL logins.</p><p>The upcoming Drupal 7 has SSL login support in core.</p><p>See <a href="http://crackingdrupal.com/blog/greggles/drupal-and-ssl-multiple-recipes-possible-solutions" title="crackingdrupal.com" rel="nofollow">http://crackingdrupal.com/blog/greggles/drupal-and-ssl-multiple-recipes-possible-solutions</a> [crackingdrupal.com]</p></htmltext>
<tokenext>Security is most certainly not an afterthought for Drupal.Up though version 6 you needed to turn on a module like Securepages module to enable SSL logins.The upcoming Drupal 7 has SSL login support in core.See http : //crackingdrupal.com/blog/greggles/drupal-and-ssl-multiple-recipes-possible-solutions [ crackingdrupal.com ]</tokentext>
<sentencetext>Security is most certainly not an afterthought for Drupal.Up though version 6 you needed to turn on a module like Securepages module to enable SSL logins.The upcoming Drupal 7 has SSL login support in core.See http://crackingdrupal.com/blog/greggles/drupal-and-ssl-multiple-recipes-possible-solutions [crackingdrupal.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864447</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29870759</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Angostura</author>
	<datestamp>1256559720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I was pretty disturbed when I looked at the new features in version 7 to find that it would salt password files for the first time. The fact that version 6 does not use salt didn't give me a particularly warm and fuzzy feeling regarding security.</p></htmltext>
<tokenext>I was pretty disturbed when I looked at the new features in version 7 to find that it would salt password files for the first time .
The fact that version 6 does not use salt did n't give me a particularly warm and fuzzy feeling regarding security .</tokentext>
<sentencetext>I was pretty disturbed when I looked at the new features in version 7 to find that it would salt password files for the first time.
The fact that version 6 does not use salt didn't give me a particularly warm and fuzzy feeling regarding security.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866431</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29870185</id>
	<title>You have got to be kidding</title>
	<author>holophrastic</author>
	<datestamp>1256550960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>So, let me get this straight.  They've decided to go for open source so that they aren't locked in to a proprietary solution provider.  Just to be clear:  you live in a country that has no problem over-throwing their own government every 4 years, and in fact insists that it happen every 8 years, but refuses to rebuild their web-site ever again?</p><p>How about this.  How about every 4 years, when there's a new president, who proceeds to fire everybody, bring in his entire team, and spend six months appointing all sorts of other positions from scratch, how about he then, and only then, rebuilds the web-site -- you know, with new technologies and new ideas -- instead of leaving the 8-year-old web-site from the last administration to sit and grow dust.</p><p>There are great reasons to benefit from an open source web-site.  But I guarantee the following super ideas won't actually be put forward by anyone but me:<br>
&nbsp; &nbsp; &nbsp; -  academic (school) assignments to improve a page of the country's web-site<br>
&nbsp; &nbsp; &nbsp; -  national challenges to build interesting and useful public features<br>
&nbsp; &nbsp; &nbsp; -  the olympics, for web developers -- you know, a task that actually has some value, unlike figure skating.  Really, I think we've pushed ice-skate technology far enough.  Even NASA can't find enough ice.<br>
&nbsp; &nbsp; &nbsp; -  every government employee to build 1 web page<br>
&nbsp; &nbsp; &nbsp; -  in order to apply for a government position, you must improve an existing web-page<br>
&nbsp; &nbsp; &nbsp; -  national web-page development day! everybody program.<br>
&nbsp; &nbsp; &nbsp; -  $100 of your annual income tax if you build a web page</p><p>But, in the end, you know as well as I do:<br>
&nbsp; &nbsp; &nbsp; -  fewer than 15 people will ever touch a single line of code for this thing<br>
&nbsp; &nbsp; &nbsp; -  fewer than 50 people will ever generate any content for this thing -- CMS or not<br>
&nbsp; &nbsp; &nbsp; -  it won't last 8 years<br>
&nbsp; &nbsp; &nbsp; -  it won't last 4 years<br>
&nbsp; &nbsp; &nbsp; -  it won't launch on-time<br>
&nbsp; &nbsp; &nbsp; -  it won't launch complete<br>
&nbsp; &nbsp; &nbsp; -  it won't ever reach initial completion<br>
&nbsp; &nbsp; &nbsp; -  it'll suck. (that's a period my friends)<br>
&nbsp; &nbsp; &nbsp; -  it won't help anyone with anything<br>
&nbsp; &nbsp; &nbsp; -  it'll be marginally better than a computerized telephone answering machine<br>
&nbsp; &nbsp; &nbsp; -  it'll be a waste of a lot of time<br>
&nbsp; &nbsp; &nbsp; -  somehow it'll manage to cost tax payers way too much money<br>
&nbsp; &nbsp; &nbsp; -  it won't create jobs.  it won't save jobs.  it won't improve the economy.  it won't feed people.  it won't save the auto industry.  it won't save the oil industry.<br>
&nbsp; &nbsp; &nbsp; -  it won't solve a single current actual problem</p><p>Amazing how much easier it was to write that second list as compared to the first.</p></htmltext>
<tokenext>So , let me get this straight .
They 've decided to go for open source so that they are n't locked in to a proprietary solution provider .
Just to be clear : you live in a country that has no problem over-throwing their own government every 4 years , and in fact insists that it happen every 8 years , but refuses to rebuild their web-site ever again ? How about this .
How about every 4 years , when there 's a new president , who proceeds to fire everybody , bring in his entire team , and spend six months appointing all sorts of other positions from scratch , how about he then , and only then , rebuilds the web-site -- you know , with new technologies and new ideas -- instead of leaving the 8-year-old web-site from the last administration to sit and grow dust.There are great reasons to benefit from an open source web-site .
But I guarantee the following super ideas wo n't actually be put forward by anyone but me :       - academic ( school ) assignments to improve a page of the country 's web-site       - national challenges to build interesting and useful public features       - the olympics , for web developers -- you know , a task that actually has some value , unlike figure skating .
Really , I think we 've pushed ice-skate technology far enough .
Even NASA ca n't find enough ice .
      - every government employee to build 1 web page       - in order to apply for a government position , you must improve an existing web-page       - national web-page development day !
everybody program .
      - $ 100 of your annual income tax if you build a web pageBut , in the end , you know as well as I do :       - fewer than 15 people will ever touch a single line of code for this thing       - fewer than 50 people will ever generate any content for this thing -- CMS or not       - it wo n't last 8 years       - it wo n't last 4 years       - it wo n't launch on-time       - it wo n't launch complete       - it wo n't ever reach initial completion       - it 'll suck .
( that 's a period my friends )       - it wo n't help anyone with anything       - it 'll be marginally better than a computerized telephone answering machine       - it 'll be a waste of a lot of time       - somehow it 'll manage to cost tax payers way too much money       - it wo n't create jobs .
it wo n't save jobs .
it wo n't improve the economy .
it wo n't feed people .
it wo n't save the auto industry .
it wo n't save the oil industry .
      - it wo n't solve a single current actual problemAmazing how much easier it was to write that second list as compared to the first .</tokentext>
<sentencetext>So, let me get this straight.
They've decided to go for open source so that they aren't locked in to a proprietary solution provider.
Just to be clear:  you live in a country that has no problem over-throwing their own government every 4 years, and in fact insists that it happen every 8 years, but refuses to rebuild their web-site ever again?How about this.
How about every 4 years, when there's a new president, who proceeds to fire everybody, bring in his entire team, and spend six months appointing all sorts of other positions from scratch, how about he then, and only then, rebuilds the web-site -- you know, with new technologies and new ideas -- instead of leaving the 8-year-old web-site from the last administration to sit and grow dust.There are great reasons to benefit from an open source web-site.
But I guarantee the following super ideas won't actually be put forward by anyone but me:
      -  academic (school) assignments to improve a page of the country's web-site
      -  national challenges to build interesting and useful public features
      -  the olympics, for web developers -- you know, a task that actually has some value, unlike figure skating.
Really, I think we've pushed ice-skate technology far enough.
Even NASA can't find enough ice.
      -  every government employee to build 1 web page
      -  in order to apply for a government position, you must improve an existing web-page
      -  national web-page development day!
everybody program.
      -  $100 of your annual income tax if you build a web pageBut, in the end, you know as well as I do:
      -  fewer than 15 people will ever touch a single line of code for this thing
      -  fewer than 50 people will ever generate any content for this thing -- CMS or not
      -  it won't last 8 years
      -  it won't last 4 years
      -  it won't launch on-time
      -  it won't launch complete
      -  it won't ever reach initial completion
      -  it'll suck.
(that's a period my friends)
      -  it won't help anyone with anything
      -  it'll be marginally better than a computerized telephone answering machine
      -  it'll be a waste of a lot of time
      -  somehow it'll manage to cost tax payers way too much money
      -  it won't create jobs.
it won't save jobs.
it won't improve the economy.
it won't feed people.
it won't save the auto industry.
it won't save the oil industry.
      -  it won't solve a single current actual problemAmazing how much easier it was to write that second list as compared to the first.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29869351</id>
	<title>Uh... No It's not...</title>
	<author>Anonymous</author>
	<datestamp>1256496360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>"Dries Buytaert reflected on this, adding: 'this is a clear sign that governments realize that Open Source does not pose additional risks compared to proprietary software"</p><p>Uh... Not it's not. It's not like there is classified data on the whitehouse.gov CMS. What's the worst that's going to happen? Some right wing nut hacker like Eric Raymond is going to have in and replace Obama's picture with one of Joseph Stalin?</p></htmltext>
<tokenext>" Dries Buytaert reflected on this , adding : 'this is a clear sign that governments realize that Open Source does not pose additional risks compared to proprietary software " Uh... Not it 's not .
It 's not like there is classified data on the whitehouse.gov CMS .
What 's the worst that 's going to happen ?
Some right wing nut hacker like Eric Raymond is going to have in and replace Obama 's picture with one of Joseph Stalin ?</tokentext>
<sentencetext>"Dries Buytaert reflected on this, adding: 'this is a clear sign that governments realize that Open Source does not pose additional risks compared to proprietary software"Uh... Not it's not.
It's not like there is classified data on the whitehouse.gov CMS.
What's the worst that's going to happen?
Some right wing nut hacker like Eric Raymond is going to have in and replace Obama's picture with one of Joseph Stalin?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864621</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>yelvington</author>
	<datestamp>1256486520000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>If your security beliefs are based on Googling " exploit" I hope you're not in charge of anything important.</p></htmltext>
<tokenext>If your security beliefs are based on Googling " exploit " I hope you 're not in charge of anything important .</tokentext>
<sentencetext>If your security beliefs are based on Googling " exploit" I hope you're not in charge of anything important.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864297</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864275</id>
	<title>Clearly</title>
	<author>Anonymous</author>
	<datestamp>1256482800000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p> this is a clear sign that governments realize that Open Source does not pose additional risks compared to proprietary software</p></div></blockquote><p>Huh. Now to me, this is a clear sign that they hired a new web guy who happens to have experience with and a preference for Drupal. I don't think there's a necessarily a political statement here.</p></div>
	</htmltext>
<tokenext>this is a clear sign that governments realize that Open Source does not pose additional risks compared to proprietary softwareHuh .
Now to me , this is a clear sign that they hired a new web guy who happens to have experience with and a preference for Drupal .
I do n't think there 's a necessarily a political statement here .</tokentext>
<sentencetext> this is a clear sign that governments realize that Open Source does not pose additional risks compared to proprietary softwareHuh.
Now to me, this is a clear sign that they hired a new web guy who happens to have experience with and a preference for Drupal.
I don't think there's a necessarily a political statement here.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</id>
	<title>High profile target and popular CMS'</title>
	<author>abigsmurf</author>
	<datestamp>1256481840000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>The problem with using Drupal for the White House is that it's a popular CMS and has lots of people looking for exploits and vulnerabilities. The second a proof of concept piece of code or an easy exploit is discovered, a few thousand script kiddies will decend to get their 15 minutes of fame.
<br> <br>
I'm not sure how Drupal fares with bugs and patching speed (I know Wordpress seems to get some high profile holes discovered) but even if all vulns are patched before someone takes advantage of it, you're still going to need an admin who's going to be constantly alert to patching it.
<br> <br>
I'm not arguing against closed source vs open, more about popular vs obscure.</htmltext>
<tokenext>The problem with using Drupal for the White House is that it 's a popular CMS and has lots of people looking for exploits and vulnerabilities .
The second a proof of concept piece of code or an easy exploit is discovered , a few thousand script kiddies will decend to get their 15 minutes of fame .
I 'm not sure how Drupal fares with bugs and patching speed ( I know Wordpress seems to get some high profile holes discovered ) but even if all vulns are patched before someone takes advantage of it , you 're still going to need an admin who 's going to be constantly alert to patching it .
I 'm not arguing against closed source vs open , more about popular vs obscure .</tokentext>
<sentencetext>The problem with using Drupal for the White House is that it's a popular CMS and has lots of people looking for exploits and vulnerabilities.
The second a proof of concept piece of code or an easy exploit is discovered, a few thousand script kiddies will decend to get their 15 minutes of fame.
I'm not sure how Drupal fares with bugs and patching speed (I know Wordpress seems to get some high profile holes discovered) but even if all vulns are patched before someone takes advantage of it, you're still going to need an admin who's going to be constantly alert to patching it.
I'm not arguing against closed source vs open, more about popular vs obscure.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864207</id>
	<title>Something fishy.</title>
	<author>Anonymous</author>
	<datestamp>1256482260000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>Ok, Netcraft's history seems to be screwed up, but I can tell you this:</p><p>Right after BO was inagurated, I checked the site. It had just switched over from Bush's site to BO's. Netcraft reported that Bush's site had been Apache on Linux, and BO's new site was IIS on MS.</p></htmltext>
<tokenext>Ok , Netcraft 's history seems to be screwed up , but I can tell you this : Right after BO was inagurated , I checked the site .
It had just switched over from Bush 's site to BO 's .
Netcraft reported that Bush 's site had been Apache on Linux , and BO 's new site was IIS on MS .</tokentext>
<sentencetext>Ok, Netcraft's history seems to be screwed up, but I can tell you this:Right after BO was inagurated, I checked the site.
It had just switched over from Bush's site to BO's.
Netcraft reported that Bush's site had been Apache on Linux, and BO's new site was IIS on MS.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868673</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>lamapper</author>
	<datestamp>1256485380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>This is the real downside to using open source code in government applications --</p> </div><p>The reality is something quite the opposite and very different.  Any flaw in open source can be found in proprietary software.  There are many flaws in proprietary software that are NOT found in open source software.

</p><p>I find that most open source exploits, not all of them, require the cracker to have ID/Password access and/or local (behind the firewall) access.  Not much of an exploit if you do not have secure ID/Passwords.  And if the exploit requires local access to the machine and/or network...that is a non issue for almost everyone. With the White house and/or its data center, good luck with getting local access....

</p><p>Open source is an excellent choice for all government applications.  I appreciate when less of my tax dollars go towards software and hardware thanks to a lower Total Cost of Ownership (TCO) for open source and FOSS software.

</p><p>Please stop spreading FUD.</p></div>
	</htmltext>
<tokenext>This is the real downside to using open source code in government applications -- The reality is something quite the opposite and very different .
Any flaw in open source can be found in proprietary software .
There are many flaws in proprietary software that are NOT found in open source software .
I find that most open source exploits , not all of them , require the cracker to have ID/Password access and/or local ( behind the firewall ) access .
Not much of an exploit if you do not have secure ID/Passwords .
And if the exploit requires local access to the machine and/or network...that is a non issue for almost everyone .
With the White house and/or its data center , good luck with getting local access... . Open source is an excellent choice for all government applications .
I appreciate when less of my tax dollars go towards software and hardware thanks to a lower Total Cost of Ownership ( TCO ) for open source and FOSS software .
Please stop spreading FUD .</tokentext>
<sentencetext>This is the real downside to using open source code in government applications -- The reality is something quite the opposite and very different.
Any flaw in open source can be found in proprietary software.
There are many flaws in proprietary software that are NOT found in open source software.
I find that most open source exploits, not all of them, require the cracker to have ID/Password access and/or local (behind the firewall) access.
Not much of an exploit if you do not have secure ID/Passwords.
And if the exploit requires local access to the machine and/or network...that is a non issue for almost everyone.
With the White house and/or its data center, good luck with getting local access....

Open source is an excellent choice for all government applications.
I appreciate when less of my tax dollars go towards software and hardware thanks to a lower Total Cost of Ownership (TCO) for open source and FOSS software.
Please stop spreading FUD.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866967</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864089</id>
	<title>Re:Why CMS</title>
	<author>chapstercni</author>
	<datestamp>1256481300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>No reinventing of the wheel.<br>All kinds of stuff that can be used as is, or modified.<br>Features, features, features.<br>Easy separation of presentation / Data.<br>Workflow.</p></htmltext>
<tokenext>No reinventing of the wheel.All kinds of stuff that can be used as is , or modified.Features , features , features.Easy separation of presentation / Data.Workflow .</tokentext>
<sentencetext>No reinventing of the wheel.All kinds of stuff that can be used as is, or modified.Features, features, features.Easy separation of presentation / Data.Workflow.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864639</id>
	<title>Re:Socialist Software</title>
	<author>rvw</author>
	<datestamp>1256486700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>My first reaction to seeing this article was how long it will take for Fox News and friends to declare open source software as socialist and how comrade Obama has taken jobs away from hard working capitalist programmers.  It's really not a stretch given their track record.</p></div><p>Take a look at the drupal logo. I think this calls for a big investigation to confirm that Obama is an alien!</p></div>
	</htmltext>
<tokenext>My first reaction to seeing this article was how long it will take for Fox News and friends to declare open source software as socialist and how comrade Obama has taken jobs away from hard working capitalist programmers .
It 's really not a stretch given their track record.Take a look at the drupal logo .
I think this calls for a big investigation to confirm that Obama is an alien !</tokentext>
<sentencetext>My first reaction to seeing this article was how long it will take for Fox News and friends to declare open source software as socialist and how comrade Obama has taken jobs away from hard working capitalist programmers.
It's really not a stretch given their track record.Take a look at the drupal logo.
I think this calls for a big investigation to confirm that Obama is an alien!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866023</id>
	<title>okay, so you guys don't like Drupal's security...</title>
	<author>Tumbleweed</author>
	<datestamp>1256498700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Do any of you have a recommendation on what to use instead? Preferably PHP-based, so it has a realistic shot of being supported on most hosting plans?</p></htmltext>
<tokenext>Do any of you have a recommendation on what to use instead ?
Preferably PHP-based , so it has a realistic shot of being supported on most hosting plans ?</tokentext>
<sentencetext>Do any of you have a recommendation on what to use instead?
Preferably PHP-based, so it has a realistic shot of being supported on most hosting plans?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866931</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>will\_die</author>
	<datestamp>1256463000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Provided they are following standard government security procedures for such sites it will not matter if they are broken into since the only info the server are items that have been approved for release to the public.</htmltext>
<tokenext>Provided they are following standard government security procedures for such sites it will not matter if they are broken into since the only info the server are items that have been approved for release to the public .</tokentext>
<sentencetext>Provided they are following standard government security procedures for such sites it will not matter if they are broken into since the only info the server are items that have been approved for release to the public.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864359</id>
	<title>Just wondering...</title>
	<author>aldld</author>
	<datestamp>1256483580000</datestamp>
	<modclass>None</modclass>
	<modscore>2</modscore>
	<htmltext>Just out of curiosity, what were they using before?</htmltext>
<tokenext>Just out of curiosity , what were they using before ?</tokentext>
<sentencetext>Just out of curiosity, what were they using before?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864149</id>
	<title>Re:Why CMS</title>
	<author>Mathiasdm</author>
	<datestamp>1256481840000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>For one, the weight a CMS adds is compensated by all of the code that is already present, all of the plugins that can be added without any trouble, the possibility for non-coders to easily modify website content<nobr> <wbr></nobr>...
<br>
Especially for large websites, this can dramatically improve how fast you can update and improve your site.
<br>
Also, if you don't want to use a CMS, a framework like Django or Ruby on Rails is the way to go. These allow you to program everything yourself, but already have a lot of functionality built-in, to avoid reinventing the wheel.</htmltext>
<tokenext>For one , the weight a CMS adds is compensated by all of the code that is already present , all of the plugins that can be added without any trouble , the possibility for non-coders to easily modify website content .. . Especially for large websites , this can dramatically improve how fast you can update and improve your site .
Also , if you do n't want to use a CMS , a framework like Django or Ruby on Rails is the way to go .
These allow you to program everything yourself , but already have a lot of functionality built-in , to avoid reinventing the wheel .</tokentext>
<sentencetext>For one, the weight a CMS adds is compensated by all of the code that is already present, all of the plugins that can be added without any trouble, the possibility for non-coders to easily modify website content ...

Especially for large websites, this can dramatically improve how fast you can update and improve your site.
Also, if you don't want to use a CMS, a framework like Django or Ruby on Rails is the way to go.
These allow you to program everything yourself, but already have a lot of functionality built-in, to avoid reinventing the wheel.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29872439</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Proteus Child</author>
	<datestamp>1256571960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>That's great!
<br>
So, what would YOU recommend that they use?  What CMSes have you personally audited, deployed, and helped fix?  You're the expert, help us out here!</htmltext>
<tokenext>That 's great !
So , what would YOU recommend that they use ?
What CMSes have you personally audited , deployed , and helped fix ?
You 're the expert , help us out here !</tokentext>
<sentencetext>That's great!
So, what would YOU recommend that they use?
What CMSes have you personally audited, deployed, and helped fix?
You're the expert, help us out here!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29867655</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864215</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Anonymous</author>
	<datestamp>1256482320000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>You could just as easily turn that argument around and say that <strong>because</strong> it's a popular CMS and has a lot of people looking through it's code for exploits, it's also a lot more secure than some other more obscure CMS which would have much less reviewed code.</p></htmltext>
<tokenext>You could just as easily turn that argument around and say that because it 's a popular CMS and has a lot of people looking through it 's code for exploits , it 's also a lot more secure than some other more obscure CMS which would have much less reviewed code .</tokentext>
<sentencetext>You could just as easily turn that argument around and say that because it's a popular CMS and has a lot of people looking through it's code for exploits, it's also a lot more secure than some other more obscure CMS which would have much less reviewed code.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864297</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Anonymous</author>
	<datestamp>1256483100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Drupal really has not been known for its security in the past; try Googling "drupal exploit", and I'm sure most webmasters are familiar with the "morfeus fucking scanner" user-agent that appears in logs from time to time checking for (among other things) active Drupal-related links (admin pages etc) to exploit.<br> <br>

Maybe is has improved since the last time I paid any attention to it, I assume is would have been given an audit before being deployed on a Government website? That would be great for open source; "Open Source Software hacked, Govt website replaced with Goatse, Microsoft says 'I told you so'"<nobr> <wbr></nobr>... It would be a media-fueled nightmare of FOSS if this goes wrong.</htmltext>
<tokenext>Drupal really has not been known for its security in the past ; try Googling " drupal exploit " , and I 'm sure most webmasters are familiar with the " morfeus fucking scanner " user-agent that appears in logs from time to time checking for ( among other things ) active Drupal-related links ( admin pages etc ) to exploit .
Maybe is has improved since the last time I paid any attention to it , I assume is would have been given an audit before being deployed on a Government website ?
That would be great for open source ; " Open Source Software hacked , Govt website replaced with Goatse , Microsoft says 'I told you so ' " ... It would be a media-fueled nightmare of FOSS if this goes wrong .</tokentext>
<sentencetext>Drupal really has not been known for its security in the past; try Googling "drupal exploit", and I'm sure most webmasters are familiar with the "morfeus fucking scanner" user-agent that appears in logs from time to time checking for (among other things) active Drupal-related links (admin pages etc) to exploit.
Maybe is has improved since the last time I paid any attention to it, I assume is would have been given an audit before being deployed on a Government website?
That would be great for open source; "Open Source Software hacked, Govt website replaced with Goatse, Microsoft says 'I told you so'" ... It would be a media-fueled nightmare of FOSS if this goes wrong.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29876489</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>lfaraone</author>
	<datestamp>1256548080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>The problem with using Drupal for the White House is that it's a popular CMS and has lots of people looking for exploits and vulnerabilities. The second a proof of concept piece of code or an easy exploit is discovered, a few thousand script kiddies will decend to get their 15 minutes of fame.



I'm not sure how Drupal fares with bugs and patching speed (I know Wordpress seems to get some high profile holes discovered) but even if all vulns are patched before someone takes advantage of it, you're still going to need an admin who's going to be constantly alert to patching it.



I'm not arguing against closed source vs open, more about popular vs obscure.</p></div><p>They're the federal government. Anything they do won't be obscure.</p></div>
	</htmltext>
<tokenext>The problem with using Drupal for the White House is that it 's a popular CMS and has lots of people looking for exploits and vulnerabilities .
The second a proof of concept piece of code or an easy exploit is discovered , a few thousand script kiddies will decend to get their 15 minutes of fame .
I 'm not sure how Drupal fares with bugs and patching speed ( I know Wordpress seems to get some high profile holes discovered ) but even if all vulns are patched before someone takes advantage of it , you 're still going to need an admin who 's going to be constantly alert to patching it .
I 'm not arguing against closed source vs open , more about popular vs obscure.They 're the federal government .
Anything they do wo n't be obscure .</tokentext>
<sentencetext>The problem with using Drupal for the White House is that it's a popular CMS and has lots of people looking for exploits and vulnerabilities.
The second a proof of concept piece of code or an easy exploit is discovered, a few thousand script kiddies will decend to get their 15 minutes of fame.
I'm not sure how Drupal fares with bugs and patching speed (I know Wordpress seems to get some high profile holes discovered) but even if all vulns are patched before someone takes advantage of it, you're still going to need an admin who's going to be constantly alert to patching it.
I'm not arguing against closed source vs open, more about popular vs obscure.They're the federal government.
Anything they do won't be obscure.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29869525</id>
	<title>yeah!</title>
	<author>JumpSocial</author>
	<datestamp>1256498460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This will harden Drupal.

Worth while.</htmltext>
<tokenext>This will harden Drupal .
Worth while .</tokentext>
<sentencetext>This will harden Drupal.
Worth while.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868767</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Anonymous</author>
	<datestamp>1256486760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>SSL logins would be trivial to add as a default.  i would guess that they go non-SSL by default to get more low-end shared hosts to support it, thus improving its popularity.</p></htmltext>
<tokenext>SSL logins would be trivial to add as a default .
i would guess that they go non-SSL by default to get more low-end shared hosts to support it , thus improving its popularity .</tokentext>
<sentencetext>SSL logins would be trivial to add as a default.
i would guess that they go non-SSL by default to get more low-end shared hosts to support it, thus improving its popularity.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864447</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868911</id>
	<title>Drupal is dire</title>
	<author>Anonymous</author>
	<datestamp>1256489220000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>One of the worse I have ever had the misfortune to come across, and I have been forced to work with drupal in a few jobs.

Granted is has a fantastic plug in system, it easily extendible, and has great scalability features.

Read: crap, very crap, granny's blog.</htmltext>
<tokenext>One of the worse I have ever had the misfortune to come across , and I have been forced to work with drupal in a few jobs .
Granted is has a fantastic plug in system , it easily extendible , and has great scalability features .
Read : crap , very crap , granny 's blog .</tokentext>
<sentencetext>One of the worse I have ever had the misfortune to come across, and I have been forced to work with drupal in a few jobs.
Granted is has a fantastic plug in system, it easily extendible, and has great scalability features.
Read: crap, very crap, granny's blog.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864345</id>
	<title>Re:Cool</title>
	<author>east coast</author>
	<datestamp>1256483460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>What do you mean "buy us off"? Do you honestly think this is going to get them any real favor? People around here have a way of overestimating the value of open source to the man on the streets or even the geek on the streets for that matter.</htmltext>
<tokenext>What do you mean " buy us off " ?
Do you honestly think this is going to get them any real favor ?
People around here have a way of overestimating the value of open source to the man on the streets or even the geek on the streets for that matter .</tokentext>
<sentencetext>What do you mean "buy us off"?
Do you honestly think this is going to get them any real favor?
People around here have a way of overestimating the value of open source to the man on the streets or even the geek on the streets for that matter.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864259</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864667</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>John Hasler</author>
	<datestamp>1256486940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>&gt; I'm not arguing against closed source vs open, more about popular vs obscure.</p><p>Whatever they use is going to be a high-profile target just because they are using it.  Security by obscurity doesn't work for such sites.</p></htmltext>
<tokenext>&gt; I 'm not arguing against closed source vs open , more about popular vs obscure.Whatever they use is going to be a high-profile target just because they are using it .
Security by obscurity does n't work for such sites .</tokentext>
<sentencetext>&gt; I'm not arguing against closed source vs open, more about popular vs obscure.Whatever they use is going to be a high-profile target just because they are using it.
Security by obscurity doesn't work for such sites.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865103</id>
	<title>Re:Cool</title>
	<author>Loadmaster</author>
	<datestamp>1256491320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Giving praise does not mean you're no longer critical of the government. Governments are like dogs, give praise when they do little things right so they will do bigger things right. Correct them when they do things wrong so they will do them right. This is a small step that could lead to more open source in government, why not tell them you like it and ask for more?</p><p>This is a good first step, but I doubt any of us have forgotten/forgiven who is 2 and 3 and the DoJ.</p></htmltext>
<tokenext>Giving praise does not mean you 're no longer critical of the government .
Governments are like dogs , give praise when they do little things right so they will do bigger things right .
Correct them when they do things wrong so they will do them right .
This is a small step that could lead to more open source in government , why not tell them you like it and ask for more ? This is a good first step , but I doubt any of us have forgotten/forgiven who is 2 and 3 and the DoJ .</tokentext>
<sentencetext>Giving praise does not mean you're no longer critical of the government.
Governments are like dogs, give praise when they do little things right so they will do bigger things right.
Correct them when they do things wrong so they will do them right.
This is a small step that could lead to more open source in government, why not tell them you like it and ask for more?This is a good first step, but I doubt any of us have forgotten/forgiven who is 2 and 3 and the DoJ.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864259</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864447</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>kamelkev</author>
	<datestamp>1256484480000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>I run a fairly high profile drupal site - and this has always been a large concern for us.</p><p>Our solution was basically to disable user logins completely. An overwhelming number of the exploits require you to login, so by removing this prerequisite, we basically avoided the problem.</p><p>Security isn't exactly a priority for drupal either, it's almost added as an afterthought. To put things in perspective, their login page doesn't even support SSL by default in either drupal 5 or drupal 6. To me that's verging on pathetic.</p><p>We were lucky because user logins weren't a core part of our site concept when we implemented the site, but I am now thinking that it might be a good way to go in the future, but I'm mostly petrified of this problem.</p><p>On the bright side of things they include a large number of extensions, and things mostly work as advertised, so we found this to be our best option out of all the open source CMSes we tried.</p></htmltext>
<tokenext>I run a fairly high profile drupal site - and this has always been a large concern for us.Our solution was basically to disable user logins completely .
An overwhelming number of the exploits require you to login , so by removing this prerequisite , we basically avoided the problem.Security is n't exactly a priority for drupal either , it 's almost added as an afterthought .
To put things in perspective , their login page does n't even support SSL by default in either drupal 5 or drupal 6 .
To me that 's verging on pathetic.We were lucky because user logins were n't a core part of our site concept when we implemented the site , but I am now thinking that it might be a good way to go in the future , but I 'm mostly petrified of this problem.On the bright side of things they include a large number of extensions , and things mostly work as advertised , so we found this to be our best option out of all the open source CMSes we tried .</tokentext>
<sentencetext>I run a fairly high profile drupal site - and this has always been a large concern for us.Our solution was basically to disable user logins completely.
An overwhelming number of the exploits require you to login, so by removing this prerequisite, we basically avoided the problem.Security isn't exactly a priority for drupal either, it's almost added as an afterthought.
To put things in perspective, their login page doesn't even support SSL by default in either drupal 5 or drupal 6.
To me that's verging on pathetic.We were lucky because user logins weren't a core part of our site concept when we implemented the site, but I am now thinking that it might be a good way to go in the future, but I'm mostly petrified of this problem.On the bright side of things they include a large number of extensions, and things mostly work as advertised, so we found this to be our best option out of all the open source CMSes we tried.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868659</id>
	<title>Re:High profile target and poorly designed CMS</title>
	<author>r7</author>
	<datestamp>1256485020000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Security is most certainly not an afterthought for Drupal.<nobr> <wbr></nobr>... The upcoming Drupal 7 has SSL login support in core.</p></div><p>Equating SSL with security is emblematic of the Drupal code base.  It is, in my experience, the least secure CMS available.  Just look at how regular and often Drupal vulnerabilities are announced.  Even the Apache configuration requires you to enable FollowSymLinks!.  The website says this was a security workaround but it is also as big a hole as the one it fixed.  RewriteEngine also cannot be disabled.  And the database load is far, far greater than any well designed CMSs.  Pile PHP on top of that and you have, well, a pretty insecure webapp (to be diplomatic).  I'm sure the Feds will do all sorts of extra stuff to monitor and patch this particular site, and I hope they contribute patches back, but I would not recommend Drupal to anyone who does not have a relatively extensive background in system monitoring, PHP, MySQL or Postgres, and Apache.</p></div>
	</htmltext>
<tokenext>Security is most certainly not an afterthought for Drupal .
... The upcoming Drupal 7 has SSL login support in core.Equating SSL with security is emblematic of the Drupal code base .
It is , in my experience , the least secure CMS available .
Just look at how regular and often Drupal vulnerabilities are announced .
Even the Apache configuration requires you to enable FollowSymLinks ! .
The website says this was a security workaround but it is also as big a hole as the one it fixed .
RewriteEngine also can not be disabled .
And the database load is far , far greater than any well designed CMSs .
Pile PHP on top of that and you have , well , a pretty insecure webapp ( to be diplomatic ) .
I 'm sure the Feds will do all sorts of extra stuff to monitor and patch this particular site , and I hope they contribute patches back , but I would not recommend Drupal to anyone who does not have a relatively extensive background in system monitoring , PHP , MySQL or Postgres , and Apache .</tokentext>
<sentencetext>Security is most certainly not an afterthought for Drupal.
... The upcoming Drupal 7 has SSL login support in core.Equating SSL with security is emblematic of the Drupal code base.
It is, in my experience, the least secure CMS available.
Just look at how regular and often Drupal vulnerabilities are announced.
Even the Apache configuration requires you to enable FollowSymLinks!.
The website says this was a security workaround but it is also as big a hole as the one it fixed.
RewriteEngine also cannot be disabled.
And the database load is far, far greater than any well designed CMSs.
Pile PHP on top of that and you have, well, a pretty insecure webapp (to be diplomatic).
I'm sure the Feds will do all sorts of extra stuff to monitor and patch this particular site, and I hope they contribute patches back, but I would not recommend Drupal to anyone who does not have a relatively extensive background in system monitoring, PHP, MySQL or Postgres, and Apache.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866431</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29870323</id>
	<title>They're a bit late to the party then..</title>
	<author>cheros</author>
	<datestamp>1256552820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>November 1999, Slashdot interview with <a href="http://slashdot.org/interviews/99/11/04/1716225.shtml" title="slashdot.org">"the Queen's webmaster"</a> [slashdot.org].</p><p>What happened since?  The consultants moved in.  Just in case you missed it, an Open solution doesn't bring in half as much money and customer lock in as proprietary solutions, so the door was thrown wide open to Microsoft based IT.  <i>"Come in, all is forgiven, we've relegated those nasty sandal wearing people to some unimportant jobs.  Now, what were you saying about a nice position after I retire again?  What?  Naah, we don't need to to save money, it's TAXpayer's money.  As long as we can sell a halfway plausible reason which it's not Open we'll be OK.  Something like "not ready for industrial use" or something will do, I'm sure you can cook up some feasibility studies that "prove" that.  We'll be nice to each other, won't we?  Got any retiring people we can stick in the audit commission?</i></p><p>I'm glad the administration is showing signs of intelligence here, but it's a mighty strong lobby..</p></htmltext>
<tokenext>November 1999 , Slashdot interview with " the Queen 's webmaster " [ slashdot.org ] .What happened since ?
The consultants moved in .
Just in case you missed it , an Open solution does n't bring in half as much money and customer lock in as proprietary solutions , so the door was thrown wide open to Microsoft based IT .
" Come in , all is forgiven , we 've relegated those nasty sandal wearing people to some unimportant jobs .
Now , what were you saying about a nice position after I retire again ?
What ? Naah , we do n't need to to save money , it 's TAXpayer 's money .
As long as we can sell a halfway plausible reason which it 's not Open we 'll be OK. Something like " not ready for industrial use " or something will do , I 'm sure you can cook up some feasibility studies that " prove " that .
We 'll be nice to each other , wo n't we ?
Got any retiring people we can stick in the audit commission ? I 'm glad the administration is showing signs of intelligence here , but it 's a mighty strong lobby. .</tokentext>
<sentencetext>November 1999, Slashdot interview with "the Queen's webmaster" [slashdot.org].What happened since?
The consultants moved in.
Just in case you missed it, an Open solution doesn't bring in half as much money and customer lock in as proprietary solutions, so the door was thrown wide open to Microsoft based IT.
"Come in, all is forgiven, we've relegated those nasty sandal wearing people to some unimportant jobs.
Now, what were you saying about a nice position after I retire again?
What?  Naah, we don't need to to save money, it's TAXpayer's money.
As long as we can sell a halfway plausible reason which it's not Open we'll be OK.  Something like "not ready for industrial use" or something will do, I'm sure you can cook up some feasibility studies that "prove" that.
We'll be nice to each other, won't we?
Got any retiring people we can stick in the audit commission?I'm glad the administration is showing signs of intelligence here, but it's a mighty strong lobby..</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29870405</id>
	<title>That's some good news!</title>
	<author>janwedekind</author>
	<datestamp>1256553780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>When <a href="http://www.theregister.co.uk/2009/01/17/obama\_silverlight/" title="theregister.co.uk">Obama's inauguration speech was published using Silverlight</a> [theregister.co.uk] I thought that the Whitehouse IT had succumbed to Microsoft lobbying. So this actually good news for once. Lobbyists will have to be more careful in their rhetorics when arguing against free and open source software.</p></htmltext>
<tokenext>When Obama 's inauguration speech was published using Silverlight [ theregister.co.uk ] I thought that the Whitehouse IT had succumbed to Microsoft lobbying .
So this actually good news for once .
Lobbyists will have to be more careful in their rhetorics when arguing against free and open source software .</tokentext>
<sentencetext>When Obama's inauguration speech was published using Silverlight [theregister.co.uk] I thought that the Whitehouse IT had succumbed to Microsoft lobbying.
So this actually good news for once.
Lobbyists will have to be more careful in their rhetorics when arguing against free and open source software.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864091</id>
	<title>Re:Why CMS</title>
	<author>sadness203</author>
	<datestamp>1256481360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yeah, and since you are at it, instead of generating webpages with a database for, say, 10,000 products, let builds each of them individually. A database always limits what you can do or how you should do it...

Great logic.</htmltext>
<tokenext>Yeah , and since you are at it , instead of generating webpages with a database for , say , 10,000 products , let builds each of them individually .
A database always limits what you can do or how you should do it.. . Great logic .</tokentext>
<sentencetext>Yeah, and since you are at it, instead of generating webpages with a database for, say, 10,000 products, let builds each of them individually.
A database always limits what you can do or how you should do it...

Great logic.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864259</id>
	<title>Cool</title>
	<author>Anonymous</author>
	<datestamp>1256482740000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p>OK, guys, now everyone should shut up about anything the government does, because it went open-source, right?<br>*crickets*<br>Does the Obama administration really think they can buy us off that easily? It's a significant step forward, but I don't think we should bother to praise them in any way.</p></htmltext>
<tokenext>OK , guys , now everyone should shut up about anything the government does , because it went open-source , right ?
* crickets * Does the Obama administration really think they can buy us off that easily ?
It 's a significant step forward , but I do n't think we should bother to praise them in any way .</tokentext>
<sentencetext>OK, guys, now everyone should shut up about anything the government does, because it went open-source, right?
*crickets*Does the Obama administration really think they can buy us off that easily?
It's a significant step forward, but I don't think we should bother to praise them in any way.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864295</id>
	<title>Oh, the Obamas are so cool now!</title>
	<author>Anonymous</author>
	<datestamp>1256483100000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>0</modscore>
	<htmltext>I just wish they'd pull through in their promises of being open as in transparent. I don't give a fuck what they do with their web site but what lobbyists are showing up for the meetings is important to me.<br> <br>I guess it's hard to be openly honest when it will prove that you're a liar. Obama had the chance to change the way his office works from the ground up and fumbled the ball. Now we're getting the same old same old.</htmltext>
<tokenext>I just wish they 'd pull through in their promises of being open as in transparent .
I do n't give a fuck what they do with their web site but what lobbyists are showing up for the meetings is important to me .
I guess it 's hard to be openly honest when it will prove that you 're a liar .
Obama had the chance to change the way his office works from the ground up and fumbled the ball .
Now we 're getting the same old same old .</tokentext>
<sentencetext>I just wish they'd pull through in their promises of being open as in transparent.
I don't give a fuck what they do with their web site but what lobbyists are showing up for the meetings is important to me.
I guess it's hard to be openly honest when it will prove that you're a liar.
Obama had the chance to change the way his office works from the ground up and fumbled the ball.
Now we're getting the same old same old.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864113</id>
	<title>Re:Why CMS</title>
	<author>Anonymous</author>
	<datestamp>1256481480000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>Just a few reasons:<br>* You want to automatically use templates and not replicate formatting code<br>* You want different people that are not programmers to be able to update different parts of the website; you want to let them do it from their browser in a wysiwyg editor; you want to let them to easily first publish their articles on a staging host and then authorize somebody else to go online with it<br>* You want to allow commenting, feedback forms, registered users etc.<br>* You easily want to keep track of versions and revisions of published pages<br>* You want to automatically index the pages for searches<br>* You want to easily include dynamic(computed) data into your web pages</p></htmltext>
<tokenext>Just a few reasons : * You want to automatically use templates and not replicate formatting code * You want different people that are not programmers to be able to update different parts of the website ; you want to let them do it from their browser in a wysiwyg editor ; you want to let them to easily first publish their articles on a staging host and then authorize somebody else to go online with it * You want to allow commenting , feedback forms , registered users etc .
* You easily want to keep track of versions and revisions of published pages * You want to automatically index the pages for searches * You want to easily include dynamic ( computed ) data into your web pages</tokentext>
<sentencetext>Just a few reasons:* You want to automatically use templates and not replicate formatting code* You want different people that are not programmers to be able to update different parts of the website; you want to let them do it from their browser in a wysiwyg editor; you want to let them to easily first publish their articles on a staging host and then authorize somebody else to go online with it* You want to allow commenting, feedback forms, registered users etc.
* You easily want to keep track of versions and revisions of published pages* You want to automatically index the pages for searches* You want to easily include dynamic(computed) data into your web pages</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864563</id>
	<title>Socialist Software</title>
	<author>Anonymous</author>
	<datestamp>1256485800000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext>My first reaction to seeing this article was how long it will take for Fox News and friends to declare open source software as socialist and how comrade Obama has taken jobs away from hard working capitalist programmers.  It's really not a stretch given their track record.</htmltext>
<tokenext>My first reaction to seeing this article was how long it will take for Fox News and friends to declare open source software as socialist and how comrade Obama has taken jobs away from hard working capitalist programmers .
It 's really not a stretch given their track record .</tokentext>
<sentencetext>My first reaction to seeing this article was how long it will take for Fox News and friends to declare open source software as socialist and how comrade Obama has taken jobs away from hard working capitalist programmers.
It's really not a stretch given their track record.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868601</id>
	<title>Re:Socialist Software</title>
	<author>Monsuco</author>
	<datestamp>1256484360000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>My first reaction to seeing this article was how long it will take for Fox News and friends to declare open source software as socialist and how comrade Obama has taken jobs away from hard working capitalist programmers.  It's really not a stretch given their track record.</p></div><p>foxnews.com's server runs on Linux according to Netcraft.</p></div>
	</htmltext>
<tokenext>My first reaction to seeing this article was how long it will take for Fox News and friends to declare open source software as socialist and how comrade Obama has taken jobs away from hard working capitalist programmers .
It 's really not a stretch given their track record.foxnews.com 's server runs on Linux according to Netcraft .</tokentext>
<sentencetext>My first reaction to seeing this article was how long it will take for Fox News and friends to declare open source software as socialist and how comrade Obama has taken jobs away from hard working capitalist programmers.
It's really not a stretch given their track record.foxnews.com's server runs on Linux according to Netcraft.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866657</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>RudeIota</author>
	<datestamp>1256503740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>As much sense as that makes and as true as it may be, those who exploit will always be one step ahead of those who patch the exploits.</htmltext>
<tokenext>As much sense as that makes and as true as it may be , those who exploit will always be one step ahead of those who patch the exploits .</tokentext>
<sentencetext>As much sense as that makes and as true as it may be, those who exploit will always be one step ahead of those who patch the exploits.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864215</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864849</id>
	<title>Re:Why CMS</title>
	<author>mrjohnson</author>
	<datestamp>1256488740000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Because if I change it, I have to have a service request, check it into svn, build, file a request for change, deploy during a change window, etc. If the users can change content in a CMS, no paperwork required.</htmltext>
<tokenext>Because if I change it , I have to have a service request , check it into svn , build , file a request for change , deploy during a change window , etc .
If the users can change content in a CMS , no paperwork required .</tokentext>
<sentencetext>Because if I change it, I have to have a service request, check it into svn, build, file a request for change, deploy during a change window, etc.
If the users can change content in a CMS, no paperwork required.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29867655</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Anonymous</author>
	<datestamp>1256472180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>I'd argue it's the exact opposite: by choosing a popular, mature CMS, they're insuring a LOT of the vulnerabilities have been found, exploited and fixed.</p></div><p>Yeah - as of this month, 13 that I've received warnings about from the Drupal security mailing list! And that's DOWN from 16 in September!</p><p>It's not Open Source that's the problem, it's that they're using Drupal that's the problem.  Drupal (and PHP webapps in general) are kind of notorious when it comes to insecurity.</p></div>
	</htmltext>
<tokenext>I 'd argue it 's the exact opposite : by choosing a popular , mature CMS , they 're insuring a LOT of the vulnerabilities have been found , exploited and fixed.Yeah - as of this month , 13 that I 've received warnings about from the Drupal security mailing list !
And that 's DOWN from 16 in September ! It 's not Open Source that 's the problem , it 's that they 're using Drupal that 's the problem .
Drupal ( and PHP webapps in general ) are kind of notorious when it comes to insecurity .</tokentext>
<sentencetext>I'd argue it's the exact opposite: by choosing a popular, mature CMS, they're insuring a LOT of the vulnerabilities have been found, exploited and fixed.Yeah - as of this month, 13 that I've received warnings about from the Drupal security mailing list!
And that's DOWN from 16 in September!It's not Open Source that's the problem, it's that they're using Drupal that's the problem.
Drupal (and PHP webapps in general) are kind of notorious when it comes to insecurity.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864661</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864309</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Kifoth</author>
	<datestamp>1256483220000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext>You're assuming that the site's pages aren't served via a third party 'dumb' caching server, with the actual Drupal server locked down and disconnected from the internet.</htmltext>
<tokenext>You 're assuming that the site 's pages are n't served via a third party 'dumb ' caching server , with the actual Drupal server locked down and disconnected from the internet .</tokentext>
<sentencetext>You're assuming that the site's pages aren't served via a third party 'dumb' caching server, with the actual Drupal server locked down and disconnected from the internet.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868567</id>
	<title>Re:okay, so you guys don't like Drupal's security.</title>
	<author>jmac\_the\_man</author>
	<datestamp>1256484000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Supported on most hosting plans? I'm pretty sure the Federal Government's hosting plan includes whatever they want. For a high enough price, they could get a TCP over Carrier Pigeon server and run a mirror off that.</htmltext>
<tokenext>Supported on most hosting plans ?
I 'm pretty sure the Federal Government 's hosting plan includes whatever they want .
For a high enough price , they could get a TCP over Carrier Pigeon server and run a mirror off that .</tokentext>
<sentencetext>Supported on most hosting plans?
I'm pretty sure the Federal Government's hosting plan includes whatever they want.
For a high enough price, they could get a TCP over Carrier Pigeon server and run a mirror off that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866023</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866741</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>lawpoop</author>
	<datestamp>1256461260000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><nobr> <wbr></nobr></p><div class="quote"><p>...with the actual Drupal server locked down and disconnected from the internet.</p></div><p> How does the caching server get the original cache? Do you connect the actual server at some point, clear the cache, and let it answer requests, or do you push a cache?</p></div>
	</htmltext>
<tokenext>...with the actual Drupal server locked down and disconnected from the internet .
How does the caching server get the original cache ?
Do you connect the actual server at some point , clear the cache , and let it answer requests , or do you push a cache ?</tokentext>
<sentencetext> ...with the actual Drupal server locked down and disconnected from the internet.
How does the caching server get the original cache?
Do you connect the actual server at some point, clear the cache, and let it answer requests, or do you push a cache?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864309</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868101</id>
	<title>Does this make Drupal the first</title>
	<author>Anonymous</author>
	<datestamp>1256477700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p> Communist Management System?</p></htmltext>
<tokenext>Communist Management System ?</tokentext>
<sentencetext> Communist Management System?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864391</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Anonymous</author>
	<datestamp>1256484060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>The other side of the coin is that whitehouse.gov is a major target whatever it is running. If they used an obscure CSM there might not be many exploit scripts but the code might easily contain very bad vulnerabilities that black hats would quickly find, because they now have a reason to look at $OBSCURE\_CSM.</p></htmltext>
<tokenext>The other side of the coin is that whitehouse.gov is a major target whatever it is running .
If they used an obscure CSM there might not be many exploit scripts but the code might easily contain very bad vulnerabilities that black hats would quickly find , because they now have a reason to look at $ OBSCURE \ _CSM .</tokentext>
<sentencetext>The other side of the coin is that whitehouse.gov is a major target whatever it is running.
If they used an obscure CSM there might not be many exploit scripts but the code might easily contain very bad vulnerabilities that black hats would quickly find, because they now have a reason to look at $OBSCURE\_CSM.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29870709</id>
	<title>Re:Great...</title>
	<author>daem0n1x</author>
	<datestamp>1256558760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>
Yeah, they should write it in a generic all-purpose language that can be translated to any programming language, proprietary or open. I guess reading the brainwaves and converting it to a website could do.
</p></htmltext>
<tokenext>Yeah , they should write it in a generic all-purpose language that can be translated to any programming language , proprietary or open .
I guess reading the brainwaves and converting it to a website could do .</tokentext>
<sentencetext>
Yeah, they should write it in a generic all-purpose language that can be translated to any programming language, proprietary or open.
I guess reading the brainwaves and converting it to a website could do.
</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864133</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865869</id>
	<title>Re:Why CMS</title>
	<author>Dhalka226</author>
	<datestamp>1256497620000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>With all due respect, are you a web developer?

</p><p>For starters, a well-developed CMS and some competent IT people can produce a site every bit as quick as a static HTML site, because that's exactly what they'll be serving up with good server-side caching.  Any "weight" in the backend is more than offset by the increased ease with which content can be updated.

</p><p>Moreover, a CMS allows non-technical people to be involved in the process.  Most likely, people from the press and communications offices are going to be the ones in charge of the content on this website, and it's not at all unreasonable to assume that most of them aren't going to be any good with HTML.

</p><p>And why should they be?  CMS is exactly what it says it is -- a <em>content</em> management system, letting people focus on content by hiding away the markup and technical nonsense they're not concerned with anyway.  Sometimes it's fully inappopriate; sometimes a custom one is better than off-the-shelf.  But you really can't see why anybody would want to use one?  Ever?</p></htmltext>
<tokenext>With all due respect , are you a web developer ?
For starters , a well-developed CMS and some competent IT people can produce a site every bit as quick as a static HTML site , because that 's exactly what they 'll be serving up with good server-side caching .
Any " weight " in the backend is more than offset by the increased ease with which content can be updated .
Moreover , a CMS allows non-technical people to be involved in the process .
Most likely , people from the press and communications offices are going to be the ones in charge of the content on this website , and it 's not at all unreasonable to assume that most of them are n't going to be any good with HTML .
And why should they be ?
CMS is exactly what it says it is -- a content management system , letting people focus on content by hiding away the markup and technical nonsense they 're not concerned with anyway .
Sometimes it 's fully inappopriate ; sometimes a custom one is better than off-the-shelf .
But you really ca n't see why anybody would want to use one ?
Ever ?</tokentext>
<sentencetext>With all due respect, are you a web developer?
For starters, a well-developed CMS and some competent IT people can produce a site every bit as quick as a static HTML site, because that's exactly what they'll be serving up with good server-side caching.
Any "weight" in the backend is more than offset by the increased ease with which content can be updated.
Moreover, a CMS allows non-technical people to be involved in the process.
Most likely, people from the press and communications offices are going to be the ones in charge of the content on this website, and it's not at all unreasonable to assume that most of them aren't going to be any good with HTML.
And why should they be?
CMS is exactly what it says it is -- a content management system, letting people focus on content by hiding away the markup and technical nonsense they're not concerned with anyway.
Sometimes it's fully inappopriate; sometimes a custom one is better than off-the-shelf.
But you really can't see why anybody would want to use one?
Ever?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864233</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Anonymous</author>
	<datestamp>1256482500000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>0</modscore>
	<htmltext><p>Such a system should not be exposed.  It should be behind a modern firewall, with a solid IPS.  With such measures in place script kiddies will find it considerably harder to get their 15 minutes of fame, and even seasoned hackers will have to go to great extra lengts to get there - if they get there at all.</p></htmltext>
<tokenext>Such a system should not be exposed .
It should be behind a modern firewall , with a solid IPS .
With such measures in place script kiddies will find it considerably harder to get their 15 minutes of fame , and even seasoned hackers will have to go to great extra lengts to get there - if they get there at all .</tokentext>
<sentencetext>Such a system should not be exposed.
It should be behind a modern firewall, with a solid IPS.
With such measures in place script kiddies will find it considerably harder to get their 15 minutes of fame, and even seasoned hackers will have to go to great extra lengts to get there - if they get there at all.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868367</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Anonymous</author>
	<datestamp>1256481660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It would be nice if Drupal had better export as static HTML than exists in the one module.</p><p>Alas, most of the CMS systems lack this, or if they had it no longer do.  (Yea, I'm looking at you Lenya)</p></htmltext>
<tokenext>It would be nice if Drupal had better export as static HTML than exists in the one module.Alas , most of the CMS systems lack this , or if they had it no longer do .
( Yea , I 'm looking at you Lenya )</tokentext>
<sentencetext>It would be nice if Drupal had better export as static HTML than exists in the one module.Alas, most of the CMS systems lack this, or if they had it no longer do.
(Yea, I'm looking at you Lenya)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864447</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866179</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>nobodyknowsimageek</author>
	<datestamp>1256499720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I'm not arguing against closed source vs open, more about the many advantages of security through obscurity.</p></div><p>There, "fixed" that for you.</p></div>
	</htmltext>
<tokenext>I 'm not arguing against closed source vs open , more about the many advantages of security through obscurity.There , " fixed " that for you .</tokentext>
<sentencetext>I'm not arguing against closed source vs open, more about the many advantages of security through obscurity.There, "fixed" that for you.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868907</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>rtb61</author>
	<datestamp>1256489220000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p> Perhaps you would also like to talk about all that closed source proprietary code that government espionage agencies all over the world have access to. In fact most governments are now refusing to you closed source proprietary code unless they have access to the code to scan for back doors not only put in by corporations for then own advantage but put in by governments via secret warrants and not disclosed for national security reasons. </p><p> The biggest difference between closed source and open source in government. When government start analysing, bug finding and error correcting private closed source code, they are in fact corruptly subsidising the business activity and profitability of one company ahead of all other companies. When are government conducts the same identical activity with open source, that investment is in fact return to every single member of the public and every company has access to and can make use of those efforts and expenditures. </p><p> As for intentional flaws in open source, what a load, most secure places do not run the latest version but let it run around in the wild for a few months, not only given them time to fully and publicly audit the code but also allowing time for faults to be discovered across the wider community. Want to know the biggest example of corruption in closed source proprietary software code, a glaring example of why it should never ever be trusted, Diebold voting software, those people actually even fought it out in court to hide their source code from the foolish governments that used it after it was proved to be extraordinarily and perceived by many to be purposefully faulty. </p><p> The reality is any downside of open source is inherently in closed source as well, on the other hand there are many downsides to closed source that are not associated with open source software.</p></htmltext>
<tokenext>Perhaps you would also like to talk about all that closed source proprietary code that government espionage agencies all over the world have access to .
In fact most governments are now refusing to you closed source proprietary code unless they have access to the code to scan for back doors not only put in by corporations for then own advantage but put in by governments via secret warrants and not disclosed for national security reasons .
The biggest difference between closed source and open source in government .
When government start analysing , bug finding and error correcting private closed source code , they are in fact corruptly subsidising the business activity and profitability of one company ahead of all other companies .
When are government conducts the same identical activity with open source , that investment is in fact return to every single member of the public and every company has access to and can make use of those efforts and expenditures .
As for intentional flaws in open source , what a load , most secure places do not run the latest version but let it run around in the wild for a few months , not only given them time to fully and publicly audit the code but also allowing time for faults to be discovered across the wider community .
Want to know the biggest example of corruption in closed source proprietary software code , a glaring example of why it should never ever be trusted , Diebold voting software , those people actually even fought it out in court to hide their source code from the foolish governments that used it after it was proved to be extraordinarily and perceived by many to be purposefully faulty .
The reality is any downside of open source is inherently in closed source as well , on the other hand there are many downsides to closed source that are not associated with open source software .</tokentext>
<sentencetext> Perhaps you would also like to talk about all that closed source proprietary code that government espionage agencies all over the world have access to.
In fact most governments are now refusing to you closed source proprietary code unless they have access to the code to scan for back doors not only put in by corporations for then own advantage but put in by governments via secret warrants and not disclosed for national security reasons.
The biggest difference between closed source and open source in government.
When government start analysing, bug finding and error correcting private closed source code, they are in fact corruptly subsidising the business activity and profitability of one company ahead of all other companies.
When are government conducts the same identical activity with open source, that investment is in fact return to every single member of the public and every company has access to and can make use of those efforts and expenditures.
As for intentional flaws in open source, what a load, most secure places do not run the latest version but let it run around in the wild for a few months, not only given them time to fully and publicly audit the code but also allowing time for faults to be discovered across the wider community.
Want to know the biggest example of corruption in closed source proprietary software code, a glaring example of why it should never ever be trusted, Diebold voting software, those people actually even fought it out in court to hide their source code from the foolish governments that used it after it was proved to be extraordinarily and perceived by many to be purposefully faulty.
The reality is any downside of open source is inherently in closed source as well, on the other hand there are many downsides to closed source that are not associated with open source software.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866967</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864305</id>
	<title>PHP based?</title>
	<author>Anonymous</author>
	<datestamp>1256483160000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>I wish they used something Python based:</p><p>def askPresidentQuestion(q):<br>
&nbsp; &nbsp; &nbsp; &nbsp; if president == "Bush":<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; misSpeak()<br>
&nbsp; &nbsp; &nbsp; &nbsp; elif president == "Obama":<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; pass</p></htmltext>
<tokenext>I wish they used something Python based : def askPresidentQuestion ( q ) :         if president = = " Bush " :                 misSpeak ( )         elif president = = " Obama " :                 pass</tokentext>
<sentencetext>I wish they used something Python based:def askPresidentQuestion(q):
        if president == "Bush":
                misSpeak()
        elif president == "Obama":
                pass</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864341</id>
	<title>Re:Cool</title>
	<author>oldspewey</author>
	<datestamp>1256483460000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>As stated in the article, this wasn't done to earn your praise.</htmltext>
<tokenext>As stated in the article , this was n't done to earn your praise .</tokentext>
<sentencetext>As stated in the article, this wasn't done to earn your praise.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864259</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868843</id>
	<title>The joys of drupal</title>
	<author>Anonymous</author>
	<datestamp>1256487900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I love Drupal and I think it is a good choice. Outside the concept of it being a in a three tier system, drupal's strengths lie it in it's scalability, high availability. and the very easy plug-in  architecture. CCK is one of the best designed plug-ins ever written.</p></htmltext>
<tokenext>I love Drupal and I think it is a good choice .
Outside the concept of it being a in a three tier system , drupal 's strengths lie it in it 's scalability , high availability .
and the very easy plug-in architecture .
CCK is one of the best designed plug-ins ever written .</tokentext>
<sentencetext>I love Drupal and I think it is a good choice.
Outside the concept of it being a in a three tier system, drupal's strengths lie it in it's scalability, high availability.
and the very easy plug-in  architecture.
CCK is one of the best designed plug-ins ever written.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865941</id>
	<title>Awesome!</title>
	<author>topham</author>
	<datestamp>1256498280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is Awesome, now all the Drupal vulnerabilities will be highlighted on a daily basis!</p><p>I like Drupal, but security isn't really their strong point, nor is proper testing of their modules.</p><p>Oh well.</p></htmltext>
<tokenext>This is Awesome , now all the Drupal vulnerabilities will be highlighted on a daily basis ! I like Drupal , but security is n't really their strong point , nor is proper testing of their modules.Oh well .</tokentext>
<sentencetext>This is Awesome, now all the Drupal vulnerabilities will be highlighted on a daily basis!I like Drupal, but security isn't really their strong point, nor is proper testing of their modules.Oh well.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037</id>
	<title>Why CMS</title>
	<author>Anonymous</author>
	<datestamp>1256480880000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>I've never understood the need to use some kind of CMS behind websites. It just adds unnecessary weight and complicates things, and always limits what you can do or how you should do it. Why not just code the website completely to begin with?</p><p>It's a lot better way to go, even more so for large websites.</p></htmltext>
<tokenext>I 've never understood the need to use some kind of CMS behind websites .
It just adds unnecessary weight and complicates things , and always limits what you can do or how you should do it .
Why not just code the website completely to begin with ? It 's a lot better way to go , even more so for large websites .</tokentext>
<sentencetext>I've never understood the need to use some kind of CMS behind websites.
It just adds unnecessary weight and complicates things, and always limits what you can do or how you should do it.
Why not just code the website completely to begin with?It's a lot better way to go, even more so for large websites.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865067</id>
	<title>Re:Something fishy.</title>
	<author>micheas</author>
	<datestamp>1256491020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I suspect your memory is a little faulty.</p><p>Akamai has been reverse proxying whitehouse.gov for quite some time.</p><p>So IIS on linux might have been reported, but all sites akamai proxies for show up as being on linux. See<br><a href="http://uptime.netcraft.com/up/graph?site=search.microsoft.com" title="netcraft.com">http://uptime.netcraft.com/up/graph?site=search.microsoft.com</a> [netcraft.com] for example</p><p>of IIS/6.0 on linux.</p></htmltext>
<tokenext>I suspect your memory is a little faulty.Akamai has been reverse proxying whitehouse.gov for quite some time.So IIS on linux might have been reported , but all sites akamai proxies for show up as being on linux .
Seehttp : //uptime.netcraft.com/up/graph ? site = search.microsoft.com [ netcraft.com ] for exampleof IIS/6.0 on linux .</tokentext>
<sentencetext>I suspect your memory is a little faulty.Akamai has been reverse proxying whitehouse.gov for quite some time.So IIS on linux might have been reported, but all sites akamai proxies for show up as being on linux.
Seehttp://uptime.netcraft.com/up/graph?site=search.microsoft.com [netcraft.com] for exampleof IIS/6.0 on linux.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864207</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866929</id>
	<title>Afghans Applaud use of Open Source!</title>
	<author>For a Free Internet</author>
	<datestamp>1256463000000</datestamp>
	<modclass>Funny</modclass>
	<modscore>0</modscore>
	<htmltext><p>Those who haven't had a hand or two blown off by Obama's cluster bombs, that is...</p></htmltext>
<tokenext>Those who have n't had a hand or two blown off by Obama 's cluster bombs , that is.. .</tokentext>
<sentencetext>Those who haven't had a hand or two blown off by Obama's cluster bombs, that is...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865615</id>
	<title>My first take is</title>
	<author>Anonymous</author>
	<datestamp>1256495580000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>does this even offset a Administration which takes all the bad habits of the last and compounds them with super sized bills that no one gets to review and a good dose of intimidation against any who speak up?</p></htmltext>
<tokenext>does this even offset a Administration which takes all the bad habits of the last and compounds them with super sized bills that no one gets to review and a good dose of intimidation against any who speak up ?</tokentext>
<sentencetext>does this even offset a Administration which takes all the bad habits of the last and compounds them with super sized bills that no one gets to review and a good dose of intimidation against any who speak up?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868831</id>
	<title>You know, a lot of people here are very silly.</title>
	<author>DavidTC</author>
	<datestamp>1256487660000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Yes, whitehouse.gov is a very attacked site, for all sorts of reasons, and I bet it will be the very first place to try out any new Drupal vulnerability, and at least one of those will succeed sometime in the next couple of years.</p><p>
But, um...who cares if it does? It's not a mission critical web site. It's stupid fluff pieces about the president and his initiatives. If something goes wrong it gets flipped offline, restored from backup, patched, and brought back online.</p><p>
It's interesting to see the government try OSS, and that might be an interesting discussion, but way too many people(1) here instantly leapt to the non-existence security implications, acting like important government computers were going to be exposed via any security issues in Drupal.</p><p>
1) And half the remaining people appear to be morons talking about how CMS are useless. They haven't realized that stating 'people don't need CMSes' doesn't, like they think, show that they're some elite HTML coder, it just reveals them as someone who's never been hired to make a web site for someone else who then can add and remove content.</p></htmltext>
<tokenext>Yes , whitehouse.gov is a very attacked site , for all sorts of reasons , and I bet it will be the very first place to try out any new Drupal vulnerability , and at least one of those will succeed sometime in the next couple of years .
But , um...who cares if it does ?
It 's not a mission critical web site .
It 's stupid fluff pieces about the president and his initiatives .
If something goes wrong it gets flipped offline , restored from backup , patched , and brought back online .
It 's interesting to see the government try OSS , and that might be an interesting discussion , but way too many people ( 1 ) here instantly leapt to the non-existence security implications , acting like important government computers were going to be exposed via any security issues in Drupal .
1 ) And half the remaining people appear to be morons talking about how CMS are useless .
They have n't realized that stating 'people do n't need CMSes ' does n't , like they think , show that they 're some elite HTML coder , it just reveals them as someone who 's never been hired to make a web site for someone else who then can add and remove content .</tokentext>
<sentencetext>Yes, whitehouse.gov is a very attacked site, for all sorts of reasons, and I bet it will be the very first place to try out any new Drupal vulnerability, and at least one of those will succeed sometime in the next couple of years.
But, um...who cares if it does?
It's not a mission critical web site.
It's stupid fluff pieces about the president and his initiatives.
If something goes wrong it gets flipped offline, restored from backup, patched, and brought back online.
It's interesting to see the government try OSS, and that might be an interesting discussion, but way too many people(1) here instantly leapt to the non-existence security implications, acting like important government computers were going to be exposed via any security issues in Drupal.
1) And half the remaining people appear to be morons talking about how CMS are useless.
They haven't realized that stating 'people don't need CMSes' doesn't, like they think, show that they're some elite HTML coder, it just reveals them as someone who's never been hired to make a web site for someone else who then can add and remove content.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864133</id>
	<title>Great...</title>
	<author>Anonymous</author>
	<datestamp>1256481720000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p>Now they're locked in to PHP.</p></htmltext>
<tokenext>Now they 're locked in to PHP .</tokentext>
<sentencetext>Now they're locked in to PHP.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29867263</id>
	<title>Don't forget about the Free Software...</title>
	<author>jojo78</author>
	<datestamp>1256466900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><a href="http://e107.org/news.php" title="e107.org" rel="nofollow">e107</a> [e107.org].</htmltext>
<tokenext>e107 [ e107.org ] .</tokentext>
<sentencetext>e107 [e107.org].</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866309</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>dogmatixpsych</author>
	<datestamp>1256500560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yep, that's the same reasoning Microsoft makes with Windows being more secure than OS X!<nobr> <wbr></nobr>;)<br> <br>
[Not really, I'm just trying to be mildly humorous].</htmltext>
<tokenext>Yep , that 's the same reasoning Microsoft makes with Windows being more secure than OS X !
; ) [ Not really , I 'm just trying to be mildly humorous ] .</tokentext>
<sentencetext>Yep, that's the same reasoning Microsoft makes with Windows being more secure than OS X!
;) 
[Not really, I'm just trying to be mildly humorous].</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864215</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868851</id>
	<title>Re:PHP based?</title>
	<author>idlemachine</author>
	<datestamp>1256487960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The pythonic solution would be to swap the if/elif for a dictionary dispatcher...<nobr> <wbr></nobr>;)</p></htmltext>
<tokenext>The pythonic solution would be to swap the if/elif for a dictionary dispatcher... ; )</tokentext>
<sentencetext>The pythonic solution would be to swap the if/elif for a dictionary dispatcher... ;)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864305</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865263</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>saltydogdesign</author>
	<datestamp>1256492940000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>The advantage to using Drupal for the White House is that it's a popular CMS and has lots of people patching exploits and vulnerabilities. The second a proof of concept piece of code or an easy exploit is discovered, a few thousand developers will descend to get their patches submitted.</p><p>As opposed to your homegrown CMS, where you only discover the security holes when 3gotiZt posts pictures of full frontal nudity on the home page of your site.</p></htmltext>
<tokenext>The advantage to using Drupal for the White House is that it 's a popular CMS and has lots of people patching exploits and vulnerabilities .
The second a proof of concept piece of code or an easy exploit is discovered , a few thousand developers will descend to get their patches submitted.As opposed to your homegrown CMS , where you only discover the security holes when 3gotiZt posts pictures of full frontal nudity on the home page of your site .</tokentext>
<sentencetext>The advantage to using Drupal for the White House is that it's a popular CMS and has lots of people patching exploits and vulnerabilities.
The second a proof of concept piece of code or an easy exploit is discovered, a few thousand developers will descend to get their patches submitted.As opposed to your homegrown CMS, where you only discover the security holes when 3gotiZt posts pictures of full frontal nudity on the home page of your site.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29870571</id>
	<title>Now time for videos...</title>
	<author>abbe</author>
	<datestamp>1256556540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Now lets hope they start publishing their videos from Adobe Flash to HTML5 VIDEO tag based on User-Agent strings. Looking forward to watch some Theora content from whitehouse.gov.</p></htmltext>
<tokenext>Now lets hope they start publishing their videos from Adobe Flash to HTML5 VIDEO tag based on User-Agent strings .
Looking forward to watch some Theora content from whitehouse.gov .</tokentext>
<sentencetext>Now lets hope they start publishing their videos from Adobe Flash to HTML5 VIDEO tag based on User-Agent strings.
Looking forward to watch some Theora content from whitehouse.gov.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865277</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Anonymous</author>
	<datestamp>1256493060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Speaking of Open Source, why the fuck does Slashdot comment thresholding work properly in Internet Explorer but not Firefox or Safari?</p></htmltext>
<tokenext>Speaking of Open Source , why the fuck does Slashdot comment thresholding work properly in Internet Explorer but not Firefox or Safari ?</tokentext>
<sentencetext>Speaking of Open Source, why the fuck does Slashdot comment thresholding work properly in Internet Explorer but not Firefox or Safari?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864429</id>
	<title>The friend of my enemy is...</title>
	<author>Anonymous</author>
	<datestamp>1256484360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>"...and that they can benefit from the innovation that is the result of thousands of developers collaborating on Drupal.'"</p><p>All located in countries hostile to the west.</p></htmltext>
<tokenext>" ...and that they can benefit from the innovation that is the result of thousands of developers collaborating on Drupal .
' " All located in countries hostile to the west .</tokentext>
<sentencetext>"...and that they can benefit from the innovation that is the result of thousands of developers collaborating on Drupal.
'"All located in countries hostile to the west.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866701</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>abigsmurf</author>
	<datestamp>1256504100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>With Linux you can heap extra layers of security on so that exploits can't be attempted. You not only have to deal with an exploit, you need to get past all the other security measures too.
<br> <br>
With a web based CMS you are constantly exposed and exploits can implemented and run in minutes (mod security only provides limited protection). You don't need to infect a webserver to do damage, you just need to be able run an sql query or upload a file with code.
<br> <br>
There will always be a timelag between an exploit being identified and a patch being installed on a server and that's a real problem for sites like The White House.
<br> <br>
An online store can ensure it's e-commerce sections are heavily sandboxed, a popular news site may get the odd attack which will get mentioned by a few blogs. The White House however would make for major news if it was defaced or delivered malicious code to users and it would be under attack far more than almost any other Drupal sites.
<br> <br>
Drupal is a big target. Exploiting Drupal means being able to hack 10,000's of sites.
<br> <br>
Assume you have 10 people determined to hack the white house. In a custom CMS, you've 10 people searching for exploits and abusing them when one is found. In a popular CMS, you then have 1000 people looking for exploits and, once one's published the 10 people from the first case then proceed to code an attack in an attempt to beat the patch.</htmltext>
<tokenext>With Linux you can heap extra layers of security on so that exploits ca n't be attempted .
You not only have to deal with an exploit , you need to get past all the other security measures too .
With a web based CMS you are constantly exposed and exploits can implemented and run in minutes ( mod security only provides limited protection ) .
You do n't need to infect a webserver to do damage , you just need to be able run an sql query or upload a file with code .
There will always be a timelag between an exploit being identified and a patch being installed on a server and that 's a real problem for sites like The White House .
An online store can ensure it 's e-commerce sections are heavily sandboxed , a popular news site may get the odd attack which will get mentioned by a few blogs .
The White House however would make for major news if it was defaced or delivered malicious code to users and it would be under attack far more than almost any other Drupal sites .
Drupal is a big target .
Exploiting Drupal means being able to hack 10,000 's of sites .
Assume you have 10 people determined to hack the white house .
In a custom CMS , you 've 10 people searching for exploits and abusing them when one is found .
In a popular CMS , you then have 1000 people looking for exploits and , once one 's published the 10 people from the first case then proceed to code an attack in an attempt to beat the patch .</tokentext>
<sentencetext>With Linux you can heap extra layers of security on so that exploits can't be attempted.
You not only have to deal with an exploit, you need to get past all the other security measures too.
With a web based CMS you are constantly exposed and exploits can implemented and run in minutes (mod security only provides limited protection).
You don't need to infect a webserver to do damage, you just need to be able run an sql query or upload a file with code.
There will always be a timelag between an exploit being identified and a patch being installed on a server and that's a real problem for sites like The White House.
An online store can ensure it's e-commerce sections are heavily sandboxed, a popular news site may get the odd attack which will get mentioned by a few blogs.
The White House however would make for major news if it was defaced or delivered malicious code to users and it would be under attack far more than almost any other Drupal sites.
Drupal is a big target.
Exploiting Drupal means being able to hack 10,000's of sites.
Assume you have 10 people determined to hack the white house.
In a custom CMS, you've 10 people searching for exploits and abusing them when one is found.
In a popular CMS, you then have 1000 people looking for exploits and, once one's published the 10 people from the first case then proceed to code an attack in an attempt to beat the patch.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864661</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864661</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Anonymous</author>
	<datestamp>1256486940000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>Didn't most people agree that security through obscurity is bad? If using popular open-source software was so bad, how come so many servers use Linux?<br>
<br>
I'd argue it's the exact opposite: by choosing a popular, mature CMS, they're insuring a LOT of the vulnerabilities have been found, exploited and fixed. The major difference between the White House site and Joe Web Dev's site is that the former will probably only upgrade for security fixes and will be very careful with new features, since that's where the bugs and exploits can hide. With good sysadmins, proper security tools and good practices, the site can be very safe. I just don't see them using alpha versions of modules and such.<br>
<br>
On the flip side, I'm hopeful that WhiteHouse.org's programmers and sysadmins will also contribute to the codebase with fixes and improvements of their own. This could end up being very beneficial for the Drupal community.</htmltext>
<tokenext>Did n't most people agree that security through obscurity is bad ?
If using popular open-source software was so bad , how come so many servers use Linux ?
I 'd argue it 's the exact opposite : by choosing a popular , mature CMS , they 're insuring a LOT of the vulnerabilities have been found , exploited and fixed .
The major difference between the White House site and Joe Web Dev 's site is that the former will probably only upgrade for security fixes and will be very careful with new features , since that 's where the bugs and exploits can hide .
With good sysadmins , proper security tools and good practices , the site can be very safe .
I just do n't see them using alpha versions of modules and such .
On the flip side , I 'm hopeful that WhiteHouse.org 's programmers and sysadmins will also contribute to the codebase with fixes and improvements of their own .
This could end up being very beneficial for the Drupal community .</tokentext>
<sentencetext>Didn't most people agree that security through obscurity is bad?
If using popular open-source software was so bad, how come so many servers use Linux?
I'd argue it's the exact opposite: by choosing a popular, mature CMS, they're insuring a LOT of the vulnerabilities have been found, exploited and fixed.
The major difference between the White House site and Joe Web Dev's site is that the former will probably only upgrade for security fixes and will be very careful with new features, since that's where the bugs and exploits can hide.
With good sysadmins, proper security tools and good practices, the site can be very safe.
I just don't see them using alpha versions of modules and such.
On the flip side, I'm hopeful that WhiteHouse.org's programmers and sysadmins will also contribute to the codebase with fixes and improvements of their own.
This could end up being very beneficial for the Drupal community.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868135</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Alpha830RulZ</author>
	<datestamp>1256478120000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>You're certainly right the Drupal has a lot of visibility.  On the other hand, is it the end of the world if Whitehouse.gov gets exploited?  If we can assume that the site is reasonably managed, and does not have a direct pipeline from the front end web server into the CIA's servers, then the likely worst result would seem to be that misinformation would be published.  This isnt' good, but it would probably get detected fairly quickly by partisans.  We're not talking missle launch systems here.</p><p>If Drupal helps the government interact better and communicate better with us, and reduces their costs for doing so,  I think the security risk is probably reasonable.  That said, I'd be surprised if Drupal is particularly weak.  We don't hear much about exploits. The top link from a google of "drupal exploit" is dated 2005.</p><p>Lets ask the question a different way:  Should the whitehouse use an open source webserver like Apache or Tomcat for the webserver, or should they use IIS? Should they run on open source Linux, or Windows Server?  Or should they write their own webserver and OS, to avoid the hacking risk that an opensource system creates?</p></htmltext>
<tokenext>You 're certainly right the Drupal has a lot of visibility .
On the other hand , is it the end of the world if Whitehouse.gov gets exploited ?
If we can assume that the site is reasonably managed , and does not have a direct pipeline from the front end web server into the CIA 's servers , then the likely worst result would seem to be that misinformation would be published .
This isnt ' good , but it would probably get detected fairly quickly by partisans .
We 're not talking missle launch systems here.If Drupal helps the government interact better and communicate better with us , and reduces their costs for doing so , I think the security risk is probably reasonable .
That said , I 'd be surprised if Drupal is particularly weak .
We do n't hear much about exploits .
The top link from a google of " drupal exploit " is dated 2005.Lets ask the question a different way : Should the whitehouse use an open source webserver like Apache or Tomcat for the webserver , or should they use IIS ?
Should they run on open source Linux , or Windows Server ?
Or should they write their own webserver and OS , to avoid the hacking risk that an opensource system creates ?</tokentext>
<sentencetext>You're certainly right the Drupal has a lot of visibility.
On the other hand, is it the end of the world if Whitehouse.gov gets exploited?
If we can assume that the site is reasonably managed, and does not have a direct pipeline from the front end web server into the CIA's servers, then the likely worst result would seem to be that misinformation would be published.
This isnt' good, but it would probably get detected fairly quickly by partisans.
We're not talking missle launch systems here.If Drupal helps the government interact better and communicate better with us, and reduces their costs for doing so,  I think the security risk is probably reasonable.
That said, I'd be surprised if Drupal is particularly weak.
We don't hear much about exploits.
The top link from a google of "drupal exploit" is dated 2005.Lets ask the question a different way:  Should the whitehouse use an open source webserver like Apache or Tomcat for the webserver, or should they use IIS?
Should they run on open source Linux, or Windows Server?
Or should they write their own webserver and OS, to avoid the hacking risk that an opensource system creates?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864909</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Anonymous</author>
	<datestamp>1256489340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>As a receiver of the Drupal security emails, I can tell you the team is very active. There are a lot of community developed Drupal modules, and the security team is well into combing through them. The documentation for writing secure code is easily found and followed. Drupal is quite well done, plain and simple. It's a gem in the FOSS world. And companies like Acquia,where Drupal's original creator can be found, offer support services that include moving a Drupal site into Amazon's cloud. It is worth learning.</p></htmltext>
<tokenext>As a receiver of the Drupal security emails , I can tell you the team is very active .
There are a lot of community developed Drupal modules , and the security team is well into combing through them .
The documentation for writing secure code is easily found and followed .
Drupal is quite well done , plain and simple .
It 's a gem in the FOSS world .
And companies like Acquia,where Drupal 's original creator can be found , offer support services that include moving a Drupal site into Amazon 's cloud .
It is worth learning .</tokentext>
<sentencetext>As a receiver of the Drupal security emails, I can tell you the team is very active.
There are a lot of community developed Drupal modules, and the security team is well into combing through them.
The documentation for writing secure code is easily found and followed.
Drupal is quite well done, plain and simple.
It's a gem in the FOSS world.
And companies like Acquia,where Drupal's original creator can be found, offer support services that include moving a Drupal site into Amazon's cloud.
It is worth learning.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864297</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868171</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Alpha830RulZ</author>
	<datestamp>1256478360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>On the flip side, I'm hopeful that WhiteHouse.org's programmers and sysadmins will also contribute to the codebase with fixes and improvements of their own. This could end up being very beneficial for the Drupal community.</p></div><p>I think it will be a huge positive for Drupal's use in the business world.  That alone will be beneficial to the Drupal Community.</p></div>
	</htmltext>
<tokenext>On the flip side , I 'm hopeful that WhiteHouse.org 's programmers and sysadmins will also contribute to the codebase with fixes and improvements of their own .
This could end up being very beneficial for the Drupal community.I think it will be a huge positive for Drupal 's use in the business world .
That alone will be beneficial to the Drupal Community .</tokentext>
<sentencetext>On the flip side, I'm hopeful that WhiteHouse.org's programmers and sysadmins will also contribute to the codebase with fixes and improvements of their own.
This could end up being very beneficial for the Drupal community.I think it will be a huge positive for Drupal's use in the business world.
That alone will be beneficial to the Drupal Community.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864661</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864569</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>Junior J. Junior III</author>
	<datestamp>1256485800000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>Popular OSS products are generally popular for a good reason.  Many people find them to be useful.

Lots of people looking for exploits on a popular product means that, all things being equal, the more popular product will be more secure, not less, so long as security holes are being attended to by the project's maintainers.  If a product is good enough to become popular, that usually means that the product also has people working on it who know what they're doing, and with a lot of interest in a product it means that there's likely to be more interest in contributing improvements.

Going with an unfamiliar/poorly known/obscure solution isn't going to help whitehouse.gov.  People know about whitehouse.gov, and are going to want to attack it, regardless of what they implement the site in.  If it's some obscure solution that few people know about, then you can be sure very quickly people will start to learn about it.  So selecting a more obscure solution isn't going to help them out any.</htmltext>
<tokenext>Popular OSS products are generally popular for a good reason .
Many people find them to be useful .
Lots of people looking for exploits on a popular product means that , all things being equal , the more popular product will be more secure , not less , so long as security holes are being attended to by the project 's maintainers .
If a product is good enough to become popular , that usually means that the product also has people working on it who know what they 're doing , and with a lot of interest in a product it means that there 's likely to be more interest in contributing improvements .
Going with an unfamiliar/poorly known/obscure solution is n't going to help whitehouse.gov .
People know about whitehouse.gov , and are going to want to attack it , regardless of what they implement the site in .
If it 's some obscure solution that few people know about , then you can be sure very quickly people will start to learn about it .
So selecting a more obscure solution is n't going to help them out any .</tokentext>
<sentencetext>Popular OSS products are generally popular for a good reason.
Many people find them to be useful.
Lots of people looking for exploits on a popular product means that, all things being equal, the more popular product will be more secure, not less, so long as security holes are being attended to by the project's maintainers.
If a product is good enough to become popular, that usually means that the product also has people working on it who know what they're doing, and with a lot of interest in a product it means that there's likely to be more interest in contributing improvements.
Going with an unfamiliar/poorly known/obscure solution isn't going to help whitehouse.gov.
People know about whitehouse.gov, and are going to want to attack it, regardless of what they implement the site in.
If it's some obscure solution that few people know about, then you can be sure very quickly people will start to learn about it.
So selecting a more obscure solution isn't going to help them out any.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866967</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>nmb3000</author>
	<datestamp>1256463360000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p><i>because it's a popular CMS and has a lot of people looking through it's code for exploits, it's also a lot more secure</i></p><p>As pointed out, Wordpress easily proves this long-believed mantra false. It's one of the mostly widely used blogging applications and it is consistently in the news for high-profile hacks and exploits.  That, and Drupal hardly seems <a href="http://www.google.com/search?q=drupal+exploits" title="google.com">immune</a> [google.com].</p><p>What's even more interesting is the possibility for <i>intentional</i> security flaws in the code.  Interested parties can start submitting patches and changes to the Drupal codebase with inherent flaws. These might even be distributed (module A has a flaw that uses module B's flaw that uses module C's flaw...), which combined with submissions over a series of weeks or months and it seems unlikely they'll be easily spotted.</p><p>This is the real downside to using open source code in government applications -- In four months the White House website may be running code written by Chineses (or Russian or whoever) hackers (who may or may not be government employees) for the sole purpose of exploiting the site.  Expand this into internally used applications like MediaWiki, Pidgin and it has even bigger implications for intelligence gathering and infiltration.</p><p>Major programs like these are big and complex. If the Debian OpenSSH fiasco taught us anything it should be that when you combine big and complex, don't be surprised if those many average eyes are insufficient to catch what the few skilled and experience hands put in the codebase.</p></htmltext>
<tokenext>because it 's a popular CMS and has a lot of people looking through it 's code for exploits , it 's also a lot more secureAs pointed out , Wordpress easily proves this long-believed mantra false .
It 's one of the mostly widely used blogging applications and it is consistently in the news for high-profile hacks and exploits .
That , and Drupal hardly seems immune [ google.com ] .What 's even more interesting is the possibility for intentional security flaws in the code .
Interested parties can start submitting patches and changes to the Drupal codebase with inherent flaws .
These might even be distributed ( module A has a flaw that uses module B 's flaw that uses module C 's flaw... ) , which combined with submissions over a series of weeks or months and it seems unlikely they 'll be easily spotted.This is the real downside to using open source code in government applications -- In four months the White House website may be running code written by Chineses ( or Russian or whoever ) hackers ( who may or may not be government employees ) for the sole purpose of exploiting the site .
Expand this into internally used applications like MediaWiki , Pidgin and it has even bigger implications for intelligence gathering and infiltration.Major programs like these are big and complex .
If the Debian OpenSSH fiasco taught us anything it should be that when you combine big and complex , do n't be surprised if those many average eyes are insufficient to catch what the few skilled and experience hands put in the codebase .</tokentext>
<sentencetext>because it's a popular CMS and has a lot of people looking through it's code for exploits, it's also a lot more secureAs pointed out, Wordpress easily proves this long-believed mantra false.
It's one of the mostly widely used blogging applications and it is consistently in the news for high-profile hacks and exploits.
That, and Drupal hardly seems immune [google.com].What's even more interesting is the possibility for intentional security flaws in the code.
Interested parties can start submitting patches and changes to the Drupal codebase with inherent flaws.
These might even be distributed (module A has a flaw that uses module B's flaw that uses module C's flaw...), which combined with submissions over a series of weeks or months and it seems unlikely they'll be easily spotted.This is the real downside to using open source code in government applications -- In four months the White House website may be running code written by Chineses (or Russian or whoever) hackers (who may or may not be government employees) for the sole purpose of exploiting the site.
Expand this into internally used applications like MediaWiki, Pidgin and it has even bigger implications for intelligence gathering and infiltration.Major programs like these are big and complex.
If the Debian OpenSSH fiasco taught us anything it should be that when you combine big and complex, don't be surprised if those many average eyes are insufficient to catch what the few skilled and experience hands put in the codebase.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864215</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866377</id>
	<title>Re:High profile target and popular CMS'</title>
	<author>blakhol</author>
	<datestamp>1256501340000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>Drupal really has not been known for its security in the past;</p></div><p>On the contrary. Drupal was one of the big open source projects to have a dedicated security team performing code audits and going through a security release process.</p><p>Drupal automatically checks for security updates (both in the core and in contributed modules) and can notify you immediately of updates. If, you know, you think that kind of thing is important.</p></div>
	</htmltext>
<tokenext>Drupal really has not been known for its security in the past ; On the contrary .
Drupal was one of the big open source projects to have a dedicated security team performing code audits and going through a security release process.Drupal automatically checks for security updates ( both in the core and in contributed modules ) and can notify you immediately of updates .
If , you know , you think that kind of thing is important .</tokentext>
<sentencetext>Drupal really has not been known for its security in the past;On the contrary.
Drupal was one of the big open source projects to have a dedicated security team performing code audits and going through a security release process.Drupal automatically checks for security updates (both in the core and in contributed modules) and can notify you immediately of updates.
If, you know, you think that kind of thing is important.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864297</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865103
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864259
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868907
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866967
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864215
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868851
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864305
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868767
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864447
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864621
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864297
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866701
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864661
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868673
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866967
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864215
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29874979
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864233
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866741
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864309
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864259
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864315
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864133
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29872439
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29867655
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864661
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865615
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864563
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864391
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29870709
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864133
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864345
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864259
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865869
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868659
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866431
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864447
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866309
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864215
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866657
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864215
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864667
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864113
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864473
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864639
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864563
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864437
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864275
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29876489
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864909
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864297
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865277
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865067
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864207
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864149
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864569
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864661
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868367
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864447
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864535
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864849
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868567
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866023
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865263
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864089
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866377
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864297
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29870759
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866431
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864447
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868601
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864563
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_25_1126210_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866931
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864037
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865869
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864113
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864149
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864091
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864089
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864849
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29874979
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864429
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864305
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868851
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864207
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865067
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864563
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864639
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868601
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865615
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864295
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864275
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864437
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864259
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865103
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864345
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864341
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864153
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864661
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29867655
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29872439
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868171
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866701
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864535
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866931
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864667
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864447
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868367
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868767
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866431
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29870759
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868659
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865277
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864215
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866967
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868673
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868907
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866309
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866657
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29876489
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864473
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865263
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866179
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864309
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866741
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864391
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868135
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864297
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866377
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864909
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864621
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864569
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864233
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29865941
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864133
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29864315
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29870709
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_25_1126210.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29866023
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_25_1126210.29868567
</commentlist>
</conversation>
