<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_07_15_2252249</id>
	<title>Integrating Wikipedia With a Local Intranet Wiki</title>
	<author>samzenpus</author>
	<datestamp>1247683200000</datestamp>
	<htmltext>An anonymous reader writes <i>"I work for a large company taking a preliminary look at developing an honest-to-goodness wiki.  We have tried to launch a company-wide wiki before, but with little success.  The technical domains of each part of the company are different, thus each article needs a good deal of background to be useful.  Of course, due the proprietary nature of our work we cannot share our articles outside of the intranet. What we would like to do is leverage existing wikis by augmenting our internal wiki with an external wiki.  When a user accesses Wikipedia from inside our intranet, they receive the wikipedia content, plus the local domain specific information.  For example, links to company-specific wiki pages would be available in Wikipedia pages. Has anyone else tried to do something like this?  I know it sounds like a logistical nightmare; are there any thoughts on how to make this successful?"</i></htmltext>
<tokenext>An anonymous reader writes " I work for a large company taking a preliminary look at developing an honest-to-goodness wiki .
We have tried to launch a company-wide wiki before , but with little success .
The technical domains of each part of the company are different , thus each article needs a good deal of background to be useful .
Of course , due the proprietary nature of our work we can not share our articles outside of the intranet .
What we would like to do is leverage existing wikis by augmenting our internal wiki with an external wiki .
When a user accesses Wikipedia from inside our intranet , they receive the wikipedia content , plus the local domain specific information .
For example , links to company-specific wiki pages would be available in Wikipedia pages .
Has anyone else tried to do something like this ?
I know it sounds like a logistical nightmare ; are there any thoughts on how to make this successful ?
"</tokentext>
<sentencetext>An anonymous reader writes "I work for a large company taking a preliminary look at developing an honest-to-goodness wiki.
We have tried to launch a company-wide wiki before, but with little success.
The technical domains of each part of the company are different, thus each article needs a good deal of background to be useful.
Of course, due the proprietary nature of our work we cannot share our articles outside of the intranet.
What we would like to do is leverage existing wikis by augmenting our internal wiki with an external wiki.
When a user accesses Wikipedia from inside our intranet, they receive the wikipedia content, plus the local domain specific information.
For example, links to company-specific wiki pages would be available in Wikipedia pages.
Has anyone else tried to do something like this?
I know it sounds like a logistical nightmare; are there any thoughts on how to make this successful?
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28723275</id>
	<title>Semantic MediaWiki and SMW+</title>
	<author>javester</author>
	<datestamp>1247741220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You may want to check the Semantic MediaWiki (semantic-mediawiki.org)  or SMW+ (wiki.ontoprise.de).</p><p>Both are built on top of MediaWiki (which powers Wikipedia) so you can tap the very rich pools of extensions (numbering in the hundreds).</p><p>SMW+ is actually built on top of SMW, and it focuses on increasing usability and it preinstall pre-configured extensions out of the box to make it easier to deploy.</p><p>With SMW/SMW+, you can put in semantic annotations for an article describing just about anything you want to assert about the article.  One assertion you can make is a Wikipedia link.  It even has the smarts to know that the assertion/property is a URL and it will put in the necessary bits to make it clickable.</p><p>And that's just the tip of the iceberg, you can do some other amaaaazzziiing stuff with the semantic smarts of SMW/SMW+.  To get a better sense of what SMW is, you may want to check out - http://simia.net/download/SemTech2009.ppt</p><p>Full disclosure - I help out with the SMW project<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>You may want to check the Semantic MediaWiki ( semantic-mediawiki.org ) or SMW + ( wiki.ontoprise.de ) .Both are built on top of MediaWiki ( which powers Wikipedia ) so you can tap the very rich pools of extensions ( numbering in the hundreds ) .SMW + is actually built on top of SMW , and it focuses on increasing usability and it preinstall pre-configured extensions out of the box to make it easier to deploy.With SMW/SMW + , you can put in semantic annotations for an article describing just about anything you want to assert about the article .
One assertion you can make is a Wikipedia link .
It even has the smarts to know that the assertion/property is a URL and it will put in the necessary bits to make it clickable.And that 's just the tip of the iceberg , you can do some other amaaaazzziiing stuff with the semantic smarts of SMW/SMW + .
To get a better sense of what SMW is , you may want to check out - http : //simia.net/download/SemTech2009.pptFull disclosure - I help out with the SMW project : )</tokentext>
<sentencetext>You may want to check the Semantic MediaWiki (semantic-mediawiki.org)  or SMW+ (wiki.ontoprise.de).Both are built on top of MediaWiki (which powers Wikipedia) so you can tap the very rich pools of extensions (numbering in the hundreds).SMW+ is actually built on top of SMW, and it focuses on increasing usability and it preinstall pre-configured extensions out of the box to make it easier to deploy.With SMW/SMW+, you can put in semantic annotations for an article describing just about anything you want to assert about the article.
One assertion you can make is a Wikipedia link.
It even has the smarts to know that the assertion/property is a URL and it will put in the necessary bits to make it clickable.And that's just the tip of the iceberg, you can do some other amaaaazzziiing stuff with the semantic smarts of SMW/SMW+.
To get a better sense of what SMW is, you may want to check out - http://simia.net/download/SemTech2009.pptFull disclosure - I help out with the SMW project :)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713991</id>
	<title>Re:URLs</title>
	<author>CarpetShark</author>
	<datestamp>1247737920000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext><p>Hahhah, 100\% accurate, and nicely put<nobr> <wbr></nobr>:D</p></htmltext>
<tokenext>Hahhah , 100 \ % accurate , and nicely put : D</tokentext>
<sentencetext>Hahhah, 100\% accurate, and nicely put :D</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713331</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714363</id>
	<title>Why not</title>
	<author>Vahokif</author>
	<datestamp>1247742660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Why not run MediaWiki on your intranet and use InterWiki links to Wikipedia in your own articles?</htmltext>
<tokenext>Why not run MediaWiki on your intranet and use InterWiki links to Wikipedia in your own articles ?</tokentext>
<sentencetext>Why not run MediaWiki on your intranet and use InterWiki links to Wikipedia in your own articles?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713619</id>
	<title>interwiki</title>
	<author>Anonymous</author>
	<datestamp>1247776500000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>You probably want <a href="http://en.wikipedia.org/wiki/InterWiki" title="wikipedia.org">interwiki</a> [wikipedia.org].</htmltext>
<tokenext>You probably want interwiki [ wikipedia.org ] .</tokentext>
<sentencetext>You probably want interwiki [wikipedia.org].</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713491</id>
	<title>Re:bad idea</title>
	<author>ArbiterShadow</author>
	<datestamp>1247775180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>I also think this is actually a decent idea. The only problem is that it takes a bit of user configuring, and will also make changes to the page on Wikipedia as well as the "internal" version.

You could also just keep a server running that mirrors Wikipedia for the pages that you want, and uses said regexes to insert the internal links then. Transforming at compile time rather than runtime, if you will.</htmltext>
<tokenext>I also think this is actually a decent idea .
The only problem is that it takes a bit of user configuring , and will also make changes to the page on Wikipedia as well as the " internal " version .
You could also just keep a server running that mirrors Wikipedia for the pages that you want , and uses said regexes to insert the internal links then .
Transforming at compile time rather than runtime , if you will .</tokentext>
<sentencetext>I also think this is actually a decent idea.
The only problem is that it takes a bit of user configuring, and will also make changes to the page on Wikipedia as well as the "internal" version.
You could also just keep a server running that mirrors Wikipedia for the pages that you want, and uses said regexes to insert the internal links then.
Transforming at compile time rather than runtime, if you will.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713343</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713423</id>
	<title>Do it the other way around?</title>
	<author>Anonymous</author>
	<datestamp>1247774520000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Have you considered taking a recent <a href="http://en.wikipedia.org/wiki/Wikipedia:Database\_download" title="wikipedia.org" rel="nofollow">wikipedia snapshot</a> [wikipedia.org] and using that as a foundation to seed your internal wiki.</p><p>Your internal users can then add their own revisions to this as required to customise it where necessary.</p><p>Of course, you'll lose the ability to pick up new changes/revisions to the original WP pages, but it might be a simpler way to go.</p></htmltext>
<tokenext>Have you considered taking a recent wikipedia snapshot [ wikipedia.org ] and using that as a foundation to seed your internal wiki.Your internal users can then add their own revisions to this as required to customise it where necessary.Of course , you 'll lose the ability to pick up new changes/revisions to the original WP pages , but it might be a simpler way to go .</tokentext>
<sentencetext>Have you considered taking a recent wikipedia snapshot [wikipedia.org] and using that as a foundation to seed your internal wiki.Your internal users can then add their own revisions to this as required to customise it where necessary.Of course, you'll lose the ability to pick up new changes/revisions to the original WP pages, but it might be a simpler way to go.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714439</id>
	<title>Re:bad idea</title>
	<author>Jane Q. Public</author>
	<datestamp>1247743620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Scraping web pages is not so bad... I have been doing it for years. But in this case it is entirely unnecessary.
<br> <br>
I know of at least two ways this could be done, neither of which is nearly as much work as this would seem at first. First, did you know that the entirety of the content of Wikipedia is downloadable, in different formats? You can get everything, or just the current articles without the history (<b>much</b> smaller), and there are other options as well. While there is a lot of data, it is really not that difficult to take a snapshot of Wikipedia and load it into a local database. I have done it before myself. It is a really huge database... but it is doable, and I managed to make it work in MySQL on my local development machine, not even a fancy server. Though I admit it was not fast that way.
<br> <br>
Probably a better solution, however, would be to use Wikipedia's API. Get a back-end programmer to write a program that compares users' search requests against the content of your local wiki. If there is no match, forward the request to Wikipedia via the Wikipedia API. This is not a terribly complicated task. The hardest part would be determining whether a search matched something local. But that is the kind of task that has to be done internally.</htmltext>
<tokenext>Scraping web pages is not so bad... I have been doing it for years .
But in this case it is entirely unnecessary .
I know of at least two ways this could be done , neither of which is nearly as much work as this would seem at first .
First , did you know that the entirety of the content of Wikipedia is downloadable , in different formats ?
You can get everything , or just the current articles without the history ( much smaller ) , and there are other options as well .
While there is a lot of data , it is really not that difficult to take a snapshot of Wikipedia and load it into a local database .
I have done it before myself .
It is a really huge database... but it is doable , and I managed to make it work in MySQL on my local development machine , not even a fancy server .
Though I admit it was not fast that way .
Probably a better solution , however , would be to use Wikipedia 's API .
Get a back-end programmer to write a program that compares users ' search requests against the content of your local wiki .
If there is no match , forward the request to Wikipedia via the Wikipedia API .
This is not a terribly complicated task .
The hardest part would be determining whether a search matched something local .
But that is the kind of task that has to be done internally .</tokentext>
<sentencetext>Scraping web pages is not so bad... I have been doing it for years.
But in this case it is entirely unnecessary.
I know of at least two ways this could be done, neither of which is nearly as much work as this would seem at first.
First, did you know that the entirety of the content of Wikipedia is downloadable, in different formats?
You can get everything, or just the current articles without the history (much smaller), and there are other options as well.
While there is a lot of data, it is really not that difficult to take a snapshot of Wikipedia and load it into a local database.
I have done it before myself.
It is a really huge database... but it is doable, and I managed to make it work in MySQL on my local development machine, not even a fancy server.
Though I admit it was not fast that way.
Probably a better solution, however, would be to use Wikipedia's API.
Get a back-end programmer to write a program that compares users' search requests against the content of your local wiki.
If there is no match, forward the request to Wikipedia via the Wikipedia API.
This is not a terribly complicated task.
The hardest part would be determining whether a search matched something local.
But that is the kind of task that has to be done internally.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714145</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713703</id>
	<title>Hyperlinks?</title>
	<author>Malibee</author>
	<datestamp>1247777280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Maybe I'm missing something, but why not just have an external links section on your internal wiki, or a "Required Reading" section? Seems like the solution you're proposing is a little bit heavyweight for the described problem.</p></htmltext>
<tokenext>Maybe I 'm missing something , but why not just have an external links section on your internal wiki , or a " Required Reading " section ?
Seems like the solution you 're proposing is a little bit heavyweight for the described problem .</tokentext>
<sentencetext>Maybe I'm missing something, but why not just have an external links section on your internal wiki, or a "Required Reading" section?
Seems like the solution you're proposing is a little bit heavyweight for the described problem.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713563</id>
	<title>Re:Solution</title>
	<author>mcrbids</author>
	<datestamp>1247775900000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>Dumps go stale, Wikipedia is updated all the time. I'd suggest something a bit more dynamic.</p><p>I did something similar (conceptually) as a dynamic help system for our web-based application, and had content in a wiki based on the URL of the page where the help message was to apply. In my case, clicking the "help" button on a page would make a proxy call to a private wiki to get the help menu content. If none was found, an email was sent to support desk and the end-user was given a web-chat prompt to tech support (with the URL prepended so that tech support could jump in, answer the questions, and write the help menu in one fell swoop)</p><p>In your case, start with your local wiki. Presumably you have some stuff in there already. Rename the articles as necessary to match URLs from Wikipedia.</p><p>Then, build a simple proxy server that rewrites wikipedia content to include a header of your local content. Probably 100 lines (or so) of glue code, and anywhere from a few man-hours to a few man-days coding.</p><p>The rest is all training.</p></htmltext>
<tokenext>Dumps go stale , Wikipedia is updated all the time .
I 'd suggest something a bit more dynamic.I did something similar ( conceptually ) as a dynamic help system for our web-based application , and had content in a wiki based on the URL of the page where the help message was to apply .
In my case , clicking the " help " button on a page would make a proxy call to a private wiki to get the help menu content .
If none was found , an email was sent to support desk and the end-user was given a web-chat prompt to tech support ( with the URL prepended so that tech support could jump in , answer the questions , and write the help menu in one fell swoop ) In your case , start with your local wiki .
Presumably you have some stuff in there already .
Rename the articles as necessary to match URLs from Wikipedia.Then , build a simple proxy server that rewrites wikipedia content to include a header of your local content .
Probably 100 lines ( or so ) of glue code , and anywhere from a few man-hours to a few man-days coding.The rest is all training .</tokentext>
<sentencetext>Dumps go stale, Wikipedia is updated all the time.
I'd suggest something a bit more dynamic.I did something similar (conceptually) as a dynamic help system for our web-based application, and had content in a wiki based on the URL of the page where the help message was to apply.
In my case, clicking the "help" button on a page would make a proxy call to a private wiki to get the help menu content.
If none was found, an email was sent to support desk and the end-user was given a web-chat prompt to tech support (with the URL prepended so that tech support could jump in, answer the questions, and write the help menu in one fell swoop)In your case, start with your local wiki.
Presumably you have some stuff in there already.
Rename the articles as necessary to match URLs from Wikipedia.Then, build a simple proxy server that rewrites wikipedia content to include a header of your local content.
Probably 100 lines (or so) of glue code, and anywhere from a few man-hours to a few man-days coding.The rest is all training.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713399</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715755</id>
	<title>Re:URLs</title>
	<author>S77IM</author>
	<datestamp>1247754900000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Said in a crude way; but to the OP:  This guy is right.  The most brain-dead simple way to make this work is to just set up your own wiki, and pepper it liberally with links to relevant Wikipedia pages.  As someone below points out, there's even a feature in MediaWiki to make this linking easier (look up "InterWiki" in the MediaWiki help).</p><p>You <i>may</i> even be able to set up #REDIRECTS using InterWiki links so that people can still see the page names you want in your search and category listing, and then be taken straight to Wikipedia.  If you want to get fancy, you can create a Template that opens the Wikipedia page in an IFRAME or does some DHTML to embed the content, so that the surrounding trim (edit link and search box) is for your wiki.  The key here is to make sure people understand which content is your own wiki and which is Wikipedia -- whenever they edit or add a page, it goes into your wiki; treat Wikipedia as read-only.  (If someone wants to make a genuine contribution to Wikipedia, they can go do that the normal way.)</p><p>I think that's the tightest integration you can get -- easy access to Wikipedia info, plus your own wiki for company-specific stuff.  On the other hand this right here sounds like a recipe for disaster:</p><p><div class="quote"><p>When a user accesses Wikipedia from inside our intranet, they receive the wikipedia content, plus the local domain specific information. For example, links to company-specific wiki pages would be available in Wikipedia pages.</p></div><p>That's not a logistical nightmare; that's a major development effort, <i>just for a freakin' wiki</i>.  Requirements like this are why so many software projects fail.  Abandon the pie-in-the-sky vision and go with something simple to start.</p><p>Like URLs.</p></div>
	</htmltext>
<tokenext>Said in a crude way ; but to the OP : This guy is right .
The most brain-dead simple way to make this work is to just set up your own wiki , and pepper it liberally with links to relevant Wikipedia pages .
As someone below points out , there 's even a feature in MediaWiki to make this linking easier ( look up " InterWiki " in the MediaWiki help ) .You may even be able to set up # REDIRECTS using InterWiki links so that people can still see the page names you want in your search and category listing , and then be taken straight to Wikipedia .
If you want to get fancy , you can create a Template that opens the Wikipedia page in an IFRAME or does some DHTML to embed the content , so that the surrounding trim ( edit link and search box ) is for your wiki .
The key here is to make sure people understand which content is your own wiki and which is Wikipedia -- whenever they edit or add a page , it goes into your wiki ; treat Wikipedia as read-only .
( If someone wants to make a genuine contribution to Wikipedia , they can go do that the normal way .
) I think that 's the tightest integration you can get -- easy access to Wikipedia info , plus your own wiki for company-specific stuff .
On the other hand this right here sounds like a recipe for disaster : When a user accesses Wikipedia from inside our intranet , they receive the wikipedia content , plus the local domain specific information .
For example , links to company-specific wiki pages would be available in Wikipedia pages.That 's not a logistical nightmare ; that 's a major development effort , just for a freakin ' wiki .
Requirements like this are why so many software projects fail .
Abandon the pie-in-the-sky vision and go with something simple to start.Like URLs .</tokentext>
<sentencetext>Said in a crude way; but to the OP:  This guy is right.
The most brain-dead simple way to make this work is to just set up your own wiki, and pepper it liberally with links to relevant Wikipedia pages.
As someone below points out, there's even a feature in MediaWiki to make this linking easier (look up "InterWiki" in the MediaWiki help).You may even be able to set up #REDIRECTS using InterWiki links so that people can still see the page names you want in your search and category listing, and then be taken straight to Wikipedia.
If you want to get fancy, you can create a Template that opens the Wikipedia page in an IFRAME or does some DHTML to embed the content, so that the surrounding trim (edit link and search box) is for your wiki.
The key here is to make sure people understand which content is your own wiki and which is Wikipedia -- whenever they edit or add a page, it goes into your wiki; treat Wikipedia as read-only.
(If someone wants to make a genuine contribution to Wikipedia, they can go do that the normal way.
)I think that's the tightest integration you can get -- easy access to Wikipedia info, plus your own wiki for company-specific stuff.
On the other hand this right here sounds like a recipe for disaster:When a user accesses Wikipedia from inside our intranet, they receive the wikipedia content, plus the local domain specific information.
For example, links to company-specific wiki pages would be available in Wikipedia pages.That's not a logistical nightmare; that's a major development effort, just for a freakin' wiki.
Requirements like this are why so many software projects fail.
Abandon the pie-in-the-sky vision and go with something simple to start.Like URLs.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713331</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713675</id>
	<title>Don't</title>
	<author>Anonymous</author>
	<datestamp>1247776980000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext>Merging wikipedia with you company wiki is a bad idea:
<ul>
<li>The wikipedia content will always be out of date</li><li>Changes made to wikipedia content don't get fed back into wikipedia</li><li>Creates confusion as to what is and is not company information</li><li>Trying to load the wikipeida DB locally is a headache due to its shear size</li></ul></htmltext>
<tokenext>Merging wikipedia with you company wiki is a bad idea : The wikipedia content will always be out of dateChanges made to wikipedia content do n't get fed back into wikipediaCreates confusion as to what is and is not company informationTrying to load the wikipeida DB locally is a headache due to its shear size</tokentext>
<sentencetext>Merging wikipedia with you company wiki is a bad idea:

The wikipedia content will always be out of dateChanges made to wikipedia content don't get fed back into wikipediaCreates confusion as to what is and is not company informationTrying to load the wikipeida DB locally is a headache due to its shear size</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28717487</id>
	<title>Wikipedia is X rated</title>
	<author>cellurl</author>
	<datestamp>1247761980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Just keep them separate.<br>
I work for a huge corporation and we have our own thing called etipedia.<br>
Also, don't forget, wikipedia is <a href="http://en.wikipedia.org/wiki/Cum\_shot" title="wikipedia.org" rel="nofollow">X rated.</a> [wikipedia.org]</htmltext>
<tokenext>Just keep them separate .
I work for a huge corporation and we have our own thing called etipedia .
Also , do n't forget , wikipedia is X rated .
[ wikipedia.org ]</tokentext>
<sentencetext>Just keep them separate.
I work for a huge corporation and we have our own thing called etipedia.
Also, don't forget, wikipedia is X rated.
[wikipedia.org]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713343</id>
	<title>bad idea</title>
	<author>uepuejq</author>
	<datestamp>1247687220000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext>create a firefox addon that downloads a master list of wikipedia urls to add a link to the intranet site to.  you can use regular expressions to parse the wikipedia source so that your link is consistently placed.  the master list can be updated at will, and could probably be filled the first time with a simple database request.  or something.</htmltext>
<tokenext>create a firefox addon that downloads a master list of wikipedia urls to add a link to the intranet site to .
you can use regular expressions to parse the wikipedia source so that your link is consistently placed .
the master list can be updated at will , and could probably be filled the first time with a simple database request .
or something .</tokentext>
<sentencetext>create a firefox addon that downloads a master list of wikipedia urls to add a link to the intranet site to.
you can use regular expressions to parse the wikipedia source so that your link is consistently placed.
the master list can be updated at will, and could probably be filled the first time with a simple database request.
or something.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28717021</id>
	<title>Re:Don't</title>
	<author>FlyingBishop</author>
	<datestamp>1247760060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Also, strictly speaking, what the poster wants to do is illegal according to the CC-BY-SA and the GFDL.</p><p>See <a href="http://en.wikipedia.org/wiki/Wikipedia:License#Re-use\_of\_text" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Wikipedia:License#Re-use\_of\_text</a> [wikipedia.org] </p><blockquote><div><p>Copyleft/Share Alike<br>
&nbsp; &nbsp; &nbsp; &nbsp; If you make modifications or additions to the page you re-use, you must license them under the Creative Commons Attribution-Share-Alike License 3.0 or later.</p></div></blockquote><p>I'm not sure he's planning on modifying, but it still sounds like a pretty clear-cut copyright violation.</p></div>
	</htmltext>
<tokenext>Also , strictly speaking , what the poster wants to do is illegal according to the CC-BY-SA and the GFDL.See http : //en.wikipedia.org/wiki/Wikipedia : License # Re-use \ _of \ _text [ wikipedia.org ] Copyleft/Share Alike         If you make modifications or additions to the page you re-use , you must license them under the Creative Commons Attribution-Share-Alike License 3.0 or later.I 'm not sure he 's planning on modifying , but it still sounds like a pretty clear-cut copyright violation .</tokentext>
<sentencetext>Also, strictly speaking, what the poster wants to do is illegal according to the CC-BY-SA and the GFDL.See http://en.wikipedia.org/wiki/Wikipedia:License#Re-use\_of\_text [wikipedia.org] Copyleft/Share Alike
        If you make modifications or additions to the page you re-use, you must license them under the Creative Commons Attribution-Share-Alike License 3.0 or later.I'm not sure he's planning on modifying, but it still sounds like a pretty clear-cut copyright violation.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713675</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715903</id>
	<title>leach</title>
	<author>Anonymous</author>
	<datestamp>1247755560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>So basically you want to benefit from the community effort that has built Wikipedia but not give back?  Do I have that correct?</p><p>Think about what Wikipedia would (not) be if everyone had your attitude -- to keep their contributions private.</p></htmltext>
<tokenext>So basically you want to benefit from the community effort that has built Wikipedia but not give back ?
Do I have that correct ? Think about what Wikipedia would ( not ) be if everyone had your attitude -- to keep their contributions private .</tokentext>
<sentencetext>So basically you want to benefit from the community effort that has built Wikipedia but not give back?
Do I have that correct?Think about what Wikipedia would (not) be if everyone had your attitude -- to keep their contributions private.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713479</id>
	<title>Management speak ?</title>
	<author>Anonymous</author>
	<datestamp>1247775120000</datestamp>
	<modclass>Redundant</modclass>
	<modscore>-1</modscore>
	<htmltext><i> leverage existing wikis by augmenting our internal wiki with an external wiki</i> <br> <br>
Congratulations, you have taken your first step into PHB'dom.... <br>
By starting out on a pointless project and using buzzwords to make it sound like you are doing something, you are doomed to failure (or at least mediocrity).</htmltext>
<tokenext>leverage existing wikis by augmenting our internal wiki with an external wiki Congratulations , you have taken your first step into PHB'dom... . By starting out on a pointless project and using buzzwords to make it sound like you are doing something , you are doomed to failure ( or at least mediocrity ) .</tokentext>
<sentencetext> leverage existing wikis by augmenting our internal wiki with an external wiki  
Congratulations, you have taken your first step into PHB'dom.... 
By starting out on a pointless project and using buzzwords to make it sound like you are doing something, you are doomed to failure (or at least mediocrity).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713921</id>
	<title>Frames</title>
	<author>Anonymous</author>
	<datestamp>1247737080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Frames! Enough said.</p></htmltext>
<tokenext>Frames !
Enough said .</tokentext>
<sentencetext>Frames!
Enough said.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28717207</id>
	<title>Extensions</title>
	<author>Jjeff1</author>
	<datestamp>1247760780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I wrote a very simple extension for my own mediawiki site that pulled in external pages as an iframe within a wiki page.

I'd imagine you can do the same, Build your own wiki, with the wikipedia pages included below your own content.</htmltext>
<tokenext>I wrote a very simple extension for my own mediawiki site that pulled in external pages as an iframe within a wiki page .
I 'd imagine you can do the same , Build your own wiki , with the wikipedia pages included below your own content .</tokentext>
<sentencetext>I wrote a very simple extension for my own mediawiki site that pulled in external pages as an iframe within a wiki page.
I'd imagine you can do the same, Build your own wiki, with the wikipedia pages included below your own content.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28725167</id>
	<title>seems like a very easy hack</title>
	<author>portscan</author>
	<datestamp>1247753100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>unless i am completely misunderstanding you, this seems like a pretty easy hack on any wiki engine. just query the page's title at other wikis and append the content to the bottom.  for example: you have a page called Server Farm -- detailing your companies server farm.  whenever that page is loaded in a browser, the dynamic content generator in the website downloads the page with the same name from wikipedia, strips out their formatting, and sticks it at the bottom of your page.  your users can only edit your local content.  this should probably take only a couple hours to fully implement and test.</p><p>if you wanted, you could also parse the "see also" section, and fetch those links and add them. or if you want to be a little more clever, you can allow people to embed keywords for relevant wikipedia articles (or other URLs) in your internal wiki's articles and then fetch those, too.  in the previous example, say your server farm consisted entirely of apple xserves.  you could fetch that wikipedia article and maybe the spec sheet from apple, etc.</p><p>yawn.</p></htmltext>
<tokenext>unless i am completely misunderstanding you , this seems like a pretty easy hack on any wiki engine .
just query the page 's title at other wikis and append the content to the bottom .
for example : you have a page called Server Farm -- detailing your companies server farm .
whenever that page is loaded in a browser , the dynamic content generator in the website downloads the page with the same name from wikipedia , strips out their formatting , and sticks it at the bottom of your page .
your users can only edit your local content .
this should probably take only a couple hours to fully implement and test.if you wanted , you could also parse the " see also " section , and fetch those links and add them .
or if you want to be a little more clever , you can allow people to embed keywords for relevant wikipedia articles ( or other URLs ) in your internal wiki 's articles and then fetch those , too .
in the previous example , say your server farm consisted entirely of apple xserves .
you could fetch that wikipedia article and maybe the spec sheet from apple , etc.yawn .</tokentext>
<sentencetext>unless i am completely misunderstanding you, this seems like a pretty easy hack on any wiki engine.
just query the page's title at other wikis and append the content to the bottom.
for example: you have a page called Server Farm -- detailing your companies server farm.
whenever that page is loaded in a browser, the dynamic content generator in the website downloads the page with the same name from wikipedia, strips out their formatting, and sticks it at the bottom of your page.
your users can only edit your local content.
this should probably take only a couple hours to fully implement and test.if you wanted, you could also parse the "see also" section, and fetch those links and add them.
or if you want to be a little more clever, you can allow people to embed keywords for relevant wikipedia articles (or other URLs) in your internal wiki's articles and then fetch those, too.
in the previous example, say your server farm consisted entirely of apple xserves.
you could fetch that wikipedia article and maybe the spec sheet from apple, etc.yawn.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714217</id>
	<title>Dokuwiki</title>
	<author>Anonymous</author>
	<datestamp>1247740620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>links to wikipedia: [[wp&gt;subject]]<br>internal links: [[subject]]</p><p>you can give the links different colours with CSS, e.g. wp link = blue, internal links = green</p></htmltext>
