Hi Bruce,

Importing of XML is covered in the TBC Help at TopBraid Composer > Import
and Export > Import external information > Import XML. It creates a set of
triples that retain all information from the XML file, including element
ordering information, and creates a namespace based on the imported file's
name and folder location. 

The triples that get created are really a starting point so that you can
then use SPARQL to convert them to triples conforming to the ontology that
suits your application. Along with that conversion, you would import the
relevant ontology or ontologies. For example, if you had XML of address book
information and used SPARQL to convert the post-import triples into a graph
that uses classes and predicates from the vcard ontology, you would also
import the ontology that defines those classes and predicates
(/TopBraid/Common/ns.rdf in the Navigator view) into the new graph.

A manual way to create smaller files from a larger one would be to use TBC's
SPARQL View to query for the triples you want in one file and then, over the
SPARQL query results, click the floppy disk icon to save that data as a
file. A more common approach would be to write a SPARQLMotion script that
uses the Export to RDF File module to save the desired data. 

Scott mentioned in another email that http://localhost:8083/tbl is the URL
that gives a browser access to the personal server. (Make sure that TBC is
running when you send your browser there; I've tried to send a browser to
that URL without realizing that TBC wasn’t even running too many times
myself.)

The 71 page document is the Application Development Quickstart Guide at
http://www.topquadrant.com/docs/tbc/AppDevQuickstartGuide.pdf . Another
important introduction to TBC is the Getting Started guide at
http://www.topquadrant.com/docs/marcom/TBC-Getting-Started-Guide.pdf , which
covers the features available in TBC for building and editing ontologies in
more detail. This was also recently updated. 

TBE is bundled with TBC and the personal server. The
http://localhost:8083/tbl URL leads to several TBE applications, and you can
create variations on these by adding, deleting, and modifying interface
components and then saving the TBE app with a new name, all from the
browser. Chapter 6 of the Application Development Quickstart Guide will get
you started with this, and chapter 8 describes how to call a SPARQLMotion
script from a TBE application.

In the TBC Help, see TopBraid Composer > User Interface Overview > RDFa
editor to learn about creating RDFa with TBC. 

Holger Knublauch, our VP of R&D, was responsible for Protégé's original OWL
support before coming to TopQuadrant. I haven't looked at Protégé in a few
years, but I know that it doesn't provide the application development
capabilities that TBC does, and as you mention they don't offer many
features for editing instance data. The Getting Started guide mentioned
above should get you off and running with ontology development in TBC so
that you won't need Protégé anymore. 

Bob DuCharme
TopQuadrant


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of brucewhealton
Sent: Friday, August 26, 2011 2:32 PM
To: TopBraid Suite Users
Subject: [topbraid-users] Working with Arbitrary XML to convert to RDF, also
local server

Hello,
            My first question is somewhat of a newbie issue to TBC.  I
wanted to do something with Genealogy for a project and so I started
by converting a couple GEDCOM files to XML.  GEDCOM is the format used
by Genealogy - it is standard, as it were.
           So, the XML file returned has no namespace definitions.  I
thought I'd make certain tags appear as sub-properties and sub-classes
of other vocabulary classes and properties.  How would one go about
doing this, what's going to be the best way?  Import it into a RDF
file?  Or just open the XML file in TBC and import other vocabs?  I'm
not sure how to then get from an arbitrary XML file into an OWL or RDF
file.
        Oh, how hard would it be to take one large XML file and also
produce individual files for each defined person in the XML version of
the GEDCOM - so I would have one large RDF file and several smaller
files?

        I have a couple other questions.  I am using TBC - Maestro
Version still in trial period.  The personal server is mentioned.
Does it need to be installed somewhere special for it to work?  I
tried browsing to the link given and nothing came up.  I thought that
the personal server came with ME.
        I finished the overview tutorial and I'm going through the API
tutorial document that is about 71 pages long.  Are there any other
documents that I should read, or tutorials, to get a feel for what can
be done?  I was wanting to see about generating RDFa and so I had
skipped a few chapters that seemed to deal with the TBE - Ensemble,
which I thought was a separate product from what I downloaded.
 I asked a lot of questions here, I hope that they can be addressed
individually... thanks so much for your help...
One last, how does TBC compare with a product like Protege from
Stamford?  Would there be a reason to use them together.  Protege
seems to be aimed at specifically creating ontologies and they don't
support working with Instance data too well.
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

-- 
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

Reply via email to