<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_11_25_1448218</id>
	<title>Moving Decimal Bug Loses Money</title>
	<author>CmdrTaco</author>
	<datestamp>1259161980000</datestamp>
	<htmltext>mario.m7 writes <i>"Poste Italiane, the Italian postal service, suffered yesterday from an abnormal computation in ATM and credit card operations, since the decimal comma was not taken into account. The whole sum was therefore multiplied by 100, resulting in a 115,00 Euro transaction being debited as 11.500 Euro!  Thousands of accounts are <a href="http://translate.google.com/translate?js=y&amp;prev=\_t&amp;hl=en&amp;ie=UTF-8&amp;u=http\%3A\%2F\%2Fwww.ilsole24ore.com\%2Fart\%2FSoleOnLine4\%2FItalia\%2F2009\%2F11\%2Fposte-italiane-disguido-addebiti-gonfiati.shtml\%3Fuuid\%3Dd6c6444e-d9c0-11de-a8b5-39ada1513d27\%26DocRulesView\%3DLibero&amp;sl=it&amp;tl=en">deep in the red and locked</a> (link pumped through translator), so that no more operations are possible. Poste Italiane is gradually recovering the problem, fixing the error and re-crediting the sum debited in excess. Consumer associations have offered support to clients in case this lasts longer and causes damage."</i></htmltext>
<tokenext>mario.m7 writes " Poste Italiane , the Italian postal service , suffered yesterday from an abnormal computation in ATM and credit card operations , since the decimal comma was not taken into account .
The whole sum was therefore multiplied by 100 , resulting in a 115,00 Euro transaction being debited as 11.500 Euro !
Thousands of accounts are deep in the red and locked ( link pumped through translator ) , so that no more operations are possible .
Poste Italiane is gradually recovering the problem , fixing the error and re-crediting the sum debited in excess .
Consumer associations have offered support to clients in case this lasts longer and causes damage .
"</tokentext>
<sentencetext>mario.m7 writes "Poste Italiane, the Italian postal service, suffered yesterday from an abnormal computation in ATM and credit card operations, since the decimal comma was not taken into account.
The whole sum was therefore multiplied by 100, resulting in a 115,00 Euro transaction being debited as 11.500 Euro!
Thousands of accounts are deep in the red and locked (link pumped through translator), so that no more operations are possible.
Poste Italiane is gradually recovering the problem, fixing the error and re-crediting the sum debited in excess.
Consumer associations have offered support to clients in case this lasts longer and causes damage.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227308</id>
	<title>Re:Happened to me recently</title>
	<author>Monkeedude1212</author>
	<datestamp>1257184140000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>You've got to handle that problem at the application layer, preferably as soon as possible.</p><p>Before converting it to a double or float point or whatever you are using, you have to do some data verification. Similarily, you wouldn't want someone putting in "ABC.75" dollars, because that can't be parsed, you have to handle all those scenarios. A try-catch will work for the obvious ones (like I stated) but there are some simple tips to help with the , and . translation done by the OS's.</p><p>All of it is done by handling it while its a string, before it goes to a numeric data class. You check if there are any Comma's. If so, how many characters follow the comma. 2 would be like 1,00 (one dollar) , and 3 would be like 1,000 (one thousand dollars). In no case in English formatting should a comma be followed by any less than 3 characters, and assuming they are inputing their information properly, French users won't have any more than 2.</p><p>Similarily, you apply the exact same logic for periods, just vice versa. This will allow your program to determine which standard is being used independant of operating system OS. Once you've nailed that, you can change comma's to decimals or what not depending on which case you are in, and then converting it to your double from there.</p><p>You should be able to test it on your own at least a few times, to make sure it works, then it SHOULD work across all OS languages.</p><p>The beautiful part about it is that this only needs to be done for Data Input, not Data output, since the OS (should) handles the display of Ints and other numeric Datatypes, when your users go to pull up a workorder - it should display in whatever standard they are using on their computer.</p></htmltext>
<tokenext>You 've got to handle that problem at the application layer , preferably as soon as possible.Before converting it to a double or float point or whatever you are using , you have to do some data verification .
Similarily , you would n't want someone putting in " ABC.75 " dollars , because that ca n't be parsed , you have to handle all those scenarios .
A try-catch will work for the obvious ones ( like I stated ) but there are some simple tips to help with the , and .
translation done by the OS 's.All of it is done by handling it while its a string , before it goes to a numeric data class .
You check if there are any Comma 's .
If so , how many characters follow the comma .
2 would be like 1,00 ( one dollar ) , and 3 would be like 1,000 ( one thousand dollars ) .
In no case in English formatting should a comma be followed by any less than 3 characters , and assuming they are inputing their information properly , French users wo n't have any more than 2.Similarily , you apply the exact same logic for periods , just vice versa .
This will allow your program to determine which standard is being used independant of operating system OS .
Once you 've nailed that , you can change comma 's to decimals or what not depending on which case you are in , and then converting it to your double from there.You should be able to test it on your own at least a few times , to make sure it works , then it SHOULD work across all OS languages.The beautiful part about it is that this only needs to be done for Data Input , not Data output , since the OS ( should ) handles the display of Ints and other numeric Datatypes , when your users go to pull up a workorder - it should display in whatever standard they are using on their computer .</tokentext>
<sentencetext>You've got to handle that problem at the application layer, preferably as soon as possible.Before converting it to a double or float point or whatever you are using, you have to do some data verification.
Similarily, you wouldn't want someone putting in "ABC.75" dollars, because that can't be parsed, you have to handle all those scenarios.
A try-catch will work for the obvious ones (like I stated) but there are some simple tips to help with the , and .
translation done by the OS's.All of it is done by handling it while its a string, before it goes to a numeric data class.
You check if there are any Comma's.
If so, how many characters follow the comma.
2 would be like 1,00 (one dollar) , and 3 would be like 1,000 (one thousand dollars).
In no case in English formatting should a comma be followed by any less than 3 characters, and assuming they are inputing their information properly, French users won't have any more than 2.Similarily, you apply the exact same logic for periods, just vice versa.
This will allow your program to determine which standard is being used independant of operating system OS.
Once you've nailed that, you can change comma's to decimals or what not depending on which case you are in, and then converting it to your double from there.You should be able to test it on your own at least a few times, to make sure it works, then it SHOULD work across all OS languages.The beautiful part about it is that this only needs to be done for Data Input, not Data output, since the OS (should) handles the display of Ints and other numeric Datatypes, when your users go to pull up a workorder - it should display in whatever standard they are using on their computer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227044</id>
	<title>Re:Periods and commas.</title>
	<author>thickdiick</author>
	<datestamp>1257182700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>In most european languages, it's easier to say "x decimal places after the comma" than "x decimal places after the period."
I'm reasonably certain that's part of the reason. And i recognize that Americans wanted to distance themselves from the British after their revolt, resulting in somewhat different grammar conventions and spellings, so perhaps the Americans wanted to change this as well?<br>I greatly prefer the decimal point as a decimal point, as opposed to the comma.</htmltext>
<tokenext>In most european languages , it 's easier to say " x decimal places after the comma " than " x decimal places after the period .
" I 'm reasonably certain that 's part of the reason .
And i recognize that Americans wanted to distance themselves from the British after their revolt , resulting in somewhat different grammar conventions and spellings , so perhaps the Americans wanted to change this as well ? I greatly prefer the decimal point as a decimal point , as opposed to the comma .</tokentext>
<sentencetext>In most european languages, it's easier to say "x decimal places after the comma" than "x decimal places after the period.
"
I'm reasonably certain that's part of the reason.
And i recognize that Americans wanted to distance themselves from the British after their revolt, resulting in somewhat different grammar conventions and spellings, so perhaps the Americans wanted to change this as well?I greatly prefer the decimal point as a decimal point, as opposed to the comma.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226748</id>
	<title>Re:Periods and commas.</title>
	<author>Grygus</author>
	<datestamp>1257181320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>In matters of custom, the more universally recognized method is the right one.

Everyone knows what 1,054.65 means.  Some people do not know what the hell 12,56 is supposed to be.  Since confusion in financial transactions is good for nobody at all, the correct custom is in fact the former.  If you want to implement a new worldwide custom then that's fine but I suspect you will need a very good justification and not simply the desire to do something new.</htmltext>
<tokenext>In matters of custom , the more universally recognized method is the right one .
Everyone knows what 1,054.65 means .
Some people do not know what the hell 12,56 is supposed to be .
Since confusion in financial transactions is good for nobody at all , the correct custom is in fact the former .
If you want to implement a new worldwide custom then that 's fine but I suspect you will need a very good justification and not simply the desire to do something new .</tokentext>
<sentencetext>In matters of custom, the more universally recognized method is the right one.
Everyone knows what 1,054.65 means.
Some people do not know what the hell 12,56 is supposed to be.
Since confusion in financial transactions is good for nobody at all, the correct custom is in fact the former.
If you want to implement a new worldwide custom then that's fine but I suspect you will need a very good justification and not simply the desire to do something new.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227710</id>
	<title>Re:Good to be a programmer</title>
	<author>Anonymous</author>
	<datestamp>1257186000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Software engineering is a much harder problem than most traditional engineering. A lot more of the design has to be reinvented each time.</p><p>If you want to compare, it would be more appropriate to liken software development to designing a first of its kind mechanical system, such as the V-2 rocket.</p></htmltext>
<tokenext>Software engineering is a much harder problem than most traditional engineering .
A lot more of the design has to be reinvented each time.If you want to compare , it would be more appropriate to liken software development to designing a first of its kind mechanical system , such as the V-2 rocket .</tokentext>
<sentencetext>Software engineering is a much harder problem than most traditional engineering.
A lot more of the design has to be reinvented each time.If you want to compare, it would be more appropriate to liken software development to designing a first of its kind mechanical system, such as the V-2 rocket.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</id>
	<title>Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257179760000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>I never understood why the hell Europeans swap periods and commas. Grammatically it doesn't even make sense.</p><p>A period ends a sentence or statement, which to me should imply a whole number. A comma is simply a separator, used within sentences. So why would it be used to separate decimals?</p><p>It would be like writing a sentence this way:<br>I went to the supermarket to buy some cola. cabbages. and condoms,</p><p>Maybe there's a very good reason for it, but I don't see it.</p><p>Regarding the story on hand, that really sucks. I wonder if they will pull the same garbage as American banks where customers only have 60 days to report a problem otherwise nothing will be done. Whereas, if the bank screws up in your favor, they could go into your account 20 years from now and withdraw whatever extra money they gave you.</p></htmltext>
<tokenext>I never understood why the hell Europeans swap periods and commas .
Grammatically it does n't even make sense.A period ends a sentence or statement , which to me should imply a whole number .
A comma is simply a separator , used within sentences .
So why would it be used to separate decimals ? It would be like writing a sentence this way : I went to the supermarket to buy some cola .
cabbages. and condoms,Maybe there 's a very good reason for it , but I do n't see it.Regarding the story on hand , that really sucks .
I wonder if they will pull the same garbage as American banks where customers only have 60 days to report a problem otherwise nothing will be done .
Whereas , if the bank screws up in your favor , they could go into your account 20 years from now and withdraw whatever extra money they gave you .</tokentext>
<sentencetext>I never understood why the hell Europeans swap periods and commas.
Grammatically it doesn't even make sense.A period ends a sentence or statement, which to me should imply a whole number.
A comma is simply a separator, used within sentences.
So why would it be used to separate decimals?It would be like writing a sentence this way:I went to the supermarket to buy some cola.
cabbages. and condoms,Maybe there's a very good reason for it, but I don't see it.Regarding the story on hand, that really sucks.
I wonder if they will pull the same garbage as American banks where customers only have 60 days to report a problem otherwise nothing will be done.
Whereas, if the bank screws up in your favor, they could go into your account 20 years from now and withdraw whatever extra money they gave you.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230534</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257156120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>We, in France, don't use neither commas nor periods as thousands separators. We just add a space. We use a comma for decimals.</p><p>10 000,00&euro;. See? No problems.</p></htmltext>
<tokenext>We , in France , do n't use neither commas nor periods as thousands separators .
We just add a space .
We use a comma for decimals.10 000,00    .
See ? No problems .</tokentext>
<sentencetext>We, in France, don't use neither commas nor periods as thousands separators.
We just add a space.
We use a comma for decimals.10 000,00€.
See? No problems.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227078</id>
	<title>Re:For the most part.</title>
	<author>Anonymous</author>
	<datestamp>1257182880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It blows me away that some people really think string is the answer.   Seriously, I think you're sincere and not trolling.  And that makes me sad.</p><p>There have been many excellent approaches to storing higher precision, avoid float roundoff, etc around for decades, and none of those answers are "use a string" and they all work far far better than "use a string."  And yet, all the answers are in vain, because people just can't <em>learn</em> from the past.</p></htmltext>
<tokenext>It blows me away that some people really think string is the answer .
Seriously , I think you 're sincere and not trolling .
And that makes me sad.There have been many excellent approaches to storing higher precision , avoid float roundoff , etc around for decades , and none of those answers are " use a string " and they all work far far better than " use a string .
" And yet , all the answers are in vain , because people just ca n't learn from the past .</tokentext>
<sentencetext>It blows me away that some people really think string is the answer.
Seriously, I think you're sincere and not trolling.
And that makes me sad.There have been many excellent approaches to storing higher precision, avoid float roundoff, etc around for decades, and none of those answers are "use a string" and they all work far far better than "use a string.
"  And yet, all the answers are in vain, because people just can't learn from the past.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227744</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257186180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Lettuce generalize: Any version of any software, ever, localized = an infinity of shit. I speak as a programmer.</p></htmltext>
<tokenext>Lettuce generalize : Any version of any software , ever , localized = an infinity of shit .
I speak as a programmer .</tokentext>
<sentencetext>Lettuce generalize: Any version of any software, ever, localized = an infinity of shit.
I speak as a programmer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228388</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257189180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>&gt; A period ends a sentence or statement</p><p>The Americans get this wrong too.</p><p>A period of history is from the first day until the last.<br>A musical period is from its first note until the silence (or stop) that follows its last.<br>A school period is from the bell that indicates its start until the bell that indicates the next.</p><p>The period of a sentence (spoken) is from the start of its first sound, with brief silences (or stops) if required, until the full silence (or stop) indicates that it has ended.</p><p>In written form the brief silences (or stops) are indicated by ',' and the full stop is indicated by '.'.</p></htmltext>
<tokenext>&gt; A period ends a sentence or statementThe Americans get this wrong too.A period of history is from the first day until the last.A musical period is from its first note until the silence ( or stop ) that follows its last.A school period is from the bell that indicates its start until the bell that indicates the next.The period of a sentence ( spoken ) is from the start of its first sound , with brief silences ( or stops ) if required , until the full silence ( or stop ) indicates that it has ended.In written form the brief silences ( or stops ) are indicated by ', ' and the full stop is indicated by ' .
' .</tokentext>
<sentencetext>&gt; A period ends a sentence or statementThe Americans get this wrong too.A period of history is from the first day until the last.A musical period is from its first note until the silence (or stop) that follows its last.A school period is from the bell that indicates its start until the bell that indicates the next.The period of a sentence (spoken) is from the start of its first sound, with brief silences (or stops) if required, until the full silence (or stop) indicates that it has ended.In written form the brief silences (or stops) are indicated by ',' and the full stop is indicated by '.
'.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227504</id>
	<title>Re:Periods and commas.</title>
	<author>MartinSchou</author>
	<datestamp>1257185160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Like I said <a href="http://slashdot.org/comments.pl?sid=1457018&amp;cid=30227414" title="slashdot.org">elsewhere</a> [slashdot.org], I suspect this is more a matter of spoken language using comma rather than point. Especially because no-one says "two period five" in English. They say "two POINT five". The period just looks like a point.</p></htmltext>
<tokenext>Like I said elsewhere [ slashdot.org ] , I suspect this is more a matter of spoken language using comma rather than point .
Especially because no-one says " two period five " in English .
They say " two POINT five " .
The period just looks like a point .</tokentext>
<sentencetext>Like I said elsewhere [slashdot.org], I suspect this is more a matter of spoken language using comma rather than point.
Especially because no-one says "two period five" in English.
They say "two POINT five".
The period just looks like a point.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229638</id>
	<title>Re:This is stupid.</title>
	<author>Anonymous</author>
	<datestamp>1257194700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Moreover, they should have used a strongly typed scaled integer class instead of whatever it was they were using. When using scaled integers, ALWAYS make sure that you use the type system of the language effectively to prevent integers with one scale from being assigned to fields with a different scale. "But I checked the math myself!" Yah, yah, yah... you WILL get it wrong someday.</p></htmltext>
<tokenext>Moreover , they should have used a strongly typed scaled integer class instead of whatever it was they were using .
When using scaled integers , ALWAYS make sure that you use the type system of the language effectively to prevent integers with one scale from being assigned to fields with a different scale .
" But I checked the math myself !
" Yah , yah , yah... you WILL get it wrong someday .</tokentext>
<sentencetext>Moreover, they should have used a strongly typed scaled integer class instead of whatever it was they were using.
When using scaled integers, ALWAYS make sure that you use the type system of the language effectively to prevent integers with one scale from being assigned to fields with a different scale.
"But I checked the math myself!
" Yah, yah, yah... you WILL get it wrong someday.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226440</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228328</id>
	<title>Re:Back to Roman numerals</title>
	<author>TheRaven64</author>
	<datestamp>1257188940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>And, best of all, you can take out as much money as you want and never be overdrawn!</htmltext>
<tokenext>And , best of all , you can take out as much money as you want and never be overdrawn !</tokentext>
<sentencetext>And, best of all, you can take out as much money as you want and never be overdrawn!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226384</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230396</id>
	<title>Re:Good to be a programmer</title>
	<author>Anonymous</author>
	<datestamp>1257155340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Infact my account is actually -2600 &euro; and I have to pay the university fee before the 30th of this month... That's how things work in Italy, you have to think about everything. I'm lucky I have some cash in my house now, or I couldn't eat tomorrow... x\_x</p></htmltext>
<tokenext>Infact my account is actually -2600    and I have to pay the university fee before the 30th of this month... That 's how things work in Italy , you have to think about everything .
I 'm lucky I have some cash in my house now , or I could n't eat tomorrow... x \ _x</tokentext>
<sentencetext>Infact my account is actually -2600 € and I have to pay the university fee before the 30th of this month... That's how things work in Italy, you have to think about everything.
I'm lucky I have some cash in my house now, or I couldn't eat tomorrow... x\_x</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226182</id>
	<title>1,00st post!</title>
	<author>Anonymous</author>
	<datestamp>1257178680000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>1,00st post!</p></htmltext>
<tokenext>1,00st post !</tokentext>
<sentencetext>1,00st post!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227752</id>
	<title>It's a Royale with Cheese</title>
	<author>Kartoffel</author>
	<datestamp>1257186240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If it was really French, you wouldn't have such bastardizations as "sous-marin de 12 pouces", cinq six bo&#238;tes de tomates vertes!</p></htmltext>
<tokenext>If it was really French , you would n't have such bastardizations as " sous-marin de 12 pouces " , cinq six bo   tes de tomates vertes !</tokentext>
<sentencetext>If it was really French, you wouldn't have such bastardizations as "sous-marin de 12 pouces", cinq six boîtes de tomates vertes!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226798</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538</id>
	<title>Happened to me recently</title>
	<author>Acer500</author>
	<datestamp>1257180300000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>I made a similar mistake recently... I made a (.NET) data entry software that received monetary quantities as user input, and I converted them without taking into account the Windows settings for decimals and thousands separators.
