<div dir="ltr">Hi Oscar et al.,<br><br><br>This looks great! Thank you very mch for the prompt action.<br><br>1. I have just updated the DNS to point <a href="http://OOR.NET">OOR.NET</a> to 128.100.49.94<br>I can see the it changed at my end already (<a href="http://oor.net">oor.net</a> works now, <a href="http://www.oor.net">www.oor.net</a> still pending). You will too when the change has adequately propagated,<br>or you can query the DNS servers: <a href="http://ns53.domaincontrol.com">ns53.domaincontrol.com</a> & <a href="http://ns54.domaincontrol.com">ns54.domaincontrol.com</a><br><br>2. the mail exchanger is still pointing to one of our servers now (<a href="http://mal01.cim3.com">mal01.cim3.com</a>), please let me know the MX hostname you want to use (so I can update the dns records accordingly.)<br><br>3. looking at the <a href="http://oor.net">http://oor.net</a> page now, these are changes/issues you/others would want to make/address:<br><br>3.1 you want to redirect the point the seven oor-instance - from "OOR-sandbox" to " Sigma-KEE" - (e.g. <a href="http://colore.oor.net">http://colore.oor.net</a> ) to the link at it's immediate right (<a href="https://github.com/gruninger/colore/blob/master/ontologies/">https://github.com/gruninger/colore/blob/master/ontologies/</a> i.e. under the label "developing instance of the COmmon LOgic REpository") <div><br></div><div>3.1.1 (for 3.1) please use whatever re-direction method you are familiar with. The above will basically get s off the ground.</div><div><br></div><div>3.1.2 we used to config the apache mod_proxy to do the re-direction, as that allowed us to do slightly fancier things. (ref. <a href="https://listserv.ovgu.de//pipermail/oor-forum/2014-July/000007.html">https://listserv.ovgu.de//pipermail/oor-forum/2014-July/000007.html</a> )</div><div>But links and requirements have since changed a bit, so please work with the stewards of the various OOR instances again to get updated requirements.<br><br>3.2 I just check, and all the links work, except for: OOR-sandbox - <a href="http://sandbox.oor.net">http://sandbox.oor.net</a> - OOR sandbox instance at <a href="http://oor.ccs.neu.edu/">http://oor.ccs.neu.edu/</a> ... [attn: KenB]<br><br>3.3 the last link on the page "Goto Homepage of the <u>OOR Initiative</u>" use to point to <a href="http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository">http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository</a><br>You would want to change that noq to point to <a href="http://ontologforum.org/index.php/OpenOntologyRepository">http://ontologforum.org/index.php/OpenOntologyRepository</a></div><div><br></div><div><br></div><div>Thanks & regards. =ppy</div><div>--</div><div> </div><div> </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 27, 2016 at 7:26 AM, Oscar del Rio <span dir="ltr"><<a href="mailto:delrio@mie.utoronto.ca" target="_blank">delrio@mie.utoronto.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi Michael, Peter:<br>
<br>
I copied the page <a href="http://oor.net" target="_blank">http://oor.net</a> to Prof. Gruninger's web server.<br>
The IP address is 128.100.49.94<br>
<br>
The page can also be viewed at<br>
<a href="http://oor.mie.utoronto.ca/" target="_blank">http://oor.mie.utoronto.ca/</a><br>
<br>
and the server will also respond to <a href="http://www.oor.net" target="_blank">http://www.oor.net</a> and
<a href="http://oor.net" target="_blank">http://oor.net</a> once the DNS points to 128.100.49.94<br>
<br>
I took the liberty of adding a footnote to the page, since it is a
policy on our network that sites<br>
hosted on our servers should identify themselves as being hosted by
the University. I hope that's OK.<br>
<br>
Michael: You can edit the page directly on your STL server in the
directory /stl/WWW/OOR<br>
<br>
Regards,<br>
Oscar<br>
-- <br><span class="HOEnZb"><font color="#888888">
<div style="font-size:12px">
<div style="color:#002554"><b>Oscar del Rio</b> | Manager,
Computing Services</div>
<b style="color:#002554">Department of Mechanical &
Industrial Engineering</b>
<div>Faculty of Applied Science & Engineering | University of
Toronto</div>
<div>5 King's College Rd.| Toronto | Ontario | M5S 3G8 | Office:
MC402B</div>
<div><a href="mailto:delrio@mie.utoronto.ca" target="_blank">delrio@mie.utoronto.ca</a>
| <a href="http://www.mie.utoronto.ca/computing" target="_blank">www.mie.utoronto.ca/computing</a></div>
<div>Tel <a href="tel:%28416%29%20978-8830" value="+14169788830" target="_blank">(416) 978-8830</a></div>
</div></font></span><div><div class="h5">
<br>
<div>On 01/26/16 06:44 PM, Peter Yim wrote:<br>
</div>
<blockquote type="cite">
<pre>Thank you, Michael. Shinya and i have met, but since Shinya is still
working on the historic archival site infrastructure, he will have to
work on the OOR details later. Regards. =ppy
Hello Oscar,
ref.
</pre>
<blockquote type="cite">
<pre>In the mean time, it would be great if you can,
1. host the current <a href="http://oor.net" target="_blank">http://oor.net</a> page at a server of your choice. You would
want it on a server where you or your sysadmin have full permission to configure
apache. ... please advise IP address of that server.
</pre>
</blockquote>
<pre>[ppy] Let me know when you have the current <a href="http://OOR.NET" target="_blank">OOR.NET</a> page (you can
download from <a href="http://oor.net" target="_blank">http://oor.net</a> ) up, and advise the IP address,
If you can get that done by end of day tomorrow (2016.01.27), I can
change the DNS and point people to your server. (If not, we might have
to work on it via email, as I will start traveling, outside of the
country, on Jan-28, and may only have sporadic Internet access.
Are you familiar with apache mod_proxy, or, other site redirection
scheme(s), which you might use for this OOR index page?
Regards. =ppy
--
Peter P Yim
<a href="http://ontolog.cim3.net/wiki/PeterYim" target="_blank">http://ontolog.cim3.net/wiki/PeterYim</a>
On Tue, Jan 26, 2016 at 1:43 PM, Michael Gruninger
<a href="mailto:gruninger@mie.utoronto.ca" target="_blank"><gruninger@mie.utoronto.ca></a> wrote:
</pre>
<blockquote type="cite">
<pre>Hi Peter,
Oscar del Rio (cc'ed on this message) will be able to set things up on my servers.
thanks!
michael
</pre>
</blockquote>
<pre>
</pre>
<blockquote type="cite">
<pre>On 16-01-22 12:56 PM, Peter Yim wrote:
Hello Michael,
Fantastic!
In the past, I've been developing the webpage and the dns config, and Shinya Yamada (copied here) has been doing the apache configurations.
I will put this on the agenda when I meet with Shinya early next week and get back to you afterwards.
In the mean time, it would be great if you can,
1. host the current <a href="http://oor.net" target="_blank">http://oor.net</a> page at a server of your choice. You would want it on a server where you or your sysadmin have full permission to configure apache. ... please advise IP address of that server.
2. identify your technical contact(s), so we can start a mail thread to work through the details to get this transfer done.
Thanks & regards. =ppy
--
</pre>
</blockquote>
<pre>
On Friday, January 22, 2016, Michael Gruninger
<a href="mailto:gruninger@mie.utoronto.ca" target="_blank"><gruninger@mie.utoronto.ca></a> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre>Hello Peter,
I can host the <a href="http://oor.net" target="_blank">oor.net</a> index page and run the proxy configuration.
What do I need to know?
thanks,
michael
</pre>
</blockquote>
</blockquote>
<pre>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre>On 15-12-17 4:34 PM, Peter Yim wrote:
</pre>
<blockquote type="cite">
<pre>(re-directing this conversation to all OOR stewards and developers)
... please pick up the conversation from here. The solicitation goes
to everyone who is willing. =ppy
Dear Michael & All,
Thanks, Michael.
Great! I will include the <a href="http://OOR.NET" target="_blank">OOR.NET</a> re-direction/proxy-service in our
to-do list in my final lag of the transition from our existing servers
at the datacenter, to our long-term historic archival servers. (...
Although, for the time being, this is not at the top of the priority
list.)
While I will retain control of the zone authority (dns services) on
the <a href="http://OOR.NET" target="_blank">OOR.NET</a> domain, I will be happy if anyone is willing take over the
hosting of the <a href="http://OOR.NET" target="_blank">OOR.NET</a> index page (something similar to what we
have/had at: <a href="http://oor.net" target="_blank">http://oor.net</a> ) and to run the apache mod_proxy
configuration which was how we implemented the <a href="http://OOR.NET" target="_blank">OOR.NET</a>
re-direction/proxy-service for the various repositories (of course,
whoever that is, can choose to implement it differently as well). That
way, future configuration changes will not have to go through me/CIM3.
... Anyone? (ShinyaYamda or I, at CIM3, can help with getting that
going.)
Best regards. =ppy
--
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre>On Thu, Dec 17, 2015 at 8:34 AM, Michael Gruninger
<a href="mailto:gruninger@mie.utoronto.ca" target="_blank"><gruninger@mie.utoronto.ca></a> wrote:
</pre>
<blockquote type="cite">
<pre>Hello Peter,
yes, we should continue the OOR initiative, considering all of the work with
OntoHub and COLORE.
- michael
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre>On 15-12-17 11:29 AM, Peter Yim wrote:
</pre>
<blockquote type="cite">
<pre>Dear Michael, Till, Ken,
Further to my last msg (below):
</pre>
<blockquote type="cite">
<pre>[ppy] yes, if people decide to continue on with the OOR initiative. I do
hope you and Till might take the lead and revive that initiative. ...
Thoughts?
</pre>
</blockquote>
<pre>Thoughts!?
Thanks & regards. =ppy
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre>On Mon, Dec 7, 2015 at 7:31 PM, Peter Yim <a href="mailto:peter.yim@cim3.com" target="_blank"><peter.yim@cim3.com></a> wrote:
</pre>
<blockquote type="cite">
<pre>Hi Michael,
</pre>
<blockquote type="cite">
<pre>what is the final outcome of the migration/changeover of OOR-related
issues?
</pre>
</blockquote>
<pre>[ppy] because of other more critical issues, as well as my travels, I still
have not had the chance to fix the "oor redirect" issue yet; sorry. However,
I have updated the <a href="http://oor.net" target="_blank">http://oor.net</a> index site to link people to the right
repository locations.
</pre>
<blockquote type="cite">
<pre>In particular, will you still be managing the aliasing of the <a href="http://oor.net" target="_blank">oor.net</a>
headers?
</pre>
</blockquote>
<pre>[ppy] yes, if people decide to continue on with the OOR initiative. I do
hope you and Till might take the lead and revive that initiative. ...
Thoughts? [Michael, Till, Ken]
(... But if there is not enough desire or momentum to continue that, I'd
probably just sell that domain name and recover some of the investment . It
took me years, some luck, a lot of effort and thousands of dollars then,
before I was able to buy that domain name. )
</pre>
<blockquote type="cite">
<pre>As a reminder, we need to change the header for COLORE ...
</pre>
</blockquote>
<pre>[ppy] Thanks. Is the <a href="http://oor.net" target="_blank">http://oor.net</a> index site pointing people to the right
location for you now?
Best regards. =ppy
--
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre>On Dec 8, 2015 9:07 AM, "Michael Gruninger" <a href="mailto:gruninger@mie.utoronto.ca" target="_blank"><gruninger@mie.utoronto.ca></a>
wrote:
</pre>
<blockquote type="cite">
<pre>
Hi Peter,
what is the final outcome of the migration/changeover of OOR-related
issues?
In particular, will you still be managing the aliasing of the <a href="http://oor.net" target="_blank">oor.net</a>
headers?
As a reminder, we need to change the header for COLORE
from the old googlecode header
<a href="https://code.google.com/p/colore/source/browse/trunk/ontologies/" target="_blank">https://code.google.com/p/colore/source/browse/trunk/ontologies/</a>
to the GitHub header:
<a href="https://github.com/gruninger/colore/blob/master/ontologies/" target="_blank">https://github.com/gruninger/colore/blob/master/ontologies/</a>
thanks,
michael
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>