<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Dear OOR community,<br>
<br>
there has been some feedback on the new Ontohub architecture at <br>
<a class="moz-txt-link-freetext" href="https://gist.github.com/tillmo/dc97c81e7bef75cbe93b85a0a1153d8e">https://gist.github.com/tillmo/dc97c81e7bef75cbe93b85a0a1153d8e</a><br>
Many thanks!<br>
<br>
Since this gist page unfortunately does not send out notifications
on new entries, I suggest to continue the discussion on this email
list.<br>
<br>
Basically, there are several issues and suggestions:<br>
1) use of git as backend, instead of some CMS. Currently, we are
inclied to stay with git, since it is quite popular and also used
by COLORE. Note that does *not* mean use of github! An alternative
suggestion is the use of a CMS (possible attractive features being
social software features and support for workflows). Do you know a
suitable candidate? It should support version control. I would be
interested in what the differences between this version control
and git are. Maybe there is even a CMS with git version control?<br>
2) re-use of NCBO technology. Here, the question is: how much is
the NCBO technology tied to OWL?<br>
3) use of Ruby on Rails as backend. Here, the main argument is the
possible re-use of existing Ontohub code and programming skills.
However, note that Ruby on Rails has a much smaller role, because
we intend to use ember.js (written in Javascript) for the
frontend. Are there specific alternative suggestions?<br>
<br>
Further comments and suggestions are welcome!<br>
<br>
All the best,<br>
Till<br>
<br>
Am 28.08.2016 um 00:56 schrieb Till Mossakowski:<br>
</div>
<blockquote
cite="mid:a2437bbf-202a-1d82-c45c-a73901ceb200@iks.cs.ovgu.de"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=utf-8">
<p>Dear users and friends of Ontohub,</p>
<p>the Ontohub development team has decided to re-implement <a
moz-do-not-send="true" href="https://ontohub.org">Ontohub</a>
from scratch for several reasons, see<br>
</p>
<p><a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://gist.github.com/tillmo/dc97c81e7bef75cbe93b85a0a1153d8e">https://gist.github.com/tillmo/dc97c81e7bef75cbe93b85a0a1153d8e</a></p>
<p>Feedback, discussion and support are welcome. However, please
do not reply to this email (that would not reach all its
recipients), but give feedback directly at the above URL. For
writing, you need to sign up at github, which however is very
easy.<br>
</p>
<p>All the best,</p>
<p>Till<br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">
_________________________________________________________________
Message Archives: <a class="moz-txt-link-freetext" href="https://listserv.ovgu.de/pipermail/oor-forum/">https://listserv.ovgu.de/pipermail/oor-forum/</a>
Subscribe: <a class="moz-txt-link-freetext" href="mailto:oor-forum-subscribe@ovgu.de">mailto:oor-forum-subscribe@ovgu.de</a>
Config/Unsubscribe: <a class="moz-txt-link-freetext" href="https://listserv.ovgu.de/mailman/listinfo/oor-forum">https://listserv.ovgu.de/mailman/listinfo/oor-forum</a>
Wiki: <a class="moz-txt-link-freetext" href="http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository">http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>