<br> <br>
It worked fine until somebody used a different language OS... and some strange quantities were recorded, one slipped all the way through the process and a confused customer received a bill for 17.000.000 local currency (about U$ 1.000.000) . I fixed it by using the CultureInfo, etc..<nobr> <wbr></nobr>.when converting, but it wasn't nice, messed with all of the higher ups' reports and everything ("Hey, hadn't we sold about U$ 1.000.000 more?" "No, it was an error from G in Development")<br> <br>
I'm sure there are better ways and good practices, but keep in mind that where I work we don't even have testing, so I guess I'm getting sloppy. If someone wants to give advice, go ahead, I'll appreciate it (or at least should<nobr> <wbr></nobr>:) ).</htmltext>
<tokenext>I made a similar mistake recently... I made a ( .NET ) data entry software that received monetary quantities as user input , and I converted them without taking into account the Windows settings for decimals and thousands separators .
It worked fine until somebody used a different language OS... and some strange quantities were recorded , one slipped all the way through the process and a confused customer received a bill for 17.000.000 local currency ( about U $ 1.000.000 ) .
I fixed it by using the CultureInfo , etc.. .when converting , but it was n't nice , messed with all of the higher ups ' reports and everything ( " Hey , had n't we sold about U $ 1.000.000 more ?
" " No , it was an error from G in Development " ) I 'm sure there are better ways and good practices , but keep in mind that where I work we do n't even have testing , so I guess I 'm getting sloppy .
If someone wants to give advice , go ahead , I 'll appreciate it ( or at least should : ) ) .</tokentext>
<sentencetext>I made a similar mistake recently... I made a (.NET) data entry software that received monetary quantities as user input, and I converted them without taking into account the Windows settings for decimals and thousands separators.
It worked fine until somebody used a different language OS... and some strange quantities were recorded, one slipped all the way through the process and a confused customer received a bill for 17.000.000 local currency (about U$ 1.000.000) .
I fixed it by using the CultureInfo, etc.. .when converting, but it wasn't nice, messed with all of the higher ups' reports and everything ("Hey, hadn't we sold about U$ 1.000.000 more?
" "No, it was an error from G in Development") 
I'm sure there are better ways and good practices, but keep in mind that where I work we don't even have testing, so I guess I'm getting sloppy.
If someone wants to give advice, go ahead, I'll appreciate it (or at least should :) ).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230050</id>
	<title>Re:Happened to me recently</title>
	<author>coolsnowmen</author>
	<datestamp>1257153540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That works until someone actually cares about fractions of a cent (financial market,stock price). Then your 1.055 (1 dollar 5 and a half cents) became 1,055 (one thousand fifty five dollars).</p><p>If you are worried about it, I think telling the user is the best way to prevent a mistake.  A simple example below the input shows how the number should be input.  Then anyone can figure it out.  If you want both possibilities, then add the option.  If you want to pull it from the locale information, then you can still display below the input:</p><p>Example:$ 1,234,567.89<br>(If your detection thinks they user is European, or they select so)<br>Example:EURO 1.234.567,89</p></htmltext>
<tokenext>That works until someone actually cares about fractions of a cent ( financial market,stock price ) .
Then your 1.055 ( 1 dollar 5 and a half cents ) became 1,055 ( one thousand fifty five dollars ) .If you are worried about it , I think telling the user is the best way to prevent a mistake .
A simple example below the input shows how the number should be input .
Then anyone can figure it out .
If you want both possibilities , then add the option .
If you want to pull it from the locale information , then you can still display below the input : Example : $ 1,234,567.89 ( If your detection thinks they user is European , or they select so ) Example : EURO 1.234.567,89</tokentext>
<sentencetext>That works until someone actually cares about fractions of a cent (financial market,stock price).
Then your 1.055 (1 dollar 5 and a half cents) became 1,055 (one thousand fifty five dollars).If you are worried about it, I think telling the user is the best way to prevent a mistake.
A simple example below the input shows how the number should be input.
Then anyone can figure it out.
If you want both possibilities, then add the option.
If you want to pull it from the locale information, then you can still display below the input:Example:$ 1,234,567.89(If your detection thinks they user is European, or they select so)Example:EURO 1.234.567,89</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227308</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30234278</id>
	<title>Re:For the most part.</title>
	<author>Anonymous</author>
	<datestamp>1257188940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Using strings to store numbers internally is wrong, it just is.</p></div><p>tell that to the COBOLers who write this kind of software...</p></div>
	</htmltext>
<tokenext>Using strings to store numbers internally is wrong , it just is.tell that to the COBOLers who write this kind of software.. .</tokentext>
<sentencetext>Using strings to store numbers internally is wrong, it just is.tell that to the COBOLers who write this kind of software...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230310</id>
	<title>Re:Happened to me recently</title>
	<author>Anonymous</author>
	<datestamp>1257154920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Try using RegExp. It's a life saver.<br> <br>
^\$?(\d{1,3},?(\d{3},?)*\d{3}(\.\d{0,2})?|\d{1,3}(\.\d{0,2})?|\.\d{1,2}?)$
<br> <br>
If it doesn't match that, then throw an error.</htmltext>
<tokenext>Try using RegExp .
It 's a life saver .
^ \ $ ? ( \ d { 1,3 } , ? ( \ d { 3 } , ? ) * \ d { 3 } ( \ . \ d { 0,2 } ) ? | \ d { 1,3 } ( \ . \ d { 0,2 } ) ? | \ . \ d { 1,2 } ? ) $ If it does n't match that , then throw an error .</tokentext>
<sentencetext>Try using RegExp.
It's a life saver.
^\$?(\d{1,3},?(\d{3},?)*\d{3}(\.\d{0,2})?|\d{1,3}(\.\d{0,2})?|\.\d{1,2}?)$
 
If it doesn't match that, then throw an error.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226834</id>
	<title>Re:God Bless the USA!</title>
	<author>Sky Cry</author>
	<datestamp>1257181740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>It makes more sense to use the stronger punctuation as the mark between whole and fraction.</p></div></blockquote><p> Why does stronger punctuation make more sense to you? Weaker punctuation makes more sense to me, because it simply separates parts of one number.</p><p>Whichever symbol you use, there'll be confusion with its other uses. So you have to watch for the space after the comma or period either way. It takes as much effort.</p></div>
	</htmltext>
<tokenext>It makes more sense to use the stronger punctuation as the mark between whole and fraction .
Why does stronger punctuation make more sense to you ?
Weaker punctuation makes more sense to me , because it simply separates parts of one number.Whichever symbol you use , there 'll be confusion with its other uses .
So you have to watch for the space after the comma or period either way .
It takes as much effort .</tokentext>
<sentencetext>It makes more sense to use the stronger punctuation as the mark between whole and fraction.
Why does stronger punctuation make more sense to you?
Weaker punctuation makes more sense to me, because it simply separates parts of one number.Whichever symbol you use, there'll be confusion with its other uses.
So you have to watch for the space after the comma or period either way.
It takes as much effort.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226306</id>
	<title>That's why it is called a floating point.</title>
	<author>Anonymous</author>
	<datestamp>1257179220000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Duh.</p></htmltext>
<tokenext>Duh .</tokentext>
<sentencetext>Duh.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210</id>
	<title>For the most part.</title>
	<author>Anonymous</author>
	<datestamp>1257178740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Most programs I have seen they don't allow you to type in thousands separator. If they are fancy they will display it to you for in the program when you type in the number. Otherwise it will not show... And for God sake why would you want to store the number as a string any ways?</p></htmltext>
<tokenext>Most programs I have seen they do n't allow you to type in thousands separator .
If they are fancy they will display it to you for in the program when you type in the number .
Otherwise it will not show... And for God sake why would you want to store the number as a string any ways ?</tokentext>
<sentencetext>Most programs I have seen they don't allow you to type in thousands separator.
If they are fancy they will display it to you for in the program when you type in the number.
Otherwise it will not show... And for God sake why would you want to store the number as a string any ways?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230320</id>
	<title>Re:Periods and commas.</title>
	<author>DjDanny</author>
	<datestamp>1257155040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I never understood why the hell Europeans swap periods and commas. Grammatically it doesn't even make sense.</p></div><p>Maybe it's for the same reason that Americans write dates in the wrong order?</p><p>DD/MM/YY makes perfect sense - you're going from the smallest unit to the largest as you go from left to right.</p><p>MM/DD/YY is just a bodge job which causes the rest of us hours of lost time when debugging code!</p></div>
	</htmltext>
<tokenext>I never understood why the hell Europeans swap periods and commas .
Grammatically it does n't even make sense.Maybe it 's for the same reason that Americans write dates in the wrong order ? DD/MM/YY makes perfect sense - you 're going from the smallest unit to the largest as you go from left to right.MM/DD/YY is just a bodge job which causes the rest of us hours of lost time when debugging code !</tokentext>
<sentencetext>I never understood why the hell Europeans swap periods and commas.
Grammatically it doesn't even make sense.Maybe it's for the same reason that Americans write dates in the wrong order?DD/MM/YY makes perfect sense - you're going from the smallest unit to the largest as you go from left to right.MM/DD/YY is just a bodge job which causes the rest of us hours of lost time when debugging code!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226844</id>
	<title>Logical separators [Re:Periods and commas.]</title>
	<author>Geoffrey.landis</author>
	<datestamp>1257181800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I never understood why the hell Europeans swap periods and commas. Grammatically it doesn't even make sense. A period ends a sentence or statement, which to me should imply a whole number. A comma is simply a separator, used within sentences. So why would it be used to separate decimals?</p></div><p>By your logic, <i>both</i> commas and periods as the decimal "point" separator are wrong, since the decimal is not the end of the number.
</p><p>Logically, then, the decimal locator should be a semicolon: more of a stop than a comma, but not the end of the number.  Like so:
</p><p>12,345;67
</p><p>That would avoid ambiguity in sentences like
<br>"He said I owed 120. 20 for the part and the rest for labor."</p></div>
	</htmltext>
<tokenext>I never understood why the hell Europeans swap periods and commas .
Grammatically it does n't even make sense .
A period ends a sentence or statement , which to me should imply a whole number .
A comma is simply a separator , used within sentences .
So why would it be used to separate decimals ? By your logic , both commas and periods as the decimal " point " separator are wrong , since the decimal is not the end of the number .
Logically , then , the decimal locator should be a semicolon : more of a stop than a comma , but not the end of the number .
Like so : 12,345 ; 67 That would avoid ambiguity in sentences like " He said I owed 120 .
20 for the part and the rest for labor .
"</tokentext>
<sentencetext>I never understood why the hell Europeans swap periods and commas.
Grammatically it doesn't even make sense.
A period ends a sentence or statement, which to me should imply a whole number.
A comma is simply a separator, used within sentences.
So why would it be used to separate decimals?By your logic, both commas and periods as the decimal "point" separator are wrong, since the decimal is not the end of the number.
Logically, then, the decimal locator should be a semicolon: more of a stop than a comma, but not the end of the number.
Like so:
12,345;67
That would avoid ambiguity in sentences like
"He said I owed 120.
20 for the part and the rest for labor.
"
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226454</id>
	<title>Re:For the most part.</title>
	<author>Anonymous</author>
	<datestamp>1257179940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>This is the same in my bank, if you type in . it gives an error. In addition it requires you to type in the<nobr> <wbr></nobr>,00 too, and next to the sum text box is an example like "150,00".</p><p>Having comma/decimal as a separator is stupid anyway, space does just fine - 150 000.35</p></div><p>Space can be just as confusing as comma or period.  I'm going to revolutionize banking and suggest we move in a new direction.  I'm going to take the offensive on confusion and suggest we use 0 to deliminate/separate groupings of numbers.</p></div>
	</htmltext>
<tokenext>This is the same in my bank , if you type in .
it gives an error .
In addition it requires you to type in the ,00 too , and next to the sum text box is an example like " 150,00 " .Having comma/decimal as a separator is stupid anyway , space does just fine - 150 000.35Space can be just as confusing as comma or period .
I 'm going to revolutionize banking and suggest we move in a new direction .
I 'm going to take the offensive on confusion and suggest we use 0 to deliminate/separate groupings of numbers .</tokentext>
<sentencetext>This is the same in my bank, if you type in .
it gives an error.
In addition it requires you to type in the ,00 too, and next to the sum text box is an example like "150,00".Having comma/decimal as a separator is stupid anyway, space does just fine - 150 000.35Space can be just as confusing as comma or period.
I'm going to revolutionize banking and suggest we move in a new direction.
I'm going to take the offensive on confusion and suggest we use 0 to deliminate/separate groupings of numbers.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226556</id>
	<title>Re:God Bless the USA!</title>
	<author>Kartoffel</author>
	<datestamp>1257180420000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>Australians seem to be doing even better than Americans, then.  They still drive on the proper side of the road, although they measure distances in kilometers rather than miles as god and the queen intended.</p><p>Well at least Australia is doing better than Canada.  Those poor sods drive on the wrong side *and* use the metric system on their roads.</p></htmltext>
<tokenext>Australians seem to be doing even better than Americans , then .
They still drive on the proper side of the road , although they measure distances in kilometers rather than miles as god and the queen intended.Well at least Australia is doing better than Canada .
Those poor sods drive on the wrong side * and * use the metric system on their roads .</tokentext>
<sentencetext>Australians seem to be doing even better than Americans, then.
They still drive on the proper side of the road, although they measure distances in kilometers rather than miles as god and the queen intended.Well at least Australia is doing better than Canada.
Those poor sods drive on the wrong side *and* use the metric system on their roads.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226332</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30232032</id>
	<title>Re:Periods and commas.</title>
	<author>Kittenman</author>
	<datestamp>1257167220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Some of us call "periods" full stops, of course.</htmltext>
<tokenext>Some of us call " periods " full stops , of course .</tokentext>
<sentencetext>Some of us call "periods" full stops, of course.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227204</id>
	<title>Re:Periods and commas.</title>
	<author>mano.m</author>
	<datestamp>1257183540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>No, no, wait, we can still milk some literary merit out of this.<p><div class="quote"><p>I went to the supermarket to buy some cola.</p></div><p>That's fine.</p><p><div class="quote"><p>cabbages.</p></div><p>And, while at the cash, the item I'd been trying to remember all this while came back to me.</p><p><div class="quote"><p>and condoms</p></div><p>A small moment of hope and optimism followed.</p><p><nobr> <wbr></nobr></p><div class="quote"><p>,</p></div><p>Until I paused to reflect and concluded that it would be not much use at all.

There, fixed that for you.</p></div>
	</htmltext>
<tokenext>No , no , wait , we can still milk some literary merit out of this.I went to the supermarket to buy some cola.That 's fine.cabbages.And , while at the cash , the item I 'd been trying to remember all this while came back to me.and condomsA small moment of hope and optimism followed .
,Until I paused to reflect and concluded that it would be not much use at all .
There , fixed that for you .</tokentext>
<sentencetext>No, no, wait, we can still milk some literary merit out of this.I went to the supermarket to buy some cola.That's fine.cabbages.And, while at the cash, the item I'd been trying to remember all this while came back to me.and condomsA small moment of hope and optimism followed.
,Until I paused to reflect and concluded that it would be not much use at all.
There, fixed that for you.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30232626</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257171480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>same way as , are more visible than . wich also makes sense "1.000,00"</p></htmltext>
<tokenext>same way as , are more visible than .
wich also makes sense " 1.000,00 "</tokentext>
<sentencetext>same way as , are more visible than .
wich also makes sense "1.000,00"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230976</id>
	<title>J. Wassil</title>
	<author>Anonymous</author>
	<datestamp>1257159060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>So did the decimal bug ever get back his money??</p></htmltext>
<tokenext>So did the decimal bug ever get back his money ?
?</tokentext>
<sentencetext>So did the decimal bug ever get back his money?
?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228034</id>
	<title>Good thing it's only one bug</title>
	<author>vinn01</author>
	<datestamp>1257187380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I used to work at a place that was nuts about bug counts.  Nevermind the severity.</p><p>This decimal comma bug would be *one* bug.  A typo on an informational page would count as one bug too.</p><p>The developers were always questioned "How many bugs did you fix on this release?"  And QA would have to answer "How many bugs did you verify on this release?".  Guess which bugs would get fixed and verified for the current release and which bugs would get deferred to later releases.</p><p>Drove me crazy.</p></htmltext>
<tokenext>I used to work at a place that was nuts about bug counts .
Nevermind the severity.This decimal comma bug would be * one * bug .
A typo on an informational page would count as one bug too.The developers were always questioned " How many bugs did you fix on this release ?
" And QA would have to answer " How many bugs did you verify on this release ? " .
Guess which bugs would get fixed and verified for the current release and which bugs would get deferred to later releases.Drove me crazy .</tokentext>
<sentencetext>I used to work at a place that was nuts about bug counts.
Nevermind the severity.This decimal comma bug would be *one* bug.
A typo on an informational page would count as one bug too.The developers were always questioned "How many bugs did you fix on this release?
"  And QA would have to answer "How many bugs did you verify on this release?".
Guess which bugs would get fixed and verified for the current release and which bugs would get deferred to later releases.Drove me crazy.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227472</id>
	<title>Re:God Bless the USA!</title>
	<author>arkham6</author>
	<datestamp>1257185040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>thank you for your<nobr> <wbr></nobr>,02 cents.</htmltext>
<tokenext>thank you for your ,02 cents .</tokentext>
<sentencetext>thank you for your ,02 cents.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227210</id>
	<title>Re:This is stupid.</title>
	<author>Anonymous</author>
	<datestamp>1257183660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><i>A moving decimal shouldn't affect the internal math, it should be nothing more than a harmless display error</i></p><p>This wasn't a "moving decimal" problem, it was a fundamental error in data parsing, on the level of mixing metric and English units in a Mars lander.  No amount of modeling and controllerizificationing (yay for buzzwords) would have fixed the fact that the programmer who wrote the routine did not realize that "," meant "." in Italian.</p></htmltext>
<tokenext>A moving decimal should n't affect the internal math , it should be nothing more than a harmless display errorThis was n't a " moving decimal " problem , it was a fundamental error in data parsing , on the level of mixing metric and English units in a Mars lander .
No amount of modeling and controllerizificationing ( yay for buzzwords ) would have fixed the fact that the programmer who wrote the routine did not realize that " , " meant " .
" in Italian .</tokentext>
<sentencetext>A moving decimal shouldn't affect the internal math, it should be nothing more than a harmless display errorThis wasn't a "moving decimal" problem, it was a fundamental error in data parsing, on the level of mixing metric and English units in a Mars lander.
No amount of modeling and controllerizificationing (yay for buzzwords) would have fixed the fact that the programmer who wrote the routine did not realize that "," meant ".
" in Italian.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226440</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227588</id>
	<title>Re:For the most part.</title>
	<author>mea37</author>
	<datestamp>1257185520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Unless I'm missing something... and I'll grant I'm being to lazy to RTFA this time...</p><p>What makes you think they stored any number as a string?  It looks to me like they made a programming error, where a number was treated as "number of Euro" in one routine and as "number of Euro cents" in another.  If a person made this error, you would say they misplaced the decimal point (er, comma I suppose); and since we like to personify computers and pretend they made a mistake when a buggy program executes, by analogy we say the ATM misplaced the decimal.</p></htmltext>
<tokenext>Unless I 'm missing something... and I 'll grant I 'm being to lazy to RTFA this time...What makes you think they stored any number as a string ?
It looks to me like they made a programming error , where a number was treated as " number of Euro " in one routine and as " number of Euro cents " in another .
If a person made this error , you would say they misplaced the decimal point ( er , comma I suppose ) ; and since we like to personify computers and pretend they made a mistake when a buggy program executes , by analogy we say the ATM misplaced the decimal .</tokentext>
<sentencetext>Unless I'm missing something... and I'll grant I'm being to lazy to RTFA this time...What makes you think they stored any number as a string?
It looks to me like they made a programming error, where a number was treated as "number of Euro" in one routine and as "number of Euro cents" in another.
If a person made this error, you would say they misplaced the decimal point (er, comma I suppose); and since we like to personify computers and pretend they made a mistake when a buggy program executes, by analogy we say the ATM misplaced the decimal.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235374</id>
	<title>Re:Periods and commas.</title>
	<author>Hurricane78</author>
	<datestamp>1259234580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Exactly. The thing here is. I use the way I learned in school. You use what you learned. Since it&rsquo;s arbitraty (and backwards reasoning will not change that), it really does not matter.</p><p>I will let you do your way and be happy, and you let me do my way and be happy too. If I go to a country that has other rules, just like I then talk the language of that country (or at least try), I change the way I write decimal separators, dates, etc. It&rsquo;s a matter of politeness and respect. And I won&rsquo;t break a leg over something that unimportant anyway.</p><p>Now the typical American on the other hand is very proud of his country (for no reason, from our p.o.v., but hey, why not), so he gets a little arrogant, by coming to your country, and expecting <em>you</em> to speak <em>his</em> language and use <em>his</em> dates and decimal systems when communicating with you. Even on price signs and hotel calendars.<br>He assumes to be better at everything. He also assumes that Americans invented everything (just like the Greeks ^^). Light bulbs, electricity, the telephone, the car, whatever...<nobr> <wbr></nobr>:D (Yes, partially they have, but you get my point.)</p><p>That&rsquo;s the difference. We don&rsquo;t go to an US forum and say that our system is better than yours in the first place if the difference is irrelevant because it&rsquo;s arbitrary.<nobr> <wbr></nobr>:)</p><p>But I must say, it <em>works</em>. It works especially well in Germany, where people live in constant fear of being called Nazis for even thinking about it being thinkable to be proud of their country or something related to it.<br>In Germany, if you have a room of 1000 people, and one person of a foreign country comes in, they instantly all start to speak <em>English</em>. Yeah, even if that person is from Mongolia and knows enough German to understand what they are saying. It&rsquo;s ridiculous. ^^</p><p>Just so you know how we feel about it: You say that the French are arrogant? Well they can&rsquo;t hold a candle to you. The funny thing  is that you don&rsquo;t <em>need</em> it. I mean who flew on the freakin <em>moon</em> for god&rsquo;s sake? ^^ It&rsquo;s not as if we would not know that without you acting all &ldquo;wow, we&rsquo;re so cool&rdquo;. In fact a proper understatement is way cooler. So do you really want to act <em>more &ldquo;French&rdquo;</em> than the French themselves? ^^</p></htmltext>
<tokenext>Exactly .
The thing here is .
I use the way I learned in school .
You use what you learned .
Since it    s arbitraty ( and backwards reasoning will not change that ) , it really does not matter.I will let you do your way and be happy , and you let me do my way and be happy too .
If I go to a country that has other rules , just like I then talk the language of that country ( or at least try ) , I change the way I write decimal separators , dates , etc .
It    s a matter of politeness and respect .
And I won    t break a leg over something that unimportant anyway.Now the typical American on the other hand is very proud of his country ( for no reason , from our p.o.v. , but hey , why not ) , so he gets a little arrogant , by coming to your country , and expecting you to speak his language and use his dates and decimal systems when communicating with you .
Even on price signs and hotel calendars.He assumes to be better at everything .
He also assumes that Americans invented everything ( just like the Greeks ^ ^ ) .
Light bulbs , electricity , the telephone , the car , whatever... : D ( Yes , partially they have , but you get my point .
) That    s the difference .
We don    t go to an US forum and say that our system is better than yours in the first place if the difference is irrelevant because it    s arbitrary .
: ) But I must say , it works .
It works especially well in Germany , where people live in constant fear of being called Nazis for even thinking about it being thinkable to be proud of their country or something related to it.In Germany , if you have a room of 1000 people , and one person of a foreign country comes in , they instantly all start to speak English .
Yeah , even if that person is from Mongolia and knows enough German to understand what they are saying .
It    s ridiculous .
^ ^ Just so you know how we feel about it : You say that the French are arrogant ?
Well they can    t hold a candle to you .
The funny thing is that you don    t need it .
I mean who flew on the freakin moon for god    s sake ?
^ ^ It    s not as if we would not know that without you acting all    wow , we    re so cool    .
In fact a proper understatement is way cooler .
So do you really want to act more    French    than the French themselves ?
^ ^</tokentext>
<sentencetext>Exactly.
The thing here is.
I use the way I learned in school.
You use what you learned.
Since it’s arbitraty (and backwards reasoning will not change that), it really does not matter.I will let you do your way and be happy, and you let me do my way and be happy too.
If I go to a country that has other rules, just like I then talk the language of that country (or at least try), I change the way I write decimal separators, dates, etc.
It’s a matter of politeness and respect.
And I won’t break a leg over something that unimportant anyway.Now the typical American on the other hand is very proud of his country (for no reason, from our p.o.v., but hey, why not), so he gets a little arrogant, by coming to your country, and expecting you to speak his language and use his dates and decimal systems when communicating with you.
Even on price signs and hotel calendars.He assumes to be better at everything.
He also assumes that Americans invented everything (just like the Greeks ^^).
Light bulbs, electricity, the telephone, the car, whatever... :D (Yes, partially they have, but you get my point.
)That’s the difference.
We don’t go to an US forum and say that our system is better than yours in the first place if the difference is irrelevant because it’s arbitrary.
:)But I must say, it works.
It works especially well in Germany, where people live in constant fear of being called Nazis for even thinking about it being thinkable to be proud of their country or something related to it.In Germany, if you have a room of 1000 people, and one person of a foreign country comes in, they instantly all start to speak English.
Yeah, even if that person is from Mongolia and knows enough German to understand what they are saying.
It’s ridiculous.
^^Just so you know how we feel about it: You say that the French are arrogant?
Well they can’t hold a candle to you.
The funny thing  is that you don’t need it.
I mean who flew on the freakin moon for god’s sake?
^^ It’s not as if we would not know that without you acting all “wow, we’re so cool”.
In fact a proper understatement is way cooler.
So do you really want to act more “French” than the French themselves?
^^</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228044</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257187500000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>I went to the supermarket to buy some cola. cabbages. and condoms,.</p></div><p>What I can't understand is why you would need cabbage and condoms... After eating the cabbage there is no way you'll be needing the condoms!</p></div>
	</htmltext>
<tokenext>I went to the supermarket to buy some cola .
cabbages. and condoms,.What I ca n't understand is why you would need cabbage and condoms... After eating the cabbage there is no way you 'll be needing the condoms !</tokentext>
<sentencetext>I went to the supermarket to buy some cola.
cabbages. and condoms,.What I can't understand is why you would need cabbage and condoms... After eating the cabbage there is no way you'll be needing the condoms!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226940</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257182220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Your logic is kind of flawed. Since "," is a separator in sentences, why sholdn't it be a separator for numbers?<br>Keeping to the logic of language,  is a week separator (separates between words),  semi-week and  strong.</p><p>The most reasonable would thus be 1000000.00 = 1 000 000,00  (which happens to be the standard in some nordic countries).</p><p>Using commas and dots would be like writing:<br>I,went,to,the,supermarket,to,buy,some,cola.cabbages.and.condoms!</p><p>Even if we can't agree on the right way to write numbers, could we at least agree localization of Excel and other programs is the SOURCE OF ALL EVIL EVER!!!<br>Whoever thought it was a good idea to change the formatting of dates, numbers etc based on your computer settings should spend an eternity in hell "converting" fucked up csv's, dump files etc.</p></htmltext>
<tokenext>Your logic is kind of flawed .
Since " , " is a separator in sentences , why shold n't it be a separator for numbers ? Keeping to the logic of language , is a week separator ( separates between words ) , semi-week and strong.The most reasonable would thus be 1000000.00 = 1 000 000,00 ( which happens to be the standard in some nordic countries ) .Using commas and dots would be like writing : I,went,to,the,supermarket,to,buy,some,cola.cabbages.and.condoms ! Even if we ca n't agree on the right way to write numbers , could we at least agree localization of Excel and other programs is the SOURCE OF ALL EVIL EVER ! !
! Whoever thought it was a good idea to change the formatting of dates , numbers etc based on your computer settings should spend an eternity in hell " converting " fucked up csv 's , dump files etc .</tokentext>
<sentencetext>Your logic is kind of flawed.
Since "," is a separator in sentences, why sholdn't it be a separator for numbers?Keeping to the logic of language,  is a week separator (separates between words),  semi-week and  strong.The most reasonable would thus be 1000000.00 = 1 000 000,00  (which happens to be the standard in some nordic countries).Using commas and dots would be like writing:I,went,to,the,supermarket,to,buy,some,cola.cabbages.and.condoms!Even if we can't agree on the right way to write numbers, could we at least agree localization of Excel and other programs is the SOURCE OF ALL EVIL EVER!!
!Whoever thought it was a good idea to change the formatting of dates, numbers etc based on your computer settings should spend an eternity in hell "converting" fucked up csv's, dump files etc.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226744</id>
	<title>Italian Office Space ?</title>
	<author>Beretta Vexe</author>
	<datestamp>1257181320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Alright so when the sub routine compounds the interest is uses all these extra decimal places that just get rounded off. So we simplified the whole thing, we rounded them all down, drop the remainder into an account we opened.</p></htmltext>
