<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_10_14_1219215</id>
	<title>Tim Berners-Lee Is Sorry About the Slashes</title>
	<author>Soulskill</author>
	<datestamp>1255525740000</datestamp>
	<htmltext>Stony Stevenson writes <i>"A light has been shone on one of the great mysteries of the internet. <a href="http://www.australianit.news.com.au/story/0,24897,26209114-15306,00.html">What is the point of the two forward slashes</a> that sit directly in front of the 'www' in every internet website address? The answer, according to Tim Berners-Lee, who had an important role in the creation of the web, is that there isn't one. Berners-Lee revisited that design decision during <a href="http://blip.tv/file/2707910">a recent talk with Paul Mohr</a> of the NY Times when Mohr asked if he would do any differently, given the chance. 'Look at all the paper and trees, he said, that could have been saved if people had not had to <a href="http://bits.blogs.nytimes.com/2009/10/12/the-webs-inventor-regrets-one-small-thing/">write or type out those slashes on paper</a> over the years &mdash; not to mention the human labor and time spent typing those two keystrokes countless millions of times in browser address boxes.'"</i></htmltext>
<tokenext>Stony Stevenson writes " A light has been shone on one of the great mysteries of the internet .
What is the point of the two forward slashes that sit directly in front of the 'www ' in every internet website address ?
The answer , according to Tim Berners-Lee , who had an important role in the creation of the web , is that there is n't one .
Berners-Lee revisited that design decision during a recent talk with Paul Mohr of the NY Times when Mohr asked if he would do any differently , given the chance .
'Look at all the paper and trees , he said , that could have been saved if people had not had to write or type out those slashes on paper over the years    not to mention the human labor and time spent typing those two keystrokes countless millions of times in browser address boxes .
' "</tokentext>
<sentencetext>Stony Stevenson writes "A light has been shone on one of the great mysteries of the internet.
What is the point of the two forward slashes that sit directly in front of the 'www' in every internet website address?
The answer, according to Tim Berners-Lee, who had an important role in the creation of the web, is that there isn't one.
Berners-Lee revisited that design decision during a recent talk with Paul Mohr of the NY Times when Mohr asked if he would do any differently, given the chance.
'Look at all the paper and trees, he said, that could have been saved if people had not had to write or type out those slashes on paper over the years — not to mention the human labor and time spent typing those two keystrokes countless millions of times in browser address boxes.
'"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589</id>
	<title>So Who's Apologizing for 'ttp' ?</title>
	<author>Anonymous</author>
	<datestamp>1255530180000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>Doesn't the same logic hold for the person that decided it should be 'http' for hypertext transfer protocol and not just simply 'h'?  Yes, http is more descriptive <i>but</i> unnecessary.  Had another protocol came along starting with 'h' they could have opted for another letter or -- if they were all taken -- became a two letter protocol.  I mean, if we're going to get into pedantic apologies for lack of brevity I would assume the three unnecessary letters in http are a greater crime than the double slashes, right?  Of course, rarely do I find myself typing anything other than the domain and TLD (i.e. slashdot.org, mail.google.com, woot.com) so this has really become a non-issue.</htmltext>
<tokenext>Does n't the same logic hold for the person that decided it should be 'http ' for hypertext transfer protocol and not just simply 'h ' ?
Yes , http is more descriptive but unnecessary .
Had another protocol came along starting with 'h ' they could have opted for another letter or -- if they were all taken -- became a two letter protocol .
I mean , if we 're going to get into pedantic apologies for lack of brevity I would assume the three unnecessary letters in http are a greater crime than the double slashes , right ?
Of course , rarely do I find myself typing anything other than the domain and TLD ( i.e .
slashdot.org , mail.google.com , woot.com ) so this has really become a non-issue .</tokentext>
<sentencetext>Doesn't the same logic hold for the person that decided it should be 'http' for hypertext transfer protocol and not just simply 'h'?
Yes, http is more descriptive but unnecessary.
Had another protocol came along starting with 'h' they could have opted for another letter or -- if they were all taken -- became a two letter protocol.
I mean, if we're going to get into pedantic apologies for lack of brevity I would assume the three unnecessary letters in http are a greater crime than the double slashes, right?
Of course, rarely do I find myself typing anything other than the domain and TLD (i.e.
slashdot.org, mail.google.com, woot.com) so this has really become a non-issue.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743505</id>
	<title>It's time to...</title>
	<author>Anonymous</author>
	<datestamp>1255529580000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>... get your pitchforks and torches!  We've finally found the guy responsible for those satanic slashes!!!</htmltext>
<tokenext>... get your pitchforks and torches !
We 've finally found the guy responsible for those satanic slashes ! !
!</tokentext>
<sentencetext>... get your pitchforks and torches!
We've finally found the guy responsible for those satanic slashes!!
!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743585</id>
	<title>Time wasted explaining a slash vs. backslash</title>
	<author>Anonymous</author>
	<datestamp>1255530120000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Not to mention all the time wasted trying to explain to people the difference between a slash and a backslash.</p></htmltext>
<tokenext>Not to mention all the time wasted trying to explain to people the difference between a slash and a backslash .</tokentext>
<sentencetext>Not to mention all the time wasted trying to explain to people the difference between a slash and a backslash.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29754643</id>
	<title>Re:backslashdot</title>
	<author>sw155kn1f3</author>
	<datestamp>1255601580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's very hard to be a smartass - it's a big shame when you shit yourself as you did.<br>DNS server is perfectly valid sentense. Domain Name System server.</p></htmltext>
<tokenext>It 's very hard to be a smartass - it 's a big shame when you shit yourself as you did.DNS server is perfectly valid sentense .
Domain Name System server .</tokentext>
<sentencetext>It's very hard to be a smartass - it's a big shame when you shit yourself as you did.DNS server is perfectly valid sentense.
Domain Name System server.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745303</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745865</id>
	<title>They Do Serve a Purpose</title>
	<author>trib4lmaniac</author>
	<datestamp>1255539720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Life any good<nobr> <wbr></nobr>/.er, I have not RTFA; but I was very surprised to see this on the front page. Tim's reasoning for the double-slash is readily available information in his very own <a href="http://www.w3.org/People/Berners-Lee/FAQ.html#etc" title="w3.org" rel="nofollow">FAQ</a> [w3.org].<blockquote><div><p>I have to say that now I regret that the syntax is so clumsy. I would like <a href="http://www.example.com/foo/bar/baz" title="example.com" rel="nofollow">http://www.example.com/foo/bar/baz</a> [example.com] to be just written <a href="http:com/example/foo/bar/baz" title="com" rel="nofollow">http:com/example/foo/bar/baz</a> [com] where the client would figure out that www.example.com existed and was the server to contact. But it is too late now. It turned out the shorthand "//www.example.com/foo/bar/baz" is rarely used and so we could dispense with the "//".</p></div></blockquote><p>

I would also like to add that protocol relative URI <em>are</em> useful. I'm sure some of you are familar with the <a href="http://www.google.com/support/googleanalytics/bin/answer.py?answer=55488&amp;utm\_source=DiscoverList&amp;utm\_medium=et&amp;utm\_campaign=en\_us&amp;hl=en" title="google.com" rel="nofollow">hideous JavaScript</a> [google.com] Google recommend using for embedding Analytics into your HTML. It would make much more sense to source the file with a protocol-relative URI.</p></div>
	</htmltext>
