<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_07_03_1637228</id>
	<title>Seattle Data Center Outage Disrupts E-Commerce</title>
	<author>ScuttleMonkey</author>
	<datestamp>1246641060000</datestamp>
	<htmltext><a href="http://www.gamehostingguide.com/" rel="nofollow">1sockchuck</a> writes <i>"A <a href="http://www.datacenterknowledge.com/archives/2009/07/03/major-outage-at-seattle-data-center/">major power outage</a> at Seattle telecom hub Fisher Plaza has knocked payment processing provider Authorize.net offline for hours, leaving thousands of web sites unable to take credit cards for online sales. The Authorize site is still down, but its <a href="http://twitter.com/authorizenet">Twitter account</a> attributes the outage to a fire, while AdHost calls it a 'significant power event.' Authorize.net is said to be trying to resume processing from a backup data center, but there's no clear ETA on when Fisher Plaza will have power again."</i></htmltext>
<tokenext>1sockchuck writes " A major power outage at Seattle telecom hub Fisher Plaza has knocked payment processing provider Authorize.net offline for hours , leaving thousands of web sites unable to take credit cards for online sales .
The Authorize site is still down , but its Twitter account attributes the outage to a fire , while AdHost calls it a 'significant power event .
' Authorize.net is said to be trying to resume processing from a backup data center , but there 's no clear ETA on when Fisher Plaza will have power again .
"</tokentext>
<sentencetext>1sockchuck writes "A major power outage at Seattle telecom hub Fisher Plaza has knocked payment processing provider Authorize.net offline for hours, leaving thousands of web sites unable to take credit cards for online sales.
The Authorize site is still down, but its Twitter account attributes the outage to a fire, while AdHost calls it a 'significant power event.
' Authorize.net is said to be trying to resume processing from a backup data center, but there's no clear ETA on when Fisher Plaza will have power again.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573481</id>
	<title>Re:Heh</title>
	<author>Anonymous</author>
	<datestamp>1246646880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This is why clustering is ABSOLUTELY necessary for as large a company as Authorize.net. As parent said, putting all your eggs in one basket is a stupid idea...<br> <br>

I wonder how many companies will switch to PayPal after this...</htmltext>
<tokenext>This is why clustering is ABSOLUTELY necessary for as large a company as Authorize.net .
As parent said , putting all your eggs in one basket is a stupid idea.. . I wonder how many companies will switch to PayPal after this.. .</tokentext>
<sentencetext>This is why clustering is ABSOLUTELY necessary for as large a company as Authorize.net.
As parent said, putting all your eggs in one basket is a stupid idea... 

I wonder how many companies will switch to PayPal after this...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573147</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576493</id>
	<title>Re:sloppy engineering</title>
	<author>Blakey Rat</author>
	<datestamp>1246627620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Also, having a Slashdot account.</p></htmltext>
<tokenext>Also , having a Slashdot account .</tokentext>
<sentencetext>Also, having a Slashdot account.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574119</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573429</id>
	<title>Re:Heh</title>
	<author>Clever7Devil</author>
	<datestamp>1246646640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Denial of service as it were?</htmltext>
<tokenext>Denial of service as it were ?</tokentext>
<sentencetext>Denial of service as it were?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573147</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28578819</id>
	<title>Re:Failover Planning (and this broke FiOS too)</title>
	<author>dodobh</author>
	<datestamp>1246702380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Not everything can always be hot/hot. Anything involving state and large data volumes, for example.<br>Think large databases. You need block level hot/hot for redundancy. Now for real redundancy, you need the other datastore to be in a different geography, and under a different government. That's a lot of latency per transaction.</p><p>Hot/Warm may be feasible.</p></htmltext>
<tokenext>Not everything can always be hot/hot .
Anything involving state and large data volumes , for example.Think large databases .
You need block level hot/hot for redundancy .
Now for real redundancy , you need the other datastore to be in a different geography , and under a different government .
That 's a lot of latency per transaction.Hot/Warm may be feasible .</tokentext>
<sentencetext>Not everything can always be hot/hot.
Anything involving state and large data volumes, for example.Think large databases.
You need block level hot/hot for redundancy.
Now for real redundancy, you need the other datastore to be in a different geography, and under a different government.
That's a lot of latency per transaction.Hot/Warm may be feasible.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573285</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575271</id>
	<title>Re:sloppy engineering</title>
	<author>citylivin</author>
	<datestamp>1246616760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Pacific Standard Time.</p><p>Seattle is on the west coast.</p><p>Not everyone lives in new york you know...</p></htmltext>
<tokenext>Pacific Standard Time.Seattle is on the west coast.Not everyone lives in new york you know.. .</tokentext>
<sentencetext>Pacific Standard Time.Seattle is on the west coast.Not everyone lives in new york you know...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574985</id>
	<title>Fisher Plaza Designed to survive External factors</title>
	<author>stmfreak</author>
	<datestamp>1246614600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I used to manage a 22 rack cage that we leased from Internap at Fisher Plaza back in 2005. They really did build the place well. Massive diesel generators, independent well water, redundant cooling, etc. But it was designed to survive and continue broadcasting for a local news station for 18 days without resupply in the event of a major <b>external</b> disaster like an earthquake.</p><p>I imagine they are reviewing their DR procedures and designs now to minimize collateral damage from internal factors.</p><p>But let's not be too hard on them, it was one of the better colo facilities I've seen. There are far worse out there holding their pants up with three hands.</p></htmltext>
<tokenext>I used to manage a 22 rack cage that we leased from Internap at Fisher Plaza back in 2005 .
They really did build the place well .
Massive diesel generators , independent well water , redundant cooling , etc .
But it was designed to survive and continue broadcasting for a local news station for 18 days without resupply in the event of a major external disaster like an earthquake.I imagine they are reviewing their DR procedures and designs now to minimize collateral damage from internal factors.But let 's not be too hard on them , it was one of the better colo facilities I 've seen .
There are far worse out there holding their pants up with three hands .</tokentext>
<sentencetext>I used to manage a 22 rack cage that we leased from Internap at Fisher Plaza back in 2005.
They really did build the place well.
Massive diesel generators, independent well water, redundant cooling, etc.
But it was designed to survive and continue broadcasting for a local news station for 18 days without resupply in the event of a major external disaster like an earthquake.I imagine they are reviewing their DR procedures and designs now to minimize collateral damage from internal factors.But let's not be too hard on them, it was one of the better colo facilities I've seen.
There are far worse out there holding their pants up with three hands.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573919</id>
	<title>Re:sloppy engineering</title>
	<author>hey</author>
	<datestamp>1246649700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I guess your point is that it is PDT time now.</p></htmltext>
<tokenext>I guess your point is that it is PDT time now .</tokentext>
<sentencetext>I guess your point is that it is PDT time now.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574309</id>
	<title>Re:Button pusher did it</title>
	<author>supernova\_hq</author>
	<datestamp>1246652880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>So THAT'S why there was a do not touch sign above it...
