Community:Proliferation of URIs, Managing Coreference - Revision history

MichaelUschold at 22:02, 13 April 2010

2010-04-13T22:02:45Z

2010-04-13T21:06:38Z

2010-04-13T01:37:43Z

2010-04-12T21:22:34Z

2010-04-12T01:57:46Z

2010-04-12T01:56:18Z

2010-04-12T01:44:23Z

2010-04-12T01:43:30Z

2010-04-12T01:42:01Z

2010-04-12T01:40:20Z

← Older revision		Revision as of 22:02, 13 April 2010
Line 33:		Line 33:
	# that these issues are arising at all can be seen as a good thing, insofar as it reflects that linked data is being made available and put to real use. Tim Berners-Lee notes that: "Life is, on balance, good."		# that these issues are arising at all can be seen as a good thing, insofar as it reflects that linked data is being made available and put to real use. Tim Berners-Lee notes that: "Life is, on balance, good."

		+	{{Semantic Elephant Text}}

	==Original Post==		==Original Post==

@@ Line 9: / Line 9: @@
 }}
 {{Additional information header}}
 ''Issue'': How to avoid or manage two negative consequences to the current proliferation of new URIs being minted for the same things. Specifically:
 # it is hard to find when two things should be the same
@@ Line 33: / Line 34: @@
-'''Original Post'''
+==Original Post==
 Here is the original Post by Michael Uschold in May 2008:
@@ Line 75: / Line 76: @@
-'''Summary of Responses'''
+==Summary of Responses==
 ''Chris Bizer:''

@@ Line 15: / Line 15: @@
 ''Source:'' This discussion is taken from a thread called [http://lists.w3.org/Archives/Public/semantic-web/2008May/0081.html Managing Co-reference (Was: A Semantic Elephant?)] on the [http://lists.w3.org/Archives/Public/semantic-web/ W3C Semantic Web Discussion List]. A vigorous discussion initially took place off the list, and then was moved to the list for the record.
-''Related Discussions'':
+''Related Discussions'': [http://lists.w3.org/Archives/Public/semantic-web/2008Oct/0192.html URIs and Unique IDs]
 ''Related Modeling Issues:''

@@ Line 17: / Line 17: @@
 ''Related Discussions'':
-''Related Modeling Issues:'' [[Community:Overloading OWL sameAs]]
+''Related Modeling Issues:''
 ''Example(s)''

@@ Line 28: / Line 28: @@
 # large scale duplication of URIs as in the case of YAGO and DBpedia, is unfortunate, but has now largely been rectified. That it happened at all is due to this all being very new.
 # it was argued that it does not matter much because noone is going to load all the triples into a one triple store. A counter argument to this is that even if you load a lot of triples into one store, the problem of inefficiency of sameAs reasoning can arise.
-# that these issues are arising at all can be seen as a good thing, insofar as it reflects that linked data is being made available and put to real use.  Tim Berners-Lee notes that: "On balance, life is good."
+# that these issues are arising at all can be seen as a good thing, insofar as it reflects that linked data is being made available and put to real use.  Tim Berners-Lee notes that: "Life is, on balance, good."

@@ Line 13: / Line 13: @@
 # even if you can find the links, prolific use of owl:sameAs will create computational problems.
-''Source:'' This discussion is taken from a thread called [http://lists.w3.org/Archives/Public/semantic-web/2008May/0078.html Managing Co-reference (Was: A Semantic Elephant?)] on the [http://lists.w3.org/Archives/Public/semantic-web/ W3C Semantic Web Discussion List]. A vigorous discussion initially took place off the list, and then was moved to the list for the record.
+''Source:'' This discussion is taken from a thread called [http://lists.w3.org/Archives/Public/semantic-web/2008May/0081.html Managing Co-reference (Was: A Semantic Elephant?)] on the [http://lists.w3.org/Archives/Public/semantic-web/ W3C Semantic Web Discussion List]. A vigorous discussion initially took place off the list, and then was moved to the list for the record.
 ''Related Discussions'':
@@ Line 22: / Line 22: @@
 # Wordnet issued new URIs for all of its terms for the new version, even when they referred to exactly the same thing.
 # Yago and DBpedia minted different URIs for the exact same Yago classes

@@ Line 1: / Line 1: @@
 {{TitleDescription Template
 |Title=Proliferation of URIs, Managing Coreference
 |Description=General Issue: There are some negative consequences to the current proliferation of new URIs being minted for the same things. The issue is how to avoid or manage this.
 }}
 {{Graphical representation}}
@@ Line 23: / Line 23: @@
 # Yago and DBpedia minted different URIs for the exact same Yago classes
 Here is the original Post by Michael Uschold in May 2008: