what is the current approach to employ an external rdf store?

[anderson....@gmail.com]

there are threads in this group which refer to both "plugin" and "sesame-compatible" approaches to attaching an external rdf store to composer.

investigations of the suggested methods and attempts to apply referenced descriptions have, however, failed to produce a working approach.

in one case, the deprecated plugin raises questions about the support for that approach.

in another, the described method to incorporate a store through a sesame connector leads in the current composer version to a dialog in which the described option is no longer present.

is there any concise documentation for either of those approaches?

- is there an api/architecture specification for plug-in for external rdf stores?

- where in the documentation is the up-to-date description for how to connect to a sesame-compatible rdf storage service?

[David Price]

As of about two years ago, the support for non-Jena triplestores in Composer was removed. Unused features occasionally get removed to stop wasting dev resources.

I see, but have never used, a Sesame connection in TBCME 6.1.1 but not in TBCME 6.2.4 so appears you’ll need to use an old 6.1 release of Composer if you need that feature.

Cheers,

David

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/143b1a74-e5f7-42d7-ad1b-de1a8e3776d0n%40googlegroups.com.

[anderson....@gmail.com]

do you make your concrete interface requirements public, to permit validation and incorporation of jena emulations?

[David Price]

On 13 May 2021, at 13:46, anderson....@gmail.com <anderson....@gmail.com> wrote:

do you make your concrete interface requirements public, to permit validation and incorporation of jena emulations?

No idea, but I’ve never heard anyone mention such a thing. I’m a Composer user not a Composer developer. Maybe someone else knows for certain?

Cheers,

David

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/753e2eba-a8b7-4dc2-8bc2-69e9b91adff6n%40googlegroups.com.

[Holger Knublauch]

As David has indicated, we no longer want to support arbitrary 3rd party triple stores from TBC, because those features are expensive to maintain for too little gain, and performance will not be good anyway. Composer (and TopBraid EDG) are programmed against Jena with certain architectural assumptions. It's all triple-based (SPO) and queries go through union graphs. This is leading to many small requests that quickly overwhelm external triple stores, while the built-in Jena graphs (in-memory and TDB) have good computational characteristics.

Holger

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/EEBF06E8-ABEC-42F4-B2C7-E2C9591FF997%40topquadrant.com.

[Matt]

revisting as we have interest in something like this.  is it possible to opensource this plugin to democratize the cost of development/support?

[Jeremy Debattista]

Hi Matt,

What version of EDG/TBC are you using? Do you have a particular usecase for why you need to use an external RDF store?

Thanks,

Jeremy

[Holger Knublauch]

Sorry but this particular code has been long deleted and wouldn’t be of much use.

Is there still no proper RDF4J/Sesame - Jena bridge anywhere?!

Holger

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/77b0130f-61de-4c2f-b158-2348bee71e36n%40googlegroups.com.

[Matt]

Hi Jeremy, will need to double check with my coworkers when I get in the office on the version (we are licensed users).  Nevertheless, we wouldn't want to be version locked. For us, we have two classes of users. Advance (modellers) and casual (subject matter experts and product owners). We find that tb is too complex for the casual users so are developing a simple web interface for them to interact with the models in a very controlled way. With that, a 3store makes sense and so if tb can also use the 3store, we could greatly simplify our approach. 

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/175da459-1b44-479e-a72d-cb73dcadf8b3n%40googlegroups.com.

[Matt]

I'll also add that in order to move the needle on semtech, in general, we need to stop treating 3stores as a second class citizen.  This comment is not directly made at tb eng but thinking aloud to the community. I hope for a day where they are evaluated equally with rdbms and nosql tech as a viable solution for the storage layer in any system.

To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-users+unsubscribe@googlegroups.com.