lid:
URI resolverThis service can be used as a resolver for URIs in the lid:
scheme (described here).
The webserver is also configured to resolve URIs in the form: https://data.is4.site/lid://example.org/ex:id/1
You may also use the form below:
Using an undefined prefix is valid, but requires the target to understand it. The prefixes recognized by the service are as follows (ordered by priority):
#
, /
or :
are considered.This means that some common prefixes may be overwritten by URI schemes (see here for examples). The syntax still allows to redefine any such prefix manually.
The list of default prefixes (JSON-LD context) is periodically synchronized with the source documents. This could result in ambiguities between different resolvers or points in time, since a particular prefix could turn from undefined to defined when one of the two lists is modified. This is easily prevented by undefining the prefix manually in the URI, or by using the empty prefix or a prefix that starts on x.
.
If an entry is removed from the source lists, it could also prevent this resolver from correctly processing URIs that use the prefix. It is assumed entries are never removed from the sources, and if so, it justifies the consequences.
The options above can be also specified in the query part of the URI. Any query parameter starting with __
is stripped of it and passed to the target endpoint.
lid://example.org/rdfs:label/1
rdfs:label
(known prefix) with a literal value of 1(any type).
lid://example.org/rdfs:label/1@
"1"
(plain untagged literal in RDF 1.0, xsd:string
in RDF 1.1).lid://example.org/rdfs:label/1@xsd:integer
"1"^^xsd:integer
.lid://example.org/rdfs:label/Person@en
"Person"@en
(English language tag).lid://example.org/ex:id/1
ex:id
with the specified value. The resolution of ex:
is performed by the target endpoint, because it is an undefined prefix.lid://example.org/foaf:mbox/uri/mailto:address%40example.org
foaf:mbox
(known prefix) with a value of <mailto:address@example.org>
(a URI).lid://example.org/'foaf:age/foaf:mbox/uri/mailto:address%40example.org
foaf:age
of the specified entity.lid://example.org/rdf:value/uri/rdf:nil
<rdf:nil>
(a URI) – likely incorrect!lid://example.org/rdf:value/uri/$rdf:nil
rdf:nil
(using the known prefix).lid://example.org/ex:id/1?ex=http://example.org/
<http://example.org/id>
property (http:
is treated as a known prefix).lid://example.org/base:id/1
<id>
property (base:
is a known prefix for producing relative URIs).