Ontologies

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

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

Best practice: avoid using `owl:imports` with uploaded files

Do not use owl:imports declarations that point to paths under uploads/. This can cause circular dependency deadlocks\n during system initialization, as the ontology loading process cannot access uploaded files without creating a circular reference.

Instead:

Host ontologies as proper documents (not uploaded files)
Import them using their document URIs
If you need to use an ontology that was uploaded, create it as a proper ontology document first

For more information, see the file upload documentation.

Main ontology properties:

Imports: Ontology to be imported
Version: Unique version of this ontology

System ontologies

\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

Ontology	Title	Prefix
`https://w3id.org/atomgraph/linkeddatahub/default#`	Default	`def:`
`https://w3id.org/atomgraph/linkeddatahub/apps#`	Applications	`lapp:`
`https://w3id.org/atomgraph/linkeddatahub/acl#`	Access control	`lacl:`
`https://w3id.org/atomgraph/linkeddatahub/admin#`	Admin	`adm:`
`https://w3id.org/atomgraph/linkeddatahub#`	LinkedDataHub	`ldh:`
`https://www.w3.org/ns/ldt/document-hierarchy#`	Document hierarchy	`dh:`

Classes

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:

Constructor: Query that constructs new class instance
Constraints: Command or command template that validates class instance

Constructors

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

For example, the constructor of the ldh:XHTML class:

PREFIX rdf:     <http://www.w3.org/1999/02/22-rdf-syntax-ns#>\n\nCONSTRUCT {\n  $this rdf:value \"<div xmlns=\\\"http://www.w3.org/1999/xhtml\\\"></div>\"^^rdf:XMLLiteral .\n}\nWHERE {}

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

LinkedDataHub reuses SPIN constructors for the implementation, but adds a\n special syntax convention using blank nodes to indicate the expected resource type ([ a ex:Person ]) or literal datatype\n ([ a xsd:string ]). The magic variable $this refers to the instance being constructed, it is a blank node resource initially but\n gets skolemized to a URI when submitted to the server.

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

Constraints

Constraints are SPARQL queries or SPIN command templates that validate submitted\n RDF data during document creation and editing. Constraints are enforced for instances of model classes on which they are defined and are\n used to check class instances for violations (missing mandatory properties, malformed values etc.). For example, an instance of\n 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.

Properties

LinkedDataHub allows definition of new properties.