EPrints Ontology

IRI:
http://eprints.org/ontology/
Authors:
http://id.ecs.soton.ac.uk/person/1248
Other visualisation:
Ontology source

Table of Content

  1. Classes
  2. Object Properties
  3. Named Individuals
  4. Annotation Properties
  5. Namespace Declarations

Classes

Documentc back to ToC or Class ToC

IRI: http://eprints.org/ontology/Document

is defined by
http://eprints.org/ontology/
A single document that is part of an ep:EPrint record. It may be a machine generated version of another document, eg. a thumbnail, in which case this will be expressed with relations from the http://eprints.org/relation/ namespace. It will have one or more files associated. Some documents can have multilple files, such as an HTML page plus image files. Resolving a document URI will redirect you to the primary file of the document.
is equivalent to
documentc
is in domain of
has Fileop
is in range of
has Documentop

EPrint Recordc back to ToC or Class ToC

IRI: http://eprints.org/ontology/EPrint

is defined by
http://eprints.org/ontology/
A single record in an EPrints Repository. Generally this will be described as BIBO and Dublin Core, and may have a number of associated ep:Documents. Resolving a URI of class ep:EPrint will direct to the HTML summary page for the record, in an HTML browser, or to an RDF (XML or N3) document in an RDF client. The RDF document will contain all available RDF information about the record including all attached ep:Document records and their metadata and links from the document to the files via ep:hasFile. Not all files may be available without authentication. If the files themselves contain semantic information of interest these will need to be resolved separately. References to people, organisations, publications and locations may be given URIs of the form /id/<typeofthing>/ext-<somevalue> -- in this case the URI will be resolvable as RDF+XML or N3 and may yield additional records in the repository referencing the same thing, although this is usually based on the hashing of metadata strings and may not be complete or perfect. The ext- indicates that this concept is not something the repository actually stores information about, it is just referenced by one or more records. For example, the RDF for an EPrint about a paper given at a conference may reference that conference with a URI of the form /id/event/ext-a43de4454. That URI will be resolvable but the repository does not contain full information about that event, just information derived from EPrint record metadata. It is hoped that the community may develop systems to link such URIs to the more definitive URI for an event, person, location etc.
is in domain of
has Documentop
is in range of
has EPrint Recordop

EPrints Repositoryc back to ToC or Class ToC

IRI: http://eprints.org/ontology/Repository

is defined by
http://eprints.org/ontology/
An EPrints Repository. This will have a number of EPrints records associated with it via the ep:hasEPrint predicate, and the records will generally be expressed as BIBO & Dublin Core, plus EPrints extensions to describe the attached documents and files. Resolving the URI of this class using a client which prefers RDF XML (or text/n3) will return an RDF document describing the repository using voID and Dublin Core, plus a ep:hasEPrint link to every current record in the public part of the repository. See ep:EPrint for more description about such records. EPrints generally supports a sitemap.xml file which describes a set of data-dump-locations. Resolving these is the fastest way to obtain every bit of RDF data from an EPrints repository.
has super-classes
datasetc
is in domain of
has EPrint Recordop

Object Properties

has Documentop back to ToC or Object Property ToC

IRI: http://eprints.org/ontology/hasDocument

is defined by
http://eprints.org/ontology/
A Document which is part of this EPrint Record.
has domain
EPrint Recordc
has range
Documentc

has EPrint Recordop back to ToC or Object Property ToC

IRI: http://eprints.org/ontology/hasEPrint

is defined by
http://eprints.org/ontology/
An EPrint record which is part of this Repository.
has domain
EPrints Repositoryc
has range
EPrint Recordc

has Fileop back to ToC or Object Property ToC

IRI: http://eprints.org/ontology/hasFile

is defined by
http://eprints.org/ontology/
A File which is part of this Document.
has domain
Documentc

OAI-PMH URLop back to ToC or Object Property ToC

IRI: http://eprints.org/ontology/OAIPMH2

is defined by
http://eprints.org/ontology/
The base URL to use to query this repository via OAI-PMH. Note that the domain is set to any dataset, not just an EPrints Repository, so as not to limit use by non-eprints repositories.
has domain
datasetc

SKOS Concept Schemeop back to ToC or Object Property ToC

IRI: http://eprints.org/ontology/hasConceptScheme

is defined by
http://eprints.org/ontology/
A SKOS concept scheme employed by this dataset.
has domain
datasetc
has range
concept schemec

Named Individuals

1248ni back to ToC or Named Individual ToC

IRI: http://id.ecs.soton.ac.uk/person/1248

belongs to
personc

Annotation Properties

nameap back to ToC or Annotation Property ToC

IRI: http://xmlns.com/foaf/0.1/name

Namespace Declarations back to ToC

default namespace
http://eprints.org/ontology/
core
http://www.w3.org/2004/02/skos/core#
foaf
http://xmlns.com/foaf/0.1/
owl
http://www.w3.org/2002/07/owl#
person
http://id.ecs.soton.ac.uk/person/
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
terms
http://purl.org/dc/terms/
vann
http://purl.org/vocab/vann/
void
http://rdfs.org/ns/void#
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.