<tokenext>links to wikipedia : [ [ wp &gt; subject ] ] internal links : [ [ subject ] ] you can give the links different colours with CSS , e.g .
wp link = blue , internal links = green</tokentext>
<sentencetext>links to wikipedia: [[wp&gt;subject]]internal links: [[subject]]you can give the links different colours with CSS, e.g.
wp link = blue, internal links = green</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714419</id>
	<title>howabout about.com?</title>
	<author>bball99</author>
	<datestamp>1247743440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>they were pretty good at page-hijacking, IIRC<nobr> <wbr></nobr>:-)</p><p>seriously though, perhaps i mis-read the question? are you looking for automated tools to do the hyper-links?</p></htmltext>
<tokenext>they were pretty good at page-hijacking , IIRC : - ) seriously though , perhaps i mis-read the question ?
are you looking for automated tools to do the hyper-links ?</tokentext>
<sentencetext>they were pretty good at page-hijacking, IIRC :-)seriously though, perhaps i mis-read the question?
are you looking for automated tools to do the hyper-links?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713747</id>
	<title>your content, how proprietory is it?</title>
	<author>tumbleweedsi</author>
	<datestamp>1247777700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>You need to make sure that there is a clear demarcation between your content and the wikipedia content and this will limit your integration. The last thing you want is for one of your users to upload confidential information onto wikipedia in the mistaken belief they are putting it on the in house wiki.</htmltext>
<tokenext>You need to make sure that there is a clear demarcation between your content and the wikipedia content and this will limit your integration .
The last thing you want is for one of your users to upload confidential information onto wikipedia in the mistaken belief they are putting it on the in house wiki .</tokentext>
<sentencetext>You need to make sure that there is a clear demarcation between your content and the wikipedia content and this will limit your integration.
The last thing you want is for one of your users to upload confidential information onto wikipedia in the mistaken belief they are putting it on the in house wiki.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28716755</id>
	<title>The Real issue is Social.</title>
	<author>Electrawn</author>
	<datestamp>1247759100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You are trying to force a technical solution on a social problem. It's probably not going to work. Your best bet for success is to try and install a WYSIWYG editor for mediawiki. There are several out there. wiki, underneath, is just a programming language. It requires training people - no matter how much it is designed to be "easy." Make it easier.</p><p>Consider Sharepoint. As much as<nobr> <wbr></nobr>/. is Anti-Microsoft, if your users are used to Exchange and Windows then Sharepoint is worth paying for.</p><p>I've worked for Larry Sanger's Citizendium.</p></htmltext>
<tokenext>You are trying to force a technical solution on a social problem .
It 's probably not going to work .
Your best bet for success is to try and install a WYSIWYG editor for mediawiki .
There are several out there .
wiki , underneath , is just a programming language .
It requires training people - no matter how much it is designed to be " easy .
" Make it easier.Consider Sharepoint .
As much as / .
is Anti-Microsoft , if your users are used to Exchange and Windows then Sharepoint is worth paying for.I 've worked for Larry Sanger 's Citizendium .</tokentext>
<sentencetext>You are trying to force a technical solution on a social problem.
It's probably not going to work.
Your best bet for success is to try and install a WYSIWYG editor for mediawiki.
There are several out there.
wiki, underneath, is just a programming language.
It requires training people - no matter how much it is designed to be "easy.
" Make it easier.Consider Sharepoint.
As much as /.
is Anti-Microsoft, if your users are used to Exchange and Windows then Sharepoint is worth paying for.I've worked for Larry Sanger's Citizendium.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713837</id>
	<title>part of an Intelligent Book</title>
	<author>williamhb</author>
	<datestamp>1247735760000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>A very small part of <a href="http://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-719.html" title="cam.ac.uk">My PhD</a> [cam.ac.uk] looked at this (but with "collaborative textbooks" rather than wikis) -- see Chapter 4.  Adding a very simple metadata-based navigation layer over the top of the wiki is pretty easy, clean (doesn't confuse users), and seems to do the trick.  The wiki itself shows in an embedded frame.  Of course, I had to go further and let students do difficult number theory proofs backed by machine reasoning systems within the book, but you won't have to solve that problem!</p><p>I'm (gradually) putting this fairly simple but useful part of the software into an online resource at <a href="http://www.theintelligentbook.com/" title="theintelligentbook.com">www.theintelligentbook.com</a> [theintelligentbook.com], though it's in my spare time and the system is down at the moment.  I'll put my contact details back up there shortly in case the question-asker wants to discuss it technically.</p></htmltext>
<tokenext>A very small part of My PhD [ cam.ac.uk ] looked at this ( but with " collaborative textbooks " rather than wikis ) -- see Chapter 4 .
Adding a very simple metadata-based navigation layer over the top of the wiki is pretty easy , clean ( does n't confuse users ) , and seems to do the trick .
The wiki itself shows in an embedded frame .
Of course , I had to go further and let students do difficult number theory proofs backed by machine reasoning systems within the book , but you wo n't have to solve that problem ! I 'm ( gradually ) putting this fairly simple but useful part of the software into an online resource at www.theintelligentbook.com [ theintelligentbook.com ] , though it 's in my spare time and the system is down at the moment .
I 'll put my contact details back up there shortly in case the question-asker wants to discuss it technically .</tokentext>
<sentencetext>A very small part of My PhD [cam.ac.uk] looked at this (but with "collaborative textbooks" rather than wikis) -- see Chapter 4.
Adding a very simple metadata-based navigation layer over the top of the wiki is pretty easy, clean (doesn't confuse users), and seems to do the trick.
The wiki itself shows in an embedded frame.
Of course, I had to go further and let students do difficult number theory proofs backed by machine reasoning systems within the book, but you won't have to solve that problem!I'm (gradually) putting this fairly simple but useful part of the software into an online resource at www.theintelligentbook.com [theintelligentbook.com], though it's in my spare time and the system is down at the moment.
I'll put my contact details back up there shortly in case the question-asker wants to discuss it technically.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713849</id>
	<title>don't mix security contexts.</title>
	<author>Anonymous</author>
	<datestamp>1247736000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>What happens when a user doesn't understand that this isn't a local copy, and edits a wikipedia page with private information?</p><p>This is a bad idea, period.</p></htmltext>
<tokenext>What happens when a user does n't understand that this is n't a local copy , and edits a wikipedia page with private information ? This is a bad idea , period .</tokentext>
<sentencetext>What happens when a user doesn't understand that this isn't a local copy, and edits a wikipedia page with private information?This is a bad idea, period.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28716185</id>
	<title>interwiki</title>
	<author>Anonymous</author>
	<datestamp>1247756700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Use mediawiki as your wiki and add the interwiki plugin.  See http://meta.wikimedia.org/wiki/Help:Interwiki\_linking</p></htmltext>
<tokenext>Use mediawiki as your wiki and add the interwiki plugin .
See http : //meta.wikimedia.org/wiki/Help : Interwiki \ _linking</tokentext>
<sentencetext>Use mediawiki as your wiki and add the interwiki plugin.
See http://meta.wikimedia.org/wiki/Help:Interwiki\_linking</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28721523</id>
	<title>yeah whatever</title>
	<author>Anonymous</author>
	<datestamp>1247777100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>this is a really dumb idea. forget about it. tell them its not possible and move on to burning the company's money on something of more value.</p></htmltext>
<tokenext>this is a really dumb idea .
forget about it .
tell them its not possible and move on to burning the company 's money on something of more value .</tokentext>
<sentencetext>this is a really dumb idea.
forget about it.
tell them its not possible and move on to burning the company's money on something of more value.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713331</id>
	<title>URLs</title>
	<author>Anonymous</author>
	<datestamp>1247687100000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>URLs. Look into it.</p></htmltext>
<tokenext>URLs .
Look into it .</tokentext>
<sentencetext>URLs.
Look into it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713989</id>
	<title>Learn from mistakes.</title>
	<author>JamesR404</author>
	<datestamp>1247737920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I think this is a very interesting story.

Aside from the technical question raised, I am wondering why the first corporate Wiki wasn't successful. If it failed the first time because the culture isn't right or there wasn't any management support, a second wiki tool - no matter how seamlessly integrated - won't succeed either.

Even if you have a company with many different technical domains it's even more reasonable to be able to share information. And an article shouldn't try to be totally comprehensible. You could write a parent page describing the concept, and subpages that are specialised for the different domains.

I'd love to discuss this further.</htmltext>
<tokenext>I think this is a very interesting story .
Aside from the technical question raised , I am wondering why the first corporate Wiki was n't successful .
If it failed the first time because the culture is n't right or there was n't any management support , a second wiki tool - no matter how seamlessly integrated - wo n't succeed either .
Even if you have a company with many different technical domains it 's even more reasonable to be able to share information .
And an article should n't try to be totally comprehensible .
You could write a parent page describing the concept , and subpages that are specialised for the different domains .
I 'd love to discuss this further .</tokentext>
<sentencetext>I think this is a very interesting story.
Aside from the technical question raised, I am wondering why the first corporate Wiki wasn't successful.
If it failed the first time because the culture isn't right or there wasn't any management support, a second wiki tool - no matter how seamlessly integrated - won't succeed either.
Even if you have a company with many different technical domains it's even more reasonable to be able to share information.
And an article shouldn't try to be totally comprehensible.
You could write a parent page describing the concept, and subpages that are specialised for the different domains.
I'd love to discuss this further.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28723675</id>
	<title>Re:URLs</title>
	<author>Nefarious Wheel</author>
	<datestamp>1247742960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Said in a crude way; but to the OP: This guy is right</p></div><p>Agree with S77IM in whole. I've put together several Wikis for corporate use.  URL's are magic.  Aggregators aren't quite that simple, and the ones we tend to see from casual Google searches are almost universally held in contempt.  Don't go there.</p><p>The company I work for settled on Confluence because we insisted on attribution and integration with our global AD (by "Global" I mean "about 40 countries").  It isn't all that bad.  Stylistically and for tracking I prefer Wikimedia, but in an engineering and SI firm the forced attribution has been a contributor to what seems to be a competitive spirit to improve the quality, which all seem to regard as a good thing.  And the number of articles keeps going up.</p></div>
	</htmltext>
<tokenext>Said in a crude way ; but to the OP : This guy is rightAgree with S77IM in whole .
I 've put together several Wikis for corporate use .
URL 's are magic .
Aggregators are n't quite that simple , and the ones we tend to see from casual Google searches are almost universally held in contempt .
Do n't go there.The company I work for settled on Confluence because we insisted on attribution and integration with our global AD ( by " Global " I mean " about 40 countries " ) .
It is n't all that bad .
Stylistically and for tracking I prefer Wikimedia , but in an engineering and SI firm the forced attribution has been a contributor to what seems to be a competitive spirit to improve the quality , which all seem to regard as a good thing .
And the number of articles keeps going up .</tokentext>
<sentencetext>Said in a crude way; but to the OP: This guy is rightAgree with S77IM in whole.
I've put together several Wikis for corporate use.
URL's are magic.
Aggregators aren't quite that simple, and the ones we tend to see from casual Google searches are almost universally held in contempt.
Don't go there.The company I work for settled on Confluence because we insisted on attribution and integration with our global AD (by "Global" I mean "about 40 countries").
It isn't all that bad.
Stylistically and for tracking I prefer Wikimedia, but in an engineering and SI firm the forced attribution has been a contributor to what seems to be a competitive spirit to improve the quality, which all seem to regard as a good thing.
And the number of articles keeps going up.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715755</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28718367</id>
	<title>We do this with External Links from MediaWiki</title>
	<author>Anonymous</author>
	<datestamp>1247765100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Uh...we do this with some success and we just add external links to wikipedia articles in our local intranet media wiki articles.   Each division has their own wiki article and subjects are organized therein.  No need to reinvent the wheel just link to it.</p></htmltext>
<tokenext>Uh...we do this with some success and we just add external links to wikipedia articles in our local intranet media wiki articles .
Each division has their own wiki article and subjects are organized therein .
No need to reinvent the wheel just link to it .</tokentext>
<sentencetext>Uh...we do this with some success and we just add external links to wikipedia articles in our local intranet media wiki articles.
Each division has their own wiki article and subjects are organized therein.
No need to reinvent the wheel just link to it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28716165</id>
	<title>See Also:</title>
	<author>Anonymous</author>
	<datestamp>1247756640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Scan each internal page and see what wikipedia pages it links to.  Store that info in a database.  Make a firefox plugin that works as follows:<br>When a user is at a wikipedia page query the database and see which internal pages link to it.  Add those links to the "See Also:" part of the wikipedia page.</p><p>No you wouldn't get inline links but it sounds much easier.</p></htmltext>
<tokenext>Scan each internal page and see what wikipedia pages it links to .
Store that info in a database .
Make a firefox plugin that works as follows : When a user is at a wikipedia page query the database and see which internal pages link to it .
Add those links to the " See Also : " part of the wikipedia page.No you would n't get inline links but it sounds much easier .</tokentext>
<sentencetext>Scan each internal page and see what wikipedia pages it links to.
Store that info in a database.
Make a firefox plugin that works as follows:When a user is at a wikipedia page query the database and see which internal pages link to it.
Add those links to the "See Also:" part of the wikipedia page.No you wouldn't get inline links but it sounds much easier.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714413</id>
	<title>Re:Download it</title>
	<author>paulatz</author>
	<datestamp>1247743320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It does not include images, and all the integration with Wikimedia Commons, the Wiktionary and other projects. Last but not least, it does not update as wikiepdia is edited.</htmltext>
<tokenext>It does not include images , and all the integration with Wikimedia Commons , the Wiktionary and other projects .
Last but not least , it does not update as wikiepdia is edited .</tokentext>
<sentencetext>It does not include images, and all the integration with Wikimedia Commons, the Wiktionary and other projects.
Last but not least, it does not update as wikiepdia is edited.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713397</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715577</id>
	<title>Greasemonkey</title>
	<author>Steneub</author>
	<datestamp>1247753940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>My first thought was to use a Greasemonkey (or Greasemonkey analogue) to add whatever you wanted to pages that show up on Wikipedia.  The way it could be integrated is you have the internal wiki with its markup and everything named as the same page title as what's on Wikipedia. When a page on Wikipedia is loaded, the script appends the internal wiki onto the Wikipedia page.</p><p>Others' concerns about Wikipedia being out of date or contradictory are valid though. You would probably do better to either.
</p><ol> <li>Don't!</li><li>At least make it very clear to end-users what is external and what is internal.</li></ol><p>Extra Points earned if, when someone clicks to edit an entry that has internal information, the process is seamless and feels like editing the Wikipedia page itself.</p></htmltext>
<tokenext>My first thought was to use a Greasemonkey ( or Greasemonkey analogue ) to add whatever you wanted to pages that show up on Wikipedia .
The way it could be integrated is you have the internal wiki with its markup and everything named as the same page title as what 's on Wikipedia .
When a page on Wikipedia is loaded , the script appends the internal wiki onto the Wikipedia page.Others ' concerns about Wikipedia being out of date or contradictory are valid though .
You would probably do better to either .
Do n't ! At least make it very clear to end-users what is external and what is internal.Extra Points earned if , when someone clicks to edit an entry that has internal information , the process is seamless and feels like editing the Wikipedia page itself .</tokentext>
<sentencetext>My first thought was to use a Greasemonkey (or Greasemonkey analogue) to add whatever you wanted to pages that show up on Wikipedia.
The way it could be integrated is you have the internal wiki with its markup and everything named as the same page title as what's on Wikipedia.
When a page on Wikipedia is loaded, the script appends the internal wiki onto the Wikipedia page.Others' concerns about Wikipedia being out of date or contradictory are valid though.
You would probably do better to either.
Don't!At least make it very clear to end-users what is external and what is internal.Extra Points earned if, when someone clicks to edit an entry that has internal information, the process is seamless and feels like editing the Wikipedia page itself.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714145</id>
	<title>Re:bad idea</title>
	<author>Max Romantschuk</author>
	<datestamp>1247739780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I wholeheartedly agree with the parent. Your best bet at doing this well is doing this as dynamically as possible. Scraping web pages is a huge pain. Building an extension to detect when you're visising wikipedia and inject something into the page is a hell of a lot simpler.</p><p>Another poster suggested greasemonkey. I haven't used it myself, but I suspect it would make sense to develop a prototype with greasemonkey first. It might well be that a custom extension is not needed at all.</p><p>Also, Firebug is your friend.</p></htmltext>
<tokenext>I wholeheartedly agree with the parent .
Your best bet at doing this well is doing this as dynamically as possible .
Scraping web pages is a huge pain .
Building an extension to detect when you 're visising wikipedia and inject something into the page is a hell of a lot simpler.Another poster suggested greasemonkey .
I have n't used it myself , but I suspect it would make sense to develop a prototype with greasemonkey first .
It might well be that a custom extension is not needed at all.Also , Firebug is your friend .</tokentext>
<sentencetext>I wholeheartedly agree with the parent.
Your best bet at doing this well is doing this as dynamically as possible.
Scraping web pages is a huge pain.
Building an extension to detect when you're visising wikipedia and inject something into the page is a hell of a lot simpler.Another poster suggested greasemonkey.
I haven't used it myself, but I suspect it would make sense to develop a prototype with greasemonkey first.
It might well be that a custom extension is not needed at all.Also, Firebug is your friend.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713343</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714665</id>
	<title>Re:Business Talk is Stupid Talk</title>
	<author>PMBjornerud</author>
	<datestamp>1247746500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>"What we would like to do is leverage existing wikis by augmenting our internal wiki with an external wiki"</p><p>What does that even mean? If you want to design something, you'll have to use more precise language.</p><p><div class="quote"><p>His example is much clearer:<br>For example, links to company-specific wiki pages would be available in Wikipedia pages.</p><p>One solution could be a Firefox greasemonkey script, as someone above already suggested.</p></div></div></div>
	</htmltext>
<tokenext>" What we would like to do is leverage existing wikis by augmenting our internal wiki with an external wiki " What does that even mean ?
If you want to design something , you 'll have to use more precise language.His example is much clearer : For example , links to company-specific wiki pages would be available in Wikipedia pages.One solution could be a Firefox greasemonkey script , as someone above already suggested .</tokentext>
<sentencetext>"What we would like to do is leverage existing wikis by augmenting our internal wiki with an external wiki"What does that even mean?
If you want to design something, you'll have to use more precise language.His example is much clearer:For example, links to company-specific wiki pages would be available in Wikipedia pages.One solution could be a Firefox greasemonkey script, as someone above already suggested.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713857</id>
	<title>Re:Don't</title>
	<author>korpique</author>
	<datestamp>1247736120000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>I agree (would mod up but gave up modding way back). However this is an interesting and probably reoccurring problem: extending the wealth of public net wisdom with precision data from local context (organisational or task-centric rather than geolocational).</p><p>
&nbsp; </p><p>A proxy adding local content into pages loaded from outside as suggested in <a href="http://ask.slashdot.org/comments.pl?sid=1304239&amp;cid=28713563" title="slashdot.org" rel="nofollow">Re:Solution by mcrbids</a> [slashdot.org] would solve some of the problems you mention:</p><p>
&nbsp; </p><p>
&nbsp; &nbsp; &nbsp; &nbsp; * The wikipedia content will always be out of date<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; * it's fetched from real sources in real time<br>
&nbsp; &nbsp; &nbsp; &nbsp; * Changes made to wikipedia content don't get fed back into wikipedia<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; * this changes to risk of unintentionally publishing private information - how hilarious!<br>
&nbsp; &nbsp; &nbsp; &nbsp; * Trying to load the wikipeida DB locally is a headache due to its shear size<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; * not done; could instead cover the whole of outside web with one solution.</p><p>
&nbsp; </p><p>This problem remains:</p><p>
&nbsp; </p><p>
&nbsp; &nbsp; &nbsp; &nbsp; * Creates confusion as to what is and is not company information</p><p>
&nbsp; </p><p>I guess you'd be best off injecting a (user-hidable) "widget" layer that would contain all the local information needed, thus providing clear separation of local and global content. Least breakage of existing layout that way, I hope.</p><p>
&nbsp; </p><p>I assume here that we restrict our proxy to embed HTML (possibly including Javascript) into well parsing HTML pages only, so as to avoid breaking things as much as possible - inevitable to happen sometimes anyway.</p><p>
&nbsp; </p><p>Updating the contents of another window based on browsed content would require either</p><p>
&nbsp; </p><p>
&nbsp; &nbsp; &nbsp; &nbsp; * a single sign-on solution to target references to correct user's desktop (seen in updaters of multiple applications views in medical solutions for instance) or<br>
&nbsp; &nbsp; &nbsp; &nbsp; * a browser-specific local hack to study each page url and content and to fetch related information from local database based on those.</p><p>
&nbsp; </p><p>OT, adding such meshing into Google Wave would probably prove an interesting challenge<nobr> <wbr></nobr>:) Think of doing it Right (tm), with private additions to documents and discussions getting saved and tracked on local servers while public parts would be passed on to public servers.</p><p>
&nbsp; </p></htmltext>
<tokenext>I agree ( would mod up but gave up modding way back ) .
However this is an interesting and probably reoccurring problem : extending the wealth of public net wisdom with precision data from local context ( organisational or task-centric rather than geolocational ) .
  A proxy adding local content into pages loaded from outside as suggested in Re : Solution by mcrbids [ slashdot.org ] would solve some of the problems you mention :           * The wikipedia content will always be out of date                 * it 's fetched from real sources in real time         * Changes made to wikipedia content do n't get fed back into wikipedia                 * this changes to risk of unintentionally publishing private information - how hilarious !
        * Trying to load the wikipeida DB locally is a headache due to its shear size                 * not done ; could instead cover the whole of outside web with one solution .
  This problem remains :           * Creates confusion as to what is and is not company information   I guess you 'd be best off injecting a ( user-hidable ) " widget " layer that would contain all the local information needed , thus providing clear separation of local and global content .
Least breakage of existing layout that way , I hope .
  I assume here that we restrict our proxy to embed HTML ( possibly including Javascript ) into well parsing HTML pages only , so as to avoid breaking things as much as possible - inevitable to happen sometimes anyway .
  Updating the contents of another window based on browsed content would require either           * a single sign-on solution to target references to correct user 's desktop ( seen in updaters of multiple applications views in medical solutions for instance ) or         * a browser-specific local hack to study each page url and content and to fetch related information from local database based on those .
  OT , adding such meshing into Google Wave would probably prove an interesting challenge : ) Think of doing it Right ( tm ) , with private additions to documents and discussions getting saved and tracked on local servers while public parts would be passed on to public servers .
 </tokentext>
<sentencetext>I agree (would mod up but gave up modding way back).
However this is an interesting and probably reoccurring problem: extending the wealth of public net wisdom with precision data from local context (organisational or task-centric rather than geolocational).
  A proxy adding local content into pages loaded from outside as suggested in Re:Solution by mcrbids [slashdot.org] would solve some of the problems you mention:
  
        * The wikipedia content will always be out of date
                * it's fetched from real sources in real time
        * Changes made to wikipedia content don't get fed back into wikipedia
                * this changes to risk of unintentionally publishing private information - how hilarious!
        * Trying to load the wikipeida DB locally is a headache due to its shear size
                * not done; could instead cover the whole of outside web with one solution.
  This problem remains:
  
        * Creates confusion as to what is and is not company information
  I guess you'd be best off injecting a (user-hidable) "widget" layer that would contain all the local information needed, thus providing clear separation of local and global content.
Least breakage of existing layout that way, I hope.
  I assume here that we restrict our proxy to embed HTML (possibly including Javascript) into well parsing HTML pages only, so as to avoid breaking things as much as possible - inevitable to happen sometimes anyway.
  Updating the contents of another window based on browsed content would require either
  
        * a single sign-on solution to target references to correct user's desktop (seen in updaters of multiple applications views in medical solutions for instance) or
        * a browser-specific local hack to study each page url and content and to fetch related information from local database based on those.
  OT, adding such meshing into Google Wave would probably prove an interesting challenge :) Think of doing it Right (tm), with private additions to documents and discussions getting saved and tracked on local servers while public parts would be passed on to public servers.
  </sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713675</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714679</id>
	<title>Re:Business Talk is Stupid Talk</title>
	<author>Hognoxious</author>
	<datestamp>1247746680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I have no idea what he means, but when he ran it up the flagpole I saluted.</htmltext>
