Deployment Approach

In the repositories

An ESIP mmiorr repository has been created and maintained as a fork of the MMI ORR software. This ESIP mmiorr repository will be used as the basis of ESIP's Community Ontology Repository service. Thus ESIP will always have control over this software, although for the most part it is expected to mirror MMI's software.

When modifications are made to the ESIPFed/mmiorr repository, the ORR team will at its discretion merge modifications that are appropriate for the MMI ORR, back to the mmisw/mmiorr repository. These merges upstream should not have any impact on the ESIP software, and should not prevent the ESIPFed/mmiorr repository from continuing to track improvements to MMI's ORR, as desired.

In the Cloud

The ORR instance to be used for the ESIP Community Ontology Repository is deployed on an ESIPFed Amazon Web Service (AWS) instance (that is, on the cloud).

Web URLs based in the ESIP domain will be used as the primary location of the COR services. These URLs will be directed to, and serviced by, the COR instance hosted on the AWS.

Automatic resolution of ontologies and terms is an important feature of the MMI ORR, and will be provided with COR as well. To achieve this, the IRIs (the new term for URIs, which are actually URLs in this case) generated for the terms in the COR ontology repository use the same path as the COR ontologies stored in the ESIP domain, and the ESIP COR service resolves those IRIs. (In the MMI ORR, these term IRIs begin http://mmisw.org/orr/; the ESIP path is not yet finalized.)

Additional services that are currently provided with MMI's ORR (such as ontology services available under the http://mmisw.org/ont/ path, and possibly some other resolution/lookup services to be determined) will be available in COR at ESIPFed URLs to be determined.