Problems using TopBraid Composer

[Bruce Whealton]

Hello,
           I am having a problem with my installation of TBC.  I had reinstalled TBC on a system that I had upgraded to a new OS.  I had TBC point to the old workspace area.  I had imported the resume/cv ontology and there were several classes and properties defined for that.  For some reason, I am not seeing those namespaces.  I selected the option to group by namespace/prefix and the prefixes that I defined cv, does not exist on the Classes view on the left. 
           I then tried to create the project from scratch.  I created a project for Resume data.  Then I copied an RDF/XML file on top of the project folder.  When I opened that file, I got an error saying more than one ontology is defined for the project.  That shouldn't be a problem as most data sets have more than one ontology that they use. 
         What should I do?  Recreate the project and re-enter the information?
          I was told in a previous post that TBC is not intended for data entry.  Initially I had chosen TBC over Protege because I thought that Protege semantic web tool was only for defining ontologies and not for working with instance data - even though, technically, this can be defined in the same file as that is a feature of RDF which doesn't require that the schema be defined separately. 
            If that is the case, can someone recommend approaches to entering and storing data that is largely described by one main ontology?   This might be a bit off topic but I have Fuseki installed on the server which supports SPARQL 1.1 and was discussed in Bob DuCharme's book "Learning SPARQL."  So, I could use SPARQL to enter new data from a form or set of forms, which describe the data that makes up a person's resume/cv.  Then I want to save it as an RDF file and display the data using microcode (schema.org) and RDFa (not sure if this can be done on the same web page.  And the saved data will go into a named graph in the triple store, where the details about a person's Resume/CV are all stored in one named graph - the named graph is used to connect the various classes and properties that make up a person's CV.  That is my plan for relating cv:Skill instances to a cv:Person.
          As for the TBC, I will try to recreate the project again from scratch and re-enter the data, as I don't know what else to do.  Again, as someone mentioned, TBC isn't meant for data entry, I believe, so I welcome suggestions for how to handle this.
Thanks,
Bruce

[Bob Ducharme]

Hi Bruce,

Instead of pointing your new installation of TBC at your old workspace, did  you try creating a new workspace and importing the existing project(s)? (Import -> General -> Existing Projects into Workspace, and leave "Copy projects into workspace" checked). Re-entry of the information is certainly not necessary.

If I had to set up several data entry people to enter data that was going into RDF models, I would write an SWP web-based application to make it easier for them instead of training them in TBC, but for someone already comfortable with navigating around TBC, I find it simple to do data entry with it, as long as the relevant properties have an rdfs:domain of the class that they go with so that when I create a new instance of that class those properties show up on its form. I click the "Create instance" icon on the Instances view, fill out the form, and repeat. Of course, the Instances view has a simple interface for editing and deleting existing instances as well. 

To keep my instance data separate from the model that defines their classes and properties, I define the classes and properties in one model (e.g. a ttl file), then create a new one for the instances, import the model into that, and add the instance data in that new one. 

Bob

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

[Bruce Whealton]

Bob,
     Thanks.  I agree that TBC may not be the best tool for the average end user.  It should be a tool to help in creating semantic web apps and for testing.  For someone comfortable navigating it, indeed it is a good tool for doing that.  So, I isolated a problem I was having with one of the ontologies I had been using.  It is the ResumeRDF ontology.  It is defined here: http://rdfs.org/resume-rdf/
with the namespaces being the following two uri:
http://purl.org/captsolo/resume-rdf/0.2/cv# - ResumeRDF ontology
http://purl.org/captsolo/resume-rdf/0.2/base# - base taxonomy containing possible values for ResumeRDF properties

I can import various other ontologies into TBC but I cannot find any of the links on this page to be something that TBC can import successfully.  I just get errors when I try to import them from the web.  I'm not able to find a link to download this - as in a link that will give back only an rdf/xml file.
I don't know if this is very popular or not... and if the underlying schema even exists on the server.  Is it ok to recreate an ontology and republish it?
I know of some resume applications that use the semantic web but they seem to be targeted to employers.  There is a schema.org schema for JobPosting but I don't see any for describing a person's full CV.
Thanks,
Bruce

[Bob Ducharme]

Bruce,

Sending a browser to those URIs just gets a 404, so there's nothing there. I would contact the resume-rdf people to ask them about the availability of parseable versions of their ontology. 

Bob

[Bruce Whealton]

Thanks, Bob.  I was running into the same thing, not finding a RDF version of the ontology.  It says it is supported by the SIOC mailing list.  I wonder what the ethics are for recreating an ontology that is not maintained.  In your book and elsewhere you mention selecting ontologies/vocabularies that are popular.  How would one assess that, whether or not the resume/cv ontology is being used at all?

Thanks,

Bruce

+++++++++++++++++++++++++++++++++++++
Bruce Whealton
Web Developer/Designer: Future Wave Designs
http://FutureWaveDesigns.com
Publisher/Editor Word Salad Poetry Magazine
http://WordSaladPoetryMagazine.com
+++++++++++++++++++++++++++++++++++++

[Bob Ducharme]

Hi Bruce,

Basic web searches can give you good clues about popularity of any software-related project--how many hits there are, how recently anyone mentions using it, whether it's discussed on mailing lists and how recently, etc. Searching for the base URI (i.e. searching for the string "http://rdfs.org/sioc/ns", as opposed to sending a browser to that URI) is a good start when assessing the popularity of an ontology.

If a particular ontology is supported by a specific mailing list, as is the case here, then that mailing list is the best resource for researching your questions. 

Bob