> On 20 May 2020, at 08:47, Rob Atkinson <[email protected]> wrote: > > > > Can you share your ontology, or better yet, reduce it to a minimal example > > that triggers the problem, so that we can investigate, fix any bugs for the > > next release, and perhaps advice on what specifically triggers the bug in > > the current release? > > > will do via email. This is an ontology that seems OK in EDG but crashed TBC
Got it, thanks, will investigate. > >> If i load the Ontology in EDG, importing via owk:imports into an empty > >> Ontology project - then run the Transform/ConvertOWL to SHACL it creates a > >> whole bunch of cruft like: ... > > Which version of EDG is this? In 6.3.2, “Convert OWL Axioms to SHACL > > Constraints” creates URIs for property shapes and not blank nodes as shown > > in your snippet, so I'm confused as to what steps exactly you took. > > 6.3.2 > > OK - this is based on exporting TTL and inspecting it - its picked up stuff > from imports - if I open the Repository and look at triples without the > imports these node shapes arent there. I didnt expect the TTL export to > include both an owl:imports statement and all the imported statements... This is the Turtle export on the Export tab of the asset collection? That doesn't include triples from owl:imported graphs. I use that frequently as a way of finding out what triples are in the asset collection's master graph. Richard -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CA50F6D1-53AB-49B4-B25E-64ABBAB44F85%40topquadrant.com.