<tokenext>Alright so when the sub routine compounds the interest is uses all these extra decimal places that just get rounded off .
So we simplified the whole thing , we rounded them all down , drop the remainder into an account we opened .</tokentext>
<sentencetext>Alright so when the sub routine compounds the interest is uses all these extra decimal places that just get rounded off.
So we simplified the whole thing, we rounded them all down, drop the remainder into an account we opened.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226730</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257181200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>URLs have more periods than commas and it seems to work fine.  Yet URLs are in words and you are trying to apply this logic to numbers.</p></htmltext>
<tokenext>URLs have more periods than commas and it seems to work fine .
Yet URLs are in words and you are trying to apply this logic to numbers .</tokentext>
<sentencetext>URLs have more periods than commas and it seems to work fine.
Yet URLs are in words and you are trying to apply this logic to numbers.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227320</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257184200000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>I think I read somewhere that the Australians would change from left to right in 2012. They would start with all the bigger vehicles like buses and lorries and if that turns out OK, it'll be mandatory for all motorized vehicles from 2015</p></htmltext>
<tokenext>I think I read somewhere that the Australians would change from left to right in 2012 .
They would start with all the bigger vehicles like buses and lorries and if that turns out OK , it 'll be mandatory for all motorized vehicles from 2015</tokentext>
<sentencetext>I think I read somewhere that the Australians would change from left to right in 2012.
They would start with all the bigger vehicles like buses and lorries and if that turns out OK, it'll be mandatory for all motorized vehicles from 2015</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226556</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227142</id>
	<title>Rookie mistake</title>
	<author>plopez</author>
	<datestamp>1257183240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>And if the people weren't rookies, shame on them. It's obvious they had no knowledge of the culture and conventions of their target user. This is what happens when the program team, including the management and QA team (assuming there was one), is offshored.</p><p>I am currently working on a distributed international project. Not only things like decimal points, measurement systems,  and spelling are taken into account but also the tone of the error messages and documentation. What is acceptable in one culture may be insulting in an other.</p><p>Also latency is taken into account. A person in another culture and/or with low speed connections to the internet may have different latency expectations than those in other cultures and/or high speed connections.</p><p>KNOW YOUR END USER!</p></htmltext>
<tokenext>And if the people were n't rookies , shame on them .
It 's obvious they had no knowledge of the culture and conventions of their target user .
This is what happens when the program team , including the management and QA team ( assuming there was one ) , is offshored.I am currently working on a distributed international project .
Not only things like decimal points , measurement systems , and spelling are taken into account but also the tone of the error messages and documentation .
What is acceptable in one culture may be insulting in an other.Also latency is taken into account .
A person in another culture and/or with low speed connections to the internet may have different latency expectations than those in other cultures and/or high speed connections.KNOW YOUR END USER !</tokentext>
<sentencetext>And if the people weren't rookies, shame on them.
It's obvious they had no knowledge of the culture and conventions of their target user.
This is what happens when the program team, including the management and QA team (assuming there was one), is offshored.I am currently working on a distributed international project.
Not only things like decimal points, measurement systems,  and spelling are taken into account but also the tone of the error messages and documentation.
What is acceptable in one culture may be insulting in an other.Also latency is taken into account.
A person in another culture and/or with low speed connections to the internet may have different latency expectations than those in other cultures and/or high speed connections.KNOW YOUR END USER!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226754</id>
	<title>Re:Periods and commas.</title>
	<author>fractic</author>
	<datestamp>1257181380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I'm British - I use "," to separate thousands and "." to separate decimals, but that doesn't make me 'right' - it really is just usage and custom, there isn't anything to really recommend one way over the other.<br>
&nbsp;</p> </div><p>Actually there is. The reason why a comma is used as a decimal separator in some places is the following. The decimal separator is more important<br>that the thousands separator, a misplaced thousands separator doesn't matter since it has no effect on the value. Now a speck of ink is more easily mistaken for a dot than a comma. It would be bad to mistake a speck of ink for a decimal separator.</p><p>Some people have argued that because the dot is more important for sentence structure it should also be used for the more important decimal separator. However this isn't a very strong argument since there is no reason to use grammar rules for the notation of numbers.</p><p>That said, personally I use a dot since I need the comma to separate lists of numbers (e.g. 1.2, 1.3, 1.4 ) and the comma notation for lists is almost<br>universal.</p></div>
	</htmltext>
<tokenext>I 'm British - I use " , " to separate thousands and " .
" to separate decimals , but that does n't make me 'right ' - it really is just usage and custom , there is n't anything to really recommend one way over the other .
  Actually there is .
The reason why a comma is used as a decimal separator in some places is the following .
The decimal separator is more importantthat the thousands separator , a misplaced thousands separator does n't matter since it has no effect on the value .
Now a speck of ink is more easily mistaken for a dot than a comma .
It would be bad to mistake a speck of ink for a decimal separator.Some people have argued that because the dot is more important for sentence structure it should also be used for the more important decimal separator .
However this is n't a very strong argument since there is no reason to use grammar rules for the notation of numbers.That said , personally I use a dot since I need the comma to separate lists of numbers ( e.g .
1.2 , 1.3 , 1.4 ) and the comma notation for lists is almostuniversal .</tokentext>
<sentencetext>I'm British - I use "," to separate thousands and ".
" to separate decimals, but that doesn't make me 'right' - it really is just usage and custom, there isn't anything to really recommend one way over the other.
  Actually there is.
The reason why a comma is used as a decimal separator in some places is the following.
The decimal separator is more importantthat the thousands separator, a misplaced thousands separator doesn't matter since it has no effect on the value.
Now a speck of ink is more easily mistaken for a dot than a comma.
It would be bad to mistake a speck of ink for a decimal separator.Some people have argued that because the dot is more important for sentence structure it should also be used for the more important decimal separator.
However this isn't a very strong argument since there is no reason to use grammar rules for the notation of numbers.That said, personally I use a dot since I need the comma to separate lists of numbers (e.g.
1.2, 1.3, 1.4 ) and the comma notation for lists is almostuniversal.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226826</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257181680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p> <i>I went to the supermarket to buy some cola. cabbages. and condoms,</i> </p><p>Your alliterative sex life intrigues me and I wish to subscribe to your newsletter.</p><p>Thus I can learn what to do with a letter-opener, a lime, and lube.</p></htmltext>
<tokenext>I went to the supermarket to buy some cola .
cabbages. and condoms , Your alliterative sex life intrigues me and I wish to subscribe to your newsletter.Thus I can learn what to do with a letter-opener , a lime , and lube .</tokentext>
<sentencetext> I went to the supermarket to buy some cola.
cabbages. and condoms, Your alliterative sex life intrigues me and I wish to subscribe to your newsletter.Thus I can learn what to do with a letter-opener, a lime, and lube.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226918</id>
	<title>Re:For the most part.</title>
	<author>v1</author>
	<datestamp>1257182100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>And for God sake why would you want to store the number as a string any ways?</i></p><p>It's not so much the <i>storage</i> as it is the <i>transport</i>.  Sometimes you need to send things as a flat text file with one record per line, for data exchange.  Then you start running into all sorts of problems like tabs vs spaces, field widths, line delimiters, right vs left justification, and other oddness like these separators.  <i>Really</i> if they wanted to do that more smartly, they'd omit all separators in a numeric field and simply state number of pennies.  Problem solved.  Every time I've had to put a dollar amount in a text field it's been in pennies for this exact reason.</p></htmltext>
