Bruce,
Try Import -> Existing Project into a workspace. Copying and refreshing
should work as well, but it is less reliable.
To answer you other question, semantically, saying that A
owl:equivalentClass B is the same as saying A rdfs:subClassOf B and B
rdfs:subClassOf A. And if you say that A rdfs:subClassOf B and X rdf:type A,
it means that X rdf:type B. However, SPARQL query engines don't know any of
this, so you would need to either run inferencing or change your queries.
For example, instead of saying:
WHERE {?x rdf:type :A}
you would say WHERE {?x rdf:type ?class. class rdfs:subClassOf* :A}.
* tells SPARQL to do the transitive closure on subclasses. You can read more
about the various operators and options included in SPARQL in the SPARQL 1.1
spec. This query pattern works when you have the explicitly stated subclass
statements. But if you say A owl:equivalentClass B, you don't have the
explicit statement that B is a subclass of A, so you will still need to do
inferencing to get the subclass statements.
For your last question, if you change your vocabulary, you need to publish
the entire new version, just like if you changed a program or an XML Schema
you would publish an entire new version.
Regards,
Irene Polikoff
From: [email protected]
[mailto:[email protected]] On Behalf Of Bruce Whealton
Sent: Thursday, September 27, 2012 12:49 AM
To: [email protected]
Subject: [topbraid-users] Aligning Classes in TBC and publishing customized
versions of a vocabulary
Hello,
Before I ask my main question, I wanted to ask about something
else. I installed TBC on a different disk on my system. I copied the
project folders I had in the workspace I had on my C drive into the new
workspace for TBC on my D drive. None of the older and existing
folders/projects were showing up, even when I did a refresh.
I would like to share two scenarios and see if I can get feedback
on this.
First, let's say that I want to use FOAF for defining FOAF files about a
person AND I want to use resume/CV vocabulary for describing a CV associated
with that person. So, I used foaf:Person owl:equivalentClass cv:Person.
Would it be correct to assume that I must now run a reasoner to make all
members of foaf:Person to be members of cv:Person also?
In the "Learning Sparql" book by Bob Ducharme, I noticed in one
place something similar to this was done but I believe RDFS and the Class
and Subclass hierarchy was used. So, maybe that is different. It might have
been about the issue of determining a rule for defining an aunt. It was
stated that since aunt is a sub-class of foaf:Person then every person that
is an aunt is also a foaf:Person, based on the RDFS sub-class structure.
Apparently no reasoner was needed to run in order to make this work, either
temporarily or by asserting it explicitly in the triple store.
The other example is for describing with schema.org, foaf and
Dublin Core, a Semantic Web version of a Poetry Magazine. It would have
poem, author, publisher and editors. I want to align these vocabularies so
that all dc:authors are foaf:Persons, and schema.org author or writer. So,
do I need to use owl:equivalentClass and then run a reasoner on this? I
would like to have RDF files for Published Poems and have it automatically
recognize that dc:author is a foaf:Person, and also use the appropriate
additional relationships handled automatically without having to display
things explicitly. I had wondered whether I need to use some other
vocabularies that are used for aligning different ontologies... or perhaps
using the open vocab vocabulary and add some additional properties to that.
Lastly, suppose I had an ontology like the Relationships ontology that
is extended from FOAF. And I need to add one or two additional properties
and/or classes. When I go to publish my modified vocabulary, called my-rel,
do I:
1) Include the entire Relationship ontology with my two additional terms, or
2) Just publish a copy of my-rel that has only the 1 or two additional
properties and Classes?
Thanks in advance for any help,
Bruce
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise
Vocabulary Network (EVN), TopBraid Composer, TopBraid Live,
TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages 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
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live,
TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages 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
