search

dgarijo / Widoco

Wizard for documenting ontologies. WIDOCO is a step by step generator of HTML templates with the documentation of your ontology. It uses the LODE environment to create part of the template.
Apache License 2.0
295 stars 89 forks source link

Documentation of named individuals is different than that for classes and properties #731

Open Zack-83 opened 1 month ago

Zack-83 commented 1 month ago

Is your feature request related to a problem? Please describe. The documentation for named individual shows all annotation properties with the subtitle "has facts". Therefore label, definition and editorial notes appear twice.

image

Describe the solution you'd like Might the presentation become more similar to the one for classes?

image

image

dgarijo commented 1 month ago

The only thing I can think of is to add an exception in the individuals for all the properties that are already covered by notes, etc.

dgarijo commented 1 month ago

Also, with the latest addition by @marioscrock the scope note would also appear twice :)

Zack-83 commented 1 month ago

Also, with the latest addition by @marioscrock the scope note would also appear twice :)

Then no annotation property needs to be reported anymore :)

marioscrock commented 1 month ago

If for individuals all the annotation properties are automatically parsed and shown, I would suggest the opposite (i.e., to have the same representation of individuals also for classes and properties). In this way, there is no need to introduce each annotation property separately (as I did for skos:scopeNote following the example by @dgarijo of skos:editorialNote).

dgarijo commented 1 month ago

But then the properties for individuals would remain inconsistent, and the labels of properties, etc would not be translated.

El mié., 2 oct. 2024 12:13 p. m., Mario Scrocca @.***> escribió:

If for individuals all the annotation properties are automatically parsed and shown, I would suggest the opposite (i.e., to have the same representation of individuals also for classes and properties). In this way, there is no need to introduce each annotation property separately (as I did for skos:scopeNote following the example by @dgarijo https://github.com/dgarijo of skos:editorialNote).

— Reply to this email directly, view it on GitHub https://github.com/dgarijo/Widoco/issues/731#issuecomment-2388260147, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALTIGWBLUWK2KCHJ6SIEQDZZPBMTAVCNFSM6AAAAABPHIZ6Y2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBYGI3DAMJUG4 . You are receiving this because you were mentioned.Message ID: @.***>