You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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.
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 asowl:Ontology
the same individual of typeskos: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 asowl:Ontology
.Other alternatives:
owl:Ontology
(with the metadata) separated from theskos:ConceptScheme
in the same fileThe text was updated successfully, but these errors were encountered: