<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article10_01_15_0826253</id>
	<title>Dragging Telephone Numbers Into the Internet Age</title>
	<author>timothy</author>
	<datestamp>1263560460000</datestamp>
	<htmltext>azoblue writes with this teaser from Ars Technica, presenting a tempting suggestion for online consolidation: <i>"E-mail, IM, Facebook, phones&mdash;what if all of these ways to reach you over a network could be <a href="http://arstechnica.com/business/news/2010/01/enum-dragging-telephone-numbers-into-the-internet-age.ars">condensed into a single, unique number</a>? The ENUM proposal aims to do just that, by giving everyone a single phone number that maps to all of their identifiers. Here's how it works, and why it isn't already widely used."</i></htmltext>
<tokenext>azoblue writes with this teaser from Ars Technica , presenting a tempting suggestion for online consolidation : " E-mail , IM , Facebook , phones    what if all of these ways to reach you over a network could be condensed into a single , unique number ?
The ENUM proposal aims to do just that , by giving everyone a single phone number that maps to all of their identifiers .
Here 's how it works , and why it is n't already widely used .
"</tokentext>
<sentencetext>azoblue writes with this teaser from Ars Technica, presenting a tempting suggestion for online consolidation: "E-mail, IM, Facebook, phones—what if all of these ways to reach you over a network could be condensed into a single, unique number?
The ENUM proposal aims to do just that, by giving everyone a single phone number that maps to all of their identifiers.
Here's how it works, and why it isn't already widely used.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778980</id>
	<title>Re:Why would you want to keep the telephone number</title>
	<author>wvmarle</author>
	<datestamp>1263571320000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>A number is very easy to give over the phone. Easier than an e-mail address. This as so many letters sound very similar and so.
</p><p>In practice I have been giving my fax number over the phone so they could fax me their e-mail address. Works great! Particularly considering I am often working with Chinese and other Asians with sometimes very poor spoken command of English. Numbers then go remarkably easy.</p></htmltext>
<tokenext>A number is very easy to give over the phone .
Easier than an e-mail address .
This as so many letters sound very similar and so .
In practice I have been giving my fax number over the phone so they could fax me their e-mail address .
Works great !
Particularly considering I am often working with Chinese and other Asians with sometimes very poor spoken command of English .
Numbers then go remarkably easy .</tokentext>
<sentencetext>A number is very easy to give over the phone.
Easier than an e-mail address.
This as so many letters sound very similar and so.
In practice I have been giving my fax number over the phone so they could fax me their e-mail address.
Works great!
Particularly considering I am often working with Chinese and other Asians with sometimes very poor spoken command of English.
Numbers then go remarkably easy.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778712</id>
	<title>Re:Enum: why you want it</title>
	<author>ascari</author>
	<datestamp>1263569820000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>My email and my phone number are the two things in my life that are constantly subject to abuse by outsiders. (Spammers, telemarketers etc.) You have not made a convincing case why it's actually a good idea to extend merger them or to other aspects of my life.</htmltext>
<tokenext>My email and my phone number are the two things in my life that are constantly subject to abuse by outsiders .
( Spammers , telemarketers etc .
) You have not made a convincing case why it 's actually a good idea to extend merger them or to other aspects of my life .</tokentext>
<sentencetext>My email and my phone number are the two things in my life that are constantly subject to abuse by outsiders.
(Spammers, telemarketers etc.
) You have not made a convincing case why it's actually a good idea to extend merger them or to other aspects of my life.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778044</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778226</id>
	<title>Re:I don't want a "number"</title>
	<author>T Murphy</author>
	<datestamp>1263567240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I don't see the harm in standardizing a number system to use, then adding a name-based system on top of that- exactly the way DNS works in the first place. Not to mention I don't care to have a new version of domain squatters rush in just yet.</htmltext>
<tokenext>I do n't see the harm in standardizing a number system to use , then adding a name-based system on top of that- exactly the way DNS works in the first place .
Not to mention I do n't care to have a new version of domain squatters rush in just yet .</tokentext>
<sentencetext>I don't see the harm in standardizing a number system to use, then adding a name-based system on top of that- exactly the way DNS works in the first place.
Not to mention I don't care to have a new version of domain squatters rush in just yet.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777800</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777990</id>
	<title>Reminds me of Compuserve almost 20 years ago</title>
	<author>Bill\_the\_Engineer</author>
	<datestamp>1263565680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Who could forget the PITA it was to transcribe someones compuserve number, so that they can send a email later?
</p><p>Hell I forgot my Compuserve number...
</p><p>It almost reminds me of the old telegraph days (My office used telegraph to send message to ships). I had a telegraph number and an answer back.</p></htmltext>
<tokenext>Who could forget the PITA it was to transcribe someones compuserve number , so that they can send a email later ?
Hell I forgot my Compuserve number.. . It almost reminds me of the old telegraph days ( My office used telegraph to send message to ships ) .
I had a telegraph number and an answer back .</tokentext>
<sentencetext>Who could forget the PITA it was to transcribe someones compuserve number, so that they can send a email later?
Hell I forgot my Compuserve number...
It almost reminds me of the old telegraph days (My office used telegraph to send message to ships).
I had a telegraph number and an answer back.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778562</id>
	<title>Re:I am not a number! I am a free man!</title>
	<author>Amorymeltzer</author>
	<datestamp>1263569100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Just guessing, but maybe because that was the better part of half a century ago?</p></htmltext>
<tokenext>Just guessing , but maybe because that was the better part of half a century ago ?</tokentext>
<sentencetext>Just guessing, but maybe because that was the better part of half a century ago?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777956</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792</id>
	<title>Re:Single person != single identity</title>
	<author>snspdaarf</author>
	<datestamp>1263570180000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p><div class="quote"><p>I do not want a single number, because I do not have a single identity.</p></div><p>Exactly. At home, I am a cop. In an internet chat room, I am a 15 year old girl who's parents have
gone away for the weekend.</p></div>
	</htmltext>
<tokenext>I do not want a single number , because I do not have a single identity.Exactly .
At home , I am a cop .
In an internet chat room , I am a 15 year old girl who 's parents have gone away for the weekend .</tokentext>
<sentencetext>I do not want a single number, because I do not have a single identity.Exactly.
At home, I am a cop.
In an internet chat room, I am a 15 year old girl who's parents have
gone away for the weekend.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779570</id>
	<title>Re:Obsolete</title>
	<author>Alnitak73</author>
	<datestamp>1263574500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>They add your phone number from caller id to their address book.</p></div><p>Yes, and if they install something like my  Enumdroid app (ENUM lookups for Android) then any time you call them thereafter it can automatically find their current SIP, Skype, EMail, Jabber, Twitter IDs etc just by looking them up in ENUM keyed off that previously received Caller ID.</p></div>
	</htmltext>
<tokenext>They add your phone number from caller id to their address book.Yes , and if they install something like my Enumdroid app ( ENUM lookups for Android ) then any time you call them thereafter it can automatically find their current SIP , Skype , EMail , Jabber , Twitter IDs etc just by looking them up in ENUM keyed off that previously received Caller ID .</tokentext>
<sentencetext>They add your phone number from caller id to their address book.Yes, and if they install something like my  Enumdroid app (ENUM lookups for Android) then any time you call them thereafter it can automatically find their current SIP, Skype, EMail, Jabber, Twitter IDs etc just by looking them up in ENUM keyed off that previously received Caller ID.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777924</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781920</id>
	<title>Re:Numbers? That's what URLs are for!</title>
	<author>SuperQ</author>
	<datestamp>1263584400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yup, phone numbers are stupid.  Organizing communication by user@domain is a much better way to to do it.  This makes it easy for people to have multiple, but easy to remember identities.   I have my user@work.com and my personal handle@personal.net.  People who don't have a personal.net can simply use a service like gmail.com.  Wouldn't it be nice if you could just remember someone's gmail, hotmail, yahoo, whatever address and that was your way to contact them via email, chat, or voice/video?</p></htmltext>
<tokenext>Yup , phone numbers are stupid .
Organizing communication by user @ domain is a much better way to to do it .
This makes it easy for people to have multiple , but easy to remember identities .
I have my user @ work.com and my personal handle @ personal.net .
People who do n't have a personal.net can simply use a service like gmail.com .
Would n't it be nice if you could just remember someone 's gmail , hotmail , yahoo , whatever address and that was your way to contact them via email , chat , or voice/video ?</tokentext>
<sentencetext>Yup, phone numbers are stupid.
Organizing communication by user@domain is a much better way to to do it.
This makes it easy for people to have multiple, but easy to remember identities.
I have my user@work.com and my personal handle@personal.net.
People who don't have a personal.net can simply use a service like gmail.com.
Wouldn't it be nice if you could just remember someone's gmail, hotmail, yahoo, whatever address and that was your way to contact them via email, chat, or voice/video?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778032</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779066</id>
	<title>Wow, great concept</title>
	<author>Anonymous</author>
	<datestamp>1263571740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I can't believe nobody has thought of this before!</p></htmltext>
<tokenext>I ca n't believe nobody has thought of this before !</tokentext>
<sentencetext>I can't believe nobody has thought of this before!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780492</id>
	<title>Re:How about using IP6?</title>
	<author>Dynedain</author>
	<datestamp>1263578880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>No, IPV6 is the exact opposite! IPV6 is meant so that every device has a unique address. What the article is talking about is a unique address per person that bridges multiple devices.</p></htmltext>
<tokenext>No , IPV6 is the exact opposite !
IPV6 is meant so that every device has a unique address .
What the article is talking about is a unique address per person that bridges multiple devices .</tokentext>
<sentencetext>No, IPV6 is the exact opposite!
IPV6 is meant so that every device has a unique address.
What the article is talking about is a unique address per person that bridges multiple devices.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777784</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777802</id>
	<title>Some questions</title>
	<author>QuietLagoon</author>
	<datestamp>1263564660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Who has access to search through all the mappings that are created?  Why stop at just a single phone number, why not have a single identity number and map everything (phone numbers, bank accounts, paychecks, etc.) to that single number.   Who would then even need a name, just write your identity number on a sticky note and put it on your forehead, or embed a RFID chip in you at birth.</htmltext>
<tokenext>Who has access to search through all the mappings that are created ?
Why stop at just a single phone number , why not have a single identity number and map everything ( phone numbers , bank accounts , paychecks , etc .
) to that single number .
Who would then even need a name , just write your identity number on a sticky note and put it on your forehead , or embed a RFID chip in you at birth .</tokentext>
<sentencetext>Who has access to search through all the mappings that are created?
Why stop at just a single phone number, why not have a single identity number and map everything (phone numbers, bank accounts, paychecks, etc.
) to that single number.
Who would then even need a name, just write your identity number on a sticky note and put it on your forehead, or embed a RFID chip in you at birth.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30783308</id>
	<title>Re:How about using IP6?</title>
	<author>alexhs</author>
	<datestamp>1263547440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>No, IPV6 is meant so that every device has a unique address</p></div><p>Not exactly. Think about masks.<br>The last 6 bytes in a IPv6 adress are the MAC address of the device.<br>The 10 first bytes are enough to identify you.<br>Actually I think that was the whole point of IPv4 classes, easing routing and DNS searches by having meaningful prefixes.</p><p>IPv6 was also my first thought. Have your own 80 bits prefix to identify you, and have the remaining 48 bits to do whatever you want with.</p></div>
	</htmltext>
<tokenext>No , IPV6 is meant so that every device has a unique addressNot exactly .
Think about masks.The last 6 bytes in a IPv6 adress are the MAC address of the device.The 10 first bytes are enough to identify you.Actually I think that was the whole point of IPv4 classes , easing routing and DNS searches by having meaningful prefixes.IPv6 was also my first thought .
Have your own 80 bits prefix to identify you , and have the remaining 48 bits to do whatever you want with .</tokentext>
<sentencetext>No, IPV6 is meant so that every device has a unique addressNot exactly.
Think about masks.The last 6 bytes in a IPv6 adress are the MAC address of the device.The 10 first bytes are enough to identify you.Actually I think that was the whole point of IPv4 classes, easing routing and DNS searches by having meaningful prefixes.IPv6 was also my first thought.
Have your own 80 bits prefix to identify you, and have the remaining 48 bits to do whatever you want with.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780492</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779014</id>
	<title>I already have a unique ID</title>
	<author>BitZtream</author>
	<datestamp>1263571560000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>I already have this.  Its my email address.  Everything I do on the Internet is keyed to an email address.</p><p>Email is email, obviously.<br>XMPP for IM, uses my email address.<br>Facebook I don't use, I actually have a live so I don't have time to sit around and convince others that I have one or to collect friends for the popularity contest.<br>Phones - If I email you, you'll get my phone number.  This won't be an issue for too much longer I don't think, its just going to take everyone finally going to VoIP (cringe)</p><p>So uhm, this is a solution searching for a problem I take it?</p></htmltext>
<tokenext>I already have this .
Its my email address .
Everything I do on the Internet is keyed to an email address.Email is email , obviously.XMPP for IM , uses my email address.Facebook I do n't use , I actually have a live so I do n't have time to sit around and convince others that I have one or to collect friends for the popularity contest.Phones - If I email you , you 'll get my phone number .
This wo n't be an issue for too much longer I do n't think , its just going to take everyone finally going to VoIP ( cringe ) So uhm , this is a solution searching for a problem I take it ?</tokentext>
<sentencetext>I already have this.
Its my email address.
Everything I do on the Internet is keyed to an email address.Email is email, obviously.XMPP for IM, uses my email address.Facebook I don't use, I actually have a live so I don't have time to sit around and convince others that I have one or to collect friends for the popularity contest.Phones - If I email you, you'll get my phone number.
This won't be an issue for too much longer I don't think, its just going to take everyone finally going to VoIP (cringe)So uhm, this is a solution searching for a problem I take it?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779308</id>
	<title>Cost rules</title>
	<author>jeroen94704</author>
	<datestamp>1263573240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Here's how it works, and why it isn't already widely used.</p></div><p>The reason it's not widely used yet, and why it will not be widely used by individuals (a requirement for ENUM to become useful, IMHO), is because when registering an ENUM number costs EUR 45 signup fee + EUR 1.79/month, according to the website of one of the registrars that is currently contracted to sell ENUM numbers in the Netherlands.</p></div>
	</htmltext>
<tokenext>Here 's how it works , and why it is n't already widely used.The reason it 's not widely used yet , and why it will not be widely used by individuals ( a requirement for ENUM to become useful , IMHO ) , is because when registering an ENUM number costs EUR 45 signup fee + EUR 1.79/month , according to the website of one of the registrars that is currently contracted to sell ENUM numbers in the Netherlands .</tokentext>
<sentencetext>Here's how it works, and why it isn't already widely used.The reason it's not widely used yet, and why it will not be widely used by individuals (a requirement for ENUM to become useful, IMHO), is because when registering an ENUM number costs EUR 45 signup fee + EUR 1.79/month, according to the website of one of the registrars that is currently contracted to sell ENUM numbers in the Netherlands.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778336</id>
	<title>It has been done many years before...</title>
	<author>ctrl-alt-canc</author>
	<datestamp>1263567900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>...but you had to dial a <a href="http://en.wikipedia.org/wiki/G\%C3\%B6del\_numbering" title="wikipedia.org" rel="nofollow">very long number</a> [wikipedia.org]. I hope they will offer a better solution.</p></htmltext>