<tokenext>Life any good /.er , I have not RTFA ; but I was very surprised to see this on the front page .
Tim 's reasoning for the double-slash is readily available information in his very own FAQ [ w3.org ] .I have to say that now I regret that the syntax is so clumsy .
I would like http : //www.example.com/foo/bar/baz [ example.com ] to be just written http : com/example/foo/bar/baz [ com ] where the client would figure out that www.example.com existed and was the server to contact .
But it is too late now .
It turned out the shorthand " //www.example.com/foo/bar/baz " is rarely used and so we could dispense with the " // " .
I would also like to add that protocol relative URI are useful .
I 'm sure some of you are familar with the hideous JavaScript [ google.com ] Google recommend using for embedding Analytics into your HTML .
It would make much more sense to source the file with a protocol-relative URI .</tokentext>
<sentencetext>Life any good /.er, I have not RTFA; but I was very surprised to see this on the front page.
Tim's reasoning for the double-slash is readily available information in his very own FAQ [w3.org].I have to say that now I regret that the syntax is so clumsy.
I would like http://www.example.com/foo/bar/baz [example.com] to be just written http:com/example/foo/bar/baz [com] where the client would figure out that www.example.com existed and was the server to contact.
But it is too late now.
It turned out the shorthand "//www.example.com/foo/bar/baz" is rarely used and so we could dispense with the "//".
I would also like to add that protocol relative URI are useful.
I'm sure some of you are familar with the hideous JavaScript [google.com] Google recommend using for embedding Analytics into your HTML.
It would make much more sense to source the file with a protocol-relative URI.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744723</id>
	<title>Re:I thought there was a point to the two slashes</title>
	<author>Anonymous</author>
	<datestamp>1255535100000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>Back in the '80s, the double slashes were invented to indicate that the following token was a machine name and not a local directory or local mount-point.  The first time I met the double slashes was on an Apollo workstation, which ran Domain, one of the first OSes where you could access remote files and local files without special software--it was built into the OS.  At the time, on UNIX, you had to use commands like FTP, or RCP.  On Domain, you could also make a soft symlink on your local computer that pointed to another server, so you could move directories around the network and the local programs didn't need to change.  (I would not be surprised if the double slashes came from DEC VMS, but I don't know.)</p><p>Compare syntaxes:<br>cp<nobr> <wbr></nobr>//machine1/dir/dir/filename<nobr> <wbr></nobr>//machine2/dir/dir   -- copy a file from machine1 to machine 2<br>cp<nobr> <wbr></nobr>/dir/dir/filename<nobr> <wbr></nobr>//machine2/dir/dir -- copy a file from the current machine to machine 2</p><p>In RCP the syntax was rather more cumbersome:<br>rcp user@machine1:/dir/dir/filename<nobr> <wbr></nobr>/dir/dir/filename -- copy a file from machine1 to my local machine<br>In RCP, the assumption is that a path name is a "remote" path if it contains the character ':'.</p><p>Windows NT and Novell Netware both used double slashes to denote machine names, although Novell's implementation wasn't originally transparent to application programs.  Because of the history of PC-DOS, they used backslashes instead of forward slashes.</p></htmltext>
<tokenext>Back in the '80s , the double slashes were invented to indicate that the following token was a machine name and not a local directory or local mount-point .
The first time I met the double slashes was on an Apollo workstation , which ran Domain , one of the first OSes where you could access remote files and local files without special software--it was built into the OS .
At the time , on UNIX , you had to use commands like FTP , or RCP .
On Domain , you could also make a soft symlink on your local computer that pointed to another server , so you could move directories around the network and the local programs did n't need to change .
( I would not be surprised if the double slashes came from DEC VMS , but I do n't know .
) Compare syntaxes : cp //machine1/dir/dir/filename //machine2/dir/dir -- copy a file from machine1 to machine 2cp /dir/dir/filename //machine2/dir/dir -- copy a file from the current machine to machine 2In RCP the syntax was rather more cumbersome : rcp user @ machine1 : /dir/dir/filename /dir/dir/filename -- copy a file from machine1 to my local machineIn RCP , the assumption is that a path name is a " remote " path if it contains the character ' : '.Windows NT and Novell Netware both used double slashes to denote machine names , although Novell 's implementation was n't originally transparent to application programs .
Because of the history of PC-DOS , they used backslashes instead of forward slashes .</tokentext>
<sentencetext>Back in the '80s, the double slashes were invented to indicate that the following token was a machine name and not a local directory or local mount-point.
The first time I met the double slashes was on an Apollo workstation, which ran Domain, one of the first OSes where you could access remote files and local files without special software--it was built into the OS.
At the time, on UNIX, you had to use commands like FTP, or RCP.
On Domain, you could also make a soft symlink on your local computer that pointed to another server, so you could move directories around the network and the local programs didn't need to change.
(I would not be surprised if the double slashes came from DEC VMS, but I don't know.
)Compare syntaxes:cp //machine1/dir/dir/filename //machine2/dir/dir   -- copy a file from machine1 to machine 2cp /dir/dir/filename //machine2/dir/dir -- copy a file from the current machine to machine 2In RCP the syntax was rather more cumbersome:rcp user@machine1:/dir/dir/filename /dir/dir/filename -- copy a file from machine1 to my local machineIn RCP, the assumption is that a path name is a "remote" path if it contains the character ':'.Windows NT and Novell Netware both used double slashes to denote machine names, although Novell's implementation wasn't originally transparent to application programs.
Because of the history of PC-DOS, they used backslashes instead of forward slashes.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743675</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744519</id>
	<title>I think he was right the first time</title>
	<author>argent</author>
	<datestamp>1255534320000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>OK, maybe it could have been reduced to one slash, since there's no<nobr> <wbr></nobr>:/ smiley elsewhere in the URL pattern, but you need to be able to distinguish relative URLs from absolute ones. Without some unique token sequence that was guaranteed not to occur elsewhere in a URI you're going to run into problems. Start removing components from a fully specified URI and see how quickly you run into ambiguities:</p><p>method://username:password@host:port/paths/terminal?token=value&amp;token=value</p><p>The reasons for the<nobr> <wbr></nobr>// convention for the "super root" in networks like OpenNet and FutureNet, that he was copying, are still valid in URIs. You need something that's easily parsed by computers, and easily recognized by humans. When I first saw the syntax I was all "slash slash whiskey tango foxtrot?", but after using it for a while I was convinced that I was wrong and he was right, and even if he's forgotten why... I still think he was right the first time.</p></htmltext>
<tokenext>OK , maybe it could have been reduced to one slash , since there 's no : / smiley elsewhere in the URL pattern , but you need to be able to distinguish relative URLs from absolute ones .
Without some unique token sequence that was guaranteed not to occur elsewhere in a URI you 're going to run into problems .
Start removing components from a fully specified URI and see how quickly you run into ambiguities : method : //username : password @ host : port/paths/terminal ? token = value&amp;token = valueThe reasons for the // convention for the " super root " in networks like OpenNet and FutureNet , that he was copying , are still valid in URIs .
You need something that 's easily parsed by computers , and easily recognized by humans .
When I first saw the syntax I was all " slash slash whiskey tango foxtrot ?
" , but after using it for a while I was convinced that I was wrong and he was right , and even if he 's forgotten why... I still think he was right the first time .</tokentext>
<sentencetext>OK, maybe it could have been reduced to one slash, since there's no :/ smiley elsewhere in the URL pattern, but you need to be able to distinguish relative URLs from absolute ones.
Without some unique token sequence that was guaranteed not to occur elsewhere in a URI you're going to run into problems.
Start removing components from a fully specified URI and see how quickly you run into ambiguities:method://username:password@host:port/paths/terminal?token=value&amp;token=valueThe reasons for the // convention for the "super root" in networks like OpenNet and FutureNet, that he was copying, are still valid in URIs.
You need something that's easily parsed by computers, and easily recognized by humans.
When I first saw the syntax I was all "slash slash whiskey tango foxtrot?
", but after using it for a while I was convinced that I was wrong and he was right, and even if he's forgotten why... I still think he was right the first time.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744747</id>
	<title>But what about netloc absolutes?</title>
	<author>Whispers\_in\_the\_dark</author>
	<datestamp>1255535220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Okay, so noone uses them, but <a href="http://www.ietf.org/rfc/rfc2396.txt" title="ietf.org">TBL's own RFC</a> [ietf.org] in section C.1 demonstrates the use of an initial double-forward-slash meaning change the netloc without changing the protocol.  This could be useful if you're dealing with resources that have the same mapping on multiple protocols (like http and https).

I know it's a corner case, but it is still technically a documented use case...</htmltext>
<tokenext>Okay , so noone uses them , but TBL 's own RFC [ ietf.org ] in section C.1 demonstrates the use of an initial double-forward-slash meaning change the netloc without changing the protocol .
This could be useful if you 're dealing with resources that have the same mapping on multiple protocols ( like http and https ) .
I know it 's a corner case , but it is still technically a documented use case.. .</tokentext>
<sentencetext>Okay, so noone uses them, but TBL's own RFC [ietf.org] in section C.1 demonstrates the use of an initial double-forward-slash meaning change the netloc without changing the protocol.
This could be useful if you're dealing with resources that have the same mapping on multiple protocols (like http and https).
I know it's a corner case, but it is still technically a documented use case...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744045</id>
	<title>Re:yes</title>
	<author>Anonymous</author>
	<datestamp>1255532280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Sir! In order to preserve your sanity, you have concealed from your friends and colleagues your familiarity with the electronical arts.</p><p>This was no modest undertaking, yet you have deceived without effort all who asked "Do I need to type in this bit?" and emerged triumphant and untroubled by their eternal protocolic queries.</p><p>Your humble servant requests that he become your disciple and learn the Way of the Unknown URI Syntax, and tear from himself the burdened title of free support guy.</p></htmltext>
<tokenext>Sir !
In order to preserve your sanity , you have concealed from your friends and colleagues your familiarity with the electronical arts.This was no modest undertaking , yet you have deceived without effort all who asked " Do I need to type in this bit ?
" and emerged triumphant and untroubled by their eternal protocolic queries.Your humble servant requests that he become your disciple and learn the Way of the Unknown URI Syntax , and tear from himself the burdened title of free support guy .</tokentext>
<sentencetext>Sir!
In order to preserve your sanity, you have concealed from your friends and colleagues your familiarity with the electronical arts.This was no modest undertaking, yet you have deceived without effort all who asked "Do I need to type in this bit?
" and emerged triumphant and untroubled by their eternal protocolic queries.Your humble servant requests that he become your disciple and learn the Way of the Unknown URI Syntax, and tear from himself the burdened title of free support guy.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747667</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>RealGrouchy</author>
	<datestamp>1255547760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>In my mother tongue, the 'w' is pronounced as [wey].</p></div><p>Must get tiresome to pronounce those square brackets all the time.</p><p>- RG&gt;</p></div>
	</htmltext>
<tokenext>In my mother tongue , the 'w ' is pronounced as [ wey ] .Must get tiresome to pronounce those square brackets all the time.- RG &gt;</tokentext>
<sentencetext>In my mother tongue, the 'w' is pronounced as [wey].Must get tiresome to pronounce those square brackets all the time.- RG&gt;
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744547</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744757</id>
	<title>Re:Theres one technical point</title>
	<author>Anonymous</author>
	<datestamp>1255535220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The prefix of www is only a required part of the hostname in a URL when either the only hostname of the box starts with www or if the web server is configured to only respond to requests when the hostname starts with www.</p><p>There is nothing at all magical about www in a hostname.  You could easily setup a web server that only responds to a hostname starting with ftp or gopher.</p><p>On the flip side, if a server is not configured to respond to a hostname starting with www, it won't ever work.</p></htmltext>
<tokenext>The prefix of www is only a required part of the hostname in a URL when either the only hostname of the box starts with www or if the web server is configured to only respond to requests when the hostname starts with www.There is nothing at all magical about www in a hostname .
You could easily setup a web server that only responds to a hostname starting with ftp or gopher.On the flip side , if a server is not configured to respond to a hostname starting with www , it wo n't ever work .</tokentext>
<sentencetext>The prefix of www is only a required part of the hostname in a URL when either the only hostname of the box starts with www or if the web server is configured to only respond to requests when the hostname starts with www.There is nothing at all magical about www in a hostname.
You could easily setup a web server that only responds to a hostname starting with ftp or gopher.On the flip side, if a server is not configured to respond to a hostname starting with www, it won't ever work.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743775</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746993</id>
	<title>Re:Now explain triple-slashes</title>
	<author>Anonymous</author>
	<datestamp>1255544820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>And if the path is an UNC one on windows, you get 5. Almost like the razorblades from wilkinsons and gillette!</p></htmltext>
<tokenext>And if the path is an UNC one on windows , you get 5 .
Almost like the razorblades from wilkinsons and gillette !</tokentext>
<sentencetext>And if the path is an UNC one on windows, you get 5.
Almost like the razorblades from wilkinsons and gillette!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749439</id>
	<title>Re:So Who's Apologizing for 'ttp' ?</title>
	<author>clone53421</author>
	<datestamp>1255512180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>In the same way that http conflicts with https. I guess what I'm saying is, in no way at all.</p></htmltext>
<tokenext>In the same way that http conflicts with https .
I guess what I 'm saying is , in no way at all .</tokentext>
<sentencetext>In the same way that http conflicts with https.
I guess what I'm saying is, in no way at all.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744435</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743771</id>
	<title>Re:to think ..</title>
	<author>aicrules</author>
	<datestamp>1255530960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>colondot</p></div><p>You should get that looked at.</p></div>
	</htmltext>
<tokenext>colondotYou should get that looked at .</tokentext>
<sentencetext>colondotYou should get that looked at.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745591</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>AP31R0N</author>
	<datestamp>1255538640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>i always liked "dub dub dub".  i suppose "sextuple-u" would do it too.<br>\_\_</p><p>Having a mark for which protocol to use is useful, but i think it might be time to review how we do it.  Web browsers could safely assume port 80 (most already do).  Webmasters should support that.  If i need to use the ftp, i would know to type ftp.</p><p>i'd much rather dispose of TLDs that allow crap like WhiteHouse.com.  If we are doing to have TLDs, can we at least put them in order?  com.Hotmail/userName/page.html</p><p>i'd rather see people CapitalizeTheFirstLetterInAWebSAddress because itseasiertoread.</p></htmltext>
<tokenext>i always liked " dub dub dub " .
i suppose " sextuple-u " would do it too. \ _ \ _Having a mark for which protocol to use is useful , but i think it might be time to review how we do it .
Web browsers could safely assume port 80 ( most already do ) .
Webmasters should support that .
If i need to use the ftp , i would know to type ftp.i 'd much rather dispose of TLDs that allow crap like WhiteHouse.com .
If we are doing to have TLDs , can we at least put them in order ?
com.Hotmail/userName/page.htmli 'd rather see people CapitalizeTheFirstLetterInAWebSAddress because itseasiertoread .</tokentext>
<sentencetext>i always liked "dub dub dub".
i suppose "sextuple-u" would do it too.\_\_Having a mark for which protocol to use is useful, but i think it might be time to review how we do it.
Web browsers could safely assume port 80 (most already do).
Webmasters should support that.
If i need to use the ftp, i would know to type ftp.i'd much rather dispose of TLDs that allow crap like WhiteHouse.com.
If we are doing to have TLDs, can we at least put them in order?
com.Hotmail/userName/page.htmli'd rather see people CapitalizeTheFirstLetterInAWebSAddress because itseasiertoread.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748827</id>
	<title>Forget the slashes</title>
	<author>bruhinb</author>
	<datestamp>1255552560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>We could very easily overcome the tragedy of the slashes if only we would agree to lose the totally usless www. that most websites still advertise. What's wrong with encouraging users to enter a simple <a href="http://example.com/" title="example.com" rel="nofollow">http://example.com/</a> [example.com] rather than insisting on <a href="http://www.example.com/" title="example.com" rel="nofollow">http://www.example.com/</a> [example.com] ?</htmltext>
<tokenext>We could very easily overcome the tragedy of the slashes if only we would agree to lose the totally usless www .
that most websites still advertise .
What 's wrong with encouraging users to enter a simple http : //example.com/ [ example.com ] rather than insisting on http : //www.example.com/ [ example.com ] ?</tokentext>
<sentencetext>We could very easily overcome the tragedy of the slashes if only we would agree to lose the totally usless www.
that most websites still advertise.
What's wrong with encouraging users to enter a simple http://example.com/ [example.com] rather than insisting on http://www.example.com/ [example.com] ?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743873</id>
	<title>Re:backslashdot</title>
	<author>Anonymous</author>
	<datestamp>1255531500000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>I'm pretty sure they are sorry about that. I can't remember who it was, Paul Allen maybe? But one of the early MS programmers said once that he hugely regretted using / for switches in DOS 1.0. When they added directories in a later version, / was already taken so they had to use \ instead.</p></htmltext>
<tokenext>I 'm pretty sure they are sorry about that .
I ca n't remember who it was , Paul Allen maybe ?
But one of the early MS programmers said once that he hugely regretted using / for switches in DOS 1.0 .
When they added directories in a later version , / was already taken so they had to use \ instead .</tokentext>
<sentencetext>I'm pretty sure they are sorry about that.
I can't remember who it was, Paul Allen maybe?
But one of the early MS programmers said once that he hugely regretted using / for switches in DOS 1.0.
When they added directories in a later version, / was already taken so they had to use \ instead.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29755017</id>
	<title>Erm...</title>
	<author>TheReal\_sabret00the</author>
	<datestamp>1255607220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I've never minded the slashes and to be fair <a href="http:slashdot.com" title="slashdot.com" rel="nofollow">http:slashdot.com</a> [slashdot.com] just isn't as charismatic.

however, that said. and this probably extends beyond his scope. I've always thought that the method in which URI's were written was the wrong way round. I'd like to see it all changed so something along the lines of:

<a href="http://com.slashdot.tech/story/xx/xx/xx/xxx.html" title="slashdot.tech" rel="nofollow">http://com.slashdot.tech/story/xx/xx/xx/xxx.html</a> [slashdot.tech]</htmltext>
<tokenext>I 've never minded the slashes and to be fair http : slashdot.com [ slashdot.com ] just is n't as charismatic .
however , that said .
and this probably extends beyond his scope .
I 've always thought that the method in which URI 's were written was the wrong way round .
I 'd like to see it all changed so something along the lines of : http : //com.slashdot.tech/story/xx/xx/xx/xxx.html [ slashdot.tech ]</tokentext>
<sentencetext>I've never minded the slashes and to be fair http:slashdot.com [slashdot.com] just isn't as charismatic.
however, that said.
and this probably extends beyond his scope.
I've always thought that the method in which URI's were written was the wrong way round.
I'd like to see it all changed so something along the lines of:

http://com.slashdot.tech/story/xx/xx/xx/xxx.html [slashdot.tech]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752431</id>
	<title>Re:to think ..</title>
	<author>barath\_s</author>
	<datestamp>1255530960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If he had foreseen the commercial impact, he would have used $$ instead of<nobr> <wbr></nobr>//
Though as a Brit working in Euroland, he could have supported other protocols such as &pound;&pound; or &euro;&euro;</htmltext>
<tokenext>If he had foreseen the commercial impact , he would have used $ $ instead of // Though as a Brit working in Euroland , he could have supported other protocols such as     or      </tokentext>
<sentencetext>If he had foreseen the commercial impact, he would have used $$ instead of //
Though as a Brit working in Euroland, he could have supported other protocols such as ££ or €€</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745169</id>
	<title>Re:From the year 2022</title>
	<author>Attila Dimedici</author>
	<datestamp>1255536900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>The problem with letting people have what they want is that the majority of people don't understand why things are the way they are.  Tim made the right choice,
he just feels that it is wrong now because he's had to hear people complain about it for the past 15-20 years. But when it comes down to it you need some parts of a URL to indicate what something is.</p></div><p>I didn't read the article and I haven't given this a lot of thought, so I am not sure I am interpreting this correctly. It is possible (likely?) that a better choice than the "://" could have been made. However, if he had made that choice, people would still be complaining about it today with a similar degree of vehemence. As several people pointed out having some unique identifier there technically simplified many tasks involving the Web, so without something there would be other problems.</p></div>
	</htmltext>
<tokenext>The problem with letting people have what they want is that the majority of people do n't understand why things are the way they are .
Tim made the right choice , he just feels that it is wrong now because he 's had to hear people complain about it for the past 15-20 years .
But when it comes down to it you need some parts of a URL to indicate what something is.I did n't read the article and I have n't given this a lot of thought , so I am not sure I am interpreting this correctly .
It is possible ( likely ?
) that a better choice than the " : // " could have been made .
However , if he had made that choice , people would still be complaining about it today with a similar degree of vehemence .
As several people pointed out having some unique identifier there technically simplified many tasks involving the Web , so without something there would be other problems .</tokentext>
<sentencetext>The problem with letting people have what they want is that the majority of people don't understand why things are the way they are.
Tim made the right choice,
he just feels that it is wrong now because he's had to hear people complain about it for the past 15-20 years.
But when it comes down to it you need some parts of a URL to indicate what something is.I didn't read the article and I haven't given this a lot of thought, so I am not sure I am interpreting this correctly.
It is possible (likely?
) that a better choice than the "://" could have been made.
However, if he had made that choice, people would still be complaining about it today with a similar degree of vehemence.
As several people pointed out having some unique identifier there technically simplified many tasks involving the Web, so without something there would be other problems.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743467</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747707</id>
	<title>Re:So Who's Apologizing for 'ttp' ?</title>
	<author>Sam the Nemesis</author>
	<datestamp>1255547880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Of course, rarely do I find myself typing anything other than the domain and TLD (i.e. slashdot.org, mail.google.com, woot.com) so this has really become a non-issue.</p></div><p>Better still - I just type sitename and press Ctrl+Enter and browser automatically adds "www." and ".com". For ".org", I just need to press Ctrl+Shift+Enter. It is a great help, and works in Firefox, Chrome and IE, at least.</p></div>
	</htmltext>
<tokenext>Of course , rarely do I find myself typing anything other than the domain and TLD ( i.e .
slashdot.org , mail.google.com , woot.com ) so this has really become a non-issue.Better still - I just type sitename and press Ctrl + Enter and browser automatically adds " www .
" and " .com " .
For " .org " , I just need to press Ctrl + Shift + Enter .
It is a great help , and works in Firefox , Chrome and IE , at least .</tokentext>
<sentencetext>Of course, rarely do I find myself typing anything other than the domain and TLD (i.e.
slashdot.org, mail.google.com, woot.com) so this has really become a non-issue.Better still - I just type sitename and press Ctrl+Enter and browser automatically adds "www.
" and ".com".
For ".org", I just need to press Ctrl+Shift+Enter.
It is a great help, and works in Firefox, Chrome and IE, at least.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746773</id>
	<title>Re:yes</title>
	<author>NotOddManOut</author>
	<datestamp>1255543740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>LOL.

How about just typing the hostname and pressing -enter?  Most browsers today have this and other keystroke time-savers built in.</htmltext>
<tokenext>LOL .
How about just typing the hostname and pressing -enter ?
Most browsers today have this and other keystroke time-savers built in .</tokentext>
<sentencetext>LOL.
How about just typing the hostname and pressing -enter?
Most browsers today have this and other keystroke time-savers built in.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743649</id>
	<title>Stupid story</title>
	<author>mgessner</author>
	<datestamp>1255530480000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>It doesn't matter a rat's ass.</p><p>Pick up any browser, type in www.yahoo.com.</p><p>Does it get there?  Sure!</p><p>If you're worried about all the time spent typing, store the stupid text in a document that you cut and paste!  (Yes, this will take more time, showing even more how stupid this whole thing is.)</p><p>Store a stupid bookmark.  Then you only have to type <a href="https://blah.blah.blah/" title="blah.blah">https://blah.blah.blah/</a> [blah.blah] one time.</p><p>Get a life.</p></htmltext>
<tokenext>It does n't matter a rat 's ass.Pick up any browser , type in www.yahoo.com.Does it get there ?
Sure ! If you 're worried about all the time spent typing , store the stupid text in a document that you cut and paste !
( Yes , this will take more time , showing even more how stupid this whole thing is .
) Store a stupid bookmark .
Then you only have to type https : //blah.blah.blah/ [ blah.blah ] one time.Get a life .</tokentext>
<sentencetext>It doesn't matter a rat's ass.Pick up any browser, type in www.yahoo.com.Does it get there?
Sure!If you're worried about all the time spent typing, store the stupid text in a document that you cut and paste!
(Yes, this will take more time, showing even more how stupid this whole thing is.
)Store a stupid bookmark.
Then you only have to type https://blah.blah.blah/ [blah.blah] one time.Get a life.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203</id>
	<title>Re:Now explain triple-slashes</title>
	<author>atomicstrawberry</author>
	<datestamp>1255533000000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>The structure of a URL is:</p><p>protocol://domain/path</p><p>When you use the 'file' protocol, there is no domain, there is only a path. Thus the domain part of the URL is omitted and you get a triple-slash.</p></htmltext>
<tokenext>The structure of a URL is : protocol : //domain/pathWhen you use the 'file ' protocol , there is no domain , there is only a path .
Thus the domain part of the URL is omitted and you get a triple-slash .</tokentext>
<sentencetext>The structure of a URL is:protocol://domain/pathWhen you use the 'file' protocol, there is no domain, there is only a path.
Thus the domain part of the URL is omitted and you get a triple-slash.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557</id>
	<title>pronouncing www is a lot more of a problem</title>
	<author>Anonymous</author>
	<datestamp>1255529880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Most people never pronounced the<nobr> <wbr></nobr>//. They would just give an address as www.google.com where the first 3 letters take more time to spell than all the rest.</p></htmltext>
<tokenext>Most people never pronounced the // .
They would just give an address as www.google.com where the first 3 letters take more time to spell than all the rest .</tokentext>
<sentencetext>Most people never pronounced the //.
They would just give an address as www.google.com where the first 3 letters take more time to spell than all the rest.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29759735</id>
	<title>Er, me for one......</title>
	<author>Anonymous</author>
	<datestamp>1255631820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I actually still type in http://www. whenever I go to a site. When I started using it back in '94 that was required, and now it's still needed if you want to use a non-standard port on some browsers. I just found it easier to keep using http://www, because then I don't have to worry about whatever browser I'm using misinterpreting it, or misconfigured DNS sending me to the wrong/no site.</p><p>Now get off my lawn......</p></htmltext>
<tokenext>I actually still type in http : //www .
whenever I go to a site .
When I started using it back in '94 that was required , and now it 's still needed if you want to use a non-standard port on some browsers .
I just found it easier to keep using http : //www , because then I do n't have to worry about whatever browser I 'm using misinterpreting it , or misconfigured DNS sending me to the wrong/no site.Now get off my lawn..... .</tokentext>
<sentencetext>I actually still type in http://www.
whenever I go to a site.
When I started using it back in '94 that was required, and now it's still needed if you want to use a non-standard port on some browsers.
I just found it easier to keep using http://www, because then I don't have to worry about whatever browser I'm using misinterpreting it, or misconfigured DNS sending me to the wrong/no site.Now get off my lawn......</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743837</id>
	<title>Am I missing something here?</title>
	<author>Anonymous</author>
	<datestamp>1255531380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>So the author of TFA knows nothing about web addresses, or else he would not pretend that they all start with "www", a subdomain that has been totally superfluous ever since servers learned to redirect requests by protocol. But Tim Berners-Lee of all people? How could he not remember that the two slashes stand for root, and that omitting them would make the address relative? Not to mention that a colon is also used between username and password before the hostname, and before hostname and port number, so the slashes cannot be omitted without making the whole syntax ambiguous. But maybe I'm just humorless.</p></htmltext>
<tokenext>So the author of TFA knows nothing about web addresses , or else he would not pretend that they all start with " www " , a subdomain that has been totally superfluous ever since servers learned to redirect requests by protocol .
But Tim Berners-Lee of all people ?
How could he not remember that the two slashes stand for root , and that omitting them would make the address relative ?
Not to mention that a colon is also used between username and password before the hostname , and before hostname and port number , so the slashes can not be omitted without making the whole syntax ambiguous .
But maybe I 'm just humorless .</tokentext>
<sentencetext>So the author of TFA knows nothing about web addresses, or else he would not pretend that they all start with "www", a subdomain that has been totally superfluous ever since servers learned to redirect requests by protocol.
But Tim Berners-Lee of all people?
How could he not remember that the two slashes stand for root, and that omitting them would make the address relative?
Not to mention that a colon is also used between username and password before the hostname, and before hostname and port number, so the slashes cannot be omitted without making the whole syntax ambiguous.
But maybe I'm just humorless.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749273</id>
	<title>Think of the children</title>
	<author>Shabazz Rabbinowitz</author>
	<datestamp>1255511520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Had he not used them, a whole lot of O.J. Simpson web site jokes would not have possible.</htmltext>
<tokenext>Had he not used them , a whole lot of O.J .
Simpson web site jokes would not have possible .</tokentext>
<sentencetext>Had he not used them, a whole lot of O.J.
Simpson web site jokes would not have possible.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748595</id>
	<title>Re:DNS</title>
	<author>jez9999</author>
	<datestamp>1255551720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>The TLD is essentially totally insignificant, and would have to be typed every single time if the order were reversed.</i></p><p>Only if you were using an autocompleter that relied on stored URLs beginning with what you typed, rather than any part of the URL (and even the page title) containing what you typed - a la Firefox 3.</p></htmltext>
<tokenext>The TLD is essentially totally insignificant , and would have to be typed every single time if the order were reversed.Only if you were using an autocompleter that relied on stored URLs beginning with what you typed , rather than any part of the URL ( and even the page title ) containing what you typed - a la Firefox 3 .</tokentext>
<sentencetext>The TLD is essentially totally insignificant, and would have to be typed every single time if the order were reversed.Only if you were using an autocompleter that relied on stored URLs beginning with what you typed, rather than any part of the URL (and even the page title) containing what you typed - a la Firefox 3.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745015</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825</id>
	<title>Now explain triple-slashes</title>
	<author>objekt</author>
	<datestamp>1255531260000</datestamp>
	<modclass>None</modclass>
	<modscore>2</modscore>
	<htmltext><p>like when I open a local file in my browser I get "file:///"</p></htmltext>
<tokenext>like when I open a local file in my browser I get " file : /// "</tokentext>
<sentencetext>like when I open a local file in my browser I get "file:///"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745833</id>
	<title>10 Other uses for a /</title>
	<author>dharte</author>
	<datestamp>1255539600000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>The BBC have put together a list of 10 other uses for a<nobr> <wbr></nobr>/: <a href="http://news.bbc.co.uk/1/hi/magazine/8306515.stm" title="bbc.co.uk" rel="nofollow">http://news.bbc.co.uk/1/hi/magazine/8306515.stm</a> [bbc.co.uk]</htmltext>
<tokenext>The BBC have put together a list of 10 other uses for a / : http : //news.bbc.co.uk/1/hi/magazine/8306515.stm [ bbc.co.uk ]</tokentext>
<sentencetext>The BBC have put together a list of 10 other uses for a /: http://news.bbc.co.uk/1/hi/magazine/8306515.stm [bbc.co.uk]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743915</id>
	<title>I don't believe him</title>
	<author>JohnFen</author>
	<datestamp>1255531740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>With all due respect to Sir Berners-Lee, I think he's fibbing. If, indeed, it "seemed like a good idea at the time," then he <i>had</i> some purpose in mind when he came up with them. I don't for a minute believe that he just randomly decided to drop some punctuation in because, hell, why not?</p><p>I think his purpose might have been embarrassingly dumb and he's covering it up.</p></htmltext>
<tokenext>With all due respect to Sir Berners-Lee , I think he 's fibbing .
If , indeed , it " seemed like a good idea at the time , " then he had some purpose in mind when he came up with them .
I do n't for a minute believe that he just randomly decided to drop some punctuation in because , hell , why not ? I think his purpose might have been embarrassingly dumb and he 's covering it up .</tokentext>
<sentencetext>With all due respect to Sir Berners-Lee, I think he's fibbing.
If, indeed, it "seemed like a good idea at the time," then he had some purpose in mind when he came up with them.
I don't for a minute believe that he just randomly decided to drop some punctuation in because, hell, why not?I think his purpose might have been embarrassingly dumb and he's covering it up.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744073</id>
	<title>Re:Theres one technical point</title>
	<author>Imsdal</author>
	<datestamp>1255532400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p> Most programs which turn text into clickable URLs look for www.* (which btw. is one of the reasons for not omitting www from the URL although it is technically not necessary either.)</p> </div><p>
Another reason is incorrectly configured DNS'es. Some domains don't accept<nobr> <wbr></nobr>.com but require www..com. Embarrasingly, I have to confess that this applies both to my employer and my internet bank. Pretty good reasons to switch jobs and banks, if you ask me... (This applies to the www part. The <a href="http:///" title="http">http:///</a> [http] part is added implicitly by the browser, of course, and so is only needed for other protocols.)</p></div>
	</htmltext>
<tokenext>Most programs which turn text into clickable URLs look for www .
* ( which btw .
is one of the reasons for not omitting www from the URL although it is technically not necessary either .
) Another reason is incorrectly configured DNS'es .
Some domains do n't accept .com but require www..com .
Embarrasingly , I have to confess that this applies both to my employer and my internet bank .
Pretty good reasons to switch jobs and banks , if you ask me... ( This applies to the www part .
The http : /// [ http ] part is added implicitly by the browser , of course , and so is only needed for other protocols .
)</tokentext>
<sentencetext> Most programs which turn text into clickable URLs look for www.
* (which btw.
is one of the reasons for not omitting www from the URL although it is technically not necessary either.
) 
Another reason is incorrectly configured DNS'es.
Some domains don't accept .com but require www..com.
Embarrasingly, I have to confess that this applies both to my employer and my internet bank.
Pretty good reasons to switch jobs and banks, if you ask me... (This applies to the www part.
The http:/// [http] part is added implicitly by the browser, of course, and so is only needed for other protocols.
)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743775</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744027</id>
	<title>Re:Now explain triple-slashes</title>
	<author>gomek-ramek</author>
	<datestamp>1255532220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>file:// indicates the protocol.  The third slash indicates that it is an absolute path.</htmltext>
<tokenext>file : // indicates the protocol .
The third slash indicates that it is an absolute path .</tokentext>
<sentencetext>file:// indicates the protocol.
The third slash indicates that it is an absolute path.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750367</id>
	<title>Re:backslashdot</title>
	<author>steelfood</author>
	<datestamp>1255516680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Switch to - for switches, or put in intelligent command line parsing like UNIX has?</p></htmltext>
<tokenext>Switch to - for switches , or put in intelligent command line parsing like UNIX has ?</tokentext>
<sentencetext>Switch to - for switches, or put in intelligent command line parsing like UNIX has?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743935</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748559</id>
	<title>Re:backslashdot</title>
	<author>BuckaBooBob</author>
	<datestamp>1255551480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Well if thats the case.. is it a good thing that someone has recognized error of their ways and did absolutely nothing about it? After all.. how many complete rewrites have the done on their software and how many other changes have the done that completely broke backwards compatibility for some things?</p><p>Not to mention especially in todays era when virtualization is cropping up everywhere... If you really require the old OS.. run it in a VM.. problem solved.</p></htmltext>
<tokenext>Well if thats the case.. is it a good thing that someone has recognized error of their ways and did absolutely nothing about it ?
After all.. how many complete rewrites have the done on their software and how many other changes have the done that completely broke backwards compatibility for some things ? Not to mention especially in todays era when virtualization is cropping up everywhere... If you really require the old OS.. run it in a VM.. problem solved .</tokentext>
<sentencetext>Well if thats the case.. is it a good thing that someone has recognized error of their ways and did absolutely nothing about it?
After all.. how many complete rewrites have the done on their software and how many other changes have the done that completely broke backwards compatibility for some things?Not to mention especially in todays era when virtualization is cropping up everywhere... If you really require the old OS.. run it in a VM.. problem solved.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743873</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746405</id>
	<title>Re:www</title>
	<author>Anonymous</author>
	<datestamp>1255542000000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext>WWW -&gt; V/ V/ V/ -&gt; VI VI VI -&gt; 6 6 6</htmltext>
<tokenext>WWW - &gt; V/ V/ V/ - &gt; VI VI VI - &gt; 6 6 6</tokentext>
<sentencetext>WWW -&gt; V/ V/ V/ -&gt; VI VI VI -&gt; 6 6 6</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743967</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743935</id>
	<title>Re:backslashdot</title>
	<author>Anonymous</author>
	<datestamp>1255531800000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>Well, they added directories in MS-DOS 2 and had already used forward slashes for switches in MS-DOS 1, so what could they do? Can someone older than me confirm that they 'researched' the slash for switches from CPM?</htmltext>
<tokenext>Well , they added directories in MS-DOS 2 and had already used forward slashes for switches in MS-DOS 1 , so what could they do ?
Can someone older than me confirm that they 'researched ' the slash for switches from CPM ?</tokentext>
<sentencetext>Well, they added directories in MS-DOS 2 and had already used forward slashes for switches in MS-DOS 1, so what could they do?
Can someone older than me confirm that they 'researched' the slash for switches from CPM?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744499</id>
	<title>Re:backslashdot</title>
	<author>digitalaudiorock</author>
	<datestamp>1255534200000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>Nah. Slashes are fine, but Microsoft should be sorry about <b>back</b>slashes!</p></div><p>Boy, you're not kidding.  Nothing like using a directory delimiter that's the escape character in pretty much every programming language there is.  It's a good thing that most GNU programs etc ported to Windows let you use forward slashes in place of back slashes.</p></div>
	</htmltext>
<tokenext>Nah .
Slashes are fine , but Microsoft should be sorry about backslashes ! Boy , you 're not kidding .
Nothing like using a directory delimiter that 's the escape character in pretty much every programming language there is .
It 's a good thing that most GNU programs etc ported to Windows let you use forward slashes in place of back slashes .</tokentext>
<sentencetext>Nah.
Slashes are fine, but Microsoft should be sorry about backslashes!Boy, you're not kidding.
Nothing like using a directory delimiter that's the escape character in pretty much every programming language there is.
It's a good thing that most GNU programs etc ported to Windows let you use forward slashes in place of back slashes.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748717</id>
	<title>Re:backslashdot</title>
	<author>BuckaBooBob</author>
	<datestamp>1255552140000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><a href="http://en.wikipedia.org/wiki/Domain\_Name\_System" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Domain\_Name\_System</a> [wikipedia.org]</p><p>Whats wrong with DNS server? I think you have fallen along the path of those that call SQL.. (forgive me for this) Sequel...</p><p>
&nbsp;</p></htmltext>
<tokenext>http : //en.wikipedia.org/wiki/Domain \ _Name \ _System [ wikipedia.org ] Whats wrong with DNS server ?
I think you have fallen along the path of those that call SQL.. ( forgive me for this ) Sequel.. .  </tokentext>
<sentencetext>http://en.wikipedia.org/wiki/Domain\_Name\_System [wikipedia.org]Whats wrong with DNS server?
I think you have fallen along the path of those that call SQL.. (forgive me for this) Sequel...
 </sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745303</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745103</id>
	<title>Re:to think ..</title>
	<author>Anonymous</author>
	<datestamp>1255536600000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Except that<nobr> <wbr></nobr>/. doesn't refer to URLs...</p></htmltext>
<tokenext>Except that / .
does n't refer to URLs.. .</tokentext>
<sentencetext>Except that /.
doesn't refer to URLs...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746519</id>
	<title>Re:I like them!</title>
	<author>Anonymous</author>
	<datestamp>1255542600000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Now if we could just teach a planet full of lusers the difference between "slash" and "backslash." People always say "backslash"</p></div><p>I would have been skeptical of this statement before last week when, during a training seminar, the instructor told everyone to type "backslash backslash... etc" into their web browsers.<br>I did a bit of a double-take, and then again as everyone just bent over their keyboards pecking out slashes without question</p></div>
	</htmltext>
<tokenext>Now if we could just teach a planet full of lusers the difference between " slash " and " backslash .
" People always say " backslash " I would have been skeptical of this statement before last week when , during a training seminar , the instructor told everyone to type " backslash backslash... etc " into their web browsers.I did a bit of a double-take , and then again as everyone just bent over their keyboards pecking out slashes without question</tokentext>
<sentencetext>Now if we could just teach a planet full of lusers the difference between "slash" and "backslash.
" People always say "backslash"I would have been skeptical of this statement before last week when, during a training seminar, the instructor told everyone to type "backslash backslash... etc" into their web browsers.I did a bit of a double-take, and then again as everyone just bent over their keyboards pecking out slashes without question
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744411</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746145</id>
	<title>Re:DNS</title>
	<author>j1mmy</author>
	<datestamp>1255540860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>how would his second form work with subdomains? the name of a server is a distinct piece of information from the path to some piece of data on that server. if everything's a slash, there's no obvious way to distinguish between the two. "com/example/foo/bar" could mean either "foo.example.com/bar" or "example.com/foo/bar", both of which are perfectly valid.</p></htmltext>
<tokenext>how would his second form work with subdomains ?
the name of a server is a distinct piece of information from the path to some piece of data on that server .
if everything 's a slash , there 's no obvious way to distinguish between the two .
" com/example/foo/bar " could mean either " foo.example.com/bar " or " example.com/foo/bar " , both of which are perfectly valid .</tokentext>
<sentencetext>how would his second form work with subdomains?
the name of a server is a distinct piece of information from the path to some piece of data on that server.
if everything's a slash, there's no obvious way to distinguish between the two.
"com/example/foo/bar" could mean either "foo.example.com/bar" or "example.com/foo/bar", both of which are perfectly valid.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744655</id>
	<title>Hey, Tim</title>
	<author>Impy the Impiuos Imp</author>
	<datestamp>1255534860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Someone should inform Tim of a magnificent development:  Browsers presume you meant to type <a href="http:///" title="http" rel="nofollow">http:///</a> [http] before everything.  It's wondrous!</p></htmltext>
<tokenext>Someone should inform Tim of a magnificent development : Browsers presume you meant to type http : /// [ http ] before everything .
It 's wondrous !</tokentext>
<sentencetext>Someone should inform Tim of a magnificent development:  Browsers presume you meant to type http:/// [http] before everything.
It's wondrous!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743763</id>
	<title>gopher, wais</title>
	<author>Anonymous</author>
	<datestamp>1255530960000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>At the time there was also gopher and WAIS- both of which were supported by mosaic. The protocol was necessary to differentiate.</p></htmltext>
<tokenext>At the time there was also gopher and WAIS- both of which were supported by mosaic .
The protocol was necessary to differentiate .</tokentext>
<sentencetext>At the time there was also gopher and WAIS- both of which were supported by mosaic.
The protocol was necessary to differentiate.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750691</id>
	<title>Re:DNS</title>
	<author>Jesus\_666</author>
	<datestamp>1255518780000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Of course one could also have had a packet layout like this:<br>
<br>
<tt>com.example.domain \2<br>
some<br>
other<br>
com.another.domain \1<br>
www<br>
org.another \1<br>
yet \1<br>
blah</tt> <br>
<br>
Essentially, every line ends with one byte (in order to save space) stating how many of the following lines are direct subdomains of this one. The last line would thus identify <tt>org.another.yet.blah</tt>. Granted, this would be slightly more computationally intensive than the currently used one.<br>
<br>
Come to think of it, if space and computational complexity is that important, one could simply have used the current format - declaring that the order of subdomains in the format is reserved for convenience reasons. It's not like we don't have a few weird file formats that use such reasoning.</htmltext>
<tokenext>Of course one could also have had a packet layout like this : com.example.domain \ 2 some other com.another.domain \ 1 www org.another \ 1 yet \ 1 blah Essentially , every line ends with one byte ( in order to save space ) stating how many of the following lines are direct subdomains of this one .
The last line would thus identify org.another.yet.blah .
Granted , this would be slightly more computationally intensive than the currently used one .
Come to think of it , if space and computational complexity is that important , one could simply have used the current format - declaring that the order of subdomains in the format is reserved for convenience reasons .
It 's not like we do n't have a few weird file formats that use such reasoning .</tokentext>
<sentencetext>Of course one could also have had a packet layout like this:

com.example.domain \2
some
other
com.another.domain \1
www
org.another \1
yet \1
blah 

Essentially, every line ends with one byte (in order to save space) stating how many of the following lines are direct subdomains of this one.
The last line would thus identify org.another.yet.blah.
Granted, this would be slightly more computationally intensive than the currently used one.
Come to think of it, if space and computational complexity is that important, one could simply have used the current format - declaring that the order of subdomains in the format is reserved for convenience reasons.
It's not like we don't have a few weird file formats that use such reasoning.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744299</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744997</id>
	<title>Re:From the year 2022</title>
	<author>bickerdyke</author>
	<datestamp>1255536240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>review from cdweggbuy (yes, that's a full URL because people thought it was ok to remove gTLDs and also got rid of that pesky <a href="http:///" title="http">http:///</a> [http] </p></div><p>(spooky voice) Prepare for "The Return Of AOL Keywords !!"</p></div>
	</htmltext>
<tokenext>review from cdweggbuy ( yes , that 's a full URL because people thought it was ok to remove gTLDs and also got rid of that pesky http : /// [ http ] ( spooky voice ) Prepare for " The Return Of AOL Keywords ! !
"</tokentext>
<sentencetext>review from cdweggbuy (yes, that's a full URL because people thought it was ok to remove gTLDs and also got rid of that pesky http:/// [http] (spooky voice) Prepare for "The Return Of AOL Keywords !!
"
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743467</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746755</id>
	<title>Phishing scams</title>
	<author>lannocc</author>
	<datestamp>1255543620000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>What I wonder is why the designers of DNS put the name in reverse? If the name had been in most-significant-first order, one could have tabcompleted it properly (using history and maybe zonetransfers of smaller zones).</p></div><p>Not only that, but it would go a \_long\_ way towards preventing phishing scams.</p></div>
	</htmltext>
<tokenext>What I wonder is why the designers of DNS put the name in reverse ?
If the name had been in most-significant-first order , one could have tabcompleted it properly ( using history and maybe zonetransfers of smaller zones ) .Not only that , but it would go a \ _long \ _ way towards preventing phishing scams .</tokentext>
<sentencetext>What I wonder is why the designers of DNS put the name in reverse?
If the name had been in most-significant-first order, one could have tabcompleted it properly (using history and maybe zonetransfers of smaller zones).Not only that, but it would go a \_long\_ way towards preventing phishing scams.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744411</id>
	<title>I like them!</title>
	<author>sootman</author>
	<datestamp>1255533840000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>I *like* unique, easily-visually-identifiable structures. a@b.c is an email address. If you're in the U.S. you know that XXX-XXX-XXXX is a phone number and that XXX-XX-XXXX is a social security number. You know that X/Y/Z is a date, even if it's not always clear if it's M/D/Y or D/M/Y.</p><p>"://", while verbose, is very clear and you always know EXACTLY what it is and what it means--that it's the START of a COMPLETE Web address. If it would have been just a : or a / it wouldn't always be clear because those symbols, by themselves, are often used elsewhere and it would lead to confusion.</p><p>Now if we could just teach a planet full of lusers the difference between "slash" and "backslash." People always say "backslash" because they've heard computer guys say it every so often when talking about logging onto MS servers so they call EVERY slash a backslash. <a href="http://www.nytimes.com/1995/06/26/business/for-today-s-computers-new-symbol-takes-over.html" title="nytimes.com">Damn you Paul Allen!!!</a> [nytimes.com]</p></htmltext>
<tokenext>I * like * unique , easily-visually-identifiable structures .
a @ b.c is an email address .
If you 're in the U.S. you know that XXX-XXX-XXXX is a phone number and that XXX-XX-XXXX is a social security number .
You know that X/Y/Z is a date , even if it 's not always clear if it 's M/D/Y or D/M/Y .
" : // " , while verbose , is very clear and you always know EXACTLY what it is and what it means--that it 's the START of a COMPLETE Web address .
If it would have been just a : or a / it would n't always be clear because those symbols , by themselves , are often used elsewhere and it would lead to confusion.Now if we could just teach a planet full of lusers the difference between " slash " and " backslash .
" People always say " backslash " because they 've heard computer guys say it every so often when talking about logging onto MS servers so they call EVERY slash a backslash .
Damn you Paul Allen ! ! !
[ nytimes.com ]</tokentext>
<sentencetext>I *like* unique, easily-visually-identifiable structures.
a@b.c is an email address.
If you're in the U.S. you know that XXX-XXX-XXXX is a phone number and that XXX-XX-XXXX is a social security number.
You know that X/Y/Z is a date, even if it's not always clear if it's M/D/Y or D/M/Y.
"://", while verbose, is very clear and you always know EXACTLY what it is and what it means--that it's the START of a COMPLETE Web address.
If it would have been just a : or a / it wouldn't always be clear because those symbols, by themselves, are often used elsewhere and it would lead to confusion.Now if we could just teach a planet full of lusers the difference between "slash" and "backslash.
" People always say "backslash" because they've heard computer guys say it every so often when talking about logging onto MS servers so they call EVERY slash a backslash.
Damn you Paul Allen!!!
[nytimes.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744041</id>
	<title>Ah, NOW I understand God's last message!</title>
	<author>Anonymous</author>
	<datestamp>1255532280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>To Marvin the Robot: We apologize for the inconvenience.</p></htmltext>
<tokenext>To Marvin the Robot : We apologize for the inconvenience .</tokentext>
<sentencetext>To Marvin the Robot: We apologize for the inconvenience.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29761391</id>
	<title>Dumb</title>
	<author>pubwvj</author>
	<datestamp>1255639680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>But you don't have to type those slashes. Nor do you have to type out www or the dot. The browsers can fill it in. The servers can fill it in. Even the http and the colon can be left off in most cases unless you're doing secure https or ftp or something special. The waste is in people bothering to type those characters. In news articles they only need give NoNAIS.org or SugarMountainFarm.com or something like that and the path is implicit.</htmltext>
<tokenext>But you do n't have to type those slashes .
Nor do you have to type out www or the dot .
The browsers can fill it in .
The servers can fill it in .
Even the http and the colon can be left off in most cases unless you 're doing secure https or ftp or something special .
The waste is in people bothering to type those characters .
In news articles they only need give NoNAIS.org or SugarMountainFarm.com or something like that and the path is implicit .</tokentext>
<sentencetext>But you don't have to type those slashes.
Nor do you have to type out www or the dot.
The browsers can fill it in.
The servers can fill it in.
Even the http and the colon can be left off in most cases unless you're doing secure https or ftp or something special.
The waste is in people bothering to type those characters.
In news articles they only need give NoNAIS.org or SugarMountainFarm.com or something like that and the path is implicit.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745601</id>
	<title>Re:Now explain triple-slashes</title>
	<author>Anonymous</author>
	<datestamp>1255538640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Um, so in other words the browser will correctly interpret a null domain as localhost... or in other words, there is no domain, only a path...</p></htmltext>
<tokenext>Um , so in other words the browser will correctly interpret a null domain as localhost... or in other words , there is no domain , only a path.. .</tokentext>
<sentencetext>Um, so in other words the browser will correctly interpret a null domain as localhost... or in other words, there is no domain, only a path...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744763</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747381</id>
	<title>Re:I thought there was a point to the two slashes</title>
	<author>WebManWalking</author>
	<datestamp>1255546560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Not which network protocol to use,<nobr> <wbr></nobr>... which INTERNET to use. There hasn't always been just one (ARPANet, NSFNet, etc). If you ignore for a moment that the DNS server name string is backwards, above the server name is precisely where "Internet name" would belong hierarchically.<nobr> <wbr></nobr>/internet/server/path/... If there's only one, or if you want the same Internet as the one you're currently on, it can be (and is) omitted. <br>
<br>
That reserved spot could yet prove to be very useful someday. Every so often the US military talks about firewalling everything mission-critical to a completely different set of wires/fibers, with certain well-defined access points to bridge to the general Internet. Hoping and praying that they'll be brief, that might be r for restricted and g for general, but only if you have to bridge (//,<nobr> <wbr></nobr>/r/ or<nobr> <wbr></nobr>/g/). I was thinking, r for restricted rather than m for mil, because mil, where needed, is already in the server name, and there are obviously civilian servers (DHS, State, White House, etc) also requiring higher security wires/fibers. <br>
<br>
But in any case, URL is a <em>location</em> string. And the only <em>location</em> above server would be Internet.</htmltext>
<tokenext>Not which network protocol to use , ... which INTERNET to use .
There has n't always been just one ( ARPANet , NSFNet , etc ) .
If you ignore for a moment that the DNS server name string is backwards , above the server name is precisely where " Internet name " would belong hierarchically .
/internet/server/path/... If there 's only one , or if you want the same Internet as the one you 're currently on , it can be ( and is ) omitted .
That reserved spot could yet prove to be very useful someday .
Every so often the US military talks about firewalling everything mission-critical to a completely different set of wires/fibers , with certain well-defined access points to bridge to the general Internet .
Hoping and praying that they 'll be brief , that might be r for restricted and g for general , but only if you have to bridge ( // , /r/ or /g/ ) .
I was thinking , r for restricted rather than m for mil , because mil , where needed , is already in the server name , and there are obviously civilian servers ( DHS , State , White House , etc ) also requiring higher security wires/fibers .
But in any case , URL is a location string .
And the only location above server would be Internet .</tokentext>
<sentencetext>Not which network protocol to use, ... which INTERNET to use.
There hasn't always been just one (ARPANet, NSFNet, etc).
If you ignore for a moment that the DNS server name string is backwards, above the server name is precisely where "Internet name" would belong hierarchically.
/internet/server/path/... If there's only one, or if you want the same Internet as the one you're currently on, it can be (and is) omitted.
That reserved spot could yet prove to be very useful someday.
Every so often the US military talks about firewalling everything mission-critical to a completely different set of wires/fibers, with certain well-defined access points to bridge to the general Internet.
Hoping and praying that they'll be brief, that might be r for restricted and g for general, but only if you have to bridge (//, /r/ or /g/).
I was thinking, r for restricted rather than m for mil, because mil, where needed, is already in the server name, and there are obviously civilian servers (DHS, State, White House, etc) also requiring higher security wires/fibers.
But in any case, URL is a location string.
And the only location above server would be Internet.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743675</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744435</id>
	<title>Re:So Who's Apologizing for 'ttp' ?</title>
	<author>Anonymous</author>
	<datestamp>1255533960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>'http' for hypertext transfer protocol and not just simply 'h'</p></div><p>For one, that would conflict with every other protocol that begins with an 'h'.</p></div>
	</htmltext>
<tokenext>'http ' for hypertext transfer protocol and not just simply 'h'For one , that would conflict with every other protocol that begins with an 'h' .</tokentext>
<sentencetext>'http' for hypertext transfer protocol and not just simply 'h'For one, that would conflict with every other protocol that begins with an 'h'.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745285</id>
	<title>Re:pronouncing www is a lot more of a problem</title>
	<author>erlando</author>
	<datestamp>1255537380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>On the other hand, if you're setting up a web server and you don't make the first component of the name www then I would have to say that you are dense and you're not really doing your job properly.</p></div></blockquote><p>I can accept "www" for the "main" site. Just. But for subdomains? No way I'm going to name a site www.subdomain.example.com.</p><p>I'm so glad you're not running my DNS / Apache. I would have to fire you on the grounds of idiotic incompetance.</p></div>
	</htmltext>
<tokenext>On the other hand , if you 're setting up a web server and you do n't make the first component of the name www then I would have to say that you are dense and you 're not really doing your job properly.I can accept " www " for the " main " site .
Just. But for subdomains ?
No way I 'm going to name a site www.subdomain.example.com.I 'm so glad you 're not running my DNS / Apache .
I would have to fire you on the grounds of idiotic incompetance .</tokentext>
<sentencetext>On the other hand, if you're setting up a web server and you don't make the first component of the name www then I would have to say that you are dense and you're not really doing your job properly.I can accept "www" for the "main" site.
Just. But for subdomains?
No way I'm going to name a site www.subdomain.example.com.I'm so glad you're not running my DNS / Apache.
I would have to fire you on the grounds of idiotic incompetance.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744465</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744709</id>
	<title>Re:Now explain triple-slashes</title>
	<author>Anonymous</author>
	<datestamp>1255534980000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Thank you, never thought of that. Always wondered though.</p></htmltext>
<tokenext>Thank you , never thought of that .
Always wondered though .</tokentext>
<sentencetext>Thank you, never thought of that.
Always wondered though.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745625</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>syncmaster955</author>
	<datestamp>1255538760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Saying "double u double u double u" takes about twice as long as saying "web" </p></div><p>Yes but typing out uuuuuu would be a pain.</p></div>
	</htmltext>
<tokenext>Saying " double u double u double u " takes about twice as long as saying " web " Yes but typing out uuuuuu would be a pain .</tokentext>
<sentencetext>Saying "double u double u double u" takes about twice as long as saying "web" Yes but typing out uuuuuu would be a pain.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745611</id>
	<title>Re:DNS</title>
	<author>Hurricane78</author>
	<datestamp>1255538700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Exactly my thought. One could simply add the whole DNS structure as a tree *above* the root directory of your system on UNIX systems. Would be very nice.</p></htmltext>
<tokenext>Exactly my thought .
One could simply add the whole DNS structure as a tree * above * the root directory of your system on UNIX systems .
Would be very nice .</tokentext>
<sentencetext>Exactly my thought.
One could simply add the whole DNS structure as a tree *above* the root directory of your system on UNIX systems.
Would be very nice.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746855</id>
	<title>Re:I like them!</title>
	<author>sanosuke001</author>
	<datestamp>1255544220000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>Ever since I started working as a contractor for the Air Force, I've been using DDMMMYYYY for my dates(ie. 14OCT2009), and technically, it is shorter than MM/DD/YYYY by a single character. It's also less ambiguous for all parties involved as not everyone has MM and DD in the same location.<br> <br>

As for web addresses (to stay sort-of on topic...), most people do not use their web browser for anything other than http addresses. So the <a href="http:///" title="http">http:///</a> [http] is automatically filled in for them; worrying about whether they were a good idea is useless at this point and has been for a decade or more. Now, the slash/backslash issue is another story. I blame that on Microsoft.</htmltext>
<tokenext>Ever since I started working as a contractor for the Air Force , I 've been using DDMMMYYYY for my dates ( ie .
14OCT2009 ) , and technically , it is shorter than MM/DD/YYYY by a single character .
It 's also less ambiguous for all parties involved as not everyone has MM and DD in the same location .
As for web addresses ( to stay sort-of on topic... ) , most people do not use their web browser for anything other than http addresses .
So the http : /// [ http ] is automatically filled in for them ; worrying about whether they were a good idea is useless at this point and has been for a decade or more .
Now , the slash/backslash issue is another story .
I blame that on Microsoft .</tokentext>
<sentencetext>Ever since I started working as a contractor for the Air Force, I've been using DDMMMYYYY for my dates(ie.
14OCT2009), and technically, it is shorter than MM/DD/YYYY by a single character.
It's also less ambiguous for all parties involved as not everyone has MM and DD in the same location.
As for web addresses (to stay sort-of on topic...), most people do not use their web browser for anything other than http addresses.
So the http:/// [http] is automatically filled in for them; worrying about whether they were a good idea is useless at this point and has been for a decade or more.
Now, the slash/backslash issue is another story.
I blame that on Microsoft.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744411</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29754939</id>
	<title>Not entirely unrelated</title>
	<author>RivenAleem</author>
	<datestamp>1255606320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>On the subject of slashes, and the internet, I got curious and typed<nobr> <wbr></nobr>/. into google search. It returned with 0 results. What's up with that?</htmltext>
<tokenext>On the subject of slashes , and the internet , I got curious and typed / .
into google search .
It returned with 0 results .
What 's up with that ?</tokentext>
<sentencetext>On the subject of slashes, and the internet, I got curious and typed /.
into google search.
It returned with 0 results.
What's up with that?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743983</id>
	<title>Backslash</title>
	<author>cafn8ed</author>
	<datestamp>1255531980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>My biggest problem with the slashes is the number of people (especially in the mainstream press) who call them backslashes.  Drives me up a wall.</p></htmltext>
<tokenext>My biggest problem with the slashes is the number of people ( especially in the mainstream press ) who call them backslashes .
Drives me up a wall .</tokentext>
<sentencetext>My biggest problem with the slashes is the number of people (especially in the mainstream press) who call them backslashes.
Drives me up a wall.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743893</id>
	<title>There was a point, but never used</title>
	<author>Anonymous</author>
	<datestamp>1255531620000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>It is explained by TBL at http://www.w3.org/People/Berners-Lee/FAQ.html#etc</p><p>"I wanted the syntax of the URI to separate the bit which the web browser has to know about (www.example.com) from the rest (the opaque string which is blindly requested by the client from the server). Within the rest of the URI, slashes (/) were the clear choice to separate parts of a hierarchical system, and I wanted to be able to make a link without having to know the name of the service (www.example.com) which was publishing the data. The relative URI syntax is just unix pathname syntax reused without apology. Anyone who had used unix would find it quite obvious. Then I needed an extension to add the service name (hostname). In fact this was similar to the problem the Apollo domain system had had when they created a network file system. They had extended the filename syntax to allow<nobr> <wbr></nobr>//computername/file/path/as/usual. So I just copied Apollo. Apollo was a brand of unix workstation."</p></htmltext>
<tokenext>It is explained by TBL at http : //www.w3.org/People/Berners-Lee/FAQ.html # etc " I wanted the syntax of the URI to separate the bit which the web browser has to know about ( www.example.com ) from the rest ( the opaque string which is blindly requested by the client from the server ) .
Within the rest of the URI , slashes ( / ) were the clear choice to separate parts of a hierarchical system , and I wanted to be able to make a link without having to know the name of the service ( www.example.com ) which was publishing the data .
The relative URI syntax is just unix pathname syntax reused without apology .
Anyone who had used unix would find it quite obvious .
Then I needed an extension to add the service name ( hostname ) .
In fact this was similar to the problem the Apollo domain system had had when they created a network file system .
They had extended the filename syntax to allow //computername/file/path/as/usual .
So I just copied Apollo .
Apollo was a brand of unix workstation .
"</tokentext>
<sentencetext>It is explained by TBL at http://www.w3.org/People/Berners-Lee/FAQ.html#etc"I wanted the syntax of the URI to separate the bit which the web browser has to know about (www.example.com) from the rest (the opaque string which is blindly requested by the client from the server).
Within the rest of the URI, slashes (/) were the clear choice to separate parts of a hierarchical system, and I wanted to be able to make a link without having to know the name of the service (www.example.com) which was publishing the data.
The relative URI syntax is just unix pathname syntax reused without apology.
Anyone who had used unix would find it quite obvious.
Then I needed an extension to add the service name (hostname).
In fact this was similar to the problem the Apollo domain system had had when they created a network file system.
They had extended the filename syntax to allow //computername/file/path/as/usual.
So I just copied Apollo.
Apollo was a brand of unix workstation.
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743769</id>
	<title>Re:From the year 2022</title>
	<author>jayhawk88</author>
	<datestamp>1255530960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I love that a post that begins "I used my time modem..." can be modded as Insightful. God bless you, you crazy mods.</p></htmltext>
<tokenext>I love that a post that begins " I used my time modem... " can be modded as Insightful .
God bless you , you crazy mods .</tokentext>
<sentencetext>I love that a post that begins "I used my time modem..." can be modded as Insightful.
God bless you, you crazy mods.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743467</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745407</id>
	<title>:/ is</title>
	<author>Anonymous</author>
	<datestamp>1255537860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>:/ is how he feels about<nobr> <wbr></nobr>:/</p></htmltext>
<tokenext>: / is how he feels about : /</tokentext>
<sentencetext>:/ is how he feels about :/</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743645</id>
	<title>It's interesting</title>
	<author>Anonymous</author>
	<datestamp>1255530480000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext>I think it's interesting to be able to talk to someone who picked something that affects so many people on a daily basis.  Of course, it's a really tiny effect, but very visible.  He could have picked two colons or dollar signs or any random thing.  It's not often you get to make a decision that ends up being used globally.</htmltext>
<tokenext>I think it 's interesting to be able to talk to someone who picked something that affects so many people on a daily basis .
Of course , it 's a really tiny effect , but very visible .
He could have picked two colons or dollar signs or any random thing .
It 's not often you get to make a decision that ends up being used globally .</tokentext>
<sentencetext>I think it's interesting to be able to talk to someone who picked something that affects so many people on a daily basis.
Of course, it's a really tiny effect, but very visible.
He could have picked two colons or dollar signs or any random thing.
It's not often you get to make a decision that ends up being used globally.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745487</id>
	<title>Re:to think ..</title>
	<author>LordKronos</author>
	<datestamp>1255538220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><a href="http://slashdot.org/faq/slashmeta.shtml#sm150" title="slashdot.org">http://slashdot.org/faq/slashmeta.shtml#sm150</a> [slashdot.org]</p><p>It was meant to be confusing with the repeated "words". h-t-t-p-colon-slash-slash-slash-dot-dot-org. Without the slashes, it would have to have been h-t-t-p-colon-colon-dot-dot-org</p></htmltext>
<tokenext>http : //slashdot.org/faq/slashmeta.shtml # sm150 [ slashdot.org ] It was meant to be confusing with the repeated " words " .
h-t-t-p-colon-slash-slash-slash-dot-dot-org. Without the slashes , it would have to have been h-t-t-p-colon-colon-dot-dot-org</tokentext>
<sentencetext>http://slashdot.org/faq/slashmeta.shtml#sm150 [slashdot.org]It was meant to be confusing with the repeated "words".
h-t-t-p-colon-slash-slash-slash-dot-dot-org. Without the slashes, it would have to have been h-t-t-p-colon-colon-dot-dot-org</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745071</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745655</id>
	<title>Re:DNS</title>
	<author>Wite\_Noiz</author>
	<datestamp>1255538880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Actually, Sir TBL himself has apologised for this before: <a href="http://slashdot.org/article.pl?sid=06/03/24/1920230" title="slashdot.org" rel="nofollow">http://slashdot.org/article.pl?sid=06/03/24/1920230</a> [slashdot.org]
<p>
I actually went to see him at this talk. Very interesting guy.</p></htmltext>
<tokenext>Actually , Sir TBL himself has apologised for this before : http : //slashdot.org/article.pl ? sid = 06/03/24/1920230 [ slashdot.org ] I actually went to see him at this talk .
Very interesting guy .</tokentext>
<sentencetext>Actually, Sir TBL himself has apologised for this before: http://slashdot.org/article.pl?sid=06/03/24/1920230 [slashdot.org]

I actually went to see him at this talk.
Very interesting guy.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29755783</id>
	<title>Re:backslashdot</title>
	<author>ToreTS</author>
	<datestamp>1255614540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>What is superfluous with referring to a Domain Name System server?</htmltext>
<tokenext>What is superfluous with referring to a Domain Name System server ?</tokentext>
<sentencetext>What is superfluous with referring to a Domain Name System server?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745303</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745075</id>
	<title>Of course there is a point to it!</title>
	<author>Hurricane78</author>
	<datestamp>1255536540000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>Just like one slash at the beginning is for the root directory in an absolute path, two slashes are for the root of the network.</p><p>The only question is, why it's<br>[protocol]://[sub].[domain].[tld]/[path]...<br>instead of<br>[protocol]://[tld]/[domain]/[sub]/[path]...</p><p>But I guess that way you can separate what's a different server and what is not.</p><p>Only the file protocol has it wrong, because it's not the root of the network, when you write:<br>file:///[path]<br>It should be:<br>file:/[path]</p><p>But hey, nothing stops you from using your own syntax when you write software like a browser.</p><p>In fact, I'd love to see the net just becoming another part of the path of the "everything is a file" file system of UNIX machines.</p></htmltext>
<tokenext>Just like one slash at the beginning is for the root directory in an absolute path , two slashes are for the root of the network.The only question is , why it 's [ protocol ] : // [ sub ] . [ domain ] .
[ tld ] / [ path ] ...instead of [ protocol ] : // [ tld ] / [ domain ] / [ sub ] / [ path ] ...But I guess that way you can separate what 's a different server and what is not.Only the file protocol has it wrong , because it 's not the root of the network , when you write : file : /// [ path ] It should be : file : / [ path ] But hey , nothing stops you from using your own syntax when you write software like a browser.In fact , I 'd love to see the net just becoming another part of the path of the " everything is a file " file system of UNIX machines .</tokentext>
<sentencetext>Just like one slash at the beginning is for the root directory in an absolute path, two slashes are for the root of the network.The only question is, why it's[protocol]://[sub].[domain].
[tld]/[path]...instead of[protocol]://[tld]/[domain]/[sub]/[path]...But I guess that way you can separate what's a different server and what is not.Only the file protocol has it wrong, because it's not the root of the network, when you write:file:///[path]It should be:file:/[path]But hey, nothing stops you from using your own syntax when you write software like a browser.In fact, I'd love to see the net just becoming another part of the path of the "everything is a file" file system of UNIX machines.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743949</id>
	<title>Re:Just for the looks?</title>
	<author>bipbop</author>
	<datestamp>1255531860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Definitely.  Can you think of anything more techie than saying "Okay, now browse to http colon slash slash slash dot dot org dot slash on your Apple slash slash e"?  I can't.</htmltext>
<tokenext>Definitely .
Can you think of anything more techie than saying " Okay , now browse to http colon slash slash slash dot dot org dot slash on your Apple slash slash e " ?
I ca n't .</tokentext>
<sentencetext>Definitely.
Can you think of anything more techie than saying "Okay, now browse to http colon slash slash slash dot dot org dot slash on your Apple slash slash e"?
I can't.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743491</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744579</id>
	<title>Re:Mosaic?</title>
	<author>Anonymous</author>
	<datestamp>1255534560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Real nerds are still using 2400 baud modems.</p><p>. . . . . Oooo I can see the HTML.  Now just need to wait for the pics to load . . . . . Might as well go get a Philly cheesesteak while I'm waiting . . . . . . . . . . . oh good, the page is displayed, and the pics are 90\% finished.  Only took half an hour.  Who needs stinkin' modern 56000 technology?  Overkill is what that is.  </p><p><nobr> <wbr></nobr>;-)</p><p>When I was stuck in a hotel one time, the lines were so noisy I routinely got 19k, 21k, or 24k connections.  Talk about slooooow.  The amazing part is that I actually bittorrented episodes of SGA and BSG at that speed.  Took about 8 hours just to get one episode, so I could come home from work and watch the latest Stargate and Galactica exploits.</p></htmltext>
<tokenext>Real nerds are still using 2400 baud modems.. . .
. .
Oooo I can see the HTML .
Now just need to wait for the pics to load .
. .
. .
Might as well go get a Philly cheesesteak while I 'm waiting .
. .
. .
. .
. .
. .
oh good , the page is displayed , and the pics are 90 \ % finished .
Only took half an hour .
Who needs stinkin ' modern 56000 technology ?
Overkill is what that is .
; - ) When I was stuck in a hotel one time , the lines were so noisy I routinely got 19k , 21k , or 24k connections .
Talk about slooooow .
The amazing part is that I actually bittorrented episodes of SGA and BSG at that speed .
Took about 8 hours just to get one episode , so I could come home from work and watch the latest Stargate and Galactica exploits .</tokentext>
<sentencetext>Real nerds are still using 2400 baud modems.. . .
. .
Oooo I can see the HTML.
Now just need to wait for the pics to load .
. .
. .
Might as well go get a Philly cheesesteak while I'm waiting .
. .
. .
. .
. .
. .
oh good, the page is displayed, and the pics are 90\% finished.
Only took half an hour.
Who needs stinkin' modern 56000 technology?
Overkill is what that is.
;-)When I was stuck in a hotel one time, the lines were so noisy I routinely got 19k, 21k, or 24k connections.
Talk about slooooow.
The amazing part is that I actually bittorrented episodes of SGA and BSG at that speed.
Took about 8 hours just to get one episode, so I could come home from work and watch the latest Stargate and Galactica exploits.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743765</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743609</id>
	<title>... it seemed like a good idea at the time...</title>
	<author>ledow</author>
	<datestamp>1255530300000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>There you go, it seemed like a good idea at the time. he said.</p><p>If the human race is ever brought before a court to account for itself, that's going to be its entire defence.  Nuclear power, the Internet, ID cards,<nobr> <wbr></nobr>... that excuse works for everything!</p></htmltext>
<tokenext>There you go , it seemed like a good idea at the time .
he said.If the human race is ever brought before a court to account for itself , that 's going to be its entire defence .
Nuclear power , the Internet , ID cards , ... that excuse works for everything !</tokentext>
<sentencetext>There you go, it seemed like a good idea at the time.
he said.If the human race is ever brought before a court to account for itself, that's going to be its entire defence.
Nuclear power, the Internet, ID cards, ... that excuse works for everything!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749745</id>
	<title>backslash</title>
	<author>w0mprat</author>
	<datestamp>1255513620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Microsoft chose backslash, in particular a double backslash \\ to indicate a hostname. I don't know the origins of this decision, but it makes sense in a number of ways instead of using<nobr> <wbr></nobr>:// to seperate protocol from domain path. (Scarily) we could have had internet with \\slashdot.org\story\09\10\14\1219215\Tim-Berners-Lee-Is-<b>Glad</b>-About-the-Slashes<br> <br>
This would make it markedly easier to pick out URLs in text, requiring no<nobr> <wbr></nobr>:// kludge since backslashes are not used commonly in text in the way colons and slashes are. Yet somehow I don't pine for this alternate destiny.</htmltext>
<tokenext>Microsoft chose backslash , in particular a double backslash \ \ to indicate a hostname .
I do n't know the origins of this decision , but it makes sense in a number of ways instead of using : // to seperate protocol from domain path .
( Scarily ) we could have had internet with \ \ slashdot.org \ story \ 09 \ 10 \ 14 \ 1219215 \ Tim-Berners-Lee-Is-Glad-About-the-Slashes This would make it markedly easier to pick out URLs in text , requiring no : // kludge since backslashes are not used commonly in text in the way colons and slashes are .
Yet somehow I do n't pine for this alternate destiny .</tokentext>
<sentencetext>Microsoft chose backslash, in particular a double backslash \\ to indicate a hostname.
I don't know the origins of this decision, but it makes sense in a number of ways instead of using :// to seperate protocol from domain path.
(Scarily) we could have had internet with \\slashdot.org\story\09\10\14\1219215\Tim-Berners-Lee-Is-Glad-About-the-Slashes 
This would make it markedly easier to pick out URLs in text, requiring no :// kludge since backslashes are not used commonly in text in the way colons and slashes are.
Yet somehow I don't pine for this alternate destiny.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746429</id>
	<title>Re:backslashdot</title>
	<author>LWATCDR</author>
	<datestamp>1255542120000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>MS-DOS was a copy of CP/M.<br>CP/M used / for switches so MS did the same. Maybe CP/M machines didn't have a backslash? I know they sure didn't  have a pipe command. Also QD-Dos was designed to run on S100 buss machines and used terminals. Microsoft bought it and made it into PC-Dos and then made it into MS-DOS.</p></htmltext>
<tokenext>MS-DOS was a copy of CP/M.CP/M used / for switches so MS did the same .
Maybe CP/M machines did n't have a backslash ?
I know they sure did n't have a pipe command .
Also QD-Dos was designed to run on S100 buss machines and used terminals .
Microsoft bought it and made it into PC-Dos and then made it into MS-DOS .</tokentext>
<sentencetext>MS-DOS was a copy of CP/M.CP/M used / for switches so MS did the same.
Maybe CP/M machines didn't have a backslash?
I know they sure didn't  have a pipe command.
Also QD-Dos was designed to run on S100 buss machines and used terminals.
Microsoft bought it and made it into PC-Dos and then made it into MS-DOS.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743873</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745771</id>
	<title>Re:I like them!</title>
	<author>clone53421</author>
	<datestamp>1255539360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>"://", while verbose, is very clear and you always know EXACTLY what it is and what it means</p></div><p>And http: isn't?</p></div>
	</htmltext>
<tokenext>" : // " , while verbose , is very clear and you always know EXACTLY what it is and what it meansAnd http : is n't ?</tokentext>
<sentencetext>"://", while verbose, is very clear and you always know EXACTLY what it is and what it meansAnd http: isn't?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744411</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747045</id>
	<title>Re:DNS</title>
	<author>DigitalCrackPipe</author>
	<datestamp>1255545000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Note that postal mail uses the same strategy - you note the name first, then the address.  While the post office looks at the last line first for the zip code, the sender likely thinks of the name first.  Also, consider that name.com and name.org may be both refer to similar concepts, while com.name1 and com.name2 may be completely unrelated.
<br>
Of course, if TLDs were strict about location and content type it would indeed make more sense to be in the order you describe.</htmltext>
<tokenext>Note that postal mail uses the same strategy - you note the name first , then the address .
While the post office looks at the last line first for the zip code , the sender likely thinks of the name first .
Also , consider that name.com and name.org may be both refer to similar concepts , while com.name1 and com.name2 may be completely unrelated .
Of course , if TLDs were strict about location and content type it would indeed make more sense to be in the order you describe .</tokentext>
<sentencetext>Note that postal mail uses the same strategy - you note the name first, then the address.
While the post office looks at the last line first for the zip code, the sender likely thinks of the name first.
Also, consider that name.com and name.org may be both refer to similar concepts, while com.name1 and com.name2 may be completely unrelated.
Of course, if TLDs were strict about location and content type it would indeed make more sense to be in the order you describe.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749339</id>
	<title>Re:DNS</title>
	<author>Anonymous</author>
	<datestamp>1255511760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>This was not done because "DOT COM" would have instead been "COM DOT" which sounds too pornographic.</htmltext>
<tokenext>This was not done because " DOT COM " would have instead been " COM DOT " which sounds too pornographic .</tokentext>
<sentencetext>This was not done because "DOT COM" would have instead been "COM DOT" which sounds too pornographic.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744749</id>
	<title>Re:DNS</title>
	<author>Richard W.M. Jones</author>
	<datestamp>1255535220000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>UK internet addresses <a href="https://secure.wikimedia.org/wikipedia/en/wiki/JANET\_NRS" title="wikimedia.org">used to be like that</a> [wikimedia.org].  I remember it well.  It caused a bit of fun during the changeover period c. 1992.</p><p>Rich.</p></htmltext>
<tokenext>UK internet addresses used to be like that [ wikimedia.org ] .
I remember it well .
It caused a bit of fun during the changeover period c. 1992.Rich .</tokentext>
<sentencetext>UK internet addresses used to be like that [wikimedia.org].
I remember it well.
It caused a bit of fun during the changeover period c. 1992.Rich.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744347</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>corbettw</author>
	<datestamp>1255533600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I've always mentally read it as "triple dub". That doesn't take so long to say, and most people understand what I mean by it when I use it in conversation.</p></htmltext>
<tokenext>I 've always mentally read it as " triple dub " .
That does n't take so long to say , and most people understand what I mean by it when I use it in conversation .</tokentext>
<sentencetext>I've always mentally read it as "triple dub".
That doesn't take so long to say, and most people understand what I mean by it when I use it in conversation.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750965</id>
	<title>Re:pronouncing www is a lot more of a problem</title>
	<author>Anonymous</author>
	<datestamp>1255520280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>I threw up my coffee on my new monitor.

You owe me a monitor.</htmltext>
<tokenext>I threw up my coffee on my new monitor .
You owe me a monitor .</tokentext>
<sentencetext>I threw up my coffee on my new monitor.
You owe me a monitor.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744495</id>
	<title>Re:backslashdot</title>
	<author>Larryish</author>
	<datestamp>1255534200000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>We should get rid of all those useless delimiters NOW!</p><p>Programming languages are full of them, think of how much more productive programmers could be if they weren't typing all those DAMNED DELIMITERS!!!</p><p>DAMNIT!!!</p></htmltext>
<tokenext>We should get rid of all those useless delimiters NOW ! Programming languages are full of them , think of how much more productive programmers could be if they were n't typing all those DAMNED DELIMITERS ! ! ! DAMNIT ! !
!</tokentext>
<sentencetext>We should get rid of all those useless delimiters NOW!Programming languages are full of them, think of how much more productive programmers could be if they weren't typing all those DAMNED DELIMITERS!!!DAMNIT!!
!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746571</id>
	<title>pedantic apologies for lack of brevity</title>
	<author>Radical Moderate</author>
	<datestamp>1255542840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Perfect title for my next album.  <br>Thanks!</htmltext>
<tokenext>Perfect title for my next album .
Thanks !</tokentext>
<sentencetext>Perfect title for my next album.
Thanks!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743491</id>
	<title>Just for the looks?</title>
	<author>kill-1</author>
	<datestamp>1255529460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I think they look pretty cool and techy</p></htmltext>
<tokenext>I think they look pretty cool and techy</tokentext>
<sentencetext>I think they look pretty cool and techy</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511</id>
	<title>to think ..</title>
	<author>Anonymous</author>
	<datestamp>1255529580000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>.. we could've had colondot instead of slashdot! I like it!</p></htmltext>
<tokenext>.. we could 've had colondot instead of slashdot !
I like it !</tokentext>
<sentencetext>.. we could've had colondot instead of slashdot!
I like it!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745353</id>
	<title>Re:  What is the point of the ...</title>
	<author>rnturn</author>
	<datestamp>1255537680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p><nobr> <wbr></nobr><i>... two forward slashes that sit directly in front of the 'www' in every internet website address?</i></p></div> </blockquote><p>Not to be too-o-o picky, but a great many website addresses do not begin with "www.".  Now if the author had written "<i>two forward slashes that sit directly after the ':' in every internet...</i>" I'd have had time to get another cup of coffee before my next meeting.  But when <a href="http://xkcd.com/386/" title="xkcd.com">duty calls</a> [xkcd.com] I just have to answer.</p></div>
	</htmltext>
<tokenext>... two forward slashes that sit directly in front of the 'www ' in every internet website address ?
Not to be too-o-o picky , but a great many website addresses do not begin with " www. " .
Now if the author had written " two forward slashes that sit directly after the ' : ' in every internet... " I 'd have had time to get another cup of coffee before my next meeting .
But when duty calls [ xkcd.com ] I just have to answer .</tokentext>
<sentencetext> ... two forward slashes that sit directly in front of the 'www' in every internet website address?
Not to be too-o-o picky, but a great many website addresses do not begin with "www.".
Now if the author had written "two forward slashes that sit directly after the ':' in every internet..." I'd have had time to get another cup of coffee before my next meeting.
But when duty calls [xkcd.com] I just have to answer.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743889</id>
	<title>Re:So Who's Apologizing for 'ttp' ?</title>
	<author>Anonymous</author>
	<datestamp>1255531620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>the worst offender of all is the 'w' in spoken web addresses. I know several attempts have been made, but can we change it to 'globe girdling grid' or something?</p></htmltext>
<tokenext>the worst offender of all is the 'w ' in spoken web addresses .
I know several attempts have been made , but can we change it to 'globe girdling grid ' or something ?</tokentext>
<sentencetext>the worst offender of all is the 'w' in spoken web addresses.
I know several attempts have been made, but can we change it to 'globe girdling grid' or something?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748311</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>osu-neko</author>
	<datestamp>1255550460000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>I've always mentally read it as "triple dub". That doesn't take so long to say, and most people understand what I mean by it when I use it in conversation.</p></div><p>That's... interesting.  Do you always "hear voices" while mentally reading?  I find I frequently don't realize I don't know how to pronounce a word until the first time I try to use it in spoken conversation.  When reading text, it simply doesn't come up how it "sounds"...</p><p>Then again, apparently I'm strange.  People talk about whether someone can <i>think</i> in another language or not, as if it requires greater aptitude to <i>think</i> in another language rather than merely speak it, whereas I point out it's a necessary prerequisite to be able to think it in order to speak it.  But I'm told they're talking about "just thinking" rather than thinking about what you're going to say -- in which case, I don't use any language at all, I just think thoughts.  I only think words in a language when I'm thinking about speaking.  If I'm thinking about water, I use neither the word "water" or "agua" in my head, which words to use only comes up when I'm thinking about how to articulate my thoughts.  I can't imagine how slow it would be to actually think in a language, native or not.</p></div>
	</htmltext>
<tokenext>I 've always mentally read it as " triple dub " .
That does n't take so long to say , and most people understand what I mean by it when I use it in conversation.That 's... interesting. Do you always " hear voices " while mentally reading ?
I find I frequently do n't realize I do n't know how to pronounce a word until the first time I try to use it in spoken conversation .
When reading text , it simply does n't come up how it " sounds " ...Then again , apparently I 'm strange .
People talk about whether someone can think in another language or not , as if it requires greater aptitude to think in another language rather than merely speak it , whereas I point out it 's a necessary prerequisite to be able to think it in order to speak it .
But I 'm told they 're talking about " just thinking " rather than thinking about what you 're going to say -- in which case , I do n't use any language at all , I just think thoughts .
I only think words in a language when I 'm thinking about speaking .
If I 'm thinking about water , I use neither the word " water " or " agua " in my head , which words to use only comes up when I 'm thinking about how to articulate my thoughts .
I ca n't imagine how slow it would be to actually think in a language , native or not .</tokentext>
<sentencetext>I've always mentally read it as "triple dub".
That doesn't take so long to say, and most people understand what I mean by it when I use it in conversation.That's... interesting.  Do you always "hear voices" while mentally reading?
I find I frequently don't realize I don't know how to pronounce a word until the first time I try to use it in spoken conversation.
When reading text, it simply doesn't come up how it "sounds"...Then again, apparently I'm strange.
People talk about whether someone can think in another language or not, as if it requires greater aptitude to think in another language rather than merely speak it, whereas I point out it's a necessary prerequisite to be able to think it in order to speak it.
But I'm told they're talking about "just thinking" rather than thinking about what you're going to say -- in which case, I don't use any language at all, I just think thoughts.
I only think words in a language when I'm thinking about speaking.
If I'm thinking about water, I use neither the word "water" or "agua" in my head, which words to use only comes up when I'm thinking about how to articulate my thoughts.
I can't imagine how slow it would be to actually think in a language, native or not.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744347</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743783</id>
	<title>POSIX</title>
	<author>Anonymous</author>
	<datestamp>1255531020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>In POSIX, file names starting with two slashes are special. One slash or even three slashes mean the root of the filesystem, but two slashes can mean something else (for instance, they can be followed by a server name). You see a leftover of that in Windows (only with backslashes instead of slashes), where a single backslash means the root of the current drive but two slashes are followed by a server name (or some even more obscure things).</p><p>So, I would guess he just used the same special meaning, only with a protocol in the front.</p></htmltext>
<tokenext>In POSIX , file names starting with two slashes are special .
One slash or even three slashes mean the root of the filesystem , but two slashes can mean something else ( for instance , they can be followed by a server name ) .
You see a leftover of that in Windows ( only with backslashes instead of slashes ) , where a single backslash means the root of the current drive but two slashes are followed by a server name ( or some even more obscure things ) .So , I would guess he just used the same special meaning , only with a protocol in the front .</tokentext>
<sentencetext>In POSIX, file names starting with two slashes are special.
One slash or even three slashes mean the root of the filesystem, but two slashes can mean something else (for instance, they can be followed by a server name).
You see a leftover of that in Windows (only with backslashes instead of slashes), where a single backslash means the root of the current drive but two slashes are followed by a server name (or some even more obscure things).So, I would guess he just used the same special meaning, only with a protocol in the front.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744143</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>Anonymous</author>
	<datestamp>1255532700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Saying "double u double u double u" takes about twice as long as saying "web" so that would have been far more beneficial than worrying about the slashes.</p></div><p>If you use a decent language, you can just say "we we we" (exact pronunciation may differ).</p></div>
	</htmltext>
<tokenext>Saying " double u double u double u " takes about twice as long as saying " web " so that would have been far more beneficial than worrying about the slashes.If you use a decent language , you can just say " we we we " ( exact pronunciation may differ ) .</tokentext>
<sentencetext>Saying "double u double u double u" takes about twice as long as saying "web" so that would have been far more beneficial than worrying about the slashes.If you use a decent language, you can just say "we we we" (exact pronunciation may differ).
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29758489</id>
	<title>Re:DNS</title>
	<author>Anonymous</author>
	<datestamp>1255626300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>So that you can with less ambiguity access local/"closer" machines without typing everything.</p><p>e.g.</p><p>ping mybox1<br>ping mybox2</p><p>vs ping edu.wustl.mybox1</p><p>Nowadays there are browsers with address completion that doesn't depend so much on what an address starts with. You can even type a pattern from the end.</p></htmltext>
<tokenext>So that you can with less ambiguity access local/ " closer " machines without typing everything.e.g.ping mybox1ping mybox2vs ping edu.wustl.mybox1Nowadays there are browsers with address completion that does n't depend so much on what an address starts with .
You can even type a pattern from the end .</tokentext>
<sentencetext>So that you can with less ambiguity access local/"closer" machines without typing everything.e.g.ping mybox1ping mybox2vs ping edu.wustl.mybox1Nowadays there are browsers with address completion that doesn't depend so much on what an address starts with.
You can even type a pattern from the end.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748427</id>
	<title>Re:backslashdot</title>
	<author>Anonymous</author>
	<datestamp>1255550820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>...or using your "PIN Number" at the "ATM Machine" to get cash so you can go to "WalMart" mart and fill your "Rx" prescription. WTF</htmltext>
<tokenext>...or using your " PIN Number " at the " ATM Machine " to get cash so you can go to " WalMart " mart and fill your " Rx " prescription .
WTF</tokentext>
<sentencetext>...or using your "PIN Number" at the "ATM Machine" to get cash so you can go to "WalMart" mart and fill your "Rx" prescription.
WTF</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745303</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745057</id>
	<title>Re:pronouncing www is a lot more of a problem</title>
	<author>mujadaddy</author>
	<datestamp>1255536480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>We (ok, my boss mostly) pronouce it "whackwhack" here.</htmltext>
<tokenext>We ( ok , my boss mostly ) pronouce it " whackwhack " here .</tokentext>
<sentencetext>We (ok, my boss mostly) pronouce it "whackwhack" here.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743637</id>
	<title>Just wondering?</title>
	<author>Anonymous</author>
	<datestamp>1255530420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Would a t-shirt with two slashes topped by a red circle with a slash through it be considered redundant?</p></htmltext>
<tokenext>Would a t-shirt with two slashes topped by a red circle with a slash through it be considered redundant ?</tokentext>
<sentencetext>Would a t-shirt with two slashes topped by a red circle with a slash through it be considered redundant?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744681</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>sunderland56</author>
	<datestamp>1255534920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Why is the www necessary in the first place? I think <b>that</b> is where Berners-Lee made the largest mistake.
<br> <br>
Thankfully any semi-intelligent web site doesn't require the www.</htmltext>
<tokenext>Why is the www necessary in the first place ?
I think that is where Berners-Lee made the largest mistake .
Thankfully any semi-intelligent web site does n't require the www .</tokentext>
<sentencetext>Why is the www necessary in the first place?
I think that is where Berners-Lee made the largest mistake.
Thankfully any semi-intelligent web site doesn't require the www.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750359</id>
	<title>What about the www?</title>
	<author>Arancaytar</author>
	<datestamp>1255516620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Screw those stupid slashes; you don't need to write those out anyway. What I want to know is who the hell came up with prefixing web addresses with www.</p><p>I can imagine it might have made sense for early networks whose "domain names" actually named "domains" with multiple hosts, were a single host might have been the webserver. But pure web names? Or even names with multiple additional services like google.com?</p><p>WWW is the single biggest evolutionary baggage in the transition from physical domain hierarchies to logical names.</p></htmltext>
<tokenext>Screw those stupid slashes ; you do n't need to write those out anyway .
What I want to know is who the hell came up with prefixing web addresses with www.I can imagine it might have made sense for early networks whose " domain names " actually named " domains " with multiple hosts , were a single host might have been the webserver .
But pure web names ?
Or even names with multiple additional services like google.com ? WWW is the single biggest evolutionary baggage in the transition from physical domain hierarchies to logical names .</tokentext>
<sentencetext>Screw those stupid slashes; you don't need to write those out anyway.
What I want to know is who the hell came up with prefixing web addresses with www.I can imagine it might have made sense for early networks whose "domain names" actually named "domains" with multiple hosts, were a single host might have been the webserver.
But pure web names?
Or even names with multiple additional services like google.com?WWW is the single biggest evolutionary baggage in the transition from physical domain hierarchies to logical names.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745303</id>
	<title>Re:backslashdot</title>
	<author>catmistake</author>
	<datestamp>1255537500000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>Nah. Slashes are fine, but Microsoft should be sorry about <b>back</b>slashes!</p></div><p>
Thanks for using the proper terminology. There are slashes, and there are backslashes. There are NO 'forward' slashes. And though Microsoft is cupable, I blame Windows users for unnecessarily complicating  the language in a vain attempt to sound like they know what they are talking about. Those extra seven letters are superfluous. It's like saying "CPU processor" or "DNS server." If I see it used again, I'm really going to forwardflip out!</p></div>
	</htmltext>
<tokenext>Nah .
Slashes are fine , but Microsoft should be sorry about backslashes !
Thanks for using the proper terminology .
There are slashes , and there are backslashes .
There are NO 'forward ' slashes .
And though Microsoft is cupable , I blame Windows users for unnecessarily complicating the language in a vain attempt to sound like they know what they are talking about .
Those extra seven letters are superfluous .
It 's like saying " CPU processor " or " DNS server .
" If I see it used again , I 'm really going to forwardflip out !</tokentext>
<sentencetext>Nah.
Slashes are fine, but Microsoft should be sorry about backslashes!
Thanks for using the proper terminology.
There are slashes, and there are backslashes.
There are NO 'forward' slashes.
And though Microsoft is cupable, I blame Windows users for unnecessarily complicating  the language in a vain attempt to sound like they know what they are talking about.
Those extra seven letters are superfluous.
It's like saying "CPU processor" or "DNS server.
" If I see it used again, I'm really going to forwardflip out!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743467</id>
	<title>From the year 2022</title>
	<author>Anonymous</author>
	<datestamp>1255529340000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>I used my time modem to login to the Internet3 in 2022 and pulled this review from cdweggbuy (yes, that's a full URL because people thought it was ok to remove gTLDs and also got rid of that pesky <a href="http:///" title="http" rel="nofollow">http:///</a> [http] for a VeriLogiSoft Computer Interface device.  But of course I got infected by a future virus because my Firefox plugin that matches malicious content didn't know how to identify as a URL.</p><p>Ok back to the present.</p><p>The problem with letting people have what they want is that the majority of people don't understand why things are the way they are.  Tim made the right choice,<br>he just feels that it is wrong now because he's had to hear people complain about it for the past 15-20 years. But when it comes down to it you need some parts of a URL to indicate what something is.</p></htmltext>
<tokenext>I used my time modem to login to the Internet3 in 2022 and pulled this review from cdweggbuy ( yes , that 's a full URL because people thought it was ok to remove gTLDs and also got rid of that pesky http : /// [ http ] for a VeriLogiSoft Computer Interface device .
But of course I got infected by a future virus because my Firefox plugin that matches malicious content did n't know how to identify as a URL.Ok back to the present.The problem with letting people have what they want is that the majority of people do n't understand why things are the way they are .
Tim made the right choice,he just feels that it is wrong now because he 's had to hear people complain about it for the past 15-20 years .
But when it comes down to it you need some parts of a URL to indicate what something is .</tokentext>
<sentencetext>I used my time modem to login to the Internet3 in 2022 and pulled this review from cdweggbuy (yes, that's a full URL because people thought it was ok to remove gTLDs and also got rid of that pesky http:/// [http] for a VeriLogiSoft Computer Interface device.
But of course I got infected by a future virus because my Firefox plugin that matches malicious content didn't know how to identify as a URL.Ok back to the present.The problem with letting people have what they want is that the majority of people don't understand why things are the way they are.
Tim made the right choice,he just feels that it is wrong now because he's had to hear people complain about it for the past 15-20 years.
But when it comes down to it you need some parts of a URL to indicate what something is.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745821</id>
	<title>i like the forward slashes</title>
	<author>karlzt</author>
	<datestamp>1255539540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>i like the forward slashes</htmltext>
<tokenext>i like the forward slashes</tokentext>
<sentencetext>i like the forward slashes</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752299</id>
	<title>Just say dub dub dub</title>
	<author>Anonymous</author>
	<datestamp>1255530180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I heard it used somewhere, knew instantly what was meant, and have used it successfully myself on occasion. Still not quite as easy to say as web, but simpler than double you double you double you.</p><p>What is it with that letter anyway? All the other ones are short and easy, why does w have to be so cumbersome? Especially since it looks like a double v more often than it looks like a double u. Maybe we should just call it wu....vee wu ex why zed (or zee for the yanks...) then we can go wuwuwu dot whatever</p></htmltext>
<tokenext>I heard it used somewhere , knew instantly what was meant , and have used it successfully myself on occasion .
Still not quite as easy to say as web , but simpler than double you double you double you.What is it with that letter anyway ?
All the other ones are short and easy , why does w have to be so cumbersome ?
Especially since it looks like a double v more often than it looks like a double u. Maybe we should just call it wu....vee wu ex why zed ( or zee for the yanks... ) then we can go wuwuwu dot whatever</tokentext>
<sentencetext>I heard it used somewhere, knew instantly what was meant, and have used it successfully myself on occasion.
Still not quite as easy to say as web, but simpler than double you double you double you.What is it with that letter anyway?
All the other ones are short and easy, why does w have to be so cumbersome?
Especially since it looks like a double v more often than it looks like a double u. Maybe we should just call it wu....vee wu ex why zed (or zee for the yanks...) then we can go wuwuwu dot whatever</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743463</id>
	<title>Theres one technical point</title>
	<author>sopssa</author>
	<datestamp>1255529340000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>From technical point of view, *not* having the<nobr> <wbr></nobr>// could create problems more easily. For example if you include port number in the URL and browser or program tries to look at what protocol it is based on value before first :</p><p><b>http</b>://tech.slashdot.org:80/story/09/10/14/1219215/Tim-Berners-Lee-Is-Sorry-About-the-Slashes<br><b>http</b>:tech.slashdot.org:80/story/09/10/14/1219215/Tim-Berners-Lee-Is-Sorry-About-the-Slashes<br>Now if you dont write that http: in browser:<br><b>tech.slashdot.org</b>:80/story/09/10/14/1219215/Tim-Berners-Lee-Is-Sorry-About-the-Slashes</p><p>Now the browser would think the protocol is tech.slashdot.org and tries to pass it to a responsible program instead of loading it. This means you would now need to actually type in the http: which none of us do now. Or dropping general URI support from browsers and IM windows and any other programs (you know all those irc:// spotify: and so on URI's). Or then typing in the<nobr> <wbr></nobr>:80 would be mandatory.</p></htmltext>
<tokenext>From technical point of view , * not * having the // could create problems more easily .
For example if you include port number in the URL and browser or program tries to look at what protocol it is based on value before first : http : //tech.slashdot.org : 80/story/09/10/14/1219215/Tim-Berners-Lee-Is-Sorry-About-the-Slasheshttp : tech.slashdot.org : 80/story/09/10/14/1219215/Tim-Berners-Lee-Is-Sorry-About-the-SlashesNow if you dont write that http : in browser : tech.slashdot.org : 80/story/09/10/14/1219215/Tim-Berners-Lee-Is-Sorry-About-the-SlashesNow the browser would think the protocol is tech.slashdot.org and tries to pass it to a responsible program instead of loading it .
This means you would now need to actually type in the http : which none of us do now .
Or dropping general URI support from browsers and IM windows and any other programs ( you know all those irc : // spotify : and so on URI 's ) .
Or then typing in the : 80 would be mandatory .</tokentext>
<sentencetext>From technical point of view, *not* having the // could create problems more easily.
For example if you include port number in the URL and browser or program tries to look at what protocol it is based on value before first :http://tech.slashdot.org:80/story/09/10/14/1219215/Tim-Berners-Lee-Is-Sorry-About-the-Slasheshttp:tech.slashdot.org:80/story/09/10/14/1219215/Tim-Berners-Lee-Is-Sorry-About-the-SlashesNow if you dont write that http: in browser:tech.slashdot.org:80/story/09/10/14/1219215/Tim-Berners-Lee-Is-Sorry-About-the-SlashesNow the browser would think the protocol is tech.slashdot.org and tries to pass it to a responsible program instead of loading it.
This means you would now need to actually type in the http: which none of us do now.
Or dropping general URI support from browsers and IM windows and any other programs (you know all those irc:// spotify: and so on URI's).
Or then typing in the :80 would be mandatory.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749469</id>
	<title>Re:So Who's Apologizing for 'ttp' ?</title>
	<author>clone53421</author>
	<datestamp>1255512300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Anybody actually uses that? I thought the m. subdomain was always used for mobile devices.</p><p><a href="http://m.wikipedia.org/" title="wikipedia.org">m.wikipedia.org</a> [wikipedia.org], <a href="http://m.google.com/" title="google.com">m.google.com</a> [google.com], etc...</p></htmltext>
<tokenext>Anybody actually uses that ?
I thought the m. subdomain was always used for mobile devices.m.wikipedia.org [ wikipedia.org ] , m.google.com [ google.com ] , etc.. .</tokentext>
<sentencetext>Anybody actually uses that?
I thought the m. subdomain was always used for mobile devices.m.wikipedia.org [wikipedia.org], m.google.com [google.com], etc...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744707</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749455</id>
	<title>Re:pronouncing www is a lot more of a problem</title>
	<author>myowntrueself</author>
	<datestamp>1255512240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Yep. In english speaking countries you're SOL!</p></div><p>I like the way they pronounce 'www' in Slavic countries...</p><p>'vuh vuh vuh' has a kind of dynamism to it, like 'v-v-voooom!!'</p><p>In English, though, many people have taken to pronouncing 'dub dub dub' which just sounds dumb.</p></div>
	</htmltext>
<tokenext>Yep .
In english speaking countries you 're SOL ! I like the way they pronounce 'www ' in Slavic countries...'vuh vuh vuh ' has a kind of dynamism to it , like 'v-v-voooom ! !
'In English , though , many people have taken to pronouncing 'dub dub dub ' which just sounds dumb .</tokentext>
<sentencetext>Yep.
In english speaking countries you're SOL!I like the way they pronounce 'www' in Slavic countries...'vuh vuh vuh' has a kind of dynamism to it, like 'v-v-voooom!!
'In English, though, many people have taken to pronouncing 'dub dub dub' which just sounds dumb.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745053</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748353</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>Anonymous</author>
	<datestamp>1255550520000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Just do what everyone else does, and say 'dub dub dub'.</p></htmltext>
<tokenext>Just do what everyone else does , and say 'dub dub dub' .</tokentext>
<sentencetext>Just do what everyone else does, and say 'dub dub dub'.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497</id>
	<title>yes</title>
	<author>nomadic</author>
	<datestamp>1255529520000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><i>not to mention the human labor and time spent typing those two keystrokes countless millions of times in browser address boxes.'</i>
<br>
<br>
Has anyone had to do that since NINETEEN NINETY FOUR?  Is Berners-Lee still using Mosaic or something?</htmltext>
<tokenext>not to mention the human labor and time spent typing those two keystrokes countless millions of times in browser address boxes .
' Has anyone had to do that since NINETEEN NINETY FOUR ?
Is Berners-Lee still using Mosaic or something ?</tokentext>
<sentencetext>not to mention the human labor and time spent typing those two keystrokes countless millions of times in browser address boxes.
'


Has anyone had to do that since NINETEEN NINETY FOUR?
Is Berners-Lee still using Mosaic or something?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745105</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>AttilaSz</author>
	<datestamp>1255536600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I use "triple double you" when I need to express "www" verbally in English.</p><p>In all other languages that I speak, "we we we" works better.</p></htmltext>
<tokenext>I use " triple double you " when I need to express " www " verbally in English.In all other languages that I speak , " we we we " works better .</tokentext>
<sentencetext>I use "triple double you" when I need to express "www" verbally in English.In all other languages that I speak, "we we we" works better.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743765</id>
	<title>Mosaic?</title>
	<author>Savage-Rabbit</author>
	<datestamp>1255530960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Has anyone had to do that since NINETEEN NINETY FOUR? Is Berners-Lee still using Mosaic or something?</p></div><p>Real nerds browse with telnet to port 80.... You should know that....</p></div>
	</htmltext>
<tokenext>Has anyone had to do that since NINETEEN NINETY FOUR ?
Is Berners-Lee still using Mosaic or something ? Real nerds browse with telnet to port 80.... You should know that... .</tokentext>
<sentencetext>Has anyone had to do that since NINETEEN NINETY FOUR?
Is Berners-Lee still using Mosaic or something?Real nerds browse with telnet to port 80.... You should know that....
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744561</id>
	<title>Re:From the year 2022, or 2084</title>
	<author>TaoPhoenix</author>
	<datestamp>1255534440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>They're playing the "StraightMod" half of a Comedy Act.</p><p>Marking you insightful opens up the way for cool citations.<br><a href="http://en.wikipedia.org/wiki/The\_Final\_Experiment" title="wikipedia.org">http://en.wikipedia.org/wiki/The\_Final\_Experiment</a> [wikipedia.org]<br>Prologue</p><p>The prologue is narrated by the magician Merlin. He explains that scientists living in the future, in the year 2084, have developed a method of sending messages back in time, using a process called 'time telepathy'. Having seen earth narrowly avert destruction from a variety of causes in the time leading up to 2084, humanity's ultimate hope rests with this experiment. These scientists must warn denizens living in the past of the future that awaits them, so that they may take preemptive action to prevent humanity's decline and ultimate destruction.[2]</p></htmltext>
<tokenext>They 're playing the " StraightMod " half of a Comedy Act.Marking you insightful opens up the way for cool citations.http : //en.wikipedia.org/wiki/The \ _Final \ _Experiment [ wikipedia.org ] PrologueThe prologue is narrated by the magician Merlin .
He explains that scientists living in the future , in the year 2084 , have developed a method of sending messages back in time , using a process called 'time telepathy' .
Having seen earth narrowly avert destruction from a variety of causes in the time leading up to 2084 , humanity 's ultimate hope rests with this experiment .
These scientists must warn denizens living in the past of the future that awaits them , so that they may take preemptive action to prevent humanity 's decline and ultimate destruction .
[ 2 ]</tokentext>
<sentencetext>They're playing the "StraightMod" half of a Comedy Act.Marking you insightful opens up the way for cool citations.http://en.wikipedia.org/wiki/The\_Final\_Experiment [wikipedia.org]PrologueThe prologue is narrated by the magician Merlin.
He explains that scientists living in the future, in the year 2084, have developed a method of sending messages back in time, using a process called 'time telepathy'.
Having seen earth narrowly avert destruction from a variety of causes in the time leading up to 2084, humanity's ultimate hope rests with this experiment.
These scientists must warn denizens living in the past of the future that awaits them, so that they may take preemptive action to prevent humanity's decline and ultimate destruction.
[2]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743769</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745071</id>
	<title>Re:to think ..</title>
	<author>Tweenk</author>
	<datestamp>1255536480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I had the impression that Slashdot was named after the notation for the filesystem root on Unix systems, not after an URL.</p></htmltext>
<tokenext>I had the impression that Slashdot was named after the notation for the filesystem root on Unix systems , not after an URL .</tokentext>
<sentencetext>I had the impression that Slashdot was named after the notation for the filesystem root on Unix systems, not after an URL.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743789</id>
	<title>That and saying "backslash"</title>
	<author>Anonymous</author>
	<datestamp>1255531080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>To think of all the time wasted on the radio saying "double-ewe double-ewe double-ewe" on top of idiots calling them "backslash" instead of "slash," the web has eaten away hundreds of decades of man-hours each year.</p></htmltext>
<tokenext>To think of all the time wasted on the radio saying " double-ewe double-ewe double-ewe " on top of idiots calling them " backslash " instead of " slash , " the web has eaten away hundreds of decades of man-hours each year .</tokentext>
<sentencetext>To think of all the time wasted on the radio saying "double-ewe double-ewe double-ewe" on top of idiots calling them "backslash" instead of "slash," the web has eaten away hundreds of decades of man-hours each year.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29751751</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>Anonymous</author>
	<datestamp>1255526340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>In Australia and New Zealand, the "www" is usually pronounced "dubdubdub". Saves six syllables.</p></htmltext>
<tokenext>In Australia and New Zealand , the " www " is usually pronounced " dubdubdub " .
Saves six syllables .</tokentext>
<sentencetext>In Australia and New Zealand, the "www" is usually pronounced "dubdubdub".
Saves six syllables.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746471</id>
	<title>Re:backslashdot</title>
	<author>not-my-real-name</author>
	<datestamp>1255542420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm not sure about CP/M, but the operating systems from DEC used slash for switches (RSTS and VMS being the ones that I'm familiar with).  This probably came from earlier versions and likely even predated CP/M.</p></htmltext>
<tokenext>I 'm not sure about CP/M , but the operating systems from DEC used slash for switches ( RSTS and VMS being the ones that I 'm familiar with ) .
This probably came from earlier versions and likely even predated CP/M .</tokentext>
<sentencetext>I'm not sure about CP/M, but the operating systems from DEC used slash for switches (RSTS and VMS being the ones that I'm familiar with).
This probably came from earlier versions and likely even predated CP/M.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743935</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745863</id>
	<title>Re:DNS</title>
	<author>Anonymous</author>
	<datestamp>1255539720000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Grey book addresses were like this. Grey book was used in mainly on the <a href="http://en.wikipedia.org/wiki/JANET\_NRS" title="wikipedia.org" rel="nofollow">JANET</a> [wikipedia.org] network in the UK, though there were gateways to the Internet before JANET was phased out.</p></htmltext>
<tokenext>Grey book addresses were like this .
Grey book was used in mainly on the JANET [ wikipedia.org ] network in the UK , though there were gateways to the Internet before JANET was phased out .</tokentext>
<sentencetext>Grey book addresses were like this.
Grey book was used in mainly on the JANET [wikipedia.org] network in the UK, though there were gateways to the Internet before JANET was phased out.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651</id>
	<title>Re:pronouncing www is a lot more of a problem</title>
	<author>Anonymous</author>
	<datestamp>1255530480000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Every time I set-up a sub-domain for work I always have to tell my boss "http://subdomain." out loud first, in the hope that he'll not prefix "www".</p><p>Sometimes he still just does both, then asks me why it isn't working. This results in a lengthy conversation where we're both saying "http colon slash slash" and "www" to each other. Makes me want to stab him in the face.</p></htmltext>
<tokenext>Every time I set-up a sub-domain for work I always have to tell my boss " http : //subdomain .
" out loud first , in the hope that he 'll not prefix " www " .Sometimes he still just does both , then asks me why it is n't working .
This results in a lengthy conversation where we 're both saying " http colon slash slash " and " www " to each other .
Makes me want to stab him in the face .</tokentext>
<sentencetext>Every time I set-up a sub-domain for work I always have to tell my boss "http://subdomain.
" out loud first, in the hope that he'll not prefix "www".Sometimes he still just does both, then asks me why it isn't working.
This results in a lengthy conversation where we're both saying "http colon slash slash" and "www" to each other.
Makes me want to stab him in the face.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746157</id>
	<title>Re:Now explain triple-slashes</title>
	<author>Ark42</author>
	<datestamp>1255540920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>^THIS^
There is a reason file:/// urls always have 3 slashes and other protocols use 2.
Additionally, <a href="http:///file.html" title="file.html">http:///file.html</a> [file.html] should be more or less an alias for <a href="http://localhost/file.html" title="localhost">http://localhost/file.html</a> [localhost] in theory.
It is also very similar to the \\computer\fileshare syntax Windows uses. Just think of Explorer as assuming the default protocol is smb: instead of how your web browser will assume http:
If Explorer used regular slashes, would it too much to type smb://server/share/path/file.doc ?</htmltext>
<tokenext>^ THIS ^ There is a reason file : /// urls always have 3 slashes and other protocols use 2 .
Additionally , http : ///file.html [ file.html ] should be more or less an alias for http : //localhost/file.html [ localhost ] in theory .
It is also very similar to the \ \ computer \ fileshare syntax Windows uses .
Just think of Explorer as assuming the default protocol is smb : instead of how your web browser will assume http : If Explorer used regular slashes , would it too much to type smb : //server/share/path/file.doc ?</tokentext>
<sentencetext>^THIS^
There is a reason file:/// urls always have 3 slashes and other protocols use 2.
Additionally, http:///file.html [file.html] should be more or less an alias for http://localhost/file.html [localhost] in theory.
It is also very similar to the \\computer\fileshare syntax Windows uses.
Just think of Explorer as assuming the default protocol is smb: instead of how your web browser will assume http:
If Explorer used regular slashes, would it too much to type smb://server/share/path/file.doc ?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29753267</id>
	<title>save a tree with a CONTROL key</title>
	<author>Shadotruth</author>
	<datestamp>1255539660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>just type the name of the company (if you know its a<nobr> <wbr></nobr>.com) and hold control down while hitting enter all the<nobr> <wbr></nobr>://blahblahs gets autofilled in for you. atleast it works for<nobr> <wbr></nobr>.com not sure if there is a shortcut for others.....example would be type google....'hit control enter'<nobr> <wbr></nobr>.....the almighty godggle will open without any tree killing and all your slashes and dashes and dots will be there............godggle improved now with free instant pestering  !</htmltext>
<tokenext>just type the name of the company ( if you know its a .com ) and hold control down while hitting enter all the : //blahblahs gets autofilled in for you .
atleast it works for .com not sure if there is a shortcut for others.....example would be type google....'hit control enter ' .....the almighty godggle will open without any tree killing and all your slashes and dashes and dots will be there............godggle improved now with free instant pestering !</tokentext>
<sentencetext>just type the name of the company (if you know its a .com) and hold control down while hitting enter all the ://blahblahs gets autofilled in for you.
atleast it works for .com not sure if there is a shortcut for others.....example would be type google....'hit control enter' .....the almighty godggle will open without any tree killing and all your slashes and dashes and dots will be there............godggle improved now with free instant pestering  !</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745369</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>danlip</author>
	<datestamp>1255537740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>But it is faster to type www than web.  And you can say "dubya dubya dubya"<nobr> <wbr></nobr>:-)</p></htmltext>
<tokenext>But it is faster to type www than web .
And you can say " dubya dubya dubya " : - )</tokentext>
<sentencetext>But it is faster to type www than web.
And you can say "dubya dubya dubya" :-)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748887</id>
	<title>Re:DNS</title>
	<author>grotgrot</author>
	<datestamp>1255552800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The UK academic network <a href="http://en.wikipedia.org/wiki/JANET" title="wikipedia.org">JANET</a> [wikipedia.org] was originally setup to have domain names in reverse and although it may seem to make logical sense it wasn't human friendly.  Also look at how we address snail mail - same order as current DNS.  For completion you can make things more intelligent pretty much like how the Firefox address bar works.  You'll also find that most DNS servers do not allow zone transfers - for example neither<nobr> <wbr></nobr>.edu nor wustl.edu allow it.</p></htmltext>
<tokenext>The UK academic network JANET [ wikipedia.org ] was originally setup to have domain names in reverse and although it may seem to make logical sense it was n't human friendly .
Also look at how we address snail mail - same order as current DNS .
For completion you can make things more intelligent pretty much like how the Firefox address bar works .
You 'll also find that most DNS servers do not allow zone transfers - for example neither .edu nor wustl.edu allow it .</tokentext>
<sentencetext>The UK academic network JANET [wikipedia.org] was originally setup to have domain names in reverse and although it may seem to make logical sense it wasn't human friendly.
Also look at how we address snail mail - same order as current DNS.
For completion you can make things more intelligent pretty much like how the Firefox address bar works.
You'll also find that most DNS servers do not allow zone transfers - for example neither .edu nor wustl.edu allow it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746333</id>
	<title>Re:Theres one technical point</title>
	<author>Anonymous</author>
	<datestamp>1255541580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Good point, TBL has nothing to apologize for (his apology looked very tongue-in-cheek anyway).  The URL scheme is nice and elegant, with two slashes denoting "next item refers to a namespace from at the root" and it beats the hell out of the previous attempts at uniform resource identifiers (there are some ancient RFCs on the subject, the syntax will make you run screaming).</p><p>URLs are just slightly bureaucratic, and user interfaces (i.e. browsers) fix even that.  Problem solved.</p></htmltext>
<tokenext>Good point , TBL has nothing to apologize for ( his apology looked very tongue-in-cheek anyway ) .
The URL scheme is nice and elegant , with two slashes denoting " next item refers to a namespace from at the root " and it beats the hell out of the previous attempts at uniform resource identifiers ( there are some ancient RFCs on the subject , the syntax will make you run screaming ) .URLs are just slightly bureaucratic , and user interfaces ( i.e .
browsers ) fix even that .
Problem solved .</tokentext>
<sentencetext>Good point, TBL has nothing to apologize for (his apology looked very tongue-in-cheek anyway).
The URL scheme is nice and elegant, with two slashes denoting "next item refers to a namespace from at the root" and it beats the hell out of the previous attempts at uniform resource identifiers (there are some ancient RFCs on the subject, the syntax will make you run screaming).URLs are just slightly bureaucratic, and user interfaces (i.e.
browsers) fix even that.
Problem solved.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743775</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743675</id>
	<title>I thought there was a point to the two slashes</title>
	<author>magloca</author>
	<datestamp>1255530600000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>Back when I wrote a thesis on dissemination of company-internal information via the world-wide web, in 1994 or so, I remember stating that originally, an indication of which network protocol to use was meant to go between the slashes. But since, in the real world, the network protocol was always TCP/IP, this was made the default and whatever was once put between the slashes was dropped.</p><p>Of course, I don't remember the source or anything.</p></htmltext>
<tokenext>Back when I wrote a thesis on dissemination of company-internal information via the world-wide web , in 1994 or so , I remember stating that originally , an indication of which network protocol to use was meant to go between the slashes .
But since , in the real world , the network protocol was always TCP/IP , this was made the default and whatever was once put between the slashes was dropped.Of course , I do n't remember the source or anything .</tokentext>
<sentencetext>Back when I wrote a thesis on dissemination of company-internal information via the world-wide web, in 1994 or so, I remember stating that originally, an indication of which network protocol to use was meant to go between the slashes.
But since, in the real world, the network protocol was always TCP/IP, this was made the default and whatever was once put between the slashes was dropped.Of course, I don't remember the source or anything.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29751037</id>
	<title>lol save paper?</title>
	<author>Anonymous</author>
	<datestamp>1255520820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>How is removing "//" going to save paper?  I doubt anyone has ever gone onto a second page because of 2 extra characters in a URL.</p></htmltext>
<tokenext>How is removing " // " going to save paper ?
I doubt anyone has ever gone onto a second page because of 2 extra characters in a URL .</tokentext>
<sentencetext>How is removing "//" going to save paper?
I doubt anyone has ever gone onto a second page because of 2 extra characters in a URL.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745195</id>
	<title>Re:Now explain triple-slashes</title>
	<author>Hurricane78</author>
	<datestamp>1255537020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The triple slash actually is an error in an otherwise constant scheme. Because if you think as the<nobr> <wbr></nobr>// at the beginning as the root of the network, just like / at the beginning is the root of your UNIX file path, then it should be file:/[path], as long as it's a absolute path on your system, and file:[path] for relative ones.</p></htmltext>
<tokenext>The triple slash actually is an error in an otherwise constant scheme .
Because if you think as the // at the beginning as the root of the network , just like / at the beginning is the root of your UNIX file path , then it should be file : / [ path ] , as long as it 's a absolute path on your system , and file : [ path ] for relative ones .</tokentext>
<sentencetext>The triple slash actually is an error in an otherwise constant scheme.
Because if you think as the // at the beginning as the root of the network, just like / at the beginning is the root of your UNIX file path, then it should be file:/[path], as long as it's a absolute path on your system, and file:[path] for relative ones.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750817</id>
	<title>Re:DNS</title>
	<author>Jesus\_666</author>
	<datestamp>1255519440000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>What's natural about www.example.com? It looks nothing like any other kind of address. Phone numbers maybe but those are rendered in a very non-uniform way and ".", "/", "-" and " " are all very common separators there.<br>
<br>
You just feel that that format feels natural for domain names because that's the way domain names are usually written. If Berners-Lee had went with com/example/www, you'd find "//com/example" to be the natural format.</htmltext>
<tokenext>What 's natural about www.example.com ?
It looks nothing like any other kind of address .
Phone numbers maybe but those are rendered in a very non-uniform way and " .
" , " / " , " - " and " " are all very common separators there .
You just feel that that format feels natural for domain names because that 's the way domain names are usually written .
If Berners-Lee had went with com/example/www , you 'd find " //com/example " to be the natural format .</tokentext>
<sentencetext>What's natural about www.example.com?
It looks nothing like any other kind of address.
Phone numbers maybe but those are rendered in a very non-uniform way and ".
", "/", "-" and " " are all very common separators there.
You just feel that that format feels natural for domain names because that's the way domain names are usually written.
If Berners-Lee had went with com/example/www, you'd find "//com/example" to be the natural format.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746043</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29753679</id>
	<title>Re:From the year 2022</title>
	<author>Anonymous</author>
	<datestamp>1255545300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If so, can we get an apology from all the media-folk who have worn down our eardrums and patience by unecessarily saying "forward slash" for 20 years?</p></htmltext>
<tokenext>If so , can we get an apology from all the media-folk who have worn down our eardrums and patience by unecessarily saying " forward slash " for 20 years ?</tokentext>
<sentencetext>If so, can we get an apology from all the media-folk who have worn down our eardrums and patience by unecessarily saying "forward slash" for 20 years?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743467</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752241</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>grubwort</author>
	<datestamp>1255529760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>In your mother tongue would the translation of "World Wide Web" still have three Ws?</htmltext>
<tokenext>In your mother tongue would the translation of " World Wide Web " still have three Ws ?</tokentext>
<sentencetext>In your mother tongue would the translation of "World Wide Web" still have three Ws?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744547</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744437</id>
	<title>Emo slashes</title>
	<author>Conchobair</author>
	<datestamp>1255533960000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>The slashes are the only way I can make myself feel...</htmltext>
<tokenext>The slashes are the only way I can make myself feel.. .</tokentext>
<sentencetext>The slashes are the only way I can make myself feel...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752731</id>
	<title>It's a special case of a more general system</title>
	<author>hendrikboom</author>
	<datestamp>1255534020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I once heard that it was based on an older convention about numbers of slashes. Using multiple slashes eats your way to be root until you meet something else with more slashes (or was it at least as many? I forget)

So if you're in a context like<nobr> <wbr></nobr>///foo//bar/f
and you append  a<nobr> <wbr></nobr>//onion/cow/patty
the resulting<nobr> <wbr></nobr>///foo//bar/f//onion/cow/patty
reduces to<nobr> <wbr></nobr>///foo/onion/cow/patty
(or was it<nobr> <wbr></nobr>///foo//bar//onion/cow/patty ? I forget)

So the number of slashes was a way of indicating what level of the naming hierarchy you were replacing.

But the more general concept was forgotten somewhere along the line.</htmltext>
<tokenext>I once heard that it was based on an older convention about numbers of slashes .
Using multiple slashes eats your way to be root until you meet something else with more slashes ( or was it at least as many ?
I forget ) So if you 're in a context like ///foo//bar/f and you append a //onion/cow/patty the resulting ///foo//bar/f//onion/cow/patty reduces to ///foo/onion/cow/patty ( or was it ///foo//bar//onion/cow/patty ?
I forget ) So the number of slashes was a way of indicating what level of the naming hierarchy you were replacing .
But the more general concept was forgotten somewhere along the line .</tokentext>
<sentencetext>I once heard that it was based on an older convention about numbers of slashes.
Using multiple slashes eats your way to be root until you meet something else with more slashes (or was it at least as many?
I forget)

So if you're in a context like ///foo//bar/f
and you append  a //onion/cow/patty
the resulting ///foo//bar/f//onion/cow/patty
reduces to ///foo/onion/cow/patty
(or was it ///foo//bar//onion/cow/patty ?
I forget)

So the number of slashes was a way of indicating what level of the naming hierarchy you were replacing.
But the more general concept was forgotten somewhere along the line.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744367</id>
	<title>Re:Just for the looks?</title>
	<author>commodore64\_love</author>
	<datestamp>1255533660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Apple<nobr> <wbr></nobr>//e?  I thought it was Apple ][e?   Or possibly Apple IIe?  I'm so confused.  (reaches for Shakespeare folio).  "To be or not to be..." ahh better.</p></htmltext>
<tokenext>Apple //e ?
I thought it was Apple ] [ e ?
Or possibly Apple IIe ?
I 'm so confused .
( reaches for Shakespeare folio ) .
" To be or not to be... " ahh better .</tokentext>
<sentencetext>Apple //e?
I thought it was Apple ][e?
Or possibly Apple IIe?
I'm so confused.
(reaches for Shakespeare folio).
"To be or not to be..." ahh better.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743949</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749025</id>
	<title>Yeah, right.</title>
	<author>PPH</author>
	<datestamp>1255553460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>And then where would all of us be? Posting our witty remarks on the Dot discussion system.</htmltext>
<tokenext>And then where would all of us be ?
Posting our witty remarks on the Dot discussion system .</tokentext>
<sentencetext>And then where would all of us be?
Posting our witty remarks on the Dot discussion system.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746521</id>
	<title>Re:Theres one technical point</title>
	<author>Tarlus</author>
	<datestamp>1255542600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>On the other hand: Who types <a href="http:///" title="http">http:///</a> [http] anyway?</p></div><p>I hear ya. Every web browser I've used since '96 has automatically inserted the protocol when an address is typed into the URL field. (And probably IE and Netscape all the way back to their 1.x days; correct me if I'm wrong.) So I remain unphased by the number of slashes in the protocol.</p></div>
	</htmltext>
<tokenext>On the other hand : Who types http : /// [ http ] anyway ? I hear ya .
Every web browser I 've used since '96 has automatically inserted the protocol when an address is typed into the URL field .
( And probably IE and Netscape all the way back to their 1.x days ; correct me if I 'm wrong .
) So I remain unphased by the number of slashes in the protocol .</tokentext>
<sentencetext>On the other hand: Who types http:/// [http] anyway?I hear ya.
Every web browser I've used since '96 has automatically inserted the protocol when an address is typed into the URL field.
(And probably IE and Netscape all the way back to their 1.x days; correct me if I'm wrong.
) So I remain unphased by the number of slashes in the protocol.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743775</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744947</id>
	<title>How big of a problem is this really</title>
	<author>sean.peters</author>
	<datestamp>1255536000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Aren't most people getting to websites via 1) bookmarks 2) links from other sites 3) google searches, etc, etc? And for 90\% of the remaining sites (https: being the obvious exception) you don't have to type the "http://" at all. And as for the dead trees... well, maybe if people were printing page after page of URLs, I could see it. But for real world print jobs, I have a hard time believing that those few extra characters are causing the job to spill over into an additional page very often.</htmltext>
<tokenext>Are n't most people getting to websites via 1 ) bookmarks 2 ) links from other sites 3 ) google searches , etc , etc ?
And for 90 \ % of the remaining sites ( https : being the obvious exception ) you do n't have to type the " http : // " at all .
And as for the dead trees... well , maybe if people were printing page after page of URLs , I could see it .
But for real world print jobs , I have a hard time believing that those few extra characters are causing the job to spill over into an additional page very often .</tokentext>
<sentencetext>Aren't most people getting to websites via 1) bookmarks 2) links from other sites 3) google searches, etc, etc?
And for 90\% of the remaining sites (https: being the obvious exception) you don't have to type the "http://" at all.
And as for the dead trees... well, maybe if people were printing page after page of URLs, I could see it.
But for real world print jobs, I have a hard time believing that those few extra characters are causing the job to spill over into an additional page very often.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745133</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>Hurricane78</author>
	<datestamp>1255536780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Well, nowadays you recognize a noob by seeing how he wants to put a www in front of everything that hasn't one. I never used www subdomains for my servers. There's no point in it. What else should it connect to than a webserver? And if, then there are ports to solve that.</p></htmltext>
<tokenext>Well , nowadays you recognize a noob by seeing how he wants to put a www in front of everything that has n't one .
I never used www subdomains for my servers .
There 's no point in it .
What else should it connect to than a webserver ?
And if , then there are ports to solve that .</tokentext>
<sentencetext>Well, nowadays you recognize a noob by seeing how he wants to put a www in front of everything that hasn't one.
I never used www subdomains for my servers.
There's no point in it.
What else should it connect to than a webserver?
And if, then there are ports to solve that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744153</id>
	<title>Apologies</title>
	<author>arikol</author>
	<datestamp>1255532760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>More to the point, isn't he in fact just apologizing for unleashing Slashdot on the world?</p></htmltext>
<tokenext>More to the point , is n't he in fact just apologizing for unleashing Slashdot on the world ?</tokentext>
<sentencetext>More to the point, isn't he in fact just apologizing for unleashing Slashdot on the world?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750573</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>Trogre</author>
	<datestamp>1255518000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's not uncommon to use "dub dub dub", or for those who want to avoid sounding like boy scouts, some people still regularly use "world wide web".</p></htmltext>
<tokenext>It 's not uncommon to use " dub dub dub " , or for those who want to avoid sounding like boy scouts , some people still regularly use " world wide web " .</tokentext>
<sentencetext>It's not uncommon to use "dub dub dub", or for those who want to avoid sounding like boy scouts, some people still regularly use "world wide web".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</id>
	<title>DNS</title>
	<author>redhog</author>
	<datestamp>1255530900000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>What I wonder is why the designers of DNS put the name in reverse? If the name had been in most-significant-first order, one could have tabcompleted it properly (using history and maybe zonetransfers of smaller zones). Also, if http had included a way to get \_parsable\_ directory listings, the tab-completion could have gone even further...<br><br>http://edu.wu&lt;TAB&gt;<br>http://edu.wustl<br>http://edu.wustl.wu&lt;TAB&gt;<br>http://edu.wustl.wuarchive<br>http://edu.wustl.wuarchive/p&lt;TAB&gt;l&lt;TAB&gt;d&lt;TAB&gt;f&lt;TAB&gt;<br>http://edu.wustl.wuarchive/pub/linux/distributions/fedora</htmltext>
<tokenext>What I wonder is why the designers of DNS put the name in reverse ?
If the name had been in most-significant-first order , one could have tabcompleted it properly ( using history and maybe zonetransfers of smaller zones ) .
Also , if http had included a way to get \ _parsable \ _ directory listings , the tab-completion could have gone even further...http : //edu.wuhttp : //edu.wustlhttp : //edu.wustl.wuhttp : //edu.wustl.wuarchivehttp : //edu.wustl.wuarchive/pldfhttp : //edu.wustl.wuarchive/pub/linux/distributions/fedora</tokentext>
<sentencetext>What I wonder is why the designers of DNS put the name in reverse?
If the name had been in most-significant-first order, one could have tabcompleted it properly (using history and maybe zonetransfers of smaller zones).
Also, if http had included a way to get \_parsable\_ directory listings, the tab-completion could have gone even further...http://edu.wuhttp://edu.wustlhttp://edu.wustl.wuhttp://edu.wustl.wuarchivehttp://edu.wustl.wuarchive/pldfhttp://edu.wustl.wuarchive/pub/linux/distributions/fedora</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745297</id>
	<title>Re:Theres one technical point</title>
	<author>clone53421</author>
	<datestamp>1255537440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The www is just a subdomain. We typically assume it'll be the same thing as the URL without the www, but depending on the server's configuration that assumption may or may not be correct.</p><p>Besides which, I had a moment of pedantic outrage when I read "the 'www' in every internet website address". Obviously they're overlooking maps.google.com, answers.yahoo.com, en.wikipedia.org, tech.slashdot.org, oh, I could go on...</p></htmltext>
<tokenext>The www is just a subdomain .
We typically assume it 'll be the same thing as the URL without the www , but depending on the server 's configuration that assumption may or may not be correct.Besides which , I had a moment of pedantic outrage when I read " the 'www ' in every internet website address " .
Obviously they 're overlooking maps.google.com , answers.yahoo.com , en.wikipedia.org , tech.slashdot.org , oh , I could go on.. .</tokentext>
<sentencetext>The www is just a subdomain.
We typically assume it'll be the same thing as the URL without the www, but depending on the server's configuration that assumption may or may not be correct.Besides which, I had a moment of pedantic outrage when I read "the 'www' in every internet website address".
Obviously they're overlooking maps.google.com, answers.yahoo.com, en.wikipedia.org, tech.slashdot.org, oh, I could go on...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744757</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744299</id>
	<title>Re:DNS</title>
	<author>isj</author>
	<datestamp>1255533420000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>My guess is that having the domains in that order allows you copy them directorly to/from DNS packets.<br>And the reason for the order in the DNS packets is that it allows compression by back-references. Roughly if a packet contains multiple names:<br>
&nbsp; &nbsp; some.domain.example.com<br>
&nbsp; &nbsp; other.domain.example.com<br>can be transmitted like:<br>
&nbsp; &nbsp; some.domain.example.com<br>
&nbsp; &nbsp; other&lt;go back in packet at offset X&gt;</p><p>See RFC 1035 section 4.1.4 for details.</p></htmltext>
<tokenext>My guess is that having the domains in that order allows you copy them directorly to/from DNS packets.And the reason for the order in the DNS packets is that it allows compression by back-references .
Roughly if a packet contains multiple names :     some.domain.example.com     other.domain.example.comcan be transmitted like :     some.domain.example.com     otherSee RFC 1035 section 4.1.4 for details .</tokentext>
<sentencetext>My guess is that having the domains in that order allows you copy them directorly to/from DNS packets.And the reason for the order in the DNS packets is that it allows compression by back-references.
Roughly if a packet contains multiple names:
    some.domain.example.com
    other.domain.example.comcan be transmitted like:
    some.domain.example.com
    otherSee RFC 1035 section 4.1.4 for details.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531</id>
	<title>backslashdot</title>
	<author>thhamm</author>
	<datestamp>1255529760000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>Nah. Slashes are fine, but Microsoft should be sorry about <b>back</b>slashes!</htmltext>
<tokenext>Nah .
Slashes are fine , but Microsoft should be sorry about backslashes !</tokentext>
<sentencetext>Nah.
Slashes are fine, but Microsoft should be sorry about backslashes!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744547</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>cerberusss</author>
	<datestamp>1255534440000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>That's just your language (which is arguably the dominant language). In my mother tongue, the 'w' is pronounced as [wey].</p></htmltext>
<tokenext>That 's just your language ( which is arguably the dominant language ) .
In my mother tongue , the 'w ' is pronounced as [ wey ] .</tokentext>
<sentencetext>That's just your language (which is arguably the dominant language).
In my mother tongue, the 'w' is pronounced as [wey].</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744763</id>
	<title>Re:Now explain triple-slashes</title>
	<author>Anonymous</author>
	<datestamp>1255535280000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>The structure of a URL is:<br> <br>

protocol://domain/path<br> <br>

When you use the 'file' protocol, <b>there is no domain</b>, there is only a path. Thus the domain part of the URL is omitted and you get a triple-slash.</p></div><p> <b>Wrong</b>. Please read RFC1738 again. It specifically states:</p><p><div class="quote"><p>3.10 FILES<br> <br><nobr> <wbr></nobr>...<br> <br>

 A file URL takes the form:<br>

       file://&lt;host&gt;/&lt;path&gt;<br> <br><nobr> <wbr></nobr>...<br> <br>

   As a special case, &lt;host&gt; can be the string "localhost" or the <b>empty<br>
   string</b>; this is interpreted as `the machine from which the URL is<br>
   being interpreted'.</p></div></div>
	</htmltext>
<tokenext>The structure of a URL is : protocol : //domain/path When you use the 'file ' protocol , there is no domain , there is only a path .
Thus the domain part of the URL is omitted and you get a triple-slash .
Wrong. Please read RFC1738 again .
It specifically states : 3.10 FILES .. . A file URL takes the form : file : /// .. . As a special case , can be the string " localhost " or the empty string ; this is interpreted as ` the machine from which the URL is being interpreted' .</tokentext>
<sentencetext>The structure of a URL is: 

protocol://domain/path 

When you use the 'file' protocol, there is no domain, there is only a path.
Thus the domain part of the URL is omitted and you get a triple-slash.
Wrong. Please read RFC1738 again.
It specifically states:3.10 FILES  ... 

 A file URL takes the form:

       file:///  ... 

   As a special case,  can be the string "localhost" or the empty
   string; this is interpreted as `the machine from which the URL is
   being interpreted'.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749547</id>
	<title>Waste Not</title>
	<author>PingPongBoy</author>
	<datestamp>1255512720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><em>Look at all the paper and trees, he said, that could have been saved if people had not had to write or type out those slashes on paper over the years </em></p><p>The two sets {1, 1x, 2, 2x, 3, 3x,<nobr> <wbr></nobr>...} and {1, 2, 3,<nobr> <wbr></nobr>...} are both infinite. If both sets represent the pages counts on printouts of websites, and the first set contains both the content and the waste due to the extra junk on the pages, an argument may be made that the waste would be infinitely less if there wasn't so much extra crap on each page.</p><p>The extra stuff is what drives the finances of the Internet, but it is infinitely more costly in bandwidth, time consumed, memory, CPU cycles, etc.</p><p>Since technology keeps improving, we condone all this waste. Indeed without all the junk, there would be little incentive to keep improving technology - who would personally sustain usage of the full bandwidth they're paying for? It's paradoxical. We can't live a good life without knowing how to waste the things we can't use.</p></htmltext>
<tokenext>Look at all the paper and trees , he said , that could have been saved if people had not had to write or type out those slashes on paper over the years The two sets { 1 , 1x , 2 , 2x , 3 , 3x , ... } and { 1 , 2 , 3 , ... } are both infinite .
If both sets represent the pages counts on printouts of websites , and the first set contains both the content and the waste due to the extra junk on the pages , an argument may be made that the waste would be infinitely less if there was n't so much extra crap on each page.The extra stuff is what drives the finances of the Internet , but it is infinitely more costly in bandwidth , time consumed , memory , CPU cycles , etc.Since technology keeps improving , we condone all this waste .
Indeed without all the junk , there would be little incentive to keep improving technology - who would personally sustain usage of the full bandwidth they 're paying for ?
It 's paradoxical .
We ca n't live a good life without knowing how to waste the things we ca n't use .</tokentext>
<sentencetext>Look at all the paper and trees, he said, that could have been saved if people had not had to write or type out those slashes on paper over the years The two sets {1, 1x, 2, 2x, 3, 3x, ...} and {1, 2, 3, ...} are both infinite.
If both sets represent the pages counts on printouts of websites, and the first set contains both the content and the waste due to the extra junk on the pages, an argument may be made that the waste would be infinitely less if there wasn't so much extra crap on each page.The extra stuff is what drives the finances of the Internet, but it is infinitely more costly in bandwidth, time consumed, memory, CPU cycles, etc.Since technology keeps improving, we condone all this waste.
Indeed without all the junk, there would be little incentive to keep improving technology - who would personally sustain usage of the full bandwidth they're paying for?
It's paradoxical.
We can't live a good life without knowing how to waste the things we can't use.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29753617</id>
	<title>base url helps slightly</title>
	<author>u64</author>
	<datestamp>1255544580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This html works.</p><p>base href=http://&gt;<br>body background=//www.w3schools.com/graphics/images/back/sky6.jpg&gt;<br>img src=//www.w3schools.com/images/stickman.gif&gt;<br>img src=http://www.w3schools.com/images/stickman.gif&gt;</p><p>But it brakes all relative paths. So it doesnt automatically saves Bytes<br>everywhere.</p></htmltext>
<tokenext>This html works.base href = http : // &gt; body background = //www.w3schools.com/graphics/images/back/sky6.jpg &gt; img src = //www.w3schools.com/images/stickman.gif &gt; img src = http : //www.w3schools.com/images/stickman.gif &gt; But it brakes all relative paths .
So it doesnt automatically saves Byteseverywhere .</tokentext>
<sentencetext>This html works.base href=http://&gt;body background=//www.w3schools.com/graphics/images/back/sky6.jpg&gt;img src=//www.w3schools.com/images/stickman.gif&gt;img src=http://www.w3schools.com/images/stickman.gif&gt;But it brakes all relative paths.
So it doesnt automatically saves Byteseverywhere.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745053</id>
	<title>Re:pronouncing www is a lot more of a problem</title>
	<author>bickerdyke</author>
	<datestamp>1255536480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yep. In english speaking countries you're SOL!</p><p>I can pronounce wwww faster than a single Double-U.</p></htmltext>
<tokenext>Yep .
In english speaking countries you 're SOL ! I can pronounce wwww faster than a single Double-U .</tokentext>
<sentencetext>Yep.
In english speaking countries you're SOL!I can pronounce wwww faster than a single Double-U.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744611</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>Anonymous</author>
	<datestamp>1255534680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>not twice, three times as long!</p><p>"The World Wide Web is the only thing I know of whose shortened form takes three times longer to say than what it's short for." (Douglas Adams)</p></htmltext>
<tokenext>not twice , three times as long !
" The World Wide Web is the only thing I know of whose shortened form takes three times longer to say than what it 's short for .
" ( Douglas Adams )</tokentext>
<sentencetext>not twice, three times as long!
"The World Wide Web is the only thing I know of whose shortened form takes three times longer to say than what it's short for.
" (Douglas Adams)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743927</id>
	<title>Re:to think ..</title>
	<author>Rude Turnip</author>
	<datestamp>1255531800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Colondot:  IT Stinks Sometimes</p></htmltext>
<tokenext>Colondot : IT Stinks Sometimes</tokentext>
<sentencetext>Colondot:  IT Stinks Sometimes</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743633</id>
	<title>Saving energy</title>
	<author>twoblink</author>
	<datestamp>1255530420000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>0</modscore>
	<htmltext><p>If microsoft set the default screen saver to blank in 5 minutes, we'd save billions a year in electricity around the world.  The<nobr> <wbr></nobr>// ain't nothing compared to that.</p></htmltext>
<tokenext>If microsoft set the default screen saver to blank in 5 minutes , we 'd save billions a year in electricity around the world .
The // ai n't nothing compared to that .</tokentext>
<sentencetext>If microsoft set the default screen saver to blank in 5 minutes, we'd save billions a year in electricity around the world.
The // ain't nothing compared to that.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746139</id>
	<title>Re:pronouncing www is a lot more of a problem</title>
	<author>b4dc0d3r</author>
	<datestamp>1255540800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Write it on a post-it note.</p><p>Or if you're virtual send it in e-mail.</p><p>If asked for it, don't say it out loud, tell him you'll e-mail or write or IM with it.</p><p>Break the cycle of abuse.</p></htmltext>
<tokenext>Write it on a post-it note.Or if you 're virtual send it in e-mail.If asked for it , do n't say it out loud , tell him you 'll e-mail or write or IM with it.Break the cycle of abuse .</tokentext>
<sentencetext>Write it on a post-it note.Or if you're virtual send it in e-mail.If asked for it, don't say it out loud, tell him you'll e-mail or write or IM with it.Break the cycle of abuse.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748059</id>
	<title>Re:DNS</title>
	<author>Ant P.</author>
	<datestamp>1255549440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>It turned out the shorthand "//www.example.com/foo/bar/baz" is rarely used</p></div><p>view-source on this page.</p></div>
	</htmltext>
<tokenext>It turned out the shorthand " //www.example.com/foo/bar/baz " is rarely usedview-source on this page .</tokentext>
<sentencetext>It turned out the shorthand "//www.example.com/foo/bar/baz" is rarely usedview-source on this page.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747863</id>
	<title>Re:DNS</title>
	<author>nine-times</author>
	<datestamp>1255548540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If the syntax was that way, how would we tell the difference between <a href="http://www.example.com/" title="example.com">http://www.example.com/</a> [example.com] and <a href="http://example.com/www/" title="example.com">http://example.com/www/</a> [example.com]?
</p><p>I'm probably just missing the point.  Still, it could have easily been <a href="http:com.example.www" title="example.www">http:com.example.www</a> [example.www] and <a href="http:com.example/www" title="com.example">http:com.example/www</a> [com.example].  At least then people might understand the structure of those names better.</p></htmltext>
<tokenext>If the syntax was that way , how would we tell the difference between http : //www.example.com/ [ example.com ] and http : //example.com/www/ [ example.com ] ?
I 'm probably just missing the point .
Still , it could have easily been http : com.example.www [ example.www ] and http : com.example/www [ com.example ] .
At least then people might understand the structure of those names better .</tokentext>
<sentencetext>If the syntax was that way, how would we tell the difference between http://www.example.com/ [example.com] and http://example.com/www/ [example.com]?
I'm probably just missing the point.
Still, it could have easily been http:com.example.www [example.www] and http:com.example/www [com.example].
At least then people might understand the structure of those names better.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745461</id>
	<title>"slash-slash" blog site</title>
	<author>peter303</author>
	<datestamp>1255538100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>A nice name for a new blog site.  Maybe I'll create it.</htmltext>
<tokenext>A nice name for a new blog site .
Maybe I 'll create it .</tokentext>
<sentencetext>A nice name for a new blog site.
Maybe I'll create it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744071</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>molecular</author>
	<datestamp>1255532400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I had occasion to have an email conversation with Berners-Lee at one time (he bought a license for a program of mine), and I asked if he regretted choosing "www" instead of "web". I was very surprised that this was not something he'd change if he could do the whole thing over<nobr> <wbr></nobr>...</p><p>Saying "double u double u double u" takes about twice as long as saying "web" so that would have been far more beneficial than worrying about the slashes.</p><p>There was a bit of a drive to use "web" some years ago, but unfortunately that fizzled..</p></div><p>the ages when webservers where on a different machine than the ftp servers are long gone. so why use subdomains there anyway.<br>I have to agree with a previous post. Some people, when I tell them a web-address, they have already put "www." in their browser an happily assume it would somehow belong there and I would just skip it (even if I say: "http://domain.tld") and then complain when the site is not found. I could kill in such moments, especially when it's over the phone.</p></div>
	</htmltext>
<tokenext>I had occasion to have an email conversation with Berners-Lee at one time ( he bought a license for a program of mine ) , and I asked if he regretted choosing " www " instead of " web " .
I was very surprised that this was not something he 'd change if he could do the whole thing over ...Saying " double u double u double u " takes about twice as long as saying " web " so that would have been far more beneficial than worrying about the slashes.There was a bit of a drive to use " web " some years ago , but unfortunately that fizzled..the ages when webservers where on a different machine than the ftp servers are long gone .
so why use subdomains there anyway.I have to agree with a previous post .
Some people , when I tell them a web-address , they have already put " www .
" in their browser an happily assume it would somehow belong there and I would just skip it ( even if I say : " http : //domain.tld " ) and then complain when the site is not found .
I could kill in such moments , especially when it 's over the phone .</tokentext>
<sentencetext>I had occasion to have an email conversation with Berners-Lee at one time (he bought a license for a program of mine), and I asked if he regretted choosing "www" instead of "web".
I was very surprised that this was not something he'd change if he could do the whole thing over ...Saying "double u double u double u" takes about twice as long as saying "web" so that would have been far more beneficial than worrying about the slashes.There was a bit of a drive to use "web" some years ago, but unfortunately that fizzled..the ages when webservers where on a different machine than the ftp servers are long gone.
so why use subdomains there anyway.I have to agree with a previous post.
Some people, when I tell them a web-address, they have already put "www.
" in their browser an happily assume it would somehow belong there and I would just skip it (even if I say: "http://domain.tld") and then complain when the site is not found.
I could kill in such moments, especially when it's over the phone.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750309</id>
	<title>Its a keyboard bug!</title>
	<author>Tired and Emotional</author>
	<datestamp>1255516320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Your keyboard should have a <a href="http://www./" title="www.">http://www./</a> [www.] key.</htmltext>
<tokenext>Your keyboard should have a http : //www./ [ www .
] key .</tokentext>
<sentencetext>Your keyboard should have a http://www./ [www.
] key.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29753877</id>
	<title>they actually do have a purpose...</title>
	<author>petrus4</author>
	<datestamp>1255547940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Although of course "http:" would be considered the protocol indicator, IMHO "http://" is more effective visually as a seperator/prefix.  That particular slash is also the one used in directory names on UNIX systems as well, so it is consistent with any other slashes which you're likely to put, later in a URL.</p><p>It's only really annoying because of its' location on most people's keyboards, I suspect; although some Windows users hate typing URLs of any length, I'm aware.</p></htmltext>
<tokenext>Although of course " http : " would be considered the protocol indicator , IMHO " http : // " is more effective visually as a seperator/prefix .
That particular slash is also the one used in directory names on UNIX systems as well , so it is consistent with any other slashes which you 're likely to put , later in a URL.It 's only really annoying because of its ' location on most people 's keyboards , I suspect ; although some Windows users hate typing URLs of any length , I 'm aware .</tokentext>
<sentencetext>Although of course "http:" would be considered the protocol indicator, IMHO "http://" is more effective visually as a seperator/prefix.
That particular slash is also the one used in directory names on UNIX systems as well, so it is consistent with any other slashes which you're likely to put, later in a URL.It's only really annoying because of its' location on most people's keyboards, I suspect; although some Windows users hate typing URLs of any length, I'm aware.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746613</id>
	<title>Re:backslashdot</title>
	<author>shutdown -p now</author>
	<datestamp>1255543020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Boy, you're not kidding. Nothing like using a directory delimiter that's the escape character in pretty much every programming language there is.</p> </div><p>At the time DOS was written, "pretty much every programming language" that used \ for escaping was C and Unix shells. Keep in mind that it was back in the day what Pascal was a serious C contender, and BASIC was also actively used for application development.</p><p>Don't make the mistake of judging design decisions from their long-time effects that are observable only today. People doing it back then didn't have that luxury.</p></div>
	</htmltext>
<tokenext>Boy , you 're not kidding .
Nothing like using a directory delimiter that 's the escape character in pretty much every programming language there is .
At the time DOS was written , " pretty much every programming language " that used \ for escaping was C and Unix shells .
Keep in mind that it was back in the day what Pascal was a serious C contender , and BASIC was also actively used for application development.Do n't make the mistake of judging design decisions from their long-time effects that are observable only today .
People doing it back then did n't have that luxury .</tokentext>
<sentencetext>Boy, you're not kidding.
Nothing like using a directory delimiter that's the escape character in pretty much every programming language there is.
At the time DOS was written, "pretty much every programming language" that used \ for escaping was C and Unix shells.
Keep in mind that it was back in the day what Pascal was a serious C contender, and BASIC was also actively used for application development.Don't make the mistake of judging design decisions from their long-time effects that are observable only today.
People doing it back then didn't have that luxury.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744499</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749361</id>
	<title>Re:So Who's Apologizing for 'ttp' ?</title>
	<author>Eil</author>
	<datestamp>1255511940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>'h' alone isn't really very descriptive, though. The thinking was that the protocol identifier should match the protocol's actual name or acronym so that people knew what kind of service they were connecting to. In the early days of the web, it was envisioned that the web would "live" on all kinds of protocols and services and that web browsers would be a common interface to that content. There were URLs like <a href="ftp://example.com" title="example.com">ftp://example.com</a> [example.com] and <a href="gopher://example.com" title="example.com">gopher://example.com</a> [example.com]. I can recall some "web" sites being served via FTP because that's all that some ISPs offered at the time.</p><p>Had Berners-Lee known that HTTP would eventually become the only protocol that anyone really used for hosting web content, he might have opted to omit it from the URI specification altogether and just let browser developers worry about how to support other services if they so wished.</p></htmltext>
<tokenext>'h ' alone is n't really very descriptive , though .
The thinking was that the protocol identifier should match the protocol 's actual name or acronym so that people knew what kind of service they were connecting to .
In the early days of the web , it was envisioned that the web would " live " on all kinds of protocols and services and that web browsers would be a common interface to that content .
There were URLs like ftp : //example.com [ example.com ] and gopher : //example.com [ example.com ] .
I can recall some " web " sites being served via FTP because that 's all that some ISPs offered at the time.Had Berners-Lee known that HTTP would eventually become the only protocol that anyone really used for hosting web content , he might have opted to omit it from the URI specification altogether and just let browser developers worry about how to support other services if they so wished .</tokentext>
<sentencetext>'h' alone isn't really very descriptive, though.
The thinking was that the protocol identifier should match the protocol's actual name or acronym so that people knew what kind of service they were connecting to.
In the early days of the web, it was envisioned that the web would "live" on all kinds of protocols and services and that web browsers would be a common interface to that content.
There were URLs like ftp://example.com [example.com] and gopher://example.com [example.com].
I can recall some "web" sites being served via FTP because that's all that some ISPs offered at the time.Had Berners-Lee known that HTTP would eventually become the only protocol that anyone really used for hosting web content, he might have opted to omit it from the URI specification altogether and just let browser developers worry about how to support other services if they so wished.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743859</id>
	<title>Re:backslashdot</title>
	<author>Anonymous</author>
	<datestamp>1255531440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Backslashes are a nightmare to type on foreign keyboard layouts (I've got first-hand experience with Finnish, you've got to press control-alt-+ so typing in especially long Windows pathnames becomes a nightmare)</p></htmltext>
<tokenext>Backslashes are a nightmare to type on foreign keyboard layouts ( I 've got first-hand experience with Finnish , you 've got to press control-alt- + so typing in especially long Windows pathnames becomes a nightmare )</tokentext>
<sentencetext>Backslashes are a nightmare to type on foreign keyboard layouts (I've got first-hand experience with Finnish, you've got to press control-alt-+ so typing in especially long Windows pathnames becomes a nightmare)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749747</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>Anonymous</author>
	<datestamp>1255513680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Some people just say "dub dub dub" or "wuh wuh wuh", which admittedly is still longer than saying "web" but it's not really that bad.</p><p>More irritating is people who think *everything* on the Internet starts with www., including their own e-mail addresses.</p></htmltext>
<tokenext>Some people just say " dub dub dub " or " wuh wuh wuh " , which admittedly is still longer than saying " web " but it 's not really that bad.More irritating is people who think * everything * on the Internet starts with www. , including their own e-mail addresses .</tokentext>
<sentencetext>Some people just say "dub dub dub" or "wuh wuh wuh", which admittedly is still longer than saying "web" but it's not really that bad.More irritating is people who think *everything* on the Internet starts with www., including their own e-mail addresses.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745773</id>
	<title>Re:It's time to...</title>
	<author>Anonymous</author>
	<datestamp>1255539360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>...and if microsoft had invented it, it would've been http:\\www...</p></htmltext>
<tokenext>...and if microsoft had invented it , it would 've been http : \ \ www.. .</tokentext>
<sentencetext>...and if microsoft had invented it, it would've been http:\\www...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743505</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744249</id>
	<title>Re:Now explain triple-slashes</title>
	<author>GargamelSpaceman</author>
	<datestamp>1255533180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Of course firefox lets me type file:/path/to/file.txt treating it as equivalent to file:///path/to/file.txt, but normalizing it to file:///path/to/file.txt .  I think it's parsed as file://<nobr> <wbr></nobr>/path/to/file.txt .  Between the first two slashes and the next one there is a 'hierarchical naming authority' in this case a null one referring to your filesystem.   I don't know if there's anything you could put in there that would not be a valid directory name, so it's really just there because many people will expect to have to type two double slashes before beginning the path.    I think it's silly to normalize to the triple slash form though.  Why not the shorter, clearer single slash form?</htmltext>
<tokenext>Of course firefox lets me type file : /path/to/file.txt treating it as equivalent to file : ///path/to/file.txt , but normalizing it to file : ///path/to/file.txt .
I think it 's parsed as file : // /path/to/file.txt .
Between the first two slashes and the next one there is a 'hierarchical naming authority ' in this case a null one referring to your filesystem .
I do n't know if there 's anything you could put in there that would not be a valid directory name , so it 's really just there because many people will expect to have to type two double slashes before beginning the path .
I think it 's silly to normalize to the triple slash form though .
Why not the shorter , clearer single slash form ?</tokentext>
<sentencetext>Of course firefox lets me type file:/path/to/file.txt treating it as equivalent to file:///path/to/file.txt, but normalizing it to file:///path/to/file.txt .
I think it's parsed as file:// /path/to/file.txt .
Between the first two slashes and the next one there is a 'hierarchical naming authority' in this case a null one referring to your filesystem.
I don't know if there's anything you could put in there that would not be a valid directory name, so it's really just there because many people will expect to have to type two double slashes before beginning the path.
I think it's silly to normalize to the triple slash form though.
Why not the shorter, clearer single slash form?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748533</id>
	<title>Re:DNS</title>
	<author>jez9999</author>
	<datestamp>1255551360000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Yeah, you're right.  I can't think of any time I regularly use slashes in common speech/reading/writing.  And it's not just me; go ask the average man/woman on the street.</p></htmltext>
<tokenext>Yeah , you 're right .
I ca n't think of any time I regularly use slashes in common speech/reading/writing .
And it 's not just me ; go ask the average man/woman on the street .</tokentext>
<sentencetext>Yeah, you're right.
I can't think of any time I regularly use slashes in common speech/reading/writing.
And it's not just me; go ask the average man/woman on the street.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746043</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746339</id>
	<title>Re:Time wasted explaining a slash vs. backslash</title>
	<author>Anonymous</author>
	<datestamp>1255541640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>That blame goes to Mr Gates along with</p></htmltext>
<tokenext>That blame goes to Mr Gates along with</tokentext>
<sentencetext>That blame goes to Mr Gates along with</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743585</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744011</id>
	<title>Re:I thought there was a point to the two slashes</title>
	<author>dylan\_-</author>
	<datestamp>1255532100000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><blockquote><div><p>I remember stating that originally, an indication of which network protocol to use was meant to go between the slashes.</p></div></blockquote><p>I don't think so, since the double slashes only apply to Internet schemes anyway. RFC1738 says:</p><blockquote><div><p>//&lt;user&gt;:&lt;password&gt;@&lt;host&gt;:&lt;port&gt;/&lt;url-path&gt;</p><p>
&nbsp; &nbsp; &nbsp; Some or all of the parts "&lt;user&gt;:&lt;password&gt;@", ":&lt;password&gt;",<br>
&nbsp; &nbsp; &nbsp; ":&lt;port&gt;", and "/&lt;url-path&gt;" may be excluded.  The scheme specific<br>
&nbsp; &nbsp; &nbsp; data start with a double slash "//" to indicate that it complies with<br>
&nbsp; &nbsp; &nbsp; the common Internet scheme syntax.</p></div></blockquote><p>But if you find another reference, please let me know.</p></div>
	</htmltext>
<tokenext>I remember stating that originally , an indication of which network protocol to use was meant to go between the slashes.I do n't think so , since the double slashes only apply to Internet schemes anyway .
RFC1738 says : // : @ : /       Some or all of the parts " : @ " , " : " ,       " : " , and " / " may be excluded .
The scheme specific       data start with a double slash " // " to indicate that it complies with       the common Internet scheme syntax.But if you find another reference , please let me know .</tokentext>
<sentencetext>I remember stating that originally, an indication of which network protocol to use was meant to go between the slashes.I don't think so, since the double slashes only apply to Internet schemes anyway.
RFC1738 says://:@:/
      Some or all of the parts ":@", ":",
      ":", and "/" may be excluded.
The scheme specific
      data start with a double slash "//" to indicate that it complies with
      the common Internet scheme syntax.But if you find another reference, please let me know.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743675</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744473</id>
	<title>Re:... it seemed like a good idea at the time...</title>
	<author>Anonymous</author>
	<datestamp>1255534080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'll be there in a flash.</p><p>Yours,</p><p>Q</p></htmltext>
<tokenext>I 'll be there in a flash.Yours,Q</tokentext>
<sentencetext>I'll be there in a flash.Yours,Q</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743609</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745015</id>
	<title>Re:DNS</title>
	<author>ukyoCE</author>
	<datestamp>1255536300000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>People don't consider the TLD to be most significant, and especially did not consider it so before any domain names used anything other than<nobr> <wbr></nobr>.com or maybe<nobr> <wbr></nobr>.edu/.net/.org.</p><p>Unless you happen to use both slashdot.com and slashdot.org (and<nobr> <wbr></nobr>.net, etc.), odds are you can almost always tab complete the name "sla" and avoid ever typing "com." or "co". The TLD is essentially totally insignificant, and would have to be typed every single time if the order were reversed.</p><p>Agreed though that compared to the rest of the path it IS backwards.</p></htmltext>
<tokenext>People do n't consider the TLD to be most significant , and especially did not consider it so before any domain names used anything other than .com or maybe .edu/.net/.org.Unless you happen to use both slashdot.com and slashdot.org ( and .net , etc .
) , odds are you can almost always tab complete the name " sla " and avoid ever typing " com .
" or " co " .
The TLD is essentially totally insignificant , and would have to be typed every single time if the order were reversed.Agreed though that compared to the rest of the path it IS backwards .</tokentext>
<sentencetext>People don't consider the TLD to be most significant, and especially did not consider it so before any domain names used anything other than .com or maybe .edu/.net/.org.Unless you happen to use both slashdot.com and slashdot.org (and .net, etc.
), odds are you can almost always tab complete the name "sla" and avoid ever typing "com.
" or "co".
The TLD is essentially totally insignificant, and would have to be typed every single time if the order were reversed.Agreed though that compared to the rest of the path it IS backwards.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29754881</id>
	<title>Re:DNS</title>
	<author>Mjlner</author>
	<datestamp>1255605480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>

Berners-Lee regrets that as well, from <a href="http://www.w3.org/People/Berners-Lee/FAQ.html" title="w3.org">back in 2000...</a> [w3.org]<blockquote><div><p>I have to say that now I regret that the syntax is so clumsy. I would like <a href="http://www.example.com/foo/bar/baz" title="example.com">http://www.example.com/foo/bar/baz</a> [example.com] to be just written <a href="http:com/example/foo/bar/baz" title="com">http:com/example/foo/bar/baz</a> [com] where the client would figure out that www.example.com existed and was the server to contact.</p></div></blockquote><p>Heavens, <b>NO!</b> Explicitly and visibly separating the hostname from the rest of the URL is essential! Just think of all how much phishing would explode if you can't tell whether you're accessing example.com/foo/bar/baz or foo.example.com/bar/baz or bar.foo.example.com/baz! <b>At the very least</b>, the dot would have to be retained, as in <a href="http:com.example/foo/bar/bax" title="com.example">http:com.example/foo/bar/bax</a> [com.example].</p></div>
	</htmltext>
<tokenext>Berners-Lee regrets that as well , from back in 2000... [ w3.org ] I have to say that now I regret that the syntax is so clumsy .
I would like http : //www.example.com/foo/bar/baz [ example.com ] to be just written http : com/example/foo/bar/baz [ com ] where the client would figure out that www.example.com existed and was the server to contact.Heavens , NO !
Explicitly and visibly separating the hostname from the rest of the URL is essential !
Just think of all how much phishing would explode if you ca n't tell whether you 're accessing example.com/foo/bar/baz or foo.example.com/bar/baz or bar.foo.example.com/baz !
At the very least , the dot would have to be retained , as in http : com.example/foo/bar/bax [ com.example ] .</tokentext>
<sentencetext>

Berners-Lee regrets that as well, from back in 2000... [w3.org]I have to say that now I regret that the syntax is so clumsy.
I would like http://www.example.com/foo/bar/baz [example.com] to be just written http:com/example/foo/bar/baz [com] where the client would figure out that www.example.com existed and was the server to contact.Heavens, NO!
Explicitly and visibly separating the hostname from the rest of the URL is essential!
Just think of all how much phishing would explode if you can't tell whether you're accessing example.com/foo/bar/baz or foo.example.com/bar/baz or bar.foo.example.com/baz!
At the very least, the dot would have to be retained, as in http:com.example/foo/bar/bax [com.example].
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744335</id>
	<title>Re:pronouncing www is a lot more of a problem</title>
	<author>Anonymous</author>
	<datestamp>1255533540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Yeah, I've had that problem as well. Except with web developers. The artist type (Photoshop / Dreamweaver jockey) rather than the tech type.</p><p>Developer: Can you set up a subdomain. Like subdomain.example.com?<br>Me: Done.<br>Developer: It's not working.<br>Me (having checked that it is, in fact, working): Yes it is. What URL are you trying to use?<br>Developer: www.subdomain.example.com</p><p>As a pre-emptive defense against this sort of thing, I tend to configure Apache something like:</p><blockquote><div><p>&lt;VirtualHost *:80&gt;<br>
&nbsp; &nbsp; ServerName www.subdomain.example.com<br>
&nbsp; &nbsp; Redirect permanent / http://subdomain.example.com/<br>&lt;/VirtualHost&gt;</p></div></blockquote><p>It means I have to have a pointless, redundant record in DNS (much like the normal www.example.com record), but at least nobody can screw it up.</p><p>Same goes for regular users and webmail. For a webmail interface hosted on https://mail.example.com, we have to have redirects from http://mail.example.com (fair enough), http://www.mail.example.com (ugh), and http://www.example.com/mail (which is on a completely different server). My guess on that last one is that some people have no idea about subdomains, assume that "mail.example.com" was a typo, and type "example.com/mail" into the address bar instead.</p></div>
	</htmltext>
<tokenext>Yeah , I 've had that problem as well .
Except with web developers .
The artist type ( Photoshop / Dreamweaver jockey ) rather than the tech type.Developer : Can you set up a subdomain .
Like subdomain.example.com ? Me : Done.Developer : It 's not working.Me ( having checked that it is , in fact , working ) : Yes it is .
What URL are you trying to use ? Developer : www.subdomain.example.comAs a pre-emptive defense against this sort of thing , I tend to configure Apache something like :     ServerName www.subdomain.example.com     Redirect permanent / http : //subdomain.example.com/It means I have to have a pointless , redundant record in DNS ( much like the normal www.example.com record ) , but at least nobody can screw it up.Same goes for regular users and webmail .
For a webmail interface hosted on https : //mail.example.com , we have to have redirects from http : //mail.example.com ( fair enough ) , http : //www.mail.example.com ( ugh ) , and http : //www.example.com/mail ( which is on a completely different server ) .
My guess on that last one is that some people have no idea about subdomains , assume that " mail.example.com " was a typo , and type " example.com/mail " into the address bar instead .</tokentext>
<sentencetext>Yeah, I've had that problem as well.
Except with web developers.
The artist type (Photoshop / Dreamweaver jockey) rather than the tech type.Developer: Can you set up a subdomain.
Like subdomain.example.com?Me: Done.Developer: It's not working.Me (having checked that it is, in fact, working): Yes it is.
What URL are you trying to use?Developer: www.subdomain.example.comAs a pre-emptive defense against this sort of thing, I tend to configure Apache something like:
    ServerName www.subdomain.example.com
    Redirect permanent / http://subdomain.example.com/It means I have to have a pointless, redundant record in DNS (much like the normal www.example.com record), but at least nobody can screw it up.Same goes for regular users and webmail.
For a webmail interface hosted on https://mail.example.com, we have to have redirects from http://mail.example.com (fair enough), http://www.mail.example.com (ugh), and http://www.example.com/mail (which is on a completely different server).
My guess on that last one is that some people have no idea about subdomains, assume that "mail.example.com" was a typo, and type "example.com/mail" into the address bar instead.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744323</id>
	<title>Re:DNS</title>
	<author>Anonymous</author>
	<datestamp>1255533480000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><p>It's the same reason Americans write dates out of order (Month/Day/Year). We humans don't always parse in a logical order. While yes, that would have been a bit simpler for typing the URLs, I could see that the general public would have had a harder time understanding it and the internet may not have reached such a wide demographic as it has now.</p></htmltext>
<tokenext>It 's the same reason Americans write dates out of order ( Month/Day/Year ) .
We humans do n't always parse in a logical order .
While yes , that would have been a bit simpler for typing the URLs , I could see that the general public would have had a harder time understanding it and the internet may not have reached such a wide demographic as it has now .</tokentext>
<sentencetext>It's the same reason Americans write dates out of order (Month/Day/Year).
We humans don't always parse in a logical order.
While yes, that would have been a bit simpler for typing the URLs, I could see that the general public would have had a harder time understanding it and the internet may not have reached such a wide demographic as it has now.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744497</id>
	<title>Re:Stupid story</title>
	<author>bendodge</author>
	<datestamp>1255534200000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p><div class="quote"><p>Store a stupid bookmark.  Then you only have to type <a href="https://blah.blah.blah/" title="blah.blah">https://blah.blah.blah/</a> [blah.blah] one time.</p></div><p>You should be more responsible than to link to <a href="https://blah.blah.blah/" title="blah.blah">https://blah.blah.blah/</a> [blah.blah]. It's got an invalid cert!</p></div>
	</htmltext>
<tokenext>Store a stupid bookmark .
Then you only have to type https : //blah.blah.blah/ [ blah.blah ] one time.You should be more responsible than to link to https : //blah.blah.blah/ [ blah.blah ] .
It 's got an invalid cert !</tokentext>
<sentencetext>Store a stupid bookmark.
Then you only have to type https://blah.blah.blah/ [blah.blah] one time.You should be more responsible than to link to https://blah.blah.blah/ [blah.blah].
It's got an invalid cert!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743649</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746043</id>
	<title>Re:DNS</title>
	<author>pmontra</author>
	<datestamp>1255540440000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>It might be habits but IMHO www.example.com looks much natural than com/example on any media, from business cards to tv commercials. We use dot in normal writing and not slashes.<br>
And what's better at highlighting a brand: org/slashdot or slashdot.org?</p><p>Luckly B-L got it right the first time. Maybe the web wouldn't have add all this success if he designed the addresses in the other way.</p></htmltext>
<tokenext>It might be habits but IMHO www.example.com looks much natural than com/example on any media , from business cards to tv commercials .
We use dot in normal writing and not slashes .
And what 's better at highlighting a brand : org/slashdot or slashdot.org ? Luckly B-L got it right the first time .
Maybe the web would n't have add all this success if he designed the addresses in the other way .</tokentext>
<sentencetext>It might be habits but IMHO www.example.com looks much natural than com/example on any media, from business cards to tv commercials.
We use dot in normal writing and not slashes.
And what's better at highlighting a brand: org/slashdot or slashdot.org?Luckly B-L got it right the first time.
Maybe the web wouldn't have add all this success if he designed the addresses in the other way.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744961</id>
	<title>Re:www</title>
	<author>John Hasler</author>
	<datestamp>1255536060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>WWW -&gt; World Wide Web.</p></htmltext>
<tokenext>WWW - &gt; World Wide Web .</tokentext>
<sentencetext>WWW -&gt; World Wide Web.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743967</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743775</id>
	<title>Re:Theres one technical point</title>
	<author>Anonymous</author>
	<datestamp>1255531020000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Try it, it works. The parser correctly identifies tech.slashdot.org as the host name. It even works with single component domain names. The only case which needs disambiguation is when you have a local host name (i.e. no ".") and it happens to be the same as one of the known protocol names. In that case,<nobr> <wbr></nobr>//name/path is a working disambiguation, but really, is that easier than prefixing http:? Even if you consider that<nobr> <wbr></nobr>//name/path is awfully close to \\name\path, which is something else entirely?</p><p>On the other hand: Who types http:// anyway? Most programs which turn text into clickable URLs look for www.* (which btw. is one of the reasons for not omitting www from the URL although it is technically not necessary either.) Besides, people type everything into the Google (Yahoo, Bing) search box these days, even HTTPS URLs.</p></htmltext>
<tokenext>Try it , it works .
The parser correctly identifies tech.slashdot.org as the host name .
It even works with single component domain names .
The only case which needs disambiguation is when you have a local host name ( i.e .
no " .
" ) and it happens to be the same as one of the known protocol names .
In that case , //name/path is a working disambiguation , but really , is that easier than prefixing http : ?
Even if you consider that //name/path is awfully close to \ \ name \ path , which is something else entirely ? On the other hand : Who types http : // anyway ?
Most programs which turn text into clickable URLs look for www .
* ( which btw .
is one of the reasons for not omitting www from the URL although it is technically not necessary either .
) Besides , people type everything into the Google ( Yahoo , Bing ) search box these days , even HTTPS URLs .</tokentext>
<sentencetext>Try it, it works.
The parser correctly identifies tech.slashdot.org as the host name.
It even works with single component domain names.
The only case which needs disambiguation is when you have a local host name (i.e.
no ".
") and it happens to be the same as one of the known protocol names.
In that case, //name/path is a working disambiguation, but really, is that easier than prefixing http:?
Even if you consider that //name/path is awfully close to \\name\path, which is something else entirely?On the other hand: Who types http:// anyway?
Most programs which turn text into clickable URLs look for www.
* (which btw.
is one of the reasons for not omitting www from the URL although it is technically not necessary either.
) Besides, people type everything into the Google (Yahoo, Bing) search box these days, even HTTPS URLs.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743463</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747801</id>
	<title>true, so many keystrokes wasted</title>
	<author>commodoresloat</author>
	<datestamp>1255548240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>almost as many keystrokes have been wasted typing<nobr> <wbr></nobr>// over the years as have been wasted today talking about the darn slashes on this slashdot article!</p></htmltext>
<tokenext>almost as many keystrokes have been wasted typing // over the years as have been wasted today talking about the darn slashes on this slashdot article !</tokentext>
<sentencetext>almost as many keystrokes have been wasted typing // over the years as have been wasted today talking about the darn slashes on this slashdot article!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745279</id>
	<title>News for Turds</title>
	<author>mahsah</author>
	<datestamp>1255537380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Stuff that splatters.</p></htmltext>
<tokenext>Stuff that splatters .</tokentext>
<sentencetext>Stuff that splatters.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745139</id>
	<title>Re:backslashdot</title>
	<author>140Mandak262Jamuna</author>
	<datestamp>1255536780000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext>The main reason is to be incompatible with everyone else. Microsofties knew backslash was an escape character in most unix shells. So they must use it to add as much pain to those people using Command line interface. Also when Win98 came out they added spaces in file names specifically because that will have to be escaped in any shell. But forward slashes work fine in the api. From any code, you could use fopen("c:/foo.txt","r") and it will work just like fopen("C:\foo.txt","r") in Windows.</htmltext>
<tokenext>The main reason is to be incompatible with everyone else .
Microsofties knew backslash was an escape character in most unix shells .
So they must use it to add as much pain to those people using Command line interface .
Also when Win98 came out they added spaces in file names specifically because that will have to be escaped in any shell .
But forward slashes work fine in the api .
From any code , you could use fopen ( " c : /foo.txt " , " r " ) and it will work just like fopen ( " C : \ foo.txt " , " r " ) in Windows .</tokentext>
<sentencetext>The main reason is to be incompatible with everyone else.
Microsofties knew backslash was an escape character in most unix shells.
So they must use it to add as much pain to those people using Command line interface.
Also when Win98 came out they added spaces in file names specifically because that will have to be escaped in any shell.
But forward slashes work fine in the api.
From any code, you could use fopen("c:/foo.txt","r") and it will work just like fopen("C:\foo.txt","r") in Windows.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743935</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743967</id>
	<title>www</title>
	<author>EricX2</author>
	<datestamp>1255531920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Was he also the guy who decided on WWW? That takes too long to say, why not AAA or VVV or any other letter that doesn't take three syllables to say. World Wide Web... what were they thinking?</p></htmltext>
<tokenext>Was he also the guy who decided on WWW ?
That takes too long to say , why not AAA or VVV or any other letter that does n't take three syllables to say .
World Wide Web... what were they thinking ?</tokentext>
<sentencetext>Was he also the guy who decided on WWW?
That takes too long to say, why not AAA or VVV or any other letter that doesn't take three syllables to say.
World Wide Web... what were they thinking?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049</id>
	<title>Re:DNS</title>
	<author>Anonymous</author>
	<datestamp>1255536420000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><blockquote><div><p>What I wonder is why the designers of DNS put the name in reverse?</p></div></blockquote><p>

Berners-Lee regrets that as well, from <a href="http://www.w3.org/People/Berners-Lee/FAQ.html" title="w3.org">back in 2000...</a> [w3.org] </p><blockquote><div><p>I have to say that now I regret that the syntax is so clumsy. I would like <a href="http://www.example.com/foo/bar/baz" title="example.com">http://www.example.com/foo/bar/baz</a> [example.com] to be just written <a href="http:com/example/foo/bar/baz" title="com">http:com/example/foo/bar/baz</a> [com] where the client would figure out that www.example.com existed and was the server to contact. But it is too late now. It turned out the shorthand "//www.example.com/foo/bar/baz" is rarely used and so we could dispense with the "//".</p></div></blockquote></div>
	</htmltext>
<tokenext>What I wonder is why the designers of DNS put the name in reverse ?
Berners-Lee regrets that as well , from back in 2000... [ w3.org ] I have to say that now I regret that the syntax is so clumsy .
I would like http : //www.example.com/foo/bar/baz [ example.com ] to be just written http : com/example/foo/bar/baz [ com ] where the client would figure out that www.example.com existed and was the server to contact .
But it is too late now .
It turned out the shorthand " //www.example.com/foo/bar/baz " is rarely used and so we could dispense with the " // " .</tokentext>
<sentencetext>What I wonder is why the designers of DNS put the name in reverse?
Berners-Lee regrets that as well, from back in 2000... [w3.org] I have to say that now I regret that the syntax is so clumsy.
I would like http://www.example.com/foo/bar/baz [example.com] to be just written http:com/example/foo/bar/baz [com] where the client would figure out that www.example.com existed and was the server to contact.
But it is too late now.
It turned out the shorthand "//www.example.com/foo/bar/baz" is rarely used and so we could dispense with the "//".
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743537</id>
	<title>Just think if he had left them out ...</title>
	<author>Anonymous</author>
	<datestamp>1255529760000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>We'd all be reading colondot right now.</htmltext>
<tokenext>We 'd all be reading colondot right now .</tokentext>
<sentencetext>We'd all be reading colondot right now.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746537</id>
	<title>Re:backslashdot</title>
	<author>shutdown -p now</author>
	<datestamp>1255542660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Nah. Slashes are fine, but Microsoft should be sorry about backslashes!</p></div><p>You can <a href="http://blogs.msdn.com/larryosterman/archive/2005/06/24/432386.aspx" title="msdn.com">thank IBM</a> [msdn.com] for that one (be sure to read <a href="http://blogs.msdn.com/larryosterman/archive/2005/06/24/432386.aspx#432629" title="msdn.com">Hans Spiller's comment</a> [msdn.com] to that blog post, too).</p><p>If anything, Microsoft tried to fight that decision back by supporting "/" for path separator as well (which lives to this day in Windows), and by providing the secret SWITCHAR option in config.sys that let you disable the use of "/" in command line switches for applications, so that "foo<nobr> <wbr></nobr>/bar" would unambiguously refer to directory "\bar", and not to switch "-bar". You can thank IBM for taking that feature out as well:</p><p><i>Much effort was made to keep the fact that SWITCHAR was in shipping systems a secret because it was suspected that when IBM found out they would make us take it out. This suspicion was proven correct. It took them almost 5 years to find it though, and none of the original DOS crew was still working on it.</i></p></div>
	</htmltext>
<tokenext>Nah .
Slashes are fine , but Microsoft should be sorry about backslashes ! You can thank IBM [ msdn.com ] for that one ( be sure to read Hans Spiller 's comment [ msdn.com ] to that blog post , too ) .If anything , Microsoft tried to fight that decision back by supporting " / " for path separator as well ( which lives to this day in Windows ) , and by providing the secret SWITCHAR option in config.sys that let you disable the use of " / " in command line switches for applications , so that " foo /bar " would unambiguously refer to directory " \ bar " , and not to switch " -bar " .
You can thank IBM for taking that feature out as well : Much effort was made to keep the fact that SWITCHAR was in shipping systems a secret because it was suspected that when IBM found out they would make us take it out .
This suspicion was proven correct .
It took them almost 5 years to find it though , and none of the original DOS crew was still working on it .</tokentext>
<sentencetext>Nah.
Slashes are fine, but Microsoft should be sorry about backslashes!You can thank IBM [msdn.com] for that one (be sure to read Hans Spiller's comment [msdn.com] to that blog post, too).If anything, Microsoft tried to fight that decision back by supporting "/" for path separator as well (which lives to this day in Windows), and by providing the secret SWITCHAR option in config.sys that let you disable the use of "/" in command line switches for applications, so that "foo /bar" would unambiguously refer to directory "\bar", and not to switch "-bar".
You can thank IBM for taking that feature out as well:Much effort was made to keep the fact that SWITCHAR was in shipping systems a secret because it was suspected that when IBM found out they would make us take it out.
This suspicion was proven correct.
It took them almost 5 years to find it though, and none of the original DOS crew was still working on it.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743685</id>
	<title>Re:... it seemed like a good idea at the time...</title>
	<author>Rosco P. Coltrane</author>
	<datestamp>1255530600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I assume you always pick the right decision yourself then...</p><p>Come on man, humanity chooses wrong paths all the time with the best of intentions, because none of us (apart from you apparently) can predict the future. We do our best to evaluate the future results of our actions, but our foreknowledge is always sketchy at best.</p></htmltext>
<tokenext>I assume you always pick the right decision yourself then...Come on man , humanity chooses wrong paths all the time with the best of intentions , because none of us ( apart from you apparently ) can predict the future .
We do our best to evaluate the future results of our actions , but our foreknowledge is always sketchy at best .</tokentext>
<sentencetext>I assume you always pick the right decision yourself then...Come on man, humanity chooses wrong paths all the time with the best of intentions, because none of us (apart from you apparently) can predict the future.
We do our best to evaluate the future results of our actions, but our foreknowledge is always sketchy at best.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743609</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752253</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>Anonymous</author>
	<datestamp>1255529820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I think the real fault here is having the pronunciation of a letter require three syllables! The other 25 manage to fit nicely in one...</p></htmltext>
<tokenext>I think the real fault here is having the pronunciation of a letter require three syllables !
The other 25 manage to fit nicely in one.. .</tokentext>
<sentencetext>I think the real fault here is having the pronunciation of a letter require three syllables!
The other 25 manage to fit nicely in one...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744629</id>
	<title>Re:pronouncing www is a lot more of a problem</title>
	<author>RandomPsychology</author>
	<datestamp>1255534800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>please go ahead and stab him in the face. one less boss in the world is one happier employee!</htmltext>
<tokenext>please go ahead and stab him in the face .
one less boss in the world is one happier employee !</tokentext>
<sentencetext>please go ahead and stab him in the face.
one less boss in the world is one happier employee!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29754273</id>
	<title>Re:I thought there was a point to the two slashes</title>
	<author>Geordie Korper</author>
	<datestamp>1255639680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><blockquote><div><p>I remember stating that originally, an indication of which network protocol to use was meant to go between the slashes.</p></div></blockquote><p>I don't think so, since the double slashes only apply to Internet schemes anyway. RFC1738 says:</p><blockquote><div><p>//&lt;user&gt;:&lt;password&gt;@&lt;host&gt;:&lt;port&gt;/&lt;url-path&gt;</p><p>
&nbsp; &nbsp; &nbsp; Some or all of the parts "&lt;user&gt;:&lt;password&gt;@", ":&lt;password&gt;",</p><p>
&nbsp; &nbsp; &nbsp; ":&lt;port&gt;", and "/&lt;url-path&gt;" may be excluded.  The scheme specific</p><p>
&nbsp; &nbsp; &nbsp; data start with a double slash "//" to indicate that it complies with</p><p>
&nbsp; &nbsp; &nbsp; the common Internet scheme syntax.</p></div></blockquote><p>But if you find another reference, please let me know.</p></div><p>The only place where I know of that being used is in AFP URLs where you can specify AppleTalk using the following syntax: afp:/at/[user[;AUTH=uamname][:password]@]servername[:zonename]/volume</p><p>This is referred to in:<br><a href="http://tools.ietf.org/html/draft-ietf-svrloc-afp-service-01" title="ietf.org" rel="nofollow">http://tools.ietf.org/html/draft-ietf-svrloc-afp-service-01</a> [ietf.org]<br>as well as:<br><a href="http://en.wikipedia.org/wiki/URI\_scheme#Unofficial\_but\_common\_URI\_schemes" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/URI\_scheme#Unofficial\_but\_common\_URI\_schemes</a> [wikipedia.org]</p></div>
	</htmltext>
<tokenext>I remember stating that originally , an indication of which network protocol to use was meant to go between the slashes.I do n't think so , since the double slashes only apply to Internet schemes anyway .
RFC1738 says : // : @ : /       Some or all of the parts " : @ " , " : " ,       " : " , and " / " may be excluded .
The scheme specific       data start with a double slash " // " to indicate that it complies with       the common Internet scheme syntax.But if you find another reference , please let me know.The only place where I know of that being used is in AFP URLs where you can specify AppleTalk using the following syntax : afp : /at/ [ user [ ; AUTH = uamname ] [ : password ] @ ] servername [ : zonename ] /volumeThis is referred to in : http : //tools.ietf.org/html/draft-ietf-svrloc-afp-service-01 [ ietf.org ] as well as : http : //en.wikipedia.org/wiki/URI \ _scheme # Unofficial \ _but \ _common \ _URI \ _schemes [ wikipedia.org ]</tokentext>
<sentencetext>I remember stating that originally, an indication of which network protocol to use was meant to go between the slashes.I don't think so, since the double slashes only apply to Internet schemes anyway.
RFC1738 says://:@:/
      Some or all of the parts ":@", ":",
      ":", and "/" may be excluded.
The scheme specific
      data start with a double slash "//" to indicate that it complies with
      the common Internet scheme syntax.But if you find another reference, please let me know.The only place where I know of that being used is in AFP URLs where you can specify AppleTalk using the following syntax: afp:/at/[user[;AUTH=uamname][:password]@]servername[:zonename]/volumeThis is referred to in:http://tools.ietf.org/html/draft-ietf-svrloc-afp-service-01 [ietf.org]as well as:http://en.wikipedia.org/wiki/URI\_scheme#Unofficial\_but\_common\_URI\_schemes [wikipedia.org]
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744011</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29761599</id>
	<title>www?</title>
	<author>incubbus13</author>
	<datestamp>1255597380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I understood at one time that the www. prefix was indicative of someone following a standard? All 'legitimate' websites used www, while those who were a bit more dodgy, or less professional, or didn't follow the ICANN (maybe) protocol skipped the prefix. Is this still technically a standard? Anybody know what the deal with that is/was? Just geeky curiousity.</p><p>K.</p></htmltext>
<tokenext>I understood at one time that the www .
prefix was indicative of someone following a standard ?
All 'legitimate ' websites used www , while those who were a bit more dodgy , or less professional , or did n't follow the ICANN ( maybe ) protocol skipped the prefix .
Is this still technically a standard ?
Anybody know what the deal with that is/was ?
Just geeky curiousity.K .</tokentext>
<sentencetext>I understood at one time that the www.
prefix was indicative of someone following a standard?
All 'legitimate' websites used www, while those who were a bit more dodgy, or less professional, or didn't follow the ICANN (maybe) protocol skipped the prefix.
Is this still technically a standard?
Anybody know what the deal with that is/was?
Just geeky curiousity.K.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744053</id>
	<title>Re:yes</title>
	<author>agnosticnixie</author>
	<datestamp>1255532340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>A number of ISP have taking to breaking that kind of functionality - at least in Canada, Rogers and Bell do it, and half the time redirect you to their stupid search portal.</p></htmltext>
<tokenext>A number of ISP have taking to breaking that kind of functionality - at least in Canada , Rogers and Bell do it , and half the time redirect you to their stupid search portal .</tokentext>
<sentencetext>A number of ISP have taking to breaking that kind of functionality - at least in Canada, Rogers and Bell do it, and half the time redirect you to their stupid search portal.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747529</id>
	<title>Re:backslashdot</title>
	<author>TeknoHog</author>
	<datestamp>1255547100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Seriously, I agree with you to some extent. Python seems to work fine with much fewer punctuation characters.</htmltext>
<tokenext>Seriously , I agree with you to some extent .
Python seems to work fine with much fewer punctuation characters .</tokentext>
<sentencetext>Seriously, I agree with you to some extent.
Python seems to work fine with much fewer punctuation characters.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744495</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744063</id>
	<title>Sorry about WHAT?</title>
	<author>JockTroll</author>
	<datestamp>1255532340000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><p>I like slashes. I like them a lot. Especially the Buffy/Faith variety. Only loserboy nerds can't handle slashes. That's why we beat them up and you can guess the rest.</p></htmltext>
<tokenext>I like slashes .
I like them a lot .
Especially the Buffy/Faith variety .
Only loserboy nerds ca n't handle slashes .
That 's why we beat them up and you can guess the rest .</tokentext>
<sentencetext>I like slashes.
I like them a lot.
Especially the Buffy/Faith variety.
Only loserboy nerds can't handle slashes.
That's why we beat them up and you can guess the rest.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</id>
	<title>Saying double u double u double u a billion times</title>
	<author>Anonymous</author>
	<datestamp>1255530660000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>I had occasion to have an email conversation with Berners-Lee at one time (he bought a license for a program of mine), and I asked if he regretted choosing "www" instead of "web". I was very surprised that this was not something he'd change if he could do the whole thing over<nobr> <wbr></nobr>...</p><p>Saying "double u double u double u" takes about twice as long as saying "web" so that would have been far more beneficial than worrying about the slashes.</p><p>There was a bit of a drive to use "web" some years ago, but unfortunately that fizzled..</p></htmltext>
<tokenext>I had occasion to have an email conversation with Berners-Lee at one time ( he bought a license for a program of mine ) , and I asked if he regretted choosing " www " instead of " web " .
I was very surprised that this was not something he 'd change if he could do the whole thing over ...Saying " double u double u double u " takes about twice as long as saying " web " so that would have been far more beneficial than worrying about the slashes.There was a bit of a drive to use " web " some years ago , but unfortunately that fizzled. .</tokentext>
<sentencetext>I had occasion to have an email conversation with Berners-Lee at one time (he bought a license for a program of mine), and I asked if he regretted choosing "www" instead of "web".
I was very surprised that this was not something he'd change if he could do the whole thing over ...Saying "double u double u double u" takes about twice as long as saying "web" so that would have been far more beneficial than worrying about the slashes.There was a bit of a drive to use "web" some years ago, but unfortunately that fizzled..</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744707</id>
	<title>Re:So Who's Apologizing for 'ttp' ?</title>
	<author>EvilNTUser</author>
	<datestamp>1255534980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>And then there's the<nobr> <wbr></nobr>.mobi domain for mobile devices, because the more characters you have to type on your phone, the better, obviously.</p></htmltext>
<tokenext>And then there 's the .mobi domain for mobile devices , because the more characters you have to type on your phone , the better , obviously .</tokentext>
<sentencetext>And then there's the .mobi domain for mobile devices, because the more characters you have to type on your phone, the better, obviously.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750823</id>
	<title>Re:pronouncing www is a lot more of a problem</title>
	<author>Dan541</author>
	<datestamp>1255519440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Thats what email is good for, people just click the links.</p></htmltext>
<tokenext>Thats what email is good for , people just click the links .</tokentext>
<sentencetext>Thats what email is good for, people just click the links.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747093</id>
	<title>Re:www</title>
	<author>ZERO1ZERO</author>
	<datestamp>1255545300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Newsflash - not everybody in the world speaks English and<nobr> <wbr></nobr>/or pronouces a w as double-u.</htmltext>
<tokenext>Newsflash - not everybody in the world speaks English and /or pronouces a w as double-u .</tokentext>
<sentencetext>Newsflash - not everybody in the world speaks English and /or pronouces a w as double-u.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743967</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744387</id>
	<title>Re:DNS</title>
	<author>Anonymous</author>
	<datestamp>1255533780000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Also, if http had included a way to get \_parsable\_ directory listings, the tab-completion could have gone even further...</p></div><p>It does, and I do this all the time.  Just search index pages (the ones that end in "/") for links that point to sub-directories...</p></div>
	</htmltext>
<tokenext>Also , if http had included a way to get \ _parsable \ _ directory listings , the tab-completion could have gone even further...It does , and I do this all the time .
Just search index pages ( the ones that end in " / " ) for links that point to sub-directories.. .</tokentext>
<sentencetext>Also, if http had included a way to get \_parsable\_ directory listings, the tab-completion could have gone even further...It does, and I do this all the time.
Just search index pages (the ones that end in "/") for links that point to sub-directories...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744465</id>
	<title>Re:pronouncing www is a lot more of a problem</title>
	<author>Paul Carver</author>
	<datestamp>1255534020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If it's not a web server and he's typing www as the first part of the name of an smtp or irc or other type of server then I agree that your boss is dense. On the other hand, if you're setting up a web server and you don't make the first component of the name www then I would have to say that you are dense and you're not really doing your job properly.</p><p>And before you start going on about multipurpose servers I'm going to cut you off and say that if you don't know how to configure CNAME records you should get the heck out of the DNS server configuration files.</p><p>$ORIGIN mydomain.com.<br>server1   IN   A   1.2.3.4<br>www.server1   IN   CNAME server1<br>smtp.server1   IN   CNAME server1<br>ldap.server1   IN   CNAME server1<br>server2   IN   A   1.2.3.5<br>www.server2   IN   CNAME server2<br>nntp.server2   IN   CNAME server2<br>irc.server2   IN   CNAME server2<nobr> <wbr></nobr>:wq<br>rndc reload</p></htmltext>
<tokenext>If it 's not a web server and he 's typing www as the first part of the name of an smtp or irc or other type of server then I agree that your boss is dense .
On the other hand , if you 're setting up a web server and you do n't make the first component of the name www then I would have to say that you are dense and you 're not really doing your job properly.And before you start going on about multipurpose servers I 'm going to cut you off and say that if you do n't know how to configure CNAME records you should get the heck out of the DNS server configuration files. $ ORIGIN mydomain.com.server1 IN A 1.2.3.4www.server1 IN CNAME server1smtp.server1 IN CNAME server1ldap.server1 IN CNAME server1server2 IN A 1.2.3.5www.server2 IN CNAME server2nntp.server2 IN CNAME server2irc.server2 IN CNAME server2 : wqrndc reload</tokentext>
<sentencetext>If it's not a web server and he's typing www as the first part of the name of an smtp or irc or other type of server then I agree that your boss is dense.
On the other hand, if you're setting up a web server and you don't make the first component of the name www then I would have to say that you are dense and you're not really doing your job properly.And before you start going on about multipurpose servers I'm going to cut you off and say that if you don't know how to configure CNAME records you should get the heck out of the DNS server configuration files.$ORIGIN mydomain.com.server1   IN   A   1.2.3.4www.server1   IN   CNAME server1smtp.server1   IN   CNAME server1ldap.server1   IN   CNAME server1server2   IN   A   1.2.3.5www.server2   IN   CNAME server2nntp.server2   IN   CNAME server2irc.server2   IN   CNAME server2 :wqrndc reload</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744319</id>
	<title>Re:Now explain triple-slashes</title>
	<author>Anonymous</author>
	<datestamp>1255533480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>like when I open a local file in my browser I get "file:///"</p></div><p>the 2 slashes that Sir Tim wants removed, and the rest is the path to the file. Accessing<nobr> <wbr></nobr>/home/user/foo.html in firefox would become file:// for the protocol and<nobr> <wbr></nobr>/home/user/foo.html for the path. Joining everything, your three slashes: file:///home/user/foo.html</p></div>
	</htmltext>
<tokenext>like when I open a local file in my browser I get " file : /// " the 2 slashes that Sir Tim wants removed , and the rest is the path to the file .
Accessing /home/user/foo.html in firefox would become file : // for the protocol and /home/user/foo.html for the path .
Joining everything , your three slashes : file : ///home/user/foo.html</tokentext>
<sentencetext>like when I open a local file in my browser I get "file:///"the 2 slashes that Sir Tim wants removed, and the rest is the path to the file.
Accessing /home/user/foo.html in firefox would become file:// for the protocol and /home/user/foo.html for the path.
Joining everything, your three slashes: file:///home/user/foo.html
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750549</id>
	<title>Re:DNS</title>
	<author>steelfood</author>
	<datestamp>1255517700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What's more interesting is that the URL parser here has parsed your second link to go to:</p><p><a href="http://tech.slashdot.org/story/09/10/14/1219215/com/example/foo/bar/baz" title="slashdot.org">http://tech.slashdot.org/story/09/10/14/1219215/com/example/foo/bar/baz</a> [slashdot.org]</p></htmltext>
<tokenext>What 's more interesting is that the URL parser here has parsed your second link to go to : http : //tech.slashdot.org/story/09/10/14/1219215/com/example/foo/bar/baz [ slashdot.org ]</tokentext>
<sentencetext>What's more interesting is that the URL parser here has parsed your second link to go to:http://tech.slashdot.org/story/09/10/14/1219215/com/example/foo/bar/baz [slashdot.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29774401</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>zummit</author>
	<datestamp>1255697460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Who says "double u double u double u"?</p><p>I say - even to new clients, "dub dub dub" and they all understand I really mean "www".</p></htmltext>
<tokenext>Who says " double u double u double u " ? I say - even to new clients , " dub dub dub " and they all understand I really mean " www " .</tokentext>
<sentencetext>Who says "double u double u double u"?I say - even to new clients, "dub dub dub" and they all understand I really mean "www".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749647</id>
	<title>It's too late now!</title>
	<author>ardle</author>
	<datestamp>1255513200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Now we have web services: an extra slash is the least of our problems<nobr> <wbr></nobr>;-)</htmltext>
<tokenext>Now we have web services : an extra slash is the least of our problems ; - )</tokentext>
<sentencetext>Now we have web services: an extra slash is the least of our problems ;-)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744489</id>
	<title>imagine the savings</title>
	<author>Anonymous</author>
	<datestamp>1255534140000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>if the protocol name would have been just "h" instead of "http"!</p></htmltext>
<tokenext>if the protocol name would have been just " h " instead of " http " !</tokentext>
<sentencetext>if the protocol name would have been just "h" instead of "http"!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745643</id>
	<title>Re:Time wasted explaining a slash vs. backslash</title>
	<author>jd2112</author>
	<datestamp>1255538820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Are you saying there is a backlash afainst the backslash?</htmltext>
<tokenext>Are you saying there is a backlash afainst the backslash ?</tokentext>
<sentencetext>Are you saying there is a backlash afainst the backslash?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743585</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749543</id>
	<title>Re:Saying double u double u double u a billion tim</title>
	<author>Eil</author>
	<datestamp>1255512720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Well, WWW was the acronym for his project, "World-Wide Web". He shouldn't feel any remorse for choosing that name as there is really nothing that forces an administrator to use "www.example.com" for the hostname of their web server. They can just as easily call it "web.example.com". I always assumed that the first web admins simply used "www" when setting up their systems because it was convention at the time. They didn't realize what a bad idea it was until they had to speak their URL out loud. (I've done that lots of times with various project/file/function names.) By the time the web went global and became a household name, everyone was using "www" to indicate the web server hostnames because that was the de facto standard.</p><p>It's far from the worst technology mistake that's ever been propagated, though. Maybe 30 years from now something else will make the web obsolete and we'll be talking fondly of all the "http://" and "www" quirks that our old web used to have.</p></htmltext>
<tokenext>Well , WWW was the acronym for his project , " World-Wide Web " .
He should n't feel any remorse for choosing that name as there is really nothing that forces an administrator to use " www.example.com " for the hostname of their web server .
They can just as easily call it " web.example.com " .
I always assumed that the first web admins simply used " www " when setting up their systems because it was convention at the time .
They did n't realize what a bad idea it was until they had to speak their URL out loud .
( I 've done that lots of times with various project/file/function names .
) By the time the web went global and became a household name , everyone was using " www " to indicate the web server hostnames because that was the de facto standard.It 's far from the worst technology mistake that 's ever been propagated , though .
Maybe 30 years from now something else will make the web obsolete and we 'll be talking fondly of all the " http : // " and " www " quirks that our old web used to have .</tokentext>
<sentencetext>Well, WWW was the acronym for his project, "World-Wide Web".
He shouldn't feel any remorse for choosing that name as there is really nothing that forces an administrator to use "www.example.com" for the hostname of their web server.
They can just as easily call it "web.example.com".
I always assumed that the first web admins simply used "www" when setting up their systems because it was convention at the time.
They didn't realize what a bad idea it was until they had to speak their URL out loud.
(I've done that lots of times with various project/file/function names.
) By the time the web went global and became a household name, everyone was using "www" to indicate the web server hostnames because that was the de facto standard.It's far from the worst technology mistake that's ever been propagated, though.
Maybe 30 years from now something else will make the web obsolete and we'll be talking fondly of all the "http://" and "www" quirks that our old web used to have.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746043
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748533
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743935
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750367
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_91</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748887
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_86</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743967
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744961
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746043
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750817
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745103
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745057
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744547
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747667
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_90</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745303
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29755783
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_64</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749361
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_55</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29774401
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_78</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743649
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744497
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_83</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744629
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745863
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746755
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745279
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744249
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744053
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_96</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745053
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749455
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743765
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744579
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_75</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744435
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749439
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743585
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745643
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_105</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750549
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_77</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743467
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745169
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_80</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744495
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747529
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745655
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743859
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_76</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745591
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744709
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_67</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748353
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_108</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747863
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_70</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745369
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744319
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_102</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749747
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743463
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743775
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746521
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_95</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743467
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744997
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744347
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748311
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745303
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29754643
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746773
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744499
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746613
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_94</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744323
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750573
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_68</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743491
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743949
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744367
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_59</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752253
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_62</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746157
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_103</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748059
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_87</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747045
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_58</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743675
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747381
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744763
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745601
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744465
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745285
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744749
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_65</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743675
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744723
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29754881
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_100</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744707
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749469
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_88</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749339
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743467
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743769
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744561
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744411
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_93</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744071
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746993
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743967
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747093
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_84</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750823
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_57</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744611
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752299
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_60</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745303
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748717
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29751751
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_74</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744411
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746519
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744027
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_106</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745133
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29759735
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_99</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745303
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748427
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_81</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745015
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748595
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743467
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29753679
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743675
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744011
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29754273
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744411
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746855
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743463
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743775
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746333
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743609
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743685
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_98</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745195
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743927
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744299
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750691
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743585
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746339
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_79</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743935
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745139
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_109</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744387
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_82</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743609
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744473
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744681
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_73</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29758489
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745625
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_69</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745071
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745487
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_72</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744045
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_63</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746139
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_104</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749543
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745105
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_97</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746571
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744143
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744335
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752431
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_89</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744547
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752241
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746537
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_92</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746145
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_66</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743967
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746405
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_107</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743505
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745773
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_71</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743463
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743775
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744073
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745611
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_101</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750965
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_85</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743463
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743775
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744757
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745297
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743873
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748559
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_56</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743889
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743935
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746471
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_61</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743873
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746429
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_14_1219215_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747707
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743463
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743775
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746333
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746521
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744073
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744757
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745297
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743505
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745773
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745075
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743649
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744497
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743609
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744473
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743685
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743967
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747093
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746405
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744961
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743467
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743769
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744561
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745169
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29753679
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744997
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745865
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743497
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744045
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744053
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29759735
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743765
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744579
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746773
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743585
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745643
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746339
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743537
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743763
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743691
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744347
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748311
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29751751
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752299
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749543
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748353
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744681
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752253
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745105
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744547
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747667
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752241
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749747
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745369
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745133
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745591
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750573
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744611
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29774401
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745625
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744071
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744143
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743511
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745103
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745279
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743771
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743927
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29752431
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745071
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745487
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743491
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743949
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744367
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744411
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745771
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746855
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746519
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743825
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744249
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744027
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744319
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744203
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745195
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744763
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745601
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746993
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746157
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744709
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743645
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743557
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745053
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749455
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745057
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743651
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744629
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750965
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750823
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744465
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745285
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744335
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746139
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744947
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743837
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743789
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743633
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743675
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747381
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744011
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29754273
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744723
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744519
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743915
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743747
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749339
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745049
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29754881
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747863
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746145
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750549
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748059
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746043
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748533
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750817
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744323
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744387
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29758489
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745015
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748595
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744749
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744299
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750691
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745863
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747045
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746755
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748887
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745655
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745611
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743531
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743935
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746471
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745139
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750367
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743859
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743873
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748559
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746429
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29745303
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748717
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29754643
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29755783
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29748427
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746537
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744495
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747529
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744499
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746613
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743589
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29746571
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749361
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29747707
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744435
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749439
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29744707
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29749469
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29743889
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_14_1219215.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_14_1219215.29750359
</commentlist>
</conversation>