<br>
*avoids eye contact*</htmltext>
<tokenext>So THAT 'S why there was a do not touch sign above it.. . * avoids eye contact *</tokentext>
<sentencetext>So THAT'S why there was a do not touch sign above it...

*avoids eye contact*</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573441</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574071</id>
	<title>Re:Authorize.Net did have a backup</title>
	<author>Anonymous</author>
	<datestamp>1246651140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>What, was the backup data center on the floor directly below the primary data center?
<br> <br>
If I had to guess, either they did something that stupid or they didn't properly test their failover procedures or their backup data center, and either one or both of those things turned out to be inadequate.</htmltext>
<tokenext>What , was the backup data center on the floor directly below the primary data center ?
If I had to guess , either they did something that stupid or they did n't properly test their failover procedures or their backup data center , and either one or both of those things turned out to be inadequate .</tokentext>
<sentencetext>What, was the backup data center on the floor directly below the primary data center?
If I had to guess, either they did something that stupid or they didn't properly test their failover procedures or their backup data center, and either one or both of those things turned out to be inadequate.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573461</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573753</id>
	<title>Re:Heh</title>
	<author>Nutria</author>
	<datestamp>1246648740000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>there was a failure in the main/generator transfer switch which resulted in a fire. The sprinkler system activated.</i></p><p>Where I work, the D.C. is in a sub-level basement.  One day a few years ago, a dim-wit plumber was brazing a pipe with a propane torch, and swung it too close to a sprinkler head.</p><p>Sprinkler went off and water did what it does: flow downhill, eventually pouring into the D.C., right onto the SAN storing "my" database...</p><p>We were down for a few days.  People couldn't access the web site or IVR, but fortunately it happened over a weekend, so the store-front operations weren't totally affected.  Also, the system is part of an "asynchronously buffered" stove pipe, so operations "in front" of the downed machine just kept on processing.</p></htmltext>
<tokenext>there was a failure in the main/generator transfer switch which resulted in a fire .
The sprinkler system activated.Where I work , the D.C. is in a sub-level basement .
One day a few years ago , a dim-wit plumber was brazing a pipe with a propane torch , and swung it too close to a sprinkler head.Sprinkler went off and water did what it does : flow downhill , eventually pouring into the D.C. , right onto the SAN storing " my " database...We were down for a few days .
People could n't access the web site or IVR , but fortunately it happened over a weekend , so the store-front operations were n't totally affected .
Also , the system is part of an " asynchronously buffered " stove pipe , so operations " in front " of the downed machine just kept on processing .</tokentext>
<sentencetext>there was a failure in the main/generator transfer switch which resulted in a fire.
The sprinkler system activated.Where I work, the D.C. is in a sub-level basement.
One day a few years ago, a dim-wit plumber was brazing a pipe with a propane torch, and swung it too close to a sprinkler head.Sprinkler went off and water did what it does: flow downhill, eventually pouring into the D.C., right onto the SAN storing "my" database...We were down for a few days.
People couldn't access the web site or IVR, but fortunately it happened over a weekend, so the store-front operations weren't totally affected.
Also, the system is part of an "asynchronously buffered" stove pipe, so operations "in front" of the downed machine just kept on processing.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573637</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574175</id>
	<title>Local Seattle coverage:</title>
	<author>icebike</author>
	<datestamp>1246651980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><a href="http://www.seattlepi.com/local/6420ap\_wa\_fisher\_plaza\_fire.html?source=mypi" title="seattlepi.com">http://www.seattlepi.com/local/6420ap\_wa\_fisher\_plaza\_fire.html?source=mypi</a> [seattlepi.com]</p><p><a href="http://seattletimes.nwsource.com/html/localnews/2009415646\_webfisherplaza04.html" title="nwsource.com">http://seattletimes.nwsource.com/html/localnews/2009415646\_webfisherplaza04.html</a> [nwsource.com]</p></htmltext>
<tokenext>http : //www.seattlepi.com/local/6420ap \ _wa \ _fisher \ _plaza \ _fire.html ? source = mypi [ seattlepi.com ] http : //seattletimes.nwsource.com/html/localnews/2009415646 \ _webfisherplaza04.html [ nwsource.com ]</tokentext>
<sentencetext>http://www.seattlepi.com/local/6420ap\_wa\_fisher\_plaza\_fire.html?source=mypi [seattlepi.com]http://seattletimes.nwsource.com/html/localnews/2009415646\_webfisherplaza04.html [nwsource.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573637</id>
	<title>Re:Heh</title>
	<author>tearmeapart</author>
	<datestamp>1246647900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>More information is available from the NANOG (North American Network Operator's Group) list: <a href="http://comments.gmane.org/gmane.org.operators.nanog/65992" title="gmane.org" rel="nofollow">http://comments.gmane.org/gmane.org.operators.nanog/65992</a> [gmane.org] .</p><p>Excerpt:<br>"<br>Fisher Plaza, a self-styled carrier hotel in Seattle, and home to multiple<br>datacenter and colocation providers, has had a major issue in one of its<br>buildings late last night, early this morning.<br>The best information I am aware of is that there was a failure in the<br>main/generator transfer switch which resulted in a fire.  The sprinkler<br>system activated.  From speaking to the fire battalion chief, I am under the<br>impression that Seattle Fire did use water on the fire as well, but I am<br>unsure of this.<br>"</p><p>(Btw: Water + Lots of electricity = not good. I bet the electricity got turned off.)</p><p>I would copy and paste the rest with reference, but people are posting more details as they come.</p></htmltext>
<tokenext>More information is available from the NANOG ( North American Network Operator 's Group ) list : http : //comments.gmane.org/gmane.org.operators.nanog/65992 [ gmane.org ] .Excerpt : " Fisher Plaza , a self-styled carrier hotel in Seattle , and home to multipledatacenter and colocation providers , has had a major issue in one of itsbuildings late last night , early this morning.The best information I am aware of is that there was a failure in themain/generator transfer switch which resulted in a fire .
The sprinklersystem activated .
From speaking to the fire battalion chief , I am under theimpression that Seattle Fire did use water on the fire as well , but I amunsure of this .
" ( Btw : Water + Lots of electricity = not good .
I bet the electricity got turned off .
) I would copy and paste the rest with reference , but people are posting more details as they come .</tokentext>
<sentencetext>More information is available from the NANOG (North American Network Operator's Group) list: http://comments.gmane.org/gmane.org.operators.nanog/65992 [gmane.org] .Excerpt:"Fisher Plaza, a self-styled carrier hotel in Seattle, and home to multipledatacenter and colocation providers, has had a major issue in one of itsbuildings late last night, early this morning.The best information I am aware of is that there was a failure in themain/generator transfer switch which resulted in a fire.
The sprinklersystem activated.
From speaking to the fire battalion chief, I am under theimpression that Seattle Fire did use water on the fire as well, but I amunsure of this.
"(Btw: Water + Lots of electricity = not good.
I bet the electricity got turned off.
)I would copy and paste the rest with reference, but people are posting more details as they come.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573147</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28577983</id>
	<title>Re:Geocaching.com too</title>
	<author>dickens</author>
	<datestamp>1246645860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Still down here at 1:30 EDT Saturday.  They could at least have done an off-site DNS.  Weak!</p></htmltext>
<tokenext>Still down here at 1 : 30 EDT Saturday .
They could at least have done an off-site DNS .
Weak !</tokentext>
<sentencetext>Still down here at 1:30 EDT Saturday.
They could at least have done an off-site DNS.
Weak!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573555</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574373</id>
	<title>Re:Failover Planning (and this broke FiOS too)</title>
	<author>brianc</author>
	<datestamp>1246653420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Best: Eliminate single points of failure...</p> </div><p>Earth is a single point of failure.</p></div>
	</htmltext>
<tokenext>Best : Eliminate single points of failure... Earth is a single point of failure .</tokentext>
<sentencetext>Best: Eliminate single points of failure... Earth is a single point of failure.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573285</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829</id>
	<title>sloppy engineering</title>
	<author>Anonymous</author>
	<datestamp>1246649220000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>1</modscore>
	<htmltext><p> <i>"Our current estimate for re-establishing Bing Travel functionality is 5pm <b>PST</b>," says a notice at Bing</i> </p><p>When someone in a technical role screws up a timezone designation, for me that is always a red flag that they are sloppy with facts, and I need to closely watch their other decisions, actions and statements, because they may be in over their head.</p></htmltext>
<tokenext>" Our current estimate for re-establishing Bing Travel functionality is 5pm PST , " says a notice at Bing When someone in a technical role screws up a timezone designation , for me that is always a red flag that they are sloppy with facts , and I need to closely watch their other decisions , actions and statements , because they may be in over their head .</tokentext>
<sentencetext> "Our current estimate for re-establishing Bing Travel functionality is 5pm PST," says a notice at Bing When someone in a technical role screws up a timezone designation, for me that is always a red flag that they are sloppy with facts, and I need to closely watch their other decisions, actions and statements, because they may be in over their head.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574461</id>
	<title>Re:Heads will roll (hopefully)</title>
	<author>batquux</author>
	<datestamp>1246654260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>it would require a terrorist attack on New York PLUS an earthquake in San Francisco to knock us offline.</p></div><p>Which is all moot since you're using authorize.net as a payment gateway.<nobr> <wbr></nobr>;)</p></div>
	</htmltext>
<tokenext>it would require a terrorist attack on New York PLUS an earthquake in San Francisco to knock us offline.Which is all moot since you 're using authorize.net as a payment gateway .
; )</tokentext>
<sentencetext>it would require a terrorist attack on New York PLUS an earthquake in San Francisco to knock us offline.Which is all moot since you're using authorize.net as a payment gateway.
;)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573201</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573329</id>
	<title>It's mindboggling ...</title>
	<author>SlashDev</author>
	<datestamp>1246645980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>... that authorize.net does not have a failover site.</htmltext>
