<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_10_30_1347216</id>
	<title>ICANN Approves Non-Latin ccTLDs</title>
	<author>kdawson</author>
	<datestamp>1256913180000</datestamp>
	<htmltext>Several readers including alphadogg tipped the news that <a href="http://www.networkworld.com/news/2009/103009-icann-approves-internationalized-domain.html">ICANN has approved non-Latin ccTLDs</a> at its meeting in Seoul. <i>"Starting in mid-November, countries and territories will be able to apply to show domain names in their native language, a major technical tweak to the Internet designed to increase language accessibility. On Friday, the Internet's addressing authority approved a Fast-Track Process for applying for an IDN (Internationalized Domain Name) and will begin accepting applications on Nov. 16. The move comes after years of technical testing and policy development... Currently, domain names can only be displayed using the Latin alphabet letters A-Z, the digits 0-9 and the hyphen, but in future countries will be able to display country-code Top Level Domains (cc TLDs) in their native language. ... 'The usability of IDNs may be limited, as not all application software is capable of working with IDNs,' ICANN said in a <a href="http://www.icann.org/en/topics/idn/fast-track/idn-cctld-implementation-plan-30sep09-en.pdf">59-page proposal</a> (PDF) dated Sept. 30 that describes the [application] process."</i> Reader dhermann adds, "Great, now even less chance I can identify NSFW links before they are blocked by my work's big brother app and my boss is notified... again."</htmltext>
<tokenext>Several readers including alphadogg tipped the news that ICANN has approved non-Latin ccTLDs at its meeting in Seoul .
" Starting in mid-November , countries and territories will be able to apply to show domain names in their native language , a major technical tweak to the Internet designed to increase language accessibility .
On Friday , the Internet 's addressing authority approved a Fast-Track Process for applying for an IDN ( Internationalized Domain Name ) and will begin accepting applications on Nov. 16. The move comes after years of technical testing and policy development... Currently , domain names can only be displayed using the Latin alphabet letters A-Z , the digits 0-9 and the hyphen , but in future countries will be able to display country-code Top Level Domains ( cc TLDs ) in their native language .
... 'The usability of IDNs may be limited , as not all application software is capable of working with IDNs, ' ICANN said in a 59-page proposal ( PDF ) dated Sept. 30 that describes the [ application ] process .
" Reader dhermann adds , " Great , now even less chance I can identify NSFW links before they are blocked by my work 's big brother app and my boss is notified.. .
again. "</tokentext>
<sentencetext>Several readers including alphadogg tipped the news that ICANN has approved non-Latin ccTLDs at its meeting in Seoul.
"Starting in mid-November, countries and territories will be able to apply to show domain names in their native language, a major technical tweak to the Internet designed to increase language accessibility.
On Friday, the Internet's addressing authority approved a Fast-Track Process for applying for an IDN (Internationalized Domain Name) and will begin accepting applications on Nov. 16. The move comes after years of technical testing and policy development... Currently, domain names can only be displayed using the Latin alphabet letters A-Z, the digits 0-9 and the hyphen, but in future countries will be able to display country-code Top Level Domains (cc TLDs) in their native language.
... 'The usability of IDNs may be limited, as not all application software is capable of working with IDNs,' ICANN said in a 59-page proposal (PDF) dated Sept. 30 that describes the [application] process.
" Reader dhermann adds, "Great, now even less chance I can identify NSFW links before they are blocked by my work's big brother app and my boss is notified...
again."</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926501</id>
	<title>Re:Encoding?</title>
	<author>Anonymous</author>
	<datestamp>1256929080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It's a myth that all DNS related code would break.  DNS has been 8-bit clean from the very beginning.  UTF8 is the obvious choice for international domain names but the IETF screwed up.  Now the IAB is trying to fix the mess.</p><p>http://tools.ietf.org/html/draft-iab-idn-encoding-00</p></htmltext>
<tokenext>It 's a myth that all DNS related code would break .
DNS has been 8-bit clean from the very beginning .
UTF8 is the obvious choice for international domain names but the IETF screwed up .
Now the IAB is trying to fix the mess.http : //tools.ietf.org/html/draft-iab-idn-encoding-00</tokentext>
<sentencetext>It's a myth that all DNS related code would break.
DNS has been 8-bit clean from the very beginning.
UTF8 is the obvious choice for international domain names but the IETF screwed up.
Now the IAB is trying to fix the mess.http://tools.ietf.org/html/draft-iab-idn-encoding-00</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923859</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924553</id>
	<title>Re:Phishing aid</title>
	<author>pablo.cl</author>
	<datestamp>1256920680000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>There are letters in the Cyrillic alphabet that have different character codes than their look-alike letters in the Latin alphabet.</p></div><p>Remember we are talking about ccTLDs. There are no more than 200 countries that would like to use non ASCII ccTLD, and they can be inspected manually. Russia wasn't awarded Cyrillic<nobr> <wbr></nobr>.ru because it looks like Latin<nobr> <wbr></nobr>.py (Paraguay). They will get<nobr> <wbr></nobr>.fr (Russian Federation) that looks like 0p (0 with vertical bar).</p></div>
	</htmltext>
<tokenext>There are letters in the Cyrillic alphabet that have different character codes than their look-alike letters in the Latin alphabet.Remember we are talking about ccTLDs .
There are no more than 200 countries that would like to use non ASCII ccTLD , and they can be inspected manually .
Russia was n't awarded Cyrillic .ru because it looks like Latin .py ( Paraguay ) .
They will get .fr ( Russian Federation ) that looks like 0p ( 0 with vertical bar ) .</tokentext>
<sentencetext>There are letters in the Cyrillic alphabet that have different character codes than their look-alike letters in the Latin alphabet.Remember we are talking about ccTLDs.
There are no more than 200 countries that would like to use non ASCII ccTLD, and they can be inspected manually.
Russia wasn't awarded Cyrillic .ru because it looks like Latin .py (Paraguay).
They will get .fr (Russian Federation) that looks like 0p (0 with vertical bar).
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925939</id>
	<title>Re:Phishing aid</title>
	<author>Tony Hoyle</author>
	<datestamp>1256926560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>They will get<nobr> <wbr></nobr>.fr (Russian Federation) that looks like 0p (0 with vertical bar).</i></p><p>That's gonna piss off the french.</p></htmltext>
<tokenext>They will get .fr ( Russian Federation ) that looks like 0p ( 0 with vertical bar ) .That 's gon na piss off the french .</tokentext>
<sentencetext>They will get .fr (Russian Federation) that looks like 0p (0 with vertical bar).That's gonna piss off the french.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924553</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923695</id>
	<title>Perdire</title>
	<author>SEWilco</author>
	<datestamp>1256917260000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>There go my plans for world domination through venividivici.vvv</htmltext>
<tokenext>There go my plans for world domination through venividivici.vvv</tokentext>
<sentencetext>There go my plans for world domination through venividivici.vvv</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924599</id>
	<title>Just what we needed...</title>
	<author>sajuuk</author>
	<datestamp>1256920920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>More places for those damn domain squatters to snatch up before we can.</htmltext>
<tokenext>More places for those damn domain squatters to snatch up before we can .</tokentext>
<sentencetext>More places for those damn domain squatters to snatch up before we can.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925297</id>
	<title>Re:ICANN has lost it!</title>
	<author>jayme0227</author>
	<datestamp>1256923500000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>You know, except for ease of use for those who don't use Latin characters in their daily lives. But who cares about them? They should just go back to their own country and create their own internet.</p></htmltext>
<tokenext>You know , except for ease of use for those who do n't use Latin characters in their daily lives .
But who cares about them ?
They should just go back to their own country and create their own internet .</tokentext>
<sentencetext>You know, except for ease of use for those who don't use Latin characters in their daily lives.
But who cares about them?
They should just go back to their own country and create their own internet.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926455</id>
	<title>Re:Excellent idea</title>
	<author>ugen</author>
	<datestamp>1256928900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is certainly NOT the case with Russian. While alphabets are different, and majority of Russians do NOT speak a foreign language, acceptance of latin alphabet is high (nearly universal). There is absolutely no issue with using latin-based URLs or addresses and very little drive to change that.</p><p>Trying to remove universal access and Babylonize the internet under the fairly flimsy pretext of internationalization seems a very misplaced effort to me.</p><p>Imagine what would happen if instead of converging on the same "arabic" numerals, each country would keep using a different counting/numeric system? Domain names are no different - they are NOT general purpose words and they should be built using one universal approach.<br>
&nbsp;</p></htmltext>
<tokenext>This is certainly NOT the case with Russian .
While alphabets are different , and majority of Russians do NOT speak a foreign language , acceptance of latin alphabet is high ( nearly universal ) .
There is absolutely no issue with using latin-based URLs or addresses and very little drive to change that.Trying to remove universal access and Babylonize the internet under the fairly flimsy pretext of internationalization seems a very misplaced effort to me.Imagine what would happen if instead of converging on the same " arabic " numerals , each country would keep using a different counting/numeric system ?
Domain names are no different - they are NOT general purpose words and they should be built using one universal approach .
 </tokentext>
<sentencetext>This is certainly NOT the case with Russian.
While alphabets are different, and majority of Russians do NOT speak a foreign language, acceptance of latin alphabet is high (nearly universal).
There is absolutely no issue with using latin-based URLs or addresses and very little drive to change that.Trying to remove universal access and Babylonize the internet under the fairly flimsy pretext of internationalization seems a very misplaced effort to me.Imagine what would happen if instead of converging on the same "arabic" numerals, each country would keep using a different counting/numeric system?
Domain names are no different - they are NOT general purpose words and they should be built using one universal approach.
 </sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924917</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924389</id>
	<title>Re:Encoding?</title>
	<author>ReallyEvilCanine</author>
	<datestamp>1256920140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>To prvnt phishing and other abus.  provids an identifiabl stpgap to prvnt m ding smthing with th URL that I'v just dn in this mmnt.</htmltext>
<tokenext>To prvnt phishing and other abus .
provids an identifiabl stpgap to prvnt m ding smthing with th URL that I'v just dn in this mmnt .</tokentext>
<sentencetext>To prvnt phishing and other abus.
provids an identifiabl stpgap to prvnt m ding smthing with th URL that I'v just dn in this mmnt.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925355</id>
	<title>Now the web is truly geek</title>
	<author>Anonymous</author>
	<datestamp>1256923740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Finally we can do web addresses in Klingon!</p></htmltext>
<tokenext>Finally we can do web addresses in Klingon !</tokentext>
<sentencetext>Finally we can do web addresses in Klingon!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817</id>
	<title>Phishing aid</title>
	<author>querist</author>
	<datestamp>1256917800000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>This will only make phishing attacks easier unless there are SERIOUS checks on domain name registrations.

There are letters in the Cyrillic alphabet that have different character codes than their look-alike letters in the Latin alphabet. I'm sure there are other collisions as well.  I'm sure they accounted for this in the proposal, but the problem always lies in the implementation.

From a security standpoint, this is a VERY bad idea without proper regulation of domain name registrations, and so far it has been demonstrated that we cannot manage them properly even with only the Latin alphabet.

From a cultural and usability standpoint, this is a good thing. It will be easier for someone whose native language uses a non-Latin alphabet to recognize the supposed purpose of a web site by its domain name if some of those domain names can be in their native language. A hypothetical native Tamil speaker who speaks no English will be able to recognize the purpose of a site with an appropriate domain name in Tamil, for example</htmltext>
<tokenext>This will only make phishing attacks easier unless there are SERIOUS checks on domain name registrations .
There are letters in the Cyrillic alphabet that have different character codes than their look-alike letters in the Latin alphabet .
I 'm sure there are other collisions as well .
I 'm sure they accounted for this in the proposal , but the problem always lies in the implementation .
From a security standpoint , this is a VERY bad idea without proper regulation of domain name registrations , and so far it has been demonstrated that we can not manage them properly even with only the Latin alphabet .
From a cultural and usability standpoint , this is a good thing .
It will be easier for someone whose native language uses a non-Latin alphabet to recognize the supposed purpose of a web site by its domain name if some of those domain names can be in their native language .
A hypothetical native Tamil speaker who speaks no English will be able to recognize the purpose of a site with an appropriate domain name in Tamil , for example</tokentext>
<sentencetext>This will only make phishing attacks easier unless there are SERIOUS checks on domain name registrations.
There are letters in the Cyrillic alphabet that have different character codes than their look-alike letters in the Latin alphabet.
I'm sure there are other collisions as well.
I'm sure they accounted for this in the proposal, but the problem always lies in the implementation.
From a security standpoint, this is a VERY bad idea without proper regulation of domain name registrations, and so far it has been demonstrated that we cannot manage them properly even with only the Latin alphabet.
From a cultural and usability standpoint, this is a good thing.
It will be easier for someone whose native language uses a non-Latin alphabet to recognize the supposed purpose of a web site by its domain name if some of those domain names can be in their native language.
A hypothetical native Tamil speaker who speaks no English will be able to recognize the purpose of a site with an appropriate domain name in Tamil, for example</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923899</id>
	<title>Re:Encoding?</title>
	<author>NevarMore</author>
	<datestamp>1256918160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Backwards compatibility with existing systems that don't support UTF-8 but still need to make DNS queries. Ranges from basic tools like dig, to un-updated browsers, to embedded devices like routers.</p><p>Are there any public DNS servers that support this to see what happens with my existing software??</p></htmltext>
<tokenext>Backwards compatibility with existing systems that do n't support UTF-8 but still need to make DNS queries .
Ranges from basic tools like dig , to un-updated browsers , to embedded devices like routers.Are there any public DNS servers that support this to see what happens with my existing software ?
?</tokentext>
<sentencetext>Backwards compatibility with existing systems that don't support UTF-8 but still need to make DNS queries.
Ranges from basic tools like dig, to un-updated browsers, to embedded devices like routers.Are there any public DNS servers that support this to see what happens with my existing software?
?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109</id>
	<title>Excellent idea</title>
	<author>ugen</author>
	<datestamp>1256919060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Now those countries, organizations and businesses that wish to become inaccessible to most of the world (except the native speakers of their own language) can finally do so as easily as possible. Create their own little Internet reservations and stay there<nobr> <wbr></nobr>:)</p><p>As long as my software (such as Firefox) obligingly converts these IDN urls into the dash-hex notation making them obviously unreadable, I am ok with that.</p><p>Disclaimer: I am a native of non-English speaking country. I am sure a few of my countrymen will use this feature based on misplaced patriotism. I am also sure that vast majority will ignore it just like they ignore potential to use non-latin domain names that exists right now.</p></htmltext>
<tokenext>Now those countries , organizations and businesses that wish to become inaccessible to most of the world ( except the native speakers of their own language ) can finally do so as easily as possible .
Create their own little Internet reservations and stay there : ) As long as my software ( such as Firefox ) obligingly converts these IDN urls into the dash-hex notation making them obviously unreadable , I am ok with that.Disclaimer : I am a native of non-English speaking country .
I am sure a few of my countrymen will use this feature based on misplaced patriotism .
I am also sure that vast majority will ignore it just like they ignore potential to use non-latin domain names that exists right now .</tokentext>
<sentencetext>Now those countries, organizations and businesses that wish to become inaccessible to most of the world (except the native speakers of their own language) can finally do so as easily as possible.
Create their own little Internet reservations and stay there :)As long as my software (such as Firefox) obligingly converts these IDN urls into the dash-hex notation making them obviously unreadable, I am ok with that.Disclaimer: I am a native of non-English speaking country.
I am sure a few of my countrymen will use this feature based on misplaced patriotism.
I am also sure that vast majority will ignore it just like they ignore potential to use non-latin domain names that exists right now.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928427</id>
	<title>Re:Um, can they be more specific than "Unicode"?</title>
	<author>raju1kabir</author>
	<datestamp>1256894700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Unicode can mean many things - UTF-8, UTF-16, UTF-32 - so specifying Unicode is not detailed enough to implement and by not specifying, it is opening a can of worms IMO.</p></div></blockquote><p>You seem to know enough to sling a lot of words (and boy have you slung a lot of irrelevant words) but not enough to understand what you're talking about.
</p><p>I'll help. You're talking about different encodings. Well, punycode is also an encoding, in the category of UTF8 and UTF16. And it's specified. So that's all they need to do.</p></div>
	</htmltext>
<tokenext>Unicode can mean many things - UTF-8 , UTF-16 , UTF-32 - so specifying Unicode is not detailed enough to implement and by not specifying , it is opening a can of worms IMO.You seem to know enough to sling a lot of words ( and boy have you slung a lot of irrelevant words ) but not enough to understand what you 're talking about .
I 'll help .
You 're talking about different encodings .
Well , punycode is also an encoding , in the category of UTF8 and UTF16 .
And it 's specified .
So that 's all they need to do .</tokentext>
<sentencetext>Unicode can mean many things - UTF-8, UTF-16, UTF-32 - so specifying Unicode is not detailed enough to implement and by not specifying, it is opening a can of worms IMO.You seem to know enough to sling a lot of words (and boy have you slung a lot of irrelevant words) but not enough to understand what you're talking about.
I'll help.
You're talking about different encodings.
Well, punycode is also an encoding, in the category of UTF8 and UTF16.
And it's specified.
So that's all they need to do.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924161</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925705</id>
	<title>Actually might make security easier</title>
	<author>Anonymous</author>
	<datestamp>1256925360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>As you should be able to use all non-latin TLD's as a element to filter against.</p></htmltext>