<tokenext>...but you had to dial a very long number [ wikipedia.org ] .
I hope they will offer a better solution .</tokentext>
<sentencetext>...but you had to dial a very long number [wikipedia.org].
I hope they will offer a better solution.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779844</id>
	<title>Was Lucas right?</title>
	<author>VirtualUK</author>
	<datestamp>1263576060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Maybe names like <a href="http://us.imdb.com/title/tt0066434/" title="imdb.com">THX-1138</a> [imdb.com] aren't that far off in the future after all?</p></htmltext>
<tokenext>Maybe names like THX-1138 [ imdb.com ] are n't that far off in the future after all ?</tokentext>
<sentencetext>Maybe names like THX-1138 [imdb.com] aren't that far off in the future after all?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777932</id>
	<title>Not good enough</title>
	<author>rennerik</author>
	<datestamp>1263565440000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>Pfft, phone numbers.  That's so 19th century.  They really should come up with something a lot more <i>modern</i>.  Ahhh yes, I can see it now:<br> <br>

"Oh my number?  Sure, no problem.  Do you have a pen?  Here we go: f3a9d4c1-0bff-4792-bf3b-09513ef61af8.  It forwards to my home, though, so don't call too late.  You can also use it to text me, or IM me.  Looking forward to hearing from you!"</htmltext>
<tokenext>Pfft , phone numbers .
That 's so 19th century .
They really should come up with something a lot more modern .
Ahhh yes , I can see it now : " Oh my number ?
Sure , no problem .
Do you have a pen ?
Here we go : f3a9d4c1-0bff-4792-bf3b-09513ef61af8 .
It forwards to my home , though , so do n't call too late .
You can also use it to text me , or IM me .
Looking forward to hearing from you !
"</tokentext>
<sentencetext>Pfft, phone numbers.
That's so 19th century.
They really should come up with something a lot more modern.
Ahhh yes, I can see it now: 

"Oh my number?
Sure, no problem.
Do you have a pen?
Here we go: f3a9d4c1-0bff-4792-bf3b-09513ef61af8.
It forwards to my home, though, so don't call too late.
You can also use it to text me, or IM me.
Looking forward to hearing from you!
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777780</id>
	<title>I for one do not welcome this</title>
	<author>For a Free Internet</author>
	<datestamp>1263564480000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><p>It is an invasion of my privacy and my right to have many numbers. Why should only Italians have multiple digits and addresses? America's hard working Christian Farmers and Small Business Owners created the Internet and should control who calls us on our telephones, not some Italian layabouts down in Mexico.</p></htmltext>
<tokenext>It is an invasion of my privacy and my right to have many numbers .
Why should only Italians have multiple digits and addresses ?
America 's hard working Christian Farmers and Small Business Owners created the Internet and should control who calls us on our telephones , not some Italian layabouts down in Mexico .</tokentext>
<sentencetext>It is an invasion of my privacy and my right to have many numbers.
Why should only Italians have multiple digits and addresses?
America's hard working Christian Farmers and Small Business Owners created the Internet and should control who calls us on our telephones, not some Italian layabouts down in Mexico.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778370</id>
	<title>Re:Single person != single identity</title>
	<author>Speare</author>
	<datestamp>1263568140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>I do not want a single number, because I do not have a single identity.</p></div></blockquote><p>I wonder why more techno-savvy people don't get this point.  A computer doesn't have to have only one network address/interface, why should people?</p></div>
	</htmltext>
<tokenext>I do not want a single number , because I do not have a single identity.I wonder why more techno-savvy people do n't get this point .
A computer does n't have to have only one network address/interface , why should people ?</tokentext>
<sentencetext>I do not want a single number, because I do not have a single identity.I wonder why more techno-savvy people don't get this point.
A computer doesn't have to have only one network address/interface, why should people?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780006</id>
	<title>Re:Not good enough</title>
	<author>apoc.famine</author>
	<datestamp>1263576900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Even if it's that bad, how many times do you enter someone's number in your cell phone? <br>
&nbsp; <br>For most people, it's once. They you sync your address/contact list, and you're done. Honestly, how is that WORSE than inputting in a name, IM handle, email address, home phone, work phone, cell phone, twitter name, facebook name, home address, etc? <br>
&nbsp; <br>While I understand the security/spam issues with tying everything to one number, a hangup based on the data entry is stupid. We tend to enter far more data for an average contact than that.</p></htmltext>
<tokenext>Even if it 's that bad , how many times do you enter someone 's number in your cell phone ?
  For most people , it 's once .
They you sync your address/contact list , and you 're done .
Honestly , how is that WORSE than inputting in a name , IM handle , email address , home phone , work phone , cell phone , twitter name , facebook name , home address , etc ?
  While I understand the security/spam issues with tying everything to one number , a hangup based on the data entry is stupid .
We tend to enter far more data for an average contact than that .</tokentext>
<sentencetext>Even if it's that bad, how many times do you enter someone's number in your cell phone?
  For most people, it's once.
They you sync your address/contact list, and you're done.
Honestly, how is that WORSE than inputting in a name, IM handle, email address, home phone, work phone, cell phone, twitter name, facebook name, home address, etc?
  While I understand the security/spam issues with tying everything to one number, a hangup based on the data entry is stupid.
We tend to enter far more data for an average contact than that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777932</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778560</id>
	<title>Danger of single numbers</title>
	<author>CopaceticOpus</author>
	<datestamp>1263569040000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>A single number to identify people would be just as powerful as a SSN or driver's license number. It would make fraud so much easier. Eventually people would compile databases tying these IDs to SSNs and would distribute those online. Then we would start seeing advisories to keep your single contact number a secret!</p><p>On the positive side, perhaps this would help to convince financial institutions that simply knowing someone's SSN and mother's maiden name doesn't prove anything about identity.</p></htmltext>
<tokenext>A single number to identify people would be just as powerful as a SSN or driver 's license number .
It would make fraud so much easier .
Eventually people would compile databases tying these IDs to SSNs and would distribute those online .
Then we would start seeing advisories to keep your single contact number a secret ! On the positive side , perhaps this would help to convince financial institutions that simply knowing someone 's SSN and mother 's maiden name does n't prove anything about identity .</tokentext>
<sentencetext>A single number to identify people would be just as powerful as a SSN or driver's license number.
It would make fraud so much easier.
Eventually people would compile databases tying these IDs to SSNs and would distribute those online.
Then we would start seeing advisories to keep your single contact number a secret!On the positive side, perhaps this would help to convince financial institutions that simply knowing someone's SSN and mother's maiden name doesn't prove anything about identity.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781564</id>
	<title>Can I ....</title>
	<author>PPH</author>
	<datestamp>1263582960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>... register an ENUM with the registrar of my choice? Maybe I'd like one overseas. Can I select the name resolution service that will handle my ENUM? Maybe I'd like one in a legal jurisdiction that won't bend over every time the Feds come calling. Can I implement custom filters, redirection rules and other features on my ENUM resolution server? Maybe I want to direct certain callers to one site and the riff-raff elsewhere?
</p><p>On the other side of the equation, with all of these capabilities I wonder how long it will be before the ENUM folks implement something like 'domain tasting' and bugger up caller ID, make life easier for shady telemarketers, etc.</p></htmltext>
<tokenext>... register an ENUM with the registrar of my choice ?
Maybe I 'd like one overseas .
Can I select the name resolution service that will handle my ENUM ?
Maybe I 'd like one in a legal jurisdiction that wo n't bend over every time the Feds come calling .
Can I implement custom filters , redirection rules and other features on my ENUM resolution server ?
Maybe I want to direct certain callers to one site and the riff-raff elsewhere ?
On the other side of the equation , with all of these capabilities I wonder how long it will be before the ENUM folks implement something like 'domain tasting ' and bugger up caller ID , make life easier for shady telemarketers , etc .</tokentext>
<sentencetext>... register an ENUM with the registrar of my choice?
Maybe I'd like one overseas.
Can I select the name resolution service that will handle my ENUM?
Maybe I'd like one in a legal jurisdiction that won't bend over every time the Feds come calling.
Can I implement custom filters, redirection rules and other features on my ENUM resolution server?
Maybe I want to direct certain callers to one site and the riff-raff elsewhere?
On the other side of the equation, with all of these capabilities I wonder how long it will be before the ENUM folks implement something like 'domain tasting' and bugger up caller ID, make life easier for shady telemarketers, etc.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778700</id>
	<title>Re:Why would you want to keep the telephone number</title>
	<author>oh\_my\_080980980</author>
	<datestamp>1263569760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Yeah keep thinking that zippy.
<br> <br>
How exactly will emergency phone calls like 911 work?
<br> <br>
Yeah see that's the problem.  There's alot more going on with phone number than you realize.
<br> <br>
Then of course there are the privacy concerns.
<br> <br>
Techno-morons need to think and stop masturbating over shiny new gadets!</htmltext>
<tokenext>Yeah keep thinking that zippy .
How exactly will emergency phone calls like 911 work ?
Yeah see that 's the problem .
There 's alot more going on with phone number than you realize .
Then of course there are the privacy concerns .
Techno-morons need to think and stop masturbating over shiny new gadets !</tokentext>
<sentencetext>Yeah keep thinking that zippy.
How exactly will emergency phone calls like 911 work?
Yeah see that's the problem.
There's alot more going on with phone number than you realize.
Then of course there are the privacy concerns.
Techno-morons need to think and stop masturbating over shiny new gadets!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777856</id>
	<title>Re:It's not the same</title>
	<author>epine</author>
	<datestamp>1263564960000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>Jenny, I got your number<br>I'm gonna make you mine<br>Jenny, I got your number<br>86.75.30.9</p></div></blockquote><p>You, too?  Last visible hop 10.226.70-86.rev.gaoland.net  gaoland.net seems to be slashdotted already.</p><p>One ring to find them all, one ring to bind them.  I wish had the graphics talent to rework that scene where the Nazg&#251;l rider is sniffing the tree roots for sneaky hobbits, and his phone goes off with some super goofy ring tone.  We could redo Orthanc as a wifi repeater and that eyeball as a Pringles can.</p><p>I'd rather have call display that worked reliably.</p></div>
	</htmltext>
<tokenext>Jenny , I got your numberI 'm gon na make you mineJenny , I got your number86.75.30.9You , too ?
Last visible hop 10.226.70-86.rev.gaoland.net gaoland.net seems to be slashdotted already.One ring to find them all , one ring to bind them .
I wish had the graphics talent to rework that scene where the Nazg   l rider is sniffing the tree roots for sneaky hobbits , and his phone goes off with some super goofy ring tone .
We could redo Orthanc as a wifi repeater and that eyeball as a Pringles can.I 'd rather have call display that worked reliably .</tokentext>
<sentencetext>Jenny, I got your numberI'm gonna make you mineJenny, I got your number86.75.30.9You, too?
Last visible hop 10.226.70-86.rev.gaoland.net  gaoland.net seems to be slashdotted already.One ring to find them all, one ring to bind them.
I wish had the graphics talent to rework that scene where the Nazgûl rider is sniffing the tree roots for sneaky hobbits, and his phone goes off with some super goofy ring tone.
We could redo Orthanc as a wifi repeater and that eyeball as a Pringles can.I'd rather have call display that worked reliably.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777762</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30788496</id>
	<title>Re:Single person != single identity</title>
	<author>Anonymous</author>
	<datestamp>1263673200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>lol ill pretend you said 18</p></htmltext>
<tokenext>lol ill pretend you said 18</tokentext>
<sentencetext>lol ill pretend you said 18</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779088</id>
	<title>Integrate other stuff.</title>
	<author>operagost</author>
	<datestamp>1263571920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'd like my Windows recycling bin to point to the trash can under my desk. And<nobr> <wbr></nobr>/dev/null to the toilet.  And my bank account number to point to Warren Buffet's.</p></htmltext>
<tokenext>I 'd like my Windows recycling bin to point to the trash can under my desk .
And /dev/null to the toilet .
And my bank account number to point to Warren Buffet 's .</tokentext>
<sentencetext>I'd like my Windows recycling bin to point to the trash can under my desk.
And /dev/null to the toilet.
And my bank account number to point to Warren Buffet's.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778018</id>
	<title>Re:I don't want a "number"</title>
	<author>Anonymous</author>
	<datestamp>1263565920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>For individuals, I think a number would be a cleaner approach.  The overhead of DNS shouldn't be wasted on something like this when you can already associate phone numbers with contact lists on your cell phone or PDA.  When I call someone, I just go to their name in my address book; I barely know the cell phone numbers of anyone in my family.</p></htmltext>
<tokenext>For individuals , I think a number would be a cleaner approach .
The overhead of DNS should n't be wasted on something like this when you can already associate phone numbers with contact lists on your cell phone or PDA .
When I call someone , I just go to their name in my address book ; I barely know the cell phone numbers of anyone in my family .</tokentext>
<sentencetext>For individuals, I think a number would be a cleaner approach.
The overhead of DNS shouldn't be wasted on something like this when you can already associate phone numbers with contact lists on your cell phone or PDA.
When I call someone, I just go to their name in my address book; I barely know the cell phone numbers of anyone in my family.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777800</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779996</id>
	<title>Unique Number</title>
	<author>Anonymous</author>
	<datestamp>1263576840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I bags PI</p></htmltext>
<tokenext>I bags PI</tokentext>
<sentencetext>I bags PI</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777832</id>
	<title>X.400 all over again</title>
	<author>argent</author>
	<datestamp>1263564840000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>This is making many of the mistakes X.400 did, albeit on a smaller scale.</p><p>People want tokens that are easy to remember. Email addresses like "myname@example.com" are much more memorable than "C=US/OU=Example/FN=My/LN=Name" or "+1 234 456 6789". If someone's using this service, they're using an internet-capable device, so they can enter an alphanumeric address and don't need to remain compatible with Strowger's switch.</p></htmltext>
<tokenext>This is making many of the mistakes X.400 did , albeit on a smaller scale.People want tokens that are easy to remember .
Email addresses like " myname @ example.com " are much more memorable than " C = US/OU = Example/FN = My/LN = Name " or " + 1 234 456 6789 " .
If someone 's using this service , they 're using an internet-capable device , so they can enter an alphanumeric address and do n't need to remain compatible with Strowger 's switch .</tokentext>
<sentencetext>This is making many of the mistakes X.400 did, albeit on a smaller scale.People want tokens that are easy to remember.
Email addresses like "myname@example.com" are much more memorable than "C=US/OU=Example/FN=My/LN=Name" or "+1 234 456 6789".
If someone's using this service, they're using an internet-capable device, so they can enter an alphanumeric address and don't need to remain compatible with Strowger's switch.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777982</id>
	<title>Digital stone age</title>
	<author>Anonymous</author>
	<datestamp>1263565620000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext>So, instead of having a separate email, IM, facebook, phone number, etc we have one unique number? Great so if we forget our unique number we are totally screwed rather than just a little bit screwed. No thanks, if this is the future I'll just stay in the digital stone age.</htmltext>
