Daniel Garijo

Logo guidelines

5

Widoco will display images in the description section, but there are no guidelines on how to add a logo.

Integrate with Travis for testing

2

Right now the tests are local to WIDOCO. It would be great if they were integrated with Travis so I could verify if any PR passess them

This is a security update

For the licenses, currently we put the URI returned by licensius. It would be better to add the license by the source returned by licensius, so we keep the intended...

Problem loading certain ontologies

1

I have noticed that ontologies that have duplicate ids produce errors due to the OWL API. For example: http://www.w3.org/ns/prov This works with LODE fine: http://150.146.207.114/lode/extract?url=+http%3A%2F%2Fwww.w3.org%2Fns%2Fprov&lang=en

Due to the security updates from many browsers, in order to test your documentation you have to set your own server and serve it. I think it would be nice...

Better support for SDO vocabularies

3

SDO-style vocabularies are not properly supported right now (see #274 for a partial fix). Mainly, what is needed is: - Support creating a different section with "properties" and recognize all...

Specify which namespace a concept/property belongs to

1

If you extend an ontology, the class/property will appear in non-capital letters, but it's confusing for a potential user (see example below). Instead, it should show the namespace where that...

If a property has an union domain, it won't appear in the domain of the respective classes

6

For example: name is a property and its domain is (Person or Dog). the name property will appear with 2 domains listed: Person or Dog. However in "Person" it won't...

Generating documentation of non-derreferenceable imports is problematic

10

Maybe WIDOCO could ask the user to resolve the dependencies manually if an error is detected when loading.