Distribute ontologies using Amazon Web Services

[GoogleCodeExporter]

This is a starting point for discussing how to move Foundry infrastructure to 
AWS. Some, if not all of what we can do might even fit under their free level 
of service.

The easiest thing to do first, I suspect, is to have the ontology files proper 
live in S3. 
Next up might be hosting the redirection server. 

Original issue reported on code.google.com by alanruttenberg@gmail.com on 21 Jan 2013 at 7:18

[GoogleCodeExporter]

For those of us that are less tech savvy.... AFAIK AWS is mostly a storage 
solution. How will it help, for example with PURLs?

Original comment by mcour...@gmail.com on 21 Jan 2013 at 8:48

[GoogleCodeExporter]

S3 is just a storage solution, but AWS has a couple of other services that are 
not.  EC2 instances are virtual servers that you can treat much like physical 
hardware.

They've got a couple of other services that might be relevant, but EC2 and S3 
are probably the most so.

Original comment by Soh...@gmail.com on 23 Jan 2013 at 8:27

[GoogleCodeExporter]

As an aside, the owlapi supports gzip, we may be able to reduce overhead by 
storing and transmitting as gzip.

Another thing to look at is OWL/ZIP. See:
https://github.com/owlcs/owlapi/issues/375

For many practical purposes, most ontologies available now consist of a core 
with imports to various import modules that are distributed as part of the 
package. It may make sense to distribute as owl/zip but not totally clear how 
this fits in to the distribution infrastructure or standard URI patterns etc

cc @kltm @hdietze

Original comment by cmung...@gmail.com on 26 Mar 2015 at 11:14

[GoogleCodeExporter]

Might check the stream - it may already be gzipped as part of the http protocol 
accept: header thing

Original comment by lori.f.r...@gmail.com on 27 Mar 2015 at 5:41