<tokenext>So , instead of having a separate email , IM , facebook , phone number , etc we have one unique number ?
Great so if we forget our unique number we are totally screwed rather than just a little bit screwed .
No thanks , if this is the future I 'll just stay in the digital stone age .</tokentext>
<sentencetext>So, instead of having a separate email, IM, facebook, phone number, etc we have one unique number?
Great so if we forget our unique number we are totally screwed rather than just a little bit screwed.
No thanks, if this is the future I'll just stay in the digital stone age.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780612</id>
	<title>Re:Single person != single identity</title>
	<author>chord.wav</author>
	<datestamp>1263579300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Batman is that you?</p></htmltext>
<tokenext>Batman is that you ?</tokentext>
<sentencetext>Batman is that you?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781126</id>
	<title>Re:Enum: why you want it</title>
	<author>Anonymous</author>
	<datestamp>1263581340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>What you fail to understand is that not everyone has business cards and for those who do, most have those two pieces of information for business and do NOT include personal email addresses and phone numbers.</p></htmltext>
<tokenext>What you fail to understand is that not everyone has business cards and for those who do , most have those two pieces of information for business and do NOT include personal email addresses and phone numbers .</tokentext>
<sentencetext>What you fail to understand is that not everyone has business cards and for those who do, most have those two pieces of information for business and do NOT include personal email addresses and phone numbers.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778044</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777800</id>
	<title>I don't want a "number"</title>
	<author>jbb999</author>
	<datestamp>1263564660000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>Why would I want a "number" for that? That's why DNS was invented, so we could move forward from using numbers to identify things and use proper identifiers instead. This is a step backwards in many ways.</htmltext>
<tokenext>Why would I want a " number " for that ?
That 's why DNS was invented , so we could move forward from using numbers to identify things and use proper identifiers instead .
This is a step backwards in many ways .</tokentext>
<sentencetext>Why would I want a "number" for that?
That's why DNS was invented, so we could move forward from using numbers to identify things and use proper identifiers instead.
This is a step backwards in many ways.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777846</id>
	<title>Been done: .tel domain</title>
	<author>Anonymous</author>
	<datestamp>1263564900000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>You mean like the<nobr> <wbr></nobr>.tel domain?</p><p><nobr> <wbr></nobr>.tel provides all contact information: phone numbers, postal addresses, email, web addresses, etc -- all within the DNS.</p></htmltext>
<tokenext>You mean like the .tel domain ?
.tel provides all contact information : phone numbers , postal addresses , email , web addresses , etc -- all within the DNS .</tokentext>
<sentencetext>You mean like the .tel domain?
.tel provides all contact information: phone numbers, postal addresses, email, web addresses, etc -- all within the DNS.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779306</id>
	<title>Re:It's not the same</title>
	<author>Chapter80</author>
	<datestamp>1263573240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Impress your friends with geek AND music knowledge.  In addition to being the phone number in the Tommy Tutone song, 867-5309 is also a prime number.  It's also a prime twin, so (I think) 867-5311 is also a prime number</p></div><p>Sorry, I'm not buying it:</p><p><tt><br>&gt;&gt;&gt; print factors(867-5309)<br>1<br>2<br>2221<br></tt></p><p>or did you mean the number 8675309L?</p></div>
	</htmltext>
<tokenext>Impress your friends with geek AND music knowledge .
In addition to being the phone number in the Tommy Tutone song , 867-5309 is also a prime number .
It 's also a prime twin , so ( I think ) 867-5311 is also a prime numberSorry , I 'm not buying it : &gt; &gt; &gt; print factors ( 867-5309 ) 122221or did you mean the number 8675309L ?</tokentext>
<sentencetext>Impress your friends with geek AND music knowledge.
In addition to being the phone number in the Tommy Tutone song, 867-5309 is also a prime number.
It's also a prime twin, so (I think) 867-5311 is also a prime numberSorry, I'm not buying it:&gt;&gt;&gt; print factors(867-5309)122221or did you mean the number 8675309L?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768</id>
	<title>Spam spam spam...</title>
	<author>michelcolman</author>
	<datestamp>1263564360000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>Great, then spammers only need one number to send you all sorts of spam in all kinds of different ways. And even better, they can try random numbers!</htmltext>
<tokenext>Great , then spammers only need one number to send you all sorts of spam in all kinds of different ways .
And even better , they can try random numbers !</tokentext>
<sentencetext>Great, then spammers only need one number to send you all sorts of spam in all kinds of different ways.
And even better, they can try random numbers!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777762</id>
	<title>It's not the same</title>
	<author>plover</author>
	<datestamp>1263564240000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Jenny, I got your number<br>I'm gonna make you mine<br>Jenny, I got your number<br>86.75.30.9</p></htmltext>
<tokenext>Jenny , I got your numberI 'm gon na make you mineJenny , I got your number86.75.30.9</tokentext>
<sentencetext>Jenny, I got your numberI'm gonna make you mineJenny, I got your number86.75.30.9</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777898</id>
	<title>Oh joy, another Universal ID</title>
	<author>wiredog</author>
	<datestamp>1263565140000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>that corporations, governments, and scammers, can use to track us.</p></htmltext>
<tokenext>that corporations , governments , and scammers , can use to track us .</tokentext>
<sentencetext>that corporations, governments, and scammers, can use to track us.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780402</id>
	<title>Re:X.400 all over again</title>
	<author>bartoku</author>
	<datestamp>1263578580000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>I agree an email address is intrinsically easier to remember to a human, but it has a huge flaw I experience all the time. Ever try to give your email address out over the phone, or any combination of unfamiliar letters? 'V' gets confused with 'B' and so on, especially when you have a unique spelling for a a name. My email address and my first name have been malformed a number of times by humans over the phone, but my phone number not once. Numbers are just easier to convey and less ambiguous, I always wondered if by design?
<br> <br>
That being said there are technological solutions to the problem, when I meet someone in person I should not be verbally relaying my address (phone number or email...) we should be doing some digital vcard exchange over Bluetooth or something between our phones. Over the phone I should not be verbally relaying information that is more clearly conveyed in text. When ordering my air plane tickets over the phone (sometimes the human operators can pull off things that the online interface is not letting me do in booking) I should simply be able to switch to instant/text messaging the operator and clearly relay any text as long as I do not hit the wrong key on my damn virtual keyboard...</htmltext>
<tokenext>I agree an email address is intrinsically easier to remember to a human , but it has a huge flaw I experience all the time .
Ever try to give your email address out over the phone , or any combination of unfamiliar letters ?
'V ' gets confused with 'B ' and so on , especially when you have a unique spelling for a a name .
My email address and my first name have been malformed a number of times by humans over the phone , but my phone number not once .
Numbers are just easier to convey and less ambiguous , I always wondered if by design ?
That being said there are technological solutions to the problem , when I meet someone in person I should not be verbally relaying my address ( phone number or email... ) we should be doing some digital vcard exchange over Bluetooth or something between our phones .
Over the phone I should not be verbally relaying information that is more clearly conveyed in text .
When ordering my air plane tickets over the phone ( sometimes the human operators can pull off things that the online interface is not letting me do in booking ) I should simply be able to switch to instant/text messaging the operator and clearly relay any text as long as I do not hit the wrong key on my damn virtual keyboard.. .</tokentext>
<sentencetext>I agree an email address is intrinsically easier to remember to a human, but it has a huge flaw I experience all the time.
Ever try to give your email address out over the phone, or any combination of unfamiliar letters?
'V' gets confused with 'B' and so on, especially when you have a unique spelling for a a name.
My email address and my first name have been malformed a number of times by humans over the phone, but my phone number not once.
Numbers are just easier to convey and less ambiguous, I always wondered if by design?
That being said there are technological solutions to the problem, when I meet someone in person I should not be verbally relaying my address (phone number or email...) we should be doing some digital vcard exchange over Bluetooth or something between our phones.
Over the phone I should not be verbally relaying information that is more clearly conveyed in text.
When ordering my air plane tickets over the phone (sometimes the human operators can pull off things that the online interface is not letting me do in booking) I should simply be able to switch to instant/text messaging the operator and clearly relay any text as long as I do not hit the wrong key on my damn virtual keyboard...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777832</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777930</id>
	<title>My precious!</title>
	<author>Vinegar Joe</author>
	<datestamp>1263565440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>One ring to rule them all!</p></htmltext>
<tokenext>One ring to rule them all !</tokentext>
<sentencetext>One ring to rule them all!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778046</id>
	<title>The simple guide to make money online</title>
	<author>Anonymous</author>
	<datestamp>1263566160000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>1. Join an adult affiliate network and choose a website for promotion</p><p>2.<br>for (enum=0;enum=OVER9000;enum++)<br>{<br>SendMessageToEnum(enum,"Hi! Check out my new website: www.chickswithdicks.com");<br>}</p><p>3. ???</p><p>4. PROFIT!</p></htmltext>