<tokenext>And for God sake why would you want to store the number as a string any ways ? It 's not so much the storage as it is the transport .
Sometimes you need to send things as a flat text file with one record per line , for data exchange .
Then you start running into all sorts of problems like tabs vs spaces , field widths , line delimiters , right vs left justification , and other oddness like these separators .
Really if they wanted to do that more smartly , they 'd omit all separators in a numeric field and simply state number of pennies .
Problem solved .
Every time I 've had to put a dollar amount in a text field it 's been in pennies for this exact reason .</tokentext>
<sentencetext>And for God sake why would you want to store the number as a string any ways?It's not so much the storage as it is the transport.
Sometimes you need to send things as a flat text file with one record per line, for data exchange.
Then you start running into all sorts of problems like tabs vs spaces, field widths, line delimiters, right vs left justification, and other oddness like these separators.
Really if they wanted to do that more smartly, they'd omit all separators in a numeric field and simply state number of pennies.
Problem solved.
Every time I've had to put a dollar amount in a text field it's been in pennies for this exact reason.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257179880000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Our method makes more sense.  A sentence can have more commas than periods.  Generally sentences have just one period (i'm distinguishing between dots and periods here).  A period is a more solid division than a comma.  It makes more sense to use the stronger punctuation as the mark between whole and fraction.</p><p>i'll grant that metric is better than imperial, but i think this is one thing where we have the better idea.</p><p>It's my opinion and it's worth every penny you paid for it.</p></htmltext>
<tokenext>Our method makes more sense .
A sentence can have more commas than periods .
Generally sentences have just one period ( i 'm distinguishing between dots and periods here ) .
A period is a more solid division than a comma .
It makes more sense to use the stronger punctuation as the mark between whole and fraction.i 'll grant that metric is better than imperial , but i think this is one thing where we have the better idea.It 's my opinion and it 's worth every penny you paid for it .</tokentext>
<sentencetext>Our method makes more sense.
A sentence can have more commas than periods.
Generally sentences have just one period (i'm distinguishing between dots and periods here).
A period is a more solid division than a comma.
It makes more sense to use the stronger punctuation as the mark between whole and fraction.i'll grant that metric is better than imperial, but i think this is one thing where we have the better idea.It's my opinion and it's worth every penny you paid for it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227686</id>
	<title>Re:Good to be a programmer</title>
	<author>mr exploiter</author>
	<datestamp>1257185880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Shut the hell up. Thanks.</htmltext>
<tokenext>Shut the hell up .
Thanks .</tokentext>
<sentencetext>Shut the hell up.
Thanks.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226206</id>
	<title>Not helping!</title>
	<author>Anonymous</author>
	<datestamp>1257178740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Given the subject, surely the submitter can see why it's worth clarifying whether they're using the decimal or comma convention <i>in the summary itself</i>!</p></htmltext>
<tokenext>Given the subject , surely the submitter can see why it 's worth clarifying whether they 're using the decimal or comma convention in the summary itself !</tokentext>
<sentencetext>Given the subject, surely the submitter can see why it's worth clarifying whether they're using the decimal or comma convention in the summary itself!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227004</id>
	<title>Re:Happened to me recently</title>
	<author>eallanjr</author>
	<datestamp>1257182520000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p><div class="quote"><p>I made a similar mistake recently... I made a (.NET) data entry software</p> </div><p>Don't you mean<nobr> <wbr></nobr>,Net?</p></div>
	</htmltext>
<tokenext>I made a similar mistake recently... I made a ( .NET ) data entry software Do n't you mean ,Net ?</tokentext>
<sentencetext>I made a similar mistake recently... I made a (.NET) data entry software Don't you mean ,Net?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235460</id>
	<title>Re:God Bless the USA!</title>
	<author>Hurricane78</author>
	<datestamp>1259235420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Do you know the nightmarish hell that is an Excel...</p></div><p>You could have stopped right there. ^^</p></div>
	</htmltext>
<tokenext>Do you know the nightmarish hell that is an Excel...You could have stopped right there .
^ ^</tokentext>
<sentencetext>Do you know the nightmarish hell that is an Excel...You could have stopped right there.
^^
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226778</id>
	<title>Re:Good to be a programmer</title>
	<author>wisty</author>
	<datestamp>1257181440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"Real engineers" have all sorts of cock-ups. Look at cost-overruns in the overage one-off construction project - they are similar to overruns in software projects.</p><p>Safety-critical hardware has all sorts of redundancy. I daresay that software could have a safety factor built in - you could duplicate the code 5 times using separate software teams and different methodologies, then weed out the incorrect results, but who would pay for all that waste? Even aircraft engineers have about 1\% safety margins. Software engineers usually have 0\%. Do you wonder why it breaks occasionally?</p></htmltext>
<tokenext>" Real engineers " have all sorts of cock-ups .
Look at cost-overruns in the overage one-off construction project - they are similar to overruns in software projects.Safety-critical hardware has all sorts of redundancy .
I daresay that software could have a safety factor built in - you could duplicate the code 5 times using separate software teams and different methodologies , then weed out the incorrect results , but who would pay for all that waste ?
Even aircraft engineers have about 1 \ % safety margins .
Software engineers usually have 0 \ % .
Do you wonder why it breaks occasionally ?</tokentext>
<sentencetext>"Real engineers" have all sorts of cock-ups.
Look at cost-overruns in the overage one-off construction project - they are similar to overruns in software projects.Safety-critical hardware has all sorts of redundancy.
I daresay that software could have a safety factor built in - you could duplicate the code 5 times using separate software teams and different methodologies, then weed out the incorrect results, but who would pay for all that waste?
Even aircraft engineers have about 1\% safety margins.
Software engineers usually have 0\%.
Do you wonder why it breaks occasionally?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227514</id>
	<title>Re:Good to be a programmer</title>
	<author>Anonymous</author>
	<datestamp>1257185220000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>If you need something to be as reliable as a bridge, or a system to deliver fresh water to taps in homes, or launching a space shuttle without it blowing up; then hire an engineer.</p><p>If you want software to do some business task and the risks aren't life threatening; then hire a programmer.</p><p>Just because YOU need a big rig truck to haul your load, doesn't mean I need to be a commercial driver just to get two bags of groceries.</p></htmltext>
<tokenext>If you need something to be as reliable as a bridge , or a system to deliver fresh water to taps in homes , or launching a space shuttle without it blowing up ; then hire an engineer.If you want software to do some business task and the risks are n't life threatening ; then hire a programmer.Just because YOU need a big rig truck to haul your load , does n't mean I need to be a commercial driver just to get two bags of groceries .</tokentext>
<sentencetext>If you need something to be as reliable as a bridge, or a system to deliver fresh water to taps in homes, or launching a space shuttle without it blowing up; then hire an engineer.If you want software to do some business task and the risks aren't life threatening; then hire a programmer.Just because YOU need a big rig truck to haul your load, doesn't mean I need to be a commercial driver just to get two bags of groceries.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226284</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257179100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>As with most things, the USA is still using the same system as the UK, and it's only mainland Europe that has them reversed.  I'm not sure 'God' has anything to do with it.</p></htmltext>
<tokenext>As with most things , the USA is still using the same system as the UK , and it 's only mainland Europe that has them reversed .
I 'm not sure 'God ' has anything to do with it .</tokentext>
<sentencetext>As with most things, the USA is still using the same system as the UK, and it's only mainland Europe that has them reversed.
I'm not sure 'God' has anything to do with it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228230</id>
	<title>Re:Good to be a programmer</title>
	<author>Anonymous</author>
	<datestamp>1257188400000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Valid point, but you forget that, in software, you also have to engineer around stupid people.  The engineer who designs a wood-chipper doesn't need to worry about someone putting a 4" thick steel rod in there, because it would void the goddamn warranty, just like putting the decimal in the wrong place for an ATM withdrawl should void the goddamn warranty.</p></htmltext>
<tokenext>Valid point , but you forget that , in software , you also have to engineer around stupid people .
The engineer who designs a wood-chipper does n't need to worry about someone putting a 4 " thick steel rod in there , because it would void the goddamn warranty , just like putting the decimal in the wrong place for an ATM withdrawl should void the goddamn warranty .</tokentext>
<sentencetext>Valid point, but you forget that, in software, you also have to engineer around stupid people.
The engineer who designs a wood-chipper doesn't need to worry about someone putting a 4" thick steel rod in there, because it would void the goddamn warranty, just like putting the decimal in the wrong place for an ATM withdrawl should void the goddamn warranty.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257180120000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><i>I never understood why the hell Europeans swap periods and commas. Grammatically it doesn't even make sense...A period ends a sentence or statement, which to me should imply a whole number. A comma is simply a separator, used within sentences. So why would it be used to separate decimals?</i>
<br> <br>
See, that argument doesn't make 'sense' either. If a comma is a separator, why not use it to separate decimals? Answer: no reason, it is completely and utterly arbitrary. You're arguing that the point of view you're used to is somehow intrinsicly 'right' - it isn't, it's just usage and custom.
<br> <br>
<i>It would be like writing a sentence this way:</i>
<br> <br>
Somehow, I suspect mainland Europe knows what it's like to write a sentence including thousands sperators and decimal separators...
<br> <br>
I'm British - I use "," to separate thousands and "." to separate decimals, but that doesn't make me 'right' - it really is just usage and custom, there isn't anything to really recommend one way over the other.
<br> <br>
Cheers,<br>
Ian</htmltext>
<tokenext>I never understood why the hell Europeans swap periods and commas .
Grammatically it does n't even make sense...A period ends a sentence or statement , which to me should imply a whole number .
A comma is simply a separator , used within sentences .
So why would it be used to separate decimals ?
See , that argument does n't make 'sense ' either .
If a comma is a separator , why not use it to separate decimals ?
Answer : no reason , it is completely and utterly arbitrary .
You 're arguing that the point of view you 're used to is somehow intrinsicly 'right ' - it is n't , it 's just usage and custom .
It would be like writing a sentence this way : Somehow , I suspect mainland Europe knows what it 's like to write a sentence including thousands sperators and decimal separators.. . I 'm British - I use " , " to separate thousands and " .
" to separate decimals , but that does n't make me 'right ' - it really is just usage and custom , there is n't anything to really recommend one way over the other .
Cheers , Ian</tokentext>
<sentencetext>I never understood why the hell Europeans swap periods and commas.
Grammatically it doesn't even make sense...A period ends a sentence or statement, which to me should imply a whole number.
A comma is simply a separator, used within sentences.
So why would it be used to separate decimals?
See, that argument doesn't make 'sense' either.
If a comma is a separator, why not use it to separate decimals?
Answer: no reason, it is completely and utterly arbitrary.
You're arguing that the point of view you're used to is somehow intrinsicly 'right' - it isn't, it's just usage and custom.
It would be like writing a sentence this way:
 
Somehow, I suspect mainland Europe knows what it's like to write a sentence including thousands sperators and decimal separators...
 
I'm British - I use "," to separate thousands and ".
" to separate decimals, but that doesn't make me 'right' - it really is just usage and custom, there isn't anything to really recommend one way over the other.
Cheers,
Ian</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226590</id>
	<title>Re:For the most part.</title>
	<author>Duhavid</author>
	<datestamp>1257180600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>BCD is an option.</p></htmltext>
<tokenext>BCD is an option .</tokentext>
<sentencetext>BCD is an option.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228240</id>
	<title>Re:Happened to me recently</title>
	<author>Anonymous</author>
	<datestamp>1257188460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Advice?</p><p>Give an input example to the user, generated using the CultureInfo, because the user will probably forget what is set for them (or they're using a different computer to their normal one).</p><p>E.g., Enter Amount: #[\_\_\_\_\_\_\_\_\_] (e.g., #400,75)</p></htmltext>
<tokenext>Advice ? Give an input example to the user , generated using the CultureInfo , because the user will probably forget what is set for them ( or they 're using a different computer to their normal one ) .E.g. , Enter Amount : # [ \ _ \ _ \ _ \ _ \ _ \ _ \ _ \ _ \ _ ] ( e.g. , # 400,75 )</tokentext>
<sentencetext>Advice?Give an input example to the user, generated using the CultureInfo, because the user will probably forget what is set for them (or they're using a different computer to their normal one).E.g., Enter Amount: #[\_\_\_\_\_\_\_\_\_] (e.g., #400,75)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228310</id>
	<title>Re:Good to be a programmer</title>
	<author>scamper\_22</author>
	<datestamp>1257188820000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>well I'm a 'formal' engineer... but let's be frank here.</p><p>The world has not come to an end.<br>The accounts will be fixed.<br>The clients will not lose any money.</p><p>Yeah, nothing would make me happy than requiring every line of software to be written by a real engineer with responsibilities, but it's more for my benefit than society's (job security, competent colleagues..  you know how doctors and lawyers do it).</p><p>In the end, society is making the trade offs.<br>Society is choosing to have features developed faster than a proper 'engineer' would implement them.<br>Society is choosing to lower the cost of programs at the expense of quality.<br>Society is choosing to deal with the results of bad quality instead of paying up front for quality engineers.</p><p>There is no 'right' and 'wrong' with these choices for society.  It's easy to see the loss of quality.  It's harder to see the loss of opportunity.</p><p>For example, you can say that only doctors should be able to prescribe medications for 'quality' reasons.  Sure, it is easy to find an example where someone took a medicine they were not supposed to and it cost them their health.  No doubt such a thing would make the news.  Yet what about the missed opportunity?  The person who doesn't see a doctor at all due to cost?  Or the doctor who is too busy to properly diagnose and care for patients?  Would society actually end up better off if less qualified people like nurses could prescribe medications?  I'll leave that an open question.</p><p>I'll trivialize the issue even further.  I've started seeing self-checkouts at many places.<br>Now you can most certainly pay for quality of process and make sure no body steals.<br>But that's not what the store/people care about.  The store only cares about the following:</p><p>if( savings\_from\_no\_cashiers &gt; additional\_money\_lost\_to\_theft )<br>{<br>
&nbsp; &nbsp; &nbsp; &nbsp; cout  "we made a good decision"  endl;<br>}</p><p>And so it is with this bank.  If they can deliver cheap systems with unregulated programmers that work without anything systemically catastrophic happening, why would they not?  They will pay the cost to fix their mistake and maybe even lose business as customers loss faith in that bank.</p></htmltext>
<tokenext>well I 'm a 'formal ' engineer... but let 's be frank here.The world has not come to an end.The accounts will be fixed.The clients will not lose any money.Yeah , nothing would make me happy than requiring every line of software to be written by a real engineer with responsibilities , but it 's more for my benefit than society 's ( job security , competent colleagues.. you know how doctors and lawyers do it ) .In the end , society is making the trade offs.Society is choosing to have features developed faster than a proper 'engineer ' would implement them.Society is choosing to lower the cost of programs at the expense of quality.Society is choosing to deal with the results of bad quality instead of paying up front for quality engineers.There is no 'right ' and 'wrong ' with these choices for society .
It 's easy to see the loss of quality .
It 's harder to see the loss of opportunity.For example , you can say that only doctors should be able to prescribe medications for 'quality ' reasons .
Sure , it is easy to find an example where someone took a medicine they were not supposed to and it cost them their health .
No doubt such a thing would make the news .
Yet what about the missed opportunity ?
The person who does n't see a doctor at all due to cost ?
Or the doctor who is too busy to properly diagnose and care for patients ?
Would society actually end up better off if less qualified people like nurses could prescribe medications ?
I 'll leave that an open question.I 'll trivialize the issue even further .
I 've started seeing self-checkouts at many places.Now you can most certainly pay for quality of process and make sure no body steals.But that 's not what the store/people care about .
The store only cares about the following : if ( savings \ _from \ _no \ _cashiers &gt; additional \ _money \ _lost \ _to \ _theft ) {         cout " we made a good decision " endl ; } And so it is with this bank .
If they can deliver cheap systems with unregulated programmers that work without anything systemically catastrophic happening , why would they not ?
They will pay the cost to fix their mistake and maybe even lose business as customers loss faith in that bank .</tokentext>
<sentencetext>well I'm a 'formal' engineer... but let's be frank here.The world has not come to an end.The accounts will be fixed.The clients will not lose any money.Yeah, nothing would make me happy than requiring every line of software to be written by a real engineer with responsibilities, but it's more for my benefit than society's (job security, competent colleagues..  you know how doctors and lawyers do it).In the end, society is making the trade offs.Society is choosing to have features developed faster than a proper 'engineer' would implement them.Society is choosing to lower the cost of programs at the expense of quality.Society is choosing to deal with the results of bad quality instead of paying up front for quality engineers.There is no 'right' and 'wrong' with these choices for society.
It's easy to see the loss of quality.
It's harder to see the loss of opportunity.For example, you can say that only doctors should be able to prescribe medications for 'quality' reasons.
Sure, it is easy to find an example where someone took a medicine they were not supposed to and it cost them their health.
No doubt such a thing would make the news.
Yet what about the missed opportunity?
The person who doesn't see a doctor at all due to cost?
Or the doctor who is too busy to properly diagnose and care for patients?
Would society actually end up better off if less qualified people like nurses could prescribe medications?
I'll leave that an open question.I'll trivialize the issue even further.
I've started seeing self-checkouts at many places.Now you can most certainly pay for quality of process and make sure no body steals.But that's not what the store/people care about.
The store only cares about the following:if( savings\_from\_no\_cashiers &gt; additional\_money\_lost\_to\_theft ){
        cout  "we made a good decision"  endl;}And so it is with this bank.
If they can deliver cheap systems with unregulated programmers that work without anything systemically catastrophic happening, why would they not?
They will pay the cost to fix their mistake and maybe even lose business as customers loss faith in that bank.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228164</id>
	<title>Re:For the most part.</title>
	<author>corbettw</author>
	<datestamp>1257188100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Sure, you laugh now. But just wait until Obama and Bernanke are done destroying our currency and that number will be the going rate for a contract programmer!</p></htmltext>
<tokenext>Sure , you laugh now .
But just wait until Obama and Bernanke are done destroying our currency and that number will be the going rate for a contract programmer !</tokentext>
<sentencetext>Sure, you laugh now.
But just wait until Obama and Bernanke are done destroying our currency and that number will be the going rate for a contract programmer!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226994</id>
	<title>Re:Good to be a programmer</title>
	<author>samael</author>
	<datestamp>1257182460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Not the programmer's fault.</p><p>If it wasn't properly specified and it wasn't properly tested then it's the fault of management for not making sure that processes were followed.</p><p>Mistakes happen - if they aren't picked up then it's the fault of the process.</p></htmltext>
<tokenext>Not the programmer 's fault.If it was n't properly specified and it was n't properly tested then it 's the fault of management for not making sure that processes were followed.Mistakes happen - if they are n't picked up then it 's the fault of the process .</tokentext>
<sentencetext>Not the programmer's fault.If it wasn't properly specified and it wasn't properly tested then it's the fault of management for not making sure that processes were followed.Mistakes happen - if they aren't picked up then it's the fault of the process.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228264</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257188580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I agree, and have another reason as well. The comma is directional since it has length, so it encourages movement in the direction we're reading (aesthetics 101), whereas a period is static in shape with no direction, thus stopping the eye.</p><p>From an aesthetics perspective, the Euro standard is ridiculous as it's counter to the natural reaction to shapes. Of course, culture can overcome this, but why?</p></htmltext>
<tokenext>I agree , and have another reason as well .
The comma is directional since it has length , so it encourages movement in the direction we 're reading ( aesthetics 101 ) , whereas a period is static in shape with no direction , thus stopping the eye.From an aesthetics perspective , the Euro standard is ridiculous as it 's counter to the natural reaction to shapes .
Of course , culture can overcome this , but why ?</tokentext>
<sentencetext>I agree, and have another reason as well.
The comma is directional since it has length, so it encourages movement in the direction we're reading (aesthetics 101), whereas a period is static in shape with no direction, thus stopping the eye.From an aesthetics perspective, the Euro standard is ridiculous as it's counter to the natural reaction to shapes.
Of course, culture can overcome this, but why?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226830</id>
	<title>Re:Decimal and Thousands separators</title>
	<author>Anonymous</author>
	<datestamp>1257181680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I would pay 100000000000 dollars for this to be the case.</p><p>Oh, you meant something like:<br>1&#166;000&#166;000&#166;000&#166;000 dollars</p></htmltext>
<tokenext>I would pay 100000000000 dollars for this to be the case.Oh , you meant something like : 1   000   000   000   000 dollars</tokentext>
<sentencetext>I would pay 100000000000 dollars for this to be the case.Oh, you meant something like:1¦000¦000¦000¦000 dollars</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226468</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226302</id>
	<title>Re:For the most part.</title>
	<author>Anonymous</author>
	<datestamp>1257179220000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>This is the same in my bank, if you type in . it gives an error. In addition it requires you to type in the<nobr> <wbr></nobr>,00 too, and next to the sum text box is an example like "150,00".</p><p>Having comma/decimal as a separator is stupid anyway, space does just fine - 150 000.35</p></htmltext>
<tokenext>This is the same in my bank , if you type in .
it gives an error .
In addition it requires you to type in the ,00 too , and next to the sum text box is an example like " 150,00 " .Having comma/decimal as a separator is stupid anyway , space does just fine - 150 000.35</tokentext>
<sentencetext>This is the same in my bank, if you type in .
it gives an error.
In addition it requires you to type in the ,00 too, and next to the sum text box is an example like "150,00".Having comma/decimal as a separator is stupid anyway, space does just fine - 150 000.35</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230170</id>
	<title>Re:Periods and commas.</title>
	<author>Carewolf</author>
	<datestamp>1257154200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's not a arguement at all, but I've seen it repeated here a lot of times. I am assuming it is a memory tool, used to teach small children, not something anyone actually believes.</p><p>Comma has always been the decimal separator, was it before computer was it before typesetting, it even was the decimal separator in America. A vertical comma for decimal a smaller tilted one to separate thousands. Americans choose a standard for thousand separators first and chose comma, leaving them with no other option than dot for the decimal, even though it neither made any sense nor matched common practise. The English copied that error much later.</p></htmltext>
<tokenext>It 's not a arguement at all , but I 've seen it repeated here a lot of times .
I am assuming it is a memory tool , used to teach small children , not something anyone actually believes.Comma has always been the decimal separator , was it before computer was it before typesetting , it even was the decimal separator in America .
A vertical comma for decimal a smaller tilted one to separate thousands .
Americans choose a standard for thousand separators first and chose comma , leaving them with no other option than dot for the decimal , even though it neither made any sense nor matched common practise .
The English copied that error much later .</tokentext>
<sentencetext>It's not a arguement at all, but I've seen it repeated here a lot of times.
I am assuming it is a memory tool, used to teach small children, not something anyone actually believes.Comma has always been the decimal separator, was it before computer was it before typesetting, it even was the decimal separator in America.
A vertical comma for decimal a smaller tilted one to separate thousands.
Americans choose a standard for thousand separators first and chose comma, leaving them with no other option than dot for the decimal, even though it neither made any sense nor matched common practise.
The English copied that error much later.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227420</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226808</id>
	<title>Re:God Bless the USA!</title>
	<author>camperdave</author>
	<datestamp>1257181500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Hey!  We have to distinguish ourselves from Americans somehow.  Using Canadian Tire money just wasn't cutting it.</htmltext>
<tokenext>Hey !
We have to distinguish ourselves from Americans somehow .
Using Canadian Tire money just was n't cutting it .</tokentext>
<sentencetext>Hey!
We have to distinguish ourselves from Americans somehow.
Using Canadian Tire money just wasn't cutting it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226556</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229506</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257194040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Numbers should be separated by decimal points, not full stops.<br>Look at a decent maths book from the 1960s and you will see divide signs &divide; instead of slash /<br>And 11500 is prettier and less ambiguous than 115.00<br>Sadly slashdot does not display it correctly and strips out the "middle dot".</p><p>
&nbsp;</p></htmltext>
<tokenext>Numbers should be separated by decimal points , not full stops.Look at a decent maths book from the 1960s and you will see divide signs   instead of slash /And 11500 is prettier and less ambiguous than 115.00Sadly slashdot does not display it correctly and strips out the " middle dot " .
 </tokentext>
<sentencetext>Numbers should be separated by decimal points, not full stops.Look at a decent maths book from the 1960s and you will see divide signs ÷ instead of slash /And 11500 is prettier and less ambiguous than 115.00Sadly slashdot does not display it correctly and strips out the "middle dot".
 </sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227420</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228458</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257189540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Agreed. But you Americans also write the date wrong. Day-month-year, please!</p></htmltext>
<tokenext>Agreed .
But you Americans also write the date wrong .
Day-month-year , please !</tokentext>
<sentencetext>Agreed.
But you Americans also write the date wrong.
Day-month-year, please!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30241764</id>
	<title>Re:Periods and commas.</title>
	<author>shutdown -p now</author>
	<datestamp>1259247900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>In matters of custom, the more universally recognized method is the right one. Everyone knows what 1,054.65 means.</p></div><p>I can assure you that it's not the case. Most people in Russia, for example, would recognize decimal point for what it is, but they would be utterly confused if they saw a comma as a group separator.</p></div>
	</htmltext>
<tokenext>In matters of custom , the more universally recognized method is the right one .
Everyone knows what 1,054.65 means.I can assure you that it 's not the case .
Most people in Russia , for example , would recognize decimal point for what it is , but they would be utterly confused if they saw a comma as a group separator .</tokentext>
<sentencetext>In matters of custom, the more universally recognized method is the right one.
Everyone knows what 1,054.65 means.I can assure you that it's not the case.
Most people in Russia, for example, would recognize decimal point for what it is, but they would be utterly confused if they saw a comma as a group separator.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226748</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229732</id>
	<title>Re:Happened to me recently</title>
	<author>Anonymous</author>
	<datestamp>1257195180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>You've got to handle that problem at the application layer, preferably as soon as possible.</p></div><p>as soon as possible = at the design phase. The simple solution: separate fields for the whole units and the fractions and only allow numeric input. That is what banks usually do in there online payment systems.<br>Maybe not very convenient but it rules out all possibilities for mistakes that the bank could possibly be held accountable for. (like assuming that 1,000 or 1.000 means "one thousand" while the customer just entered a "0" to much by accident and actually meant "one")</p></div>
	</htmltext>
<tokenext>You 've got to handle that problem at the application layer , preferably as soon as possible.as soon as possible = at the design phase .
The simple solution : separate fields for the whole units and the fractions and only allow numeric input .
That is what banks usually do in there online payment systems.Maybe not very convenient but it rules out all possibilities for mistakes that the bank could possibly be held accountable for .
( like assuming that 1,000 or 1.000 means " one thousand " while the customer just entered a " 0 " to much by accident and actually meant " one " )</tokentext>
<sentencetext>You've got to handle that problem at the application layer, preferably as soon as possible.as soon as possible = at the design phase.
The simple solution: separate fields for the whole units and the fractions and only allow numeric input.
That is what banks usually do in there online payment systems.Maybe not very convenient but it rules out all possibilities for mistakes that the bank could possibly be held accountable for.
(like assuming that 1,000 or 1.000 means "one thousand" while the customer just entered a "0" to much by accident and actually meant "one")
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227308</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231584</id>
	<title>Re:Good to be a programmer</title>
	<author>Stevecrox</author>
	<datestamp>1257163320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The problem comparing "real engineers" against software engineering that Software is completely different from Electronics/Mechanics/Civil/etc.... <br> <br>
The first issue is implementation, my final year project with a mass storage Bluetooth device, designing and building the 8052 micro-controller board took weeks and it took days to fabricate. Minor changes delayed me by weeks. Taking the time to design and test the system before implementation was a must because early mistakes cost a lot. <br>In comparison I recently added functionality to an application, I set a series of requirements from our system level ones and built the feature up. By the time I had finished adding the feature our customers and management saw the potential of it and rapidly expanded the requirements. It took 1 day to make the modification required for the change in requirements. Software is seen as inherently flexible and it is. The problem is because of its flexibility it's hard to maintain proper design methodology. Why do you need to spend hours making a UML design for something that will take you a quarter the time to code and will most likely change before your finished?<br> <br>
Safety critical near perfect code can be produced but it costs an insane amount of money and isn't necessarily appropriate for every task (e.g. Windows Calculator does not need to be anywhere near to that level). But what level and standard does the code need to be at? Pick any of the two: Fast, Good and Cheap.<br> <br>
Software Engineering also has 1 other major difference to traditional engineering in that the majority of the cost is linked to people and not materials. Using a bridge as an example if the bridge is overrunning cheaper materials can be found, but cheaper people in Software are often less productive. In traditional engineering if a project is late you can throw more money and people and construction etc.. will increase. Software projects don't work that way, increasing staff will cause a temporary decrease in productivity while new staff learn the system and not all problems can be shared.<br> <br>
It's easy to mock software engineering (I know I felt that way when I finished by EEE based course), but Software Engineering a quite a different beast to traditional engineering. I'd also like to see groups like the IET or BCS qualify people to be Software Engineers but I doubt that will happen I did a IET approved degree course but as far as I can tell I might as well completed one of the easier non approved courses (One uni was proud it had no exams for instance)and it would mean exactly the same to the IET and when I was a member the only difference I noticed was a monthly magazine. As long as that sort of attitude/response exists I can't see professional membership really being taken up.<br> <br>
As for the engineers responsible seeing no consequence for this failure? That seems unlikely to me, I wouldn't be surprised if someone lost their job as a result of this.</htmltext>
<tokenext>The problem comparing " real engineers " against software engineering that Software is completely different from Electronics/Mechanics/Civil/etc... . The first issue is implementation , my final year project with a mass storage Bluetooth device , designing and building the 8052 micro-controller board took weeks and it took days to fabricate .
Minor changes delayed me by weeks .
Taking the time to design and test the system before implementation was a must because early mistakes cost a lot .
In comparison I recently added functionality to an application , I set a series of requirements from our system level ones and built the feature up .
By the time I had finished adding the feature our customers and management saw the potential of it and rapidly expanded the requirements .
It took 1 day to make the modification required for the change in requirements .
Software is seen as inherently flexible and it is .
The problem is because of its flexibility it 's hard to maintain proper design methodology .
Why do you need to spend hours making a UML design for something that will take you a quarter the time to code and will most likely change before your finished ?
Safety critical near perfect code can be produced but it costs an insane amount of money and is n't necessarily appropriate for every task ( e.g .
Windows Calculator does not need to be anywhere near to that level ) .
But what level and standard does the code need to be at ?
Pick any of the two : Fast , Good and Cheap .
Software Engineering also has 1 other major difference to traditional engineering in that the majority of the cost is linked to people and not materials .
Using a bridge as an example if the bridge is overrunning cheaper materials can be found , but cheaper people in Software are often less productive .
In traditional engineering if a project is late you can throw more money and people and construction etc.. will increase .
Software projects do n't work that way , increasing staff will cause a temporary decrease in productivity while new staff learn the system and not all problems can be shared .
It 's easy to mock software engineering ( I know I felt that way when I finished by EEE based course ) , but Software Engineering a quite a different beast to traditional engineering .
I 'd also like to see groups like the IET or BCS qualify people to be Software Engineers but I doubt that will happen I did a IET approved degree course but as far as I can tell I might as well completed one of the easier non approved courses ( One uni was proud it had no exams for instance ) and it would mean exactly the same to the IET and when I was a member the only difference I noticed was a monthly magazine .
As long as that sort of attitude/response exists I ca n't see professional membership really being taken up .
As for the engineers responsible seeing no consequence for this failure ?
That seems unlikely to me , I would n't be surprised if someone lost their job as a result of this .</tokentext>
<sentencetext>The problem comparing "real engineers" against software engineering that Software is completely different from Electronics/Mechanics/Civil/etc....  
The first issue is implementation, my final year project with a mass storage Bluetooth device, designing and building the 8052 micro-controller board took weeks and it took days to fabricate.
Minor changes delayed me by weeks.
Taking the time to design and test the system before implementation was a must because early mistakes cost a lot.
In comparison I recently added functionality to an application, I set a series of requirements from our system level ones and built the feature up.
By the time I had finished adding the feature our customers and management saw the potential of it and rapidly expanded the requirements.
It took 1 day to make the modification required for the change in requirements.
Software is seen as inherently flexible and it is.
The problem is because of its flexibility it's hard to maintain proper design methodology.
Why do you need to spend hours making a UML design for something that will take you a quarter the time to code and will most likely change before your finished?
Safety critical near perfect code can be produced but it costs an insane amount of money and isn't necessarily appropriate for every task (e.g.
Windows Calculator does not need to be anywhere near to that level).
But what level and standard does the code need to be at?
Pick any of the two: Fast, Good and Cheap.
Software Engineering also has 1 other major difference to traditional engineering in that the majority of the cost is linked to people and not materials.
Using a bridge as an example if the bridge is overrunning cheaper materials can be found, but cheaper people in Software are often less productive.
In traditional engineering if a project is late you can throw more money and people and construction etc.. will increase.
Software projects don't work that way, increasing staff will cause a temporary decrease in productivity while new staff learn the system and not all problems can be shared.
It's easy to mock software engineering (I know I felt that way when I finished by EEE based course), but Software Engineering a quite a different beast to traditional engineering.
I'd also like to see groups like the IET or BCS qualify people to be Software Engineers but I doubt that will happen I did a IET approved degree course but as far as I can tell I might as well completed one of the easier non approved courses (One uni was proud it had no exams for instance)and it would mean exactly the same to the IET and when I was a member the only difference I noticed was a monthly magazine.
As long as that sort of attitude/response exists I can't see professional membership really being taken up.
As for the engineers responsible seeing no consequence for this failure?
That seems unlikely to me, I wouldn't be surprised if someone lost their job as a result of this.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226720</id>
	<title>testing is the issue</title>
	<author>maxwells daemon</author>
	<datestamp>1257181200000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>This is not a representation issue.  It is a project management and testing issue.</p></htmltext>
<tokenext>This is not a representation issue .
It is a project management and testing issue .</tokentext>
<sentencetext>This is not a representation issue.
It is a project management and testing issue.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226332</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257179400000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>I think you mean "God Save the Queen". We (the British) gave you the correct method for decimals before we decided to let you have the place. You've managed to pick up a few bad habits from the French, such as driving on the right.</p><p>But apart from that, you're doing quite well.</p><p>(For the benefit of Australians, this is humour, not flamebait.)</p></htmltext>
<tokenext>I think you mean " God Save the Queen " .
We ( the British ) gave you the correct method for decimals before we decided to let you have the place .
You 've managed to pick up a few bad habits from the French , such as driving on the right.But apart from that , you 're doing quite well .
( For the benefit of Australians , this is humour , not flamebait .
)</tokentext>
<sentencetext>I think you mean "God Save the Queen".
We (the British) gave you the correct method for decimals before we decided to let you have the place.
You've managed to pick up a few bad habits from the French, such as driving on the right.But apart from that, you're doing quite well.
(For the benefit of Australians, this is humour, not flamebait.
)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227120</id>
	<title>Re:For the most part.</title>
	<author>Anonymous</author>
	<datestamp>1257183120000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>So you've obviously never coded an intrabank transfer system then. Packed decimal (using COBOL or PL/1) is the way to go...</p></htmltext>
<tokenext>So you 've obviously never coded an intrabank transfer system then .
Packed decimal ( using COBOL or PL/1 ) is the way to go.. .</tokentext>
<sentencetext>So you've obviously never coded an intrabank transfer system then.
Packed decimal (using COBOL or PL/1) is the way to go...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356</id>
	<title>Re:For the most part.</title>
	<author>sopssa</author>
	<datestamp>1257179580000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>int64 Unsigned: 0 to +18,446,744,073,709,551,615</p><p>You mean I cannot transfer my 18 quintillion, 446 quadrillion, 744 trillion, 73 billion, 709 million, 551 thousand and 615 dollars (or in easier words 18 billion billion dollars) as a single transfer from my banking account? I need to do two of them? This is outrageous!</p></htmltext>
<tokenext>int64 Unsigned : 0 to + 18,446,744,073,709,551,615You mean I can not transfer my 18 quintillion , 446 quadrillion , 744 trillion , 73 billion , 709 million , 551 thousand and 615 dollars ( or in easier words 18 billion billion dollars ) as a single transfer from my banking account ?
I need to do two of them ?
This is outrageous !</tokentext>
<sentencetext>int64 Unsigned: 0 to +18,446,744,073,709,551,615You mean I cannot transfer my 18 quintillion, 446 quadrillion, 744 trillion, 73 billion, 709 million, 551 thousand and 615 dollars (or in easier words 18 billion billion dollars) as a single transfer from my banking account?
I need to do two of them?
This is outrageous!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227414</id>
	<title>Re:God Bless the USA!</title>
	<author>MartinSchou</author>
	<datestamp>1257184740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Whether you use a comma or a period is very unlikely to have anything to do with "logic", and more to do with language.</p><p>Two and a half in English: "Two point five"/2.5<br>Two and a half in Danish: "To komma fem"/2,5<br>Two and a half in Swedish: "Tv&#229; komma fem"/2,5<br>Two and a half in German: "Zwei komma f&#252;nf"/2,5</p><p>My German is rather rusty, but I think it's correct.</p><p>My point is, that when the language uses comma, it makes no sense not using it for maths. People just need to know how to translate from different language. This last bit is an issue though. Especially when you're dealing with incredibly lazy journalists who don't know how to read numbers and just copy paste stuff.</p><p>It's always fun to see Danish newspapers report on the <a href="http://en.wikipedia.org/wiki/Us\_budget" title="wikipedia.org">US federal budget</a> [wikipedia.org].</p><p>Total: 2.979 trillion dollars (2,979 billion or 2,979,000,000,000). In Danish, however, that number (2.979 trillion) is a LOT bigger. In part because we use the . as a thousands separator, and in part because we use long numbers. In other words 2.979 trillion dollars in Danish is 2 979 000 000 000 000 000.</p><p>When you have these lazy reporters, things get interesting. They MIGHT stop and wonder a bit about that number, as it is huge. But a number like 2.979 million might just go through without being translated. Same with 2.979 billion.</p></htmltext>
<tokenext>Whether you use a comma or a period is very unlikely to have anything to do with " logic " , and more to do with language.Two and a half in English : " Two point five " /2.5Two and a half in Danish : " To komma fem " /2,5Two and a half in Swedish : " Tv   komma fem " /2,5Two and a half in German : " Zwei komma f   nf " /2,5My German is rather rusty , but I think it 's correct.My point is , that when the language uses comma , it makes no sense not using it for maths .
People just need to know how to translate from different language .
This last bit is an issue though .
Especially when you 're dealing with incredibly lazy journalists who do n't know how to read numbers and just copy paste stuff.It 's always fun to see Danish newspapers report on the US federal budget [ wikipedia.org ] .Total : 2.979 trillion dollars ( 2,979 billion or 2,979,000,000,000 ) .
In Danish , however , that number ( 2.979 trillion ) is a LOT bigger .
In part because we use the .
as a thousands separator , and in part because we use long numbers .
In other words 2.979 trillion dollars in Danish is 2 979 000 000 000 000 000.When you have these lazy reporters , things get interesting .
They MIGHT stop and wonder a bit about that number , as it is huge .
But a number like 2.979 million might just go through without being translated .
Same with 2.979 billion .</tokentext>
<sentencetext>Whether you use a comma or a period is very unlikely to have anything to do with "logic", and more to do with language.Two and a half in English: "Two point five"/2.5Two and a half in Danish: "To komma fem"/2,5Two and a half in Swedish: "Två komma fem"/2,5Two and a half in German: "Zwei komma fünf"/2,5My German is rather rusty, but I think it's correct.My point is, that when the language uses comma, it makes no sense not using it for maths.
People just need to know how to translate from different language.
This last bit is an issue though.
Especially when you're dealing with incredibly lazy journalists who don't know how to read numbers and just copy paste stuff.It's always fun to see Danish newspapers report on the US federal budget [wikipedia.org].Total: 2.979 trillion dollars (2,979 billion or 2,979,000,000,000).
In Danish, however, that number (2.979 trillion) is a LOT bigger.
In part because we use the .
as a thousands separator, and in part because we use long numbers.
In other words 2.979 trillion dollars in Danish is 2 979 000 000 000 000 000.When you have these lazy reporters, things get interesting.
They MIGHT stop and wonder a bit about that number, as it is huge.
But a number like 2.979 million might just go through without being translated.
Same with 2.979 billion.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228236</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257188460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Actually using a demimal comma makes more sence than the decimal point. Here's why:</p><p>The comma is bigger, easier to notice, and in general stands out much more than the point. That's why it makes sence to seperate the decimals with the comma, and the thousands with small, unobtrusive points to make the number more readable while they could also be left out.</p></htmltext>
<tokenext>Actually using a demimal comma makes more sence than the decimal point .
Here 's why : The comma is bigger , easier to notice , and in general stands out much more than the point .
That 's why it makes sence to seperate the decimals with the comma , and the thousands with small , unobtrusive points to make the number more readable while they could also be left out .</tokentext>
<sentencetext>Actually using a demimal comma makes more sence than the decimal point.
Here's why:The comma is bigger, easier to notice, and in general stands out much more than the point.
That's why it makes sence to seperate the decimals with the comma, and the thousands with small, unobtrusive points to make the number more readable while they could also be left out.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230360</id>
	<title>How is parent not flamebait?</title>
	<author>raddan</author>
	<datestamp>1257155220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>An engineer can slap a piece of paper on a building that says "if it falls, it ain't our fault" just as a programmer can claim no liability for software.  In both cases, saying such a thing does not make it so.  The big difference is that most bugs in most software doesn't have the potential to kill people.
<br> <br>
If you're a programmer and you work on a critical system, you bet your ass you can be held liable!  Where in the article does it say that the programmers will be shielded from consequences?</htmltext>
<tokenext>An engineer can slap a piece of paper on a building that says " if it falls , it ai n't our fault " just as a programmer can claim no liability for software .
In both cases , saying such a thing does not make it so .
The big difference is that most bugs in most software does n't have the potential to kill people .
If you 're a programmer and you work on a critical system , you bet your ass you can be held liable !
Where in the article does it say that the programmers will be shielded from consequences ?</tokentext>
<sentencetext>An engineer can slap a piece of paper on a building that says "if it falls, it ain't our fault" just as a programmer can claim no liability for software.
In both cases, saying such a thing does not make it so.
The big difference is that most bugs in most software doesn't have the potential to kill people.
If you're a programmer and you work on a critical system, you bet your ass you can be held liable!
Where in the article does it say that the programmers will be shielded from consequences?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228040</id>
	<title>History do not care for sense</title>
	<author>aepervius</author>
	<datestamp>1257187440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>from wiki ond ecimal separator : "In the Middle Ages, before printing, a bar (  ) over the units digit was used to separate the integral part of a number from its fractional part, a tradition derived from the decimal system used in Indian mathematics.[1] Its regular usage and classification can be attributed to the Iranian mathematician Al-Khwarizmi. Later, a separator () (a short, roughly vertical, ink stroke) between the units and tenths position became the norm. When this character was typeset, it was convenient to use the existing comma (,) or period (.) instead."
<br> <br>

If you look at the countries  using the comma, it is actually historically that they used something similar as shown above. Mostly latin countries and europe use comma, north america and asia use period. <br> <br>
<i>In France, the period was already in use in printing to make Roman numerals more readable, so the comma was chosen. Many other countries also chose to use the comma to mark the decimal units position.[2] It has been made standard by the ISO for international blueprints. However, English-speaking countries took the comma to separate sequences of three digits.</i> <br> <br> See : comma is an ISO standard. So using periosd made no sense<nobr> <wbr></nobr>:). Tit for tat, pot, kettle, your psot not being so insgihtful etc...</htmltext>
<tokenext>from wiki ond ecimal separator : " In the Middle Ages , before printing , a bar ( ) over the units digit was used to separate the integral part of a number from its fractional part , a tradition derived from the decimal system used in Indian mathematics .
[ 1 ] Its regular usage and classification can be attributed to the Iranian mathematician Al-Khwarizmi .
Later , a separator ( ) ( a short , roughly vertical , ink stroke ) between the units and tenths position became the norm .
When this character was typeset , it was convenient to use the existing comma ( , ) or period ( .
) instead .
" If you look at the countries using the comma , it is actually historically that they used something similar as shown above .
Mostly latin countries and europe use comma , north america and asia use period .
In France , the period was already in use in printing to make Roman numerals more readable , so the comma was chosen .
Many other countries also chose to use the comma to mark the decimal units position .
[ 2 ] It has been made standard by the ISO for international blueprints .
However , English-speaking countries took the comma to separate sequences of three digits .
See : comma is an ISO standard .
So using periosd made no sense : ) .
Tit for tat , pot , kettle , your psot not being so insgihtful etc.. .</tokentext>
<sentencetext>from wiki ond ecimal separator : "In the Middle Ages, before printing, a bar (  ) over the units digit was used to separate the integral part of a number from its fractional part, a tradition derived from the decimal system used in Indian mathematics.
[1] Its regular usage and classification can be attributed to the Iranian mathematician Al-Khwarizmi.
Later, a separator () (a short, roughly vertical, ink stroke) between the units and tenths position became the norm.
When this character was typeset, it was convenient to use the existing comma (,) or period (.
) instead.
"
 

If you look at the countries  using the comma, it is actually historically that they used something similar as shown above.
Mostly latin countries and europe use comma, north america and asia use period.
In France, the period was already in use in printing to make Roman numerals more readable, so the comma was chosen.
Many other countries also chose to use the comma to mark the decimal units position.
[2] It has been made standard by the ISO for international blueprints.
However, English-speaking countries took the comma to separate sequences of three digits.
See : comma is an ISO standard.
So using periosd made no sense :).
Tit for tat, pot, kettle, your psot not being so insgihtful etc...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228246</id>
	<title>Re:For the most part.</title>
	<author>TheRaven64</author>
	<datestamp>1257188460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Note that the range isn't quite that great.  First, most banking systems need to be able to handle negative values, which loses you one bit.  Then you need to store cents as well as dollars, which loses you another 6.  For interest calculations, you need at least to store tenths of a cent and possibly hundredths; these are never shown, but they are stored (although you might just store cents + remainder or fraction).  Even taking that into account, a 64-bit integer is still likely to have more digits than you need.</htmltext>
