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
284 stars 88 forks source link

Add skos:editorialNote in the generated documentation #592

Closed fsutter closed 1 year ago

fsutter commented 1 year ago

Hi,

I've a lot of skos:editorialNote annotations in my RDF. Is it possible to have them displayed in the generated documentation? If so, how?

Many thanks in advance and kind regards,

dgarijo commented 1 year ago

@fsutter, it's quite simple to add the property, but you need to extend the xslt file for conversions. What would be the header of the property? editorial note?

fsutter commented 1 year ago

@dgarijo yes exactly. Thanks

dgarijo commented 1 year ago

it's a simple extension, I can do it for the next release

fsutter commented 1 year ago

Great, when is the next release planed? Thanks

dgarijo commented 1 year ago

When I have the time :) It's going to take a bit, since I just did a release last week.

andre-hui commented 1 year ago

Hello! Just wondering, would it be very taxing to add in a config file or similar which can be edited to determine which properties (and their labels) are generated? For example, being able to also generate skos:scopeNote would be really helpful. (I guess it would be a bonus if this could somehow be declared within the ontology itself, like how you did for ontology metadata... maybe if you declare a namespace for WIDOCO config and then have terms in that namespace be predicates/objects of object/datatype properties in the ontology of interest, or something like that, similar to what Sparnatural does for their config)

See https://www.ica.org/standards/RiC/RiC-O_v0-2.html for what I mean by a custom property that was generated in the html ("Mapping to to RiC-CM v0.2")

dgarijo commented 1 year ago

@andre-hui, Widoco uses a xslt transformation to go from owl into html (based on LODE). So in order to add new custom properties, you'd have to edit the xslt mapping file. Devising a flexible mechanism to include custom properties so they are edited in the xslt on the fly so everything work is not trivial. Plus, the labels to all supported languages would also have to be declared. If you do it in the ontology, then you would have to filter afterwards the corresponding individuals so they don't appear in the documentation.

andre-hui commented 1 year ago

Thanks for letting me know! Appreciate that you took the time to reply.

dgarijo commented 1 year ago

I'll provide some insight int how to edit the xslt to support your own stuff.