Kees; The Export/Merge/Convert exporter does all three in one wizard. If you check one of the imports, then the triples from the imported file will be merged into a single file or data back-end. Suppose you start out with f1, which imports f2. When performing an Export/Merge/ Convert on f1, choosing f2 results in a file, f3, that contains the union of f1 and f2. See Help > How to? > Refactor ontologies > Export / Merge / Convert RDF Graphs
On the second question, the default output for file saves for RDF files is RDF/XML Abbrev. To get the file in RDF/XML, you will need to Export each time. (There is a preference for source code (Preferences > TopBraid Composer > Source Code), but this only seems to affect the initial serialization choice in the Source code sub- tab.) The ExportToRDFFile module in SPARQLMotion will also return a .rdf file in RDF/XML. Note that there is a great deal of variability in how RDF triples can be expressed in XML. TopBraid assumes that the target is fully RDF capable and can utilize any of those variations. If not, then using Semantic XML is the best option. Another option is to use the Turtle text serialization, which has many advantages, including little variation for how triples are expressed. -- Scott On Mar 29, 6:39 am, Kees <[email protected]> wrote: > Hi Scott, > > thanks a lot, the export to RDF/XML worked. > Two questions though, in the list of files to export there is also an > option to check the Inference graph in the export. What does actually > mean in the process? > Secondly, how do I get Topbraid to save all rdf files as RDF/XML? > Currently when I export to RDF/XML it creates skos:broader defenitions > as > <skos:broader rdf:resource="URI"/>. However, when I subsequently save > the file topbraid creates several <skos:broader> as tagges. I want the > file to stay consistent so using one method. > > thanks! > > Kees > > On Mar 28, 6:39 pm, Scott Henninger <[email protected]> > wrote: > > > Kees, you can save the file manually using Export > Export/Merge/ > > Convert RDF graphs. Choose RDF/XML as the format. If you have a > > script that uses a ExportToRDFFile module, this will default to RDF/ > > XML. > > > -- Scott > > > On Mar 28, 11:25 am, Kees <[email protected]> wrote: > > > > Hi I have small question. > > > > I have couple of RDF files that Topbraid 3.2 saves in the rdf/xml- > > > abbrev format. Is tthere are way to have them saved in rdf/xml? So it > > > will revert back to <rdf:Description rdf:about="URI">? > > > For building the model it is not a problem but the ICT department in > > > our company have problems with some terms not being able to select in > > > our search engine. The problem is related to paths in our model that > > > comprise polyhierarchy. This goes beyond my understanding but during > > > data extraction in building a Jena TDB store for some terms the wrong > > > path is selected. I am worrying that they don't have enough experience > > > in using rdf/skos models and related to this the problem is that they > > > do not have time to invest as they are closing in on launching a new > > > product. If I could revert to model to the non abbreviated rdf/skos > > > then I could test if that would help them. > > > > thanks a lot > > > > Kees -- 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
