Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add skos:editorialNote in the generated documentation #592

Closed
fsutter opened this issue Jun 5, 2023 · 9 comments
Closed

Add skos:editorialNote in the generated documentation #592

fsutter opened this issue Jun 5, 2023 · 9 comments
Labels
enhancement pressing Will fix issue in next release
Milestone

Comments

@fsutter
Copy link

fsutter commented Jun 5, 2023

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
Copy link
Owner

dgarijo commented Jun 6, 2023

@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
Copy link
Author

fsutter commented Jun 6, 2023

@dgarijo yes exactly.
Thanks

@dgarijo
Copy link
Owner

dgarijo commented Jun 6, 2023

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

@dgarijo dgarijo added this to the v1.4.xx milestone Jun 6, 2023
@fsutter
Copy link
Author

fsutter commented Jun 6, 2023

Great, when is the next release planed?
Thanks

@dgarijo
Copy link
Owner

dgarijo commented Jun 6, 2023

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

@dgarijo dgarijo added the pressing Will fix issue in next release label Jun 6, 2023
@andre-hui
Copy link

andre-hui commented Jul 4, 2023

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
Copy link
Owner

dgarijo commented Jul 5, 2023

@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
Copy link

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

@dgarijo
Copy link
Owner

dgarijo commented Jul 5, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement pressing Will fix issue in next release
Projects
None yet
Development

No branches or pull requests

3 participants