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

Use Widoco for the documentation of a SKOS vocabulary #641

Open
marioscrock opened this issue Oct 16, 2023 · 2 comments
Open

Use Widoco for the documentation of a SKOS vocabulary #641

marioscrock opened this issue Oct 16, 2023 · 2 comments
Assignees

Comments

@marioscrock
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Currently, the metadata are correctly parsed only if an owl:Ontology entity is defined within the ontology file. For this reason, I can generate a useful documentation page for a SKOS vocabulary only by defining as owl:Ontology the same individual of type skos:ConceptScheme (all the other SKOS properties are correctly parsed anyway).

Describe the solution you'd like
I'd propose to accept also skos:ConceptScheme as “root entity” for Widoco to generate documentation for this type of vocabulary.

Describe alternatives you've considered
I am currently adding a triple defining the skos:ConceptScheme individual as owl:Ontology.

Other alternatives:

  • Create an entity of type owl:Ontology (with the metadata) separated from the skos:ConceptScheme in the same file
  • Use a completely different tool
@dgarijo
Copy link
Owner

dgarijo commented Oct 16, 2023

This is a nice suggestion. But what happens if you have multiple conceptSchemes in a file?
If it's just a matter of adding a triple, I think it should be doable.

@dgarijo dgarijo self-assigned this Oct 16, 2023
@marioscrock
Copy link
Contributor Author

This is a nice suggestion. But what happens if you have multiple conceptSchemes in a file? If it's just a matter of adding a triple, I think it should be doable.

I think it may return a warning message and continue using the default behaviour. It would be nice to generate multiple documentation folders/files but it would imply an analysis of the file to determine which individuals are associated with each ConceptScheme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants