Open fennibay opened 1 year ago
This behavior is not clear. What happens if one of the URLs to filter has subclasses? Should those be filtered then? If not, then the hierarchy would break. What about the domain and range of properties of where the domain or range should be filtered? What if you are trying to filter the URI of a property? Should the program then review the axioms in all other classes. I think the consequences of this request require some serious thinking: If you remove the terms to filter, you may significantly affect the model. If you remove only the classes but without their semantics then some work is needed. Perhaps if you have many models it is better to separate 1 html per class and render them separately.
Thank you for the quick feedback.
You're right to point out that it is not clear what it means to render one URI.
-renderURIs
renders only the triples where the specified URIs occur as a subject.Alternatively, we could restrict renderURIs
only to URIs of type owl:NamedIndividual and owl:Class, but that would couple it too strictly to OWL IMHO.
One HTML page per class would not solve my specific problem, because I really have lots of classes, with little information in each of them. Basically my model is a controlled vocabulary.
-renderURIs
would affect only the HTML output, i.e. documentation. So the completeness of the model itself is not affected, only the documentation. Conceptually I don't see an issue rendering only part of the model to HTML, because typically a given model will contain references to other models, but it's practically sufficient to focus on one model.
Is your feature request related to a problem? Please describe.
When rendering large models (e.g. with lots of classes), we see that the resulting HTML is becoming too big, not easy to show on browsers, as well as causing issues in our rendering pipeline (specifically with mkdocs; treating the rendered result as a page that is included in a mkdocs based web application).
We'd like to have feature where we can minimize the HTML content, focusing on the high-level description ("header") of the model, while still keeping the full model content in RDF files.
Describe the solution you'd like
-renderURIs
(among the existing options)Describe alternatives you've considered
Additional context
Attached you find an artificial example containing 10K subclasses with a base class: output.ttl.gz
@weissjoh