<tokenext>Note that the range is n't quite that great .
First , most banking systems need to be able to handle negative values , which loses you one bit .
Then you need to store cents as well as dollars , which loses you another 6 .
For interest calculations , you need at least to store tenths of a cent and possibly hundredths ; these are never shown , but they are stored ( although you might just store cents + remainder or fraction ) .
Even taking that into account , a 64-bit integer is still likely to have more digits than you need .</tokentext>
<sentencetext>Note that the range isn't quite that great.
First, most banking systems need to be able to handle negative values, which loses you one bit.
Then you need to store cents as well as dollars, which loses you another 6.
For interest calculations, you need at least to store tenths of a cent and possibly hundredths; these are never shown, but they are stored (although you might just store cents + remainder or fraction).
Even taking that into account, a 64-bit integer is still likely to have more digits than you need.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226740</id>
	<title>Re:Periods and commas.</title>
	<author>Monkeedude1212</author>
	<datestamp>1257181260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You fail to Recognise that seperators in numbers are completely irrelevant to English Grammar.</p><p>Similarily, if I say</p><p>"I would like to buy that item for $2.50 please."</p><p>That there is a period in the middle of the sentence. It's one thing that has bugged me for a long time. But the point is that Period and comma's are interchangable in math. After all, they are just symbols applied to a concept. I think the best way to describe it would be like saying the same rules for syntax that apply to English do not apply to Spanish or French. Similarily, you can't apply those same rules to Mathematics. They are their own language.</p></htmltext>
<tokenext>You fail to Recognise that seperators in numbers are completely irrelevant to English Grammar.Similarily , if I say " I would like to buy that item for $ 2.50 please .
" That there is a period in the middle of the sentence .
It 's one thing that has bugged me for a long time .
But the point is that Period and comma 's are interchangable in math .
After all , they are just symbols applied to a concept .
I think the best way to describe it would be like saying the same rules for syntax that apply to English do not apply to Spanish or French .
Similarily , you ca n't apply those same rules to Mathematics .
They are their own language .</tokentext>
<sentencetext>You fail to Recognise that seperators in numbers are completely irrelevant to English Grammar.Similarily, if I say"I would like to buy that item for $2.50 please.
"That there is a period in the middle of the sentence.
It's one thing that has bugged me for a long time.
But the point is that Period and comma's are interchangable in math.
After all, they are just symbols applied to a concept.
I think the best way to describe it would be like saying the same rules for syntax that apply to English do not apply to Spanish or French.
Similarily, you can't apply those same rules to Mathematics.
They are their own language.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226672</id>
	<title>Oblig. Office Space</title>
	<author>Powys</author>
	<datestamp>1257181020000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>1</modscore>
	<htmltext>&ldquo;I always do that. I always mess up some mundane detail.&rdquo;</htmltext>
<tokenext>   I always do that .
I always mess up some mundane detail.   </tokentext>
<sentencetext>“I always do that.
I always mess up some mundane detail.”</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30232104</id>
	<title>Re:Lets all use the decimal point</title>
	<author>Cassini2</author>
	<datestamp>1257167880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>I propose we get rid of some useless ASCII character and use that for decimal point. How about 0x7f (DEL)</p></div></blockquote><p>0x7F corresponds to the delete key and/or the backspace key in many different computer systems.  See <a href="http://en.wikipedia.org/wiki/ASCII" title="wikipedia.org">ASCII Character Chart.</a> [wikipedia.org]  As the wikipedia page points out, there is a degree of ambiguity between delete and backspace, and that causes enough chaos when dealing with different pieces of software.
</p><p>I am absolutely certain making the delete key a decimal point would cause complete accounting chaos.  I typed "100.00" but the computer says "10000".  We're broke!!!</p></div>
	</htmltext>
<tokenext>I propose we get rid of some useless ASCII character and use that for decimal point .
How about 0x7f ( DEL ) 0x7F corresponds to the delete key and/or the backspace key in many different computer systems .
See ASCII Character Chart .
[ wikipedia.org ] As the wikipedia page points out , there is a degree of ambiguity between delete and backspace , and that causes enough chaos when dealing with different pieces of software .
I am absolutely certain making the delete key a decimal point would cause complete accounting chaos .
I typed " 100.00 " but the computer says " 10000 " .
We 're broke ! !
!</tokentext>
<sentencetext>I propose we get rid of some useless ASCII character and use that for decimal point.
How about 0x7f (DEL)0x7F corresponds to the delete key and/or the backspace key in many different computer systems.
See ASCII Character Chart.
[wikipedia.org]  As the wikipedia page points out, there is a degree of ambiguity between delete and backspace, and that causes enough chaos when dealing with different pieces of software.
I am absolutely certain making the delete key a decimal point would cause complete accounting chaos.
I typed "100.00" but the computer says "10000".
We're broke!!
!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227692</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227028</id>
	<title>Re:For the most part.</title>
	<author>Anonymous</author>
	<datestamp>1257182640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>precision floats (i.e. fixed point)</p></div><p>Shouldn't those be called "fixeds"?</p></div>
	</htmltext>
<tokenext>precision floats ( i.e .
fixed point ) Should n't those be called " fixeds " ?</tokentext>
<sentencetext>precision floats (i.e.
fixed point)Shouldn't those be called "fixeds"?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226270</id>
	<title>Re:You mean 11,500 Euro</title>
	<author>Anonymous</author>
	<datestamp>1257179040000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>No, I think he means 115 Euro as 11500 Euro (thousands separators are more trouble than they're worth).</htmltext>
<tokenext>No , I think he means 115 Euro as 11500 Euro ( thousands separators are more trouble than they 're worth ) .</tokentext>
<sentencetext>No, I think he means 115 Euro as 11500 Euro (thousands separators are more trouble than they're worth).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227340</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257184260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Let's see comma is the separator for main clause and subordinate clause; main and non-main pat;r a whole part and a fractional part. It looks illogical to use dot as a separator for that purpose, especially knowing it comes from typographical reasons. Then again, English is full of inconsitencies and stones and miles are as good as grams and meters.</p></htmltext>
<tokenext>Let 's see comma is the separator for main clause and subordinate clause ; main and non-main pat ; r a whole part and a fractional part .
It looks illogical to use dot as a separator for that purpose , especially knowing it comes from typographical reasons .
Then again , English is full of inconsitencies and stones and miles are as good as grams and meters .</tokentext>
<sentencetext>Let's see comma is the separator for main clause and subordinate clause; main and non-main pat;r a whole part and a fractional part.
It looks illogical to use dot as a separator for that purpose, especially knowing it comes from typographical reasons.
Then again, English is full of inconsitencies and stones and miles are as good as grams and meters.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227788</id>
	<title>Re:You mean 11,500 Euro</title>
	<author>Anonymous</author>
	<datestamp>1257186360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>No, you should read "resulting in a 115.00 Euro transaction being debited as 11,500 Euro!".<br>Many European countries use the point and comma in the opposite way.</p></htmltext>
<tokenext>No , you should read " resulting in a 115.00 Euro transaction being debited as 11,500 Euro !
" .Many European countries use the point and comma in the opposite way .</tokentext>
<sentencetext>No, you should read "resulting in a 115.00 Euro transaction being debited as 11,500 Euro!
".Many European countries use the point and comma in the opposite way.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226442</id>
	<title>Bizzarro Superman</title>
	<author>Kartoffel</author>
	<datestamp>1257179940000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>It's just like in Superman III, but backwards!</p></htmltext>
<tokenext>It 's just like in Superman III , but backwards !</tokentext>
<sentencetext>It's just like in Superman III, but backwards!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228720</id>
	<title>Re:Good to be a programmer</title>
	<author>Anonymous</author>
	<datestamp>1257190680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>That's not insightful. That's regurgitating the same old line that's been circulating for over 30 years. Insightful would be seeing something new in the situation or, god forbid, making a useful suggestion towards solving it.</p></htmltext>
<tokenext>That 's not insightful .
That 's regurgitating the same old line that 's been circulating for over 30 years .
Insightful would be seeing something new in the situation or , god forbid , making a useful suggestion towards solving it .</tokentext>
<sentencetext>That's not insightful.
That's regurgitating the same old line that's been circulating for over 30 years.
Insightful would be seeing something new in the situation or, god forbid, making a useful suggestion towards solving it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227692</id>
	<title>Lets all use the decimal point</title>
	<author>hippo</author>
	<datestamp>1257185880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>When I was a kid I was taught to write decimal points in the middle of the line, not on the bottom like a full-stop. Can we invent a new character for the decimal point. I have two keys on my keyboard with dots on them though I've never pressed the one on the numeric keypad. I propose we get rid of some useless ASCII character and use that for decimal point. How about 0x7f (DEL)? Have you ever wanted to print out DEL?</p></htmltext>
<tokenext>When I was a kid I was taught to write decimal points in the middle of the line , not on the bottom like a full-stop .
Can we invent a new character for the decimal point .
I have two keys on my keyboard with dots on them though I 've never pressed the one on the numeric keypad .
I propose we get rid of some useless ASCII character and use that for decimal point .
How about 0x7f ( DEL ) ?
Have you ever wanted to print out DEL ?</tokentext>
<sentencetext>When I was a kid I was taught to write decimal points in the middle of the line, not on the bottom like a full-stop.
Can we invent a new character for the decimal point.
I have two keys on my keyboard with dots on them though I've never pressed the one on the numeric keypad.
I propose we get rid of some useless ASCII character and use that for decimal point.
How about 0x7f (DEL)?
Have you ever wanted to print out DEL?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226702</id>
	<title>In Socialist Italy......</title>
	<author>benwiggy</author>
	<datestamp>1257181140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>In Socialist Italy, the period separates you into groups of thousands!</p></htmltext>
<tokenext>In Socialist Italy , the period separates you into groups of thousands !</tokentext>
<sentencetext>In Socialist Italy, the period separates you into groups of thousands!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226798</id>
	<title>Re:God Bless the USA!</title>
	<author>saforrest</author>
	<datestamp>1257181440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>Well at least Australia is doing better than Canada. Those poor sods drive on the wrong side *and* use the metric system on their roads.</i></p><p>And on top of that we have French as one of our official languages.</p><p>Nous sommes vraiment des moutons perdus!</p></htmltext>
<tokenext>Well at least Australia is doing better than Canada .
Those poor sods drive on the wrong side * and * use the metric system on their roads.And on top of that we have French as one of our official languages.Nous sommes vraiment des moutons perdus !</tokentext>
<sentencetext>Well at least Australia is doing better than Canada.
Those poor sods drive on the wrong side *and* use the metric system on their roads.And on top of that we have French as one of our official languages.Nous sommes vraiment des moutons perdus!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226556</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227534</id>
	<title>The post is using the wrong format</title>
	<author>Anonymous</author>
	<datestamp>1257185280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I am pretty sure the slashdot post, rather than TFA is using the european format for decimals/thousand seperaters.  From what i can gather from TFA what happened was 115 euro transactions were processed as 11500 euro transactions.</p></htmltext>
<tokenext>I am pretty sure the slashdot post , rather than TFA is using the european format for decimals/thousand seperaters .
From what i can gather from TFA what happened was 115 euro transactions were processed as 11500 euro transactions .</tokentext>
<sentencetext>I am pretty sure the slashdot post, rather than TFA is using the european format for decimals/thousand seperaters.
From what i can gather from TFA what happened was 115 euro transactions were processed as 11500 euro transactions.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476</id>
	<title>Re:For the most part.</title>
	<author>Anonymous</author>
	<datestamp>1257180060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Using strings to store numbers internally is wrong, it just is. It's slow, wasteful, and unnessecary. I don't think I've ever (in 20 years of coding) needed to store something bigger than 2^64, but if I did, there are plenty of options (e.g. BigDecimal in Java, bigint in Perl, etc) which are essentially unlimited in size. Doing math with strings is just such a horrible concept<nobr> <wbr></nobr>:)  As for precision floats (i.e. fixed point) there are real solutions for that issue in most languages too. String isn't one of them.</p><p>Exchanging your data with other systems (e.g. generating a web page, or XML, or whatever) is of course an entirely different story, you do what makes sense for the requirements. XML Schema, for example, mandates that a parser has to accept up to an 18-digit value for the digit type, but doesn't set an upper bound. So you need knowledge of the parser to know how to transfer very large values.</p></htmltext>
<tokenext>Using strings to store numbers internally is wrong , it just is .
It 's slow , wasteful , and unnessecary .
I do n't think I 've ever ( in 20 years of coding ) needed to store something bigger than 2 ^ 64 , but if I did , there are plenty of options ( e.g .
BigDecimal in Java , bigint in Perl , etc ) which are essentially unlimited in size .
Doing math with strings is just such a horrible concept : ) As for precision floats ( i.e .
fixed point ) there are real solutions for that issue in most languages too .
String is n't one of them.Exchanging your data with other systems ( e.g .
generating a web page , or XML , or whatever ) is of course an entirely different story , you do what makes sense for the requirements .
XML Schema , for example , mandates that a parser has to accept up to an 18-digit value for the digit type , but does n't set an upper bound .
So you need knowledge of the parser to know how to transfer very large values .</tokentext>
<sentencetext>Using strings to store numbers internally is wrong, it just is.
It's slow, wasteful, and unnessecary.
I don't think I've ever (in 20 years of coding) needed to store something bigger than 2^64, but if I did, there are plenty of options (e.g.
BigDecimal in Java, bigint in Perl, etc) which are essentially unlimited in size.
Doing math with strings is just such a horrible concept :)  As for precision floats (i.e.
fixed point) there are real solutions for that issue in most languages too.
String isn't one of them.Exchanging your data with other systems (e.g.
generating a web page, or XML, or whatever) is of course an entirely different story, you do what makes sense for the requirements.
XML Schema, for example, mandates that a parser has to accept up to an 18-digit value for the digit type, but doesn't set an upper bound.
So you need knowledge of the parser to know how to transfer very large values.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227450</id>
	<title>Re:Periods and commas.</title>
	<author>Bazman</author>
	<datestamp>1257184860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>We don't use periods (full stops) to separate decimals - we use a decimal point, which is a small dot half-way up the base-height of a piece of text. I'd love to type one for you but there isn't one in ASCII. I'm sure it's there in the Unicode tables somewhere.</p><p>This wasn't a problem on typewriters, when you would just shift the roller half a line space and hit the full stop. Technology eh? We need a 0.5LF character. Or Unicode everywhere. Or \LaTeX everywhere.</p></htmltext>
<tokenext>We do n't use periods ( full stops ) to separate decimals - we use a decimal point , which is a small dot half-way up the base-height of a piece of text .
I 'd love to type one for you but there is n't one in ASCII .
I 'm sure it 's there in the Unicode tables somewhere.This was n't a problem on typewriters , when you would just shift the roller half a line space and hit the full stop .
Technology eh ?
We need a 0.5LF character .
Or Unicode everywhere .
Or \ LaTeX everywhere .</tokentext>
<sentencetext>We don't use periods (full stops) to separate decimals - we use a decimal point, which is a small dot half-way up the base-height of a piece of text.
I'd love to type one for you but there isn't one in ASCII.
I'm sure it's there in the Unicode tables somewhere.This wasn't a problem on typewriters, when you would just shift the roller half a line space and hit the full stop.
Technology eh?
We need a 0.5LF character.
Or Unicode everywhere.
Or \LaTeX everywhere.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235990</id>
	<title>Time for another marvelous solution from ISO</title>
	<author>hicksw</author>
	<datestamp>1259241720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>In the spirit of ISO 2014, which settled the argument of whether dates should be written</p><p>
&nbsp; &nbsp; &nbsp; "day/month/year" or "month/day/year" by specifying "year-month-day",</p><p>I propose this simple solution which should satisfy both comma/period user factions:</p><p>Use either comma or period as a thousands separator.<br>Use semi-colon to separate the integer part from the fractional part.</p><p>A few programmers (c, java, Pascal) may be temporarily inconvenienced, but this is a small price to pay for sorting out this perplexing problem in monetary representation.<br>--<br>Often wrong but never in doubt.</p></htmltext>
<tokenext>In the spirit of ISO 2014 , which settled the argument of whether dates should be written       " day/month/year " or " month/day/year " by specifying " year-month-day " ,I propose this simple solution which should satisfy both comma/period user factions : Use either comma or period as a thousands separator.Use semi-colon to separate the integer part from the fractional part.A few programmers ( c , java , Pascal ) may be temporarily inconvenienced , but this is a small price to pay for sorting out this perplexing problem in monetary representation.--Often wrong but never in doubt .</tokentext>
<sentencetext>In the spirit of ISO 2014, which settled the argument of whether dates should be written
      "day/month/year" or "month/day/year" by specifying "year-month-day",I propose this simple solution which should satisfy both comma/period user factions:Use either comma or period as a thousands separator.Use semi-colon to separate the integer part from the fractional part.A few programmers (c, java, Pascal) may be temporarily inconvenienced, but this is a small price to pay for sorting out this perplexing problem in monetary representation.--Often wrong but never in doubt.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226544</id>
	<title>Re:Periods and commas.</title>
	<author>EvilIdler</author>
	<datestamp>1257180360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I don't think this has anything to do with us using commas for decimal space at all. It is perfectly clear to us, despite it not being clear to your untrained mind<nobr> <wbr></nobr>;)</p><p>My bank uses spaces to separate thousands and a comma for the decimal spot. If a sentence ends with a sum of money, we won't have two full stops in a row, which I'd find harder to read than "1 324 299,53" at the end of a sentence.</p></htmltext>
<tokenext>I do n't think this has anything to do with us using commas for decimal space at all .
It is perfectly clear to us , despite it not being clear to your untrained mind ; ) My bank uses spaces to separate thousands and a comma for the decimal spot .
If a sentence ends with a sum of money , we wo n't have two full stops in a row , which I 'd find harder to read than " 1 324 299,53 " at the end of a sentence .</tokentext>
<sentencetext>I don't think this has anything to do with us using commas for decimal space at all.
It is perfectly clear to us, despite it not being clear to your untrained mind ;)My bank uses spaces to separate thousands and a comma for the decimal spot.
If a sentence ends with a sum of money, we won't have two full stops in a row, which I'd find harder to read than "1 324 299,53" at the end of a sentence.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229048</id>
	<title>Radix Point notation conventions</title>
	<author>Anonymous</author>
	<datestamp>1257192000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>In Engineering ( I am an EE ):<br>The 'thing' / location / construct described by the period (or comma) 10.00 (or 10,00) is called the Radix point.<br>this is base 10 for decimal, base 2 for binary etc.<br>the point indicates the positional significance of each number written.<br>in decimal 10s, 100s, 1000s to the left (increasing 10-fold, errr... as in Base10 duh!), etc, or 1/10th, 1/100th etc to right of the radix point for decreasing fractional values<br>It all depends on your number system: so while we accept generally that something costs $10.95 id US dollars, or 10,95 in Euros for example is normally understood by most people, the fact that you can have something in base 2 (binary)  such as 1101.011101 is a real actual possible fractional number in Base 2, binary.<br>although computers/electronics are  0 or 1 i.e. sort of single 'bitwise'  at a time, (actually an analogue voltage that is characterized as a 1 or 0 depending on the design criteria)</p><p>obviously we have 64, 32, 128, etc bit 'things' memory, cpu, registers, flip-flips, etc in parallel, but each bit is only a integer 0 or 1.</p><p>---<br>the math behind Base 2 allows for a number like 1101.101<br>to figure out this number equivalent in decimal:<br>(1)x2^3+(1)x2^2+(0)x2^1+(1)x2^0 (radix point) + (1)x2^-1+(0)x2^-2+(1)x2^-3 so that is 8+4+0+1=13.00 is the whole part and the fraction is (0.5+0+0.125)=0.625 so 13.625 in decimal or 13,625 in (sorry) 'euro-decimal'</p><p>my point is all it is -- it's just a convention for the radix point notation:<br>
