Using owl:sameAs and also issue with geonames ontology
brucewhealton
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
Tim Smith
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
Bob Ducharme
I agree with Tim, that assigning rdf:type values of both foaf:Person and
cv:Person to the same instance is the simplest approach.
The geonames ontology at
http://www.geonames.org/ontology/ontology_v2.2.1.rdf assigns the gn: prefix
to the http://www.geonames.org/ontology# URI, and the one included with
TopBraid assigns the ontology: prefix, so you would see the name property as
either gn:name or ontology:name in TopBraid Composer's Properties view,
depending on which one you use.
The geo: prefix is most often used with the W3C's Geo Positioning ontology
(http://www.w3.org/2003/01/geo/wgs84_pos), which is separate from the
geonames one and included with TopBraid as wgs84_pos.rdf. This ontology does
not include a name property, but does have alt, lat, long, and lat_long
properties, so perhaps that is what you saw.
Instead of choosing between the geonames and wgs84_pos ontologies, you can
easily import both into the same project and use them together.
Bob DuCharme
TopQuadrant
Hi Bruce,
Hope that helps,
Tim
--
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
topbrai...@googlegroups.com
To unsubscribe from this group, send email to
topbraid-user...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en