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 On Dec 3, 8:41 am, Peter Ward <[email protected]> wrote: > OK, I can see why, from comparing it with another simpler mapping that > works. > > I was using a mapping generated with the D2RQ command line tool. The > d2rq:class entries did not correspond with the schema classes. In TBC, you > can still see the instances (subclass of rdfs:Resource, not owl:Thing), but > not in Ensemble. > > When the d2rq:ClassMap is correctly associated with the schema type, the > views in Ensemble work correctly. I'm guessing this is intended behaviour! > > I am finding it quite hard going with d2rq, as I find I need to edit the > maps by hand, partly because the Oracle databases require me to hack the > schema owner, also because I prefer N3 files (play nice with Subversion). > > Still, I'm collecting good practice as I go, and this is the first time I > now have some corporate data visible through Ensemble!! > > Thanks > Peter > > 2009/12/3 Scott Henninger <[email protected]> > > > > > Peter, you should have no problem displaying data from any back-end > > using Ensemble, including D2RQ mappings. Perhaps you chose the schema > > file instead of the -Test file? Also try clicking on a class you know > > has instances and see if they show up in the results grid (Default > > Application). Failing that, how large is the data store? I can't > > think of what else could be causing a problem, so any additional > > information will help. > > > -- Scott > > > On Dec 3, 6:21 am, peter <[email protected]> wrote: > > > Hello, I'm sure you can help, I must be missing something simple. > > > > I'm using TBC-ME 3.2.1 in trial. I have created a number of mappings > > > using D2RQ and I can browse the relational data from within TBC. I > > > though this data would be automatically visible by accessing the same > > > ontology through the default application in Ensemble. But I see only > > > the class tree, no instances. This is true even if I first open the > > > ontology in TBC. > > > Must I do something else to make the underlying relational data > > > accessible this way, or is this not intended or recommended? > > > > Peter > > > -- > > > 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]<topbraid-composer-users%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/topbraid-composer-users?hl=en. > > --http://www.linkedin.com/in/peterjamesward -- 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.
