\n

System endpoints

\n

Endpoints that LinkedDataHub serves in addition to the document hierarchy. Paths are relative to the dataspace's base URI; the admin app's\n are relative to the administration dataspace's base, e.g. https://admin.localhost:4443/clear.

\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n

System endpoints by path

Path	Description
Admin and end-user apps
ns	In-memory namespace ontology as well as its SPARQL endpoint
sitemap.xml	The dataspace's public documents, in the sitemaps protocol: queried on request from the public read rules of the dataspace's own admin service, so an origin lists only its own documents. Past 50,000 documents it is a sitemap index over sitemap.xml?bucket=… pages, which group the documents by the MD5 prefix of their URI. Served only when ENABLE_SITEMAP is on; an end-user dataspace with nothing public has none, and neither does an admin dataspace
robots.txt	Allows crawling and names the sitemap when the sitemap is enabled and the dataspace has at least one public document; disallows everything otherwise
context	The public description of every dataspace of the instance: its type, title, origin, ontology and stylesheet, and the lds:admin base URI of each end-user dataspace (see dataspace context). Readable by anyone; it never contains service endpoints or credentials
settings	The dataspace's own description in the dataspace configuration. PATCH with a SPARQL update edits it — this is how packages are installed and uninstalled. Editing is restricted to end-user dataspaces: a PATCH on an admin dataspace's settings answers 422 Unprocessable Entity
Admin app only
access	Access metadata (for the authenticated agent)
access/request	Access request (for the authenticated agent)
sign%20up	WebID-TLS agent signup
oauth2/login/google	OpenID Connect with Google login
oauth2/login/orcid	OpenID Connect with ORCID login
oauth2/authorize/google	OpenID Connect with Google callback
oauth2/authorize/orcid	OpenID Connect with ORCID callback
clear	Clears every cached ontology graph and imports closure from memory. With an optional uri form parameter, also purges that ontology's proxy caches and reloads its closure from the admin SPARQL endpoint

\n