<tokenext>As you should be able to use all non-latin TLD 's as a element to filter against .</tokentext>
<sentencetext>As you should be able to use all non-latin TLD's as a element to filter against.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924917</id>
	<title>Re:Excellent idea</title>
	<author>wvmarle</author>
	<datestamp>1256922180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>For example in China this will be used a lot. Other countries using non-Latin scripts will do so as well.
</p><p>Actually it was possible already for a few years to register domain names in Chinese characters in Hong Kong, but still ending in<nobr> <wbr></nobr>.hk. Now that part can also become Chinese characters as replacement for<nobr> <wbr></nobr>.hk,<nobr> <wbr></nobr>.cn or<nobr> <wbr></nobr>.tw.
</p><p>The catch was that a Chinese URL would work only within HK/China. Now this will also start to work worldwide.
</p><p>One big issue for many lower-educated Chinese is that the Latin script is as strange as Chinese characters to us. Of course you can look at the shape and recognise them, but that's it: the letters do not carry sounds to them. So it's impossible to remember an URL for those people. Even for Chinese that can read/understand the Latin script it is far harder to remember an URL that they see in say an advertisement, than if that URL were in Chinese.
</p><p>I bet the same accounts for many other languages. Japanese, Indian languages, Vietnamese (Latin letters with lots and lots of accents to make it pronounceable for them), Korean, Russian. Even many West-European languages French would be happy with adding just the accents.
</p><p>This is a major leap forward for the Internet at large, don't underestimate it just because your language (group) is doing fine with just a-z, 0-9 and hyphens. Already more than half of the Internet users worldwide is using a non-Latin script for their native language. And that's the users that are going to benefit most.</p></htmltext>
<tokenext>For example in China this will be used a lot .
Other countries using non-Latin scripts will do so as well .
Actually it was possible already for a few years to register domain names in Chinese characters in Hong Kong , but still ending in .hk .
Now that part can also become Chinese characters as replacement for .hk , .cn or .tw .
The catch was that a Chinese URL would work only within HK/China .
Now this will also start to work worldwide .
One big issue for many lower-educated Chinese is that the Latin script is as strange as Chinese characters to us .
Of course you can look at the shape and recognise them , but that 's it : the letters do not carry sounds to them .
So it 's impossible to remember an URL for those people .
Even for Chinese that can read/understand the Latin script it is far harder to remember an URL that they see in say an advertisement , than if that URL were in Chinese .
I bet the same accounts for many other languages .
Japanese , Indian languages , Vietnamese ( Latin letters with lots and lots of accents to make it pronounceable for them ) , Korean , Russian .
Even many West-European languages French would be happy with adding just the accents .
This is a major leap forward for the Internet at large , do n't underestimate it just because your language ( group ) is doing fine with just a-z , 0-9 and hyphens .
Already more than half of the Internet users worldwide is using a non-Latin script for their native language .
And that 's the users that are going to benefit most .</tokentext>
<sentencetext>For example in China this will be used a lot.
Other countries using non-Latin scripts will do so as well.
Actually it was possible already for a few years to register domain names in Chinese characters in Hong Kong, but still ending in .hk.
Now that part can also become Chinese characters as replacement for .hk, .cn or .tw.
The catch was that a Chinese URL would work only within HK/China.
Now this will also start to work worldwide.
One big issue for many lower-educated Chinese is that the Latin script is as strange as Chinese characters to us.
Of course you can look at the shape and recognise them, but that's it: the letters do not carry sounds to them.
So it's impossible to remember an URL for those people.
Even for Chinese that can read/understand the Latin script it is far harder to remember an URL that they see in say an advertisement, than if that URL were in Chinese.
I bet the same accounts for many other languages.
Japanese, Indian languages, Vietnamese (Latin letters with lots and lots of accents to make it pronounceable for them), Korean, Russian.
Even many West-European languages French would be happy with adding just the accents.
This is a major leap forward for the Internet at large, don't underestimate it just because your language (group) is doing fine with just a-z, 0-9 and hyphens.
Already more than half of the Internet users worldwide is using a non-Latin script for their native language.
And that's the users that are going to benefit most.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923631</id>
	<title>how to...</title>
	<author>Anonymous</author>
	<datestamp>1256917020000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext>...break the internet, again.</htmltext>
<tokenext>...break the internet , again .</tokentext>
<sentencetext>...break the internet, again.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928357</id>
	<title>Re:Hmm...</title>
	<author>Valdrax</author>
	<datestamp>1256894400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Despite how metal that sounds, it's not where you'll find Chrome.</p></htmltext>
<tokenext>Despite how metal that sounds , it 's not where you 'll find Chrome .</tokentext>
<sentencetext>Despite how metal that sounds, it's not where you'll find Chrome.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923639</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927497</id>
	<title>Re:Latin =/= Support for English only.</title>
	<author>Estanislao Martínez</author>
	<datestamp>1256933580000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>Also, the unavailability of non-Latin scripts hasn't hampered the flourishing of home-grown websites in India and China named in their many local languages - what makes the ICANN think this is even necessary?</p></div></blockquote><p>And how exactly do you claim to know this?  It certainly makes it difficult to market the website among the potential user base who have only a shaky command of the Latin alphabet.</p></div>
	</htmltext>
<tokenext>Also , the unavailability of non-Latin scripts has n't hampered the flourishing of home-grown websites in India and China named in their many local languages - what makes the ICANN think this is even necessary ? And how exactly do you claim to know this ?
It certainly makes it difficult to market the website among the potential user base who have only a shaky command of the Latin alphabet .</tokentext>
<sentencetext>Also, the unavailability of non-Latin scripts hasn't hampered the flourishing of home-grown websites in India and China named in their many local languages - what makes the ICANN think this is even necessary?And how exactly do you claim to know this?
It certainly makes it difficult to market the website among the potential user base who have only a shaky command of the Latin alphabet.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924457</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923713</id>
	<title>Speeding the path to IPv6?</title>
	<author>Anonymous</author>
	<datestamp>1256917320000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext>I wonder what impact this will have on the ever decreasing amount of IPv4 addresses available. If it means that this pushes us towards a greater uptake of IPv6, it can only be good. For too long ISPs have been reluctant to encourage the rollout  of IPv6 connectivity, all the time turning a blind eye to this problem of diminishing IPv4 addresses. Perhaps with a rush for new domains there will be a significant drop in the number of free IPv4 addresses and this will spur the uptake of IPv6.</htmltext>
<tokenext>I wonder what impact this will have on the ever decreasing amount of IPv4 addresses available .
If it means that this pushes us towards a greater uptake of IPv6 , it can only be good .
For too long ISPs have been reluctant to encourage the rollout of IPv6 connectivity , all the time turning a blind eye to this problem of diminishing IPv4 addresses .
Perhaps with a rush for new domains there will be a significant drop in the number of free IPv4 addresses and this will spur the uptake of IPv6 .</tokentext>
<sentencetext>I wonder what impact this will have on the ever decreasing amount of IPv4 addresses available.
If it means that this pushes us towards a greater uptake of IPv6, it can only be good.
For too long ISPs have been reluctant to encourage the rollout  of IPv6 connectivity, all the time turning a blind eye to this problem of diminishing IPv4 addresses.
Perhaps with a rush for new domains there will be a significant drop in the number of free IPv4 addresses and this will spur the uptake of IPv6.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927177</id>
	<title>dhermann</title>
	<author>Anonymous</author>
	<datestamp>1256932020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You know, dhermann makes a really good point. I think we should hold off on any further changes to the internet or the web, so that he can continue shirking his duties at work. Why should he be inconvenienced, just so that all these barbarians with their crazy moon languages can have domain names that make sense to them? The audacity of these people!</p><p>What a dumb asshole comment to make. Grr.</p></htmltext>
<tokenext>You know , dhermann makes a really good point .
I think we should hold off on any further changes to the internet or the web , so that he can continue shirking his duties at work .
Why should he be inconvenienced , just so that all these barbarians with their crazy moon languages can have domain names that make sense to them ?
The audacity of these people ! What a dumb asshole comment to make .
Grr .</tokentext>
<sentencetext>You know, dhermann makes a really good point.
I think we should hold off on any further changes to the internet or the web, so that he can continue shirking his duties at work.
Why should he be inconvenienced, just so that all these barbarians with their crazy moon languages can have domain names that make sense to them?
The audacity of these people!What a dumb asshole comment to make.
Grr.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924501</id>
	<title>Squatting</title>
	<author>Anonymous</author>
	<datestamp>1256920500000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Regardless of implementation, once/if this does go through, my biggest question is what (if anything) is being done about domain squatting? We are talking about opening up potentially millions of domain names that have never been registered and I assume the moment this begins to be possible there would be some mad dash to register everything imaginable...</p></htmltext>
<tokenext>Regardless of implementation , once/if this does go through , my biggest question is what ( if anything ) is being done about domain squatting ?
We are talking about opening up potentially millions of domain names that have never been registered and I assume the moment this begins to be possible there would be some mad dash to register everything imaginable.. .</tokentext>
<sentencetext>Regardless of implementation, once/if this does go through, my biggest question is what (if anything) is being done about domain squatting?
We are talking about opening up potentially millions of domain names that have never been registered and I assume the moment this begins to be possible there would be some mad dash to register everything imaginable...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</id>
	<title>ICANN has lost it!</title>
	<author>Anonymous</author>
	<datestamp>1256917440000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Far too much software makes the assumption that TLDs only contain [a-z0-9-], so if you want to go changing that there needs to be a damn good reason, there is not. There are ~1369 2 letter TLDS to be shared between ~200 soverin states and 49284 3 letter generic ones to be split between uses (.xxx<nobr> <wbr></nobr>.nws<nobr> <wbr></nobr>.org<nobr> <wbr></nobr>.edu, etc), there doesn't seam to be any good reason to expand that and make lots of software more complex.</p></htmltext>
<tokenext>Far too much software makes the assumption that TLDs only contain [ a-z0-9- ] , so if you want to go changing that there needs to be a damn good reason , there is not .
There are ~ 1369 2 letter TLDS to be shared between ~ 200 soverin states and 49284 3 letter generic ones to be split between uses ( .xxx .nws .org .edu , etc ) , there does n't seam to be any good reason to expand that and make lots of software more complex .</tokentext>
<sentencetext>Far too much software makes the assumption that TLDs only contain [a-z0-9-], so if you want to go changing that there needs to be a damn good reason, there is not.
There are ~1369 2 letter TLDS to be shared between ~200 soverin states and 49284 3 letter generic ones to be split between uses (.xxx .nws .org .edu, etc), there doesn't seam to be any good reason to expand that and make lots of software more complex.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924583</id>
	<title>Re:Here comes the Phishers!</title>
	<author>pablo.cl</author>
	<datestamp>1256920860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>slashd&#246;t is not a ccTLD, and currently is allowed. Click here in Firefox or Opera: <a href="http://xn--slashdt-f1a.de/" title="xn--slashdt-f1a.de" rel="nofollow">http://xn--slashdt-f1a.de/</a> [xn--slashdt-f1a.de]</p></htmltext>
<tokenext>slashd   t is not a ccTLD , and currently is allowed .
Click here in Firefox or Opera : http : //xn--slashdt-f1a.de/ [ xn--slashdt-f1a.de ]</tokentext>
<sentencetext>slashdöt is not a ccTLD, and currently is allowed.
Click here in Firefox or Opera: http://xn--slashdt-f1a.de/ [xn--slashdt-f1a.de]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923845</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923703</id>
	<title>first urls, then slashdot</title>
	<author>Anonymous</author>
	<datestamp>1256917320000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>&#239; h&#246;p&#233; th&#227;t sl&#226;sh&#240;&#245;t w&#236;ll d&#246; th&#237;s t&#246;&#248; w&#236;th &#220;RLs!</p><p>www.&#237;&#231;&#225;&#241;n.&#246;rg</p><p>&#236;t w&#246;rk&#233;&#240;!</p></htmltext>
<tokenext>  h   p   th   t sl   sh     t w   ll d   th   s t     w   th   RLs ! www.         n.   rg   t w   rk     !</tokentext>
<sentencetext>ï höpé thãt slâshðõt wìll dö thís töø wìth ÜRLs!www.íçáñn.örgìt wörkéð!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924145</id>
	<title>Re:ICANN has lost it!</title>
	<author>cdrudge</author>
	<datestamp>1256919180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Far too much software makes the assumption that TLDs only contain [a-z0-9-]</p></div></blockquote><p>It's not really an assumption is it if until now the "standard" only called for [a-z0-9-].</p></div>
	</htmltext>
<tokenext>Far too much software makes the assumption that TLDs only contain [ a-z0-9- ] It 's not really an assumption is it if until now the " standard " only called for [ a-z0-9- ] .</tokentext>
<sentencetext>Far too much software makes the assumption that TLDs only contain [a-z0-9-]It's not really an assumption is it if until now the "standard" only called for [a-z0-9-].
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924573</id>
	<title>Re:ICANN has lost it!</title>
	<author>Anonymous</author>
	<datestamp>1256920800000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>We are not stopping them from building their own separate networks if they don't like the one that is already in place. But the US built the groundwork for the first computer network that evolved into the internet. Why would you be surprised that something that was invented in the US would be in English? And why do you expect the people that the system is working for to fix it for the people who don't like it? I would figure that it is up to the people who don't like it to fix it.</htmltext>
<tokenext>We are not stopping them from building their own separate networks if they do n't like the one that is already in place .
But the US built the groundwork for the first computer network that evolved into the internet .
Why would you be surprised that something that was invented in the US would be in English ?
And why do you expect the people that the system is working for to fix it for the people who do n't like it ?
I would figure that it is up to the people who do n't like it to fix it .</tokentext>
<sentencetext>We are not stopping them from building their own separate networks if they don't like the one that is already in place.
But the US built the groundwork for the first computer network that evolved into the internet.
Why would you be surprised that something that was invented in the US would be in English?
And why do you expect the people that the system is working for to fix it for the people who don't like it?
I would figure that it is up to the people who don't like it to fix it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924021</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29932565</id>
	<title>Re:</title>
	<author>clint999</author>
	<datestamp>1256931000000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><strong>I can't speak for Windows or Linux, but on a Mac:how do you compose this cedille on your qwerty keyboard?</strong></htmltext>
<tokenext>I ca n't speak for Windows or Linux , but on a Mac : how do you compose this cedille on your qwerty keyboard ?</tokentext>
<sentencetext>I can't speak for Windows or Linux, but on a Mac:how do you compose this cedille on your qwerty keyboard?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923955</id>
	<title>Re:Encoding?</title>
	<author>bradley13</author>
	<datestamp>1256918340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>The goal is to encode international characters as the characters currently accepted by the standard (a-z, 0-9, etc.) UTF does not do this. Also, the number of characters you can have in a domain name is limited to 26 (and it is the encoded length that counts), so the coding has to be efficient. This is precisely what <a href="http://en.wikipedia.org/wiki/Punycode" title="wikipedia.org">Punycode</a> [wikipedia.org] is designed to do. Software can recognize an encoded name by the fact that it begins with the special sequence of letters "xn--"</htmltext>
<tokenext>The goal is to encode international characters as the characters currently accepted by the standard ( a-z , 0-9 , etc .
) UTF does not do this .
Also , the number of characters you can have in a domain name is limited to 26 ( and it is the encoded length that counts ) , so the coding has to be efficient .
This is precisely what Punycode [ wikipedia.org ] is designed to do .
Software can recognize an encoded name by the fact that it begins with the special sequence of letters " xn-- "</tokentext>
<sentencetext>The goal is to encode international characters as the characters currently accepted by the standard (a-z, 0-9, etc.
) UTF does not do this.
Also, the number of characters you can have in a domain name is limited to 26 (and it is the encoded length that counts), so the coding has to be efficient.
This is precisely what Punycode [wikipedia.org] is designed to do.
Software can recognize an encoded name by the fact that it begins with the special sequence of letters "xn--"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923617</id>
	<title>terrorist level domain</title>
	<author>czarangelus</author>
	<datestamp>1256916960000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext>Arabic TLDs are a threat to national security</htmltext>
<tokenext>Arabic TLDs are a threat to national security</tokentext>
<sentencetext>Arabic TLDs are a threat to national security</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927323</id>
	<title>Re:Latin =/= Support for English only.</title>
	<author>minion</author>
	<datestamp>1256932740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Its not necessary, its purely political. The world hates the US, and what better way to tell the world that the US "does not run the internet" by making non-latin character sets valid.</htmltext>
<tokenext>Its not necessary , its purely political .
The world hates the US , and what better way to tell the world that the US " does not run the internet " by making non-latin character sets valid .</tokentext>
<sentencetext>Its not necessary, its purely political.
The world hates the US, and what better way to tell the world that the US "does not run the internet" by making non-latin character sets valid.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924457</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923945</id>
	<title>Re:Encoding?</title>
	<author>jeffasselin</author>
	<datestamp>1256918340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Good question. The field size for DNS requests is in double words (16bits) increments, so I don't see why it couldn't have been.</p></htmltext>
