How can we construct one URI based on another?
Sometimes when generating a Patterned URI the key that we have for as URL Slug is not a simple literal value, but instead another URI. For example this can occur when generating a new Named Graph URI for a resource, or when defining a service URL for a URI Resolver.
Rewrite the original URI to use a new, predictable base URI using on of the options described below.
An application needs to generate a new Named Graph URI for a resource URI of http://example.org/document/1. The application uses a regular expression to rewrite the original URI to a new base, e.g. http://graphs.example.org/document/1.
URL rewriting is a common feature of all web servers and most web frameworks. Rewriting is normally carried out using regular expressions to match and replace portions of the original URI with some standard replacement text.
URL rewriting is used in several Linked Data services in order to create new URLs. This is typically to support URI resolution for remote (RDF) resources.
Several different approaches seem to be in use. The following examples all show a rewrite for this URI: http://example.org/document/1. Each example notes an example service that uses the approach:
http://service.example.com/resolve/http://example.org/document/1. The original URI is simply appended to a new base URL. Has the advantage of working with any protocol.http://service.example.com/resolve/example.org/document/1. The original URI is simply appended to a new base URL after first removing the protocol (e.g. "http://"). Server will need to assume the http protocol if de-referencing the URI or reversing the rewrite.http://service.example.com/resolve;http://example.org/document/1. The original URI is simply appended to a new base URL which ends with a semi-colon.http://service.example.com/resolve?uri=http://example.org/document/1. The original URI is simply appended to a new base URL as a query string parameter.http://data.example.org/document/1. The authority component of the URI is rewritten to create a new base URI. This approach might lead to URI clashes unless the input URIs have a predictable structure.