Hi Bruce, Without knowing anything about your intended use of your ontology and instances, I'm going to take a guess and suggest that you can make an instance of foaf:Person and then make the same instance an instance of cv:Person by dragging the cv:Person class onto the rdf:type property in the form view of the instance. This will create a single resource that is both a cv:Person and foaf:Person, eliminating the need to use owl:sameAs.
If you need to use owl:sameAs, you can find it by going to the properties window, and clicking on "Preferences" on the drop-down menu. You can then select the system properties you would like displayed in the properties window including owl:sameAs. I don't have any ideas regarding what you are seeing with respect to the geonames import. Hope that helps, Tim On Aug 3, 6:18 pm, brucewhealton <[email protected]> wrote: > Hello, > I imported the resume-rdf vocabulary into a file using the > import from URL option. I want to see if I am doing this right. This > vocabulary has its own class for a Person. I thought that I needed to > create an instance of both a foaf:Person and cv:Person (the prefix for > resume-rdf is cv) and then use owl:sameAs to equate them. > Unfortunately, I couldn't even find the owl:sameAs option to try to > relate these two Instances together and say they are about the same > person. > I also found it strange that when I imported geonames > ontology from the web, I didn't see many of the properties that are > part of the specification. For example, geo:name. I only have > altitude, lat/long, latitude, location and longitude. > Thanks, > Bruce -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. 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-users?hl=en
