Linked Data: Evolving the Web into a Global Data Space
owl:sameAs
owl:sameAs is an OWL built-in property used to link an individual to an individual. Such an owl:sameAs statement indicates that two URI references actually refer to the same thing: the individuals have the same "identity". In N3 syntax = is a synonym for owl:sameAs. owl:sameAs is described in Section 5.2 Individual identity of the OWL Web Ontology Language Reference Linked Data Alternatives As pointed by Alexandre Passant there are Inconsistencies in the LOD cloud that relate back to incorrect owl:sameAs links. Examples GoodRelations Examples The following examples were provided by Martin Hepp on the GoodRelations mailing list ( October 10, 2009). "The distributed character of the Web makes it very likely that the exact same entity is being defined in multiple graphs. Note that the current rules assume perfect equivalence of the legal names resp. the EAN/UPC code.
sameAs
Documentation - COEUS
COEUS has now the capability to share your data in the Nanopublication format. With this new plugin you can transform your integrated data in this prominent format by following the next steps: Go to the Nanopublication Section on the Dashboard. Select the concept root and related data that will generate the nanopublications. Download tutorial Visit website December 9-12, 2013 Edinburgh, United Kingdom In this tutorial/hands-on session, we will guide you through the process of creating your own custom COEUS knowledge base. Create a new COEUS instance From GitHub download to web deployment Integrate data from heterogeneous *omics sources into your COEUS knowledge base Create your mashup merging multiple datasets Explore COEUS API to access aggregated data Build new rich web information systems using the API Access knowledge federation through the SPARQL and LinkedData interfaces Download tutorial Customizing the seed configuration is the most cumbersome task for COEUS deployment. Web settings
Linked Data Platform 1.0
5.1 Introduction This section is non-normative. Many HTTP applications and sites have organizing concepts that partition the overall space of resources into smaller containers. Blog posts are grouped into blogs, wiki pages are grouped into wikis, and products are grouped into catalogs. Each resource created in the application or site is created within an instance of one of these container-like entities, and users can list the existing artifacts within one. Containers answer some basic questions, which are: To which URLs can I POST to create new resources? This document defines the representation and behavior of containers that address these issues. This document includes a set of guidelines for creating new resources and adding them to the list of resources linked to a container. The following illustrates a very simple container with only three members and some information about the container (the fact that it is a container and a brief title): Example 1 Example 2 Example 3 Example 4 Example 5
Lost Boy | The blog of @ldodds
Data
What is Linked Data? The Semantic Web is a Web of Data — of dates and titles and part numbers and chemical properties and any other data one might conceive of. The collection of Semantic Web technologies (RDF, OWL, SKOS, SPARQL, etc.) provides an environment where application can query that data, draw inferences using vocabularies, etc. However, to make the Web of Data a reality, it is important to have the huge amount of data on the Web available in a standard format, reachable and manageable by Semantic Web tools. To achieve and create Linked Data, technologies should be available for a common format (RDF), to make either conversion or on-the-fly access to existing databases (relational, XML, HTML, etc). What is Linked Data Used For? Linked Data lies at the heart of what Semantic Web is all about: large scale integration of, and reasoning on, data on the Web. Examples Learn More Tim Berners-Lee's note on Linked Data gives a succinct description of the Linked Data principles.
URL, URN, URI, IRI - Why So Many?
Computer guys tend to lack imagination, especially when they work with acronyms. This may lead to a lot of funny stuff. Let’s look at the following acronyms, for instance: URI, URN, URL, and IRI. In interviews I like to ask this question and only once a guy was able to give an almost 100% correct answer. Somehow, I was not particularly surprised about it, as even widely adopted specifications contain subtle mistakes. What Is URI? URI stands for Uniform Resource Identifier. Mathematically speaking, the previous definition fails to specify if any URL is an URI and if any URN is an URI. The answer in both cases is yes. On the other hand, the URN is just a name. Technically, both terms (URL and URN) are obsolete and URI should be used instead. Namespaces When URIs appear in schemes, it gets very confusing. For example, a namespace like is very common. In A Nutshell In short, URI is the recommended term to use. What about IRI? P.S.