<tokenext>I have no idea what he means , but when he ran it up the flagpole I saluted .</tokentext>
<sentencetext>I have no idea what he means, but when he ran it up the flagpole I saluted.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714379</id>
	<title>Re:Business Talk is Stupid Talk</title>
	<author>MrMr</author>
	<datestamp>1247742780000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>As a non native speaker I find a dictionary quite convenient in these cases. so I'll do some back and forth translation for you here:<br>
<br>
leverage (v.) -&gt; opkrikken -&gt; fuck up<br>
augment -&gt; duurder maken -&gt; make more expensive<br>
internal wiki -&gt; krabbel zonder net -&gt; off-line blurb<br>
external wiki -&gt; krabbel met net -&gt; on-line blurb<br>
existing -&gt; nog bestaand -&gt; not yet deleted
<br> <br>
So the English to English translation is:
"What we would like to do is fuck up non yet deleted blurbs by making our off-line blurbs more expensive with on-line blurbs".<br>
Now that I can understand.</htmltext>
<tokenext>As a non native speaker I find a dictionary quite convenient in these cases .
so I 'll do some back and forth translation for you here : leverage ( v. ) - &gt; opkrikken - &gt; fuck up augment - &gt; duurder maken - &gt; make more expensive internal wiki - &gt; krabbel zonder net - &gt; off-line blurb external wiki - &gt; krabbel met net - &gt; on-line blurb existing - &gt; nog bestaand - &gt; not yet deleted So the English to English translation is : " What we would like to do is fuck up non yet deleted blurbs by making our off-line blurbs more expensive with on-line blurbs " .
Now that I can understand .</tokentext>
<sentencetext>As a non native speaker I find a dictionary quite convenient in these cases.
so I'll do some back and forth translation for you here:

leverage (v.) -&gt; opkrikken -&gt; fuck up
augment -&gt; duurder maken -&gt; make more expensive
internal wiki -&gt; krabbel zonder net -&gt; off-line blurb
external wiki -&gt; krabbel met net -&gt; on-line blurb
existing -&gt; nog bestaand -&gt; not yet deleted
 
So the English to English translation is:
"What we would like to do is fuck up non yet deleted blurbs by making our off-line blurbs more expensive with on-line blurbs".
Now that I can understand.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714319</id>
	<title>Re:Business Talk is Stupid Talk</title>
	<author>Anonymous</author>
	<datestamp>1247742000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>whilst i agree with your overall sentiment...</p><p>the word leverage has meanings beyond the mechanical sense, and despite the sentence in question being in my opinion quite clumsy; its meaning is not lost nor backwards.</p><p>one may leverage a resource in order gain some kind of advantage.</p><p>In anycase, I agree with your general point, 'ffs use some clarity, this is<nobr> <wbr></nobr>/. not bloomberg.com', the use of the word here was hardly pivotal.</p></htmltext>
<tokenext>whilst i agree with your overall sentiment...the word leverage has meanings beyond the mechanical sense , and despite the sentence in question being in my opinion quite clumsy ; its meaning is not lost nor backwards.one may leverage a resource in order gain some kind of advantage.In anycase , I agree with your general point , 'ffs use some clarity , this is / .
not bloomberg.com ' , the use of the word here was hardly pivotal .</tokentext>
<sentencetext>whilst i agree with your overall sentiment...the word leverage has meanings beyond the mechanical sense, and despite the sentence in question being in my opinion quite clumsy; its meaning is not lost nor backwards.one may leverage a resource in order gain some kind of advantage.In anycase, I agree with your general point, 'ffs use some clarity, this is /.
not bloomberg.com', the use of the word here was hardly pivotal.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28717265</id>
	<title>Tearline Wiki</title>
	<author>ijones</author>
	<datestamp>1247761020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The experimental <a href="http://www.galois.com/files/MLwiki\_Datasheet.pdf" title="galois.com">Tearline Wiki</a> [galois.com] system we've developed at <a href="http://www.galois.com/" title="galois.com">Galois</a> [galois.com] might suit your needs. Inside the firewall, you use MediaWiki with the Tearline system, and get a combined view of your internal wiki(s), possibly different wikis on different sub-nets, and you can integrate it with Wikipedia or other internet-based wikis to get the global context of the article.</p><p>As others have said, integrating your content with other people's content can be a legal issue.</p><p>Contact me if you want more information on Tearline<nobr> <wbr></nobr>:)</p><p>peace,</p><p>