<tokenext>Good question .
The field size for DNS requests is in double words ( 16bits ) increments , so I do n't see why it could n't have been .</tokentext>
<sentencetext>Good question.
The field size for DNS requests is in double words (16bits) increments, so I don't see why it couldn't have been.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924523</id>
	<title>Re:Encoding?</title>
	<author>Creepy</author>
	<datestamp>1256920560000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Actually, UTF-8 can and is being used in DNS - as long as you stick to basic Latin characters, that is.  Also it is Unicode - as I posted earlier, Unicode is a blanket for UTF-8, UTF-16 and UTF-32 which makes it ambiguous.</p><p>UTF-8 bits 0-7 is ASCII as long as bit 8 isn't set, so to fully support it you'd need to still exclude bits below 7 that are not valid html characters and include support for multiple bytes and bit 8.  The reason existing DNS servers won't work with it is because bit 8 indicates multibyte and the second byte may carry an invalid character from the 0-7 bits and the first byte may have a language encoding for the second byte (indicated by bit 8).  For instance character 43 is + and that is invalid in a URL.  If character 1 had bit 8 set and indicated the language as French in the language encoding (which I believe is done in the first 7 bits and can in some cases be extended to the second or even third byte, but its been a while since I read the spec - I do know there is an encoding that does this and I'm pretty sure it is UTF-8), the second byte 43 would (probably - I'm not going to look it up) mean something entirely different and be perfectly valid.</p></htmltext>
<tokenext>Actually , UTF-8 can and is being used in DNS - as long as you stick to basic Latin characters , that is .
Also it is Unicode - as I posted earlier , Unicode is a blanket for UTF-8 , UTF-16 and UTF-32 which makes it ambiguous.UTF-8 bits 0-7 is ASCII as long as bit 8 is n't set , so to fully support it you 'd need to still exclude bits below 7 that are not valid html characters and include support for multiple bytes and bit 8 .
The reason existing DNS servers wo n't work with it is because bit 8 indicates multibyte and the second byte may carry an invalid character from the 0-7 bits and the first byte may have a language encoding for the second byte ( indicated by bit 8 ) .
For instance character 43 is + and that is invalid in a URL .
If character 1 had bit 8 set and indicated the language as French in the language encoding ( which I believe is done in the first 7 bits and can in some cases be extended to the second or even third byte , but its been a while since I read the spec - I do know there is an encoding that does this and I 'm pretty sure it is UTF-8 ) , the second byte 43 would ( probably - I 'm not going to look it up ) mean something entirely different and be perfectly valid .</tokentext>
<sentencetext>Actually, UTF-8 can and is being used in DNS - as long as you stick to basic Latin characters, that is.
Also it is Unicode - as I posted earlier, Unicode is a blanket for UTF-8, UTF-16 and UTF-32 which makes it ambiguous.UTF-8 bits 0-7 is ASCII as long as bit 8 isn't set, so to fully support it you'd need to still exclude bits below 7 that are not valid html characters and include support for multiple bytes and bit 8.
The reason existing DNS servers won't work with it is because bit 8 indicates multibyte and the second byte may carry an invalid character from the 0-7 bits and the first byte may have a language encoding for the second byte (indicated by bit 8).
For instance character 43 is + and that is invalid in a URL.
If character 1 had bit 8 set and indicated the language as French in the language encoding (which I believe is done in the first 7 bits and can in some cases be extended to the second or even third byte, but its been a while since I read the spec - I do know there is an encoding that does this and I'm pretty sure it is UTF-8), the second byte 43 would (probably - I'm not going to look it up) mean something entirely different and be perfectly valid.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923939</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925131</id>
	<title>How far will they allow this....</title>
	<author>PinkyDead</author>
	<datestamp>1256922960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>One word: Klingon.</p></htmltext>
<tokenext>One word : Klingon .</tokentext>
<sentencetext>One word: Klingon.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924815</id>
	<title>Re:how to...</title>
	<author>andreyvul</author>
	<datestamp>1256921880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>apart from typing google into google?</p></htmltext>
<tokenext>apart from typing google into google ?</tokentext>
<sentencetext>apart from typing google into google?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923631</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923891</id>
	<title>Re:Encoding?</title>
	<author>tokul</author>
	<datestamp>1256918160000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>Any DNS gurus care to explain why they wouldn't simply use UTF8?</p></div>
</blockquote><p>
I am not DNS guru, but guessing. RFC882 - November 1983. RFC2044 - October 1996.</p></div>
	</htmltext>
<tokenext>Any DNS gurus care to explain why they would n't simply use UTF8 ?
I am not DNS guru , but guessing .
RFC882 - November 1983 .
RFC2044 - October 1996 .</tokentext>
<sentencetext>Any DNS gurus care to explain why they wouldn't simply use UTF8?
I am not DNS guru, but guessing.
RFC882 - November 1983.
RFC2044 - October 1996.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930261</id>
	<title>Re:Hmm...</title>
	<author>gnud</author>
	<datestamp>1256905980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>A Micr&#246;s&#246;ft product once BSODd my sisters computer.</htmltext>
<tokenext>A Micr   s   ft product once BSODd my sisters computer .</tokentext>
<sentencetext>A Micrösöft product once BSODd my sisters computer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923639</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927165</id>
	<title>Re:so chase.com</title>
	<author>pablo.cl</author>
	<datestamp>1256931960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>could be ch&#224;se.com or ch&#225;se.com</p><p>every website i go to from now on, i need to study the url with a magnifying glass to make sure i am getting the actual site i wanted.</p></div><p>The new characteristic is that ccTLDs are allowed. Second level domains have been available for several years. For example <a href="http://www.xn--and-6ma2c.cl/" title="xn--and-6ma2c.cl" rel="nofollow">http://www.xn--and-6ma2c.cl/</a> [xn--and-6ma2c.cl] &#241;and&#250;<nobr> <wbr></nobr>.cl</p></div>
	</htmltext>
<tokenext>could be ch   se.com or ch   se.comevery website i go to from now on , i need to study the url with a magnifying glass to make sure i am getting the actual site i wanted.The new characteristic is that ccTLDs are allowed .
Second level domains have been available for several years .
For example http : //www.xn--and-6ma2c.cl/ [ xn--and-6ma2c.cl ]   and   .cl</tokentext>
<sentencetext>could be chàse.com or cháse.comevery website i go to from now on, i need to study the url with a magnifying glass to make sure i am getting the actual site i wanted.The new characteristic is that ccTLDs are allowed.
Second level domains have been available for several years.
For example http://www.xn--and-6ma2c.cl/ [xn--and-6ma2c.cl] ñandú .cl
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924961</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924385</id>
	<title>IDNs are dangerous.</title>
	<author>harry666t</author>
	<datestamp>1256920140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>See these slides about exploiting UTF-aware software.</p><p><a href="http://www.casabasecurity.com/files/Chris\_Weber\_Character\%20Transformations\%20v1.7\_IUC33.pdf" title="casabasecurity.com">http://www.casabasecurity.com/files/Chris\_Weber\_Character\%20Transformations\%20v1.7\_IUC33.pdf</a> [casabasecurity.com]</p></htmltext>
<tokenext>See these slides about exploiting UTF-aware software.http : //www.casabasecurity.com/files/Chris \ _Weber \ _Character \ % 20Transformations \ % 20v1.7 \ _IUC33.pdf [ casabasecurity.com ]</tokentext>
<sentencetext>See these slides about exploiting UTF-aware software.http://www.casabasecurity.com/files/Chris\_Weber\_Character\%20Transformations\%20v1.7\_IUC33.pdf [casabasecurity.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29932297</id>
	<title>Homonyms?</title>
	<author>Anonymous</author>
	<datestamp>1256925960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The landgrab is going to be a mess, especially in places like China.   Here domains use romanization to represent domain names, but each pinyin (romanized) syllable maps to sometimes hundreds of different chinese characters... definitely will be a lot of jostling.</p><p>LS</p></htmltext>
<tokenext>The landgrab is going to be a mess , especially in places like China .
Here domains use romanization to represent domain names , but each pinyin ( romanized ) syllable maps to sometimes hundreds of different chinese characters... definitely will be a lot of jostling.LS</tokentext>
<sentencetext>The landgrab is going to be a mess, especially in places like China.
Here domains use romanization to represent domain names, but each pinyin (romanized) syllable maps to sometimes hundreds of different chinese characters... definitely will be a lot of jostling.LS</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923859</id>
	<title>Re:Encoding?</title>
	<author>DamonHD</author>
	<datestamp>1256917980000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>To avoid breaking all the DNS-related code out there that assumes (ie correctly, based on the current spec) only alphanumerics and '-' in each component.</p><p>If you wish to rewrite every single bit of DNS-dependent code, in every laptop, server, embedded network device, etc, etc,<nobr> <wbr></nobr>... well assume that it can't be done, and with this mechanism it doesn't need to be.  Though I bet a few bits of code will barf at the '--' anyhow...</p><p>Rgds</p><p>Damon</p></htmltext>
<tokenext>To avoid breaking all the DNS-related code out there that assumes ( ie correctly , based on the current spec ) only alphanumerics and '- ' in each component.If you wish to rewrite every single bit of DNS-dependent code , in every laptop , server , embedded network device , etc , etc , ... well assume that it ca n't be done , and with this mechanism it does n't need to be .
Though I bet a few bits of code will barf at the '-- ' anyhow...RgdsDamon</tokentext>
<sentencetext>To avoid breaking all the DNS-related code out there that assumes (ie correctly, based on the current spec) only alphanumerics and '-' in each component.If you wish to rewrite every single bit of DNS-dependent code, in every laptop, server, embedded network device, etc, etc, ... well assume that it can't be done, and with this mechanism it doesn't need to be.
Though I bet a few bits of code will barf at the '--' anyhow...RgdsDamon</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29929049</id>
	<title>.com/.net/.org should be off-limits to Unicode</title>
	<author>Miamicanes</author>
	<datestamp>1256897940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>IMHO, the worst decision ever made in the history of the internet was ICANN's decision to allow non-ASCII subdomains of<nobr> <wbr></nobr>.com,<nobr> <wbr></nobr>.net, and<nobr> <wbr></nobr>.org. Those three gTLDs, if not others as well, should be forever off-limits to any characters besides the original 26 letters a..z, the digits 0..9, and hyphen.</p><p>For other TLDs, and for national TLDs, DNS should be extended to allow a TLD's authoritative top-level registrar to authoritatively indicate which UTF8 characters (or range(s) of characters) beyond those historically-allowed for ASCII DNS are valid for its subdomains. The registrar for Spain might decide it needs accented vowels and tilde+n, but has no reason for Turkish vowels that conveniently (for phishers) look identical to ASCII characters.</p><p>The next step would have been the creation of a few brand new TLDs, like ".Zhong" (U4E2D) and ".Nihongo" (U65E5 + U672C) -- think ".(Chinese)" and ".(Japanese)", not to mention similar TLDs for Hindi, Korean, Russian, and other languages that use non-Roman alphabets.</p><p>The point is, ICANN could have done a much, much better job with this whole mess. I think everyone can agree that international domain names are something that needs to exist, but trying to staple them onto<nobr> <wbr></nobr>.com/.net/.org was an incredibly bad idea.</p></htmltext>
<tokenext>IMHO , the worst decision ever made in the history of the internet was ICANN 's decision to allow non-ASCII subdomains of .com , .net , and .org .
Those three gTLDs , if not others as well , should be forever off-limits to any characters besides the original 26 letters a..z , the digits 0..9 , and hyphen.For other TLDs , and for national TLDs , DNS should be extended to allow a TLD 's authoritative top-level registrar to authoritatively indicate which UTF8 characters ( or range ( s ) of characters ) beyond those historically-allowed for ASCII DNS are valid for its subdomains .
The registrar for Spain might decide it needs accented vowels and tilde + n , but has no reason for Turkish vowels that conveniently ( for phishers ) look identical to ASCII characters.The next step would have been the creation of a few brand new TLDs , like " .Zhong " ( U4E2D ) and " .Nihongo " ( U65E5 + U672C ) -- think " .
( Chinese ) " and " .
( Japanese ) " , not to mention similar TLDs for Hindi , Korean , Russian , and other languages that use non-Roman alphabets.The point is , ICANN could have done a much , much better job with this whole mess .
I think everyone can agree that international domain names are something that needs to exist , but trying to staple them onto .com/.net/.org was an incredibly bad idea .</tokentext>
<sentencetext>IMHO, the worst decision ever made in the history of the internet was ICANN's decision to allow non-ASCII subdomains of .com, .net, and .org.
Those three gTLDs, if not others as well, should be forever off-limits to any characters besides the original 26 letters a..z, the digits 0..9, and hyphen.For other TLDs, and for national TLDs, DNS should be extended to allow a TLD's authoritative top-level registrar to authoritatively indicate which UTF8 characters (or range(s) of characters) beyond those historically-allowed for ASCII DNS are valid for its subdomains.
The registrar for Spain might decide it needs accented vowels and tilde+n, but has no reason for Turkish vowels that conveniently (for phishers) look identical to ASCII characters.The next step would have been the creation of a few brand new TLDs, like ".Zhong" (U4E2D) and ".Nihongo" (U65E5 + U672C) -- think ".
(Chinese)" and ".
(Japanese)", not to mention similar TLDs for Hindi, Korean, Russian, and other languages that use non-Roman alphabets.The point is, ICANN could have done a much, much better job with this whole mess.
I think everyone can agree that international domain names are something that needs to exist, but trying to staple them onto .com/.net/.org was an incredibly bad idea.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923639</id>
	<title>Hmm...</title>
	<author>Anonymous</author>
	<datestamp>1256917080000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>micr&#246;s&#246;ft.c&#246;m?</p></htmltext>
<tokenext>micr   s   ft.c   m ?</tokentext>
<sentencetext>micrösöft.cöm?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924991</id>
	<title>Re:Excellent idea</title>
	<author>Hythlodaeus</author>
	<datestamp>1256922420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>They make sense as aliases to sites that also have standard domain names.</p></htmltext>
<tokenext>They make sense as aliases to sites that also have standard domain names .</tokentext>
<sentencetext>They make sense as aliases to sites that also have standard domain names.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923967</id>
	<title>Re:ICANN has lost it!</title>
	<author>Anonymous</author>
	<datestamp>1256918340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Domain names have been muddy for quite some time. Think of all the non commercial dot coms. Or government sites on anything other than their<nobr> <wbr></nobr>.gov or their country code. del. del.icio.us? They've been mostly ignored. People get<nobr> <wbr></nobr>.com to look professional,<nobr> <wbr></nobr>.net at random (though it is supposed to be for ISPs), and<nobr> <wbr></nobr>.org if you want to stand for some ideal. <br> <br>Though TBH I'm not certain WHY we need TLDs anyways. It isn't like there is some commercial slashdot.com it just redirects. I imagine that any big name will own all of the tlds with its name. Google is the only company that differentiates but it does it completely wrong. It shouldn't be google.com and google.org<nobr> <wbr></nobr>... it could just be www.google vs org.google. I guess it is something that lets companies sell the same product to people multiple times.</htmltext>
<tokenext>Domain names have been muddy for quite some time .
Think of all the non commercial dot coms .
Or government sites on anything other than their .gov or their country code .
del. del.icio.us ?
They 've been mostly ignored .
People get .com to look professional , .net at random ( though it is supposed to be for ISPs ) , and .org if you want to stand for some ideal .
Though TBH I 'm not certain WHY we need TLDs anyways .
It is n't like there is some commercial slashdot.com it just redirects .
I imagine that any big name will own all of the tlds with its name .
Google is the only company that differentiates but it does it completely wrong .
It should n't be google.com and google.org ... it could just be www.google vs org.google .
I guess it is something that lets companies sell the same product to people multiple times .</tokentext>
<sentencetext>Domain names have been muddy for quite some time.
Think of all the non commercial dot coms.
Or government sites on anything other than their .gov or their country code.
del. del.icio.us?
They've been mostly ignored.
People get .com to look professional, .net at random (though it is supposed to be for ISPs), and .org if you want to stand for some ideal.
Though TBH I'm not certain WHY we need TLDs anyways.
It isn't like there is some commercial slashdot.com it just redirects.
I imagine that any big name will own all of the tlds with its name.
Google is the only company that differentiates but it does it completely wrong.
It shouldn't be google.com and google.org ... it could just be www.google vs org.google.
I guess it is something that lets companies sell the same product to people multiple times.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925837</id>
	<title>right</title>
	<author>Anonymous</author>
	<datestamp>1256926020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>'Cause as a website visitor, I *really* want to learn all those other languages and switch my keyboard every other website I go to. *REALLY!* I've wanted to for *years*!!</p><p>And as a website owner, I want to pay to register 248+ domain names just to cover all the new TDL languages.. instead of having <a href="http://www.mywebsite.com/jp/index.php" title="mywebsite.com" rel="nofollow">http://www.mywebsite.com/jp/index.php</a> [mywebsite.com], et al.</p><p>Smells like teen scam to me. I really had to laugh when they showed the South Korean Pensioners learning how to use the internet. And complaining about having to learn english.</p></htmltext>
<tokenext>'Cause as a website visitor , I * really * want to learn all those other languages and switch my keyboard every other website I go to .
* REALLY ! * I 've wanted to for * years * !
! And as a website owner , I want to pay to register 248 + domain names just to cover all the new TDL languages.. instead of having http : //www.mywebsite.com/jp/index.php [ mywebsite.com ] , et al.Smells like teen scam to me .
I really had to laugh when they showed the South Korean Pensioners learning how to use the internet .
And complaining about having to learn english .</tokentext>
<sentencetext>'Cause as a website visitor, I *really* want to learn all those other languages and switch my keyboard every other website I go to.
*REALLY!* I've wanted to for *years*!
!And as a website owner, I want to pay to register 248+ domain names just to cover all the new TDL languages.. instead of having http://www.mywebsite.com/jp/index.php [mywebsite.com], et al.Smells like teen scam to me.
I really had to laugh when they showed the South Korean Pensioners learning how to use the internet.
And complaining about having to learn english.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923989</id>
	<title>Not trying to be harsh but...</title>
	<author>Anonymous</author>
	<datestamp>1256918520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>cmon how could you think "but in future countries" sounds okay.</p><p>it should be "but in the future countries"</p><p>great info though. I mean its nice to see that the internet is starting to become more international, especially as the US cuts mandatory ties to ICANN.</p></htmltext>
<tokenext>cmon how could you think " but in future countries " sounds okay.it should be " but in the future countries " great info though .
I mean its nice to see that the internet is starting to become more international , especially as the US cuts mandatory ties to ICANN .</tokentext>
<sentencetext>cmon how could you think "but in future countries" sounds okay.it should be "but in the future countries"great info though.
I mean its nice to see that the internet is starting to become more international, especially as the US cuts mandatory ties to ICANN.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925813</id>
	<title>Re:Latin =/= Support for English only.</title>
	<author>w000t</author>
	<datestamp>1256925900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>English uses a simple form of Latin. Other languages using the Latin alphabet, such as Spanish, French or Portuguese, German, etc. contain symbols not available in the English version. It is generally not a problem though, as most used symbols are available and missing ones can generally be replaced by similar ones.</htmltext>
<tokenext>English uses a simple form of Latin .
Other languages using the Latin alphabet , such as Spanish , French or Portuguese , German , etc .
contain symbols not available in the English version .
It is generally not a problem though , as most used symbols are available and missing ones can generally be replaced by similar ones .</tokentext>
<sentencetext>English uses a simple form of Latin.
Other languages using the Latin alphabet, such as Spanish, French or Portuguese, German, etc.
contain symbols not available in the English version.
It is generally not a problem though, as most used symbols are available and missing ones can generally be replaced by similar ones.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924457</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924657</id>
	<title>Re:ICANN has lost it!</title>
	<author>defaria</author>
	<datestamp>1256921160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Huh? Wouldn't software be simplified by <b>not</b> applying any regex to the TLD?!? IOW why not simply assume it can be anything (short of a null byte).</htmltext>
<tokenext>Huh ?
Would n't software be simplified by not applying any regex to the TLD ? ! ?
IOW why not simply assume it can be anything ( short of a null byte ) .</tokentext>
<sentencetext>Huh?
Wouldn't software be simplified by not applying any regex to the TLD?!?
IOW why not simply assume it can be anything (short of a null byte).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926615</id>
	<title>Please...</title>
	<author>shentino</author>
	<datestamp>1256929560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>At least restrict the character set to UTF-8</p></htmltext>
<tokenext>At least restrict the character set to UTF-8</tokentext>
<sentencetext>At least restrict the character set to UTF-8</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924011</id>
	<title>Raise your hand if you're surprised...</title>
	<author>Anonymous</author>
	<datestamp>1256918580000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>1</modscore>
	<htmltext>... Yeah, I didn't think so.<br> <br>
ICANN just made another move to make everyday life on the internet slightly more difficult for many users, while making life for con artists, spammers, phishers, etc, much much easier (and more profitable).  It is safe to expect that someone (probably more than one actually) at ICANN made some money on the deal.<br> <br>
Hell it wouldn't surprise me if they were working with some financiers to try to find a way to sell internet subprime mortgages for profit as well.</htmltext>
<tokenext>... Yeah , I did n't think so .
ICANN just made another move to make everyday life on the internet slightly more difficult for many users , while making life for con artists , spammers , phishers , etc , much much easier ( and more profitable ) .
It is safe to expect that someone ( probably more than one actually ) at ICANN made some money on the deal .
Hell it would n't surprise me if they were working with some financiers to try to find a way to sell internet subprime mortgages for profit as well .</tokentext>
<sentencetext>... Yeah, I didn't think so.
ICANN just made another move to make everyday life on the internet slightly more difficult for many users, while making life for con artists, spammers, phishers, etc, much much easier (and more profitable).
It is safe to expect that someone (probably more than one actually) at ICANN made some money on the deal.
Hell it wouldn't surprise me if they were working with some financiers to try to find a way to sell internet subprime mortgages for profit as well.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924633</id>
	<title>Re:Excellent idea</title>
	<author>pablo.cl</author>
	<datestamp>1256921040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Compare <a href="http://xn--slashdt-f1a.com/" title="xn--slashdt-f1a.com" rel="nofollow">http://xn--slashdt-f1a.com/</a> [xn--slashdt-f1a.com] and <a href="http://xn--slashdt-f1a.de/" title="xn--slashdt-f1a.de" rel="nofollow">http://xn--slashdt-f1a.de/</a> [xn--slashdt-f1a.de] In Firefox the first one shows punycode and the German one correctly appears as slashd&#246;t.de, because Germans are known to forbid scammers, and<nobr> <wbr></nobr>.com is notoriously the opposite.</p></htmltext>
<tokenext>Compare http : //xn--slashdt-f1a.com/ [ xn--slashdt-f1a.com ] and http : //xn--slashdt-f1a.de/ [ xn--slashdt-f1a.de ] In Firefox the first one shows punycode and the German one correctly appears as slashd   t.de , because Germans are known to forbid scammers , and .com is notoriously the opposite .</tokentext>
<sentencetext>Compare http://xn--slashdt-f1a.com/ [xn--slashdt-f1a.com] and http://xn--slashdt-f1a.de/ [xn--slashdt-f1a.de] In Firefox the first one shows punycode and the German one correctly appears as slashdöt.de, because Germans are known to forbid scammers, and .com is notoriously the opposite.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923845</id>
	<title>Here comes the Phishers!</title>
	<author>Anonymous</author>
	<datestamp>1256917980000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext>Yay!!!  The door is open for an even harder to detect phishing scheme!  Imagine the emails linking to <a href="http://slashd/" title="slashd">http://slashd/</a> [slashd]&#246;t.org/something...  <br> <br>
I'm all for internationalization, but perhaps limit it to internationalized domain extensions (.jp or<nobr> <wbr></nobr>.es for example)...</htmltext>
<tokenext>Yay ! ! !
The door is open for an even harder to detect phishing scheme !
Imagine the emails linking to http : //slashd/ [ slashd ]   t.org/something.. . I 'm all for internationalization , but perhaps limit it to internationalized domain extensions ( .jp or .es for example ) .. .</tokentext>
<sentencetext>Yay!!!
The door is open for an even harder to detect phishing scheme!
Imagine the emails linking to http://slashd/ [slashd]öt.org/something...   
I'm all for internationalization, but perhaps limit it to internationalized domain extensions (.jp or .es for example)...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927943</id>
	<title>Did anyone tell the IETF yet?</title>
	<author>help\_cecil\_help</author>
	<datestamp>1256935620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>
I used to look here (http://www.ietf.org/rfc/rfc1738.txt) for this kind of thing...</htmltext>
<tokenext>I used to look here ( http : //www.ietf.org/rfc/rfc1738.txt ) for this kind of thing.. .</tokentext>
<sentencetext>
I used to look here (http://www.ietf.org/rfc/rfc1738.txt) for this kind of thing...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928265</id>
	<title>Fragmentation.</title>
	<author>MaWeiTao</author>
	<datestamp>1256893860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Initially I thought this was cool. But then I started thinking about this and I realized that all this is going to do is fragment the internet. The existing system ensured a convenient standard that anyone could access. How the hell are non-Chinese, for example, every going to figure out how to type a Chinese address? Unless someone provides you with an address it's not likely you'll ever figure it out.</p><p>Even being able to speak Chinese this would be a challenge for me. I expect even Chinese natives are going to have a hard time with this. I could tell someone my web address, but then I also have to explain which character I mean because there could be there might be multiple characters for that particular phonetic. And lets not get into all the languages out there with their own unique writing systems.</p><p>The fact is that certain languages aren't quite as conducive to use with computers as others. In many cases it's probably just that nobody has made the effort to optimize input devices and system interfaces. But then when you do that you also alienate the rest of the world. It's entirely possible most foreigners wouldn't ever end up on these sites anyway but I don't like this fragmentation by what I see as dumping a standard. Technology will eventually reach a point when this is not an issue, but we're not there yet. I really don't see what was wrong with the Latin alphabet and Arabic numerals. Every computer in the world supports this by default so how exactly does this move enhance accessibility?</p></htmltext>
<tokenext>Initially I thought this was cool .
But then I started thinking about this and I realized that all this is going to do is fragment the internet .
The existing system ensured a convenient standard that anyone could access .
How the hell are non-Chinese , for example , every going to figure out how to type a Chinese address ?
Unless someone provides you with an address it 's not likely you 'll ever figure it out.Even being able to speak Chinese this would be a challenge for me .
I expect even Chinese natives are going to have a hard time with this .
I could tell someone my web address , but then I also have to explain which character I mean because there could be there might be multiple characters for that particular phonetic .
And lets not get into all the languages out there with their own unique writing systems.The fact is that certain languages are n't quite as conducive to use with computers as others .
In many cases it 's probably just that nobody has made the effort to optimize input devices and system interfaces .
But then when you do that you also alienate the rest of the world .
It 's entirely possible most foreigners would n't ever end up on these sites anyway but I do n't like this fragmentation by what I see as dumping a standard .
Technology will eventually reach a point when this is not an issue , but we 're not there yet .
I really do n't see what was wrong with the Latin alphabet and Arabic numerals .
Every computer in the world supports this by default so how exactly does this move enhance accessibility ?</tokentext>
<sentencetext>Initially I thought this was cool.
But then I started thinking about this and I realized that all this is going to do is fragment the internet.
The existing system ensured a convenient standard that anyone could access.
How the hell are non-Chinese, for example, every going to figure out how to type a Chinese address?
Unless someone provides you with an address it's not likely you'll ever figure it out.Even being able to speak Chinese this would be a challenge for me.
I expect even Chinese natives are going to have a hard time with this.
I could tell someone my web address, but then I also have to explain which character I mean because there could be there might be multiple characters for that particular phonetic.
And lets not get into all the languages out there with their own unique writing systems.The fact is that certain languages aren't quite as conducive to use with computers as others.
In many cases it's probably just that nobody has made the effort to optimize input devices and system interfaces.
But then when you do that you also alienate the rest of the world.
It's entirely possible most foreigners wouldn't ever end up on these sites anyway but I don't like this fragmentation by what I see as dumping a standard.
Technology will eventually reach a point when this is not an issue, but we're not there yet.
I really don't see what was wrong with the Latin alphabet and Arabic numerals.
Every computer in the world supports this by default so how exactly does this move enhance accessibility?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928273</id>
	<title>Re:Excellent idea</title>
	<author>raju1kabir</author>
	<datestamp>1256893920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Actually it was possible already for a few years to register domain names in Chinese characters in Hong Kong, but still ending in<nobr> <wbr></nobr>.hk. Now that part can also become Chinese characters as replacement for<nobr> <wbr></nobr>.hk,<nobr> <wbr></nobr>.cn or<nobr> <wbr></nobr>.tw.

The catch was that a Chinese URL would work only within HK/China. Now this will also start to work worldwide.</p></div> </blockquote><p>There has been nothing stopping you from visiting a Chinese-character<nobr> <wbr></nobr>.hk domain name for lo these many years, they've worked fine.
</p><p>What's changing is that now the<nobr> <wbr></nobr>.hk part itself can be in Chinese characters.</p></div>
	</htmltext>
<tokenext>Actually it was possible already for a few years to register domain names in Chinese characters in Hong Kong , but still ending in .hk .
Now that part can also become Chinese characters as replacement for .hk , .cn or .tw .
The catch was that a Chinese URL would work only within HK/China .
Now this will also start to work worldwide .
There has been nothing stopping you from visiting a Chinese-character .hk domain name for lo these many years , they 've worked fine .
What 's changing is that now the .hk part itself can be in Chinese characters .</tokentext>
<sentencetext>Actually it was possible already for a few years to register domain names in Chinese characters in Hong Kong, but still ending in .hk.
Now that part can also become Chinese characters as replacement for .hk, .cn or .tw.
The catch was that a Chinese URL would work only within HK/China.
Now this will also start to work worldwide.
There has been nothing stopping you from visiting a Chinese-character .hk domain name for lo these many years, they've worked fine.
What's changing is that now the .hk part itself can be in Chinese characters.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924917</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923731</id>
	<title>Toto, you are not in nss any more.</title>
	<author>Anonymous</author>
	<datestamp>1256917440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>nss or Kansas for that matter</htmltext>
<tokenext>nss or Kansas for that matter</tokentext>
<sentencetext>nss or Kansas for that matter</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745</id>
	<title>Encoding?</title>
	<author>Anonymous</author>
	<datestamp>1256917500000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>1</modscore>
	<htmltext><p>The encoding seems weird to me:</p><blockquote><div><p>In reality, the new domain names will be stored in the DNS as sequences of letters and numbers beginning xn-- in order to maintain compatibility with the existing infrastructure. The characters following the xn-- will be used to encode a sequence of Unicode characters representing the country name.</p></div></blockquote><p>Any DNS gurus care to explain why they wouldn't simply use UTF8?</p></div>
	</htmltext>
<tokenext>The encoding seems weird to me : In reality , the new domain names will be stored in the DNS as sequences of letters and numbers beginning xn-- in order to maintain compatibility with the existing infrastructure .
The characters following the xn-- will be used to encode a sequence of Unicode characters representing the country name.Any DNS gurus care to explain why they would n't simply use UTF8 ?</tokentext>
<sentencetext>The encoding seems weird to me:In reality, the new domain names will be stored in the DNS as sequences of letters and numbers beginning xn-- in order to maintain compatibility with the existing infrastructure.
The characters following the xn-- will be used to encode a sequence of Unicode characters representing the country name.Any DNS gurus care to explain why they wouldn't simply use UTF8?
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924539</id>
	<title>Re:Phishing aid</title>
	<author>petermgreen</author>
	<datestamp>1256920620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I don't think it's a big deal for TLDs since afaict those are created manually anyway.</p><p>For lower level domains (which are already using IDN) it's a bigger issue, firefox resorted to using a whitelist to get arround irresponsible registrars.</p></htmltext>
<tokenext>I do n't think it 's a big deal for TLDs since afaict those are created manually anyway.For lower level domains ( which are already using IDN ) it 's a bigger issue , firefox resorted to using a whitelist to get arround irresponsible registrars .</tokentext>
<sentencetext>I don't think it's a big deal for TLDs since afaict those are created manually anyway.For lower level domains (which are already using IDN) it's a bigger issue, firefox resorted to using a whitelist to get arround irresponsible registrars.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925869</id>
	<title>Re:The problem is switching keyboard input</title>
	<author>Locke2005</author>
	<datestamp>1256926200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><i>Even if you are fluent in both languages, it is a pain in the arse.</i> If typing is a pain in the arse for you... well then, you're obviously doing it wrong!<br> <br>
In general, I really don't see any benefit to non-latin URLs; most webpages are accessed through links, and most people type URLs into Google anyway to let it Google correct their typos for them. People can't type URLs correctly now; how are they going to type mixed character set URLs correctly?</htmltext>
<tokenext>Even if you are fluent in both languages , it is a pain in the arse .
If typing is a pain in the arse for you... well then , you 're obviously doing it wrong !
In general , I really do n't see any benefit to non-latin URLs ; most webpages are accessed through links , and most people type URLs into Google anyway to let it Google correct their typos for them .
People ca n't type URLs correctly now ; how are they going to type mixed character set URLs correctly ?</tokentext>
<sentencetext>Even if you are fluent in both languages, it is a pain in the arse.
If typing is a pain in the arse for you... well then, you're obviously doing it wrong!
In general, I really don't see any benefit to non-latin URLs; most webpages are accessed through links, and most people type URLs into Google anyway to let it Google correct their typos for them.
People can't type URLs correctly now; how are they going to type mixed character set URLs correctly?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924333</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927037</id>
	<title>Re:Um, can they be more specific than "Unicode"?</title>
	<author>spitzak</author>
	<datestamp>1256931420000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>Several mistakes there.</p><p>First of all any domain name is going to have to be encoded as a stream of bytes somehow because far too much stuff is already implemented to handle the string that way. As others pointed out punycode is used.</p><p>Second, UTF-8 is smaller than UTF-16 for all languages, even Chinese. This is because all the ASCII 0x00-0x7F characters are smaller, and therefore the encoding will be smaller if there are more of these than there Unicode 0x800-0xFFFF characters. This seems incorrect for Chinese but you have to realize that ASCII includes spaces, newlines, numbers, and all XML and HTML markup and therefore any reasonable sized Chinese document will be smaller in UTF-8.</p><p>Translating encodings to "wide characters" is a mistake, as you have noticed. You should write your software to deal with it in it's original encoding because that is the only way to intelligently deal with errors in the string. The fact that Windows uses UTF-16 for an encoding a lot seems to be confusing people no end, but please check exactly what they do when that UTF-16 has surrogate pairs, or even "invalid" surrogate halves. They are handling the original encoding, they are not "translating it to Unicode".</p></htmltext>
<tokenext>Several mistakes there.First of all any domain name is going to have to be encoded as a stream of bytes somehow because far too much stuff is already implemented to handle the string that way .
As others pointed out punycode is used.Second , UTF-8 is smaller than UTF-16 for all languages , even Chinese .
This is because all the ASCII 0x00-0x7F characters are smaller , and therefore the encoding will be smaller if there are more of these than there Unicode 0x800-0xFFFF characters .
This seems incorrect for Chinese but you have to realize that ASCII includes spaces , newlines , numbers , and all XML and HTML markup and therefore any reasonable sized Chinese document will be smaller in UTF-8.Translating encodings to " wide characters " is a mistake , as you have noticed .
You should write your software to deal with it in it 's original encoding because that is the only way to intelligently deal with errors in the string .
The fact that Windows uses UTF-16 for an encoding a lot seems to be confusing people no end , but please check exactly what they do when that UTF-16 has surrogate pairs , or even " invalid " surrogate halves .
They are handling the original encoding , they are not " translating it to Unicode " .</tokentext>
<sentencetext>Several mistakes there.First of all any domain name is going to have to be encoded as a stream of bytes somehow because far too much stuff is already implemented to handle the string that way.
As others pointed out punycode is used.Second, UTF-8 is smaller than UTF-16 for all languages, even Chinese.
This is because all the ASCII 0x00-0x7F characters are smaller, and therefore the encoding will be smaller if there are more of these than there Unicode 0x800-0xFFFF characters.
This seems incorrect for Chinese but you have to realize that ASCII includes spaces, newlines, numbers, and all XML and HTML markup and therefore any reasonable sized Chinese document will be smaller in UTF-8.Translating encodings to "wide characters" is a mistake, as you have noticed.
You should write your software to deal with it in it's original encoding because that is the only way to intelligently deal with errors in the string.
The fact that Windows uses UTF-16 for an encoding a lot seems to be confusing people no end, but please check exactly what they do when that UTF-16 has surrogate pairs, or even "invalid" surrogate halves.
They are handling the original encoding, they are not "translating it to Unicode".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924161</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29933175</id>
	<title>Re:Here comes the Phishers!</title>
	<author>mjwx</author>
	<datestamp>1256987460000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>You do know that this is for the TLD part of the URL only. The first part of a domain can already be written in non latin scripts, Korean for example but the TLD must but Latin, this decision just enables the<nobr> <wbr></nobr>.com.kr to be turned into Hangul.<br> <br>

If ICANN did not standardise this then nations will just implement their own systems which will be different and incompatible with each other, much like China and Thailand have already done.</htmltext>
<tokenext>You do know that this is for the TLD part of the URL only .
The first part of a domain can already be written in non latin scripts , Korean for example but the TLD must but Latin , this decision just enables the .com.kr to be turned into Hangul .
If ICANN did not standardise this then nations will just implement their own systems which will be different and incompatible with each other , much like China and Thailand have already done .</tokentext>
<sentencetext>You do know that this is for the TLD part of the URL only.
The first part of a domain can already be written in non latin scripts, Korean for example but the TLD must but Latin, this decision just enables the .com.kr to be turned into Hangul.
If ICANN did not standardise this then nations will just implement their own systems which will be different and incompatible with each other, much like China and Thailand have already done.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923845</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930561</id>
	<title>Dear slashdotters,</title>
	<author>Anonymous</author>
	<datestamp>1256907600000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>before posting any more comments to this story be sure you understand what these terms mean:<br>* TLD = <strong>top</strong> level domain<br>* punycode</p><p>&lt;grumble&gt;...used to be news for nerds...&lt;/grumble&gt;</p></htmltext>
<tokenext>before posting any more comments to this story be sure you understand what these terms mean : * TLD = top level domain * punycode...used to be news for nerds.. .</tokentext>
<sentencetext>before posting any more comments to this story be sure you understand what these terms mean:* TLD = top level domain* punycode...used to be news for nerds...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924117</id>
	<title>Re:Hmm...</title>
	<author>4D6963</author>
	<datestamp>1256919060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>No fortunately they're not going yet for a full unicode thing, only a few select character sets like Chinese or Arabic. So for the moment that shouldn't be a problem.</p></htmltext>
<tokenext>No fortunately they 're not going yet for a full unicode thing , only a few select character sets like Chinese or Arabic .
So for the moment that should n't be a problem .</tokentext>
<sentencetext>No fortunately they're not going yet for a full unicode thing, only a few select character sets like Chinese or Arabic.
So for the moment that shouldn't be a problem.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923639</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925643</id>
	<title>Need ability to block this</title>
	<author>Anonymous</author>
	<datestamp>1256925000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I look forward to browser plugins that block or auto translate these urls for the sake of security.</p></htmltext>
<tokenext>I look forward to browser plugins that block or auto translate these urls for the sake of security .</tokentext>
<sentencetext>I look forward to browser plugins that block or auto translate these urls for the sake of security.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29929309</id>
	<title>Re:Latin =/= Support for English only.</title>
	<author>Anonymous</author>
	<datestamp>1256899740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>English is one of the few language that uses only 26 letters. For example, Spanish, French and German all have special letters or accents such as : &#233;&#232;&#231;&#244;&#226;&#252;&#236;</p></htmltext>
<tokenext>English is one of the few language that uses only 26 letters .
For example , Spanish , French and German all have special letters or accents such as :              </tokentext>
<sentencetext>English is one of the few language that uses only 26 letters.
For example, Spanish, French and German all have special letters or accents such as : éèçôâüì</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924457</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29931689</id>
	<title>Re:Excellent idea</title>
	<author>wvmarle</author>
	<datestamp>1256918160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Trying to remove universal access and Babylonize the internet under the fairly flimsy pretext of internationalization seems a very misplaced effort to me.</p></div><p>Sorry but this sounds very much like arrogant neo-colonialism.
</p><p>Why would everyone have to use the Latin script? Just because it's convenient for you and the language of the people that happened to have set up the Internet? How about all those people that do not understand Latin scripts in the first place? Forcing them to use Latin scripts instead of their own is NOT universal access. Latin script is just one of the many scripts used in this world.
</p><p>On top of htat you don't even need to know how to enter Chinese or Arabic scripts as the underlying tech is still using the legacy Latin scripts. You can enter the Chinese URL in that way as well.</p></div>
	</htmltext>
<tokenext>Trying to remove universal access and Babylonize the internet under the fairly flimsy pretext of internationalization seems a very misplaced effort to me.Sorry but this sounds very much like arrogant neo-colonialism .
Why would everyone have to use the Latin script ?
Just because it 's convenient for you and the language of the people that happened to have set up the Internet ?
How about all those people that do not understand Latin scripts in the first place ?
Forcing them to use Latin scripts instead of their own is NOT universal access .
Latin script is just one of the many scripts used in this world .
On top of htat you do n't even need to know how to enter Chinese or Arabic scripts as the underlying tech is still using the legacy Latin scripts .
You can enter the Chinese URL in that way as well .</tokentext>
<sentencetext>Trying to remove universal access and Babylonize the internet under the fairly flimsy pretext of internationalization seems a very misplaced effort to me.Sorry but this sounds very much like arrogant neo-colonialism.
Why would everyone have to use the Latin script?
Just because it's convenient for you and the language of the people that happened to have set up the Internet?
How about all those people that do not understand Latin scripts in the first place?
Forcing them to use Latin scripts instead of their own is NOT universal access.
Latin script is just one of the many scripts used in this world.
On top of htat you don't even need to know how to enter Chinese or Arabic scripts as the underlying tech is still using the legacy Latin scripts.
You can enter the Chinese URL in that way as well.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926455</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927537</id>
	<title>Re:Raise your hand if you're surprised...</title>
	<author>Anonymous</author>
	<datestamp>1256933760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>They also just made everyday life on the internet less difficult for an even larger number of people. You should already be paying close attention to the links you're clicking - maybe you should just stick to latin based domains?</p></htmltext>
<tokenext>They also just made everyday life on the internet less difficult for an even larger number of people .
You should already be paying close attention to the links you 're clicking - maybe you should just stick to latin based domains ?</tokentext>
<sentencetext>They also just made everyday life on the internet less difficult for an even larger number of people.
You should already be paying close attention to the links you're clicking - maybe you should just stick to latin based domains?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924011</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925011</id>
	<title>Re:Phishing aid</title>
	<author>Mathieu Lutfy</author>
	<datestamp>1256922540000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>This risk can be greatly reduced if they limit domain names to only one alphabet, i.e. Russian domain with Cyrillic ccTLD should have only Cyrillic letters in it.</p><p>In many of these countries, they often have two domain names for a website: one that is easy to remember by foreigners, one that is easy to remember by locals (i.e. cyrillic name transliterated to Latin alphabet). The transliterated domain name is usually horrible, sounds weird, and often people transliterate stuff in different ways, so it's often not easy to remember anyway.</p><p>I think non-latin ccTLDs is a good thing.</p><p>matt</p></htmltext>
<tokenext>This risk can be greatly reduced if they limit domain names to only one alphabet , i.e .
Russian domain with Cyrillic ccTLD should have only Cyrillic letters in it.In many of these countries , they often have two domain names for a website : one that is easy to remember by foreigners , one that is easy to remember by locals ( i.e .
cyrillic name transliterated to Latin alphabet ) .
The transliterated domain name is usually horrible , sounds weird , and often people transliterate stuff in different ways , so it 's often not easy to remember anyway.I think non-latin ccTLDs is a good thing.matt</tokentext>
<sentencetext>This risk can be greatly reduced if they limit domain names to only one alphabet, i.e.
Russian domain with Cyrillic ccTLD should have only Cyrillic letters in it.In many of these countries, they often have two domain names for a website: one that is easy to remember by foreigners, one that is easy to remember by locals (i.e.
cyrillic name transliterated to Latin alphabet).
The transliterated domain name is usually horrible, sounds weird, and often people transliterate stuff in different ways, so it's often not easy to remember anyway.I think non-latin ccTLDs is a good thing.matt</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926837</id>
	<title>Re:Encoding?</title>
	<author>spitzak</author>
	<datestamp>1256930400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>In UTF-8 if the second byte does not have the high bit set, it is an invalid encoding, and therefore should be treated as an error byte followed by that ASCII letter. You can be certain that if you see the byte 43 anywhere that it means a '+' , you do not ever have to examine surrounding bytes.</p><p>UTF-8 is much much easier to deal with than people think. The best way to deal with UTF-8 is to treat all sequences of bytes with the high bit set as some kind of "foreign word" that you should not interpret and not split. The fact that it might actually be a single Unicode code point or mulitple ones or contain errors really should have no effect on your software. Only in extremely rare circumstances, such as when you actually need to draw a string on the display for the user, do you need to do anything more complicated such as detect errors and figure out what Unicode code points are represented.</p><p>Unfortunatly there are far too many programmers who get completely flummoxed when presented with UTF-8 and go crazy trying to treat the Unicode decoding as "characters". This seems to be due to decades of being exposed to documentation that says "character" instead of "byte" so that they start to think there is some magical property so that the computer is incapable of pointing to a byte inside a character or that existence of such a pointer will somehow make the string unreadable. The best exercise is to imagine "words" in text and figure out why a huge amount of text processing is possible without having to always find the word boundaries, and why you can iterate over the "pieces" of the "words" without crashing and without making the string somehow "wrong", and that the word 'I' and 'a' have only one letter but are still "words", and then hit yourself with the clue-by-4 until you realize that there is no difference between a "word" and a "character".</p></htmltext>
<tokenext>In UTF-8 if the second byte does not have the high bit set , it is an invalid encoding , and therefore should be treated as an error byte followed by that ASCII letter .
You can be certain that if you see the byte 43 anywhere that it means a ' + ' , you do not ever have to examine surrounding bytes.UTF-8 is much much easier to deal with than people think .
The best way to deal with UTF-8 is to treat all sequences of bytes with the high bit set as some kind of " foreign word " that you should not interpret and not split .
The fact that it might actually be a single Unicode code point or mulitple ones or contain errors really should have no effect on your software .
Only in extremely rare circumstances , such as when you actually need to draw a string on the display for the user , do you need to do anything more complicated such as detect errors and figure out what Unicode code points are represented.Unfortunatly there are far too many programmers who get completely flummoxed when presented with UTF-8 and go crazy trying to treat the Unicode decoding as " characters " .
This seems to be due to decades of being exposed to documentation that says " character " instead of " byte " so that they start to think there is some magical property so that the computer is incapable of pointing to a byte inside a character or that existence of such a pointer will somehow make the string unreadable .
The best exercise is to imagine " words " in text and figure out why a huge amount of text processing is possible without having to always find the word boundaries , and why you can iterate over the " pieces " of the " words " without crashing and without making the string somehow " wrong " , and that the word 'I ' and 'a ' have only one letter but are still " words " , and then hit yourself with the clue-by-4 until you realize that there is no difference between a " word " and a " character " .</tokentext>
<sentencetext>In UTF-8 if the second byte does not have the high bit set, it is an invalid encoding, and therefore should be treated as an error byte followed by that ASCII letter.
You can be certain that if you see the byte 43 anywhere that it means a '+' , you do not ever have to examine surrounding bytes.UTF-8 is much much easier to deal with than people think.
The best way to deal with UTF-8 is to treat all sequences of bytes with the high bit set as some kind of "foreign word" that you should not interpret and not split.
The fact that it might actually be a single Unicode code point or mulitple ones or contain errors really should have no effect on your software.
Only in extremely rare circumstances, such as when you actually need to draw a string on the display for the user, do you need to do anything more complicated such as detect errors and figure out what Unicode code points are represented.Unfortunatly there are far too many programmers who get completely flummoxed when presented with UTF-8 and go crazy trying to treat the Unicode decoding as "characters".
This seems to be due to decades of being exposed to documentation that says "character" instead of "byte" so that they start to think there is some magical property so that the computer is incapable of pointing to a byte inside a character or that existence of such a pointer will somehow make the string unreadable.
The best exercise is to imagine "words" in text and figure out why a huge amount of text processing is possible without having to always find the word boundaries, and why you can iterate over the "pieces" of the "words" without crashing and without making the string somehow "wrong", and that the word 'I' and 'a' have only one letter but are still "words", and then hit yourself with the clue-by-4 until you realize that there is no difference between a "word" and a "character".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924523</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927455</id>
	<title>Re:Raise your hand if you're surprised...</title>
	<author>Estanislao Martínez</author>
	<datestamp>1256933400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>ICANN just made another move to make everyday life on the internet slightly more difficult for many users, while making life for con artists, spammers, phishers, etc, much much easier (and more profitable).</p></div> </blockquote><p>Why do I get the feeling that there's a group of people affected by this change that you're not mentioning...</p></div>
	</htmltext>
<tokenext>ICANN just made another move to make everyday life on the internet slightly more difficult for many users , while making life for con artists , spammers , phishers , etc , much much easier ( and more profitable ) .
Why do I get the feeling that there 's a group of people affected by this change that you 're not mentioning.. .</tokentext>
<sentencetext>ICANN just made another move to make everyday life on the internet slightly more difficult for many users, while making life for con artists, spammers, phishers, etc, much much easier (and more profitable).
Why do I get the feeling that there's a group of people affected by this change that you're not mentioning...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924011</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925437</id>
	<title>Re:Phishing aid</title>
	<author>Yvanhoe</author>
	<datestamp>1256923980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>That was my first thought. I'll go register "slshdot.org" now (the first 'a' is in fact the cyrilic version). I'm sure<nobr> <wbr></nobr>.net will be popular as well.</htmltext>
<tokenext>That was my first thought .
I 'll go register " slshdot.org " now ( the first 'a ' is in fact the cyrilic version ) .
I 'm sure .net will be popular as well .</tokentext>
<sentencetext>That was my first thought.
I'll go register "slshdot.org" now (the first 'a' is in fact the cyrilic version).
I'm sure .net will be popular as well.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924047</id>
	<title>ICANN...</title>
	<author>Schnoogs</author>
	<datestamp>1256918760000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><p>haz cheezburger?</p><p>(Short messages rule)</p></htmltext>
<tokenext>haz cheezburger ?
( Short messages rule )</tokentext>
<sentencetext>haz cheezburger?
(Short messages rule)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926955</id>
	<title>Its to do with people with the wrong keyboard ...</title>
	<author>clint999</author>
	<datestamp>1256931000000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><b>That has been possible for years.This is about registering bankofamerica.c&#245;m or lloydstsb.c&#248;.&#251;kThe part AFTER the dot.</b></htmltext>
<tokenext>That has been possible for years.This is about registering bankofamerica.c   m or lloydstsb.c   .   kThe part AFTER the dot .</tokentext>
<sentencetext>That has been possible for years.This is about registering bankofamerica.cõm or lloydstsb.cø.ûkThe part AFTER the dot.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924631</id>
	<title>A complete mess.</title>
	<author>Anonymous</author>
	<datestamp>1256921040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>As I said, a complete mess.</p><p>God knows what will happen with all DNS caches full of cn--, all security risks, bugs, all unreachable websites (unless you have unicode in your system), confusion, the exponential gowth of phishing, scams, and domain theft.</p><p>Unbelievable. Today Internet was such an orderly, quiet medium and now this. One day they will allow people to call each other through the Internet without using their home telephone! Can you imagine?</p></htmltext>
<tokenext>As I said , a complete mess.God knows what will happen with all DNS caches full of cn-- , all security risks , bugs , all unreachable websites ( unless you have unicode in your system ) , confusion , the exponential gowth of phishing , scams , and domain theft.Unbelievable .
Today Internet was such an orderly , quiet medium and now this .
One day they will allow people to call each other through the Internet without using their home telephone !
Can you imagine ?</tokentext>
<sentencetext>As I said, a complete mess.God knows what will happen with all DNS caches full of cn--, all security risks, bugs, all unreachable websites (unless you have unicode in your system), confusion, the exponential gowth of phishing, scams, and domain theft.Unbelievable.
Today Internet was such an orderly, quiet medium and now this.
One day they will allow people to call each other through the Internet without using their home telephone!
Can you imagine?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925255</id>
	<title>Re:Excellent idea</title>
	<author>chord.wav</author>
	<datestamp>1256923380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Your point may be valid for some non-latin languages but as soon as you put China into the equation the figures change radically.</p><p>China IS the world. They are zillions! If they start using Chinese names it'll be us, "latin speakers", who'll be confined to our "own language and make our sites inaccesible to the rest of the world".</p></htmltext>
<tokenext>Your point may be valid for some non-latin languages but as soon as you put China into the equation the figures change radically.China IS the world .
They are zillions !
If they start using Chinese names it 'll be us , " latin speakers " , who 'll be confined to our " own language and make our sites inaccesible to the rest of the world " .</tokentext>
<sentencetext>Your point may be valid for some non-latin languages but as soon as you put China into the equation the figures change radically.China IS the world.
They are zillions!
If they start using Chinese names it'll be us, "latin speakers", who'll be confined to our "own language and make our sites inaccesible to the rest of the world".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925615</id>
	<title>Re:Um, can they be more specific than "Unicode"?</title>
	<author>Kickasso</author>
	<datestamp>1256924880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Unicode does not necessarily mean any of this crap. International domain names don't use UTF-8 or UCS2 or anything like that, they are represented with a scheme called Punycode. Being a software developer, you may want to know a bit more about it. Just stop by any information kiosk marked with big rainbow-coloured GOOGLE sign and ask the friendly staff. Don't hesitate to ask about the difference between Unicode and the UTFs too, while you're at it.</p><p>The C programming language and sizeof(wchar\_t) has absolutely nothing to do with this discussion. Internet standards are not defined in terms of C and its data types.</p></htmltext>
<tokenext>Unicode does not necessarily mean any of this crap .
International domain names do n't use UTF-8 or UCS2 or anything like that , they are represented with a scheme called Punycode .
Being a software developer , you may want to know a bit more about it .
Just stop by any information kiosk marked with big rainbow-coloured GOOGLE sign and ask the friendly staff .
Do n't hesitate to ask about the difference between Unicode and the UTFs too , while you 're at it.The C programming language and sizeof ( wchar \ _t ) has absolutely nothing to do with this discussion .
Internet standards are not defined in terms of C and its data types .</tokentext>
<sentencetext>Unicode does not necessarily mean any of this crap.
International domain names don't use UTF-8 or UCS2 or anything like that, they are represented with a scheme called Punycode.
Being a software developer, you may want to know a bit more about it.
Just stop by any information kiosk marked with big rainbow-coloured GOOGLE sign and ask the friendly staff.
Don't hesitate to ask about the difference between Unicode and the UTFs too, while you're at it.The C programming language and sizeof(wchar\_t) has absolutely nothing to do with this discussion.
Internet standards are not defined in terms of C and its data types.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924161</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923889</id>
	<title>Re:ICANN has lost it!</title>
	<author>Anonymous</author>
	<datestamp>1256918100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>That no reason to stop progress.  If everyone thought like this, we would still all be programming in COBOL</p></htmltext>
<tokenext>That no reason to stop progress .
If everyone thought like this , we would still all be programming in COBOL</tokentext>
<sentencetext>That no reason to stop progress.
If everyone thought like this, we would still all be programming in COBOL</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924579</id>
	<title>What's new here?</title>
	<author>nstrom</author>
	<datestamp>1256920800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Aren't IDNs already available via Puncode encoding? (For example the ones at <a href="http://www.w3.org/2003/Talks/0425-duerst-idniri/slide12-0.html" title="w3.org">http://www.w3.org/2003/Talks/0425-duerst-idniri/slide12-0.html</a> [w3.org]) Or am I missing something?</htmltext>
<tokenext>Are n't IDNs already available via Puncode encoding ?
( For example the ones at http : //www.w3.org/2003/Talks/0425-duerst-idniri/slide12-0.html [ w3.org ] ) Or am I missing something ?</tokentext>
<sentencetext>Aren't IDNs already available via Puncode encoding?
(For example the ones at http://www.w3.org/2003/Talks/0425-duerst-idniri/slide12-0.html [w3.org]) Or am I missing something?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925787</id>
	<title>Re:Hmm...</title>
	<author>xaxa</author>
	<datestamp>1256925720000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>micr&#246;s&#246;ft.c&#246;m?</p></div><p>That's Microsoft with the volume turned up to 11?</p></div>
	</htmltext>
<tokenext>micr   s   ft.c   m ? That 's Microsoft with the volume turned up to 11 ?</tokentext>
<sentencetext>micrösöft.cöm?That's Microsoft with the volume turned up to 11?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923639</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924761</id>
	<title>Re:first urls, then slashdot</title>
	<author>mrdoogee</author>
	<datestamp>1256921640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>A M&#248;&#248;se once bit my sister...</htmltext>
<tokenext>A M     se once bit my sister.. .</tokentext>
<sentencetext>A Møøse once bit my sister...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923703</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923991</id>
	<title>Re:ICANN has lost it!</title>
	<author>Anonymous</author>
	<datestamp>1256918520000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>This is about letting people use characters from their frickin' own language instead of just english.</p><p>Just like so many other things in programming.. if the software doesn't do international, it doesn't do international.</p><p>This has nothing to do with making more TLDs.</p></htmltext>
<tokenext>This is about letting people use characters from their frickin ' own language instead of just english.Just like so many other things in programming.. if the software does n't do international , it does n't do international.This has nothing to do with making more TLDs .</tokentext>
<sentencetext>This is about letting people use characters from their frickin' own language instead of just english.Just like so many other things in programming.. if the software doesn't do international, it doesn't do international.This has nothing to do with making more TLDs.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924435</id>
	<title>Re:ICANN has lost it!</title>
	<author>pablo.cl</author>
	<datestamp>1256920260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What about<nobr> <wbr></nobr>.museum or<nobr> <wbr></nobr>.info? (more than three letters).</p></htmltext>
<tokenext>What about .museum or .info ?
( more than three letters ) .</tokentext>
<sentencetext>What about .museum or .info?
(more than three letters).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924961</id>
	<title>so chase.com</title>
	<author>circletimessquare</author>
	<datestamp>1256922300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>could be ch&#224;se.com or ch&#225;se.com</p><p>every website i go to from now on, i need to study the url with a magnifying glass to make sure i am getting the actual site i wanted. not even as a security precaution, but just to avoid phony sites that might be spoofing a real one for all sorts of purposes, even if just humor, not all of them nefarious, but all of them certainly annoying</p><p>a with accent mark may be easy to see, but there are some subtle unicode characters that are so completely like the lowercase "L" or upper case "I" or upper and lowercase "O", etc., and each different font might render the different characters in so many subtle variations, that its almost impossible anymore to guarantee that the link you followed actually went to the site you think it did</p><p>so we have to type addresses by hand to make sure they are genuine from now on?</p><p>its not cultural imperialism to support only 30 or so characters for website addresses. think of it as a universal routing system, that is purposefully limited, simply for the sake of security and peace of mind</p><p>characters for website addresses should remain small in number. simplicity means security. now we have opened a can of worms, and i think the spoofing will actually be worst for those who use nonlatin alphabets, as they are more likely to be mixing latin and nonlatin characters in their address bar</p></htmltext>
<tokenext>could be ch   se.com or ch   se.comevery website i go to from now on , i need to study the url with a magnifying glass to make sure i am getting the actual site i wanted .
not even as a security precaution , but just to avoid phony sites that might be spoofing a real one for all sorts of purposes , even if just humor , not all of them nefarious , but all of them certainly annoyinga with accent mark may be easy to see , but there are some subtle unicode characters that are so completely like the lowercase " L " or upper case " I " or upper and lowercase " O " , etc. , and each different font might render the different characters in so many subtle variations , that its almost impossible anymore to guarantee that the link you followed actually went to the site you think it didso we have to type addresses by hand to make sure they are genuine from now on ? its not cultural imperialism to support only 30 or so characters for website addresses .
think of it as a universal routing system , that is purposefully limited , simply for the sake of security and peace of mindcharacters for website addresses should remain small in number .
simplicity means security .
now we have opened a can of worms , and i think the spoofing will actually be worst for those who use nonlatin alphabets , as they are more likely to be mixing latin and nonlatin characters in their address bar</tokentext>
<sentencetext>could be chàse.com or cháse.comevery website i go to from now on, i need to study the url with a magnifying glass to make sure i am getting the actual site i wanted.
not even as a security precaution, but just to avoid phony sites that might be spoofing a real one for all sorts of purposes, even if just humor, not all of them nefarious, but all of them certainly annoyinga with accent mark may be easy to see, but there are some subtle unicode characters that are so completely like the lowercase "L" or upper case "I" or upper and lowercase "O", etc., and each different font might render the different characters in so many subtle variations, that its almost impossible anymore to guarantee that the link you followed actually went to the site you think it didso we have to type addresses by hand to make sure they are genuine from now on?its not cultural imperialism to support only 30 or so characters for website addresses.
think of it as a universal routing system, that is purposefully limited, simply for the sake of security and peace of mindcharacters for website addresses should remain small in number.
simplicity means security.
now we have opened a can of worms, and i think the spoofing will actually be worst for those who use nonlatin alphabets, as they are more likely to be mixing latin and nonlatin characters in their address bar</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926589</id>
	<title>Boo hoo</title>
	<author>Anonymous</author>
	<datestamp>1256929440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>How about just put the icon in the URL bar (like there is for FAVICON etc) with the country flag of the non-ASCII components in a URL if it exists.</p><p>The only reason not to use a flag in the case of plain old ASCII 7 bit is because it should be the UK flag, but the USians wouldn't like that.</p><p>So if you see www.chase.com and a french flag, YOU run away. Unless you know they host a french site at that URL.</p></htmltext>
<tokenext>How about just put the icon in the URL bar ( like there is for FAVICON etc ) with the country flag of the non-ASCII components in a URL if it exists.The only reason not to use a flag in the case of plain old ASCII 7 bit is because it should be the UK flag , but the USians would n't like that.So if you see www.chase.com and a french flag , YOU run away .
Unless you know they host a french site at that URL .</tokentext>
<sentencetext>How about just put the icon in the URL bar (like there is for FAVICON etc) with the country flag of the non-ASCII components in a URL if it exists.The only reason not to use a flag in the case of plain old ASCII 7 bit is because it should be the UK flag, but the USians wouldn't like that.So if you see www.chase.com and a french flag, YOU run away.
Unless you know they host a french site at that URL.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924961</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924897</id>
	<title>Re:Um, can they be more specific than "Unicode"?</title>
	<author>maxume</author>
	<datestamp>1256922060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The article doesn't say so, but the standard uses Punycode, which is pretty much equivalent to UTF-8 and such (in that it encodes some Unicode codepoints in a specific way).</p></htmltext>
<tokenext>The article does n't say so , but the standard uses Punycode , which is pretty much equivalent to UTF-8 and such ( in that it encodes some Unicode codepoints in a specific way ) .</tokentext>
<sentencetext>The article doesn't say so, but the standard uses Punycode, which is pretty much equivalent to UTF-8 and such (in that it encodes some Unicode codepoints in a specific way).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924161</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924457</id>
	<title>Latin =/= Support for English only.</title>
	<author>mano.m</author>
	<datestamp>1256920380000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>A lot of the debate here seems to be about English-speaking countries vs. the rest of the world, but English isn't the only language that uses the Latin. Also, the unavailability of non-Latin scripts hasn't hampered the flourishing of home-grown websites in India and China named in their many local languages - what makes the ICANN think this is even necessary?</htmltext>
<tokenext>A lot of the debate here seems to be about English-speaking countries vs. the rest of the world , but English is n't the only language that uses the Latin .
Also , the unavailability of non-Latin scripts has n't hampered the flourishing of home-grown websites in India and China named in their many local languages - what makes the ICANN think this is even necessary ?</tokentext>
<sentencetext>A lot of the debate here seems to be about English-speaking countries vs. the rest of the world, but English isn't the only language that uses the Latin.
Also, the unavailability of non-Latin scripts hasn't hampered the flourishing of home-grown websites in India and China named in their many local languages - what makes the ICANN think this is even necessary?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925857</id>
	<title>Re:ICANN has lost it!</title>
	<author>xaxa</author>
	<datestamp>1256926140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Slashdot won't take accept my links, but some examples are on <a href="http://idn.icann.org/#The\_example.test\_names" title="icann.org">this page</a> [icann.org]</p></htmltext>
<tokenext>Slashdot wo n't take accept my links , but some examples are on this page [ icann.org ]</tokentext>
<sentencetext>Slashdot won't take accept my links, but some examples are on this page [icann.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927305</id>
	<title>Re:Excellent idea</title>
	<author>Estanislao Martínez</author>
	<datestamp>1256932680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>One big issue for many lower-educated Chinese is that the Latin script is as strange as Chinese characters to us. Of course you can look at the shape and recognise them, but that's it: the letters do not carry sounds to them.</p></div></blockquote><p>Actually, many of them have problems even in the "look at the shape and recognize them" part.  Spend some time looking at some of those "Engrish" websites featuring incorrect and/or nonsensical English in Asian countries, and you can spot this regularly: people mixing up "p" and "q", "b" and "d", "r" and "n", "t" and "f", "i" and "l", etc., because the shapes are similar.</p></div>
	</htmltext>
<tokenext>One big issue for many lower-educated Chinese is that the Latin script is as strange as Chinese characters to us .
Of course you can look at the shape and recognise them , but that 's it : the letters do not carry sounds to them.Actually , many of them have problems even in the " look at the shape and recognize them " part .
Spend some time looking at some of those " Engrish " websites featuring incorrect and/or nonsensical English in Asian countries , and you can spot this regularly : people mixing up " p " and " q " , " b " and " d " , " r " and " n " , " t " and " f " , " i " and " l " , etc. , because the shapes are similar .</tokentext>
<sentencetext>One big issue for many lower-educated Chinese is that the Latin script is as strange as Chinese characters to us.
Of course you can look at the shape and recognise them, but that's it: the letters do not carry sounds to them.Actually, many of them have problems even in the "look at the shape and recognize them" part.
Spend some time looking at some of those "Engrish" websites featuring incorrect and/or nonsensical English in Asian countries, and you can spot this regularly: people mixing up "p" and "q", "b" and "d", "r" and "n", "t" and "f", "i" and "l", etc., because the shapes are similar.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924917</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930397</id>
	<title>Re:ICANN has lost it!</title>
	<author>DarkOx</author>
	<datestamp>1256906700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>There is no reason to make most of South East Asia and China 2nd-rate citizens on the internet.</p></div><p>Sure there is a reason.  The internet is most likely the most influential media outlet in existence today.  It can do more to spread culture and ideas than any other tools we have.  I for one enjoy living in the dominate culture where global communication and commerce are concerned.  As an American I very much want American hegemony CONTINUED!  I also understand not cooperating with other cultures at all will lead them to form their own little clubs which exclude us; and if that happens and enough of them get together than we would find ourselves on the outside.</p><p>I am not totally against letting them have their funny little characters in URLs for stuff only they care about anyway.  I just hope its part of a larger plan to keep them on our network doing things for the most part on our terms.  I am all for marginalizing other cultures and making them feel good about it at the same time if we can get away with it.</p></div>
	</htmltext>
<tokenext>There is no reason to make most of South East Asia and China 2nd-rate citizens on the internet.Sure there is a reason .
The internet is most likely the most influential media outlet in existence today .
It can do more to spread culture and ideas than any other tools we have .
I for one enjoy living in the dominate culture where global communication and commerce are concerned .
As an American I very much want American hegemony CONTINUED !
I also understand not cooperating with other cultures at all will lead them to form their own little clubs which exclude us ; and if that happens and enough of them get together than we would find ourselves on the outside.I am not totally against letting them have their funny little characters in URLs for stuff only they care about anyway .
I just hope its part of a larger plan to keep them on our network doing things for the most part on our terms .
I am all for marginalizing other cultures and making them feel good about it at the same time if we can get away with it .</tokentext>
<sentencetext>There is no reason to make most of South East Asia and China 2nd-rate citizens on the internet.Sure there is a reason.
The internet is most likely the most influential media outlet in existence today.
It can do more to spread culture and ideas than any other tools we have.
I for one enjoy living in the dominate culture where global communication and commerce are concerned.
As an American I very much want American hegemony CONTINUED!
I also understand not cooperating with other cultures at all will lead them to form their own little clubs which exclude us; and if that happens and enough of them get together than we would find ourselves on the outside.I am not totally against letting them have their funny little characters in URLs for stuff only they care about anyway.
I just hope its part of a larger plan to keep them on our network doing things for the most part on our terms.
I am all for marginalizing other cultures and making them feel good about it at the same time if we can get away with it.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924021</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923771</id>
	<title>NSFW</title>
	<author>Anonymous</author>
	<datestamp>1256917560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>===Reader dhermann adds, "Great, now even less chance I can identify NSFW links before they are blocked by my work's big brother app and my boss is notified... again."===</p><p>Seriously?  You think people shouldn't be able to use internet in their native language because you are afraid of getting in trouble for browsing the web at work when you already know you shouldn't?  I'd fire you right now if I was your boss.</p></htmltext>
<tokenext>= = = Reader dhermann adds , " Great , now even less chance I can identify NSFW links before they are blocked by my work 's big brother app and my boss is notified.. .
again. " = = = Seriously ? You think people should n't be able to use internet in their native language because you are afraid of getting in trouble for browsing the web at work when you already know you should n't ?
I 'd fire you right now if I was your boss .</tokentext>
<sentencetext>===Reader dhermann adds, "Great, now even less chance I can identify NSFW links before they are blocked by my work's big brother app and my boss is notified...
again."===Seriously?  You think people shouldn't be able to use internet in their native language because you are afraid of getting in trouble for browsing the web at work when you already know you shouldn't?
I'd fire you right now if I was your boss.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923939</id>
	<title>Re:Encoding?</title>
	<author>Looce</author>
	<datestamp>1256918280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Since <a href="http://tech.slashdot.org/comments.pl?sid=1425033&amp;cid=29923735" title="slashdot.org">software makes the assumption that TLDs only contain [a-z0-9-]</a> [slashdot.org], UTF-8 can't be used in the DNS. Internationalised domain names, even before these new ccTLDs, used that xn-- system, called <a href="http://en.wikipedia.org/wiki/Punycode" title="wikipedia.org">Punycode</a> [wikipedia.org]. For instance, the site tinyarro.ws, which provides short URLs via a Unicode domain name, already used<nobr> <wbr></nobr>.ws for that purpose. It turns into xn--hgi.ws when the DNS request is issued.</p><p>ccTLDs using Punycode is just an extension of that mechanism for second-level domains.</p></htmltext>
<tokenext>Since software makes the assumption that TLDs only contain [ a-z0-9- ] [ slashdot.org ] , UTF-8 ca n't be used in the DNS .
Internationalised domain names , even before these new ccTLDs , used that xn-- system , called Punycode [ wikipedia.org ] .
For instance , the site tinyarro.ws , which provides short URLs via a Unicode domain name , already used .ws for that purpose .
It turns into xn--hgi.ws when the DNS request is issued.ccTLDs using Punycode is just an extension of that mechanism for second-level domains .</tokentext>
<sentencetext>Since software makes the assumption that TLDs only contain [a-z0-9-] [slashdot.org], UTF-8 can't be used in the DNS.
Internationalised domain names, even before these new ccTLDs, used that xn-- system, called Punycode [wikipedia.org].
For instance, the site tinyarro.ws, which provides short URLs via a Unicode domain name, already used .ws for that purpose.
It turns into xn--hgi.ws when the DNS request is issued.ccTLDs using Punycode is just an extension of that mechanism for second-level domains.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930251</id>
	<title>Re:Phishing aid</title>
	<author>Anonymous</author>
	<datestamp>1256905980000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>What? Since when are TLDs semantic? Most TLDs are freely available, so you cannot infer anything from them, other than the image the domain holder tries to convey. I don't know if anyone will be fooled by a Cyrillic<nobr> <wbr></nobr>.ru domain into thinking it must be a website about Python. And if they are, what is the damage?</p></htmltext>
<tokenext>What ?
Since when are TLDs semantic ?
Most TLDs are freely available , so you can not infer anything from them , other than the image the domain holder tries to convey .
I do n't know if anyone will be fooled by a Cyrillic .ru domain into thinking it must be a website about Python .
And if they are , what is the damage ?</tokentext>
<sentencetext>What?
Since when are TLDs semantic?
Most TLDs are freely available, so you cannot infer anything from them, other than the image the domain holder tries to convey.
I don't know if anyone will be fooled by a Cyrillic .ru domain into thinking it must be a website about Python.
And if they are, what is the damage?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924031</id>
	<title>Re:Encoding?</title>
	<author>Delwin</author>
	<datestamp>1256918640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>because UTF8 only solves the null term problem, not the readable character issue.</htmltext>
<tokenext>because UTF8 only solves the null term problem , not the readable character issue .</tokentext>
<sentencetext>because UTF8 only solves the null term problem, not the readable character issue.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928685</id>
	<title>Re:Encoding?</title>
	<author>Anonymous</author>
	<datestamp>1256896020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'm not a DNS guru, but I've had lots of experience with UTF-8 characters and problems that involve them (not UTF8's fault, but the fault of bad systems that don't accept them properly).</p><p>UTF-8 has, in addition to a wonderfully rich set of characters that can represent almost any written text in the world's history, also tends to have lots of repeated and easily confusable characters.  E.g. "your&ndash;bank&ndash;website.com" looks just like "your-bank-website.com", but it's not!  Several other characters have the same thing going on.  This is a Cyrillic "x": "".  Can you tell the difference?  UTF8 will lead to abuse in this way.  Unless you tried to restrict the set of UTF8 characters that can be used in DNS but that's obviously going to lead to very messy implementations.</p></htmltext>
<tokenext>I 'm not a DNS guru , but I 've had lots of experience with UTF-8 characters and problems that involve them ( not UTF8 's fault , but the fault of bad systems that do n't accept them properly ) .UTF-8 has , in addition to a wonderfully rich set of characters that can represent almost any written text in the world 's history , also tends to have lots of repeated and easily confusable characters .
E.g. " your    bank    website.com " looks just like " your-bank-website.com " , but it 's not !
Several other characters have the same thing going on .
This is a Cyrillic " x " : " " .
Can you tell the difference ?
UTF8 will lead to abuse in this way .
Unless you tried to restrict the set of UTF8 characters that can be used in DNS but that 's obviously going to lead to very messy implementations .</tokentext>
<sentencetext>I'm not a DNS guru, but I've had lots of experience with UTF-8 characters and problems that involve them (not UTF8's fault, but the fault of bad systems that don't accept them properly).UTF-8 has, in addition to a wonderfully rich set of characters that can represent almost any written text in the world's history, also tends to have lots of repeated and easily confusable characters.
E.g. "your–bank–website.com" looks just like "your-bank-website.com", but it's not!
Several other characters have the same thing going on.
This is a Cyrillic "x": "".
Can you tell the difference?
UTF8 will lead to abuse in this way.
Unless you tried to restrict the set of UTF8 characters that can be used in DNS but that's obviously going to lead to very messy implementations.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924809</id>
	<title>Don't</title>
	<author>Anonymous</author>
	<datestamp>1256921820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Don't most countries already have a country code tld? What will they do with the old code for thier country? Sell it like Tonga and Tuvalu?<br>(And those two countries just mentioned don't have a different alphabet - I don't think they had a written language before contact with europeans.</p></htmltext>
<tokenext>Do n't most countries already have a country code tld ?
What will they do with the old code for thier country ?
Sell it like Tonga and Tuvalu ?
( And those two countries just mentioned do n't have a different alphabet - I do n't think they had a written language before contact with europeans .</tokentext>
<sentencetext>Don't most countries already have a country code tld?
What will they do with the old code for thier country?
Sell it like Tonga and Tuvalu?
(And those two countries just mentioned don't have a different alphabet - I don't think they had a written language before contact with europeans.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925159</id>
	<title>Search Engins ^</title>
	<author>EgNagRah</author>
	<datestamp>1256923080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This will make guys like google seem like definite gateway to the internet... Everything seems to be shifting.
I don't think phishing will become a huge problem for people who get some PC training. On the other hand the countries more likely to have problems with this also have less of a chance to get people trained.
I also would hope that browsers will adopt a feature to protect us in a more realistic way.</htmltext>
<tokenext>This will make guys like google seem like definite gateway to the internet... Everything seems to be shifting .
I do n't think phishing will become a huge problem for people who get some PC training .
On the other hand the countries more likely to have problems with this also have less of a chance to get people trained .
I also would hope that browsers will adopt a feature to protect us in a more realistic way .</tokentext>
<sentencetext>This will make guys like google seem like definite gateway to the internet... Everything seems to be shifting.
I don't think phishing will become a huge problem for people who get some PC training.
On the other hand the countries more likely to have problems with this also have less of a chance to get people trained.
I also would hope that browsers will adopt a feature to protect us in a more realistic way.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29932289</id>
	<title>Obligatory</title>
	<author>Anonymous</author>
	<datestamp>1256925840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>ICANN haz UTF-8 domainz?</p></htmltext>
<tokenext>ICANN haz UTF-8 domainz ?</tokentext>
<sentencetext>ICANN haz UTF-8 domainz?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925253</id>
	<title>Re:The problem is switching keyboard input</title>
	<author>Lord Lode</author>
	<datestamp>1256923380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Hmm, I rarely, if ever, manually type URL's. Do you often have to?</htmltext>
<tokenext>Hmm , I rarely , if ever , manually type URL 's .
Do you often have to ?</tokentext>
<sentencetext>Hmm, I rarely, if ever, manually type URL's.
Do you often have to?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924333</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924021</id>
	<title>Re:ICANN has lost it!</title>
	<author>Anonymous</author>
	<datestamp>1256918580000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Yeah right. Because everybody in the whole world only uses ASCII right?</p><p>Sorry for sounding flippant, but such US-myopia is far to prevalent for my liking.... Come on guys: Wake up and smell the coffee! There is more to the world than the US! There is no reason to make most of South East Asia and China 2nd-rate citizens on the internet.</p><p>I agree that there is a lot of software that needs changing as a result though. But that just means more work, right? You could probably sell this as an anti-recession measure too.</p></htmltext>
<tokenext>Yeah right .
Because everybody in the whole world only uses ASCII right ? Sorry for sounding flippant , but such US-myopia is far to prevalent for my liking.... Come on guys : Wake up and smell the coffee !
There is more to the world than the US !
There is no reason to make most of South East Asia and China 2nd-rate citizens on the internet.I agree that there is a lot of software that needs changing as a result though .
But that just means more work , right ?
You could probably sell this as an anti-recession measure too .</tokentext>
<sentencetext>Yeah right.
Because everybody in the whole world only uses ASCII right?Sorry for sounding flippant, but such US-myopia is far to prevalent for my liking.... Come on guys: Wake up and smell the coffee!
There is more to the world than the US!
There is no reason to make most of South East Asia and China 2nd-rate citizens on the internet.I agree that there is a lot of software that needs changing as a result though.
But that just means more work, right?
You could probably sell this as an anti-recession measure too.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923729</id>
	<title>FORSTUS POSTUS</title>
	<author>Anonymous</author>
	<datestamp>1256917440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>First non-latin top level post.</p></htmltext>
<tokenext>First non-latin top level post .</tokentext>
<sentencetext>First non-latin top level post.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924577</id>
	<title>it just got easier to phish</title>
	<author>Nadaka</author>
	<datestamp>1256920800000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>Yay. Now you can can register yourbankname.com with some funky characters that render in exactly the same way as the letter you are used to.</p></htmltext>
<tokenext>Yay .
Now you can can register yourbankname.com with some funky characters that render in exactly the same way as the letter you are used to .</tokentext>
<sentencetext>Yay.
Now you can can register yourbankname.com with some funky characters that render in exactly the same way as the letter you are used to.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923667</id>
	<title>I took Latin in high school</title>
	<author>Anonymous</author>
	<datestamp>1256917200000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>I'm glad we're going with Non-Latin TLDs now, I never understood going to the website "e.pluribus.unm"</p></htmltext>
<tokenext>I 'm glad we 're going with Non-Latin TLDs now , I never understood going to the website " e.pluribus.unm "</tokentext>
<sentencetext>I'm glad we're going with Non-Latin TLDs now, I never understood going to the website "e.pluribus.unm"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924367</id>
	<title>NSFW links</title>
	<author>TheGreatOrangePeel</author>
	<datestamp>1256920080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>"Great, now even less chance I can identify NSFW links before they are blocked by my work's big brother app and my boss is notified... again."</p></div></blockquote><p>
If this is a common problem for you, turn off your browser's "load images" setting. Not a perfect solution, but better than a flashing neon animated GIF of bouncing boobs right as your boss walks by. Myself, I've a number of people I follow on twitter who post links and often fail to mention if they're work appropriate, so I set up <a href="http://souptonuts.sourceforge.net/sshtips.htm" title="sourceforge.net" rel="nofollow">PuTTY to be an SSH tunnel/SOCKS proxy</a> [sourceforge.net] (scroll down to, "PuTTY for WindowsXP") to my home file server.</p></div>
	</htmltext>
<tokenext>" Great , now even less chance I can identify NSFW links before they are blocked by my work 's big brother app and my boss is notified.. .
again. " If this is a common problem for you , turn off your browser 's " load images " setting .
Not a perfect solution , but better than a flashing neon animated GIF of bouncing boobs right as your boss walks by .
Myself , I 've a number of people I follow on twitter who post links and often fail to mention if they 're work appropriate , so I set up PuTTY to be an SSH tunnel/SOCKS proxy [ sourceforge.net ] ( scroll down to , " PuTTY for WindowsXP " ) to my home file server .</tokentext>
<sentencetext>"Great, now even less chance I can identify NSFW links before they are blocked by my work's big brother app and my boss is notified...
again."
If this is a common problem for you, turn off your browser's "load images" setting.
Not a perfect solution, but better than a flashing neon animated GIF of bouncing boobs right as your boss walks by.
Myself, I've a number of people I follow on twitter who post links and often fail to mention if they're work appropriate, so I set up PuTTY to be an SSH tunnel/SOCKS proxy [sourceforge.net] (scroll down to, "PuTTY for WindowsXP") to my home file server.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924161</id>
	<title>Um, can they be more specific than "Unicode"?</title>
	<author>Creepy</author>
	<datestamp>1256919300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Unicode can mean many things - UTF-8, UTF-16, UTF-32 - so specifying Unicode is not detailed enough to implement and by not specifying, it is opening a can of worms IMO.  UTF-8 tends to be slower and larger for non-ASCII but has wide acceptance.  It would also be the favorite for Linux/UNIX because it is very common there (my Linux box has LANG=en\_US.UTF-8) and also for communication with databases (in my experience, UTF-8 is what most enterprise companies use for their database settings if they need multi-language databases).  UTF-16 is worse for ASCII because it always has a second byte, but is generally faster and smaller for multibyte languages.  It is also the default character encoding for MacOS and Windows (and contrary to its name, it can, in fact, contain 4 bytes of characters - the older format, UCS-2 was 2-byte only).  It would be possible to support multiple encodings maybe on the URL, but this needs to be specified (for instance you could do something like http8:// or http16://).</p><p>To further throw a wrench in the works, wchar\_t in C has unspecified length and can be 8, 16, or 32 bit characters.  On Windows and Linux it is 16 bits.  On mac and BSD UNIX it is generally 32 bit.  This makes multi-platform programming using wide characters in C/C++ a bitch (and I say that from experience).</p></htmltext>
<tokenext>Unicode can mean many things - UTF-8 , UTF-16 , UTF-32 - so specifying Unicode is not detailed enough to implement and by not specifying , it is opening a can of worms IMO .
UTF-8 tends to be slower and larger for non-ASCII but has wide acceptance .
It would also be the favorite for Linux/UNIX because it is very common there ( my Linux box has LANG = en \ _US.UTF-8 ) and also for communication with databases ( in my experience , UTF-8 is what most enterprise companies use for their database settings if they need multi-language databases ) .
UTF-16 is worse for ASCII because it always has a second byte , but is generally faster and smaller for multibyte languages .
It is also the default character encoding for MacOS and Windows ( and contrary to its name , it can , in fact , contain 4 bytes of characters - the older format , UCS-2 was 2-byte only ) .
It would be possible to support multiple encodings maybe on the URL , but this needs to be specified ( for instance you could do something like http8 : // or http16 : // ) .To further throw a wrench in the works , wchar \ _t in C has unspecified length and can be 8 , 16 , or 32 bit characters .
On Windows and Linux it is 16 bits .
On mac and BSD UNIX it is generally 32 bit .
This makes multi-platform programming using wide characters in C/C + + a bitch ( and I say that from experience ) .</tokentext>
<sentencetext>Unicode can mean many things - UTF-8, UTF-16, UTF-32 - so specifying Unicode is not detailed enough to implement and by not specifying, it is opening a can of worms IMO.
UTF-8 tends to be slower and larger for non-ASCII but has wide acceptance.
It would also be the favorite for Linux/UNIX because it is very common there (my Linux box has LANG=en\_US.UTF-8) and also for communication with databases (in my experience, UTF-8 is what most enterprise companies use for their database settings if they need multi-language databases).
UTF-16 is worse for ASCII because it always has a second byte, but is generally faster and smaller for multibyte languages.
It is also the default character encoding for MacOS and Windows (and contrary to its name, it can, in fact, contain 4 bytes of characters - the older format, UCS-2 was 2-byte only).
It would be possible to support multiple encodings maybe on the URL, but this needs to be specified (for instance you could do something like http8:// or http16://).To further throw a wrench in the works, wchar\_t in C has unspecified length and can be 8, 16, or 32 bit characters.
On Windows and Linux it is 16 bits.
On mac and BSD UNIX it is generally 32 bit.
This makes multi-platform programming using wide characters in C/C++ a bitch (and I say that from experience).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29949836</id>
	<title>This could actually be useful.</title>
	<author>KritonK</author>
	<datestamp>1257175140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Although we already have non-Latin domain names, these were rather inconvenient for languages that are based on alphabets that are not derived from the Latin alphabet. E.g., if you wanted a Greek domain, you'd get something like &lt;bunch\_of\_Greek\_characters&gt;.gr, which requires keyboard switching to type, and is more inconvenient than simply typing an all-Latin name. Turning that "gr" into Greek may actually make browsing Greek sites easier, as the keyboard may be left permanently switched to Greek, while typing.</p><p>The same goes for Cyrillic, Arabic, Chinese, etc.</p><p>It goes without saying that there <em>is</em> a lot of money to be made here. Not only are non-English web sites now going to have an incentive to actually register non-Latin domain names, they're still going to keep renewing the old Latin domain names as well, so that the sites remain accessible from the English-speaking parts of the world.</p></htmltext>
<tokenext>Although we already have non-Latin domain names , these were rather inconvenient for languages that are based on alphabets that are not derived from the Latin alphabet .
E.g. , if you wanted a Greek domain , you 'd get something like .gr , which requires keyboard switching to type , and is more inconvenient than simply typing an all-Latin name .
Turning that " gr " into Greek may actually make browsing Greek sites easier , as the keyboard may be left permanently switched to Greek , while typing.The same goes for Cyrillic , Arabic , Chinese , etc.It goes without saying that there is a lot of money to be made here .
Not only are non-English web sites now going to have an incentive to actually register non-Latin domain names , they 're still going to keep renewing the old Latin domain names as well , so that the sites remain accessible from the English-speaking parts of the world .</tokentext>
<sentencetext>Although we already have non-Latin domain names, these were rather inconvenient for languages that are based on alphabets that are not derived from the Latin alphabet.
E.g., if you wanted a Greek domain, you'd get something like .gr, which requires keyboard switching to type, and is more inconvenient than simply typing an all-Latin name.
Turning that "gr" into Greek may actually make browsing Greek sites easier, as the keyboard may be left permanently switched to Greek, while typing.The same goes for Cyrillic, Arabic, Chinese, etc.It goes without saying that there is a lot of money to be made here.
Not only are non-English web sites now going to have an incentive to actually register non-Latin domain names, they're still going to keep renewing the old Latin domain names as well, so that the sites remain accessible from the English-speaking parts of the world.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927033</id>
	<title>Re:Phishing aid</title>
	<author>Anonymous</author>
	<datestamp>1256931360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>an idea i've thought about was to colour-code the url in the address bar to what language it's using.  for example, if it has cyrillic letters they appear against a red background while english ones appear against a blue one.</p><p>getting what language range a certain character is in with most utf8 (i know this isn't) systems is easy enough.</p><p>just &pound;0.01.</p></htmltext>
<tokenext>an idea i 've thought about was to colour-code the url in the address bar to what language it 's using .
for example , if it has cyrillic letters they appear against a red background while english ones appear against a blue one.getting what language range a certain character is in with most utf8 ( i know this is n't ) systems is easy enough.just   0.01 .</tokentext>
<sentencetext>an idea i've thought about was to colour-code the url in the address bar to what language it's using.
for example, if it has cyrillic letters they appear against a red background while english ones appear against a blue one.getting what language range a certain character is in with most utf8 (i know this isn't) systems is easy enough.just £0.01.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924151</id>
	<title>Good news</title>
	<author>qtriangle</author>
	<datestamp>1256919180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Good news for the non-english speaking users.

Though a challenge for search engines.</htmltext>
<tokenext>Good news for the non-english speaking users .
Though a challenge for search engines .</tokentext>
<sentencetext>Good news for the non-english speaking users.
Though a challenge for search engines.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923949</id>
	<title>Re:ICANN has lost it!</title>
	<author>imagoon</author>
	<datestamp>1256918340000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>If everyone in the world liked those latin characters, then sure.  But maybe someone else in the world prefers yahoo.(nihon*)?  Wanted to write it in kanji but<nobr> <wbr></nobr>/. doesn't seem to take unicode.</htmltext>
<tokenext>If everyone in the world liked those latin characters , then sure .
But maybe someone else in the world prefers yahoo. ( nihon * ) ?
Wanted to write it in kanji but / .
does n't seem to take unicode .</tokentext>
<sentencetext>If everyone in the world liked those latin characters, then sure.
But maybe someone else in the world prefers yahoo.(nihon*)?
Wanted to write it in kanji but /.
doesn't seem to take unicode.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924333</id>
	<title>The problem is switching keyboard input</title>
	<author>boef</author>
	<datestamp>1256919960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Most people here seem to miss one of the big reasons for this.   Just imagine what a pain it would be for you if it was required that you type 2 or 3 Kanji characters at the end of every URL that you type out manually.  These are not characters that are generally available on your keyboard and you have to switch they keyboard input to try and type them, or use a software keyboard etc.   Even if you are fluent in both languages, it is a pain in the arse.</htmltext>
<tokenext>Most people here seem to miss one of the big reasons for this .
Just imagine what a pain it would be for you if it was required that you type 2 or 3 Kanji characters at the end of every URL that you type out manually .
These are not characters that are generally available on your keyboard and you have to switch they keyboard input to try and type them , or use a software keyboard etc .
Even if you are fluent in both languages , it is a pain in the arse .</tokentext>
<sentencetext>Most people here seem to miss one of the big reasons for this.
Just imagine what a pain it would be for you if it was required that you type 2 or 3 Kanji characters at the end of every URL that you type out manually.
These are not characters that are generally available on your keyboard and you have to switch they keyboard input to try and type them, or use a software keyboard etc.
Even if you are fluent in both languages, it is a pain in the arse.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930885</id>
	<title>parent not troll</title>
	<author>reiisi</author>
	<datestamp>1256910060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I suppose I should go read the friendly A and see if ICANN has already specified all the native TLDs allowed as equivalents for country codes, and probably for<nobr> <wbr></nobr>.com,<nobr> <wbr></nobr>.org,<nobr> <wbr></nobr>.net,<nobr> <wbr></nobr>.mil,<nobr> <wbr></nobr>.edu,<nobr> <wbr></nobr>.etc., and mapped them to the equivalents.</p><p>Somehow, I doubt it.</p></htmltext>
<tokenext>I suppose I should go read the friendly A and see if ICANN has already specified all the native TLDs allowed as equivalents for country codes , and probably for .com , .org , .net , .mil , .edu , .etc. , and mapped them to the equivalents.Somehow , I doubt it .</tokentext>
<sentencetext>I suppose I should go read the friendly A and see if ICANN has already specified all the native TLDs allowed as equivalents for country codes, and probably for .com, .org, .net, .mil, .edu, .etc., and mapped them to the equivalents.Somehow, I doubt it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923631</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925599</id>
	<title>Re:Excellent idea</title>
	<author>w000t</author>
	<datestamp>1256924880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Believe it or not, it is possible to register multiple domain names and make them point to the same site. I mean, who would have thought of that, right? I've even heard it's possible to have more than one site to your name. Maybe this other little know fact could be used to have 2 sites, perhaps a local one and an international one (but who am I to tell what people will come up with when they found out all this?). But, yeah, other than that, I totally agree with you. Non-latin ccTLDs can't possibly be used for anything else than fulfilling people's "misplaced patriotism". It's not like everybody in the world can't understand the latin alphabet already. That's only to be expected, after all, we would too fell right at home if asked to type giberish in other alphabets as well. I for one would certainly have no trouble typing anything you throw at me, irregardless of alphabet. Chinese, Arabic, Cyrillic, Japanese, you name it, I've mastered them all. What's more, thanks to my great observation skills, I can guess the general meaning of it simply by staring at said giberish for a minute or so. Anyways, I hope to have contributed to your in-deep analysis of the situation.</htmltext>
<tokenext>Believe it or not , it is possible to register multiple domain names and make them point to the same site .
I mean , who would have thought of that , right ?
I 've even heard it 's possible to have more than one site to your name .
Maybe this other little know fact could be used to have 2 sites , perhaps a local one and an international one ( but who am I to tell what people will come up with when they found out all this ? ) .
But , yeah , other than that , I totally agree with you .
Non-latin ccTLDs ca n't possibly be used for anything else than fulfilling people 's " misplaced patriotism " .
It 's not like everybody in the world ca n't understand the latin alphabet already .
That 's only to be expected , after all , we would too fell right at home if asked to type giberish in other alphabets as well .
I for one would certainly have no trouble typing anything you throw at me , irregardless of alphabet .
Chinese , Arabic , Cyrillic , Japanese , you name it , I 've mastered them all .
What 's more , thanks to my great observation skills , I can guess the general meaning of it simply by staring at said giberish for a minute or so .
Anyways , I hope to have contributed to your in-deep analysis of the situation .</tokentext>
<sentencetext>Believe it or not, it is possible to register multiple domain names and make them point to the same site.
I mean, who would have thought of that, right?
I've even heard it's possible to have more than one site to your name.
Maybe this other little know fact could be used to have 2 sites, perhaps a local one and an international one (but who am I to tell what people will come up with when they found out all this?).
But, yeah, other than that, I totally agree with you.
Non-latin ccTLDs can't possibly be used for anything else than fulfilling people's "misplaced patriotism".
It's not like everybody in the world can't understand the latin alphabet already.
That's only to be expected, after all, we would too fell right at home if asked to type giberish in other alphabets as well.
I for one would certainly have no trouble typing anything you throw at me, irregardless of alphabet.
Chinese, Arabic, Cyrillic, Japanese, you name it, I've mastered them all.
What's more, thanks to my great observation skills, I can guess the general meaning of it simply by staring at said giberish for a minute or so.
Anyways, I hope to have contributed to your in-deep analysis of the situation.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926657</id>
	<title>Re:ICANN has lost it!</title>
	<author>bill\_mcgonigle</author>
	<datestamp>1256929680000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>if you want to go changing that there needs to be a damn good reason</i></p><p>I don't have any first-hand experience, but according to the BBC story when one enters a native-script domain name into one's browser, the domain name is entered normally (for the locale) and then to enter, e.g., ".in", one needs to press a key combination to shift the keyboard into latin-mode, then, enter the two letters, then shift the keyboard back into native mode.</p><p>It's a usability problem.  I sure would be annoyed if<nobr> <wbr></nobr>.com had to be rendered in Kanji on my system.</p></htmltext>
<tokenext>if you want to go changing that there needs to be a damn good reasonI do n't have any first-hand experience , but according to the BBC story when one enters a native-script domain name into one 's browser , the domain name is entered normally ( for the locale ) and then to enter , e.g. , " .in " , one needs to press a key combination to shift the keyboard into latin-mode , then , enter the two letters , then shift the keyboard back into native mode.It 's a usability problem .
I sure would be annoyed if .com had to be rendered in Kanji on my system .</tokentext>
<sentencetext>if you want to go changing that there needs to be a damn good reasonI don't have any first-hand experience, but according to the BBC story when one enters a native-script domain name into one's browser, the domain name is entered normally (for the locale) and then to enter, e.g., ".in", one needs to press a key combination to shift the keyboard into latin-mode, then, enter the two letters, then shift the keyboard back into native mode.It's a usability problem.
I sure would be annoyed if .com had to be rendered in Kanji on my system.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924099</id>
	<title>Re:Phishing aid</title>
	<author>nsayer</author>
	<datestamp>1256919000000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>I think the limitation that nationalized character sets will be restricted to the country TLDs where that language is native is a good first step. Additionally, I believe you're not allowed to use the latin alternative form characters from unicode (like 0xFF20-0xFF5F).</p><p>If you're really paranoid, you could just be extra suspicious of domains that end in two letters (and yes, I am including<nobr> <wbr></nobr>.us), particularly when the 2nd level name is something you recognize, like paypal, ebay, etc. If you're in China, there may indeed be a legitimate paypal.cn, but I suspect it would set off my spidey sense to see a URL like that show up in my e-mail.</p></htmltext>
<tokenext>I think the limitation that nationalized character sets will be restricted to the country TLDs where that language is native is a good first step .
Additionally , I believe you 're not allowed to use the latin alternative form characters from unicode ( like 0xFF20-0xFF5F ) .If you 're really paranoid , you could just be extra suspicious of domains that end in two letters ( and yes , I am including .us ) , particularly when the 2nd level name is something you recognize , like paypal , ebay , etc .
If you 're in China , there may indeed be a legitimate paypal.cn , but I suspect it would set off my spidey sense to see a URL like that show up in my e-mail .</tokentext>
<sentencetext>I think the limitation that nationalized character sets will be restricted to the country TLDs where that language is native is a good first step.
Additionally, I believe you're not allowed to use the latin alternative form characters from unicode (like 0xFF20-0xFF5F).If you're really paranoid, you could just be extra suspicious of domains that end in two letters (and yes, I am including .us), particularly when the 2nd level name is something you recognize, like paypal, ebay, etc.
If you're in China, there may indeed be a legitimate paypal.cn, but I suspect it would set off my spidey sense to see a URL like that show up in my e-mail.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924907</id>
	<title>Re:ICANN has lost it!</title>
	<author>Anonymous</author>
	<datestamp>1256922120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>&gt;  And why do you expect the people that the system is working for to fix it for the people who don't like it?</p><p>Because they might actually take you up on this threat and tell ICANN &amp; the US Government to fuck off. And that's not ideal for anybody, least of all the US.</p></htmltext>
<tokenext>&gt; And why do you expect the people that the system is working for to fix it for the people who do n't like it ? Because they might actually take you up on this threat and tell ICANN &amp; the US Government to fuck off .
And that 's not ideal for anybody , least of all the US .</tokentext>
<sentencetext>&gt;  And why do you expect the people that the system is working for to fix it for the people who don't like it?Because they might actually take you up on this threat and tell ICANN &amp; the US Government to fuck off.
And that's not ideal for anybody, least of all the US.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924573</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924235</id>
	<title>Re:Encoding?</title>
	<author>ObsessiveMathsFreak</author>
	<datestamp>1256919600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Any DNS gurus care to explain why they wouldn't simply use UTF8?</p></div></blockquote><p>Because they know full well that the vast majority of <a href="http://www.joelonsoftware.com/articles/Unicode.html" title="joelonsoftware.com">web developers don't really know what unicode is</a> [joelonsoftware.com] or how it works. Moreover the unicode spec is forever in flux and complete overkill for the international url problem. Lation only urls are a fly, we don't need a bazooka.</p><p>Frankly, the current Punycode based system is truly inspired, giving the best of both worlds. Newer browsers can display and use international urls seamlessly, but older systems need never know they exist. People get what they wanted and the entire system chugs on as before. This is exactly what was needed. A simple and effective system that sits on top of existing infrastructure.</p><p>If only IPv6 has been designed to be this transition friendly.</p></div>
	</htmltext>
<tokenext>Any DNS gurus care to explain why they would n't simply use UTF8 ? Because they know full well that the vast majority of web developers do n't really know what unicode is [ joelonsoftware.com ] or how it works .
Moreover the unicode spec is forever in flux and complete overkill for the international url problem .
Lation only urls are a fly , we do n't need a bazooka.Frankly , the current Punycode based system is truly inspired , giving the best of both worlds .
Newer browsers can display and use international urls seamlessly , but older systems need never know they exist .
People get what they wanted and the entire system chugs on as before .
This is exactly what was needed .
A simple and effective system that sits on top of existing infrastructure.If only IPv6 has been designed to be this transition friendly .</tokentext>
<sentencetext>Any DNS gurus care to explain why they wouldn't simply use UTF8?Because they know full well that the vast majority of web developers don't really know what unicode is [joelonsoftware.com] or how it works.
Moreover the unicode spec is forever in flux and complete overkill for the international url problem.
Lation only urls are a fly, we don't need a bazooka.Frankly, the current Punycode based system is truly inspired, giving the best of both worlds.
Newer browsers can display and use international urls seamlessly, but older systems need never know they exist.
People get what they wanted and the entire system chugs on as before.
This is exactly what was needed.
A simple and effective system that sits on top of existing infrastructure.If only IPv6 has been designed to be this transition friendly.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924099
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924011
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927537
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_56</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923889
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923631
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924815
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925437
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923939
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924523
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926837
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928685
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924161
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925615
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923845
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924583
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923949
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923945
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923703
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924761
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924011
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927455
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925297
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924457
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29929309
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924917
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927305
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924633
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924917
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926455
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29931689
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923891
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924235
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923955
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925599
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923639
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930261
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923967
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924917
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928273
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923631
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930885
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_55</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926657
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924991
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930251
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924333
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925253
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923899
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924539
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924021
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930397
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924457
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927323
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923639
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925787
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924031
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923991
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924457
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927497
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924389
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923845
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29933175
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924161
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924897
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925255
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924657
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923639
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924117
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924961
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927165
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924161
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928427
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927033
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924457
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925813
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924161
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927037
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923859
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926501
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923639
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928357
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924435
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925011
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_58</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924961
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926589
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925857
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924021
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924573
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924907
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_57</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924333
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925869
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924145
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_30_1347216_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924553
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925939
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924151
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923731
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926615
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924961
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926589
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927165
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923713
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924457
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927323
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927497
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29929309
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925813
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924161
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927037
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925615
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924897
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928427
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924011
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927455
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927537
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923989
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924501
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923817
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924539
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925011
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924099
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924553
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925939
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930251
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925437
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927033
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923771
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923745
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924031
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923945
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923899
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923891
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923859
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926501
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928685
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923955
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924235
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924389
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923939
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924523
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926837
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923845
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29933175
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924583
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923695
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924109
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924991
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924917
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29927305
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926455
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29931689
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928273
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925599
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925255
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924633
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923703
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924761
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923631
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924815
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930885
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924579
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923639
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924117
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930261
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925787
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928357
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29928265
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923729
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923617
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924333
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925869
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925253
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923735
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925297
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29926657
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924145
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924021
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924573
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924907
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29930397
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924657
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923967
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923889
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923949
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29925857
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29923991
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924435
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_30_1347216.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_30_1347216.29924577
</commentlist>
</conversation>
