When you import RDF, EDG will insert a subclass relationship to Thing for all classes that have no parent.
Of course, you could later remove such relationship from a class and then the class will disappear from the view. In general, having such unconnected resources that should have been deleted but were not, is not a problem, they will not cause any issues. If you want to find and remove them, then yes, use Problems and Suggestions. Or, alternatively, SPARQL. What package of EDG do you have? All collection types you have licensed appear on the left in the blue navigator. To create a new collection, click on one of the types and then click on Create. By default, all users can create new collections. However, your organization may set up permissions such a way that only certain users can do this. You would need to discuss this with your EDG administrator. If you can’t and/or should not be creating new collections, then you would have to import your data into one of already existing collections. > On Aug 5, 2019, at 4:00 AM, Stefan Verweij <[email protected]> wrote: > > Thanks, I indeed discovered if something is not (in)directly linked to Thing > it will not be visible.So I deleted them manually by navigating and using the > 'Problems and Suggestions' option to find unlinked properties resulting in > errors. Since I am not the manager I do not have the right permissions to use > the manage tab to configure root, so the only ways to find unlinked classes > and properties is by using Problems and Suggestions (or manually scrolling > through the lines of code)? > > About the validation, thanks again for the problems and suggestions option, > it helped debugging the ontology. I have one question about importing my > instance data: Where do I create a Data Graph collection? If I understand it > correctly I have to create a collection in 'Data Assets collections', but, > again, since I am not the admin nor a manager I cannot create one. So the > only option is by importing instances through the import tab then? > > Again, thanks for all the valuable help! > Stefan > > Op vrijdag 2 augustus 2019 15:26:14 UTC+2 schreef Irene Polikoff: >> >> Yes, I believe currently if you delete a class, the associated property >> shape gets deleted, but not the property itself. >> >> Since you found the property, just click on Delete button to remove it. >> >> Problems and Suggestions will validate the collection you are in. It will >> validate either everything in it (including information in the included >> collections) or, optionally, only resources of a certain type. The >> validation will be against the shapes found in the collection - directly or >> because they are included through owl:imports. In other words, in the >> validation the current collection is used as both, the data graph and the >> shapes graph. >> >> You could load your instance data into your ontology or, better, create a >> Data Graph collection and load it there. Then you can validate it. >> >> If you decide to use Data Graph collections, note that when you create one >> you will need to select an Ontology it is based on. It must contain the >> schema (shapes) your data will be based on. >> >> In the Ontology, you'll need to declare classes which instances you will be >> storing in the Data Graph ‘public classes’ of its GraphQL Schema. This can >> be done once on a parent class if these classes have a common parent. This >> set up step is explained here: >> http://wiki.topquadrant.com/display/master/Ontology+View+or+Edit#OntologyVieworEdit-SHACLrequirementsforworkingwithReferenceDatasetsandDataGraphs. >> >> If your data is based on SKOS, you could also use a Taxonomy to store it. >> >> You may not need to convert CSV data outside of EDG. EDG lets you import >> data from CSV, converting it to RDF. This option is available under Imports >> tab. > >> Op vrijdag 2 augustus 2019 18:04:51 UTC+2 schreef Irene Polikoff: >>> >>> One more thing to add about “invisibility to the user”. >>> >>> I expect that by this you mean that they do not show in the class >>> hierarchy. Class hierarchy starts with a root class (by default owl:Thing) >>> and shows all subclasses, then their subclasses, etc. Root can be >>> configured on the Manage tab. >>> >>> Under each class, properties associated with it are shown. >>> >>> So, if something does not show in the hierarchy, it does not mean it does >>> not exist and was deleted. It simply means that it is not connected in the >>> way this particular view expects. As you have discovered, user can still >>> find and navigate to these resources. > > -- > 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/4067ddbf-81ff-4c77-b89f-c038c9ecce99%40googlegroups.com. -- 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/AE38CE29-73D5-491A-97FD-06BE1D5EECD5%40topquadrant.com.
