Hi Scott I guess you'd normally be right, but access to other user's Oracle schemas is not currently a configurable option in D2RQ. I took advice from Richard Cyganiak on this, and he showed me where to hack the code. So, little choice but to use command line for the time being. I set things up using the wizard, and just replace the mapping file, so not too hard. I prefer the N3 output from D2RQ as it is neatly grouped by table, whereas the N3 conversion from TBC is less friendly. Now I am becoming more accustomed, I can probably do subsequent editing direct on the ontology rather than the N3 file; this will help. Thanks for the tip on Ensemble tree.
Peter 2009/12/3 Scott Henninger <[email protected]> > Peter; I suggest you use the D2RQ wizard in Composer (Import... RDF/ > OWL View on Relational...). This will eliminate a lot of the manual > tasks. The mapping and schema files are generated automatically. > From there, you can edit the mapping file to fine tune the mapping. > You may be able manipulate schema owner in the d2rq:Database instance > (see http://www4.wiwiss.fu-berlin.de/bizer/D2RQ/spec/ for more). N3 > files can be created through Export... Export/MergeConvert. > > Also, in Ensemble, if you want to view rdfs:Resource in the tree, use > the configuration (top middle button that looks like a wrench), choose > the Tree Component's, open Attributes, and change the root node from > Thing to Resource. You can also choose to display the root in the > Attributes. > > -- Scott -- You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. 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-composer-users?hl=en.
