TY - GEN

T1 - How to trace and revise identities

AU - Gaugaz, Julien

AU - Zakrzewski, Jakub

AU - Demartini, Gianluca

AU - Nejdl, Wolfgang

N1 - Funding Information: This work is partially supported by the FP7 EU Large-Scale Integrating Project OKKAM Enabling a Web of Entities (contract no. ICT-215032).

PY - 2009

Y1 - 2009

N2 - The Entity Name System (ENS) is a service aiming at providing globally unique URIs for all kinds of real-world entities such as persons, locations and products, based on descriptions of such entities. Because entity descriptions available to the ENS for deciding on entity identity-Do two entity descriptions refer to the same real-world entity?-are changing over time, the system has to revise its past decisions: One entity has been given two different URIs or two entities have been attributed the same URI. The question we have to investigate in this context is then: How do we propagate entity decision revisions to the clients which make use of the URIs provided by the ENS? In this paper we propose a solution which relies on labelling the IDs with additional history information. These labels allow clients to locally detect deprecated URIs they are using and also merge IDs referring to the same real-world entity without needing to consult the ENS. Making update requests to the ENS only for the IDs detected as deprecated considerably reduces the number of update requests, at the cost of a decrease in uniqueness quality. We investigate how much the number of update requests decreases using ID history labelling, as well as how this impacts the uniqueness of the IDs on the client. For the experiments we use both artificially generated entity revision histories as well as a real case study based on the revision history of the Dutch and Simple English Wikipedia.

AB - The Entity Name System (ENS) is a service aiming at providing globally unique URIs for all kinds of real-world entities such as persons, locations and products, based on descriptions of such entities. Because entity descriptions available to the ENS for deciding on entity identity-Do two entity descriptions refer to the same real-world entity?-are changing over time, the system has to revise its past decisions: One entity has been given two different URIs or two entities have been attributed the same URI. The question we have to investigate in this context is then: How do we propagate entity decision revisions to the clients which make use of the URIs provided by the ENS? In this paper we propose a solution which relies on labelling the IDs with additional history information. These labels allow clients to locally detect deprecated URIs they are using and also merge IDs referring to the same real-world entity without needing to consult the ENS. Making update requests to the ENS only for the IDs detected as deprecated considerably reduces the number of update requests, at the cost of a decrease in uniqueness quality. We investigate how much the number of update requests decreases using ID history labelling, as well as how this impacts the uniqueness of the IDs on the client. For the experiments we use both artificially generated entity revision histories as well as a real case study based on the revision history of the Dutch and Simple English Wikipedia.

UR - http://www.scopus.com/inward/record.url?scp=69949096915&partnerID=8YFLogxK

U2 - 10.1007/978-3-642-02121-3_32

DO - 10.1007/978-3-642-02121-3_32

M3 - Conference contribution

AN - SCOPUS:69949096915

SN - 978-3-642-02120-6

T3 - Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

SP - 414

EP - 428

BT - The Semantic Web

T2 - 6th European Semantic Web Conference, ESWC 2009

Y2 - 31 May 2009 through 4 June 2009

ER -