Deployment Approach

In the repositories

The ESIP Federation mmiorr repository will be used as the basis of the COR deployment to the AWS instance (see next section). Thus ESIP will always have control over this 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, if that's desired.

In the Cloud

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

URLs based in the ESIP domain will be used as the primary location of the services of the COR. These will be forwarded to the actual instance hosted on the AWS.

The URIs generated for the terms in the ontology repository (in ORR, these begin http://mmisw.org/orr/) will use the same path as the location of the ontologies URL in the ESIP domain. This will allow resolution of the terms using their actual URIs, a key feature of the ORR repository service.

Additional services, currently associated with MMI's ORR (such as ontology services available under the http://mmisw.org/ont/ path, and any other services that may be provided) will be available at ESIPFed URLs to be determined.