Irene and Scott, I will try out the suggested techniques and see how they work for me. I never thought of using the basket, but it seems like it would probably solve my problem. Thank you for your rapid replies!
/Karl On 23 Feb, 16:49, "Irene Polikoff" <[email protected]> wrote: > Finally, you can open with TBC any ontology you want to map to, place a > resource(s) you want to map to into the basket and then open your ontology. > Resources will still be in the basket since the basket works across > ontologies. They will be shown as full URIs not as qnames if the namespace > in question is not imported by your ontology. You can then use resources in > the basket for your mapping operations. > > In this approach when you save and reopen your ontology you will get an > information message saying that you are using resources from a namespace > that is not imported. Just ignore it. > > > > -----Original Message----- > From: [email protected] > > [mailto:[email protected]] On Behalf Of Scott > Henninger > Sent: Tuesday, February 23, 2010 10:33 AM > To: TopBraid Composer Users > Subject: [tbc-users] Re: Hiding imported classes/properties > > Karl; First I'd like to make a plea that this is a difficult design > decision face by all ontology editors. Yes, some of these models are > excessively verbose, foaf being a prime example. But there is > currently no standard resolution to the problem, so defining our own > endangers standardization and interoperability. Composer is designed > for ontology modelers, so the tradeoff of accuracy and standards vs. > making it "easier on the eyes" will always fall on the accuracy and > standards side. > > That said there is another tool to use, which is the search box at the > bottom of the property/class pane. It may seem like an extra and > unnecessary step, but I can confirm that this will become second > nature when working with verbose models. It works quit well. > > Lastly, take a look athttp://sparqlpedia.org/rdfex/ Partial imports > are supported by Composer for foaf, dc, tcterms, sioc and skos. For > example, if you want to restrict foaf import, go to the import tab and > open Import from URL with the following URL example: > > http://rdfex.org/foaf/firstName,givenname,knows,mbox_sha1sum,depictio... > r > > You can also use the Basket Batch operation 'Add partial imports via > RDFex'. Add all of the resources you want to partially import into > the basket and choose the operation. This will create the partial > imports and you can then remove the full imports. > > For other models, you can create your own copy of the model, edit as > desired, and store in the workspace. If you use the same base URI, > then it will work in other workspaces/editors, but with the full model > instead of your edited model. > > -- Scott > > On Feb 23, 1:05 am, Karl Hammar <[email protected]> wrote: > > Irene, > > > I have noticed this option previously. However, while making the > > overview a little easier on the eyes on the macro level, it brings > > with it the problem that class and property inheritance is no longer > > shown, rather the namespaces become completely flat which is also > > useless. I still need class and property inheritance to be shown > > properly so that I can work easily with the ontology, but without the > > overcrowding caused by all of the properties and classes from the > > imported ontologies that I do not use. > > > Searching this group I've found the following thread, indicating that > > a request for this feature is something that have been in your > > bugtracker for over two > years:http://groups.google.com/group/topbraid-composer-users/browse_thread/. > ... > > Is it a feature that you are planning to implement at some point? Such > > a feature is in my view a necessary requirement if one is to use > > TopBraid Composer to interconnect one's own ontologies with these > > large standardized semantic web ontologies in an efficient manner - > > without it the tool becomes almost unworkable as the number of > > imported classes and properties grow. > > > I should also say that apart from this oversight I am very happy with > > TopBraid Composer on the whole, it is by far the best ontology > > development environment that I have tried and I am trying to get my > > colleagues to use it. However, I believe you will make the job of > > promoting your tool significantly easier if a feature such as the one > > described is added. > > > Best regards, > > > Karl Hammar > > > On 23 Feb, 04:39, "Irene Polikoff" <[email protected]> wrote: > > > > Karl, > > > > Try "group by namespace" option to see if it helps. It is accessible > from an > > > icon at the bottom left of the Properties and Classes views. > > > > Regards, > > > > Irene > > > > -----Original Message----- > > > From: [email protected] > > > > [mailto:[email protected]] On Behalf Of Karl > Hammar > > > Sent: Monday, February 22, 2010 10:08 AM > > > To: TopBraid Composer Users > > > Subject: [tbc-users] Hiding imported classes/properties > > > > Hello all, > > > > I've got a problem with TopBraid composer becoming extremely cluttered > > > when I import some large online ontologies, and I'm starting to think > > > that I must have missed something about how to do such things. > > > > My story: I have an ontology that I want to align with BIBO and FOAF, > > > for the sake of improving interoperability by utilizing standardized > > > base classes and properties. Thus, I import BIBO and FOAF into my > > > ontology using the Imports tab of Composer, and start to connect my > > > classes as being subclasses of various BIBO and FOAF classes. However, > > > since these two ontologies are fairly large my lists of properties and > > > classes now become extremely cluttered and more or less impossible to > > > navigate efficiently. > > > > Things raises two questions: > > > > 1) Am I going about things in the wrong way entirely? Is there another > > > easier way of saying that my entities are subentities of things in > > > these standard ontologies, besides importing the whole ontologies? > > > > 2) If not, is there any way of filtering what I get to see when using > > > TopBraid Composer, so that I can filter out all of the properties and > > > classes from the imported ontologies that are irrelevant to me? > > > > Any feedback is much appreciated! > > > > Best regards, > > > > Karl Hammar > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "TopBraid Composer Users" group. > > > To post to this group, send email to > > > [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]. > > > For more options, visit this group > athttp://groups.google.com/group/topbraid-composer-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "TopBraid Composer Users" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/topbraid-composer-users?hl=en. -- You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en.