&nbsp; US uses .<br>FR uses ,</p><p>so what? somebody made the convention 6'4" for 6 foot 4 inches which is not 6.4 feet it's 6.3333( repeating) feet<nobr> <wbr></nobr>.... the places that use metric use scientific notation: 1.9304 meters.<br>sometime people also swap usage of , and . for thousands in compared in various countries: 15,000.00 US is 15.000,00 elsewhere.... just notation convention</p><p>Just one of quirk of puny humans and their unorganized societies,</p><p>(and of course...)<br>I for one, hail our new Math Overlords....</p></htmltext>
<tokenext>In Engineering ( I am an EE ) : The 'thing ' / location / construct described by the period ( or comma ) 10.00 ( or 10,00 ) is called the Radix point.this is base 10 for decimal , base 2 for binary etc.the point indicates the positional significance of each number written.in decimal 10s , 100s , 1000s to the left ( increasing 10-fold , errr... as in Base10 duh !
) , etc , or 1/10th , 1/100th etc to right of the radix point for decreasing fractional valuesIt all depends on your number system : so while we accept generally that something costs $ 10.95 id US dollars , or 10,95 in Euros for example is normally understood by most people , the fact that you can have something in base 2 ( binary ) such as 1101.011101 is a real actual possible fractional number in Base 2 , binary.although computers/electronics are 0 or 1 i.e .
sort of single 'bitwise ' at a time , ( actually an analogue voltage that is characterized as a 1 or 0 depending on the design criteria ) obviously we have 64 , 32 , 128 , etc bit 'things ' memory , cpu , registers , flip-flips , etc in parallel , but each bit is only a integer 0 or 1.---the math behind Base 2 allows for a number like 1101.101to figure out this number equivalent in decimal : ( 1 ) x2 ^ 3 + ( 1 ) x2 ^ 2 + ( 0 ) x2 ^ 1 + ( 1 ) x2 ^ 0 ( radix point ) + ( 1 ) x2 ^ -1 + ( 0 ) x2 ^ -2 + ( 1 ) x2 ^ -3 so that is 8 + 4 + 0 + 1 = 13.00 is the whole part and the fraction is ( 0.5 + 0 + 0.125 ) = 0.625 so 13.625 in decimal or 13,625 in ( sorry ) 'euro-decimal'my point is all it is -- it 's just a convention for the radix point notation :   US uses .FR uses ,so what ?
somebody made the convention 6'4 " for 6 foot 4 inches which is not 6.4 feet it 's 6.3333 ( repeating ) feet .... the places that use metric use scientific notation : 1.9304 meters.sometime people also swap usage of , and .
for thousands in compared in various countries : 15,000.00 US is 15.000,00 elsewhere.... just notation conventionJust one of quirk of puny humans and their unorganized societies , ( and of course... ) I for one , hail our new Math Overlords... .</tokentext>
<sentencetext>In Engineering ( I am an EE ):The 'thing' / location / construct described by the period (or comma) 10.00 (or 10,00) is called the Radix point.this is base 10 for decimal, base 2 for binary etc.the point indicates the positional significance of each number written.in decimal 10s, 100s, 1000s to the left (increasing 10-fold, errr... as in Base10 duh!
), etc, or 1/10th, 1/100th etc to right of the radix point for decreasing fractional valuesIt all depends on your number system: so while we accept generally that something costs $10.95 id US dollars, or 10,95 in Euros for example is normally understood by most people, the fact that you can have something in base 2 (binary)  such as 1101.011101 is a real actual possible fractional number in Base 2, binary.although computers/electronics are  0 or 1 i.e.
sort of single 'bitwise'  at a time, (actually an analogue voltage that is characterized as a 1 or 0 depending on the design criteria)obviously we have 64, 32, 128, etc bit 'things' memory, cpu, registers, flip-flips, etc in parallel, but each bit is only a integer 0 or 1.---the math behind Base 2 allows for a number like 1101.101to figure out this number equivalent in decimal:(1)x2^3+(1)x2^2+(0)x2^1+(1)x2^0 (radix point) + (1)x2^-1+(0)x2^-2+(1)x2^-3 so that is 8+4+0+1=13.00 is the whole part and the fraction is (0.5+0+0.125)=0.625 so 13.625 in decimal or 13,625 in (sorry) 'euro-decimal'my point is all it is -- it's just a convention for the radix point notation:
  US uses .FR uses ,so what?
somebody made the convention 6'4" for 6 foot 4 inches which is not 6.4 feet it's 6.3333( repeating) feet .... the places that use metric use scientific notation: 1.9304 meters.sometime people also swap usage of , and .
for thousands in compared in various countries: 15,000.00 US is 15.000,00 elsewhere.... just notation conventionJust one of quirk of puny humans and their unorganized societies,(and of course...)I for one, hail our new Math Overlords....</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226530</id>
	<title>Re:For the most part.</title>
	<author>Nadaka</author>
	<datestamp>1257180300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>a 64 bit long has more than enough space to handle every currency in the world (except possibly hyper-inflationary Zimbabwe) to a tiny fraction of a penny. Even then, there are data structures that offer arbitrary precision and arbitrary ranges of values that are far more efficient than any string manipulation. In most cases, you are going to be converting the string back to a number for real math anyway. Hell even cobol handles numbers better than strings.</p><p>I won't even go into the rediculousness of using xml for data storage and retrieval for high throughput systems.</p></htmltext>
<tokenext>a 64 bit long has more than enough space to handle every currency in the world ( except possibly hyper-inflationary Zimbabwe ) to a tiny fraction of a penny .
Even then , there are data structures that offer arbitrary precision and arbitrary ranges of values that are far more efficient than any string manipulation .
In most cases , you are going to be converting the string back to a number for real math anyway .
Hell even cobol handles numbers better than strings.I wo n't even go into the rediculousness of using xml for data storage and retrieval for high throughput systems .</tokentext>
<sentencetext>a 64 bit long has more than enough space to handle every currency in the world (except possibly hyper-inflationary Zimbabwe) to a tiny fraction of a penny.
Even then, there are data structures that offer arbitrary precision and arbitrary ranges of values that are far more efficient than any string manipulation.
In most cases, you are going to be converting the string back to a number for real math anyway.
Hell even cobol handles numbers better than strings.I won't even go into the rediculousness of using xml for data storage and retrieval for high throughput systems.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227296</id>
	<title>Re:God Bless the USA!</title>
	<author>DomNF15</author>
	<datestamp>1257184080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>We (Americans) also picked up the disease known as the Imperial measurement system<nobr> <wbr></nobr>:-)  It's simply spectacular than 12 inches = 1 foot, 5280 feet = 1 mile, and 1 acre = 43560 square feet.  This, clearly, is much more logical and obvious than that pesky metric system with it's 100 centimeters = 1 meter, 1000 meters = 1 km, and 1 square km = you guessed it, 1000000 square meters.  I also love having to buy 2 sets of tools to work on my house/car, thanks again, UK.</htmltext>
<tokenext>We ( Americans ) also picked up the disease known as the Imperial measurement system : - ) It 's simply spectacular than 12 inches = 1 foot , 5280 feet = 1 mile , and 1 acre = 43560 square feet .
This , clearly , is much more logical and obvious than that pesky metric system with it 's 100 centimeters = 1 meter , 1000 meters = 1 km , and 1 square km = you guessed it , 1000000 square meters .
I also love having to buy 2 sets of tools to work on my house/car , thanks again , UK .</tokentext>
<sentencetext>We (Americans) also picked up the disease known as the Imperial measurement system :-)  It's simply spectacular than 12 inches = 1 foot, 5280 feet = 1 mile, and 1 acre = 43560 square feet.
This, clearly, is much more logical and obvious than that pesky metric system with it's 100 centimeters = 1 meter, 1000 meters = 1 km, and 1 square km = you guessed it, 1000000 square meters.
I also love having to buy 2 sets of tools to work on my house/car, thanks again, UK.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226332</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226486</id>
	<title>Powers-of-ten Information Biases</title>
	<author>Anonymous</author>
	<datestamp>1257180060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This is called a "power-of-ten information bias." The problem was described almost 20 years ago in the Management Information Systems Quarterly, Vol. 14, No. 1, March 1990, pp. 63-77.</p></htmltext>
<tokenext>This is called a " power-of-ten information bias .
" The problem was described almost 20 years ago in the Management Information Systems Quarterly , Vol .
14 , No .
1 , March 1990 , pp .
63-77 .</tokentext>
<sentencetext>This is called a "power-of-ten information bias.
" The problem was described almost 20 years ago in the Management Information Systems Quarterly, Vol.
14, No.
1, March 1990, pp.
63-77.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228260</id>
	<title>Re:Good to be a programmer</title>
	<author>Anonymous</author>
	<datestamp>1257188580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>LOL?</p><p>Seriously, it is like you have never written a single line of code in your life. For ANY warranty to be meaningful, first and foremost the OS must have some sort of a warranty and all the API the application uses must also have some sort of a warranty. If they do not, how can the you write a program that then has LIABILITY for defects?? It's utterly retarded.</p><p>So FU. Write some software that is used by anyone first then start bitching. Maybe after the 10th OS bug that is then listed as a "feature" you'll have a clue WTF you are talking about.</p></htmltext>
<tokenext>LOL ? Seriously , it is like you have never written a single line of code in your life .
For ANY warranty to be meaningful , first and foremost the OS must have some sort of a warranty and all the API the application uses must also have some sort of a warranty .
If they do not , how can the you write a program that then has LIABILITY for defects ? ?
It 's utterly retarded.So FU .
Write some software that is used by anyone first then start bitching .
Maybe after the 10th OS bug that is then listed as a " feature " you 'll have a clue WTF you are talking about .</tokentext>
<sentencetext>LOL?Seriously, it is like you have never written a single line of code in your life.
For ANY warranty to be meaningful, first and foremost the OS must have some sort of a warranty and all the API the application uses must also have some sort of a warranty.
If they do not, how can the you write a program that then has LIABILITY for defects??
It's utterly retarded.So FU.
Write some software that is used by anyone first then start bitching.
Maybe after the 10th OS bug that is then listed as a "feature" you'll have a clue WTF you are talking about.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382</id>
	<title>Re:God Bless the USA!</title>
	<author>Yvanhoe</author>
	<datestamp>1257179700000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>Do you know the nightmarish hell that is an Excel localized in French while being part of an international team ?

Copy-paste of the same data using Excel EN or Excel FR will result in either 115.5 or 115,5 leading to interesting bugs to track...</htmltext>
<tokenext>Do you know the nightmarish hell that is an Excel localized in French while being part of an international team ?
Copy-paste of the same data using Excel EN or Excel FR will result in either 115.5 or 115,5 leading to interesting bugs to track.. .</tokentext>
<sentencetext>Do you know the nightmarish hell that is an Excel localized in French while being part of an international team ?
Copy-paste of the same data using Excel EN or Excel FR will result in either 115.5 or 115,5 leading to interesting bugs to track...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226166</id>
	<title>Obligatory Office Space</title>
	<author>Anonymous</author>
	<datestamp>1257178620000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>I always do that, I mess up some mundane detail!</p></htmltext>
<tokenext>I always do that , I mess up some mundane detail !</tokentext>
<sentencetext>I always do that, I mess up some mundane detail!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226630</id>
	<title>Windows XP</title>
	<author>Krneki</author>
	<datestamp>1257180840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The whole system is probably running on Windows XP Home and someone must have changed the regional settings to Italy so he can install some Italian crap on it.<br><br>P.S: Just trolling.<nobr> <wbr></nobr>:)</htmltext>
<tokenext>The whole system is probably running on Windows XP Home and someone must have changed the regional settings to Italy so he can install some Italian crap on it.P.S : Just trolling .
: )</tokentext>
<sentencetext>The whole system is probably running on Windows XP Home and someone must have changed the regional settings to Italy so he can install some Italian crap on it.P.S: Just trolling.
:)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228046</id>
	<title>Re:For the most part.</title>
	<author>Anonymous</author>
	<datestamp>1257187500000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This is a typical Cobol bug. It's not actually a String, but a "Picture" -- it's ultimately rooted in the strange hardware design of the Univac II.</p></htmltext>
<tokenext>This is a typical Cobol bug .
It 's not actually a String , but a " Picture " -- it 's ultimately rooted in the strange hardware design of the Univac II .</tokentext>
<sentencetext>This is a typical Cobol bug.
It's not actually a String, but a "Picture" -- it's ultimately rooted in the strange hardware design of the Univac II.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231836</id>
	<title>Re:For the most part.</title>
	<author>selven</author>
	<datestamp>1257165420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><tt>Use arrays!<br><br>int[] multiply(int[] a, int[] b) {<br>&nbsp; &nbsp; k = new int(a.length + b.length)<br>&nbsp; &nbsp; for (int i = 0; i &lt; a.length; i++) {<br>&nbsp; &nbsp; &nbsp; &nbsp; for (int j = 0; j &lt; b.length; j++) {<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; k[i+j] = a[i] * b[j];<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; if (k[i+j] &gt; 65535) {<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; k[i+j+1] = int(k[i+j]/65536);<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; k[i+j] = k[i+j] \% 65536;<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }<br>&nbsp; &nbsp; &nbsp; &nbsp; }<br>&nbsp; &nbsp; }<br>}</tt></htmltext>
<tokenext>Use arrays ! int [ ] multiply ( int [ ] a , int [ ] b ) {     k = new int ( a.length + b.length )     for ( int i = 0 ; i         for ( int j = 0 ; j             k [ i + j ] = a [ i ] * b [ j ] ;             if ( k [ i + j ] &gt; 65535 ) {                 k [ i + j + 1 ] = int ( k [ i + j ] /65536 ) ;                 k [ i + j ] = k [ i + j ] \ % 65536 ;             }         }     } }</tokentext>
<sentencetext>Use arrays!int[] multiply(int[] a, int[] b) {    k = new int(a.length + b.length)    for (int i = 0; i         for (int j = 0; j             k[i+j] = a[i] * b[j];            if (k[i+j] &gt; 65535) {                k[i+j+1] = int(k[i+j]/65536);                k[i+j] = k[i+j] \% 65536;            }        }    }}</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226732</id>
	<title>That's what LC\_NUMERIC is for</title>
	<author>gzipped\_tar</author>
	<datestamp>1257181260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Use it or lose it. Duh.</htmltext>
<tokenext>Use it or lose it .
Duh .</tokentext>
<sentencetext>Use it or lose it.
Duh.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226640</id>
	<title>Re:For the most part.</title>
	<author>The MAZZTer</author>
	<datestamp>1257180900000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>Doing math with strings will guarantee your code a place on the front page of thedailywtf.com</htmltext>
<tokenext>Doing math with strings will guarantee your code a place on the front page of thedailywtf.com</tokentext>
<sentencetext>Doing math with strings will guarantee your code a place on the front page of thedailywtf.com</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229236</id>
	<title>Re:For the most part.</title>
	<author>Anonymous</author>
	<datestamp>1257192840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You just wait until Bernanke is done.</p></htmltext>
<tokenext>You just wait until Bernanke is done .</tokentext>
<sentencetext>You just wait until Bernanke is done.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226756</id>
	<title>Re:God Bless the USA!</title>
	<author>Firehed</author>
	<datestamp>1257181380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Did you just inadvertently congratulate America for <i>not</i> using the Metric system? Shame on you! It makes 10 weather so uncomfortable!</p></htmltext>
<tokenext>Did you just inadvertently congratulate America for not using the Metric system ?
Shame on you !
It makes 10 weather so uncomfortable !</tokentext>
<sentencetext>Did you just inadvertently congratulate America for not using the Metric system?
Shame on you!
It makes 10 weather so uncomfortable!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226556</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228362</id>
	<title>Does your software work in Turkey?</title>
	<author>Nyrath the nearly wi</author>
	<datestamp>1257189120000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>This is just one of the many pitfalls when trying to localize your software. </p><p>
<a href="http://www.moserware.com/2008/02/does-your-code-pass-turkey-test.html" title="moserware.com">Does Your Code Pass The Turkey Test?</a> [moserware.com]</p></htmltext>
<tokenext>This is just one of the many pitfalls when trying to localize your software .
Does Your Code Pass The Turkey Test ?
[ moserware.com ]</tokentext>
<sentencetext>This is just one of the many pitfalls when trying to localize your software.
Does Your Code Pass The Turkey Test?
[moserware.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227006</id>
	<title>Re:Happened to me recently</title>
	<author>Nadaka</author>
	<datestamp>1257182520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Use this experience as evidence that you need to implement a robust software testing regiment.</p></htmltext>
<tokenext>Use this experience as evidence that you need to implement a robust software testing regiment .</tokentext>
<sentencetext>Use this experience as evidence that you need to implement a robust software testing regiment.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227618</id>
	<title>Apostrophes!</title>
	<author>munch117</author>
	<datestamp>1257185580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Here's a practical option, you can start using right away without waiting for the whole world to agree on anything: Use apostrophes for the thousands separator. It's just better: It looks good, everyone trivially understands it, and it's unambiguous.</p><p>If you configure that in the regional settings of a Microsoft OS, and the decimal separator is set to a comma, then Excel becomes capable of reading CSV files with either decimal separator.</p></htmltext>
<tokenext>Here 's a practical option , you can start using right away without waiting for the whole world to agree on anything : Use apostrophes for the thousands separator .
It 's just better : It looks good , everyone trivially understands it , and it 's unambiguous.If you configure that in the regional settings of a Microsoft OS , and the decimal separator is set to a comma , then Excel becomes capable of reading CSV files with either decimal separator .</tokentext>
<sentencetext>Here's a practical option, you can start using right away without waiting for the whole world to agree on anything: Use apostrophes for the thousands separator.
It's just better: It looks good, everyone trivially understands it, and it's unambiguous.If you configure that in the regional settings of a Microsoft OS, and the decimal separator is set to a comma, then Excel becomes capable of reading CSV files with either decimal separator.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226468</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229626</id>
	<title>Re:God Bless the USA!</title>
	<author>jonbryce</author>
	<datestamp>1257194640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It could be worse.  You could receive Hebrew localised Excel files with the columns going from Z - A in the wrong direction.</p></htmltext>
<tokenext>It could be worse .
You could receive Hebrew localised Excel files with the columns going from Z - A in the wrong direction .</tokentext>
<sentencetext>It could be worse.
You could receive Hebrew localised Excel files with the columns going from Z - A in the wrong direction.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226490</id>
	<title>Re:For the most part.</title>
	<author>ls671</author>
	<datestamp>1257180120000</datestamp>
	<modclass>None</modclass>
	<modscore>2</modscore>
	<htmltext><p>Huh, haven't you heard of BigInteger like data types ?</p><p>They are pretty common in accounting in various languages...</p><p><a href="http://java.sun.com/j2se/1.5.0/docs/api/java/math/BigInteger.html" title="sun.com">http://java.sun.com/j2se/1.5.0/docs/api/java/math/BigInteger.html</a> [sun.com]</p></htmltext>
<tokenext>Huh , have n't you heard of BigInteger like data types ? They are pretty common in accounting in various languages...http : //java.sun.com/j2se/1.5.0/docs/api/java/math/BigInteger.html [ sun.com ]</tokentext>
<sentencetext>Huh, haven't you heard of BigInteger like data types ?They are pretty common in accounting in various languages...http://java.sun.com/j2se/1.5.0/docs/api/java/math/BigInteger.html [sun.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228646</id>
	<title>Re:Good to be a programmer</title>
	<author>dkleinsc</author>
	<datestamp>1257190380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Real engineers have the power to say no. Their legal culpability makes it harder to cut corners, and since an engineer needs to sign off on a real-life project in order to make it happen, they essentially have veto power in their organization over what they're responsible for.</p><p>Software engineers, on the other hand, generally are required by management to cut corners wherever possible. Time-to-market nearly always trumps all other factors. They have no authority whatsoever organizationally, and have no laws to back them up.</p><p>Basically, think of an engineer who is told to build a bridge capable of handling the load of 50 laden semis using string and duct tape within 6 months, or lose his job. Can you really fault him for trying his best to meet that demand (he has a family to feed), or making a mistake and only handling the load of 45 semis?</p></htmltext>
<tokenext>Real engineers have the power to say no .
Their legal culpability makes it harder to cut corners , and since an engineer needs to sign off on a real-life project in order to make it happen , they essentially have veto power in their organization over what they 're responsible for.Software engineers , on the other hand , generally are required by management to cut corners wherever possible .
Time-to-market nearly always trumps all other factors .
They have no authority whatsoever organizationally , and have no laws to back them up.Basically , think of an engineer who is told to build a bridge capable of handling the load of 50 laden semis using string and duct tape within 6 months , or lose his job .
Can you really fault him for trying his best to meet that demand ( he has a family to feed ) , or making a mistake and only handling the load of 45 semis ?</tokentext>
<sentencetext>Real engineers have the power to say no.
Their legal culpability makes it harder to cut corners, and since an engineer needs to sign off on a real-life project in order to make it happen, they essentially have veto power in their organization over what they're responsible for.Software engineers, on the other hand, generally are required by management to cut corners wherever possible.
Time-to-market nearly always trumps all other factors.
They have no authority whatsoever organizationally, and have no laws to back them up.Basically, think of an engineer who is told to build a bridge capable of handling the load of 50 laden semis using string and duct tape within 6 months, or lose his job.
Can you really fault him for trying his best to meet that demand (he has a family to feed), or making a mistake and only handling the load of 45 semis?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235290</id>
	<title>Re:Happened to me recently</title>
	<author>RogerWilco</author>
	<datestamp>1259233560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Always keep localisation in mind for every piece of software you write. Always.</p><p>I live in a small European country, the chances my software get used abroad are always significant, but even in the USA there are large numbers of non-English speakers, and Canada and Mexico are near too.</p><p>Sometimes I just write ""This code was developed only to work in XXXX locale/country" as a comment in the code. Usually my code will use defines/enumerations like DECIMALSEPARATOR and FILETOBIGWARNING instead of hardcoded values/strings, even if only one locale is used. Retroactively internationalising a piece of code not written that way is a huge pain. Just assume every piece of software you write will be a huge success and end up being used all over the world in a decade.<nobr> <wbr></nobr>;-)</p></htmltext>
<tokenext>Always keep localisation in mind for every piece of software you write .
Always.I live in a small European country , the chances my software get used abroad are always significant , but even in the USA there are large numbers of non-English speakers , and Canada and Mexico are near too.Sometimes I just write " " This code was developed only to work in XXXX locale/country " as a comment in the code .
Usually my code will use defines/enumerations like DECIMALSEPARATOR and FILETOBIGWARNING instead of hardcoded values/strings , even if only one locale is used .
Retroactively internationalising a piece of code not written that way is a huge pain .
Just assume every piece of software you write will be a huge success and end up being used all over the world in a decade .
; - )</tokentext>
<sentencetext>Always keep localisation in mind for every piece of software you write.
Always.I live in a small European country, the chances my software get used abroad are always significant, but even in the USA there are large numbers of non-English speakers, and Canada and Mexico are near too.Sometimes I just write ""This code was developed only to work in XXXX locale/country" as a comment in the code.
Usually my code will use defines/enumerations like DECIMALSEPARATOR and FILETOBIGWARNING instead of hardcoded values/strings, even if only one locale is used.
Retroactively internationalising a piece of code not written that way is a huge pain.
Just assume every piece of software you write will be a huge success and end up being used all over the world in a decade.
;-)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226352</id>
	<title>Mundane detail</title>
	<author>nitsew</author>
	<datestamp>1257179520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Ok! Ok! I must have, I must have put a decimal point in the wrong place