&nbsp; &nbsp; isaac</p></htmltext>
<tokenext>The experimental Tearline Wiki [ galois.com ] system we 've developed at Galois [ galois.com ] might suit your needs .
Inside the firewall , you use MediaWiki with the Tearline system , and get a combined view of your internal wiki ( s ) , possibly different wikis on different sub-nets , and you can integrate it with Wikipedia or other internet-based wikis to get the global context of the article.As others have said , integrating your content with other people 's content can be a legal issue.Contact me if you want more information on Tearline : ) peace ,     isaac</tokentext>
<sentencetext>The experimental Tearline Wiki [galois.com] system we've developed at Galois [galois.com] might suit your needs.
Inside the firewall, you use MediaWiki with the Tearline system, and get a combined view of your internal wiki(s), possibly different wikis on different sub-nets, and you can integrate it with Wikipedia or other internet-based wikis to get the global context of the article.As others have said, integrating your content with other people's content can be a legal issue.Contact me if you want more information on Tearline :)peace,
    isaac</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475</id>
	<title>Business Talk is Stupid Talk</title>
	<author>Anonymous</author>
	<datestamp>1247775060000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>"What we would like to do is leverage existing wikis by augmenting our internal wiki with an external wiki"</p><p>What does that even mean? If you want to design something, you'll have to use more precise language. And for god's sake, stop using the word leverage without thinking about it. You used it backwards - if you are augmenting your internal wiki with external wikis, you are leveraging your internal wiki with the external wikis. You leverage a boulder with a lever, but you don't leverage a lever with a boulder.</p></htmltext>
<tokenext>" What we would like to do is leverage existing wikis by augmenting our internal wiki with an external wiki " What does that even mean ?
If you want to design something , you 'll have to use more precise language .
And for god 's sake , stop using the word leverage without thinking about it .
You used it backwards - if you are augmenting your internal wiki with external wikis , you are leveraging your internal wiki with the external wikis .
You leverage a boulder with a lever , but you do n't leverage a lever with a boulder .</tokentext>
<sentencetext>"What we would like to do is leverage existing wikis by augmenting our internal wiki with an external wiki"What does that even mean?
If you want to design something, you'll have to use more precise language.
And for god's sake, stop using the word leverage without thinking about it.
You used it backwards - if you are augmenting your internal wiki with external wikis, you are leveraging your internal wiki with the external wikis.
You leverage a boulder with a lever, but you don't leverage a lever with a boulder.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28718585</id>
	<title>Re:Business Talk is Stupid Talk</title>
	<author>psmears</author>
	<datestamp>1247765820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>You leverage a boulder with a lever, but you don't leverage a lever with a boulder.</p></div><p>Actually I <a href="http://dictionary.cambridge.org/define\_b.asp?key=45757&amp;dict=CALD" title="cambridge.org">lever</a> [cambridge.org] the boulder with a lever. Where I come from, "leverage" is a noun, to which the corresponding verb is "lever"<nobr> <wbr></nobr>:-)</p></div>
	</htmltext>
<tokenext>You leverage a boulder with a lever , but you do n't leverage a lever with a boulder.Actually I lever [ cambridge.org ] the boulder with a lever .
Where I come from , " leverage " is a noun , to which the corresponding verb is " lever " : - )</tokentext>
<sentencetext>You leverage a boulder with a lever, but you don't leverage a lever with a boulder.Actually I lever [cambridge.org] the boulder with a lever.
Where I come from, "leverage" is a noun, to which the corresponding verb is "lever" :-)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713847</id>
	<title>Re:interwiki</title>
	<author>Anonymous</author>
	<datestamp>1247735940000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><p><div class="quote"><p>You probably want <a href="http://en.wikipedia.org/wiki/InterWiki" title="wikipedia.org" rel="nofollow">interwiki</a> [wikipedia.org].</p></div><p>Yes, but I have a wiki fetish. Due to the open nature of most of them, I will be copulating with wikis until 2029, at least.</p></div>
	</htmltext>
<tokenext>You probably want interwiki [ wikipedia.org ] .Yes , but I have a wiki fetish .
Due to the open nature of most of them , I will be copulating with wikis until 2029 , at least .</tokentext>
<sentencetext>You probably want interwiki [wikipedia.org].Yes, but I have a wiki fetish.
Due to the open nature of most of them, I will be copulating with wikis until 2029, at least.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713619</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713399</id>
	<title>Solution</title>
	<author>Anonymous</author>
	<datestamp>1247687820000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>Perhaps the easiest thing to do would be start with a complete dump of Wikipedia and add your own stuff to it.  Their database dump page is <a href="http://en.wikipedia.org/wiki/Wikipedia\_database" title="wikipedia.org">here</a> [wikipedia.org].</p><p>It <i>is</i> 2.8TB, however.  They allude to a "Wikipedia API" for working on a "random subset" of Wikipedia; maybe that would be helpful too.</p></htmltext>
<tokenext>Perhaps the easiest thing to do would be start with a complete dump of Wikipedia and add your own stuff to it .
Their database dump page is here [ wikipedia.org ] .It is 2.8TB , however .
They allude to a " Wikipedia API " for working on a " random subset " of Wikipedia ; maybe that would be helpful too .</tokentext>
<sentencetext>Perhaps the easiest thing to do would be start with a complete dump of Wikipedia and add your own stuff to it.
Their database dump page is here [wikipedia.org].It is 2.8TB, however.
They allude to a "Wikipedia API" for working on a "random subset" of Wikipedia; maybe that would be helpful too.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713787</id>
	<title>What?</title>
	<author>madcow\_ucsb</author>
	<datestamp>1247735040000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Why?  Can't you just link to wikipedia pages where appropriate?  OK, my company has an internal server we link through to sanitize referrer info so our internal wiki titles don't get all over teh interwebs.  But if the wiki users can't figure out "hey, this article is too specific - maybe wikipedia has more general information that would help me," you've got bigger problems than your wiki management.</p></htmltext>
<tokenext>Why ?
Ca n't you just link to wikipedia pages where appropriate ?
OK , my company has an internal server we link through to sanitize referrer info so our internal wiki titles do n't get all over teh interwebs .
But if the wiki users ca n't figure out " hey , this article is too specific - maybe wikipedia has more general information that would help me , " you 've got bigger problems than your wiki management .</tokentext>
<sentencetext>Why?
Can't you just link to wikipedia pages where appropriate?
OK, my company has an internal server we link through to sanitize referrer info so our internal wiki titles don't get all over teh interwebs.
But if the wiki users can't figure out "hey, this article is too specific - maybe wikipedia has more general information that would help me," you've got bigger problems than your wiki management.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714237</id>
	<title>The simplest solution I can think of is..</title>
	<author>kikito</author>
	<datestamp>1247740980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>
1. On your personal wiki server, have a copy of each page of the wikipedia you want to apply modifications to, and add whatever you want on those.
</p><p>
2. Have a modified http proxy on the intranet that detects queries to the wikipedia about items that you have on the server and re-route them.
</p><p>
For example, let's say you want custom information on <a href="http://en.wikipedia.org/wiki/Socks" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Socks</a> [wikipedia.org]. You copy it to  http//yourintranetserver/wiki/Socks, and make your changes.
</p><p>
Then, if someone from inside your network tries to get <a href="http://en.wikipedia.org/wiki/Socks" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Socks</a> [wikipedia.org], they get yours instead.
</p><p>
At the same time, the proxy needs to be intelligent enough to redirect back to the wikipedia page if your server doesn't have a page. Ideally the http redirect rules should be put automatically in place when a new page is added to yourintranetserver.</p></htmltext>
<tokenext>1 .
On your personal wiki server , have a copy of each page of the wikipedia you want to apply modifications to , and add whatever you want on those .
2. Have a modified http proxy on the intranet that detects queries to the wikipedia about items that you have on the server and re-route them .
For example , let 's say you want custom information on http : //en.wikipedia.org/wiki/Socks [ wikipedia.org ] .
You copy it to http//yourintranetserver/wiki/Socks , and make your changes .
Then , if someone from inside your network tries to get http : //en.wikipedia.org/wiki/Socks [ wikipedia.org ] , they get yours instead .
At the same time , the proxy needs to be intelligent enough to redirect back to the wikipedia page if your server does n't have a page .
Ideally the http redirect rules should be put automatically in place when a new page is added to yourintranetserver .</tokentext>
<sentencetext>
1.
On your personal wiki server, have a copy of each page of the wikipedia you want to apply modifications to, and add whatever you want on those.
2. Have a modified http proxy on the intranet that detects queries to the wikipedia about items that you have on the server and re-route them.
For example, let's say you want custom information on http://en.wikipedia.org/wiki/Socks [wikipedia.org].
You copy it to  http//yourintranetserver/wiki/Socks, and make your changes.
Then, if someone from inside your network tries to get http://en.wikipedia.org/wiki/Socks [wikipedia.org], they get yours instead.
At the same time, the proxy needs to be intelligent enough to redirect back to the wikipedia page if your server doesn't have a page.
Ideally the http redirect rules should be put automatically in place when a new page is added to yourintranetserver.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715581</id>
	<title>Re:Business Talk is Stupid Talk</title>
	<author>Lumpy</author>
	<datestamp>1247754000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>give him some slack, he's been in meetings all week with PHB's and Executives that throw the terms around like candy and they don't even know what it means.</p><p>"It will bring us a whole new dynamic by leveraging our skill-set when applied to the future latitude and positions."</p><p>Everyone knows the suits in the corner offices talk only to hear themselves talk.  It's either that or Business Administration degrees have a "ramble on like you are educated" class requirement.</p></htmltext>
<tokenext>give him some slack , he 's been in meetings all week with PHB 's and Executives that throw the terms around like candy and they do n't even know what it means .
" It will bring us a whole new dynamic by leveraging our skill-set when applied to the future latitude and positions .
" Everyone knows the suits in the corner offices talk only to hear themselves talk .
It 's either that or Business Administration degrees have a " ramble on like you are educated " class requirement .</tokentext>
<sentencetext>give him some slack, he's been in meetings all week with PHB's and Executives that throw the terms around like candy and they don't even know what it means.
"It will bring us a whole new dynamic by leveraging our skill-set when applied to the future latitude and positions.
"Everyone knows the suits in the corner offices talk only to hear themselves talk.
It's either that or Business Administration degrees have a "ramble on like you are educated" class requirement.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28716201</id>
	<title>Is this really worthwhile?</title>
	<author>gertam</author>
	<datestamp>1247756760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I don't get it. Are people in your company using Wikipedia so much in their daily work that this would really be useful. Just set up your internal wiki. It is your focal point. Why try and integrate the two beyond just making a link to Wikipedia? Using Mediawiki, you can even use Interwiki links to easily link outside of your internal wiki.</p></htmltext>
<tokenext>I do n't get it .
Are people in your company using Wikipedia so much in their daily work that this would really be useful .
Just set up your internal wiki .
It is your focal point .
Why try and integrate the two beyond just making a link to Wikipedia ?
Using Mediawiki , you can even use Interwiki links to easily link outside of your internal wiki .</tokentext>
<sentencetext>I don't get it.
Are people in your company using Wikipedia so much in their daily work that this would really be useful.
Just set up your internal wiki.
It is your focal point.
Why try and integrate the two beyond just making a link to Wikipedia?
Using Mediawiki, you can even use Interwiki links to easily link outside of your internal wiki.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713613</id>
	<title>Doinitwrong</title>
	<author>Anonymous</author>
	<datestamp>1247776500000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Agreed.  Appending to wikipedia is the ass backwards way to do it. Everyone suggesting greasemonkey and other addons are just enabling your backassery.</p><p>What you do is create an internal wiki, and wherever relevent you link to  the wikipedia article. Or an external doc. Or nothing at all and expect your employees to look it up on their own.</p></htmltext>
<tokenext>Agreed .
Appending to wikipedia is the ass backwards way to do it .
Everyone suggesting greasemonkey and other addons are just enabling your backassery.What you do is create an internal wiki , and wherever relevent you link to the wikipedia article .
Or an external doc .
Or nothing at all and expect your employees to look it up on their own .</tokentext>
<sentencetext>Agreed.
Appending to wikipedia is the ass backwards way to do it.
Everyone suggesting greasemonkey and other addons are just enabling your backassery.What you do is create an internal wiki, and wherever relevent you link to  the wikipedia article.
Or an external doc.
Or nothing at all and expect your employees to look it up on their own.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28720673</id>
	<title>Squid Proxy</title>
	<author>psychcf</author>
	<datestamp>1247773500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Use squid proxy to inject the extra content, that way it's centralized.</htmltext>
<tokenext>Use squid proxy to inject the extra content , that way it 's centralized .</tokentext>
<sentencetext>Use squid proxy to inject the extra content, that way it's centralized.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28719321</id>
	<title>Yo Dawg</title>
	<author>Anonymous</author>
	<datestamp>1247768640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I heard your company likes Wikis so we copied the entirety of Wikipedia onto your web server, so you can wiki while you wiki.</p></htmltext>
<tokenext>I heard your company likes Wikis so we copied the entirety of Wikipedia onto your web server , so you can wiki while you wiki .</tokentext>
<sentencetext>I heard your company likes Wikis so we copied the entirety of Wikipedia onto your web server, so you can wiki while you wiki.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713603</id>
	<title>free legal advice</title>
	<author>Anonymous</author>
	<datestamp>1247776440000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Hi,<br>In this article you can find the aspects relevant to the licence used by Wikipedia and your wish to integrate Wiipedia in your intranet:<br>Can Tpms Create a Commons? Looking at Whether and How Tpms and Creative Commons Licenses Can Work Together.<br>http://papers.ssrn.com/sol3/papers.cfm?abstract\_id=852285<br>Good luck!<br>EH</p></htmltext>
