EDG does not edit ontologies in TTL files. To use EDG, you create an ontology using EDG and Import RDF the TTL files into those ontologies. The ontologies are persisted in the RDF database, not TTL files. That’s how you get the nice features like Working Copies, history, revert of change, etc.
FYI in EDG you can “view” TTL files though. Create an EDG ontology and “Include" the ontology from the TTL file you’ve deployed to the server, then you can see the classes, etc in the importing ontology. Cheers, David UK +44 7788 561308 US +1 336 283 0606 > On 19 Jul 2017, at 15:33, Semantics Matter <[email protected]> wrote: > > Hello, > > We are in the middle of an EDG evaluation pilot. I have a collection of 20 > models in .ttl format with many imported into a core model and that core > model import to an extension model. Every .ttl file opens in TBC-ME and the > imports all work fine. However, when I import the project to EDG, I can see > the project exists in the admin interface, but none of the models are visible > in the UI. Uploading an archive file through the Project Upload or direct > upload through TBC ME export to TBL server makes no difference. > > I have folks ready to edit these files in EDG at 2:00 today. > > Thank you > > -- > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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]. For more options, visit https://groups.google.com/d/optout.