or something. Shit. I always do that. I always mess up some mundane
detail.</htmltext>
<tokenext>Ok !
Ok ! I must have , I must have put a decimal point in the wrong place or something .
Shit. I always do that .
I always mess up some mundane detail .</tokentext>
<sentencetext>Ok!
Ok! I must have, I must have put a decimal point in the wrong place
or something.
Shit. I always do that.
I always mess up some mundane
detail.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227420</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257184740000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>If a comma is a separator, why not use it to separate decimals?</i></p><p>A number can only have one decimal separator. A sentence can have only one period.</p><p>A number can have many thousands separators.  A sentence can have many commas.</p><p>This isn't a strong argument, but in the absence of any reason to do it otherwise it's better to do it in the marginally more consistent way.</p></htmltext>
<tokenext>If a comma is a separator , why not use it to separate decimals ? A number can only have one decimal separator .
A sentence can have only one period.A number can have many thousands separators .
A sentence can have many commas.This is n't a strong argument , but in the absence of any reason to do it otherwise it 's better to do it in the marginally more consistent way .</tokentext>
<sentencetext>If a comma is a separator, why not use it to separate decimals?A number can only have one decimal separator.
A sentence can have only one period.A number can have many thousands separators.
A sentence can have many commas.This isn't a strong argument, but in the absence of any reason to do it otherwise it's better to do it in the marginally more consistent way.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235402</id>
	<title>Re:For the most part.</title>
	<author>Hurricane78</author>
	<datestamp>1259234880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I don&rsquo;t get who came up with the idea, that using &ldquo;billion billion&rdquo; was somehow easier than &ldquo;quintillion&rdquo; alone.</p><p>If you go by that standard, you should follow it to the end, and say &ldquo;eight ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten moneys&rdquo;.</p><p>&ldquo;billion billion&rdquo;. The &ldquo;Clippy&rdquo; way of assistance to the understanding of big numbers. ^^</p></htmltext>
<tokenext>I don    t get who came up with the idea , that using    billion billion    was somehow easier than    quintillion    alone.If you go by that standard , you should follow it to the end , and say    eight ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten moneys    .    billion billion    .
The    Clippy    way of assistance to the understanding of big numbers .
^ ^</tokentext>
<sentencetext>I don’t get who came up with the idea, that using “billion billion” was somehow easier than “quintillion” alone.If you go by that standard, you should follow it to the end, and say “eight ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten ten moneys”.“billion billion”.
The “Clippy” way of assistance to the understanding of big numbers.
^^</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231452</id>
	<title>Re:God Bless the USA!</title>
	<author>zmaragdus</author>
	<datestamp>1257162300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The best system I've run across (and the one I've personally adopted) is, when representing numbers as strings (e.g. when simply typing something up or writing them out by hand), put a space between each group of three digits to the left of the decimal separator and use either a comma or a period as the "decimal point" (being from the US, I tend to use the period). Thus the number 456786557 and 67484/100000 would be represented as either "456 786 557.67484" or "456 786 557,67484"</p></htmltext>
<tokenext>The best system I 've run across ( and the one I 've personally adopted ) is , when representing numbers as strings ( e.g .
when simply typing something up or writing them out by hand ) , put a space between each group of three digits to the left of the decimal separator and use either a comma or a period as the " decimal point " ( being from the US , I tend to use the period ) .
Thus the number 456786557 and 67484/100000 would be represented as either " 456 786 557.67484 " or " 456 786 557,67484 "</tokentext>
<sentencetext>The best system I've run across (and the one I've personally adopted) is, when representing numbers as strings (e.g.
when simply typing something up or writing them out by hand), put a space between each group of three digits to the left of the decimal separator and use either a comma or a period as the "decimal point" (being from the US, I tend to use the period).
Thus the number 456786557 and 67484/100000 would be represented as either "456 786 557.67484" or "456 786 557,67484"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226148</id>
	<title>No, no, that's just a voluntary tax payment...</title>
	<author>DamonHD</author>
	<datestamp>1257178560000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><p>(FIRST?)</p><p>B^&gt;</p><p>Rgds</p><p>Damon</p></htmltext>
<tokenext>( FIRST ?
) B ^ &gt; RgdsDamon</tokentext>
<sentencetext>(FIRST?
)B^&gt;RgdsDamon</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227264</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257183900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Ive asked myself recently how translation programms differentiate between a period as an end to a sentence or an number.</p><p>Let me think of a sentence, ehm: While Germanys National debt rose about 18 \% in the last year,  Japans debt rose about 100. 10000s of jobs are on the edge.</p></htmltext>
<tokenext>Ive asked myself recently how translation programms differentiate between a period as an end to a sentence or an number.Let me think of a sentence , ehm : While Germanys National debt rose about 18 \ % in the last year , Japans debt rose about 100 .
10000s of jobs are on the edge .</tokentext>
<sentencetext>Ive asked myself recently how translation programms differentiate between a period as an end to a sentence or an number.Let me think of a sentence, ehm: While Germanys National debt rose about 18 \% in the last year,  Japans debt rose about 100.
10000s of jobs are on the edge.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226760</id>
	<title>Re:For the most part.</title>
	<author>31415926535897</author>
	<datestamp>1257181380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This could be true in Zimbabwe.</p></htmltext>
<tokenext>This could be true in Zimbabwe .</tokentext>
<sentencetext>This could be true in Zimbabwe.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227172</id>
	<title>Re:For the most part.</title>
	<author>Nadaka</author>
	<datestamp>1257183360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I have had exactly one occasion where I needed more than 64 bits, and we did use strings (technically a small array of bytes). It was a programming contest. We had 8 hours to solve as many problems as possible. One of them was to display pi to at least a 500 digits with the ability to display arbitrarily more precise values.</p></htmltext>
<tokenext>I have had exactly one occasion where I needed more than 64 bits , and we did use strings ( technically a small array of bytes ) .
It was a programming contest .
We had 8 hours to solve as many problems as possible .
One of them was to display pi to at least a 500 digits with the ability to display arbitrarily more precise values .</tokentext>
<sentencetext>I have had exactly one occasion where I needed more than 64 bits, and we did use strings (technically a small array of bytes).
It was a programming contest.
We had 8 hours to solve as many problems as possible.
One of them was to display pi to at least a 500 digits with the ability to display arbitrarily more precise values.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226784</id>
	<title>Re:You mean 11,500 Euro</title>
	<author>Anonymous</author>
	<datestamp>1257181440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>No, they do mean 115,00 as 11.500[,00]<nobr> <wbr></nobr>...</p></htmltext>
<tokenext>No , they do mean 115,00 as 11.500 [ ,00 ] .. .</tokentext>
<sentencetext>No, they do mean 115,00 as 11.500[,00] ...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30374040</id>
	<title>Re:For the most part.</title>
	<author>Qu4Z</author>
	<datestamp>1260292320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>My suggestion: Binary-Coded Decimal!</p></htmltext>
<tokenext>My suggestion : Binary-Coded Decimal !</tokentext>
<sentencetext>My suggestion: Binary-Coded Decimal!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227714</id>
	<title>Re:You mean 11,500 Euro</title>
	<author>this great guy</author>
	<datestamp>1257186000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>You are wrong (1000x difference between your numbers -- the summary said 100x).
<br> <br>
Also many other posters are wrong when saying that European use dots to separate thousands. Some countries may do it, but precisely because of these different and confusing conventions, French schools teach students to use <b>spaces</b> to separate thousands, eg. 11 500 Euro, 115 000 Euro, 1 150 000 Euros.</htmltext>
<tokenext>You are wrong ( 1000x difference between your numbers -- the summary said 100x ) .
Also many other posters are wrong when saying that European use dots to separate thousands .
Some countries may do it , but precisely because of these different and confusing conventions , French schools teach students to use spaces to separate thousands , eg .
11 500 Euro , 115 000 Euro , 1 150 000 Euros .</tokentext>
<sentencetext>You are wrong (1000x difference between your numbers -- the summary said 100x).
Also many other posters are wrong when saying that European use dots to separate thousands.
Some countries may do it, but precisely because of these different and confusing conventions, French schools teach students to use spaces to separate thousands, eg.
11 500 Euro, 115 000 Euro, 1 150 000 Euros.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</id>
	<title>Good to be a programmer</title>
	<author>Anonymous</author>
	<datestamp>1257178980000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Good thing the programmers will be shielded from any consequences from this little 'bug'.</p><p>It doesn't matter that it caused potential harm to clients, corporations in the form of losses, lost time, expenses, etc.</p><p>The simple programmers just need to release a hot-fix or service pack.</p><p>Now if these were engineers, and I mean real engineers not "software engineers", there would be consequences.</p><p>Their licenses could be revoked, they could be investigated for incompetence, and held professionally and personally liable for any bugs.</p><p>But please, keep on purchasing software with NO WARRANTY, or NO FITNESS FOR A PARTICULAR PURPOSE, and that contains KNOWN DEFECTS.</p><p>Gotta keep the programming industry alive, and don't wanna stress theses "engineers" too much.</p></htmltext>
<tokenext>Good thing the programmers will be shielded from any consequences from this little 'bug'.It does n't matter that it caused potential harm to clients , corporations in the form of losses , lost time , expenses , etc.The simple programmers just need to release a hot-fix or service pack.Now if these were engineers , and I mean real engineers not " software engineers " , there would be consequences.Their licenses could be revoked , they could be investigated for incompetence , and held professionally and personally liable for any bugs.But please , keep on purchasing software with NO WARRANTY , or NO FITNESS FOR A PARTICULAR PURPOSE , and that contains KNOWN DEFECTS.Got ta keep the programming industry alive , and do n't wan na stress theses " engineers " too much .</tokentext>
<sentencetext>Good thing the programmers will be shielded from any consequences from this little 'bug'.It doesn't matter that it caused potential harm to clients, corporations in the form of losses, lost time, expenses, etc.The simple programmers just need to release a hot-fix or service pack.Now if these were engineers, and I mean real engineers not "software engineers", there would be consequences.Their licenses could be revoked, they could be investigated for incompetence, and held professionally and personally liable for any bugs.But please, keep on purchasing software with NO WARRANTY, or NO FITNESS FOR A PARTICULAR PURPOSE, and that contains KNOWN DEFECTS.Gotta keep the programming industry alive, and don't wanna stress theses "engineers" too much.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226794</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257181440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Europeans did not make the swap, americans did...</p><p>Or are you not aware that Europe used decimals way before the US existed ?</p></htmltext>
<tokenext>Europeans did not make the swap , americans did...Or are you not aware that Europe used decimals way before the US existed ?</tokentext>
<sentencetext>Europeans did not make the swap, americans did...Or are you not aware that Europe used decimals way before the US existed ?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231960</id>
	<title>Re:Happened to me recently</title>
	<author>Anonymous</author>
	<datestamp>1257166620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Before converting it to a double or float point or whatever you are using<nobr> <wbr></nobr>...</p></div><p>Based on that statement do you actually believe that it's even a remotely good idea to store monetary values in an inexact form subject to errors like rounding? Anyone silly enough to do monetary calculations using floating point numbers without considering (and minimising) errors that can creep into those calculations deserves to cause errors that will see them handling class action law suits related to incorrect calculations.</p><p>BCD rules!</p></div>
	</htmltext>
<tokenext>Before converting it to a double or float point or whatever you are using ...Based on that statement do you actually believe that it 's even a remotely good idea to store monetary values in an inexact form subject to errors like rounding ?
Anyone silly enough to do monetary calculations using floating point numbers without considering ( and minimising ) errors that can creep into those calculations deserves to cause errors that will see them handling class action law suits related to incorrect calculations.BCD rules !</tokentext>
<sentencetext>Before converting it to a double or float point or whatever you are using ...Based on that statement do you actually believe that it's even a remotely good idea to store monetary values in an inexact form subject to errors like rounding?
Anyone silly enough to do monetary calculations using floating point numbers without considering (and minimising) errors that can creep into those calculations deserves to cause errors that will see them handling class action law suits related to incorrect calculations.BCD rules!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227308</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226568</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257180480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Well, guess what? We usually do not use the point at all. In common usage, 1000's are seperated by spaces : 10 000,00 Euro, to give an example.<br>Now why the comma? Because the number does not end at the "decimal seperator", and the comma is much easier to actually read.</p><p>10 000,00<br>10 000.00</p><p>Pretty obvious, yes?</p></htmltext>
<tokenext>Well , guess what ?
We usually do not use the point at all .
In common usage , 1000 's are seperated by spaces : 10 000,00 Euro , to give an example.Now why the comma ?
Because the number does not end at the " decimal seperator " , and the comma is much easier to actually read.10 000,0010 000.00Pretty obvious , yes ?</tokentext>
<sentencetext>Well, guess what?
We usually do not use the point at all.
In common usage, 1000's are seperated by spaces : 10 000,00 Euro, to give an example.Now why the comma?
Because the number does not end at the "decimal seperator", and the comma is much easier to actually read.10 000,0010 000.00Pretty obvious, yes?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30233612</id>
	<title>Re:You mean 11,500 Euro</title>
	<author>Golddess</author>
	<datestamp>1257180600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Except that across the pond they <i>don't</i> use a comma as a kilo separator, but instead use it as a decimal separator.</htmltext>
<tokenext>Except that across the pond they do n't use a comma as a kilo separator , but instead use it as a decimal separator .</tokentext>
<sentencetext>Except that across the pond they don't use a comma as a kilo separator, but instead use it as a decimal separator.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226868</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226554</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257180420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Europeans don't "swap periods and commas". They all use the comma as decimal separator, and some of them use periods as thousands separator against standards. Thousands should always be separated with a space. Either periods or commas make no sense for separating thousands, as this separation does not *mean* anything, it is only here to make big numbers easier to read.</p></htmltext>
<tokenext>Europeans do n't " swap periods and commas " .
They all use the comma as decimal separator , and some of them use periods as thousands separator against standards .
Thousands should always be separated with a space .
Either periods or commas make no sense for separating thousands , as this separation does not * mean * anything , it is only here to make big numbers easier to read .</tokentext>
<sentencetext>Europeans don't "swap periods and commas".
They all use the comma as decimal separator, and some of them use periods as thousands separator against standards.
Thousands should always be separated with a space.
Either periods or commas make no sense for separating thousands, as this separation does not *mean* anything, it is only here to make big numbers easier to read.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230112</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257153900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>A comma is simply a separator, used within sentences. So why would it be used to separate decimals?</p></div><p>Because that is the purpose of a "decimal separator", as it is also called in general? To separate the the integer and the fractional part of a number?</p><p>http://en.wikipedia.org/wiki/Decimal\_separator</p><p><div class="quote"><p>A period ends a sentence or statement, which to me should imply a whole number.</p></div><p>According to your argument, if you want to write "three and a half" it sounds to me to be a bit illogical to but something that "ends a statement after 3", because the statement does not really end there.</p></div>
	</htmltext>
<tokenext>A comma is simply a separator , used within sentences .
So why would it be used to separate decimals ? Because that is the purpose of a " decimal separator " , as it is also called in general ?
To separate the the integer and the fractional part of a number ? http : //en.wikipedia.org/wiki/Decimal \ _separatorA period ends a sentence or statement , which to me should imply a whole number.According to your argument , if you want to write " three and a half " it sounds to me to be a bit illogical to but something that " ends a statement after 3 " , because the statement does not really end there .</tokentext>
<sentencetext>A comma is simply a separator, used within sentences.
So why would it be used to separate decimals?Because that is the purpose of a "decimal separator", as it is also called in general?
To separate the the integer and the fractional part of a number?http://en.wikipedia.org/wiki/Decimal\_separatorA period ends a sentence or statement, which to me should imply a whole number.According to your argument, if you want to write "three and a half" it sounds to me to be a bit illogical to but something that "ends a statement after 3", because the statement does not really end there.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226722</id>
	<title>Re:God Bless the USA!</title>
	<author>Tim C</author>
	<datestamp>1257181200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>i'll grant that metric is better than imperial, but i think this is one thing where we have the better idea.</i></p><p>Using a comma or a period for the decimal separator is not a metric vs imperial issue, neither system mandates the character used for that.</p></htmltext>
<tokenext>i 'll grant that metric is better than imperial , but i think this is one thing where we have the better idea.Using a comma or a period for the decimal separator is not a metric vs imperial issue , neither system mandates the character used for that .</tokentext>
<sentencetext>i'll grant that metric is better than imperial, but i think this is one thing where we have the better idea.Using a comma or a period for the decimal separator is not a metric vs imperial issue, neither system mandates the character used for that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227282</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1257183960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>And as a European, I never understood why Americans (and others) use the visually smaller separator at the more important place, and vice versa.</p><p>Also, what does grammar have to do with it?</p></htmltext>
<tokenext>And as a European , I never understood why Americans ( and others ) use the visually smaller separator at the more important place , and vice versa.Also , what does grammar have to do with it ?</tokentext>
<sentencetext>And as a European, I never understood why Americans (and others) use the visually smaller separator at the more important place, and vice versa.Also, what does grammar have to do with it?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229334</id>
	<title>Re:God Bless the USA!</title>
	<author>Kr3m3Puff</author>
	<datestamp>1257193260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Well, we should really thank the Hindu-Arabs for coming up with our modern digits to make a decimal system easier, otherwise we would have been going around using something like MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMM in our ATM.</p></htmltext>
<tokenext>Well , we should really thank the Hindu-Arabs for coming up with our modern digits to make a decimal system easier , otherwise we would have been going around using something like MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMM in our ATM .</tokentext>
<sentencetext>Well, we should really thank the Hindu-Arabs for coming up with our modern digits to make a decimal system easier, otherwise we would have been going around using something like MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMMM MMM in our ATM.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226332</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235468</id>
	<title>Re:Periods and commas.</title>
	<author>Anonymous</author>
	<datestamp>1259235540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>&gt;I never understood why the hell Europeans swap periods and commas.</p><p>Europeans were using the periods and commas and Grammar way before Americans exist.<br>Better studying some history here...</p></htmltext>
<tokenext>&gt; I never understood why the hell Europeans swap periods and commas.Europeans were using the periods and commas and Grammar way before Americans exist.Better studying some history here.. .</tokentext>
<sentencetext>&gt;I never understood why the hell Europeans swap periods and commas.Europeans were using the periods and commas and Grammar way before Americans exist.Better studying some history here...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235670</id>
	<title>Re:You mean 11,500 Euro</title>
	<author>hfranz</author>
	<datestamp>1259237820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>In financial software one often uses fixed point decimal numbers or rather an integer representation of monetary amounts in terms of the smallest unit of the currency, like euro cents. For securities usually tenths of cents are used.</p><p>This is due to the numerical instability of floating point numbers for certain values like 1.01 which can only be approximated in base 2 mantissa and exponent notation. Thus floating point is ruled out and fixed point decimal numbers are used. Lazyness and/or the unavailability of a native fixed point decimal type on some legacy platforms leads to the use of simple integer numbers.</p><p>To an inexperienced programmer, such currency values just look like integer amounts and the unit of the amounts is ignored, so the mistake mentioned in TFA actually happens a lot during development, but is usually found by unit and QA tests.</p><p>So the lesson to be learned from this  is to thoroughly test your financial software. But we all do that, do we?</p></htmltext>
<tokenext>In financial software one often uses fixed point decimal numbers or rather an integer representation of monetary amounts in terms of the smallest unit of the currency , like euro cents .
For securities usually tenths of cents are used.This is due to the numerical instability of floating point numbers for certain values like 1.01 which can only be approximated in base 2 mantissa and exponent notation .
Thus floating point is ruled out and fixed point decimal numbers are used .
Lazyness and/or the unavailability of a native fixed point decimal type on some legacy platforms leads to the use of simple integer numbers.To an inexperienced programmer , such currency values just look like integer amounts and the unit of the amounts is ignored , so the mistake mentioned in TFA actually happens a lot during development , but is usually found by unit and QA tests.So the lesson to be learned from this is to thoroughly test your financial software .
But we all do that , do we ?</tokentext>
<sentencetext>In financial software one often uses fixed point decimal numbers or rather an integer representation of monetary amounts in terms of the smallest unit of the currency, like euro cents.
For securities usually tenths of cents are used.This is due to the numerical instability of floating point numbers for certain values like 1.01 which can only be approximated in base 2 mantissa and exponent notation.
Thus floating point is ruled out and fixed point decimal numbers are used.
Lazyness and/or the unavailability of a native fixed point decimal type on some legacy platforms leads to the use of simple integer numbers.To an inexperienced programmer, such currency values just look like integer amounts and the unit of the amounts is ignored, so the mistake mentioned in TFA actually happens a lot during development, but is usually found by unit and QA tests.So the lesson to be learned from this  is to thoroughly test your financial software.
But we all do that, do we?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226868</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226482</id>
	<title>Re:For the most part.</title>
	<author>dontclapthrowmoney</author>
	<datestamp>1257180060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Not a horrible suggestion for some situations, but the space just doesn't work for me... it looks like two different numbers, especially if you're writing a list of numbers next each other - do you use comma then?  <br> <br>

50 006.49, 14 032.45, 200 154 209.45,
<br> <br>
Did I miss a comma and one of the numbers is also missing the<nobr> <wbr></nobr>.00, did I miss a decimal point somewhere and the decimal is more precise, or is the last number just really large?
<br> <br>
Not in favor of the comma separators in large numbers, it is not universally understood, so don't do it.
<br> <br>
50006.49 14032.45 200154209.45
<br> <br>
I think this number sequence would be interpreted correctly in most places, most people (even people who normally use decimal commas) would understand what the decimal point represents here.</htmltext>
<tokenext>Not a horrible suggestion for some situations , but the space just does n't work for me... it looks like two different numbers , especially if you 're writing a list of numbers next each other - do you use comma then ?
50 006.49 , 14 032.45 , 200 154 209.45 , Did I miss a comma and one of the numbers is also missing the .00 , did I miss a decimal point somewhere and the decimal is more precise , or is the last number just really large ?
Not in favor of the comma separators in large numbers , it is not universally understood , so do n't do it .
50006.49 14032.45 200154209.45 I think this number sequence would be interpreted correctly in most places , most people ( even people who normally use decimal commas ) would understand what the decimal point represents here .</tokentext>
<sentencetext>Not a horrible suggestion for some situations, but the space just doesn't work for me... it looks like two different numbers, especially if you're writing a list of numbers next each other - do you use comma then?
50 006.49, 14 032.45, 200 154 209.45,
 
Did I miss a comma and one of the numbers is also missing the .00, did I miss a decimal point somewhere and the decimal is more precise, or is the last number just really large?
Not in favor of the comma separators in large numbers, it is not universally understood, so don't do it.
50006.49 14032.45 200154209.45
 
I think this number sequence would be interpreted correctly in most places, most people (even people who normally use decimal commas) would understand what the decimal point represents here.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227292</id>
	<title>Re:God Bless the USA!</title>
	<author>plague3106</author>
	<datestamp>1257184020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Well that, in language commas are used in lists to group things, or parts  of a sentence... so it makes more sense to use a comma to group otherwise insignificant digits.</p></htmltext>
<tokenext>Well that , in language commas are used in lists to group things , or parts of a sentence... so it makes more sense to use a comma to group otherwise insignificant digits .</tokentext>
<sentencetext>Well that, in language commas are used in lists to group things, or parts  of a sentence... so it makes more sense to use a comma to group otherwise insignificant digits.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227280</id>
	<title>Translated article</title>
	<author>Anonymous</author>
	<datestamp>1257183960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>BancoPosta: depositors debited with thousands of euros, but it's a mistake</p><p>Thousands of customers of PosteItaliane, and in particular BancoPosta were stunned this morning.  Thousands of euros vanished, overdrafts for many and unability to pay with a debit card or withdraw money from an ATM.  "It was an accounting error, which caused a higher debit than was factual,"  people explain from Poste Italiane.</p><p>In practice, the last performed operation's decimal point has shifted, adding two more zeros.  For instance, for a 115 euro bill, the charge was 11,500.  "A mistake which did not occur for all depositors - they add - but only for those who had made recent transactions. "</p><p>No way to contact the call center (803,160): the line drops after a few minutes wait.</p><p>The problem has not been solved yet but the press office of Poste Italiane has assured us that in a few hours--tomorrow morning at worst--, the drawback would be overcome and - of course - without interest charges for those who had found their account in overdraft.</p><p>Dozens of reports came to ADOC from alarmed depositors.  President Carlo Pileri promises: "If account avaabiity is not restored within 24 hours, ADOC will make their attorneys available in order to pursue a possible lawsuit, including compensation for such damages as may have been incurred."</p></htmltext>