<tokenext>Hi,In this article you can find the aspects relevant to the licence used by Wikipedia and your wish to integrate Wiipedia in your intranet : Can Tpms Create a Commons ?
Looking at Whether and How Tpms and Creative Commons Licenses Can Work Together.http : //papers.ssrn.com/sol3/papers.cfm ? abstract \ _id = 852285Good luck ! EH</tokentext>
<sentencetext>Hi,In this article you can find the aspects relevant to the licence used by Wikipedia and your wish to integrate Wiipedia in your intranet:Can Tpms Create a Commons?
Looking at Whether and How Tpms and Creative Commons Licenses Can Work Together.http://papers.ssrn.com/sol3/papers.cfm?abstract\_id=852285Good luck!EH</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28716191</id>
	<title>Re:bad idea</title>
	<author>fedxone-v86</author>
	<datestamp>1247756700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Also, Firebug is your friend.</p></div><p>Have you just woken up from cryostasis*, too?</p><p>And you know the craziest thing I've heard about Firebug? Allegedly, people also use it to debug web applications written in JavaScript! Applications... On the web... In JavaScript...</p><p>What's next? Apple running on Intel? Bill Gates becoming a humanitarian?</p><p>----</p><p>*) I was frozen just before GWB started WWIII and thawed after the Blacks won<nobr> <wbr></nobr>:D</p><p>**) Thank you, thank you. I'll be here all night.</p></div>
	</htmltext>
<tokenext>Also , Firebug is your friend.Have you just woken up from cryostasis * , too ? And you know the craziest thing I 've heard about Firebug ?
Allegedly , people also use it to debug web applications written in JavaScript !
Applications... On the web... In JavaScript...What 's next ?
Apple running on Intel ?
Bill Gates becoming a humanitarian ? ---- * ) I was frozen just before GWB started WWIII and thawed after the Blacks won : D * * ) Thank you , thank you .
I 'll be here all night .</tokentext>
<sentencetext>Also, Firebug is your friend.Have you just woken up from cryostasis*, too?And you know the craziest thing I've heard about Firebug?
Allegedly, people also use it to debug web applications written in JavaScript!
Applications... On the web... In JavaScript...What's next?
Apple running on Intel?
Bill Gates becoming a humanitarian?----*) I was frozen just before GWB started WWIII and thawed after the Blacks won :D**) Thank you, thank you.
I'll be here all night.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714145</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713539</id>
	<title>Friendly MITM attack</title>
	<author>RiotingPacifist</author>
	<datestamp>1247775600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Sounds like a weird setup, so you'll probably need to do most of it yourself. Perhaps the easiest way is<br>1) setup a normal local wiki, with care to name pages the same as the relevant wikipedia page [I'm guessing you know how to do this]<br>2) use DNS redirects or similar tricks to get all wikipedia requests to go to a proxy<br>3a) do html injection on the page and stick your stuff at the bottom [MITM attack using ettercap or something like that]. This is probably a pretty bad solution, but is going to be the easiest to research as its textbook hacking.<br>3b) host dynamic pages that mash-up the 2 wikis (python,php,something like that). This is probably the closest to the right way to do it, no hmtl injection just a DNS redirect, but will require serverside processing for every.<br>3c) use injection, but only inject a bit of javascript/an iframe that tacks on your wiki stuff at the end (when avalible), This doesn't require much to be done serverside, just inject the same html on all pages.</p><p>Whatever you do you will probably spend more time reading hacking tutorials than wikihowtos</p></htmltext>
<tokenext>Sounds like a weird setup , so you 'll probably need to do most of it yourself .
Perhaps the easiest way is1 ) setup a normal local wiki , with care to name pages the same as the relevant wikipedia page [ I 'm guessing you know how to do this ] 2 ) use DNS redirects or similar tricks to get all wikipedia requests to go to a proxy3a ) do html injection on the page and stick your stuff at the bottom [ MITM attack using ettercap or something like that ] .
This is probably a pretty bad solution , but is going to be the easiest to research as its textbook hacking.3b ) host dynamic pages that mash-up the 2 wikis ( python,php,something like that ) .
This is probably the closest to the right way to do it , no hmtl injection just a DNS redirect , but will require serverside processing for every.3c ) use injection , but only inject a bit of javascript/an iframe that tacks on your wiki stuff at the end ( when avalible ) , This does n't require much to be done serverside , just inject the same html on all pages.Whatever you do you will probably spend more time reading hacking tutorials than wikihowtos</tokentext>
<sentencetext>Sounds like a weird setup, so you'll probably need to do most of it yourself.
Perhaps the easiest way is1) setup a normal local wiki, with care to name pages the same as the relevant wikipedia page [I'm guessing you know how to do this]2) use DNS redirects or similar tricks to get all wikipedia requests to go to a proxy3a) do html injection on the page and stick your stuff at the bottom [MITM attack using ettercap or something like that].
This is probably a pretty bad solution, but is going to be the easiest to research as its textbook hacking.3b) host dynamic pages that mash-up the 2 wikis (python,php,something like that).
This is probably the closest to the right way to do it, no hmtl injection just a DNS redirect, but will require serverside processing for every.3c) use injection, but only inject a bit of javascript/an iframe that tacks on your wiki stuff at the end (when avalible), This doesn't require much to be done serverside, just inject the same html on all pages.Whatever you do you will probably spend more time reading hacking tutorials than wikihowtos</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713437</id>
	<title>IFRAME? Intelligent proxy/page modification?</title>
	<author>seifried</author>
	<datestamp>1247774700000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>I assume you want up to date content and to have it clearly seperated from what is yours. Why not enclose the content within an IFRAME? Seriously, it's stupid and simple but might be all you need. Alternatively you coudl use some form of an intelligent proxy/page modifier, either as a mediawiki plugin or whatever floats your boat (i.e. every time a page is loaded also try to get the wikipedia stuff).</htmltext>
<tokenext>I assume you want up to date content and to have it clearly seperated from what is yours .
Why not enclose the content within an IFRAME ?
Seriously , it 's stupid and simple but might be all you need .
Alternatively you coudl use some form of an intelligent proxy/page modifier , either as a mediawiki plugin or whatever floats your boat ( i.e .
every time a page is loaded also try to get the wikipedia stuff ) .</tokentext>
<sentencetext>I assume you want up to date content and to have it clearly seperated from what is yours.
Why not enclose the content within an IFRAME?
Seriously, it's stupid and simple but might be all you need.
Alternatively you coudl use some form of an intelligent proxy/page modifier, either as a mediawiki plugin or whatever floats your boat (i.e.
every time a page is loaded also try to get the wikipedia stuff).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713397</id>
	<title>Download it</title>
	<author>Anonymous</author>
	<datestamp>1247687820000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>http://en.wikipedia.org/wiki/Wikipedia\_database</p><p>Download their database, put it into your system, and you're set.</p></htmltext>
<tokenext>http : //en.wikipedia.org/wiki/Wikipedia \ _databaseDownload their database , put it into your system , and you 're set .</tokentext>
<sentencetext>http://en.wikipedia.org/wiki/Wikipedia\_databaseDownload their database, put it into your system, and you're set.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713995</id>
	<title>Not without merit.</title>
	<author>asdfndsagse</author>
	<datestamp>1247737920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is something the <a href="http://www.youtube.com/watch?v=v\_UyVmITiYQ" title="youtube.com" rel="nofollow">Google Wave protocol and platform</a> [youtube.com] completely anticipates.</p><p>Its based on a tree structure and source code management. People who edit from the synergized wiki could add to either the private or public versions, and patches to public versions or additional documents could be changed and maintained internally.</p></htmltext>
<tokenext>This is something the Google Wave protocol and platform [ youtube.com ] completely anticipates.Its based on a tree structure and source code management .
People who edit from the synergized wiki could add to either the private or public versions , and patches to public versions or additional documents could be changed and maintained internally .</tokentext>
<sentencetext>This is something the Google Wave protocol and platform [youtube.com] completely anticipates.Its based on a tree structure and source code management.
People who edit from the synergized wiki could add to either the private or public versions, and patches to public versions or additional documents could be changed and maintained internally.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714727</id>
	<title>WikiSlurp...</title>
	<author>bagsta</author>
	<datestamp>1247747460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Accidentally I saw this <a href="http://thecodetrain.co.uk/code/wikislurp/" title="thecodetrain.co.uk" rel="nofollow">site</a> [thecodetrain.co.uk]. I haven't tested and I don't know the results. I think it's in the early stages of development.</htmltext>
<tokenext>Accidentally I saw this site [ thecodetrain.co.uk ] .
I have n't tested and I do n't know the results .
I think it 's in the early stages of development .</tokentext>
<sentencetext>Accidentally I saw this site [thecodetrain.co.uk].
I haven't tested and I don't know the results.
I think it's in the early stages of development.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713785</id>
	<title>Maybe...</title>
	<author>denmarkw00t</author>
	<datestamp>1247734980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Open page in intranet for...say, capcitor.</p><p>Script grabs wikipedia article, strips out header, sidebar, etc and fill in remaining links/images with proper URLs to wikipedia (so they work)</p><p>Stores in a database for diff'ing and updating later, dumps remaining content from Wikipedia at the bottom with a good 'ol &lt;hr&gt; and you're off!</p></htmltext>
<tokenext>Open page in intranet for...say , capcitor.Script grabs wikipedia article , strips out header , sidebar , etc and fill in remaining links/images with proper URLs to wikipedia ( so they work ) Stores in a database for diff'ing and updating later , dumps remaining content from Wikipedia at the bottom with a good 'ol and you 're off !</tokentext>
<sentencetext>Open page in intranet for...say, capcitor.Script grabs wikipedia article, strips out header, sidebar, etc and fill in remaining links/images with proper URLs to wikipedia (so they work)Stores in a database for diff'ing and updating later, dumps remaining content from Wikipedia at the bottom with a good 'ol  and you're off!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714035</id>
	<title>Re:Business Talk is Stupid Talk</title>
	<author>Anonymous</author>
	<datestamp>1247738280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><blockquote><div><p>if you are augmenting your internal wiki with external wikis, you are leveraging your internal wiki with the external wikis. You leverage a boulder with a lever, but you don't leverage a lever with a boulder.</p></div></blockquote><p>
Wow, you totally shifted my paradigm.</p></div>
	</htmltext>
<tokenext>if you are augmenting your internal wiki with external wikis , you are leveraging your internal wiki with the external wikis .
You leverage a boulder with a lever , but you do n't leverage a lever with a boulder .
Wow , you totally shifted my paradigm .</tokentext>
<sentencetext>if you are augmenting your internal wiki with external wikis, you are leveraging your internal wiki with the external wikis.
You leverage a boulder with a lever, but you don't leverage a lever with a boulder.
Wow, you totally shifted my paradigm.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714343</id>
	<title>Done this before</title>
	<author>MarkH</author>
	<datestamp>1247742360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>1) Install Wikipedia software locally and use this for any locally created articles</p><p>2) The web server running this simply proxies out to en.wikipedia.org for that request if not available in the local version. The easiest way to do this is with Apache + rewrite rules</p><p>This means that users can get to articles locally and on wikipedia from the same command</p><p>You then need to consider the following</p><p>1) The search request needs to go to the local version of wikipedia then the external one and concatinate the results together - a small proxy script should be more than capable of doing this</p><p>2) You may want to create a reference table which maps external wiki articles to related internal ones. Again a small script could insert these into the external wikipedia articles during rendering</p></htmltext>
<tokenext>1 ) Install Wikipedia software locally and use this for any locally created articles2 ) The web server running this simply proxies out to en.wikipedia.org for that request if not available in the local version .
The easiest way to do this is with Apache + rewrite rulesThis means that users can get to articles locally and on wikipedia from the same commandYou then need to consider the following1 ) The search request needs to go to the local version of wikipedia then the external one and concatinate the results together - a small proxy script should be more than capable of doing this2 ) You may want to create a reference table which maps external wiki articles to related internal ones .
Again a small script could insert these into the external wikipedia articles during rendering</tokentext>
<sentencetext>1) Install Wikipedia software locally and use this for any locally created articles2) The web server running this simply proxies out to en.wikipedia.org for that request if not available in the local version.
The easiest way to do this is with Apache + rewrite rulesThis means that users can get to articles locally and on wikipedia from the same commandYou then need to consider the following1) The search request needs to go to the local version of wikipedia then the external one and concatinate the results together - a small proxy script should be more than capable of doing this2) You may want to create a reference table which maps external wiki articles to related internal ones.
Again a small script could insert these into the external wikipedia articles during rendering</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714479</id>
	<title>There's lots of value in a compound wiki</title>
	<author>davide marney</author>
	<datestamp>1247743920000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>Ignore the nay sayers. <i>Of course</i> there is a lot of value in aggregating content and creating a compound page that blends your internal content with other sources.</p><p>From a usuability and authority-of-source perspective, however, I think it would be best to list each source in a separate section on the page, starting with your internal content at the top. You can get to the other content either by embedding links into your internal content, or by collecting the links in a separate section.</p><p>Wikipedia itself uses the embedded technique. When composing or editing an article, the author can embed markup for external references. On display, this markup is turned into a footnote link at the point of embedding, and a footnote at the bottom of the page.  I don't see why you couldn't do something similar.  In this case, however, you would be embedding references to <i>Wikipedia articles</i>.</p><p>I don't see why you couldn't do something similar. In your internal wiki templates, have a custom markup for embedding wikipedia queries related to the article. On display, turn this markup queries either into embedded links to footnotes, resolve the queries and deposit them at the bottom of the page, or toss them into iframes and let the user sort it out.</p><p>The other technique is to have a custom form in your internal wiki template where you collect the cross-references.  On display, turn these queries into links or resolve them into content.</p><p>In any event, why limit yourself to Wikipedia? Include cross-references to patent search engines and other domain-specific sources.</p><p>A big word of caution, of course, is owed to the legal angle. Make sure you follow the law whenever reusing anyone else's content, even if it's just a link. Have your legal department sign off on your reuse policy. Don't distract them with technical aspects of what you want to do. They're lawyers; they only care about the law. Ask them a specific legal question, such as, "what is our legal exposure if we republish (links to or actual content from) Wikipedia on our internal wiki?".</p></htmltext>
