AKSW/OntoWiki

how and why did this end?

koo5 opened this issue · 6 comments

koo5 commented
how and why did this end?
white-gecko commented

Related to #440.

The main reason for us not continuing with this code base is, the switch of PHP from 5 to 7 and the foundation of OntoWiki on Zend Framework 1. Migrating to PHP 7 would involve migrating to Zend Framework 2 for which we did not have enough capacity.

However, with a combination of

and possibly more tools we try to build a more flexible tool stack that hopefully will eventually satisfy most of the OntoWiki use cases.

white-gecko commented

I'm curious what your use cases is for OntoWiki and why you are interested in it.
I have opened this repository to collect use cases, I would like to read yours: https://github.com/AKSW/OntoWiki.UseCases

  • 👍2
koo5 commented

Thanks! The followup projects you link are definitely intriguing to me (i am also building something comparable to jekyll-rdf). There was no particular clear-cut usecase for OntoWiki that i had in mind, just the vague thought that it was roughly the right direction ..

seebi commented

@koo5 Another reason was that parts of our research group spin-off eccenca as a company in order to create a product out of OntoWiki. We fastly failed with this, decided to re-implement parts of OntoWiki as DataManager which is now part of eccenca Corporate Memory :-)

  • 👍1
alfureu commented

Hi, I just discovered this project and I was also wondering what other (relatively simple) solutions are out there if this is not maintained anymore. Totally new to the topic...

KonradHoeffner commented

@seebi, @white-gecko:
Just a quick question from 2024: Would you still recommend a combination of OntoPad, QuitStore and jekyll-rdf for free vocabulary/simple ontology collaborative editing on the web and eccenca Corporate Memory as a non-free option or has the landscape changed in the last years?
We are looking for something where you can also create a class hierarchy and maybe a few more RDFS/OWL features but it should also be easy to use for domain-experts for whom Web Protégé is too complicated.

P.S.: Maybe others have similar questions, I suggest 1-2 sentences with an archival notice and maybe a link or two to essenca and other recommendations on top of the readme file.

  • 👍1