Matches in ScholarlyData for { ?s ?p Today, as a result of many independent initiatives, research projects and commercial initiatives, relatively large and important content repositories are available which actually are (or can be easily tranformed into) local ``semantic webs'', namely graphs of resources connected through properties which are defined in some schema or vocabulary. The data published as part of the LinkedData initiative are examples of content already insemantic web format (RDF/OWL); however, any social network, digital library metadata collection, commercial catalog and in principle any relational database could be easily (and mostly syntactically) transformed into a local semantic web. So what is missing enabling factor which can support the automatic and smooth integration of these local ``semantic webs'' into something like the envisaged global Semantic Web? In this paper, we argue that the missing factor is a service which, in analogy with what the DNS did for the Web, can make the addressing mechanism of the Semantic Web global. The addressing mechanism of the WWW was made global by building it on top of the pre-existing DNS service; the addressing mechanism of the Semantic Web cannot go global, as no such pre-existing infrastructure is available, and therefore no fast and easy (semantic) integration is readily available. In this paper, we first introduce and describe what we consider to be the cornerstone of such an infrastructure, a service called Entity Naming System (ENS) which is designed to resolve a local URI or even an arbitrary description of a resource (not only, and not mainly, information resources) into a global identifier for that resource. Then we discuss the main issues and challenges associated with the design and implementation of a scalable and sustainable ENS. Third, we report the results of an experiment which we made on integrating the metadata of several Web and Semantic Web conference with or without a ENS. Finally, we present two simple examples of how existing applications can use the ENS for creating semantically integrated knowledge for the Semantic Web.. }
Showing items 1 to 1 of
1
with 100 items per page.
- 245 abstract "Today, as a result of many independent initiatives, research projects and commercial initiatives, relatively large and important content repositories are available which actually are (or can be easily tranformed into) local ``semantic webs'', namely graphs of resources connected through properties which are defined in some schema or vocabulary. The data published as part of the LinkedData initiative are examples of content already insemantic web format (RDF/OWL); however, any social network, digital library metadata collection, commercial catalog and in principle any relational database could be easily (and mostly syntactically) transformed into a local semantic web. So what is missing enabling factor which can support the automatic and smooth integration of these local ``semantic webs'' into something like the envisaged global Semantic Web? In this paper, we argue that the missing factor is a service which, in analogy with what the DNS did for the Web, can make the addressing mechanism of the Semantic Web global. The addressing mechanism of the WWW was made global by building it on top of the pre-existing DNS service; the addressing mechanism of the Semantic Web cannot go global, as no such pre-existing infrastructure is available, and therefore no fast and easy (semantic) integration is readily available. In this paper, we first introduce and describe what we consider to be the cornerstone of such an infrastructure, a service called Entity Naming System (ENS) which is designed to resolve a local URI or even an arbitrary description of a resource (not only, and not mainly, information resources) into a global identifier for that resource. Then we discuss the main issues and challenges associated with the design and implementation of a scalable and sustainable ENS. Third, we report the results of an experiment which we made on integrating the metadata of several Web and Semantic Web conference with or without a ENS. Finally, we present two simple examples of how existing applications can use the ENS for creating semantically integrated knowledge for the Semantic Web.".