Michele Pasin / Quotes

Any HTTP URI should be dereferenceable

Any HTTP URI should be dereferenceable, meaning that HTTP clients can look up the URI using the HTTP protocol and retrieve a description of the resource that is identified by the URI. This applies to URIs that are used to identify classic HTML documents, as well as URIs that are used in the Linked Data context to identify real-world objects and abstract concepts.

Descriptions of resources are embodied in the form of Web documents. Descriptions that are intended to be read by humans are often represented as HTML. Descriptions that are intended for consumption by machines are represented as RDF data.

Where URIs identify real-world objects, it is essential to not confuse the objects themselves with the Web documents that describe them. It is, therefore, common practice to use different URIs to identify the real-world object and the document that describes it, in order to be unambiguous. This practice allows separate statements to be made about an object and about a document that describes that object. For example, the creation date of a person may be rather different to the creation date of a document that describes this person. Being able to distinguish the two through use of different URIs is critical to the coherence of the Web of Data.

Saved 4 September 2014 / linkeddatabook.com ↗

#real-world-objects #URI #web-documents #objects #documents

Cool URIs: be on the Web, be unambiguous

Given such a URI, how can we find out what it identifies? We need some way to answer this question, because otherwise it will be hard to achieve…

Cool Uris For The Semantic Web #real-world-objects #URI #web-documents #search-engines #Web #documents

Web document (information resource)

Like everything on the traditional Web, each of the pages mentioned above are Web documents. Every Web document has its own URI. Note that a Web document is…

Cool Uris For The Semantic Web #web-documents #URI #documents #files #Web #pages

Hash URIs versus 303 redirects

The solutions described in the following apply to deployment scenarios in which the RDF data and the HTML data is served separately, such as a standalone…

Cool Uris For The Semantic Web #web-documents #server #URI #HTML #web-server #RDF

Content negotiation for RDF and HTML

Web clients and servers use the HTTP protocol [RFC2616] to request representations of Web documents and send back the responses. HTTP has a powerful mechanism…

Cool Uris For The Semantic Web #web-documents #content-negotiation #server #format #documents

Naming statements happens outside RDF

RDF does not provide a built-in way of indicating how a URIref like exproducts:triple12345 is associated with a particular statement or graph, any more than…

Rdf Primer #RDF #URI #documents #RDF-documents #statements #resources

Setting a base URI with XML Base

...relative URIrefs such as #item10245 will be interpreted relative to a base URI. By default, this base URI would be the URI of the resource in which the…

Rdf Primer #URI #documents #RDF/XML #XML-documents #resources