Hi Hugh,
thanks for the quick reaction!
The first option (the Virtuoso RDF Data Storage Provider) works, but I'd
have to change my client code which I really don't want.
The second option is the one that fails.
best,
Florian
On 19.4.2011 14:24, Hugh Williams wrote:
Hi Florian,
What meth
Hi Florian,
What method are you using to query the Virtuoso repository from Sesame as we
support two methods:
1. Using the Virtuoso RDF Data Storage provider as detailed at:
http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtSesame2Provider
2. Using the Sesame HTTP repository
Hi all,
I'm using the virtuoso sesame provider with the latest openrdf-workbench
and openrdf-sesame webapps.
sesame version: 2.3.3
virtuoso version: virtuoso-opensource-win32-20110330
I've configured a repository to use virtuoso and I can access it
normally in the openrdf workbench.
However
Herman,
I forgot to mention that Virtuoso provides a full blown web-server and
a preprocessor ( something like PHP/ASP ) called Virtuoso Server Pages
( VSP ).
It provides session management and low-level integration with all
other database features.
http://docs.openlinksw.com/virtuoso/vsp1.html
Hi Herman,
On Mon, Apr 18, 2011 at 10:21 PM, Herman A. Junge wrote:
> Hi,
> As a first project using an RDF Database, I would like to build an app with
> Session Management: storing sessionId, userId, dates (in and out)... All the
> traditional components, just using triplets instead of RDB Table
Hi,
As a first project using an RDF Database, I would like to build an app with
Session Management: storing sessionId, userId, dates (in and out)... All the
traditional components, just using triplets instead of RDB Tables.
*Question:* Is there some recommendation on the Data Structure of such
ap