<tokenext>... that authorize.net does not have a failover site .</tokentext>
<sentencetext>... that authorize.net does not have a failover site.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574119</id>
	<title>Re:sloppy engineering</title>
	<author>eln</author>
	<datestamp>1246651500000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>Focusing on something that 99\% of us screw up at one point or another, particularly when our primary focus at the time is probably getting the service back online rather than checking the calendar to see if it's Daylight Saving Time or not, for me is always a red flag that you're an insufferable pedant.</htmltext>
<tokenext>Focusing on something that 99 \ % of us screw up at one point or another , particularly when our primary focus at the time is probably getting the service back online rather than checking the calendar to see if it 's Daylight Saving Time or not , for me is always a red flag that you 're an insufferable pedant .</tokentext>
<sentencetext>Focusing on something that 99\% of us screw up at one point or another, particularly when our primary focus at the time is probably getting the service back online rather than checking the calendar to see if it's Daylight Saving Time or not, for me is always a red flag that you're an insufferable pedant.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573305</id>
	<title>There should be an international backup day</title>
	<author>Anonymous</author>
	<datestamp>1246645800000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Where everyone tests their backups and failovers, because when the crap hits the fan for real everyone just sticks their head in the sand and then blames a third party post mortem</p></htmltext>
<tokenext>Where everyone tests their backups and failovers , because when the crap hits the fan for real everyone just sticks their head in the sand and then blames a third party post mortem</tokentext>
<sentencetext>Where everyone tests their backups and failovers, because when the crap hits the fan for real everyone just sticks their head in the sand and then blames a third party post mortem</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573157</id>
	<title>No Carr....</title>
	<author>BeerCat</author>
	<datestamp>1246645020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Hmm. Power outage stops<nobr> <wbr></nobr>/. posts. News at 11</p></htmltext>
<tokenext>Hmm .
Power outage stops / .
posts. News at 11</tokentext>
<sentencetext>Hmm.
Power outage stops /.
posts. News at 11</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573441</id>
	<title>Button pusher did it</title>
	<author>Anonymous</author>
	<datestamp>1246646700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This is a common problem in this datacenter.  The red candy like emergency power shut off button is located right by the exit door.  Noobs think it is the door release.</p></htmltext>
<tokenext>This is a common problem in this datacenter .
The red candy like emergency power shut off button is located right by the exit door .
Noobs think it is the door release .</tokentext>
<sentencetext>This is a common problem in this datacenter.
The red candy like emergency power shut off button is located right by the exit door.
Noobs think it is the door release.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28578777</id>
	<title>Re:Geocaching.com too</title>
	<author>dwywit</author>
	<datestamp>1246701360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>My wife's going nuts. She asked me "what happens when it comes back online and a bazillion geocachers start hitting the site?</htmltext>
<tokenext>My wife 's going nuts .
She asked me " what happens when it comes back online and a bazillion geocachers start hitting the site ?</tokentext>
<sentencetext>My wife's going nuts.
She asked me "what happens when it comes back online and a bazillion geocachers start hitting the site?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573555</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574179</id>
	<title>Re:sloppy engineering</title>
	<author>Phroggy</author>
	<datestamp>1246651980000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p> <i>"Our current estimate for re-establishing Bing Travel functionality is 5pm <b>PST</b>," says a notice at Bing</i> </p><p>When someone in a technical role screws up a timezone designation, for me that is always a red flag that they are sloppy with facts, and I need to closely watch their other decisions, actions and statements, because they may be in over their head.</p></div><p>It's quite likely that this message was not posted by somebody in a technical role, but a managerial role.  The technical people may very well have just said "by 5:00" or possibly "by 5:00 Pacific Time", and whoever posted the notice on the web site (while the technical people were busy working on trying to fix things) added "PST" instead of "PDT".</p></div>
	</htmltext>
