I first used OntoWiki around 2013 for the GeoKnow research project to let the project team collaboratively edit the research project structure (work packages, tasks and deliverables) of the GeoKnow project and to publish it on the web page.
It was modeled around the FP7 research ontology http://purl.org/research-fp# created just for that but it doesn't seem to be used by anyone else anymore and the link is dead as well.
My PHP skills don't extend beyond small websites and I didn't know quite how to set it up but I think Michael Martin did it for me on the GeoKnow Ubuntu virtual server. One early pain point was the default setting to give everyone write access, which makes sense for a Wiki but caused automatic web crawlers to traverse delete links, causing many mysteriously deleted resources until we figured out that there were no mysterious bad guys and disabled anonymous write access.
This issue persists to 2021 (using OntoWiki 1.0.0), so my recommendation is to disable write access for the anonymous user by default or at least prevent deleting resources by opening URIs alone. This problem is described in more detail in https://symbolicdata.github.io/OntoWiki.
After that it worked really well and I think it was a perfect fit with OntoWiki and the site extension because there are just a few classes like milestone, project, deliverable and so on, and those could are shown both in numbered lists as well as in detail views that are hierarchically linked using OntoWiki site-extension templates.
For example, http://geoknow.eu/wp2.html shows the detail view of work package 2 but also shows the other work packages in the sidebar and all tasks associated with that work package in a list below.
I was really impressed by how we could create and edit such a nice website for a multi million euro research project with such ease, including multi-user concurrent access, backups and so on.
I think if we went to a web developer or company and asked for a website with that feature set including a CRUD editor, backups and so on it would have been quite costly.
Finally, when the project was finished and there were no more changes, we wanted to keep it online indefinitely but also minimize the effort to maintain it, so the we just made a static copy of the entire website using the Linux wget tool with recursive traversal of the generated HTML files.
That static web site is still rock solid many years later and will probably be for as long as the server exists, because the result is just static HTML without much JavaScript or other dynamic content that could somehow break.
Properties
small amount of data
site extension
simple structure
All in all, full marks from me for OntoWiki + site extension for the GeoKnow use case.
GeoKnow
I first used OntoWiki around 2013 for the GeoKnow research project to let the project team collaboratively edit the research project structure (work packages, tasks and deliverables) of the GeoKnow project and to publish it on the web page. It was modeled around the FP7 research ontology http://purl.org/research-fp# created just for that but it doesn't seem to be used by anyone else anymore and the link is dead as well. My PHP skills don't extend beyond small websites and I didn't know quite how to set it up but I think Michael Martin did it for me on the GeoKnow Ubuntu virtual server. One early pain point was the default setting to give everyone write access, which makes sense for a Wiki but caused automatic web crawlers to traverse delete links, causing many mysteriously deleted resources until we figured out that there were no mysterious bad guys and disabled anonymous write access. This issue persists to 2021 (using OntoWiki 1.0.0), so my recommendation is to disable write access for the anonymous user by default or at least prevent deleting resources by opening URIs alone. This problem is described in more detail in https://symbolicdata.github.io/OntoWiki.
After that it worked really well and I think it was a perfect fit with OntoWiki and the site extension because there are just a few classes like milestone, project, deliverable and so on, and those could are shown both in numbered lists as well as in detail views that are hierarchically linked using OntoWiki site-extension templates. For example, http://geoknow.eu/wp2.html shows the detail view of work package 2 but also shows the other work packages in the sidebar and all tasks associated with that work package in a list below. I was really impressed by how we could create and edit such a nice website for a multi million euro research project with such ease, including multi-user concurrent access, backups and so on. I think if we went to a web developer or company and asked for a website with that feature set including a CRUD editor, backups and so on it would have been quite costly. Finally, when the project was finished and there were no more changes, we wanted to keep it online indefinitely but also minimize the effort to maintain it, so the we just made a static copy of the entire website using the Linux wget tool with recursive traversal of the generated HTML files. That static web site is still rock solid many years later and will probably be for as long as the server exists, because the result is just static HTML without much JavaScript or other dynamic content that could somehow break.
Properties
All in all, full marks from me for OntoWiki + site extension for the GeoKnow use case.