essepuntato / LODE

Live OWL Documentation Environment, to convert OWL ontologies into HTML human-readable pages.
ISC License
104 stars 55 forks source link

web version offline #21

Closed jaygray0919 closed 5 years ago

jaygray0919 commented 5 years ago

the LODE web services seems to be offline.

tfrancart commented 5 years ago

+1 The web version is down and I do have a couple of project that suffer from this unavailability. @essepuntato can you do something about it ?

essepuntato commented 5 years ago

We did a major issue with the server that is hosting it, and I don’t know when we will be able to put it up again. I’m trying to figure out if we can to move it on another machine, but I’m not entirely sure it is feasible right now.

Il giorno 21 giu 2019, alle ore 09:20, Thomas Francart notifications@github.com ha scritto:

+1 The web version is down and I do have a couple of project that suffer from this unavailability. @essepuntato can you do something about it ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

essepuntato commented 5 years ago

The online version is now usable at another URL, starting with https://w3id.org/lode, e.g. https://w3id.org/lode/owlapi/http://purl.org/spar/cito.

fosterlynn commented 5 years ago

Thank you!! It was very useful for us, and we never found a replacement that gave that same single page output, and that worked.

dr-shorthair commented 5 years ago

FWIW my mate @nicholascar has cloned LODE in Python - an API is described here https://kurrawong.net/pylode-online

tfrancart commented 5 years ago

@fosterlynn Widoco (https://github.com/dgarijo/Widoco) was our offline choice as a replacement for LODE. It integrates LODE in a more comprehensive OWL documentation solution. (any plan to update the ValueFlows documentation generation ?)

fosterlynn commented 5 years ago

Thank you very much @dr-shorthair and @tfrancart .

any plan to update the ValueFlows documentation generation ?

Yes for sure; we will look into the options you have mentioned, and also consider the moved LODE. The quick solution we implemented (Protege run locally then static output loaded to a server) is very much less than ideal. For ValueFlows, we still probably need an online solution, but are interested in everything that was mentioned. Thanks again for your help!

fosterlynn commented 4 years ago

any plan to update the ValueFlows documentation generation ?

Done, thanks again to all.