<tokenext>" Our current estimate for re-establishing Bing Travel functionality is 5pm PST , " says a notice at Bing When someone in a technical role screws up a timezone designation , for me that is always a red flag that they are sloppy with facts , and I need to closely watch their other decisions , actions and statements , because they may be in over their head.It 's quite likely that this message was not posted by somebody in a technical role , but a managerial role .
The technical people may very well have just said " by 5 : 00 " or possibly " by 5 : 00 Pacific Time " , and whoever posted the notice on the web site ( while the technical people were busy working on trying to fix things ) added " PST " instead of " PDT " .</tokentext>
<sentencetext> "Our current estimate for re-establishing Bing Travel functionality is 5pm PST," says a notice at Bing When someone in a technical role screws up a timezone designation, for me that is always a red flag that they are sloppy with facts, and I need to closely watch their other decisions, actions and statements, because they may be in over their head.It's quite likely that this message was not posted by somebody in a technical role, but a managerial role.
The technical people may very well have just said "by 5:00" or possibly "by 5:00 Pacific Time", and whoever posted the notice on the web site (while the technical people were busy working on trying to fix things) added "PST" instead of "PDT".
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576541</id>
	<title>Re:Failover Planning (and this broke FiOS too)</title>
	<author>bertoelcon</author>
	<datestamp>1246628040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p><div class="quote"><p>Best: Eliminate single points of failure...</p></div><p>Earth is a single point of failure.</p></div><p>Milky Way Galaxy is a single point of failure.</p></div>
	</htmltext>
<tokenext>Best : Eliminate single points of failure...Earth is a single point of failure.Milky Way Galaxy is a single point of failure .</tokentext>
<sentencetext>Best: Eliminate single points of failure...Earth is a single point of failure.Milky Way Galaxy is a single point of failure.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574373</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573251</id>
	<title>Also affecting Bing.com</title>
	<author>Cothol</author>
	<datestamp>1246645500000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Bing Travel servers are located in the same server hall. More info: http://isc.sans.org/diary.html?storyid=6721</p></htmltext>
<tokenext>Bing Travel servers are located in the same server hall .
More info : http : //isc.sans.org/diary.html ? storyid = 6721</tokentext>
<sentencetext>Bing Travel servers are located in the same server hall.
More info: http://isc.sans.org/diary.html?storyid=6721</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574679</id>
	<title>Re:sloppy engineering</title>
	<author>Anonymous</author>
	<datestamp>1246612560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Look, I'm not trying to troll....but, really?  You're ready to discard someone's entire team due to one person typed "PST" instead of "PDT"?  Until you brought it up, I didn't realize there was a difference.   I also work long-haul communications, but refer to Zulu as my main time zone... so maybe it's my sole ignorance.  But if you knew they meant Pacific, and the posters below knew you meant Pacific, and I knew it..... </p><p><nobr> <wbr></nobr>...is it really worth the "need to closely watch their other decisions..." etc?</p></htmltext>
<tokenext>Look , I 'm not trying to troll....but , really ?
You 're ready to discard someone 's entire team due to one person typed " PST " instead of " PDT " ?
Until you brought it up , I did n't realize there was a difference .
I also work long-haul communications , but refer to Zulu as my main time zone... so maybe it 's my sole ignorance .
But if you knew they meant Pacific , and the posters below knew you meant Pacific , and I knew it..... ...is it really worth the " need to closely watch their other decisions... " etc ?</tokentext>
<sentencetext>Look, I'm not trying to troll....but, really?
You're ready to discard someone's entire team due to one person typed "PST" instead of "PDT"?
Until you brought it up, I didn't realize there was a difference.
I also work long-haul communications, but refer to Zulu as my main time zone... so maybe it's my sole ignorance.
But if you knew they meant Pacific, and the posters below knew you meant Pacific, and I knew it.....  ...is it really worth the "need to closely watch their other decisions..." etc?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574945</id>
	<title>Wow...</title>
	<author>ThousandStars</author>
	<datestamp>1246614300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Adhost oversees two sites for my family's business: <a href="http://www.seliger.com/" title="seliger.com">http://www.seliger.com</a> [seliger.com] and <a href="http://blog.seliger.com/" title="seliger.com">http://blog.seliger.com</a> [seliger.com]. At least part of the Fisher Plaza data center seems to be up at the moment because seliger.com will load for me, while blog.seliger.com won't. When I figured this out a few hours ago, I sent an e-mail to Adhost and got this as part of the response:<blockquote><div><p>We have been advised by the building engineering team that they anticipate restoring power to the Plaza East building in plus or minus 4 hours.  We sincerely hope this is an accurate number and, if not, we will let you know as soon as we receive new information from the engineers.</p></div>
</blockquote><p>

Imagine my surprise at learning that the problem is big enough to make<nobr> <wbr></nobr>/.. Actually, what's even more surprising is the unplanned outage in the first place: I don't recall Adhost ever going down for this long, especially in the middle of the day.</p></div>
	</htmltext>
<tokenext>Adhost oversees two sites for my family 's business : http : //www.seliger.com [ seliger.com ] and http : //blog.seliger.com [ seliger.com ] .
At least part of the Fisher Plaza data center seems to be up at the moment because seliger.com will load for me , while blog.seliger.com wo n't .
When I figured this out a few hours ago , I sent an e-mail to Adhost and got this as part of the response : We have been advised by the building engineering team that they anticipate restoring power to the Plaza East building in plus or minus 4 hours .
We sincerely hope this is an accurate number and , if not , we will let you know as soon as we receive new information from the engineers .
Imagine my surprise at learning that the problem is big enough to make /.. Actually , what 's even more surprising is the unplanned outage in the first place : I do n't recall Adhost ever going down for this long , especially in the middle of the day .</tokentext>
<sentencetext>Adhost oversees two sites for my family's business: http://www.seliger.com [seliger.com] and http://blog.seliger.com [seliger.com].
At least part of the Fisher Plaza data center seems to be up at the moment because seliger.com will load for me, while blog.seliger.com won't.
When I figured this out a few hours ago, I sent an e-mail to Adhost and got this as part of the response:We have been advised by the building engineering team that they anticipate restoring power to the Plaza East building in plus or minus 4 hours.
We sincerely hope this is an accurate number and, if not, we will let you know as soon as we receive new information from the engineers.
Imagine my surprise at learning that the problem is big enough to make /.. Actually, what's even more surprising is the unplanned outage in the first place: I don't recall Adhost ever going down for this long, especially in the middle of the day.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573405</id>
	<title>Fisher Plaza is a disaster response center</title>
	<author>Anonymous</author>
	<datestamp>1246646460000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>Fisher Plaza is supposed to be a regional telecomm / communications / medical care hub for the Seattle area.  It was designed and built to *not* crash, even in a magnitude 9.5 quake.  Sounds like they've got work to do<nobr> <wbr></nobr>...</p></htmltext>
<tokenext>Fisher Plaza is supposed to be a regional telecomm / communications / medical care hub for the Seattle area .
It was designed and built to * not * crash , even in a magnitude 9.5 quake .
Sounds like they 've got work to do .. .</tokentext>
<sentencetext>Fisher Plaza is supposed to be a regional telecomm / communications / medical care hub for the Seattle area.
It was designed and built to *not* crash, even in a magnitude 9.5 quake.
Sounds like they've got work to do ...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28577567</id>
	<title>Re:Geocaching.com too</title>
	<author>ackthpt</author>
	<datestamp>1246640580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is the bummer of all bummers this weekend.  And me with a cache I'm about to hide.</p><p>Nope, not gonna tell.  It's a puzzle cache and no freebies!</p></htmltext>
