I think, SHACL is more about RDF, not OWL.
And there is a solution which offers RDF support out-of-the box: RDF Protege.
I think it is a little bit more appropriate platform, then the original OWLAPIv4-based Protege.
I think that the described subject could be interesting if not to the authors of this repository,
then at least to those who are faced with the limitations of the classic converters-like solutions.
close,
the discussion could be reopened if really interesting.
otherwise sorry for disturbing.
As for RDF Protege, the SHACL support can be always done in independence way.
Why?
I think, SHACL is more about RDF, not OWL. And there is a solution which offers RDF support out-of-the box: RDF Protege. I think it is a little bit more appropriate platform, then the original OWLAPIv4-based Protege.
at.ac.tuwien.shacl.plugin.syntax.JenaOwlConverter is actually a bit buggy, inefficient and limited solution (sure, this is obvious). There is a RDF-centric OWLAPI-v5 implementation that offers direct reading OWL without any converting.
I think that the described subject could be interesting if not to the authors of this repository, then at least to those who are faced with the limitations of the classic converters-like solutions.
Thanks for attention