Rapid prototyping of semantic mash-ups through semantic web pipes
Proceedings of the 18th international conference on World wide web
Sindice.com: weaving the open linked data
ISWC'07/ASWC'07 Proceedings of the 6th international The semantic web and 2nd Asian conference on Asian semantic web conference
An entity name system (ENS) for the semantic web
ESWC'08 Proceedings of the 5th European semantic web conference on The semantic web: research and applications
When owl: sameAs isn't the same: an analysis of identity in linked data
ISWC'10 Proceedings of the 9th international semantic web conference on The semantic web - Volume Part I
Weaving a social data web with semantic Pingback
EKAW'10 Proceedings of the 17th international conference on Knowledge engineering and management by the masses
Linking the (un)linked data through backlinks
Proceedings of the International Conference on Web Intelligence, Mining and Semantics
Creating voiD descriptions for Web-scale data
Web Semantics: Science, Services and Agents on the World Wide Web
ISWC'11 Proceedings of the 10th international conference on The semantic web - Volume Part I
| Hi-index | 0.00 |
A key requirement in linking open data refers to the rendering of such data easy to explore and consume. Such a requirement is critical for the overall quality of linked data in terms of consistency and interlinking. Although the provision of dereferenceable URIs is a step towards the right direction, current status of the semantic web indicates that such a feature alone is not enough. After all, as Berners Lee stressed, a URI is just an identifier for a resource not a recipe for its retrieval. In this paper, a decentralized infrastructure is presented capable of efficiently managing the URIs that are being consumed within the web of data. The proposed work is based on the registry, a place where triplestores may store information about their local URI entities. Such information evolves around backlinks that are defined as the references that are made from triples of remote triplestores to the locally defined URIs of a given triplestore. The registries communicate with each other through a lightweight protocol that facilitates the management and retrieval of URI entities across the LOD cloud.