<tokenext>This is the bummer of all bummers this weekend .
And me with a cache I 'm about to hide.Nope , not gon na tell .
It 's a puzzle cache and no freebies !</tokentext>
<sentencetext>This is the bummer of all bummers this weekend.
And me with a cache I'm about to hide.Nope, not gonna tell.
It's a puzzle cache and no freebies!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573555</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576651</id>
	<title>Re:According to KOMO news</title>
	<author>aaarrrgggh</author>
	<datestamp>1246629180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Fischer plaza is actually pretty robust of a site, and well compartementalized. The problem with most telecom hotels though is the battery plant is the main line of defense; generator and utility equipment are often located in the same room.</p><p>With Verizon, their HUB there should go 8 hours on battery in this type of failure while they are trying to coordinate with Aggrecco for a roll-up unit. Depending on timing and the fire department, they would expect a 6-8 hour outage.</p></htmltext>
<tokenext>Fischer plaza is actually pretty robust of a site , and well compartementalized .
The problem with most telecom hotels though is the battery plant is the main line of defense ; generator and utility equipment are often located in the same room.With Verizon , their HUB there should go 8 hours on battery in this type of failure while they are trying to coordinate with Aggrecco for a roll-up unit .
Depending on timing and the fire department , they would expect a 6-8 hour outage .</tokentext>
<sentencetext>Fischer plaza is actually pretty robust of a site, and well compartementalized.
The problem with most telecom hotels though is the battery plant is the main line of defense; generator and utility equipment are often located in the same room.With Verizon, their HUB there should go 8 hours on battery in this type of failure while they are trying to coordinate with Aggrecco for a roll-up unit.
Depending on timing and the fire department, they would expect a 6-8 hour outage.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573741</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575525</id>
	<title>Re:Geocaching.com too</title>
	<author>johannesg</author>
	<datestamp>1246618800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Geocachers of Slashdot unite!</p><p>Yesterday I almost broke my daily record with 42 finds, but I came home too late to do the logging. Today the site was down all day long. Well, tomorrow then...</p><p>As for KPexEA: great service!</p></htmltext>
<tokenext>Geocachers of Slashdot unite ! Yesterday I almost broke my daily record with 42 finds , but I came home too late to do the logging .
Today the site was down all day long .
Well , tomorrow then...As for KPexEA : great service !</tokentext>
<sentencetext>Geocachers of Slashdot unite!Yesterday I almost broke my daily record with 42 finds, but I came home too late to do the logging.
Today the site was down all day long.
Well, tomorrow then...As for KPexEA: great service!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573555</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573559</id>
	<title>Re:Failover Planning (and this broke FiOS too)</title>
	<author>Anonymous</author>
	<datestamp>1246647420000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>Not just FIOS it looks like, I was wondering why my DSL was offline.  Nearly all network services I would guess.</p></htmltext>
<tokenext>Not just FIOS it looks like , I was wondering why my DSL was offline .
Nearly all network services I would guess .</tokentext>
<sentencetext>Not just FIOS it looks like, I was wondering why my DSL was offline.
Nearly all network services I would guess.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573285</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573151</id>
	<title>Maybe they...</title>
	<author>Anonymous</author>
	<datestamp>1246644960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>...should switch to twitter to do all their authorizations.</p><p>I know I'd feel much safer if Ashton Kutcher was processing my credit card.</p></htmltext>
<tokenext>...should switch to twitter to do all their authorizations.I know I 'd feel much safer if Ashton Kutcher was processing my credit card .</tokentext>
<sentencetext>...should switch to twitter to do all their authorizations.I know I'd feel much safer if Ashton Kutcher was processing my credit card.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574053</id>
	<title>Re:System failure</title>
	<author>eln</author>
	<datestamp>1246650960000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>3: WEAK INFRASTRUCTRUCTURE</p> </div><p>It's good to see that you've provided redundancy for the "TRUC" part of your infrastructure, but I'm concerned about the rest of it.</p></div>
	</htmltext>
<tokenext>3 : WEAK INFRASTRUCTRUCTURE It 's good to see that you 've provided redundancy for the " TRUC " part of your infrastructure , but I 'm concerned about the rest of it .</tokentext>
<sentencetext>3: WEAK INFRASTRUCTRUCTURE It's good to see that you've provided redundancy for the "TRUC" part of your infrastructure, but I'm concerned about the rest of it.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573431</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576611</id>
	<title>affected me</title>
	<author>Rene S. Hollan</author>
	<datestamp>1246628700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I had to work today to find and fix a bug related to a particular external site... sure enough, our internet access was down.</p><p>Pfft! I had a copy of Barry on a linux box, tethered my BlackBerry, a bit of iptables magic, and I'm back online to test.</p></htmltext>
<tokenext>I had to work today to find and fix a bug related to a particular external site... sure enough , our internet access was down.Pfft !
I had a copy of Barry on a linux box , tethered my BlackBerry , a bit of iptables magic , and I 'm back online to test .</tokentext>
<sentencetext>I had to work today to find and fix a bug related to a particular external site... sure enough, our internet access was down.Pfft!
I had a copy of Barry on a linux box, tethered my BlackBerry, a bit of iptables magic, and I'm back online to test.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573395</id>
	<title>Re:Heh</title>
	<author>Anonymous</author>
	<datestamp>1246646460000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>It's interesting how many companies have assumed redundancy in place but never take the time to do proper testing. They figure that once a disaster happens, that everything will automatically work because their vendor or staff said so. To achieve true redundancy a company needs to do semi-frequent testing to ensure that everything is working properly. Authorize.net might have had what was assumed a redundant system in place, but once the disaster happen they soon realized their system wasn't designed or configured properly.  It is expensive and time consuming to test redundancy, let alone actually paying for the redundant equipment/staff/etc, but in times like this it shows how one gets their moneys worth in doing so.</p></htmltext>
<tokenext>It 's interesting how many companies have assumed redundancy in place but never take the time to do proper testing .
They figure that once a disaster happens , that everything will automatically work because their vendor or staff said so .
To achieve true redundancy a company needs to do semi-frequent testing to ensure that everything is working properly .
Authorize.net might have had what was assumed a redundant system in place , but once the disaster happen they soon realized their system was n't designed or configured properly .
It is expensive and time consuming to test redundancy , let alone actually paying for the redundant equipment/staff/etc , but in times like this it shows how one gets their moneys worth in doing so .</tokentext>
<sentencetext>It's interesting how many companies have assumed redundancy in place but never take the time to do proper testing.
They figure that once a disaster happens, that everything will automatically work because their vendor or staff said so.
To achieve true redundancy a company needs to do semi-frequent testing to ensure that everything is working properly.
Authorize.net might have had what was assumed a redundant system in place, but once the disaster happen they soon realized their system wasn't designed or configured properly.
It is expensive and time consuming to test redundancy, let alone actually paying for the redundant equipment/staff/etc, but in times like this it shows how one gets their moneys worth in doing so.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573147</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573235</id>
	<title>Backup data center was impacted too</title>
	<author>basementman</author>
	<datestamp>1246645380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><a href="http://twitter.com/AuthorizeNet/status/2455435020" title="twitter.com">http://twitter.com/AuthorizeNet/status/2455435020</a> [twitter.com]

Hopefully someone made an offsite backup as well.</htmltext>
<tokenext>http : //twitter.com/AuthorizeNet/status/2455435020 [ twitter.com ] Hopefully someone made an offsite backup as well .</tokentext>
<sentencetext>http://twitter.com/AuthorizeNet/status/2455435020 [twitter.com]

Hopefully someone made an offsite backup as well.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573461</id>
	<title>Authorize.Net did have a backup</title>
	<author>Anonymous</author>
	<datestamp>1246646760000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext>...except it failed as well. From their twitter:<br> <br>

"@gotwww The backup data center was impacted too. Don't have info as to why. The team is solely focused on getting us back up for now."</htmltext>
<tokenext>...except it failed as well .
From their twitter : " @ gotwww The backup data center was impacted too .
Do n't have info as to why .
The team is solely focused on getting us back up for now .
"</tokentext>
<sentencetext>...except it failed as well.
From their twitter: 

"@gotwww The backup data center was impacted too.
Don't have info as to why.
The team is solely focused on getting us back up for now.
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28584145</id>
	<title>Re:Failover Planning (and this broke FiOS too)</title>
	<author>Anonymous</author>
	<datestamp>1246723920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Verizon finally starts rolling FIOS out in Snohomish</p></div><p>Why don't you move out of Dumbfuck you dirtyass redneck? Stop whining.</p></div>
	</htmltext>
<tokenext>Verizon finally starts rolling FIOS out in SnohomishWhy do n't you move out of Dumbfuck you dirtyass redneck ?
Stop whining .</tokentext>
<sentencetext>Verizon finally starts rolling FIOS out in SnohomishWhy don't you move out of Dumbfuck you dirtyass redneck?
Stop whining.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576471</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574295</id>
	<title>Re:System failure</title>
	<author>supernova\_hq</author>
	<datestamp>1246652820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Isn't #3 a result of #4?</htmltext>
<tokenext>Is n't # 3 a result of # 4 ?</tokentext>
<sentencetext>Isn't #3 a result of #4?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573431</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573431</id>
	<title>System failure</title>
	<author>ErkDemon</author>
	<datestamp>1246646640000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>There are four main factors that can take a part of a society's key infrastructure offline.
<p> <b>1: ACTS OF GOD</b>
<br>Meteor strike, lightnight strike, extreme weather<nobr> <wbr></nobr>...

</p><p> <b>2: ACTS OF MALICE</b>
<br>War, terrorism, extortion, employee sabotage, criminal attacks<nobr> <wbr></nobr>...

</p><p> <b>3: WEAK INFRASTRUCTRUCTURE</b>
<br>Underpowered networks, inadequate UPS backups, skeleton staffing, the shaving of safety margins as an efficiency exercise, inadequate rate of replacing old hardware<nobr> <wbr></nobr>...

</p><p> <b>4: MANAGEMENT ARSINESS</b>
<br>This is when a problem starts, and the people in charge either don't know how to react, don't care, or prioritise face-saving over actual problem-solving. This happens when you get an outage, and instead of system management promptly calling all their critical clients to inform them, and warn them that there's maybe twenty minutes of UPS capacity in the routers if the system's not fixed by then, they instead cross their fingers and hope that things'll work out, and worry about what to tell the clients afterwards.
</p><p>
Fisher Plaza seems to have suffered from a case of #4 recently, so it's not surprising that they've gone down again. The first time should have been the wakeup call to show them that their human systems were in need of an overhaul. Without that overhaul, you're setting up a dynamic in which the second time it happens, things are even worse  (because now people are locked into defensive mode).
</p><p>
No matter how advanced your technological systems, if the people running it have the wrong mindset, you're gonna go down. And when you go down, you're gonna go down far far harder than necessary.</p></htmltext>
<tokenext>There are four main factors that can take a part of a society 's key infrastructure offline .
1 : ACTS OF GOD Meteor strike , lightnight strike , extreme weather .. . 2 : ACTS OF MALICE War , terrorism , extortion , employee sabotage , criminal attacks .. . 3 : WEAK INFRASTRUCTRUCTURE Underpowered networks , inadequate UPS backups , skeleton staffing , the shaving of safety margins as an efficiency exercise , inadequate rate of replacing old hardware .. . 4 : MANAGEMENT ARSINESS This is when a problem starts , and the people in charge either do n't know how to react , do n't care , or prioritise face-saving over actual problem-solving .
This happens when you get an outage , and instead of system management promptly calling all their critical clients to inform them , and warn them that there 's maybe twenty minutes of UPS capacity in the routers if the system 's not fixed by then , they instead cross their fingers and hope that things 'll work out , and worry about what to tell the clients afterwards .
Fisher Plaza seems to have suffered from a case of # 4 recently , so it 's not surprising that they 've gone down again .
The first time should have been the wakeup call to show them that their human systems were in need of an overhaul .
Without that overhaul , you 're setting up a dynamic in which the second time it happens , things are even worse ( because now people are locked into defensive mode ) .
No matter how advanced your technological systems , if the people running it have the wrong mindset , you 're gon na go down .
And when you go down , you 're gon na go down far far harder than necessary .</tokentext>
<sentencetext>There are four main factors that can take a part of a society's key infrastructure offline.
1: ACTS OF GOD
Meteor strike, lightnight strike, extreme weather ...

 2: ACTS OF MALICE
War, terrorism, extortion, employee sabotage, criminal attacks ...

 3: WEAK INFRASTRUCTRUCTURE
Underpowered networks, inadequate UPS backups, skeleton staffing, the shaving of safety margins as an efficiency exercise, inadequate rate of replacing old hardware ...

 4: MANAGEMENT ARSINESS
This is when a problem starts, and the people in charge either don't know how to react, don't care, or prioritise face-saving over actual problem-solving.
This happens when you get an outage, and instead of system management promptly calling all their critical clients to inform them, and warn them that there's maybe twenty minutes of UPS capacity in the routers if the system's not fixed by then, they instead cross their fingers and hope that things'll work out, and worry about what to tell the clients afterwards.
Fisher Plaza seems to have suffered from a case of #4 recently, so it's not surprising that they've gone down again.
The first time should have been the wakeup call to show them that their human systems were in need of an overhaul.
Without that overhaul, you're setting up a dynamic in which the second time it happens, things are even worse  (because now people are locked into defensive mode).
No matter how advanced your technological systems, if the people running it have the wrong mindset, you're gonna go down.
And when you go down, you're gonna go down far far harder than necessary.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573201</id>
	<title>Heads will roll (hopefully)</title>
	<author>Anonymous</author>
	<datestamp>1246645140000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It's absurd that a service provider like AuthorizeNet can be taken down by any single point of failure. I run a much, much smaller business and even we have our resources distributed widely enough that it would require a terrorist attack on New York PLUS an earthquake in San Francisco to knock us offline.</p></htmltext>