<tokenext>Ignore the nay sayers .
Of course there is a lot of value in aggregating content and creating a compound page that blends your internal content with other sources.From a usuability and authority-of-source perspective , however , I think it would be best to list each source in a separate section on the page , starting with your internal content at the top .
You can get to the other content either by embedding links into your internal content , or by collecting the links in a separate section.Wikipedia itself uses the embedded technique .
When composing or editing an article , the author can embed markup for external references .
On display , this markup is turned into a footnote link at the point of embedding , and a footnote at the bottom of the page .
I do n't see why you could n't do something similar .
In this case , however , you would be embedding references to Wikipedia articles.I do n't see why you could n't do something similar .
In your internal wiki templates , have a custom markup for embedding wikipedia queries related to the article .
On display , turn this markup queries either into embedded links to footnotes , resolve the queries and deposit them at the bottom of the page , or toss them into iframes and let the user sort it out.The other technique is to have a custom form in your internal wiki template where you collect the cross-references .
On display , turn these queries into links or resolve them into content.In any event , why limit yourself to Wikipedia ?
Include cross-references to patent search engines and other domain-specific sources.A big word of caution , of course , is owed to the legal angle .
Make sure you follow the law whenever reusing anyone else 's content , even if it 's just a link .
Have your legal department sign off on your reuse policy .
Do n't distract them with technical aspects of what you want to do .
They 're lawyers ; they only care about the law .
Ask them a specific legal question , such as , " what is our legal exposure if we republish ( links to or actual content from ) Wikipedia on our internal wiki ?
" .</tokentext>
<sentencetext>Ignore the nay sayers.
Of course there is a lot of value in aggregating content and creating a compound page that blends your internal content with other sources.From a usuability and authority-of-source perspective, however, I think it would be best to list each source in a separate section on the page, starting with your internal content at the top.
You can get to the other content either by embedding links into your internal content, or by collecting the links in a separate section.Wikipedia itself uses the embedded technique.
When composing or editing an article, the author can embed markup for external references.
On display, this markup is turned into a footnote link at the point of embedding, and a footnote at the bottom of the page.
I don't see why you couldn't do something similar.
In this case, however, you would be embedding references to Wikipedia articles.I don't see why you couldn't do something similar.
In your internal wiki templates, have a custom markup for embedding wikipedia queries related to the article.
On display, turn this markup queries either into embedded links to footnotes, resolve the queries and deposit them at the bottom of the page, or toss them into iframes and let the user sort it out.The other technique is to have a custom form in your internal wiki template where you collect the cross-references.
On display, turn these queries into links or resolve them into content.In any event, why limit yourself to Wikipedia?
Include cross-references to patent search engines and other domain-specific sources.A big word of caution, of course, is owed to the legal angle.
Make sure you follow the law whenever reusing anyone else's content, even if it's just a link.
Have your legal department sign off on your reuse policy.
Don't distract them with technical aspects of what you want to do.
They're lawyers; they only care about the law.
Ask them a specific legal question, such as, "what is our legal exposure if we republish (links to or actual content from) Wikipedia on our internal wiki?
".</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713897</id>
	<title>Simple. Two Tabs</title>
	<author>Phoe6</author>
	<datestamp>1247736720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>One Tab for your Internal Wiki. Another one for wikipedia.<br>You can also highlight a particular word in your internal wiki, do a right click and search wikipedia (if your search is set so). The search term automatically open the wikipedia content in a new tab. How amazing. Isn't it?</p><p> <i> Is it only me wondering how did this article ever made it to<nobr> <wbr></nobr>/. ?</i> </p></htmltext>
<tokenext>One Tab for your Internal Wiki .
Another one for wikipedia.You can also highlight a particular word in your internal wiki , do a right click and search wikipedia ( if your search is set so ) .
The search term automatically open the wikipedia content in a new tab .
How amazing .
Is n't it ?
Is it only me wondering how did this article ever made it to / .
?</tokentext>
<sentencetext>One Tab for your Internal Wiki.
Another one for wikipedia.You can also highlight a particular word in your internal wiki, do a right click and search wikipedia (if your search is set so).
The search term automatically open the wikipedia content in a new tab.
How amazing.
Isn't it?
Is it only me wondering how did this article ever made it to /.
? </sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713731</id>
	<title>Legitimate use for this hack</title>
	<author>biduxe</author>
	<datestamp>1247777520000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Am I the only one which cannot see any legitimate uses for this hack.</p><p>Why lure your users into thinking the content is on wikipedia if it is on your network?<br>Can't your users use wikipedia \_and\_ your wiki.</p><p>Sincerely I think that the goal for this hack is luring users to think they're reading/editing wikipedia for someone's profit.</p></htmltext>
<tokenext>Am I the only one which can not see any legitimate uses for this hack.Why lure your users into thinking the content is on wikipedia if it is on your network ? Ca n't your users use wikipedia \ _and \ _ your wiki.Sincerely I think that the goal for this hack is luring users to think they 're reading/editing wikipedia for someone 's profit .</tokentext>
<sentencetext>Am I the only one which cannot see any legitimate uses for this hack.Why lure your users into thinking the content is on wikipedia if it is on your network?Can't your users use wikipedia \_and\_ your wiki.Sincerely I think that the goal for this hack is luring users to think they're reading/editing wikipedia for someone's profit.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713381</id>
	<title>redirect wikipedia traffic to an internal web app</title>
	<author>Anonymous</author>
	<datestamp>1247687700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Build a web application to merge wikipedia content with internal content (iframes maybe).<br>Then setup a DNS alias to redirect the wikipedia traffic to this web app.</p></htmltext>
<tokenext>Build a web application to merge wikipedia content with internal content ( iframes maybe ) .Then setup a DNS alias to redirect the wikipedia traffic to this web app .</tokentext>
<sentencetext>Build a web application to merge wikipedia content with internal content (iframes maybe).Then setup a DNS alias to redirect the wikipedia traffic to this web app.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713531</id>
	<title>Browser overlay</title>
	<author>Phroggy</author>
	<datestamp>1247775540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It seems to me I've seen a browser extension somewhere that lets users add their own comments to any arbitrary web page, and those comments can be made public so anyone else running the same browser extension will see them when they load the same page.  I bet you could use something like that, with all your users having a browser plugin that pulls URL-based content from an internal server.</p></htmltext>
<tokenext>It seems to me I 've seen a browser extension somewhere that lets users add their own comments to any arbitrary web page , and those comments can be made public so anyone else running the same browser extension will see them when they load the same page .
I bet you could use something like that , with all your users having a browser plugin that pulls URL-based content from an internal server .</tokentext>
<sentencetext>It seems to me I've seen a browser extension somewhere that lets users add their own comments to any arbitrary web page, and those comments can be made public so anyone else running the same browser extension will see them when they load the same page.
I bet you could use something like that, with all your users having a browser plugin that pulls URL-based content from an internal server.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714287</id>
	<title>Freebase.com</title>
	<author>TwistedPants</author>
	<datestamp>1247741580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Go and look at Freebase:

<a href="http://www.freebase.com/" title="freebase.com" rel="nofollow">http://www.freebase.com/</a> [freebase.com] <br>


They provide an API to obtain articles and structured data from them. They handle all of the wikipedia import.<br>

Additionally, you can do much more with the structured data there<br>

For instance - Olympic Cyclists and the Way They Died.<br>
<a href="http://www.freebase.com/view/user/doconnor/default\_domain/views/olympic\_cyclists\_and\_they\_way\_they\_died" title="freebase.com" rel="nofollow">http://www.freebase.com/view/user/doconnor/default\_domain/views/olympic\_cyclists\_and\_they\_way\_they\_died</a> [freebase.com]

Try doing that with Wikipedia.</htmltext>
<tokenext>Go and look at Freebase : http : //www.freebase.com/ [ freebase.com ] They provide an API to obtain articles and structured data from them .
They handle all of the wikipedia import .
Additionally , you can do much more with the structured data there For instance - Olympic Cyclists and the Way They Died .
http : //www.freebase.com/view/user/doconnor/default \ _domain/views/olympic \ _cyclists \ _and \ _they \ _way \ _they \ _died [ freebase.com ] Try doing that with Wikipedia .</tokentext>
<sentencetext>Go and look at Freebase:

http://www.freebase.com/ [freebase.com] 


They provide an API to obtain articles and structured data from them.
They handle all of the wikipedia import.
Additionally, you can do much more with the structured data there

For instance - Olympic Cyclists and the Way They Died.
http://www.freebase.com/view/user/doconnor/default\_domain/views/olympic\_cyclists\_and\_they\_way\_they\_died [freebase.com]

