Dataspace
LinkedDataHub dataspaces, applications, and services
Dataspaces
The LinkedDataHub URI address space is split into dataspaces. Every dataspace consists of a pair of LDT applications: end-user and administration.
The end-user app will be available on the given base URI; the admin app will be available
at that base URI with admin/ appended. The agent that installed the admin dataset will be the application owner.
The secretary is a special agent which represents the software application itself. It is distinct from the owner agent and is used to delegate the owner's access.
Applications
All LDT applications have the following traits:
- Base URI
- Base URI is a URI by which an application can be identified. All request URIs processed by an application are relative to one of its base URIs.
- URIs in the application dataset are usually (but not necessarily) relative to its base URIs.
- Service
- SPARQL service
- Namespace ontology
- Ontology that defines the terms (classes, properties, constraints etc.) of the application's domain. It can import other ontologies from within the application as well as from external documents.
- Ontologies as managed in the administration application.
Base URI must end with a forward slash (/).
In addition to that, LinkedDataHub applications have one additional property:
- Stylesheet
- XSLT stylesheet that renders the applications layout
End-user
The base URI of an end-user application is also the base URI of its dataspace.
Every end-user application is related to one administration application.
Administration
Every administration application is related to one end-user application. It cannot exist standalone.
The base URI(s) of an administration application is the base URI(s) of its end-user
application with admin/ appended
to it. Note that any URIs in the end-user application that are equal or relative to
the admin application base URI will not
be accessible.
Administration application provides means to control the domain model and the access control of its end-user application. Only dataspace owners have access to its administration application.
The agent which installs the adminstration application dataset becomes the owner of its dataspace.
LinkedDataHub imports the default datasets for each application type into its service. The dataset URIs are rebased to be relative to the base URI of the application.
Services
A service is a persistent SPARQL 1.1-compatible store from which the application's RDF dataset is accessible over HTTP. LinkedDataHub supports generic services as well as triplestore-specific services which support easier configuration and optimized access. HTTP Basic is suppported as an authentication scheme. Contact us regarding support for vendor-specific authentication such as API keys.
The end-user application service must be able to federate with the administration
application service using the
SPARQL SERVICE keyword.
Generic services
Generic service has the following properties:
- Endpoint
- SPARQL 1.1 Protocol endpoint URI
- Graph Store
- SPARQL 1.1 Graph Store Protocol endpoint URI
- Username
- HTTP Basic username (optional)
- Password
- HTTP Basic password (optional)
Custom services
LinkedDataHub has extension points for vendor-specific SPARQL services, which can be used to implement proprietary authentication schemes, for example.
If you are ready to create a dataspace, see our step-by-step tutorial on dataspace management.