Dave; Glad you got it all working. Thank you for the feedback, and it is very useful. To make sure we end up on the same page, I wanted to be clear on a couple of things.
1) The data connectors in Composer/Live are true connectors. All of the information displayed in Composer is from the data store. The connector information is used only to establish and name the connection. If connector information needs to be changed, it is advised that the connection wizard be re-invoked to create a new .sdb/.tdb/.oracle/.allegro/etc. connector file. Given this, and the overall contract that anything displayed in Composer is accessible as triples (except namespace prefixes, of course), I'm afraid it would be more confusing than useful to have connector information displayed in the model itself. 2) The best practice is to use the same name for both the "Base URI" and "SDB Named GRAPH URI (Optional)" fields, unless this causes a name (base URI) conflict in the workspace. Note that the wizard supports this - if the fields are the same and you modify the Base URI, the Named Graph URI also changes. However. to support cases where they should not be the same, changes to Named Graph URI do not change the Base URI field. Note the core issue here - Composer is a named graph system that can access named graph systems, such as SDB databases. The level of indirection afforded by giving the connector a name (base URI) allows one to unambiguously reference named graphs inside of databases that may have, inadverently or purposefully, the same name, and use them consistently throughout the workspace including in owl:imports statements (which uses a URI to identify the graph import). This does prove to be a useful feature, but we are also aware that it causes issues when there are lots of named graphs in a database. Again, the feedback is appreciated and do not hesitate to ask further questions! -- Scott On Apr 11, 4:12 pm, DaveL <[email protected]> wrote: > Scott, > > I finally managed to get it working. > > What it finally turned out to be is my misunderstanding of the > semantics of the various fields in the New / Jena/SDB Database > Connection dialog. Pulling up the Triples view helped a lot, as I was > able to see what was actually there. > > For some reason, this led me to change the "Base URI" to something > ("http://localhost.repo";) that didn't conflict with anything else in > my environment. I was using "http://localhost/jenaStore"; as both my > database URL and my Base URI, and at various times I had tried other > Base URIs that were apparently the same as something in the database. > (I hope that makes some sense to you.) Once I did this, everything > worked. > > In any case, I can now load the core ontology, load the UnionGraph, > and do my SPARQL queries. > > If I could make a suggestion, it would be to include all the fields > from the "New" dialog in the Ontology Overview tab, even if you don't > want some of them editable, and also to describe the semantics of Base > UI (including the "don'ts") in simpler terms than linking to the W3C > site. > > Thanks for all your help (and infinite patience). > > Dave > > On Apr 11, 3:04 pm, Scott Henninger <[email protected]> > wrote: > > > To see if anything is being imported, try the Triples view or do a > > SELECT * WHERE {?s ?p ?o} in the SPARQL view. There is a chance that > > the data is there but somehow mismatching rdfs/owl URIs. (Composer > > always shows "basic rdf: and owl: stuff" for any model it recognized > > as RDF.) > > > The better chance is that either 1) the Named Graph URI is not > > matching exactly (it is case-sensitive), or 2) the "Overwrite existing > > database content" box was accidentally checked. > > > Failing those, then there is a chance that the original SDB was > > created in a different version that the one Composer uses, and they > > could be incompatible. If you have the original .owl files, you could > > open the .owl file in Composer and use Export to write it to SDB. > > This would eliminate any potential version mismatches. > > > -- Scott -- 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