<tokenext>It 's absurd that a service provider like AuthorizeNet can be taken down by any single point of failure .
I run a much , much smaller business and even we have our resources distributed widely enough that it would require a terrorist attack on New York PLUS an earthquake in San Francisco to knock us offline .</tokentext>
<sentencetext>It's absurd that a service provider like AuthorizeNet can be taken down by any single point of failure.
I run a much, much smaller business and even we have our resources distributed widely enough that it would require a terrorist attack on New York PLUS an earthquake in San Francisco to knock us offline.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575389</id>
	<title>Re:sloppy engineering</title>
	<author>DerekLyons</author>
	<datestamp>1246617780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>When someone in a technical role screws up a timezone designation, for me that is always a red flag that they are sloppy with facts, and I need to closely watch their other decisions, actions and statements, because they may be in over their head.</p></div></blockquote><p>When someone is excessively pedantic for the sole reason of making his virtual penis larger and harder, I point and <i>laaaaaaaaaaugh</i>.<br>
&nbsp; <br>Seriously, get the fuck over yourself.  PST is a widely used and widely accepted descriptive term for the Pacific time zone.  For 99\% of the people, it doesn't matter whether it's actually PST or PDST.</p></div>
	</htmltext>
<tokenext>When someone in a technical role screws up a timezone designation , for me that is always a red flag that they are sloppy with facts , and I need to closely watch their other decisions , actions and statements , because they may be in over their head.When someone is excessively pedantic for the sole reason of making his virtual penis larger and harder , I point and laaaaaaaaaaugh .
  Seriously , get the fuck over yourself .
PST is a widely used and widely accepted descriptive term for the Pacific time zone .
For 99 \ % of the people , it does n't matter whether it 's actually PST or PDST .</tokentext>
<sentencetext>When someone in a technical role screws up a timezone designation, for me that is always a red flag that they are sloppy with facts, and I need to closely watch their other decisions, actions and statements, because they may be in over their head.When someone is excessively pedantic for the sole reason of making his virtual penis larger and harder, I point and laaaaaaaaaaugh.
  Seriously, get the fuck over yourself.
PST is a widely used and widely accepted descriptive term for the Pacific time zone.
For 99\% of the people, it doesn't matter whether it's actually PST or PDST.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573247</id>
	<title>Slow news day!</title>
	<author>Another AC</author>
	<datestamp>1246645500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>News at 11...</p><p>tomorrow.</p></htmltext>
<tokenext>News at 11...tomorrow .</tokentext>
<sentencetext>News at 11...tomorrow.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575275</id>
	<title>Huge portable generator arrives at Fisher Plaza</title>
	<author>KPexEA</author>
	<datestamp>1246616820000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><a href="http://twitpic.com/966ee" title="twitpic.com" rel="nofollow">http://twitpic.com/966ee</a> [twitpic.com]</htmltext>
<tokenext>http : //twitpic.com/966ee [ twitpic.com ]</tokentext>
<sentencetext>http://twitpic.com/966ee [twitpic.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573285</id>
	<title>Failover Planning (and this broke FiOS too)</title>
	<author>Cysgod</author>
	<datestamp>1246645740000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>Apparently Verizon has a single point of failure for much of its FiOS for the metro areas of Western Washington state in this building as well so the FiOS customers are offline as well right now.</p><ul> <li> <b>Clownshoes</b>: Have no failover plan and be singly homed.</li><li> <b>Meh</b>: Have a failover plan.</li><li> <b>Good</b>: Have a failover plan that requires humans and exercise it regularly.</li><li> <b>Better</b>: Have a failover plan that is automated and exercise it regularly.</li><li> <b>Best</b>: Eliminate single points of failure so failover is turning off the flake or fail and going back to drinking a beer.</li></ul><p>Hot/Hot is always a more ideal solution than Hot/Warm or Hot/Cold for disaster recovery (and increasing equipment utilization/ROI), and this event demonstrates why.</p></htmltext>
<tokenext>Apparently Verizon has a single point of failure for much of its FiOS for the metro areas of Western Washington state in this building as well so the FiOS customers are offline as well right now .
Clownshoes : Have no failover plan and be singly homed .
Meh : Have a failover plan .
Good : Have a failover plan that requires humans and exercise it regularly .
Better : Have a failover plan that is automated and exercise it regularly .
Best : Eliminate single points of failure so failover is turning off the flake or fail and going back to drinking a beer.Hot/Hot is always a more ideal solution than Hot/Warm or Hot/Cold for disaster recovery ( and increasing equipment utilization/ROI ) , and this event demonstrates why .</tokentext>
<sentencetext>Apparently Verizon has a single point of failure for much of its FiOS for the metro areas of Western Washington state in this building as well so the FiOS customers are offline as well right now.
Clownshoes: Have no failover plan and be singly homed.
Meh: Have a failover plan.
Good: Have a failover plan that requires humans and exercise it regularly.
Better: Have a failover plan that is automated and exercise it regularly.
Best: Eliminate single points of failure so failover is turning off the flake or fail and going back to drinking a beer.Hot/Hot is always a more ideal solution than Hot/Warm or Hot/Cold for disaster recovery (and increasing equipment utilization/ROI), and this event demonstrates why.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574429</id>
	<title>Re:Authorize.Net did have a backup</title>
	<author>ZorinLynx</author>
	<datestamp>1246653840000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>Sometimes folks set up a redundant system and forget to make one key piece redundant.</p><p>Example: A server rack with two UPS systems. Each server has two power cords, one going to each UPS.. but the switch everything is plugged into only has one power input, so it's connected to UPS A.</p><p>Power blinks and UPS A decides to shit itself. Rack goes down, even though all the machines are up, because the network switch loses power.</p><p>Solution? An auto switching power Y-cable with two inputs, and one output. But 80\% of people will be lazy and not bother. Oops.</p><p>Happens all the time; I see it everywhere.</p></htmltext>
<tokenext>Sometimes folks set up a redundant system and forget to make one key piece redundant.Example : A server rack with two UPS systems .
Each server has two power cords , one going to each UPS.. but the switch everything is plugged into only has one power input , so it 's connected to UPS A.Power blinks and UPS A decides to shit itself .
Rack goes down , even though all the machines are up , because the network switch loses power.Solution ?
An auto switching power Y-cable with two inputs , and one output .
But 80 \ % of people will be lazy and not bother .
Oops.Happens all the time ; I see it everywhere .</tokentext>
<sentencetext>Sometimes folks set up a redundant system and forget to make one key piece redundant.Example: A server rack with two UPS systems.
Each server has two power cords, one going to each UPS.. but the switch everything is plugged into only has one power input, so it's connected to UPS A.Power blinks and UPS A decides to shit itself.
Rack goes down, even though all the machines are up, because the network switch loses power.Solution?
An auto switching power Y-cable with two inputs, and one output.
But 80\% of people will be lazy and not bother.
Oops.Happens all the time; I see it everywhere.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573461</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574761</id>
	<title>Fisher Plaza?</title>
	<author>Anonymous</author>
	<datestamp>1246613220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Sounds more like Fischer Price.

