Bruce,
Again, I am sorry for my delayed reply. Replies below:
Hello,
I see one problem that I had. I had to open with TopBraid
(Semantic XML Documents) instead of just opening with XML Editor. Ok,
so I did that. I'm watching the video on youtube.com that has the
same title, opening arbitrary xml documents. When I get to open
Associations, I see nothing. It is empty. I thought I had followed
that video and was going to create an ontology using an xml file. I
was going to import into that xml file FOAF, BIO and REL, 3 web
ontologies, one of which comes with TBC.
I think, I will need to see the XML file myself. If it is a private
file, you could send it to my email address at
[email protected]
I opened a xml file that was translated from a GEDCOM (the
file format for Genealogy). So, where it uses PERSON in the XML file,
I'd change that Class to foaf:Person after importing foaf. So, if I
understand right, I'd then remove all the instance data and Save As>
name.owl. For some reason, I'm not seeing the xmap property which
would be needed to map PERSON to foaf:Person. I actually didn't get
rid of the instance data yet. So, the instance data is still mapped
to PERSON and other classes and not to foaf:Person. I guess when I
import the original xml file into the owl file then it will do the
mapping.
Again, I would need to see the file.
Further questions: (1) If you have a class in an xml file that you
imported and in a vocabulary that you use, it is a property, what can
you do? For example the GEDCOM xml has a class of NAME, which
corresponds to foaf:name which is a property.
As of TBC 3.5.1, you need to post-process the imported XML file to
transform it into the model you like. Currently (TBC 3.5.1), you can
annotate classes, but not properties for SXML mapping. However, in TBC
3.6.0 beta, you will be able to annotate both your classes and
properties for SXML mapping, so that the XML instances will map to the
instance and instance relationships that you want. There will be more
annotation options in 3.6.0 beta for classes.
So, if the XML appears like this:
<someRootInstance>
<NAME>...</NAME>
</someRootInstance>
then, in TBC 3.6.0 Beta, it will become (in TTL)
<generated-URI-of-Root-instance>
foaf:name <generated-URI-of-NAME-instance> .
(2) I have a class when the xml is imported called RELATIONSHIP, which
happens to be the name of an ontology and it is a class in the
ontology. I'm not sure if I should reuse existing ontologies like
these three and keep their structure or create my own ontology. I do
have data elsewhere that uses these ontologies. I'm just not sure how
to tell TBC that when it sees the class NAME make that into foaf:name
property and etc.
Yes, you could re-use existing ontologies - the class annotation
approach (TBC 3.5.1) and the class and property annotation approach (TBC
3.6.0).
(3) should I worry or wonder why there is nothing showing up in the
Associations view?
If there are composite:child relationships generated when you imported
the XML, then you could be able to pick composite:child property at the
Associations View and they should be displayed. If they don't, then
there is a bug there.
Gokhan
--
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
