How it works

The check resolvability tool allows you to test if a given URI is resolvable. It is based on the HTTP HEAD method. We check the resolvability of a URI by sending a HEAD request to the URI and checking if the response status code is 200 (OK) and the returned content type is equal to one of the following application/json, application/rdf+xml, text/turtle, text/n3, text/html.

We have a timeout set to 5 seconds, so if the URI is not resolvable within that time, the check will fail. And a max redirections set to 10, so if the URI is not resolvable within that number of redirections, the check will fail.

Resolving a URI

In the context of web semantics, dereferencing refers to the process of resolving and obtaining the actual data associated with a Uniform Resource Identifier (URI). In simpler terms, it involves following a link represented by a URI/IRI to retrieve information or resources linked to that identifier. In the Semantic Web, URIs are used to uniquely identify resources, and dereferencing allows systems to access and retrieve data related to those resources. When a URI/IRI is dereferenced, it typically leads to the retrieval of RDF (Resource Description Framework) data or other structured information that describes the resource in a machine-readable format. This enables systems to understand and process the meaning of the linked data, facilitating the exchange and integration of information on the web.

Content negotiation

Content negotiation in the context of the Semantic Web refers to the mechanism by which two communicating parties, such as a client and a server, agree on the most suitable representation of a resource during the process of dereferencing a URI or IRI. This negotiation aims to ensure effective communication between different systems that may prefer different data formats or languages. In other words, when a client requests a resource by dereferencing a URI, it indicates its preferences for the format or language of the response data through HTTP headers or other negotiation mechanisms. The server, in turn, examines these preferences and selects the most appropriate representation of the resource based on what is available. different formats can be agreed upon between a client and server when accessing linked data. Common formats include: RDF/XML: XML-based representation of Resource Description Framework data. Turtle: Human-readable serialization format for RDF. JSON-LD: JSON-based format for linked data. N-Triples and N-Quads: Text formats for expressing RDF triples and quads. HTML: Markup language for web pages, also used to embed RDF data. RDFa: Embedding RDF data in HTML or XML using attributes. SPARQL Query Results XML and JSON: Formats for representing SPARQL query results.