Closed sasjonge closed 8 months ago
To some extent, we follow the IRI conventions defined in https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#fibo-standard-iri-format. In particular, in order to make a difference between web documents and real-world objects (see: https://www.w3.org/TR/cooluris/), we assume that all ontology IRIs end with the '/'.
Do you have any issues with ontologies that follow this convention?
Thank you for your quick reply.
No, then I don't have further issues. I believe it could be a good idea to the information about the standard iri format into the "... with an ontology of your choice" section of the readme.
Hello, I'm trying to run the onto-viewer with a custom ontology (I use the pizza.owl for now, as a minimal example), but the onto-viewer , does not work as expected when I'm following the short tutorial in the Readme. The search seems to work, but if I choose an entity I get a 404 page. Also, the type hierarchy on the left is missing.
Is there generally a problem with ontologies where the IRI's do not end with "/"
Expected Behavior
Entity pages and type hierarchy for custom ontologies are shown as expected
Current Behavior
The page shows a 404 error, and the URI also seems strange, for example http://localhost:8080/dev/ontology?query=http://www.co-ode.org/ontologies/pizza/pizza.owl%23Hot
Context (Environment)
I tried to set up a minimal example with the pizza.owl in my fork.
This does not work, but I'm unsure if I'm missing something in the config files.
Detailed Description
It would be nice to have a more concrete example of running onto-viewer with a custom ontology, like the pizza.owl