<tokenext>1 .
Join an adult affiliate network and choose a website for promotion2.for ( enum = 0 ; enum = OVER9000 ; enum + + ) { SendMessageToEnum ( enum , " Hi !
Check out my new website : www.chickswithdicks.com " ) ; } 3 .
? ? ? 4. PROFIT !</tokentext>
<sentencetext>1.
Join an adult affiliate network and choose a website for promotion2.for (enum=0;enum=OVER9000;enum++){SendMessageToEnum(enum,"Hi!
Check out my new website: www.chickswithdicks.com");}3.
???4. PROFIT!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780028</id>
	<title>Re:Digital stone age</title>
	<author>apoc.famine</author>
	<datestamp>1263576960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You'll have a lot of company with all the people who forgot their unique number....</p></htmltext>
<tokenext>You 'll have a lot of company with all the people who forgot their unique number... .</tokentext>
<sentencetext>You'll have a lot of company with all the people who forgot their unique number....</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777982</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30800482</id>
	<title>Re:It's not the same</title>
	<author>LordKronos</author>
	<datestamp>1263761640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>And my calculator says that I already pointed out my own mistake 2 hours and 9 minutes before you did. Try reading the replies before posting a redundant one.</p><p>Oh, and also...the +2 insightful I received says the mods don't bother to check math.</p></htmltext>
<tokenext>And my calculator says that I already pointed out my own mistake 2 hours and 9 minutes before you did .
Try reading the replies before posting a redundant one.Oh , and also...the + 2 insightful I received says the mods do n't bother to check math .</tokentext>
<sentencetext>And my calculator says that I already pointed out my own mistake 2 hours and 9 minutes before you did.
Try reading the replies before posting a redundant one.Oh, and also...the +2 insightful I received says the mods don't bother to check math.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782278</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777850</id>
	<title>Why on earth..</title>
	<author>Nomeko</author>
	<datestamp>1263564960000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>would you use the phone number as a universally unique id?</p><p>One user might have several phone numbers, while the one phone number might have several users.</p><p>Additionally, the phone number is not portable across national borders. You can not bring your Norwegian phone number and use it with an american registrar.</p><p>Additionally users might be forced at regular basis to change their phone numbers. Me for one, had to change my phone number when I changed employer.</p><p>Database designers have known this for ages. Always assign a new unique id to any row in a table. Ids that seem unique and stable might change. Even social security numbers might change.</p><p>Oh.. Who would want all their contact info to be collected in one global system available for all?</p></htmltext>
<tokenext>would you use the phone number as a universally unique id ? One user might have several phone numbers , while the one phone number might have several users.Additionally , the phone number is not portable across national borders .
You can not bring your Norwegian phone number and use it with an american registrar.Additionally users might be forced at regular basis to change their phone numbers .
Me for one , had to change my phone number when I changed employer.Database designers have known this for ages .
Always assign a new unique id to any row in a table .
Ids that seem unique and stable might change .
Even social security numbers might change.Oh.. Who would want all their contact info to be collected in one global system available for all ?</tokentext>
<sentencetext>would you use the phone number as a universally unique id?One user might have several phone numbers, while the one phone number might have several users.Additionally, the phone number is not portable across national borders.
You can not bring your Norwegian phone number and use it with an american registrar.Additionally users might be forced at regular basis to change their phone numbers.
Me for one, had to change my phone number when I changed employer.Database designers have known this for ages.
Always assign a new unique id to any row in a table.
Ids that seem unique and stable might change.
Even social security numbers might change.Oh.. Who would want all their contact info to be collected in one global system available for all?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781878</id>
	<title>Re: VoIP you say?</title>
	<author>blueforce</author>
	<datestamp>1263584160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>VoIP, you say?

This me$asge wa dictat@# usi#n9g a VoI#33P connection-on-on-on.  Hope\%^full^y b\%and(*width impro-o-oves by by then.</htmltext>
<tokenext>VoIP , you say ?
This me $ asge wa dictat @ # usi # n9g a VoI # 33P connection-on-on-on .
Hope \ % ^ full ^ y b \ % and ( * width impro-o-oves by by then .</tokentext>
<sentencetext>VoIP, you say?
This me$asge wa dictat@# usi#n9g a VoI#33P connection-on-on-on.
Hope\%^full^y b\%and(*width impro-o-oves by by then.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778486</id>
	<title>Just say no</title>
	<author>LiteralBoy</author>
	<datestamp>1263568740000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>I see nothing wrong with keeping email, IM, Facebook and whatever else separate from my phone number. Despite the conventional wisdom of this age, I have no desire to be "constantly connected" and reachable, much less have it all rolled into one convenient number.

Besides the "one stop" hacking opportunity alluded to in someone else's comment above, it also strikes me as one more step towards a world of constant surveillance.</htmltext>
<tokenext>I see nothing wrong with keeping email , IM , Facebook and whatever else separate from my phone number .
Despite the conventional wisdom of this age , I have no desire to be " constantly connected " and reachable , much less have it all rolled into one convenient number .
Besides the " one stop " hacking opportunity alluded to in someone else 's comment above , it also strikes me as one more step towards a world of constant surveillance .</tokentext>
<sentencetext>I see nothing wrong with keeping email, IM, Facebook and whatever else separate from my phone number.
Despite the conventional wisdom of this age, I have no desire to be "constantly connected" and reachable, much less have it all rolled into one convenient number.
Besides the "one stop" hacking opportunity alluded to in someone else's comment above, it also strikes me as one more step towards a world of constant surveillance.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778994</id>
	<title>Re:Why would you want to keep the telephone number</title>
	<author>complete loony</author>
	<datestamp>1263571380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Why would you want to keep the telephone number?</p></div><p>Long term? You don't. But as the world moves to SIP or some other telephony solution that runs on the internet, some people in the world will be stuck for some time on a POTS exchange with a simple phone that can only dial numbers. So what if that exchange didn't have to use the normal international phone network but could use DNS to find a SIP server to route the call to directly over the internet?</p></div>
	</htmltext>
<tokenext>Why would you want to keep the telephone number ? Long term ?
You do n't .
But as the world moves to SIP or some other telephony solution that runs on the internet , some people in the world will be stuck for some time on a POTS exchange with a simple phone that can only dial numbers .
So what if that exchange did n't have to use the normal international phone network but could use DNS to find a SIP server to route the call to directly over the internet ?</tokentext>
<sentencetext>Why would you want to keep the telephone number?Long term?
You don't.
But as the world moves to SIP or some other telephony solution that runs on the internet, some people in the world will be stuck for some time on a POTS exchange with a simple phone that can only dial numbers.
So what if that exchange didn't have to use the normal international phone network but could use DNS to find a SIP server to route the call to directly over the internet?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779590</id>
	<title>Re:Digital stone age</title>
	<author>Alnitak73</author>
	<datestamp>1263574620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>No, you've missed the point.  You can (and should) still have all those IDs.  But they can be found by looking them up in the ENUM database with your telephone number as the key.</htmltext>
<tokenext>No , you 've missed the point .
You can ( and should ) still have all those IDs .
But they can be found by looking them up in the ENUM database with your telephone number as the key .</tokentext>
<sentencetext>No, you've missed the point.
You can (and should) still have all those IDs.
But they can be found by looking them up in the ENUM database with your telephone number as the key.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777982</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777818</id>
	<title>You mean...</title>
	<author>Anonymous</author>
	<datestamp>1263564720000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Like a social security number or tax id?</p></htmltext>
<tokenext>Like a social security number or tax id ?</tokentext>
<sentencetext>Like a social security number or tax id?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781230</id>
	<title>Re:Spam spam spam... (private# and aliases)</title>
	<author>Anonymous</author>
	<datestamp>1263581760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I also came to that conclusion. Google voice is a good start. You can use a disposable number that points to a personal number.</p></htmltext>
<tokenext>I also came to that conclusion .
Google voice is a good start .
You can use a disposable number that points to a personal number .</tokentext>
<sentencetext>I also came to that conclusion.
Google voice is a good start.
You can use a disposable number that points to a personal number.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779146</id>
	<title>Re:Enum: why you want it</title>
	<author>-homb-</author>
	<datestamp>1263572280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>But why would you want ENUM when<nobr> <wbr></nobr>.tel already does it in much more generalized way, and with encryption to boot?</p></htmltext>
<tokenext>But why would you want ENUM when .tel already does it in much more generalized way , and with encryption to boot ?</tokentext>
<sentencetext>But why would you want ENUM when .tel already does it in much more generalized way, and with encryption to boot?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778044</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778860</id>
	<title>old news</title>
	<author>fulldecent</author>
	<datestamp>1263570600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is already done. It's called an email address.</p><p>Import your gmail contacts to find new friends on facebook. this concept is applied many ways.</p></htmltext>
<tokenext>This is already done .
It 's called an email address.Import your gmail contacts to find new friends on facebook .
this concept is applied many ways .</tokentext>
<sentencetext>This is already done.
It's called an email address.Import your gmail contacts to find new friends on facebook.
this concept is applied many ways.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780116</id>
	<title>Re:Numbers? That's what URLs are for!</title>
	<author>burkmat</author>
	<datestamp>1263577440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I believe the official explanation is that "<a href="http://tech.slashdot.org/story/09/10/14/1219215/" title="slashdot.org" rel="nofollow">it seemed like a good idea at the time.</a> [slashdot.org]"</htmltext>
<tokenext>I believe the official explanation is that " it seemed like a good idea at the time .
[ slashdot.org ] "</tokentext>
<sentencetext>I believe the official explanation is that "it seemed like a good idea at the time.
[slashdot.org]"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778032</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779328</id>
	<title>Re:I am not a number! I am a free man!</title>
	<author>Anonymous</author>
	<datestamp>1263573300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>We were all waiting for You!</p></htmltext>
<tokenext>We were all waiting for You !</tokentext>
<sentencetext>We were all waiting for You!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777956</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777870</id>
	<title>why backword?</title>
	<author>xonicx</author>
	<datestamp>1263565080000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>ENUM is a temporary workaround to make SIPURI and TelURI compatible. Once everyone start using sipuri, enum will phaseout. joe@airtel.com is easier to remember than +918764233906</htmltext>
<tokenext>ENUM is a temporary workaround to make SIPURI and TelURI compatible .
Once everyone start using sipuri , enum will phaseout .
joe @ airtel.com is easier to remember than + 918764233906</tokentext>
<sentencetext>ENUM is a temporary workaround to make SIPURI and TelURI compatible.
Once everyone start using sipuri, enum will phaseout.
joe@airtel.com is easier to remember than +918764233906</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777820</id>
	<title>And</title>
	<author>JustOK</author>
	<datestamp>1263564720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Tattooed on our foreheads</p></htmltext>
<tokenext>Tattooed on our foreheads</tokentext>
<sentencetext>Tattooed on our foreheads</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779318</id>
	<title>Use ICQ numbers!</title>
	<author>Mishotaki</author>
	<datestamp>1263573300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It's not like anyone uses them anymore...</htmltext>
<tokenext>It 's not like anyone uses them anymore.. .</tokentext>
<sentencetext>It's not like anyone uses them anymore...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779440</id>
	<title>SSN</title>
	<author>Anonymous</author>
	<datestamp>1263573900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Why don't they just use our social security numbers as our ENUM?</p><p>I'm sure it's already linked to in all gov databases to your phone/address/CC/personal info, it would make things easier and more transparent, right?</p><p>(Oh that's right, lets keep the illusion of personal privacy).</p></htmltext>
<tokenext>Why do n't they just use our social security numbers as our ENUM ? I 'm sure it 's already linked to in all gov databases to your phone/address/CC/personal info , it would make things easier and more transparent , right ?
( Oh that 's right , lets keep the illusion of personal privacy ) .</tokentext>
<sentencetext>Why don't they just use our social security numbers as our ENUM?I'm sure it's already linked to in all gov databases to your phone/address/CC/personal info, it would make things easier and more transparent, right?
(Oh that's right, lets keep the illusion of personal privacy).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30783602</id>
	<title>My number</title>
	<author>Anonymous</author>
	<datestamp>1263548760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>42</p></htmltext>
<tokenext>42</tokentext>
<sentencetext>42</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778044</id>
	<title>Enum: why you want it</title>
	<author>Raindeer</author>
	<datestamp>1263566100000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>I'm the author of the piece. Most comments in my opinion make the mistake of saying: I want this or that to be my identifier. Or I don't want a universal identifier.</p><p>The reality is: there are two identifiers that are on most business cards. Phone numbers and e-mail adresses. Both could be used in a much more advanced way. No matter which way you look at it the telephone number won't go away. ENUM would enable you to use it in multiple ways.</p></htmltext>
<tokenext>I 'm the author of the piece .
Most comments in my opinion make the mistake of saying : I want this or that to be my identifier .
Or I do n't want a universal identifier.The reality is : there are two identifiers that are on most business cards .
Phone numbers and e-mail adresses .
Both could be used in a much more advanced way .
No matter which way you look at it the telephone number wo n't go away .
ENUM would enable you to use it in multiple ways .</tokentext>
<sentencetext>I'm the author of the piece.
Most comments in my opinion make the mistake of saying: I want this or that to be my identifier.
Or I don't want a universal identifier.The reality is: there are two identifiers that are on most business cards.
Phone numbers and e-mail adresses.
Both could be used in a much more advanced way.
No matter which way you look at it the telephone number won't go away.
ENUM would enable you to use it in multiple ways.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30786420</id>
	<title>Re:Why would you want to keep the telephone number</title>
	<author>ajlisows</author>
	<datestamp>1263564060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>
<p>Right now when I want to call someone I select that person's name and press "call".  If I want to IM, mail, or text, I press other buttons.</p><p>I can't see why you think email address lists will be any different than the situation most people have right now with their cell phones.  Years ago when my friends and I started using cell phones we swapped numbers, dumped them into our contacts list and never really worried about them again.  I still know by heart all those peoples' home phone numbers from when we were kids but I don't think I could recite half of their current numbers.</p></htmltext>
<tokenext>Right now when I want to call someone I select that person 's name and press " call " .
If I want to IM , mail , or text , I press other buttons.I ca n't see why you think email address lists will be any different than the situation most people have right now with their cell phones .
Years ago when my friends and I started using cell phones we swapped numbers , dumped them into our contacts list and never really worried about them again .
I still know by heart all those peoples ' home phone numbers from when we were kids but I do n't think I could recite half of their current numbers .</tokentext>
<sentencetext>
Right now when I want to call someone I select that person's name and press "call".
If I want to IM, mail, or text, I press other buttons.I can't see why you think email address lists will be any different than the situation most people have right now with their cell phones.
Years ago when my friends and I started using cell phones we swapped numbers, dumped them into our contacts list and never really worried about them again.
I still know by heart all those peoples' home phone numbers from when we were kids but I don't think I could recite half of their current numbers.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778012</id>
	<title>I've been patient</title>
	<author>Anonymous</author>
	<datestamp>1263565920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Great stuff. I've been waiting for years.</p></htmltext>
<tokenext>Great stuff .
I 've been waiting for years .</tokentext>
<sentencetext>Great stuff.
I've been waiting for years.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779616</id>
	<title>Re:It's not the same</title>
	<author>Anonymous</author>
	<datestamp>1263574860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I can confirm this, my prime factoring routine says:<br>8675309 = 8675309^1<br>8675311 = 8675311^1</p><p>However, I first tried the palindrome (didn't read what you meant by a prime twin) and that isn't prime:<br>9035768 = 2^3 + 7^1 + 317^1 + 509^1<br>but the twins palindrome almost is:<br>1135768 = 2^3 + 141971^1</p></htmltext>
<tokenext>I can confirm this , my prime factoring routine says : 8675309 = 8675309 ^ 18675311 = 8675311 ^ 1However , I first tried the palindrome ( did n't read what you meant by a prime twin ) and that is n't prime : 9035768 = 2 ^ 3 + 7 ^ 1 + 317 ^ 1 + 509 ^ 1but the twins palindrome almost is : 1135768 = 2 ^ 3 + 141971 ^ 1</tokentext>
<sentencetext>I can confirm this, my prime factoring routine says:8675309 = 8675309^18675311 = 8675311^1However, I first tried the palindrome (didn't read what you meant by a prime twin) and that isn't prime:9035768 = 2^3 + 7^1 + 317^1 + 509^1but the twins palindrome almost is:1135768 = 2^3 + 141971^1</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779388</id>
	<title>Re:Obsolete</title>
	<author>residieu</author>
	<datestamp>1263573720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>There must be SOME sharing of addresses/numbers there, or the first person can't contact the second person so they can add them to address books. You're right, though. It doesn't have to be memorable, though it helps when I can remember my own phone number, which is tricky some days...</htmltext>
<tokenext>There must be SOME sharing of addresses/numbers there , or the first person ca n't contact the second person so they can add them to address books .
You 're right , though .
It does n't have to be memorable , though it helps when I can remember my own phone number , which is tricky some days.. .</tokentext>
<sentencetext>There must be SOME sharing of addresses/numbers there, or the first person can't contact the second person so they can add them to address books.
You're right, though.
It doesn't have to be memorable, though it helps when I can remember my own phone number, which is tricky some days...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777924</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779920</id>
	<title>Gold Medal</title>
	<author>Anonymous</author>
	<datestamp>1263576480000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>KlaymenDK (713149) wins the gold medal!</p><p>The basic concept of identity management espoused in the article is sound, but it mustn't be tied to a person's physical identity.  People have varying needs from identities, and must be free to create and destroy them as they see fit.  Any system that is used must recognize that.  Further, as it would happen anyway, building it in increases the trust of the system.  If I know that KlaymenDK might have alter egos then I can act accordingly.  That versus being fooled that there is only one identity associated with a physical person which would enable fraud.</p><p>What should be attached to an identity?  Anything that the user wants, including an escrow account (no direct funding should be attached), access to banking, websites, phones, buildings, etc.  But the sensitive ones on that list (again, direct funding, banks, and in some cases building access, etc.) require the identity to be authenticated along with some extra identity that verifies it is the real, unique person.  This could be accomplished in various ways, but building it in to a physical device (eg, a mobile phone) with a single password (for encryption-based authentication) and possibly biometric authentication as well.</p></htmltext>
<tokenext>KlaymenDK ( 713149 ) wins the gold medal ! The basic concept of identity management espoused in the article is sound , but it must n't be tied to a person 's physical identity .
People have varying needs from identities , and must be free to create and destroy them as they see fit .
Any system that is used must recognize that .
Further , as it would happen anyway , building it in increases the trust of the system .
If I know that KlaymenDK might have alter egos then I can act accordingly .
That versus being fooled that there is only one identity associated with a physical person which would enable fraud.What should be attached to an identity ?
Anything that the user wants , including an escrow account ( no direct funding should be attached ) , access to banking , websites , phones , buildings , etc .
But the sensitive ones on that list ( again , direct funding , banks , and in some cases building access , etc .
) require the identity to be authenticated along with some extra identity that verifies it is the real , unique person .
This could be accomplished in various ways , but building it in to a physical device ( eg , a mobile phone ) with a single password ( for encryption-based authentication ) and possibly biometric authentication as well .</tokentext>
<sentencetext>KlaymenDK (713149) wins the gold medal!The basic concept of identity management espoused in the article is sound, but it mustn't be tied to a person's physical identity.
People have varying needs from identities, and must be free to create and destroy them as they see fit.
Any system that is used must recognize that.
Further, as it would happen anyway, building it in increases the trust of the system.
If I know that KlaymenDK might have alter egos then I can act accordingly.
That versus being fooled that there is only one identity associated with a physical person which would enable fraud.What should be attached to an identity?
Anything that the user wants, including an escrow account (no direct funding should be attached), access to banking, websites, phones, buildings, etc.
But the sensitive ones on that list (again, direct funding, banks, and in some cases building access, etc.
) require the identity to be authenticated along with some extra identity that verifies it is the real, unique person.
This could be accomplished in various ways, but building it in to a physical device (eg, a mobile phone) with a single password (for encryption-based authentication) and possibly biometric authentication as well.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781216</id>
	<title>OpenID</title>
	<author>Gaffod</author>
	<datestamp>1263581700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Did not RTFA, but  why not just use OpenID? That way you get one identity across multiple sites, and don't have to remember random numbers. There aren't that many OpenID supporting sites, and when there are a lot have not worked for me (with Google) but when they did work I found the experience to be wonderfully convenient.</p></htmltext>
<tokenext>Did not RTFA , but why not just use OpenID ?
That way you get one identity across multiple sites , and do n't have to remember random numbers .
There are n't that many OpenID supporting sites , and when there are a lot have not worked for me ( with Google ) but when they did work I found the experience to be wonderfully convenient .</tokentext>
<sentencetext>Did not RTFA, but  why not just use OpenID?
That way you get one identity across multiple sites, and don't have to remember random numbers.
There aren't that many OpenID supporting sites, and when there are a lot have not worked for me (with Google) but when they did work I found the experience to be wonderfully convenient.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781516</id>
	<title>Re:Spam spam spam... (private# and aliases)</title>
	<author>Simetrical</author>
	<datestamp>1263582840000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>i've thought about this before - i think what one needs is a single PRIVATE number - that never gets given out to anyone - and you have a bunch of private ALIAS/Reference numbers which you yourself point to your private number - then you only give out the aliases - and if one of the aliases gets overloaded, you pull the plug on the alias, create a new alias, and then direct that new alias towards your private number.</p></div><p>I do that in Gmail with plus-addressing.  For instance, if I get spam from Simetrical+dontsendhere@gmail.com, I can just block all mail from that address.  Haven't had it happen yet, though.</p></div>
	</htmltext>
<tokenext>i 've thought about this before - i think what one needs is a single PRIVATE number - that never gets given out to anyone - and you have a bunch of private ALIAS/Reference numbers which you yourself point to your private number - then you only give out the aliases - and if one of the aliases gets overloaded , you pull the plug on the alias , create a new alias , and then direct that new alias towards your private number.I do that in Gmail with plus-addressing .
For instance , if I get spam from Simetrical + dontsendhere @ gmail.com , I can just block all mail from that address .
Have n't had it happen yet , though .</tokentext>
<sentencetext>i've thought about this before - i think what one needs is a single PRIVATE number - that never gets given out to anyone - and you have a bunch of private ALIAS/Reference numbers which you yourself point to your private number - then you only give out the aliases - and if one of the aliases gets overloaded, you pull the plug on the alias, create a new alias, and then direct that new alias towards your private number.I do that in Gmail with plus-addressing.
For instance, if I get spam from Simetrical+dontsendhere@gmail.com, I can just block all mail from that address.
Haven't had it happen yet, though.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862</id>
	<title>Re:It's not the same</title>
	<author>Anonymous</author>
	<datestamp>1263565020000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>Impress your friends with geek AND music knowledge.  In addition to being the phone number in the Tommy Tutone song, 867-5309 is also a prime number.  It's also a prime twin, so (I think) 867-5311 is also a prime number</p></htmltext>
<tokenext>Impress your friends with geek AND music knowledge .
In addition to being the phone number in the Tommy Tutone song , 867-5309 is also a prime number .
It 's also a prime twin , so ( I think ) 867-5311 is also a prime number</tokentext>
<sentencetext>Impress your friends with geek AND music knowledge.
In addition to being the phone number in the Tommy Tutone song, 867-5309 is also a prime number.
It's also a prime twin, so (I think) 867-5311 is also a prime number</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777762</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782786</id>
	<title>Re:Numbers? That's what URLs are for!</title>
	<author>horza</author>
	<datestamp>1263588180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>But I&rsquo;m not sure about the point of the &ldquo;//&rdquo;</i></p><p>I presume it is to indicate a remote directory, as if you do a single slash it is a local absolute path and no slash means a local relative path. I don't think there is really an inconsistency. One is a URL and the other an email address. Both have clear unambiguous RFCs.</p><p>Phillip.</p></htmltext>
<tokenext>But I    m not sure about the point of the    //    I presume it is to indicate a remote directory , as if you do a single slash it is a local absolute path and no slash means a local relative path .
I do n't think there is really an inconsistency .
One is a URL and the other an email address .
Both have clear unambiguous RFCs.Phillip .</tokentext>
<sentencetext>But I’m not sure about the point of the “//”I presume it is to indicate a remote directory, as if you do a single slash it is a local absolute path and no slash means a local relative path.
I don't think there is really an inconsistency.
One is a URL and the other an email address.
Both have clear unambiguous RFCs.Phillip.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778032</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782160</id>
	<title>Why numbers?</title>
	<author>nsayer</author>
	<datestamp>1263585420000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>In the really, really, REALLY old days of telephony, there were no numbers. You rang up the operator and asked to be connected to the Smith house, and the operator connected your plug to their socket.</p><p>Once that stopped scaling, numbers were used because it made looking them up on a plug board a lot faster. When automatic dialing came, that scaled similarly because you could cascade stepper relays to do the dialing.</p><p>But nowadays telephone switches have more in common with Cisco routers than they do the old gear. There's no reason that you have to number stuff anymore. The instant messaging folks - particularly jabber - are closer to what we need than the old tired PSTN numbering scheme.</p></htmltext>
<tokenext>In the really , really , REALLY old days of telephony , there were no numbers .
You rang up the operator and asked to be connected to the Smith house , and the operator connected your plug to their socket.Once that stopped scaling , numbers were used because it made looking them up on a plug board a lot faster .
When automatic dialing came , that scaled similarly because you could cascade stepper relays to do the dialing.But nowadays telephone switches have more in common with Cisco routers than they do the old gear .
There 's no reason that you have to number stuff anymore .
The instant messaging folks - particularly jabber - are closer to what we need than the old tired PSTN numbering scheme .</tokentext>
<sentencetext>In the really, really, REALLY old days of telephony, there were no numbers.
You rang up the operator and asked to be connected to the Smith house, and the operator connected your plug to their socket.Once that stopped scaling, numbers were used because it made looking them up on a plug board a lot faster.
When automatic dialing came, that scaled similarly because you could cascade stepper relays to do the dialing.But nowadays telephone switches have more in common with Cisco routers than they do the old gear.
There's no reason that you have to number stuff anymore.
The instant messaging folks - particularly jabber - are closer to what we need than the old tired PSTN numbering scheme.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779892</id>
	<title>Re:Single person != single identity</title>
	<author>knarfling</author>
	<datestamp>1263576300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Actually, only two of my identities* have delusions, but one of them is paranoid and the other is out to get him. <br> <br> <br>*Personalities.</htmltext>
<tokenext>Actually , only two of my identities * have delusions , but one of them is paranoid and the other is out to get him .
* Personalities .</tokentext>
<sentencetext>Actually, only two of my identities* have delusions, but one of them is paranoid and the other is out to get him.
*Personalities.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777784</id>
	<title>How about using IP6?</title>
	<author>Anonymous</author>
	<datestamp>1263564540000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>A single IP6 address could be enough for all those things.</p></htmltext>
<tokenext>A single IP6 address could be enough for all those things .</tokentext>
<sentencetext>A single IP6 address could be enough for all those things.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778832</id>
	<title>Re:I am not a number! I am a free man!</title>
	<author>L4t3r4lu5</author>
	<datestamp>1263570420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Number 2 is still working out which number I am. He's been going for 4 minutes now. Needless to say "6" was taken by someone closer to the deal than me. I'll be lucky to get something close to my UID. More than likely it'll be something close to my MAC address mixed with the VIN on my car.</htmltext>
<tokenext>Number 2 is still working out which number I am .
He 's been going for 4 minutes now .
Needless to say " 6 " was taken by someone closer to the deal than me .
I 'll be lucky to get something close to my UID .
More than likely it 'll be something close to my MAC address mixed with the VIN on my car .</tokentext>
<sentencetext>Number 2 is still working out which number I am.
He's been going for 4 minutes now.
Needless to say "6" was taken by someone closer to the deal than me.
I'll be lucky to get something close to my UID.
More than likely it'll be something close to my MAC address mixed with the VIN on my car.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777956</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30788606</id>
	<title>Re:Spam spam spam...</title>
	<author>RockDoctor</author>
	<datestamp>1263632880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Great, then spammers only need one number to send you all sorts of spam in all kinds of different ways. And even better, they can try random numbers!</p></div></blockquote><p>Not just spammers ; bosses, wives, girlfriends, parents, landlord, people you owe money to and a whole range of other undesirable contacts too.</p><p>There are perfectly good reasons for not wanting to have a unique personal identifier. And even more not quite perfectly good reasons.</p></div>
	</htmltext>
<tokenext>Great , then spammers only need one number to send you all sorts of spam in all kinds of different ways .
And even better , they can try random numbers ! Not just spammers ; bosses , wives , girlfriends , parents , landlord , people you owe money to and a whole range of other undesirable contacts too.There are perfectly good reasons for not wanting to have a unique personal identifier .
And even more not quite perfectly good reasons .</tokentext>
<sentencetext>Great, then spammers only need one number to send you all sorts of spam in all kinds of different ways.
And even better, they can try random numbers!Not just spammers ; bosses, wives, girlfriends, parents, landlord, people you owe money to and a whole range of other undesirable contacts too.There are perfectly good reasons for not wanting to have a unique personal identifier.
And even more not quite perfectly good reasons.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777924</id>
	<title>Obsolete</title>
	<author>jmyers</author>
	<datestamp>1263565380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Easy to remember numbers or email addresses or anything else are obsolete. Everyone uses an address book built into the phone or other device and never has to remember anything other than your name or what ever they filed it under. People almost never exchange email addresses or phone numbers. You send someone as email so they have your address. They add your phone number from caller id to their address book.</p></htmltext>
<tokenext>Easy to remember numbers or email addresses or anything else are obsolete .
Everyone uses an address book built into the phone or other device and never has to remember anything other than your name or what ever they filed it under .
People almost never exchange email addresses or phone numbers .
You send someone as email so they have your address .
They add your phone number from caller id to their address book .</tokentext>
<sentencetext>Easy to remember numbers or email addresses or anything else are obsolete.
Everyone uses an address book built into the phone or other device and never has to remember anything other than your name or what ever they filed it under.
People almost never exchange email addresses or phone numbers.
You send someone as email so they have your address.
They add your phone number from caller id to their address book.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777774</id>
	<title>Please no!!!</title>
	<author>Choozy</author>
	<datestamp>1263564480000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>All I can think of is SPAM.  I understand the idea and sometimes I think it'd be a great tool (especially if you move ISP's etc, everything would move with you kind of like redirecting your real mail when you move house but with less hassle) but I consider my privacy (what little we have left in this world) way more important than having a single identifier.</p></htmltext>
<tokenext>All I can think of is SPAM .
I understand the idea and sometimes I think it 'd be a great tool ( especially if you move ISP 's etc , everything would move with you kind of like redirecting your real mail when you move house but with less hassle ) but I consider my privacy ( what little we have left in this world ) way more important than having a single identifier .</tokentext>
<sentencetext>All I can think of is SPAM.
I understand the idea and sometimes I think it'd be a great tool (especially if you move ISP's etc, everything would move with you kind of like redirecting your real mail when you move house but with less hassle) but I consider my privacy (what little we have left in this world) way more important than having a single identifier.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779672</id>
	<title>Changing numbers?</title>
	<author>HikingStick</author>
	<datestamp>1263575160000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>In reviewing the comments, I did not notice anyone raising the idea of wanting to (or needing to) change numbers (except one who noted that they like getting a new number when they move so that old acquaintances can be dropped).  If the phone number becomes the primary hook on which all other identities are hung, what happens when you want an unlisted number or have need to change numbers? Victims of domestic abuse, some State employees (like corrections officers), and others have reasons to either switch numbers or request an unlisted number.  In Minnesota, corrections officers can even request vehicle license plates that are registered to the State so that the inmates can't use their personal license plate numbers as a means to have friends on the outside look up personal information on them (the corrections officers).</htmltext>
<tokenext>In reviewing the comments , I did not notice anyone raising the idea of wanting to ( or needing to ) change numbers ( except one who noted that they like getting a new number when they move so that old acquaintances can be dropped ) .
If the phone number becomes the primary hook on which all other identities are hung , what happens when you want an unlisted number or have need to change numbers ?
Victims of domestic abuse , some State employees ( like corrections officers ) , and others have reasons to either switch numbers or request an unlisted number .
In Minnesota , corrections officers can even request vehicle license plates that are registered to the State so that the inmates ca n't use their personal license plate numbers as a means to have friends on the outside look up personal information on them ( the corrections officers ) .</tokentext>
<sentencetext>In reviewing the comments, I did not notice anyone raising the idea of wanting to (or needing to) change numbers (except one who noted that they like getting a new number when they move so that old acquaintances can be dropped).
If the phone number becomes the primary hook on which all other identities are hung, what happens when you want an unlisted number or have need to change numbers?
Victims of domestic abuse, some State employees (like corrections officers), and others have reasons to either switch numbers or request an unlisted number.
In Minnesota, corrections officers can even request vehicle license plates that are registered to the State so that the inmates can't use their personal license plate numbers as a means to have friends on the outside look up personal information on them (the corrections officers).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779302</id>
	<title>On SSN fraud, and identifiers vs. authenticators</title>
	<author>jonaskoelker</author>
	<datestamp>1263573240000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p><div class="quote"><p>A single number to identify people would be just as powerful as a SSN or driver's license number. It would make fraud so much easier.</p></div><p>While you are right in practice, it doesn't need to be so in theory.</p><p>On<nobr> <wbr></nobr>/. you are "CopaceticOpus".  That is, in the slashdot universe you have a single number which identifies you.  Does that make you more vulnerable to<nobr> <wbr></nobr>/. fraud?</p><p>No, you have a password which you use to prove that you are the person identified by the name CopaceticOpus.</p><p>The problem with SSNs is that they don't have a password.</p><p>Using a single identifier isn't a danger in itself; it just magnifies the underlying problem of not having a secure way to establish which people the identifiers identify (and which they don't).</p></div>
	</htmltext>
<tokenext>A single number to identify people would be just as powerful as a SSN or driver 's license number .
It would make fraud so much easier.While you are right in practice , it does n't need to be so in theory.On / .
you are " CopaceticOpus " .
That is , in the slashdot universe you have a single number which identifies you .
Does that make you more vulnerable to / .
fraud ? No , you have a password which you use to prove that you are the person identified by the name CopaceticOpus.The problem with SSNs is that they do n't have a password.Using a single identifier is n't a danger in itself ; it just magnifies the underlying problem of not having a secure way to establish which people the identifiers identify ( and which they do n't ) .</tokentext>
<sentencetext>A single number to identify people would be just as powerful as a SSN or driver's license number.
It would make fraud so much easier.While you are right in practice, it doesn't need to be so in theory.On /.
you are "CopaceticOpus".
That is, in the slashdot universe you have a single number which identifies you.
Does that make you more vulnerable to /.
fraud?No, you have a password which you use to prove that you are the person identified by the name CopaceticOpus.The problem with SSNs is that they don't have a password.Using a single identifier isn't a danger in itself; it just magnifies the underlying problem of not having a secure way to establish which people the identifiers identify (and which they don't).
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778560</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781248</id>
	<title>Single number?</title>
	<author>Gordonjcp</author>
	<datestamp>1263581820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I've had the same mobile number for well over a decade.  If you knew my phone number in 1999, it hasn't changed.  I've lived in a wide range of different places since then, though.</p></htmltext>
<tokenext>I 've had the same mobile number for well over a decade .
If you knew my phone number in 1999 , it has n't changed .
I 've lived in a wide range of different places since then , though .</tokentext>
<sentencetext>I've had the same mobile number for well over a decade.
If you knew my phone number in 1999, it hasn't changed.
I've lived in a wide range of different places since then, though.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778454</id>
	<title>Re:Single person != single identity</title>
	<author>Jason Levine</author>
	<datestamp>1263568560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Perhaps a Grand Central/Google Voice setup would be in order then.  With Google Voice (previously Grand Central), I can give everyone a phone number and it will ring all of my phones.  However, I can also specify some rules.  For example, if someone from my work calls me on my Google Voice number, I can have it only ring my work phone and cell phone and not my wife's cell phone or my home phone.  If I call the Google Voice number, it will call my wife's cell and our home phone, not my cell or work phone.  So you can give your work and personal contacts the same number and what phone(s) it rings would depend on who is calling you.</p></htmltext>
<tokenext>Perhaps a Grand Central/Google Voice setup would be in order then .
With Google Voice ( previously Grand Central ) , I can give everyone a phone number and it will ring all of my phones .
However , I can also specify some rules .
For example , if someone from my work calls me on my Google Voice number , I can have it only ring my work phone and cell phone and not my wife 's cell phone or my home phone .
If I call the Google Voice number , it will call my wife 's cell and our home phone , not my cell or work phone .
So you can give your work and personal contacts the same number and what phone ( s ) it rings would depend on who is calling you .</tokentext>
<sentencetext>Perhaps a Grand Central/Google Voice setup would be in order then.
With Google Voice (previously Grand Central), I can give everyone a phone number and it will ring all of my phones.
However, I can also specify some rules.
For example, if someone from my work calls me on my Google Voice number, I can have it only ring my work phone and cell phone and not my wife's cell phone or my home phone.
If I call the Google Voice number, it will call my wife's cell and our home phone, not my cell or work phone.
So you can give your work and personal contacts the same number and what phone(s) it rings would depend on who is calling you.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778066</id>
	<title>Re:Single person != single identity</title>
	<author>BitKat</author>
	<datestamp>1263566220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Well, with ENUM you can still have those two numbers, each referring to their own set of services. One for home use and one for work. Where's the problem?</p></htmltext>
<tokenext>Well , with ENUM you can still have those two numbers , each referring to their own set of services .
One for home use and one for work .
Where 's the problem ?</tokentext>
<sentencetext>Well, with ENUM you can still have those two numbers, each referring to their own set of services.
One for home use and one for work.
Where's the problem?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779662</id>
	<title>US Specific</title>
	<author>Anonymous</author>
	<datestamp>1263575100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'd be about as likely to give out my social security number as to use this system.</p></htmltext>
<tokenext>I 'd be about as likely to give out my social security number as to use this system .</tokentext>
<sentencetext>I'd be about as likely to give out my social security number as to use this system.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778308</id>
	<title>Re:Single person != single identity</title>
	<author>Anonymous</author>
	<datestamp>1263567720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Hell of a lot of it. If you want to be found, you can easily get your name (with perhaps a general location, like "John Random Loser, Iowa") to be the top google hit. Put everything you please on the page, including any phone numbers, addresses, GPS coordinates, etc. There you go - anyone who knows your name and perhaps some minor detail to tell you apart from namespace crashes can find out all of your contact info. But we don't do that, because of the people we'd prefer didn't find us. We'd like a degree of control over who gets what and a modicum of firewalls to limit damage when one of the IDs get found out by the wrong people and has to be abandoned.</htmltext>
<tokenext>Hell of a lot of it .
If you want to be found , you can easily get your name ( with perhaps a general location , like " John Random Loser , Iowa " ) to be the top google hit .
Put everything you please on the page , including any phone numbers , addresses , GPS coordinates , etc .
There you go - anyone who knows your name and perhaps some minor detail to tell you apart from namespace crashes can find out all of your contact info .
But we do n't do that , because of the people we 'd prefer did n't find us .
We 'd like a degree of control over who gets what and a modicum of firewalls to limit damage when one of the IDs get found out by the wrong people and has to be abandoned .</tokentext>
<sentencetext>Hell of a lot of it.
If you want to be found, you can easily get your name (with perhaps a general location, like "John Random Loser, Iowa") to be the top google hit.
Put everything you please on the page, including any phone numbers, addresses, GPS coordinates, etc.
There you go - anyone who knows your name and perhaps some minor detail to tell you apart from namespace crashes can find out all of your contact info.
But we don't do that, because of the people we'd prefer didn't find us.
We'd like a degree of control over who gets what and a modicum of firewalls to limit damage when one of the IDs get found out by the wrong people and has to be abandoned.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780710</id>
	<title>Re:Spam spam spam...</title>
	<author>Whorhay</author>
	<datestamp>1263579720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Exactly! There are a very small number of people who I would want to have all of my contact information. There is a number of people orders of magnitude larger than the first who I want to have some of my contact information, but definitely not all.</htmltext>
<tokenext>Exactly !
There are a very small number of people who I would want to have all of my contact information .
There is a number of people orders of magnitude larger than the first who I want to have some of my contact information , but definitely not all .</tokentext>
<sentencetext>Exactly!
There are a very small number of people who I would want to have all of my contact information.
There is a number of people orders of magnitude larger than the first who I want to have some of my contact information, but definitely not all.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778456</id>
	<title>Good idea...i think</title>
	<author>hesaigo999ca</author>
	<datestamp>1263568560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Seriously, I do see the advantage...of which your universal number could also become your ssn, and tie into your phone number and drivers license, even your passport, then again why stop there, you could have it easily accessible through a chip or a barcode tattoo...<br>wait a minute, i think i heard of this story before...link <a href="http://en.wikipedia.org/wiki/Number\_of\_the\_Beast" title="wikipedia.org"> here </a> [wikipedia.org]</p></htmltext>
<tokenext>Seriously , I do see the advantage...of which your universal number could also become your ssn , and tie into your phone number and drivers license , even your passport , then again why stop there , you could have it easily accessible through a chip or a barcode tattoo...wait a minute , i think i heard of this story before...link here [ wikipedia.org ]</tokentext>
<sentencetext>Seriously, I do see the advantage...of which your universal number could also become your ssn, and tie into your phone number and drivers license, even your passport, then again why stop there, you could have it easily accessible through a chip or a barcode tattoo...wait a minute, i think i heard of this story before...link  here  [wikipedia.org]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30820240</id>
	<title>Re:Why would you want to keep the telephone number</title>
	<author>bill\_mcgonigle</author>
	<datestamp>1263921120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>I think it will go completely the other way, and that in 50 years people will never have heard of phone numbers. The identifier will be the email address, and if I want to call someone I select that address and press "call", and a VOIP connection will be made. If I want to IM or mail, I press other buttons.</i></p><p>I've had that in place for about a year here.  You just need to add an SRV record, of the form:</p><p>\_sip.\_udp.example.com</p><p>and then have your PBX link the extensions, with, e.g. LDAP.</p></htmltext>
<tokenext>I think it will go completely the other way , and that in 50 years people will never have heard of phone numbers .
The identifier will be the email address , and if I want to call someone I select that address and press " call " , and a VOIP connection will be made .
If I want to IM or mail , I press other buttons.I 've had that in place for about a year here .
You just need to add an SRV record , of the form : \ _sip. \ _udp.example.comand then have your PBX link the extensions , with , e.g .
LDAP .</tokentext>
<sentencetext>I think it will go completely the other way, and that in 50 years people will never have heard of phone numbers.
The identifier will be the email address, and if I want to call someone I select that address and press "call", and a VOIP connection will be made.
If I want to IM or mail, I press other buttons.I've had that in place for about a year here.
You just need to add an SRV record, of the form:\_sip.\_udp.example.comand then have your PBX link the extensions, with, e.g.
LDAP.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30895666</id>
	<title>No Thanks</title>
	<author>Anonymous</author>
	<datestamp>1264413660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'd rather my e-mail, phone, Facebook, etc. remained separate, honestly.  When I use my e-mail address to sign up for something, I really don't want them to be able to call me, find me on Facebook, check out my personal website, and find out all sorts of details about me that I'd like to keep private.  Plus, spam might be an issue.  No thanks.</p></htmltext>
<tokenext>I 'd rather my e-mail , phone , Facebook , etc .
remained separate , honestly .
When I use my e-mail address to sign up for something , I really do n't want them to be able to call me , find me on Facebook , check out my personal website , and find out all sorts of details about me that I 'd like to keep private .
Plus , spam might be an issue .
No thanks .</tokentext>
<sentencetext>I'd rather my e-mail, phone, Facebook, etc.
remained separate, honestly.
When I use my e-mail address to sign up for something, I really don't want them to be able to call me, find me on Facebook, check out my personal website, and find out all sorts of details about me that I'd like to keep private.
Plus, spam might be an issue.
No thanks.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568</id>
	<title>Re:Spam spam spam... (private# and aliases)</title>
	<author>johnrpenner</author>
	<datestamp>1263574500000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>i've thought about this before - i think what one needs is a single PRIVATE number - that never gets given out to anyone - and you have a bunch of private ALIAS/Reference numbers which you yourself point to your private number - then you only give out the aliases - and if one of the aliases gets overloaded, you pull the plug on the alias, create a new alias, and then direct that new alias towards your private number.</p></htmltext>
<tokenext>i 've thought about this before - i think what one needs is a single PRIVATE number - that never gets given out to anyone - and you have a bunch of private ALIAS/Reference numbers which you yourself point to your private number - then you only give out the aliases - and if one of the aliases gets overloaded , you pull the plug on the alias , create a new alias , and then direct that new alias towards your private number .</tokentext>
<sentencetext>i've thought about this before - i think what one needs is a single PRIVATE number - that never gets given out to anyone - and you have a bunch of private ALIAS/Reference numbers which you yourself point to your private number - then you only give out the aliases - and if one of the aliases gets overloaded, you pull the plug on the alias, create a new alias, and then direct that new alias towards your private number.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781728</id>
	<title>The Problem with Enum</title>
	<author>Jason Pollock</author>
	<datestamp>1263583680000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>The problem with ENUM is that the data is stored in DNS.  Which means it is harvestable and intended to be cached.  I don't \_want\_ to share my email addresses, Facebook ID, work, cell and home phone numbers and IM addresses with anyone and everyone.  That's just stupid.</p><p>ENUM is a Bell-Head protocol invented before spam.  It was meant to be easily mirrored between carriers, with the standard behaviour of "caller pays".</p><p>What we really need is a protocol that will ask \_my software\_ where the call should be sent.  The software is then able to decide based on the originating details if I want to receive the call, and what endpoint/protocol it should be sent to.</p><p>That's what I want.  Invidividualised call control at the point of address resolution.</p></htmltext>
<tokenext>The problem with ENUM is that the data is stored in DNS .
Which means it is harvestable and intended to be cached .
I do n't \ _want \ _ to share my email addresses , Facebook ID , work , cell and home phone numbers and IM addresses with anyone and everyone .
That 's just stupid.ENUM is a Bell-Head protocol invented before spam .
It was meant to be easily mirrored between carriers , with the standard behaviour of " caller pays " .What we really need is a protocol that will ask \ _my software \ _ where the call should be sent .
The software is then able to decide based on the originating details if I want to receive the call , and what endpoint/protocol it should be sent to.That 's what I want .
Invidividualised call control at the point of address resolution .</tokentext>
<sentencetext>The problem with ENUM is that the data is stored in DNS.
Which means it is harvestable and intended to be cached.
I don't \_want\_ to share my email addresses, Facebook ID, work, cell and home phone numbers and IM addresses with anyone and everyone.
That's just stupid.ENUM is a Bell-Head protocol invented before spam.
It was meant to be easily mirrored between carriers, with the standard behaviour of "caller pays".What we really need is a protocol that will ask \_my software\_ where the call should be sent.
The software is then able to decide based on the originating details if I want to receive the call, and what endpoint/protocol it should be sent to.That's what I want.
Invidividualised call control at the point of address resolution.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780776</id>
	<title>Re:Already there?</title>
	<author>c-reus</author>
	<datestamp>1263579960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>ICQ was using numbers as identifiers</p></htmltext>
<tokenext>ICQ was using numbers as identifiers</tokentext>
<sentencetext>ICQ was using numbers as identifiers</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777796</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778322</id>
	<title>End Times</title>
	<author>Anonymous</author>
	<datestamp>1263567780000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>I can't believe nobody's figured out that ENUM is simply the Mark of the Beast and is going to be burned into chips that will implanted in our brainstems.</p><p>ENUM spelled backwards is MUNE and it's on the MUNE that they have the secret military bases where they're going to send those of us that won't use our ENUMs.</p><p>The only thing that can save us now is when the prophesied "Woman of the North" comes down from Alaska to use her secret mental powers to organize the Wolverines(!) so we can defeat the forces of ZOG and usher in the return of Jesus and Ronald Wilson Reagan where they will reign together for 1000 years.</p><p>Don't you guys read your bibles and World Net Daily?  megamerican, where are you when we really need you?</p></htmltext>
<tokenext>I ca n't believe nobody 's figured out that ENUM is simply the Mark of the Beast and is going to be burned into chips that will implanted in our brainstems.ENUM spelled backwards is MUNE and it 's on the MUNE that they have the secret military bases where they 're going to send those of us that wo n't use our ENUMs.The only thing that can save us now is when the prophesied " Woman of the North " comes down from Alaska to use her secret mental powers to organize the Wolverines ( !
) so we can defeat the forces of ZOG and usher in the return of Jesus and Ronald Wilson Reagan where they will reign together for 1000 years.Do n't you guys read your bibles and World Net Daily ?
megamerican , where are you when we really need you ?</tokentext>
<sentencetext>I can't believe nobody's figured out that ENUM is simply the Mark of the Beast and is going to be burned into chips that will implanted in our brainstems.ENUM spelled backwards is MUNE and it's on the MUNE that they have the secret military bases where they're going to send those of us that won't use our ENUMs.The only thing that can save us now is when the prophesied "Woman of the North" comes down from Alaska to use her secret mental powers to organize the Wolverines(!
) so we can defeat the forces of ZOG and usher in the return of Jesus and Ronald Wilson Reagan where they will reign together for 1000 years.Don't you guys read your bibles and World Net Daily?
megamerican, where are you when we really need you?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777796</id>
	<title>Already there?</title>
	<author>Anonymous</author>
	<datestamp>1263564600000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Isn't Google Voice already doing this? It seems to be for me.</p></htmltext>
<tokenext>Is n't Google Voice already doing this ?
It seems to be for me .</tokentext>
<sentencetext>Isn't Google Voice already doing this?
It seems to be for me.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779030</id>
	<title>$0.02 from an XML geek</title>
	<author>psbrogna</author>
	<datestamp>1263571620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Why not switch to XPath for personal GUIDs? For example<nobr> <wbr></nobr>///[/address]/, etc...and when it's time, prefixing<nobr> <wbr></nobr>///... is easy enough.
<br>
As far as the Spam issue many have brought up, I don't think security through obscurity is ever going to be adequate protection so worrying about the public registry of IDs seems like a waste of time- the evil marketers will only either derive your ID via brute force or buy the ID from somebody else. Using finer grained sender authentication at the user level (combined with cryptographic certificates for sender identity assurance) would seem to me to be the appropriate solution.</htmltext>
<tokenext>Why not switch to XPath for personal GUIDs ?
For example /// [ /address ] / , etc...and when it 's time , prefixing ///... is easy enough .
As far as the Spam issue many have brought up , I do n't think security through obscurity is ever going to be adequate protection so worrying about the public registry of IDs seems like a waste of time- the evil marketers will only either derive your ID via brute force or buy the ID from somebody else .
Using finer grained sender authentication at the user level ( combined with cryptographic certificates for sender identity assurance ) would seem to me to be the appropriate solution .</tokentext>
<sentencetext>Why not switch to XPath for personal GUIDs?
For example ///[/address]/, etc...and when it's time, prefixing ///... is easy enough.
As far as the Spam issue many have brought up, I don't think security through obscurity is ever going to be adequate protection so worrying about the public registry of IDs seems like a waste of time- the evil marketers will only either derive your ID via brute force or buy the ID from somebody else.
Using finer grained sender authentication at the user level (combined with cryptographic certificates for sender identity assurance) would seem to me to be the appropriate solution.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779142</id>
	<title>Here's my number</title>
	<author>arndawg</author>
	<datestamp>1263572280000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>0118 999 881 999 119 725........3</htmltext>
<tokenext>0118 999 881 999 119 725........3</tokentext>
<sentencetext>0118 999 881 999 119 725........3</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30783660</id>
	<title>They picked the wrong identifier.</title>
	<author>nilbog</author>
	<datestamp>1263549060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is a bad idea simply because the choose the wrong identifier.  Who wants to remember a number?  Email would be a much better identifier because people can choose their own and make it something easy to remember.</p></htmltext>
<tokenext>This is a bad idea simply because the choose the wrong identifier .
Who wants to remember a number ?
Email would be a much better identifier because people can choose their own and make it something easy to remember .</tokentext>
<sentencetext>This is a bad idea simply because the choose the wrong identifier.
Who wants to remember a number?
Email would be a much better identifier because people can choose their own and make it something easy to remember.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777936</id>
	<title>Re:Please no!!!</title>
	<author>happy\_place</author>
	<datestamp>1263565440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If all our numbers were condensed into one number, then we'd have one MORE number to memorize... cuz you know someone would find some reason to have all the others, and then we'd all need them.<nobr> <wbr></nobr>:)</htmltext>
<tokenext>If all our numbers were condensed into one number , then we 'd have one MORE number to memorize... cuz you know someone would find some reason to have all the others , and then we 'd all need them .
: )</tokentext>
<sentencetext>If all our numbers were condensed into one number, then we'd have one MORE number to memorize... cuz you know someone would find some reason to have all the others, and then we'd all need them.
:)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777774</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778870</id>
	<title>Re:Some questions</title>
	<author>MortenMW</author>
	<datestamp>1263570720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Barcodes in the neck is the best choice. I want 47.</htmltext>
<tokenext>Barcodes in the neck is the best choice .
I want 47 .</tokentext>
<sentencetext>Barcodes in the neck is the best choice.
I want 47.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777802</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782198</id>
	<title>haha.. the I.T Crowd</title>
	<author>KingPin27</author>
	<datestamp>1263585660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Newsreader: From today, dialling 999 won't get you the emergency services. And that's not the only thing that's changing. Nicer ambulances, faster response times and better-looking drivers mean they're not just "the" emergency services - they're "your" emergency services. So, remember the new number: <br>
[singing number] <br>
Newsreader: 0118 999 881 999 119 725... 3</htmltext>
<tokenext>Newsreader : From today , dialling 999 wo n't get you the emergency services .
And that 's not the only thing that 's changing .
Nicer ambulances , faster response times and better-looking drivers mean they 're not just " the " emergency services - they 're " your " emergency services .
So , remember the new number : [ singing number ] Newsreader : 0118 999 881 999 119 725... 3</tokentext>
<sentencetext>Newsreader: From today, dialling 999 won't get you the emergency services.
And that's not the only thing that's changing.
Nicer ambulances, faster response times and better-looking drivers mean they're not just "the" emergency services - they're "your" emergency services.
So, remember the new number: 
[singing number] 
Newsreader: 0118 999 881 999 119 725... 3</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880</id>
	<title>Single person != single identity</title>
	<author>KlaymenDK</author>
	<datestamp>1263565140000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>I do not want a single number, because I do not have a single identity.</p><p>I do not want my work to call me on my personal phone, so they don't have that number. But my job naturally requires some amount of phone work, so they all have *that* number. Makes sense, right?</p></htmltext>
<tokenext>I do not want a single number , because I do not have a single identity.I do not want my work to call me on my personal phone , so they do n't have that number .
But my job naturally requires some amount of phone work , so they all have * that * number .
Makes sense , right ?</tokentext>
<sentencetext>I do not want a single number, because I do not have a single identity.I do not want my work to call me on my personal phone, so they don't have that number.
But my job naturally requires some amount of phone work, so they all have *that* number.
Makes sense, right?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779514</id>
	<title>I get off watching you getting off watching me</title>
	<author>AverageJoe8686</author>
	<datestamp>1263574320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This one number thing idea is a stalker's wet dream. Hello nurse.</htmltext>
<tokenext>This one number thing idea is a stalker 's wet dream .
Hello nurse .</tokentext>
<sentencetext>This one number thing idea is a stalker's wet dream.
Hello nurse.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780220</id>
	<title>Re:Why would you want to keep the telephone number</title>
	<author>Anonymous</author>
	<datestamp>1263577860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><i>The email address is easy to remember</i> <br> <br>
My email address 09\_f9\_11\_02\_9d\_74\_e3\_5b\_d8\_41\_56\_c5\_63\_56\_88\_c0@aol.com, because it was easy to remember at the time.</htmltext>
<tokenext>The email address is easy to remember My email address 09 \ _f9 \ _11 \ _02 \ _9d \ _74 \ _e3 \ _5b \ _d8 \ _41 \ _56 \ _c5 \ _63 \ _56 \ _88 \ _c0 @ aol.com , because it was easy to remember at the time .</tokentext>
<sentencetext>The email address is easy to remember  
My email address 09\_f9\_11\_02\_9d\_74\_e3\_5b\_d8\_41\_56\_c5\_63\_56\_88\_c0@aol.com, because it was easy to remember at the time.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781222</id>
	<title>Re:Single person != single identity</title>
	<author>Anonymous</author>
	<datestamp>1263581760000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>What are you wearing?</p></htmltext>
<tokenext>What are you wearing ?</tokentext>
<sentencetext>What are you wearing?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778374</id>
	<title>Re:I am not a number! I am a free man!</title>
	<author>Anonymous</author>
	<datestamp>1263568200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Or paranoid number of the beast reference?</p></htmltext>
<tokenext>Or paranoid number of the beast reference ?</tokentext>
<sentencetext>Or paranoid number of the beast reference?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777956</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778772</id>
	<title>Bit of PC in the article</title>
	<author>RobertLTux</author>
	<datestamp>1263570060000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>"Using numbers made it easier to train people to operate the exchanges. (Women were chosen because their voices worked better in exchanges.)"</p><p>No Women were used because the messenger boys they replaced were proto-hackers and kept doing nasty tricks to the customers.</p></htmltext>
<tokenext>" Using numbers made it easier to train people to operate the exchanges .
( Women were chosen because their voices worked better in exchanges .
) " No Women were used because the messenger boys they replaced were proto-hackers and kept doing nasty tricks to the customers .</tokentext>
<sentencetext>"Using numbers made it easier to train people to operate the exchanges.
(Women were chosen because their voices worked better in exchanges.
)"No Women were used because the messenger boys they replaced were proto-hackers and kept doing nasty tricks to the customers.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778032</id>
	<title>Numbers? That's what URLs are for!</title>
	<author>Anonymous</author>
	<datestamp>1263566040000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>We should rather use DNS for phone numbers, and then allow something like:<br>phone:cowboyneal@slashdot.org<br>Similar to &ldquo;mailto:&rdquo;.<br>Or one of<br>^(phone|voip):(//)?(cowboyneal@slashdot\.org|slashdot\.org/~cowboyneal/?)$</p><p>By the way: Why are URLs (URIs) so inconsistent?<br>I guess the voip and @ version is the cleanest one. But I&rsquo;m not sure about the point of the &ldquo;//&rdquo;.</p></htmltext>
<tokenext>We should rather use DNS for phone numbers , and then allow something like : phone : cowboyneal @ slashdot.orgSimilar to    mailto :    .Or one of ^ ( phone | voip ) : ( // ) ? ( cowboyneal @ slashdot \ .org | slashdot \ .org/ ~ cowboyneal/ ?
) $ By the way : Why are URLs ( URIs ) so inconsistent ? I guess the voip and @ version is the cleanest one .
But I    m not sure about the point of the    //    .</tokentext>
<sentencetext>We should rather use DNS for phone numbers, and then allow something like:phone:cowboyneal@slashdot.orgSimilar to “mailto:”.Or one of^(phone|voip):(//)?(cowboyneal@slashdot\.org|slashdot\.org/~cowboyneal/?
)$By the way: Why are URLs (URIs) so inconsistent?I guess the voip and @ version is the cleanest one.
But I’m not sure about the point of the “//”.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778078</id>
	<title>A George divided against itself cannot stand!</title>
	<author>Anonymous</author>
	<datestamp>1263566340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Independent George</p><p><a href="http://www.youtube.com/watch?v=SxuYdzs4SS8" title="youtube.com" rel="nofollow">http://www.youtube.com/watch?v=SxuYdzs4SS8</a> [youtube.com]</p></htmltext>
<tokenext>Independent Georgehttp : //www.youtube.com/watch ? v = SxuYdzs4SS8 [ youtube.com ]</tokentext>
<sentencetext>Independent Georgehttp://www.youtube.com/watch?v=SxuYdzs4SS8 [youtube.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782232</id>
	<title>Re:X.400 all over again</title>
	<author>Rob the Bold</author>
	<datestamp>1263585840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>This is making many of the mistakes X.400 did, albeit on a smaller scale.</p><p>People want tokens that are easy to remember. Email addresses like "myname@example.com" are much more memorable than "C=US/OU=Example/FN=My/LN=Name" or "+1 234 456 6789". If someone's using this service, they're using an internet-capable device, so they can enter an alphanumeric address and don't need to remain compatible with Strowger's switch.</p></div><p>I've got it: just use a sequences of letters.  You could also monetize this, if you were in charge.  For top price you get your name or business, a little less and and you get something pronounceable, and for the basic charge, just a random string.  So simple, I wonder why no one thought of it before . . .</p></div>
	</htmltext>
<tokenext>This is making many of the mistakes X.400 did , albeit on a smaller scale.People want tokens that are easy to remember .
Email addresses like " myname @ example.com " are much more memorable than " C = US/OU = Example/FN = My/LN = Name " or " + 1 234 456 6789 " .
If someone 's using this service , they 're using an internet-capable device , so they can enter an alphanumeric address and do n't need to remain compatible with Strowger 's switch.I 've got it : just use a sequences of letters .
You could also monetize this , if you were in charge .
For top price you get your name or business , a little less and and you get something pronounceable , and for the basic charge , just a random string .
So simple , I wonder why no one thought of it before .
. .</tokentext>
<sentencetext>This is making many of the mistakes X.400 did, albeit on a smaller scale.People want tokens that are easy to remember.
Email addresses like "myname@example.com" are much more memorable than "C=US/OU=Example/FN=My/LN=Name" or "+1 234 456 6789".
If someone's using this service, they're using an internet-capable device, so they can enter an alphanumeric address and don't need to remain compatible with Strowger's switch.I've got it: just use a sequences of letters.
You could also monetize this, if you were in charge.
For top price you get your name or business, a little less and and you get something pronounceable, and for the basic charge, just a random string.
So simple, I wonder why no one thought of it before .
. .
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777832</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781532</id>
	<title>Re:Spam spam spam... (private# and aliases)</title>
	<author>raddan</author>
	<datestamp>1263582840000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>NUMBERS, wow, great idea!  After that, we'll need some kind of DIRECTORY to figure out what the numbers map to.
<br> <br>
Ironically, current telephone architecture is better than current Internet technology (any telephone number, anywhere, can be portable; IPs-- NOT!), and they want to "marry telephone numbers to the Internet"?  Why not marry the Internet to telephone numbers instead?
<br> <br>
People, numbers are ADDRESSES.  They're supposed to imply location, otherwise, why not use a more intuitive identifier, like [your name]?  This is a terrible idea.</htmltext>
<tokenext>NUMBERS , wow , great idea !
After that , we 'll need some kind of DIRECTORY to figure out what the numbers map to .
Ironically , current telephone architecture is better than current Internet technology ( any telephone number , anywhere , can be portable ; IPs-- NOT !
) , and they want to " marry telephone numbers to the Internet " ?
Why not marry the Internet to telephone numbers instead ?
People , numbers are ADDRESSES .
They 're supposed to imply location , otherwise , why not use a more intuitive identifier , like [ your name ] ?
This is a terrible idea .</tokentext>
<sentencetext>NUMBERS, wow, great idea!
After that, we'll need some kind of DIRECTORY to figure out what the numbers map to.
Ironically, current telephone architecture is better than current Internet technology (any telephone number, anywhere, can be portable; IPs-- NOT!
), and they want to "marry telephone numbers to the Internet"?
Why not marry the Internet to telephone numbers instead?
People, numbers are ADDRESSES.
They're supposed to imply location, otherwise, why not use a more intuitive identifier, like [your name]?
This is a terrible idea.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782278</id>
	<title>Re:It's not the same</title>
	<author>Anonymous</author>
	<datestamp>1263586020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><blockquote><div><p>Really? Seems to me that it factors into 5, 887, and -1</p></div></blockquote><p>Uh, what?  My calculator says 8675309 / 887 = 9780.5062006764.</p><p>887 is not a factor.</p></div>
	</htmltext>
<tokenext>Really ?
Seems to me that it factors into 5 , 887 , and -1Uh , what ?
My calculator says 8675309 / 887 = 9780.5062006764.887 is not a factor .</tokentext>
<sentencetext>Really?
Seems to me that it factors into 5, 887, and -1Uh, what?
My calculator says 8675309 / 887 = 9780.5062006764.887 is not a factor.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780242</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781578</id>
	<title>Re:Spam spam spam... (private# and aliases)</title>
	<author>SwordsmanLuke</author>
	<datestamp>1263583080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Like Google Voice</htmltext>
<tokenext>Like Google Voice</tokentext>
<sentencetext>Like Google Voice</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780242</id>
	<title>Re:It's not the same</title>
	<author>LordKronos</author>
	<datestamp>1263577920000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>867-5309 is also a prime number</p></div></blockquote><p>Really? Seems to me that it factors into 5, 887, and -1</p></div>
	</htmltext>
<tokenext>867-5309 is also a prime numberReally ?
Seems to me that it factors into 5 , 887 , and -1</tokentext>
<sentencetext>867-5309 is also a prime numberReally?
Seems to me that it factors into 5, 887, and -1
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778106</id>
	<title>Re:It's not the same</title>
	<author>plover</author>
	<datestamp>1263566580000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>Dzubin P-1 CUR ALLOC 20193 . .<nobr> <wbr></nobr>.5804M</p></div><p> <tt><br>rodtsasdt llllllreport*<br></tt></p></div>
	</htmltext>
<tokenext>Dzubin P-1 CUR ALLOC 20193 .
. .5804M rodtsasdt llllllreport *</tokentext>
<sentencetext>Dzubin P-1 CUR ALLOC 20193 .
. .5804M rodtsasdt llllllreport*
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30786972</id>
	<title>Re:Spam spam spam... (private# and aliases)</title>
	<author>SlothDead</author>
	<datestamp>1263568080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That actually exists for emails and is called "Spam Gourmet", where you make up a username that is tied to a real e-mail and which allows you to hand out limited addresses, like slashdotcomment.3.johnrpenner@spamgourmet.com, which will only forward 3 mails to your real address.</p></htmltext>
<tokenext>That actually exists for emails and is called " Spam Gourmet " , where you make up a username that is tied to a real e-mail and which allows you to hand out limited addresses , like slashdotcomment.3.johnrpenner @ spamgourmet.com , which will only forward 3 mails to your real address .</tokentext>
<sentencetext>That actually exists for emails and is called "Spam Gourmet", where you make up a username that is tied to a real e-mail and which allows you to hand out limited addresses, like slashdotcomment.3.johnrpenner@spamgourmet.com, which will only forward 3 mails to your real address.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778696</id>
	<title>Re:Why would you want to keep the telephone number</title>
	<author>T Murphy</author>
	<datestamp>1263569760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I know the blackberry- along with many/most other phones I'm sure- has voice recognition to allow you to assign a name to various phone numbers as you wish. Despite phone numbers having to be unique, this system lets everyone use "home" as the name as their home phone number, and everyone with a friend named Dave can call a different Dave. Not to mention you can use whatever name you would find easy to remember. I would rather use a similar, user-defined naming system on top of a unique number standardized system. Among other things I don't think we need another batch of domain squatters and squabbling over what company gets what common names, so I favor making this numbering system and leaving it at that.</htmltext>
<tokenext>I know the blackberry- along with many/most other phones I 'm sure- has voice recognition to allow you to assign a name to various phone numbers as you wish .
Despite phone numbers having to be unique , this system lets everyone use " home " as the name as their home phone number , and everyone with a friend named Dave can call a different Dave .
Not to mention you can use whatever name you would find easy to remember .
I would rather use a similar , user-defined naming system on top of a unique number standardized system .
Among other things I do n't think we need another batch of domain squatters and squabbling over what company gets what common names , so I favor making this numbering system and leaving it at that .</tokentext>
<sentencetext>I know the blackberry- along with many/most other phones I'm sure- has voice recognition to allow you to assign a name to various phone numbers as you wish.
Despite phone numbers having to be unique, this system lets everyone use "home" as the name as their home phone number, and everyone with a friend named Dave can call a different Dave.
Not to mention you can use whatever name you would find easy to remember.
I would rather use a similar, user-defined naming system on top of a unique number standardized system.
Among other things I don't think we need another batch of domain squatters and squabbling over what company gets what common names, so I favor making this numbering system and leaving it at that.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780022</id>
	<title>Re:Single person != single identity</title>
	<author>bar-agent</author>
	<datestamp>1263576900000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p><i> am a 15 year old girl who's parents have gone away for the weekend.</i></p><p>OHAI! How do you feel about robes...and wizard hats?</p></htmltext>
<tokenext>am a 15 year old girl who 's parents have gone away for the weekend.OHAI !
How do you feel about robes...and wizard hats ?</tokentext>
<sentencetext> am a 15 year old girl who's parents have gone away for the weekend.OHAI!
How do you feel about robes...and wizard hats?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778478</id>
	<title>well yeah</title>
	<author>circletimessquare</author>
	<datestamp>1263568740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>if jenny is worth writing a song about her phone number, you just know she is a prime cut of female finery</p><p>as for the issue of prime twins, oh man, are her twins prime!</p></htmltext>
<tokenext>if jenny is worth writing a song about her phone number , you just know she is a prime cut of female fineryas for the issue of prime twins , oh man , are her twins prime !</tokentext>
<sentencetext>if jenny is worth writing a song about her phone number, you just know she is a prime cut of female fineryas for the issue of prime twins, oh man, are her twins prime!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777836</id>
	<title>Cute hack...</title>
	<author>fuzzyfuzzyfungus</author>
	<datestamp>1263564900000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>But I'm not quite sure why I would want to tie all my shiny new contact mechanisms to a 19th century relic controlled by the telcoms, entities which are sclerotic at best and downright evil at worst.<br> <br>

ENUM seems like the sort of thing that would happen if you got a bunch of fairly sharp techies together and told them that it was an axiomatic, foundational, truth that telephone numbers must remain relevant and central to communication. Within those constraints, they seem to have come up with a good solution. Those constraints, though, seem irrelevant. The internet, and its design philosophies, is simply better.</htmltext>
<tokenext>But I 'm not quite sure why I would want to tie all my shiny new contact mechanisms to a 19th century relic controlled by the telcoms , entities which are sclerotic at best and downright evil at worst .
ENUM seems like the sort of thing that would happen if you got a bunch of fairly sharp techies together and told them that it was an axiomatic , foundational , truth that telephone numbers must remain relevant and central to communication .
Within those constraints , they seem to have come up with a good solution .
Those constraints , though , seem irrelevant .
The internet , and its design philosophies , is simply better .</tokentext>
<sentencetext>But I'm not quite sure why I would want to tie all my shiny new contact mechanisms to a 19th century relic controlled by the telcoms, entities which are sclerotic at best and downright evil at worst.
ENUM seems like the sort of thing that would happen if you got a bunch of fairly sharp techies together and told them that it was an axiomatic, foundational, truth that telephone numbers must remain relevant and central to communication.
Within those constraints, they seem to have come up with a good solution.
Those constraints, though, seem irrelevant.
The internet, and its design philosophies, is simply better.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781998</id>
	<title>Re:I don't want a "number"</title>
	<author>rantingkitten</author>
	<datestamp>1263584760000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>Yeah!  I am not a number!  I am a <b>free man!</b></htmltext>
<tokenext>Yeah !
I am not a number !
I am a free man !</tokentext>
<sentencetext>Yeah!
I am not a number!
I am a free man!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777800</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778756</id>
	<title>Re:Single person != single identity</title>
	<author>Anonymous</author>
	<datestamp>1263570000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Because Home and Work aren't enough.  Do you want EVERYONE you know in your personal life to have access to ALL your communication methods?  What about the annoying guy you get emails from daily?  At least with email, you can easily filter, and there is a lesser expectation on his part of your reply being timely.  If your ENUM id gave that person access to your phone, it would be ringing all day long.  What about the throwaway emails you use to register software, since some packages require a real address?  Do you really want all the resulting spam to flood your actual personal email address? I keep a separate email for family, one for school friends, one for gaming friends, one for coworkers, one for work, one for my wife, and something like 5 more for forums, software registration, etc.  I don't, in any way, want all that tied together.</p><p>And of those, ONE is tied to my actual home street address.</p></htmltext>
<tokenext>Because Home and Work are n't enough .
Do you want EVERYONE you know in your personal life to have access to ALL your communication methods ?
What about the annoying guy you get emails from daily ?
At least with email , you can easily filter , and there is a lesser expectation on his part of your reply being timely .
If your ENUM id gave that person access to your phone , it would be ringing all day long .
What about the throwaway emails you use to register software , since some packages require a real address ?
Do you really want all the resulting spam to flood your actual personal email address ?
I keep a separate email for family , one for school friends , one for gaming friends , one for coworkers , one for work , one for my wife , and something like 5 more for forums , software registration , etc .
I do n't , in any way , want all that tied together.And of those , ONE is tied to my actual home street address .</tokentext>
<sentencetext>Because Home and Work aren't enough.
Do you want EVERYONE you know in your personal life to have access to ALL your communication methods?
What about the annoying guy you get emails from daily?
At least with email, you can easily filter, and there is a lesser expectation on his part of your reply being timely.
If your ENUM id gave that person access to your phone, it would be ringing all day long.
What about the throwaway emails you use to register software, since some packages require a real address?
Do you really want all the resulting spam to flood your actual personal email address?
I keep a separate email for family, one for school friends, one for gaming friends, one for coworkers, one for work, one for my wife, and something like 5 more for forums, software registration, etc.
I don't, in any way, want all that tied together.And of those, ONE is tied to my actual home street address.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778066</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30785818</id>
	<title>Re:Single person != single identity</title>
	<author>Anonymous</author>
	<datestamp>1263559740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Curiously at home I am a 15 year old girl and in Internet chats I'm a cop.

Arresting development eh!</htmltext>
<tokenext>Curiously at home I am a 15 year old girl and in Internet chats I 'm a cop .
Arresting development eh !</tokentext>
<sentencetext>Curiously at home I am a 15 year old girl and in Internet chats I'm a cop.
Arresting development eh!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826</id>
	<title>Why would you want to keep the telephone number?</title>
	<author>Omegium</author>
	<datestamp>1263564840000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext>(I posted this earlier on Ars Technica)<p>

Why would you want to keep the telephone number?</p><p>


The telephone number is a good example of a situation where the technical factor prevailed over the human factor. Numbers are abstract and difficult to remember for most people. And since its invention we have needed to use lists to associate these numbers to things we actually can remember, such as names.</p><p>


I think it will go completely the other way, and that in 50 years people will never have heard of phone numbers. The identifier will be the email address, and if I want to call someone I select that address and press "call", and a VOIP connection will be made. If I want to IM or mail, I press other buttons.</p><p>


The email address is easy to remember, it has build-in identification of the purpose you want to use it for (private, business,<nobr> <wbr></nobr>...), can already be used for several types of communication (mail, jabber) and is completely transparent to location</p></htmltext>
<tokenext>( I posted this earlier on Ars Technica ) Why would you want to keep the telephone number ?
The telephone number is a good example of a situation where the technical factor prevailed over the human factor .
Numbers are abstract and difficult to remember for most people .
And since its invention we have needed to use lists to associate these numbers to things we actually can remember , such as names .
I think it will go completely the other way , and that in 50 years people will never have heard of phone numbers .
The identifier will be the email address , and if I want to call someone I select that address and press " call " , and a VOIP connection will be made .
If I want to IM or mail , I press other buttons .
The email address is easy to remember , it has build-in identification of the purpose you want to use it for ( private , business , ... ) , can already be used for several types of communication ( mail , jabber ) and is completely transparent to location</tokentext>
<sentencetext>(I posted this earlier on Ars Technica)

Why would you want to keep the telephone number?
The telephone number is a good example of a situation where the technical factor prevailed over the human factor.
Numbers are abstract and difficult to remember for most people.
And since its invention we have needed to use lists to associate these numbers to things we actually can remember, such as names.
I think it will go completely the other way, and that in 50 years people will never have heard of phone numbers.
The identifier will be the email address, and if I want to call someone I select that address and press "call", and a VOIP connection will be made.
If I want to IM or mail, I press other buttons.
The email address is easy to remember, it has build-in identification of the purpose you want to use it for (private, business, ...), can already be used for several types of communication (mail, jabber) and is completely transparent to location</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779742</id>
	<title>Re:Single person != single identity</title>
	<author>Anonymous</author>
	<datestamp>1263575520000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>What's your email address for the latter identity?<nobr> <wbr></nobr>;)</p></htmltext>
<tokenext>What 's your email address for the latter identity ?
; )</tokentext>
<sentencetext>What's your email address for the latter identity?
;)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779290</id>
	<title>Re:Why would you want to keep the telephone number</title>
	<author>residieu</author>
	<datestamp>1263573180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I assumed "Dragging Telephone Numbers into the Internet Age" meant something like replacing numbers on phones with some other form of id. Apparently, I was wrong.</htmltext>
<tokenext>I assumed " Dragging Telephone Numbers into the Internet Age " meant something like replacing numbers on phones with some other form of id .
Apparently , I was wrong .</tokentext>
<sentencetext>I assumed "Dragging Telephone Numbers into the Internet Age" meant something like replacing numbers on phones with some other form of id.
Apparently, I was wrong.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779482</id>
	<title>Re:Why would you want to keep the telephone number</title>
	<author>VShael</author>
	<datestamp>1263574200000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>in 50 years people will never have heard of phone numbers</i></p><p>Considering that today, we still know of the phonograph, telegraph poles, and telegrams.... human nature and socities memory doesn't change as quickly as you think, even when it comes to outmoded technology.</p></htmltext>
<tokenext>in 50 years people will never have heard of phone numbersConsidering that today , we still know of the phonograph , telegraph poles , and telegrams.... human nature and socities memory does n't change as quickly as you think , even when it comes to outmoded technology .</tokentext>
<sentencetext>in 50 years people will never have heard of phone numbersConsidering that today, we still know of the phonograph, telegraph poles, and telegrams.... human nature and socities memory doesn't change as quickly as you think, even when it comes to outmoded technology.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781440</id>
	<title>Re:Been done: .tel domain</title>
	<author>Anonymous</author>
	<datestamp>1263582480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>While at first glance it seems like a good idea to put all contact info directly into the DNS system, it will result in a massive spam problem at some pont.<nobr> <wbr></nobr>.tel was thrown together too quickly. As archaic as switched phone systems seems, there is something to be said for it. If the internet goes down in the future (and it will), all global communication will be impossible under a DNS based system, where as with 2 separate phone infrastructures you at least have some communication in the event of a massive world wide internet outage.</p></htmltext>
<tokenext>While at first glance it seems like a good idea to put all contact info directly into the DNS system , it will result in a massive spam problem at some pont .
.tel was thrown together too quickly .
As archaic as switched phone systems seems , there is something to be said for it .
If the internet goes down in the future ( and it will ) , all global communication will be impossible under a DNS based system , where as with 2 separate phone infrastructures you at least have some communication in the event of a massive world wide internet outage .</tokentext>
<sentencetext>While at first glance it seems like a good idea to put all contact info directly into the DNS system, it will result in a massive spam problem at some pont.
.tel was thrown together too quickly.
As archaic as switched phone systems seems, there is something to be said for it.
If the internet goes down in the future (and it will), all global communication will be impossible under a DNS based system, where as with 2 separate phone infrastructures you at least have some communication in the event of a massive world wide internet outage.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777846</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30791528</id>
	<title>Antitrust</title>
	<author>Anonymous</author>
	<datestamp>1263667320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Antitrust, anyone?</p></htmltext>
<tokenext>Antitrust , anyone ?</tokentext>
<sentencetext>Antitrust, anyone?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777956</id>
	<title>I am not a number! I am a free man!</title>
	<author>damburger</author>
	<datestamp>1263565500000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>How the hell did this thread go so long without a Prisoner reference?</htmltext>
<tokenext>How the hell did this thread go so long without a Prisoner reference ?</tokentext>
<sentencetext>How the hell did this thread go so long without a Prisoner reference?</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_61</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777932
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780006
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30786420
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777784
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780492
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30783308
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780612
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779290
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778700
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778370
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780710
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30820240
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778032
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781920
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_60</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781532
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778696
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777762
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780242
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782278
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30800482
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781222
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778032
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780116
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781878
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777956
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778374
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777796
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780776
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777762
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778106
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30786972
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777762
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779306
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778044
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778712
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777832
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780402
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_56</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778560
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779302
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781516
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777956
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778562
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777802
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778870
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779742
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778044
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781126
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778078
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778032
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782786
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_55</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777846
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781440
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779920
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779482
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778226
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778066
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778756
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777956
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779328
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777762
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778478
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781998
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781230
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777924
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779388
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778994
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777956
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778832
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777762
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777856
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30788606
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779892
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780220
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777982
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779590
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780022
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777982
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780028
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_59</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778044
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779146
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_58</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30788496
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778308
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777800
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778018
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777832
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782232
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30785818
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778454
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777924
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779570
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777774
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777936
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781578
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_57</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777762
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779616
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_10_01_15_0826253_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778980
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778032
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782786
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781920
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780116
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778322
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777850
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777982
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779590
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780028
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777784
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780492
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30783308
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777796
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780776
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777820
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777924
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779388
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779570
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777832
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782232
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780402
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777930
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777990
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781728
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777762
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777856
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777862
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778106
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780242
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30782278
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30800482
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779306
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778478
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779616
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777898
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777774
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777936
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778560
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779302
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778044
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781126
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778712
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779146
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777932
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780006
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778046
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777818
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777846
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781440
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777802
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778870
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779308
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779030
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779142
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777836
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777800
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778226
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781998
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778018
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777826
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779290
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779482
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781878
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780220
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778994
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778696
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30820240
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778700
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778980
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30786420
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777880
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778454
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778792
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779742
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780022
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30785818
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781222
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30788496
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778066
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778756
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779920
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780612
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778078
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778370
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778308
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779892
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779088
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777956
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779328
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778562
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778832
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30778374
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation10_01_15_0826253.27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30777768
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30780710
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30779568
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781532
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781578
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781230
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30781516
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30786972
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment10_01_15_0826253.30788606
</commentlist>
</conversation>
