Configuring podd

PODD is mainly configured using a single file, named podd.properties.

An example of a podd.properties file is at [TO BE CREATED]

This file must be on the classpath to be discovered. This can be done with a Maven WAR project by putting it in src/main/resources/podd.properties

The other main configuration file is an RDF file representing the Schema Ontologies to be used by the instance of PODD. The location of this manifest file on the classpath is referenced from podd.properties. It can be named anything, as long as the extension is a recognised file extension for the RDF format that it is encoded in.

An example of a Schema Ontology Manifest file is at https://github.com/podd/podd-ontologies/blob/master/src/main/resources/podd-schema-manifest.ttl.sample

It must contain the details for the schema ontologies, the versions that are available, the classpath reference used to find them, and any imports. The imports must be present in the schema manifest to ensure that they are loaded in the correct order, and to ensure that the manifest can be used to identify the full ontology closure for any desired set of schema ontologies.

When creating a new artifact using the PODD API, the schema ontologies that it imports must be specified using owl:imports. These schema ontologies must already be present in the PODD system.

Although the podd.properties file is completely optional, it must be present to configure a permanent storage location for PODD data.