Re: [Sesamewinclient-devel] dotNetRDF Interop and some questions regarding Sesame API

[Rob V. <rv...@vd...>]

Hi Anton

There is a pretty much complete initial attempt at a bridge in SVN under 
Trunk\Libraries\interop.sesame\ which provides Repository and 
RepositoryConnection's for both an in-memory store and a generic store 
(i.e. any external store my API can connect to)

I have tested some of the basics but I expect that there are various bugs 
yet to be found.

I hacked my stuff into SWC to do some basic testing but I'll leave you to 
work out a way to integrate it properly and do fuller testing.  I did 
attempt to create a RepositoryFactory and a RepositoryImplConfig 
implementation but these don't seem to work properly.

Regards,
Rob

----------------------------------------
From: "Anton Andreev" <ton...@gm...>
Sent: 16 November 2010 11:09
To: rv...@vd...
Subject: Re: [Sesamewinclient-devel] dotNetRDF Interop and some questions 
regarding Sesame API 

Hello Rob,

How is it the bridge between your APIs and Sesame going?

Do you have a version we could test?

Cheers,
Anton

On Tue, Nov 2, 2010 at 4:31 PM, Rob Vesse <rv...@vd...> 
wrote:

Hi Guys

I have successfully produced a client profile build of dotNetRDF, I do get 
compilation warnings about Virtuoso's ADO.Net provider using some 
non-client profile stuff.  I don't think my code uses that but can't 
guarantee it.  To get a client profile build you'll need to check out the 
whole Trunk and use nant to build it (build file in Trunk\Build\nant\) with 
the target compile-clientprofile

To build it with VS instead you'll need to use nant to generate the project 
file with the target projectgen-clientprofile and then you'll get a valid 
project file in the Trunk\Libraries\clientprofile\ directory which you can 
build.

With regards to the dotSesame bridge I have a basic outline of my interop 
library between dotNetRDF and Sesame done, so far I have the means to 
convert a dotNetRDF Graph to a Sesame Graph and vice versa.  I'm in the 
process of adding classes which wrap the two concepts so you can use a 
dotNetRDF Graph like it's a Sesame Graph and vice versa but I wanted to 
check with you on a couple of points about the Sesame API:

What is the retainAll() method supposed to do?What does the 
toArray(object[] objarr) do?  Does it fill the given array?  And I assume 
toArray() without arguments just gives an array of Statements?
I also plan on adding wrappers around my Triple Store interface at a later 
date.

I've also had an interesting bug report regarding someone using dotNetRDF 
and Sesame which you guys may be able to help me with.  He's put some data 
containing cyrillic characters into his repository and when querying it 
through dotNetRDF queries which specify the cyrillic literal come back with 
no results.  He noted that the same query works in SWC (which I can confirm 
it does) but I note that the returned value of the literal is a series of 
\u encodes, do I need to be escaping literals in my query into \u encodes 
when querying Sesame for the query to work correctly?

I can't see anything in your code that does this so I assume that dotSesame 
is doing this somewhere in it's code?

Rob Vesse

----------------------------------------------------------------------------
--

Nokia and AT&T present the 2010 Calling All Innovators-North America 
contest

Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada

$10 million total in prizes - $4M cash, 500 devices, nearly $6M in 
marketing

Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store

http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________

Sesamewinclient-devel mailing list

Ses...@li...

https://lists.sourceforge.net/lists/listinfo/sesamewinclient-devel