Glad that none of customers rely on Authorize.net.</htmltext>
<tokenext>Sounds more like Fischer Price .
Glad that none of customers rely on Authorize.net .</tokentext>
<sentencetext>Sounds more like Fischer Price.
Glad that none of customers rely on Authorize.net.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575151</id>
	<title>Not the first time</title>
	<author>Anonymous</author>
	<datestamp>1246615860000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is the 2nd fire since 2008... Apparently Internap rent the power from the building so they have no control over the quality/maintenance of these generators and UPSes.</p><p>The fire which started around 11:30 PM (or maybe earlier, but first signs were around that time) damaged badly some of the electrical risers, so they are unable to get power back so some parts of the datacenter. According to their last update they're getting external generators to bypass the damaged equipment and power up the rest of the datacenter, which should be completed late this evening... At best it's going to be a nearly full day outage for some of their customers.</p></htmltext>
<tokenext>This is the 2nd fire since 2008... Apparently Internap rent the power from the building so they have no control over the quality/maintenance of these generators and UPSes.The fire which started around 11 : 30 PM ( or maybe earlier , but first signs were around that time ) damaged badly some of the electrical risers , so they are unable to get power back so some parts of the datacenter .
According to their last update they 're getting external generators to bypass the damaged equipment and power up the rest of the datacenter , which should be completed late this evening... At best it 's going to be a nearly full day outage for some of their customers .</tokentext>
<sentencetext>This is the 2nd fire since 2008... Apparently Internap rent the power from the building so they have no control over the quality/maintenance of these generators and UPSes.The fire which started around 11:30 PM (or maybe earlier, but first signs were around that time) damaged badly some of the electrical risers, so they are unable to get power back so some parts of the datacenter.
According to their last update they're getting external generators to bypass the damaged equipment and power up the rest of the datacenter, which should be completed late this evening... At best it's going to be a nearly full day outage for some of their customers.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573741</id>
	<title>According to KOMO news</title>
	<author>PPH</author>
	<datestamp>1246648620000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>... who's broadcast facilities reside in this building (they were broadcasting from a park on Queen Anne hill this morning), it was due to a transformer vault fire. The resulting sprinkler operation rendered their backup generator inoperable.
</p><p>Being in the power biz, this sort of thing is to be expected in typical office buildings. Sometimes the power goes out. Live with it. What really puzzles me is how someone can take such a structure, install a raised floor and some big A/C units on the roof and sell it as a data center. This kind of crap goes on all the time, as I've seen purpose built data centers go down for single point failures.</p></htmltext>
<tokenext>... who 's broadcast facilities reside in this building ( they were broadcasting from a park on Queen Anne hill this morning ) , it was due to a transformer vault fire .
The resulting sprinkler operation rendered their backup generator inoperable .
Being in the power biz , this sort of thing is to be expected in typical office buildings .
Sometimes the power goes out .
Live with it .
What really puzzles me is how someone can take such a structure , install a raised floor and some big A/C units on the roof and sell it as a data center .
This kind of crap goes on all the time , as I 've seen purpose built data centers go down for single point failures .</tokentext>
<sentencetext>... who's broadcast facilities reside in this building (they were broadcasting from a park on Queen Anne hill this morning), it was due to a transformer vault fire.
The resulting sprinkler operation rendered their backup generator inoperable.
Being in the power biz, this sort of thing is to be expected in typical office buildings.
Sometimes the power goes out.
Live with it.
What really puzzles me is how someone can take such a structure, install a raised floor and some big A/C units on the roof and sell it as a data center.
This kind of crap goes on all the time, as I've seen purpose built data centers go down for single point failures.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573147</id>
	<title>Heh</title>
	<author>MightyMartian</author>
	<datestamp>1246644900000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Redundancy ain't just a river in Egypt.</p></htmltext>
<tokenext>Redundancy ai n't just a river in Egypt .</tokentext>
<sentencetext>Redundancy ain't just a river in Egypt.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573555</id>
	<title>Geocaching.com too</title>
	<author>dickens</author>
	<datestamp>1246647360000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>And on a holiday. Bummer.<nobr> <wbr></nobr>:(</p></htmltext>
<tokenext>And on a holiday .
Bummer. : (</tokentext>
<sentencetext>And on a holiday.
Bummer. :(</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576471</id>
	<title>Re:Failover Planning (and this broke FiOS too)</title>
	<author>Blakey Rat</author>
	<datestamp>1246627440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'll really be concerned about that in 2087 when Verizon finally starts rolling FIOS out in Snohomish. Christ, we had DSL in 1997, what the hell do you have to do to get FIOS? Sacrifice a virgin? Then to pour lemon juice on the wound, they SATURATE the airspace, billboards, advertising on mass transit (especially buses that go to Snohomish!) telling people to order FIOS. Meanwhile I know hicks in Louisiana who can't even spell the word "fiber" who have it in their dirt-floored one-room shacks.</p><p>Fucking Verizon.</p></htmltext>
<tokenext>I 'll really be concerned about that in 2087 when Verizon finally starts rolling FIOS out in Snohomish .
Christ , we had DSL in 1997 , what the hell do you have to do to get FIOS ?
Sacrifice a virgin ?
Then to pour lemon juice on the wound , they SATURATE the airspace , billboards , advertising on mass transit ( especially buses that go to Snohomish !
) telling people to order FIOS .
Meanwhile I know hicks in Louisiana who ca n't even spell the word " fiber " who have it in their dirt-floored one-room shacks.Fucking Verizon .</tokentext>
<sentencetext>I'll really be concerned about that in 2087 when Verizon finally starts rolling FIOS out in Snohomish.
Christ, we had DSL in 1997, what the hell do you have to do to get FIOS?
Sacrifice a virgin?
Then to pour lemon juice on the wound, they SATURATE the airspace, billboards, advertising on mass transit (especially buses that go to Snohomish!
) telling people to order FIOS.
Meanwhile I know hicks in Louisiana who can't even spell the word "fiber" who have it in their dirt-floored one-room shacks.Fucking Verizon.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573285</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28584145
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576471
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573285
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574053
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573431
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576493
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574119
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574309
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573441
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573919
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575271
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28577983
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573555
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574461
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573201
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574679
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573481
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573147
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573559
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573285
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576651
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573741
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573429
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573147
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28578777
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573555
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575389
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575525
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573555
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28577567
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573555
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28578819
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573285
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573395
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573147
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576541
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574373
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573285
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574429
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573461
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573753
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573637
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573147
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574071
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573461
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_03_1637228_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574295
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573431
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573251
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575275
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574945
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573741
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576651
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573405
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573147
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573637
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573753
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573395
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573481
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573429
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574761
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573329
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573555
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575525
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28578777
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28577567
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28577983
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573461
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574429
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574071
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573829
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575389
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28575271
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574679
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574119
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576493
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574179
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573919
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573235
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573285
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28578819
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574373
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576541
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28576471
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28584145
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573559
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573431
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574295
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574053
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573441
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574309
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_03_1637228.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28573201
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_03_1637228.28574461
</commentlist>
</conversation>
