Ontologies are sets of domain concepts. The domain can span both documents (information resources) and abstract/physical things (non-information resources).

Ontologies can import other ontologies, both user-defined and system ones provided by LinkedDataHub. The imports are retrieved during application initialization, and the ontology becomes a transitive union, i.e. is merged with its imports and imports of the imports etc.

Main ontology properties:

Ontology to be imported
Unique version of this ontology


Classes are simply RDFS classes. Usually the application dataset contains class instances.

Main class properties such as constructor and constraint are explained in the sub-sections below. Additional properties are:

Query that constructs new class instance
Command or command template that validates class instance


Constructors are SPARQL CONSTRUCT queries that serve as templates for class instances. They specify the properties (both mandatory and optional) that the instance is supposed to have, as well as expected datatypes of their values. Constructors are used in create/edit modes. A class can have multiple constructors.

For example, one of the constructors of the dh:Container and dh:Item classes:

PREFIX rdf:     <>
PREFIX xsd:     <>
PREFIX sioc:    <>
PREFIX dct:     <>

  $this sioc:content "<div xmlns=\"\"></div>"^^rdf:XMLLiteral .

An instance of these classes by default have a content property with XML literal.

LinkedDataHub reuses SPIN constructors for the implementation, but adds a special syntax convention using blank nodes to indicate the expected resource type ([ a ex:Person ]) or literal datatype ([ a xsd:string ]).

Note that classes inherit constructors from superclasses in runtime. Subclasses do not have to redefine constructor properties already found in superclass constructors, only additional properties.


Constraints are SPARQL queries or SPIN command templates that validate submitted RDF data during document creation and editing. Constraints are enforced for instances of model classes on which they are defined and are used to check class instances for violations (missing mandatory properties, malformed values etc.). For example, an instance of dh:Item without dct:title will fail validation because titles are mandatory for LinkedDataHub documents.

LinkedDataHub reuses SPIN constraints. Classes inherit constraints from superclasses.

SHACL constraint validation is supported as well.


LinkedDataHub allows definition of new properties.