Try doing that with Wikipedia.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715273</id>
	<title>Re:bad idea</title>
	<author>uepuejq</author>
	<datestamp>1247752020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>i think you really get into too much development and design effort when such a simple task can be accomplished by using resources that are already available.  wikipedia already exists, and they already have servers to handle the search requests.  i still say developing a small application (whether it's some javascript, a new add-on, or something that already exists) to add links to wikipedia entries that have alternate internal wiki entries, since according to the parent question the employees are going to be using wikipedia a lot, anyway.  you can make the link apparent so that employees can simply take a quick glance to see whether they need to do any more internal research.  you don't have to waste time downloading, restoring, and implementing the wikipedia database internally, and you don't have to waste time updating it, writing scripts to do so automatically, or finding scripts that will.<br> <br>

as to the api approach, i think that would be fun, but it seems like a waste of server power to have a machine dedicated to doing something that could be done on client computers dynamically with a relatively minute bit of javascript, and would be just as functional and ultimately less effort to upkeep.  for future changes to the api you may have to alter your entire application, but if wikipedia just changes the html layout all you have to do is modify a regular expression and the rest of the code is still usable.</htmltext>
<tokenext>i think you really get into too much development and design effort when such a simple task can be accomplished by using resources that are already available .
wikipedia already exists , and they already have servers to handle the search requests .
i still say developing a small application ( whether it 's some javascript , a new add-on , or something that already exists ) to add links to wikipedia entries that have alternate internal wiki entries , since according to the parent question the employees are going to be using wikipedia a lot , anyway .
you can make the link apparent so that employees can simply take a quick glance to see whether they need to do any more internal research .
you do n't have to waste time downloading , restoring , and implementing the wikipedia database internally , and you do n't have to waste time updating it , writing scripts to do so automatically , or finding scripts that will .
as to the api approach , i think that would be fun , but it seems like a waste of server power to have a machine dedicated to doing something that could be done on client computers dynamically with a relatively minute bit of javascript , and would be just as functional and ultimately less effort to upkeep .
for future changes to the api you may have to alter your entire application , but if wikipedia just changes the html layout all you have to do is modify a regular expression and the rest of the code is still usable .</tokentext>
<sentencetext>i think you really get into too much development and design effort when such a simple task can be accomplished by using resources that are already available.
wikipedia already exists, and they already have servers to handle the search requests.
i still say developing a small application (whether it's some javascript, a new add-on, or something that already exists) to add links to wikipedia entries that have alternate internal wiki entries, since according to the parent question the employees are going to be using wikipedia a lot, anyway.
you can make the link apparent so that employees can simply take a quick glance to see whether they need to do any more internal research.
you don't have to waste time downloading, restoring, and implementing the wikipedia database internally, and you don't have to waste time updating it, writing scripts to do so automatically, or finding scripts that will.
as to the api approach, i think that would be fun, but it seems like a waste of server power to have a machine dedicated to doing something that could be done on client computers dynamically with a relatively minute bit of javascript, and would be just as functional and ultimately less effort to upkeep.
for future changes to the api you may have to alter your entire application, but if wikipedia just changes the html layout all you have to do is modify a regular expression and the rest of the code is still usable.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714439</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714619</id>
	<title>Re:Business Talk is Stupid Talk</title>
	<author>Anonymous</author>
	<datestamp>1247745960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>What does that even mean?</p></div><p>That he's a dickhead?  I think that he communicated that quite effectively.</p></div>
	</htmltext>
<tokenext>What does that even mean ? That he 's a dickhead ?
I think that he communicated that quite effectively .</tokentext>
<sentencetext>What does that even mean?That he's a dickhead?
I think that he communicated that quite effectively.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713657</id>
	<title>google wave</title>
	<author>linhares</author>
	<datestamp>1247776920000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext>sorry folks, it's all over and google has won.

Google wave, coupled with an internal dump of wikipedia, seems to me perfect for your needs.

<p>watch 1.20hs here and <a href="http://wave.google.com/" title="google.com">see for yourself</a> [google.com].  This monster will change email, chat, wikis and forums.  I'd be worried if I was a slashdot overlord.  In fact, an idea for an extension to google wave would be to implement slashdot's moderation system into it.  </p><p>Maybe I drank too much of the kool-aid, but I think wikis and forums will all have to rapidly adapt, or adopt the coming plague from Mountain View.</p></htmltext>
<tokenext>sorry folks , it 's all over and google has won .
Google wave , coupled with an internal dump of wikipedia , seems to me perfect for your needs .
watch 1.20hs here and see for yourself [ google.com ] .
This monster will change email , chat , wikis and forums .
I 'd be worried if I was a slashdot overlord .
In fact , an idea for an extension to google wave would be to implement slashdot 's moderation system into it .
Maybe I drank too much of the kool-aid , but I think wikis and forums will all have to rapidly adapt , or adopt the coming plague from Mountain View .</tokentext>
<sentencetext>sorry folks, it's all over and google has won.
Google wave, coupled with an internal dump of wikipedia, seems to me perfect for your needs.
watch 1.20hs here and see for yourself [google.com].
This monster will change email, chat, wikis and forums.
I'd be worried if I was a slashdot overlord.
In fact, an idea for an extension to google wave would be to implement slashdot's moderation system into it.
Maybe I drank too much of the kool-aid, but I think wikis and forums will all have to rapidly adapt, or adopt the coming plague from Mountain View.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713915</id>
	<title>Re:URLs</title>
	<author>Anonymous</author>
	<datestamp>1247736960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>chinga tu madre</p></htmltext>
<tokenext>chinga tu madre</tokentext>
<sentencetext>chinga tu madre</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713331</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713705</id>
	<title>Re:URLs</title>
	<author>smallfries</author>
	<datestamp>1247777340000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Noise.</p><p>It's a good place to bury the signal.</p></htmltext>
<tokenext>Noise.It 's a good place to bury the signal .</tokentext>
<sentencetext>Noise.It's a good place to bury the signal.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713331</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713817</id>
	<title>CMS Federated Search</title>
	<author>Anonymous</author>
	<datestamp>1247735460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Nowadays, any content management system worth anything has a built-in wiki and most allow direct linking and searching between the local wiki and wikipedia.</p><p>For example <a href="http://www.emc.com/products/documentum-platform/federated-search-adapter-library.htm" title="emc.com" rel="nofollow">Documentum</a> [emc.com] and <a href="http://technet.microsoft.com/en-us/library/cc788935.aspx" title="microsoft.com" rel="nofollow">Sharepoint</a> [microsoft.com] both have <a href="http://en.wikipedia.org/wiki/Federated\_search" title="wikipedia.org" rel="nofollow">federated search</a> [wikipedia.org] providers for Wikipedia.</p><p>Plus, because the OP works for a "large company" they probably already have DCTM or MOSS installed somewhere.<br>Why reinvent the wheel when you've already bought a better one? (job security?)</p></htmltext>
<tokenext>Nowadays , any content management system worth anything has a built-in wiki and most allow direct linking and searching between the local wiki and wikipedia.For example Documentum [ emc.com ] and Sharepoint [ microsoft.com ] both have federated search [ wikipedia.org ] providers for Wikipedia.Plus , because the OP works for a " large company " they probably already have DCTM or MOSS installed somewhere.Why reinvent the wheel when you 've already bought a better one ?
( job security ?
)</tokentext>
<sentencetext>Nowadays, any content management system worth anything has a built-in wiki and most allow direct linking and searching between the local wiki and wikipedia.For example Documentum [emc.com] and Sharepoint [microsoft.com] both have federated search [wikipedia.org] providers for Wikipedia.Plus, because the OP works for a "large company" they probably already have DCTM or MOSS installed somewhere.Why reinvent the wheel when you've already bought a better one?
(job security?
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28722629</id>
	<title>Enterprise wiki</title>
	<author>Anonymous</author>
	<datestamp>1247738220000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>We started using Atlassian Confluence a year ago, and I am so pleased with this product. We are currently ~100 users contributing and using it on a standalone server internally with SSO for Windows domain. You should seriously consider this wiki, because it beats everything I have seen.</p></htmltext>
<tokenext>We started using Atlassian Confluence a year ago , and I am so pleased with this product .
We are currently ~ 100 users contributing and using it on a standalone server internally with SSO for Windows domain .
You should seriously consider this wiki , because it beats everything I have seen .</tokentext>
<sentencetext>We started using Atlassian Confluence a year ago, and I am so pleased with this product.
We are currently ~100 users contributing and using it on a standalone server internally with SSO for Windows domain.
You should seriously consider this wiki, because it beats everything I have seen.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713405</id>
	<title>intrawiki</title>
	<author>Anonymous</author>
	<datestamp>1247687880000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext><p>you fucking dolt</p></htmltext>
<tokenext>you fucking dolt</tokentext>
<sentencetext>you fucking dolt</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28718983</id>
	<title>MediaWiki interwiki links</title>
	<author>BitZtream</author>
	<datestamp>1247767260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Use interwiki links.   I use them to link our intranet, mediawiki, our external developer wiki, and our external support wiki.</p><p>You will probably be unable to use them since using them requires the ability to get off your lazy ass and read the MediaWiki documentation or google for it, which results in plenty of information.</p><p>Also the fact that you're going to have to be able to insert a row in a database is probably going to be over your head.</p><p>READ THE DOCUMENTATION YOU LAZY FUCK.</p></htmltext>
<tokenext>Use interwiki links .
I use them to link our intranet , mediawiki , our external developer wiki , and our external support wiki.You will probably be unable to use them since using them requires the ability to get off your lazy ass and read the MediaWiki documentation or google for it , which results in plenty of information.Also the fact that you 're going to have to be able to insert a row in a database is probably going to be over your head.READ THE DOCUMENTATION YOU LAZY FUCK .</tokentext>
<sentencetext>Use interwiki links.
I use them to link our intranet, mediawiki, our external developer wiki, and our external support wiki.You will probably be unable to use them since using them requires the ability to get off your lazy ass and read the MediaWiki documentation or google for it, which results in plenty of information.Also the fact that you're going to have to be able to insert a row in a database is probably going to be over your head.READ THE DOCUMENTATION YOU LAZY FUCK.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28725043</id>
	<title>Re:bad idea</title>
	<author>JuzzFunky</author>
	<datestamp>1247752080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Check out the <a href="http://www.mediawiki.org/wiki/API" title="mediawiki.org" rel="nofollow"> Media Wiki API</a> [mediawiki.org] <br>
Here's a detailed howto on creating a <a href="http://en.wikipedia.org/wiki/Wikipedia:Creating\_a\_bot" title="wikipedia.org" rel="nofollow">Bot</a> [wikipedia.org].</htmltext>
<tokenext>Check out the Media Wiki API [ mediawiki.org ] Here 's a detailed howto on creating a Bot [ wikipedia.org ] .</tokentext>
<sentencetext>Check out the  Media Wiki API [mediawiki.org] 
Here's a detailed howto on creating a Bot [wikipedia.org].</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714439</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28726937</id>
	<title>Re:Solution</title>
	<author>ibbey</author>
	<datestamp>1247821560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I guess I don't see the problem... I'm a lousy programmer, and I could work up a proof-of-concept for this in about 10 minutes in PHP. Put your internal information in one frame and the Wikipedia information in another. Simply load the data from Wikipedia, either using the Wikipedia API, or just put the wikipedia page in a frame. This is not really any different than about a million other websites that aggregate information from multiple sources. This doesn't actually integrate the data (for example inserting internal links in the Wikipedia content), but that could be done easily enough in the PHP script (or whatever) if you really wanted to.</p></htmltext>
<tokenext>I guess I do n't see the problem... I 'm a lousy programmer , and I could work up a proof-of-concept for this in about 10 minutes in PHP .
Put your internal information in one frame and the Wikipedia information in another .
Simply load the data from Wikipedia , either using the Wikipedia API , or just put the wikipedia page in a frame .
This is not really any different than about a million other websites that aggregate information from multiple sources .
This does n't actually integrate the data ( for example inserting internal links in the Wikipedia content ) , but that could be done easily enough in the PHP script ( or whatever ) if you really wanted to .</tokentext>
<sentencetext>I guess I don't see the problem... I'm a lousy programmer, and I could work up a proof-of-concept for this in about 10 minutes in PHP.
Put your internal information in one frame and the Wikipedia information in another.
Simply load the data from Wikipedia, either using the Wikipedia API, or just put the wikipedia page in a frame.
This is not really any different than about a million other websites that aggregate information from multiple sources.
This doesn't actually integrate the data (for example inserting internal links in the Wikipedia content), but that could be done easily enough in the PHP script (or whatever) if you really wanted to.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28716329</id>
	<title>Try the other way round</title>
	<author>RogL</author>
	<datestamp>1247757420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Why not try the other way round:</p><p>Create your wiki, add pages, add links from your wiki pages (which you have full control over) to relevant wikipedia pages?</p><p>Much simpler, and should still produce the desired effect.</p></htmltext>
<tokenext>Why not try the other way round : Create your wiki , add pages , add links from your wiki pages ( which you have full control over ) to relevant wikipedia pages ? Much simpler , and should still produce the desired effect .</tokentext>
<sentencetext>Why not try the other way round:Create your wiki, add pages, add links from your wiki pages (which you have full control over) to relevant wikipedia pages?Much simpler, and should still produce the desired effect.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28722353</id>
	<title>IFrame + JavaScript = robust and simple</title>
	<author>thasmudyan</author>
	<datestamp>1247737020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If Wikipedia is indeed a good base for a lot of your company knowledge, you can do something dead simple: build a single PHP (or whatever language you prefer) page with an IFrame in it. Inside the IFrame you let users browse Wikipedia or any other web resource. Outside, in the parent document, there is a script that looks at the current IFrame URL and checks a local database for additional information. This could be additional text or even a stream of internal comments on this URL.

The beauty of this idea is that you don't need a local copy of WP, and you don't need any HTML scraping. And it'll work with other only resources besides Wikipedia as well. You make the URL the reference point for the internal database lookup and you're done. It also has the benefit that your users will be able to easily distinguish between public and proprietary content on the page, because those two will be clearly separated.

And, you can set this up within a few hours.</htmltext>
<tokenext>If Wikipedia is indeed a good base for a lot of your company knowledge , you can do something dead simple : build a single PHP ( or whatever language you prefer ) page with an IFrame in it .
Inside the IFrame you let users browse Wikipedia or any other web resource .
Outside , in the parent document , there is a script that looks at the current IFrame URL and checks a local database for additional information .
This could be additional text or even a stream of internal comments on this URL .
The beauty of this idea is that you do n't need a local copy of WP , and you do n't need any HTML scraping .
And it 'll work with other only resources besides Wikipedia as well .
You make the URL the reference point for the internal database lookup and you 're done .
It also has the benefit that your users will be able to easily distinguish between public and proprietary content on the page , because those two will be clearly separated .
And , you can set this up within a few hours .</tokentext>
<sentencetext>If Wikipedia is indeed a good base for a lot of your company knowledge, you can do something dead simple: build a single PHP (or whatever language you prefer) page with an IFrame in it.
Inside the IFrame you let users browse Wikipedia or any other web resource.
Outside, in the parent document, there is a script that looks at the current IFrame URL and checks a local database for additional information.
This could be additional text or even a stream of internal comments on this URL.
The beauty of this idea is that you don't need a local copy of WP, and you don't need any HTML scraping.
And it'll work with other only resources besides Wikipedia as well.
You make the URL the reference point for the internal database lookup and you're done.
It also has the benefit that your users will be able to easily distinguish between public and proprietary content on the page, because those two will be clearly separated.
And, you can set this up within a few hours.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713861</id>
	<title>Two approaches - browser extension or proxy</title>
	<author>Anonymous</author>
	<datestamp>1247736240000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>With a browser extension (probably relatively easy with Firefox or Opera), you can modify HTML DOM and include an iFrame with company specific information.  This should probably be unobtrusive on the Wikipedia page, but it should be clearly marked as internal to your company.. users aren't always the brightest, and there's always the possibility of them editing the Wikipedia page itself to correct local content which should never be published on the Internet.  It might also be possible to force the Wikipedia page into an Frame, and have company content clearly identifiable in another frame.</p><p>With a proxy, you would add some Javascript near the end of the HTML page, which does pretty much the same thing.. you will be limited to the security settings of the browser, though..</p><p>Also interesting are the extensions allowing you to comment on any public webpage, and share those comments with other people.  Most of these use a public server, but you could probably modify an existing firefox extension to talk to a local server (which you then need to script).  I think there's even an open protocol for this.</p><p>Of course, if you're going the browser extension path with Firefox, why modify the HTML at all?  Modify the user interface, so that the company's wiki becomes part of the browser?  Somebody has a site they want to bookmark for the wiki?  Have a button for it.  They want to create a new topic, based around this page's content?  Have a button for it?  They want to see all related internal pages, have a sidebar which updates with info from the local server.  Standardising on Firefox in an organisation isn't a bad idea at all, especially if you can bring such benefits to the company.<nobr> <wbr></nobr>:-)</p></htmltext>
<tokenext>With a browser extension ( probably relatively easy with Firefox or Opera ) , you can modify HTML DOM and include an iFrame with company specific information .
This should probably be unobtrusive on the Wikipedia page , but it should be clearly marked as internal to your company.. users are n't always the brightest , and there 's always the possibility of them editing the Wikipedia page itself to correct local content which should never be published on the Internet .
It might also be possible to force the Wikipedia page into an Frame , and have company content clearly identifiable in another frame.With a proxy , you would add some Javascript near the end of the HTML page , which does pretty much the same thing.. you will be limited to the security settings of the browser , though..Also interesting are the extensions allowing you to comment on any public webpage , and share those comments with other people .
Most of these use a public server , but you could probably modify an existing firefox extension to talk to a local server ( which you then need to script ) .
I think there 's even an open protocol for this.Of course , if you 're going the browser extension path with Firefox , why modify the HTML at all ?
Modify the user interface , so that the company 's wiki becomes part of the browser ?
Somebody has a site they want to bookmark for the wiki ?
Have a button for it .
They want to create a new topic , based around this page 's content ?
Have a button for it ?
They want to see all related internal pages , have a sidebar which updates with info from the local server .
Standardising on Firefox in an organisation is n't a bad idea at all , especially if you can bring such benefits to the company .
: - )</tokentext>
<sentencetext>With a browser extension (probably relatively easy with Firefox or Opera), you can modify HTML DOM and include an iFrame with company specific information.
This should probably be unobtrusive on the Wikipedia page, but it should be clearly marked as internal to your company.. users aren't always the brightest, and there's always the possibility of them editing the Wikipedia page itself to correct local content which should never be published on the Internet.
It might also be possible to force the Wikipedia page into an Frame, and have company content clearly identifiable in another frame.With a proxy, you would add some Javascript near the end of the HTML page, which does pretty much the same thing.. you will be limited to the security settings of the browser, though..Also interesting are the extensions allowing you to comment on any public webpage, and share those comments with other people.
Most of these use a public server, but you could probably modify an existing firefox extension to talk to a local server (which you then need to script).
I think there's even an open protocol for this.Of course, if you're going the browser extension path with Firefox, why modify the HTML at all?
Modify the user interface, so that the company's wiki becomes part of the browser?
Somebody has a site they want to bookmark for the wiki?
Have a button for it.
They want to create a new topic, based around this page's content?
Have a button for it?
They want to see all related internal pages, have a sidebar which updates with info from the local server.
Standardising on Firefox in an organisation isn't a bad idea at all, especially if you can bring such benefits to the company.
:-)</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714619
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28726937
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713563
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713399
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28717021
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713675
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28716191
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714145
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713343
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715581
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714319
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714035
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713847
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713619
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28718585
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714665
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28725043
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714439
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714145
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713343
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714379
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715273
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714439
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714145
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713343
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713915
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713331
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713991
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713331
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713857
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713675
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28723675
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715755
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713331
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713705
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713331
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713491
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713343
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714679
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_07_15_2252249_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714413
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713397
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713399
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713563
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28726937
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713619
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713847
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713675
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713857
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28717021
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713343
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713491
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714145
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714439
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28725043
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715273
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28716191
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713475
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714035
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714379
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714679
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714665
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714619
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715581
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714319
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28718585
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713657
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713331
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713915
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28715755
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28723675
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713705
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713991
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713539
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713437
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713995
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713613
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713731
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_07_15_2252249.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28713397
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_07_15_2252249.28714413
</commentlist>
</conversation>