<tokenext>BancoPosta : depositors debited with thousands of euros , but it 's a mistakeThousands of customers of PosteItaliane , and in particular BancoPosta were stunned this morning .
Thousands of euros vanished , overdrafts for many and unability to pay with a debit card or withdraw money from an ATM .
" It was an accounting error , which caused a higher debit than was factual , " people explain from Poste Italiane.In practice , the last performed operation 's decimal point has shifted , adding two more zeros .
For instance , for a 115 euro bill , the charge was 11,500 .
" A mistake which did not occur for all depositors - they add - but only for those who had made recent transactions .
" No way to contact the call center ( 803,160 ) : the line drops after a few minutes wait.The problem has not been solved yet but the press office of Poste Italiane has assured us that in a few hours--tomorrow morning at worst-- , the drawback would be overcome and - of course - without interest charges for those who had found their account in overdraft.Dozens of reports came to ADOC from alarmed depositors .
President Carlo Pileri promises : " If account avaabiity is not restored within 24 hours , ADOC will make their attorneys available in order to pursue a possible lawsuit , including compensation for such damages as may have been incurred .
"</tokentext>
<sentencetext>BancoPosta: depositors debited with thousands of euros, but it's a mistakeThousands of customers of PosteItaliane, and in particular BancoPosta were stunned this morning.
Thousands of euros vanished, overdrafts for many and unability to pay with a debit card or withdraw money from an ATM.
"It was an accounting error, which caused a higher debit than was factual,"  people explain from Poste Italiane.In practice, the last performed operation's decimal point has shifted, adding two more zeros.
For instance, for a 115 euro bill, the charge was 11,500.
"A mistake which did not occur for all depositors - they add - but only for those who had made recent transactions.
"No way to contact the call center (803,160): the line drops after a few minutes wait.The problem has not been solved yet but the press office of Poste Italiane has assured us that in a few hours--tomorrow morning at worst--, the drawback would be overcome and - of course - without interest charges for those who had found their account in overdraft.Dozens of reports came to ADOC from alarmed depositors.
President Carlo Pileri promises: "If account avaabiity is not restored within 24 hours, ADOC will make their attorneys available in order to pursue a possible lawsuit, including compensation for such damages as may have been incurred.
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231768</id>
	<title>Re:God Bless the USA!</title>
	<author>selven</author>
	<datestamp>1257164880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>So trucks and cars will drive in opposite directions, causing a whole bunch of crashes? So that's the disaster that's supposed to happen in 2012!</p></htmltext>
<tokenext>So trucks and cars will drive in opposite directions , causing a whole bunch of crashes ?
So that 's the disaster that 's supposed to happen in 2012 !</tokentext>
<sentencetext>So trucks and cars will drive in opposite directions, causing a whole bunch of crashes?
So that's the disaster that's supposed to happen in 2012!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227320</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162</id>
	<title>You mean 11,500 Euro</title>
	<author>Anonymous</author>
	<datestamp>1257178620000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext>You mean 11,500 Euro as 11.500 Euro.</htmltext>
<tokenext>You mean 11,500 Euro as 11.500 Euro .</tokentext>
<sentencetext>You mean 11,500 Euro as 11.500 Euro.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226650</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257180900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><i>Do you know the nightmarish hell that is an Excel localized in French while being part of an international team ? Copy-paste of the same data using Excel EN or Excel FR will result in either 115.5 or 115,5 leading to interesting bugs to track...</i></p><p>Did you know that<nobr> <wbr></nobr>.csv files are different too? Excel in French expects<nobr> <wbr></nobr>.csv files to have fields separated by semicolons.</p></htmltext>
<tokenext>Do you know the nightmarish hell that is an Excel localized in French while being part of an international team ?
Copy-paste of the same data using Excel EN or Excel FR will result in either 115.5 or 115,5 leading to interesting bugs to track...Did you know that .csv files are different too ?
Excel in French expects .csv files to have fields separated by semicolons .</tokentext>
<sentencetext>Do you know the nightmarish hell that is an Excel localized in French while being part of an international team ?
Copy-paste of the same data using Excel EN or Excel FR will result in either 115.5 or 115,5 leading to interesting bugs to track...Did you know that .csv files are different too?
Excel in French expects .csv files to have fields separated by semicolons.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172</id>
	<title>God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257178620000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Our Comma to separate numbers and periods to indicate decimal are far superior to your backward period to separate numbers and comma to indicate a decimal number!</p></htmltext>
<tokenext>Our Comma to separate numbers and periods to indicate decimal are far superior to your backward period to separate numbers and comma to indicate a decimal number !</tokentext>
<sentencetext>Our Comma to separate numbers and periods to indicate decimal are far superior to your backward period to separate numbers and comma to indicate a decimal number!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30233804</id>
	<title>Re:You mean 11,500 Euro</title>
	<author>kingturkey</author>
	<datestamp>1257183060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>How can this be modded as informative? It's nonsensical and informs nothing without the context. I guess you could assume that the poster is in an English speaking country and thus uses decimal points and commas to separate unit groupings, but there are plenty of Europeans here posting in English, especially given that this article is about an Italian incident. How about:</p><p><div class="quote"><p>You mean 11 500 Euro as 11.500 Euro.</p></div><p>I think that's what you mean, but I can't be sure. Using anything other than a space (or half space) to separate groups of (three) digits &mdash; that's a comma <i>or</i> a period &mdash; is stupid and is the reason this bug occurred.<br>Why can't everybody just follow the SI standard and use a comma or a period for the decimal point and <b>no</b> mark for unit grouping?</p></div>
	</htmltext>
<tokenext>How can this be modded as informative ?
It 's nonsensical and informs nothing without the context .
I guess you could assume that the poster is in an English speaking country and thus uses decimal points and commas to separate unit groupings , but there are plenty of Europeans here posting in English , especially given that this article is about an Italian incident .
How about : You mean 11 500 Euro as 11.500 Euro.I think that 's what you mean , but I ca n't be sure .
Using anything other than a space ( or half space ) to separate groups of ( three ) digits    that 's a comma or a period    is stupid and is the reason this bug occurred.Why ca n't everybody just follow the SI standard and use a comma or a period for the decimal point and no mark for unit grouping ?</tokentext>
<sentencetext>How can this be modded as informative?
It's nonsensical and informs nothing without the context.
I guess you could assume that the poster is in an English speaking country and thus uses decimal points and commas to separate unit groupings, but there are plenty of Europeans here posting in English, especially given that this article is about an Italian incident.
How about:You mean 11 500 Euro as 11.500 Euro.I think that's what you mean, but I can't be sure.
Using anything other than a space (or half space) to separate groups of (three) digits — that's a comma or a period — is stupid and is the reason this bug occurred.Why can't everybody just follow the SI standard and use a comma or a period for the decimal point and no mark for unit grouping?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227062</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257182820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>A period is a more solid division than a comma.</p>  </div><p>Experiment:<br>10 000,00<br>10 000.00</p><p>Hmm... hypothesis refuted. Try again?</p></div>
	</htmltext>
<tokenext>A period is a more solid division than a comma .
Experiment : 10 000,0010 000.00Hmm... hypothesis refuted .
Try again ?</tokentext>
<sentencetext>A period is a more solid division than a comma.
Experiment:10 000,0010 000.00Hmm... hypothesis refuted.
Try again?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226838</id>
	<title>Re:God Bless the USA!</title>
	<author>Anonymous</author>
	<datestamp>1257181740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Well, that and the fact that in math you use a period to separate the whole from the fraction.  Even European math uses the same system.</p><p>So basically the comma fraction separator is an anomaly.  It makes no sense because it's not how anyone does math.</p></htmltext>
<tokenext>Well , that and the fact that in math you use a period to separate the whole from the fraction .
Even European math uses the same system.So basically the comma fraction separator is an anomaly .
It makes no sense because it 's not how anyone does math .</tokentext>
<sentencetext>Well, that and the fact that in math you use a period to separate the whole from the fraction.
Even European math uses the same system.So basically the comma fraction separator is an anomaly.
It makes no sense because it's not how anyone does math.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30233654</id>
	<title>Re:You mean 11,500 Euro</title>
	<author>Golddess</author>
	<datestamp>1257181020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Erm, no?  Whether you're using a comma or a period as the decimal, one of your values has a three-digit cents place (and to the best of my knowledge the Euro does not have a hundredths piece), so I've no clue what exactly you are saying.<br>
<br>
To Americanize the results, it would be debiting a 115.00 transaction as 11500.</htmltext>
<tokenext>Erm , no ?
Whether you 're using a comma or a period as the decimal , one of your values has a three-digit cents place ( and to the best of my knowledge the Euro does not have a hundredths piece ) , so I 've no clue what exactly you are saying .
To Americanize the results , it would be debiting a 115.00 transaction as 11500 .</tokentext>
<sentencetext>Erm, no?
Whether you're using a comma or a period as the decimal, one of your values has a three-digit cents place (and to the best of my knowledge the Euro does not have a hundredths piece), so I've no clue what exactly you are saying.
To Americanize the results, it would be debiting a 115.00 transaction as 11500.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230846</id>
	<title>Re:Good to be a programmer</title>
	<author>Anonymous</author>
	<datestamp>1257158220000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Yes, because regulation always works. Just look at banking, the most regulated industry known. Perfect...</p></htmltext>
<tokenext>Yes , because regulation always works .
Just look at banking , the most regulated industry known .
Perfect.. .</tokentext>
<sentencetext>Yes, because regulation always works.
Just look at banking, the most regulated industry known.
Perfect...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226218</id>
	<title>Sounds like a hacker got a decimal in the wrong pl</title>
	<author>Anonymous</author>
	<datestamp>1257178800000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Sounds like a hacker got a decimal in the wrong place and now they need to unload the money some where fast they have try talking to drug dealers about money laundering.</p></htmltext>
<tokenext>Sounds like a hacker got a decimal in the wrong place and now they need to unload the money some where fast they have try talking to drug dealers about money laundering .</tokentext>
<sentencetext>Sounds like a hacker got a decimal in the wrong place and now they need to unload the money some where fast they have try talking to drug dealers about money laundering.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226420</id>
	<title>At least they roll back without a law suit</title>
	<author>Anonymous</author>
	<datestamp>1257179820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>At least they roll this back immediately. Here in the US of A they would wait for a class action law suit to develop and then offer a settlement that leaves their customers with pennies on the dollar.</p></htmltext>
<tokenext>At least they roll this back immediately .
Here in the US of A they would wait for a class action law suit to develop and then offer a settlement that leaves their customers with pennies on the dollar .</tokentext>
<sentencetext>At least they roll this back immediately.
Here in the US of A they would wait for a class action law suit to develop and then offer a settlement that leaves their customers with pennies on the dollar.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296</id>
	<title>Re:For the most part.</title>
	<author>Anonymous</author>
	<datestamp>1257179160000</datestamp>
	<modclass>Troll</modclass>
	<modscore>1</modscore>
	<htmltext><p>Int-like dataypes have hard limit of 2^32 or 64 or even more.</p><p>Eventually you simply want something bigger. And you also want to use somethign that can work well with XML schemans and several other systems. You simply have to use string as your other option is 32 bit int.</p><p>Also, String unlike Float does not loose precission. A lot slower, but precise.</p></htmltext>
<tokenext>Int-like dataypes have hard limit of 2 ^ 32 or 64 or even more.Eventually you simply want something bigger .
And you also want to use somethign that can work well with XML schemans and several other systems .
You simply have to use string as your other option is 32 bit int.Also , String unlike Float does not loose precission .
A lot slower , but precise .</tokentext>
<sentencetext>Int-like dataypes have hard limit of 2^32 or 64 or even more.Eventually you simply want something bigger.
And you also want to use somethign that can work well with XML schemans and several other systems.
You simply have to use string as your other option is 32 bit int.Also, String unlike Float does not loose precission.
A lot slower, but precise.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228980</id>
	<title>Re:God Bless the USA!</title>
	<author>Toze</author>
	<datestamp>1257191640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Do you know the nightmarish hell that is an Excel</p></div><p>Yes.</p></div>
	</htmltext>
<tokenext>Do you know the nightmarish hell that is an ExcelYes .</tokentext>
<sentencetext>Do you know the nightmarish hell that is an ExcelYes.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226440</id>
	<title>This is stupid.</title>
	<author>Anonymous</author>
	<datestamp>1257179940000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>There's a reason we separate the data model from the external view and internal controller mechanisms. A moving decimal shouldn't affect the internal math, it should be nothing more than a harmless display error. The fact a moving decimal actually affected the internal management is sad. Well, maybe I'm being an elitist boob, but this seems more like negligent high level design that compounded a low level bug into being much worse than it should have been.</htmltext>
<tokenext>There 's a reason we separate the data model from the external view and internal controller mechanisms .
A moving decimal should n't affect the internal math , it should be nothing more than a harmless display error .
The fact a moving decimal actually affected the internal management is sad .
Well , maybe I 'm being an elitist boob , but this seems more like negligent high level design that compounded a low level bug into being much worse than it should have been .</tokentext>
<sentencetext>There's a reason we separate the data model from the external view and internal controller mechanisms.
A moving decimal shouldn't affect the internal math, it should be nothing more than a harmless display error.
The fact a moving decimal actually affected the internal management is sad.
Well, maybe I'm being an elitist boob, but this seems more like negligent high level design that compounded a low level bug into being much worse than it should have been.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226468</id>
	<title>Decimal and Thousands separators</title>
	<author>Razalhague</author>
	<datestamp>1257180000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I really wish it could be standardized with the decimal separator being <strong>either</strong> a comma or a period and the thousands separator being <strong>neither</strong>.</htmltext>
<tokenext>I really wish it could be standardized with the decimal separator being either a comma or a period and the thousands separator being neither .</tokentext>
<sentencetext>I really wish it could be standardized with the decimal separator being either a comma or a period and the thousands separator being neither.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226728</id>
	<title>This Could Never Happen In The U.S.</title>
	<author>Anonymous</author>
	<datestamp>1257181200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>People in the U.S. with that kind of cash are considered so rich that they don't go down to the post office themselves.</htmltext>
<tokenext>People in the U.S. with that kind of cash are considered so rich that they do n't go down to the post office themselves .</tokentext>
<sentencetext>People in the U.S. with that kind of cash are considered so rich that they don't go down to the post office themselves.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229326</id>
	<title>Re:Good to be a programmer</title>
	<author>Anonymous</author>
	<datestamp>1257193200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Your post wants to be sarcastic, but it shouldn't. Software engineering is NOT engineering, and it shouldn't be.<br>Build a bridge, use engineering standards. If you don't, people die.<br>Build software, don't use engineering standards. If you do, it will take 1000x more time.</p><p>It's preposterous to want to apply engineering principles to code all the time. It's like requiring formal proofs for your code. It can't be done. It shouldn't be done. It's useless in 100-1e-15 percent of the cases.</p><p>Your post should be modded Troll, not insightful...</p></htmltext>
<tokenext>Your post wants to be sarcastic , but it should n't .
Software engineering is NOT engineering , and it should n't be.Build a bridge , use engineering standards .
If you do n't , people die.Build software , do n't use engineering standards .
If you do , it will take 1000x more time.It 's preposterous to want to apply engineering principles to code all the time .
It 's like requiring formal proofs for your code .
It ca n't be done .
It should n't be done .
It 's useless in 100-1e-15 percent of the cases.Your post should be modded Troll , not insightful.. .</tokentext>
<sentencetext>Your post wants to be sarcastic, but it shouldn't.
Software engineering is NOT engineering, and it shouldn't be.Build a bridge, use engineering standards.
If you don't, people die.Build software, don't use engineering standards.
If you do, it will take 1000x more time.It's preposterous to want to apply engineering principles to code all the time.
It's like requiring formal proofs for your code.
It can't be done.
It shouldn't be done.
It's useless in 100-1e-15 percent of the cases.Your post should be modded Troll, not insightful...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227298</id>
	<title>Re:God Bless the USA!</title>
	<author>orzetto</author>
	<datestamp>1257184080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>On the other hand, the comma is graphically stronger and more visible. The period is so graphically weak that we have the rule to use an upper-case letter after it to make sure people do not miss it.</p></htmltext>
<tokenext>On the other hand , the comma is graphically stronger and more visible .
The period is so graphically weak that we have the rule to use an upper-case letter after it to make sure people do not miss it .</tokentext>
<sentencetext>On the other hand, the comma is graphically stronger and more visible.
The period is so graphically weak that we have the rule to use an upper-case letter after it to make sure people do not miss it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226868</id>
	<title>Re:You mean 11,500 Euro</title>
	<author>Anonymous</author>
	<datestamp>1257181920000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>That does not make sense.<br>Presuming the amount was 115,00 and somebody (stupidly) padded the number with zeroes  it would result in 115,000 -&gt; 115 000 Euro if we interpret the comma as a kilo seperator.<br>But there is not really a way that you can convert 115,00 to 11 500; not without \_moving\_ the seperator (or omitting it completely) and that is beyond stupidity.</p></htmltext>
<tokenext>That does not make sense.Presuming the amount was 115,00 and somebody ( stupidly ) padded the number with zeroes it would result in 115,000 - &gt; 115 000 Euro if we interpret the comma as a kilo seperator.But there is not really a way that you can convert 115,00 to 11 500 ; not without \ _moving \ _ the seperator ( or omitting it completely ) and that is beyond stupidity .</tokentext>
<sentencetext>That does not make sense.Presuming the amount was 115,00 and somebody (stupidly) padded the number with zeroes  it would result in 115,000 -&gt; 115 000 Euro if we interpret the comma as a kilo seperator.But there is not really a way that you can convert 115,00 to 11 500; not without \_moving\_ the seperator (or omitting it completely) and that is beyond stupidity.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226270</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226488</id>
	<title>Re:Obligatory Office Space</title>
	<author>bytethese</author>
	<datestamp>1257180060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It's not some mundane detail Michael!<br> <br>

Apparently I got logged off with my last comment, also not a mundane detail!</htmltext>
<tokenext>It 's not some mundane detail Michael !
Apparently I got logged off with my last comment , also not a mundane detail !</tokentext>
<sentencetext>It's not some mundane detail Michael!
Apparently I got logged off with my last comment, also not a mundane detail!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226166</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229426</id>
	<title>FxCop</title>
	<author>Carra</author>
	<datestamp>1257193680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Our build system now checks the code with M$ FxCop. Any problems with the cultural settings and the build stops.
<br> <br>
We hit a brick the day our program was started in Turkey. Having that problem once is more than enough.</htmltext>
<tokenext>Our build system now checks the code with M $ FxCop .
Any problems with the cultural settings and the build stops .
We hit a brick the day our program was started in Turkey .
Having that problem once is more than enough .</tokentext>
<sentencetext>Our build system now checks the code with M$ FxCop.
Any problems with the cultural settings and the build stops.
We hit a brick the day our program was started in Turkey.
Having that problem once is more than enough.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227180</id>
	<title>Re:Periods and commas.</title>
	<author>BoppreH</author>
	<datestamp>1257183420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It's easier to see the comma, and if you don't notice the period it's not a big deal.</htmltext>
<tokenext>It 's easier to see the comma , and if you do n't notice the period it 's not a big deal .</tokentext>
<sentencetext>It's easier to see the comma, and if you don't notice the period it's not a big deal.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226384</id>
	<title>Back to Roman numerals</title>
	<author>ewg</author>
	<datestamp>1257179700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I bet you LXXVII bucks this would not have happened with Roman numerals. That's what they get for upgrading a perfectly good numeration system.</htmltext>
<tokenext>I bet you LXXVII bucks this would not have happened with Roman numerals .
That 's what they get for upgrading a perfectly good numeration system .</tokentext>
<sentencetext>I bet you LXXVII bucks this would not have happened with Roman numerals.
That's what they get for upgrading a perfectly good numeration system.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226154</id>
	<title>This just in</title>
	<author>Anonymous</author>
	<datestamp>1257178560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Small errors, such as TYPOS can cause big problems.</htmltext>
<tokenext>Small errors , such as TYPOS can cause big problems .</tokentext>
<sentencetext>Small errors, such as TYPOS can cause big problems.</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_85</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227028
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235402
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_110</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229326
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228310
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_90</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30233804
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_101</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226332
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226556
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227320
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231768
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_64</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227062
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226332
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229334
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_100</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226640
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226332
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226556
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226808
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227120
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30234278
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_77</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228980
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226918
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228646
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_93</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226440
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229638
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_84</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228236
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226590
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226270
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226868
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235670
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226784
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_83</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228044
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227340
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_106</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227308
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229732
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_74</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228246
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_69</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228720
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227420
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229506
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_113</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226748
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30241764
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30233654
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226730
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227292
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_99</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228240
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226332
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226556
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226756
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_75</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226568
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226166
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226488
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230534
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_89</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227472
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_82</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30374040
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228260
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_105</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228230
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_68</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227788
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228040
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_96</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230112
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227078
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227744
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_104</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226826
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_72</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230310
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230360
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_58</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226844
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227308
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230050
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_111</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226650
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30232032
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_63</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227308
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231960
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_97</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226332
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226556
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226798
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227752
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227686
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_88</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227004
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227692
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30232104
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_91</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226490
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227504
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_87</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228046
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_78</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226740
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_103</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235290
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_94</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228164
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_55</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226270
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226868
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30233612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229426
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226302
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226482
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_62</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229236
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227514
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227172
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_61</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226468
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227618
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_79</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226940
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226722
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30232626
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_86</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231452
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_109</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226994
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_80</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226544
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231584
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_108</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226794
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_76</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235468
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228458
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_81</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226760
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226440
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227210
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_67</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230320
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_60</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227204
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227710
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226302
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226454
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226838
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230396
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235460
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_107</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226468
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226830
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_73</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226530
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_98</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228264
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227264
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_59</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227006
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227044
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_92</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226834
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_112</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226384
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228328
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227714
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226754
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_66</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227414
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227588
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227282
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_102</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226284
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_70</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228388
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_65</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227450
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_56</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227420
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230170
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231836
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226778
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_95</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227180
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229626
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226332
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227296
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_71</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226554
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227298
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_25_1448218_57</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230846
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226538
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229426
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230310
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235290
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227308
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230050
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229732
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231960
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228240
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227004
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227006
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226630
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226384
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228328
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226440
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229638
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227210
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227692
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30232104
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226394
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227204
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227044
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230112
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226554
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227450
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227340
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230534
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226940
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226544
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226826
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226740
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226844
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235468
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30232032
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226510
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227420
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229506
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230170
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227504
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226754
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226748
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30241764
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235374
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226794
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228388
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227282
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228236
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227180
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230320
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226568
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228044
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226162
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227788
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30233654
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226270
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226868
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30233612
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235670
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227714
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30233804
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226784
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226166
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226488
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226258
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227686
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227710
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229326
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231584
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228310
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230360
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226994
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228646
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228260
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230396
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227514
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228720
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30230846
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226778
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228230
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226172
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226382
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227744
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226650
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229626
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235460
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228980
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226332
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229334
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227296
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226556
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226808
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226756
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226798
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227752
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227320
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231768
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226284
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226436
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226730
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227292
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30232626
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227264
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226834
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228458
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226722
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226838
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227062
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228264
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227298
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228040
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231452
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227472
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227414
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226210
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227588
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228046
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226296
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227078
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226490
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226476
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226640
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30231836
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30234278
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227172
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227028
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227120
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226590
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226356
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228246
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30235402
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226760
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30228164
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30229236
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30374040
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226530
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226918
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226302
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226482
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226454
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226206
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226728
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226468
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226830
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30227618
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226154
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226182
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_25_1448218.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_25_1448218.30226420
</commentlist>
</conversation>
