dotnetrdf-develop — Developer Discussion and Feature Request

[dotNetRDF-Develop] Fw: SparqlRemoteEndpoint, SparqlFormatter minor issues

[Eugen F <feu...@ya...>]

I have created a fork "dotnetrdf bigdata connector". Unit tests pass using bigdata 1.3 - quad mode.
 Let me know if there are issues that I need to fix.



On Thursday, January 30, 2014 8:49 PM, Eugen F <feu...@ya...> wrote:
 
I would like to since every new release of dnr I have to get source code and reintegrate the connector. But the problem is that at the time I wrote the connector I didn't know about SparqlParameterizedString and there might be other issues caused by the lack of knowledge of various dnr aspects. 
Also I used the connector in quad mode, but I don't know how it behaves in triple mode or triples with provenance(bigdata custom implem).

So I will try to make some time to look again through that code, try to fix what I can and i'll create a fork after.





On Tuesday, January 28, 2014 10:09 PM, Rob Vesse <rv...@do...> wrote:
 
Is the BigData connector something you would consider contributing to the project?

Rob

From:  Eugen F <feu...@ya...>
Reply-To:  Eugen F <feu...@ya...>
Date:  Thursday, 16 January 2014 10:57
To:  Rob Vesse <rv...@do...>, dotNetRDF Developer Discussion and Feature Request <dot...@li...>
Subject:  Re: [dotNetRDF-Develop] SparqlRemoteEndpoint, SparqlFormatter minor issues


"Why do you need this, are you using the formatters in such a way that you don't want the a keyword to be used?"
>
>I wrote a connector to systap bigdata store some time ago and it is using sparql formatter to create queries. It was a problem when using "a" keyword so i had to change the dnr code. But I can't remember exactly the case and now i've updated to latest db version and all unit tests seem to pass with both true/false so I don't think the change is needed.
>
>
>
>
>
>
>On Thursday, January 16, 2014 5:09 PM, Rob Vesse <rv...@do...> wrote:
> 
>Comments inline:
>
>
>From:  Eugen F <feu...@ya...>
>Reply-To:  Eugen F <feu...@ya...>, dotNetRDF Developer Discussion and Feature Request <dot...@li...>
>Date:  Thursday, 9 January 2014 12:16
>To:  dotNetRDF Developer Discussion and Feature Request <dot...@li...>
>Subject:  [dotNetRDF-Develop] SparqlRemoteEndpoint, SparqlFormatter minor issues
>
>
>
>Hi,
>>
>>
>>1. In "SparqlFormatter" code:
>>
>>
>>
>>SparqlFormatter  : TurtleFormatter :  QNameFormatter(..., bool allowAKeyword)
>>
>>
>>The problem is that "_allowAKeyword" is not exposed in SparqlFormatter so I can't pass it. So I sugest either to add
>> public bool AllowAKeyword
>>        {
>>            get { return _allowAKeyword;
 }
>>            set { _allowAKeyword = value; }
>>        }
>>or create new constructor overloads in Sparql, Turtle formatters.
>
>
>Why do you need this, are you using the formatters in such a way that you don't want the a keyword to be used?
>
>
>
>>
>>2. SparqlRemoteEndpoint should allow custom query params for url in case db accepts more (bigdata does for analytic queries)
>>So code could be changed by adding(key,value):
>> public Dictionary<String, String> QueryParams
>>        {
>>            get
>>            {
>>                return this._queryParams;
>>            }
>>        }
>>and changing apropriate http calls.
>
>
>Logged as a future improvement as CORE-396 (http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=396)
>
>
>Rob
>
>
>
>>
>>
>>------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk_______________________________________________ dotNetRDF-develop mailing list dot...@li...https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
>

[dotNetRDF-Develop] Issue CORE-400 has been added to a project you are monitoring.

[<tr...@do...>]

<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Cannot increase query timeout more than default HttpWebRequest 100 seconds for SPARQL Update on Stardog</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td><b>Created By:</b></td>
    <td>Alexandre Bouffard</td>
  </tr>
  <tr>
    <td><b>Milestone:</b></td>
    <td>Unassigned</td>
  </tr>
  <tr>
    <td><b>Category:</b></td>
    <td>Stardog</td>
  </tr>
  <tr>
    <td><b>Priority:</b></td>
    <td>Unassigned</td>
  </tr>
  <tr>
    <td><b>Type:</b></td>
    <td>Improvement</td>
  </tr>
  <tr>
    <td><b>Description:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Hi,</p>
<p>
	I get a HttpWebRequest query timeout after 100 seconds for a long-running SPARQL Update query on Stardog.</p>
<ul>
	<li>
		The Stardog server query timeout is set to 24 hours.</li>
	<li>
		I did not find how to set the timeout at query level for a SPARQL Update query (while it is available for SPARQL Select queries) or stardog client level (while it is available for SparqlRemoteUpdateEndpoint).</li>
	<li>
		I tried to set both Options.QueryExecutionTimeout and Options.UpdateExecutionTimeout to 1800000 (30 minutes) without success.</li>
</ul>
<p>
	Did I miss something ?</p>
<p>
	Thanks.</p></td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=400" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=400</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>

Re: [dotNetRDF-Develop] DotNetRDF

[Tomasz P. <tom...@gm...>]

Hi Miloš,

Yes I did get your email! Thank you and sorry for late reply.

I have been thinking long ago about using the R2RML mapping to
translate SPARQL into SQL. Unfortunately there is always little time
and more pressing issues and eventually I haven't even finished
R2RML.net in 100%.

However I will be happy to help with your project shall you desire to
use the R2RML.net mapping as input and dotNetRDF as the query
processor. As Rob said in his response, you could implement the
existing interfaces to read through an input SQL query and transform
it to SPARQL. There you will need the mappings.

Most difficult is probably the actual algorithm for converting one
query into another. Other than that of course you will need a way to
process the SPARQL query. dotNetRDF parses it into a nice abstract
model so you should be fine. Lastly you will eventually need a way to
produce SQL queries for different DBMS flavours.

On the mapping side you would have to make sure that R2RML.net exposes
all the required mapping data. If you need any changes I encourage you
to fork my repository and we'll try to adjust it to your needs.

Regards,
Tom

PS
There's also a blog posts which briefly discusses a way to do what you
try to achive: http://antoniogarrote.wordpress.com/2011/01/10/translating-sparql-queries-into-sql-using-r2rml/

On Thu, Feb 13, 2014 at 12:09 PM, Rob Vesse <rv...@do...> wrote:
> Hi Milos
>
> To be honest we've moved away from SQL backed storage because in the past it
> hasn't proven that performant.  However providing a R2RML adaptor layer does
> make a lot more sense and provides a better solution than what we've tried
> in the past (which was based on storing triples natively in a SQL database).
>
> I would suggest looking at implementing a IStorageProvider which also
> implements IQueryableStorage if you are intending to support SPARQL.  Since
> this likely involves some sort of dependency upon Tom's existing R2RML
> library then this would be best implemented as a separate library in a
> similar way to the existing Data.Virtuoso library because we want to mimize
> dependencies in the core library.  I'd suggest reading up on the Storage API
> (https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Storage%20API) if
> you haven't already and taking a look at the implementations of existing
> IStorageProviders.
>
> Contribution wise I would suggest you create your own fork, work in there
> and then submit pull request(s) as and when you have something you thing is
> sufficiently stable for inclusion in the main project.  Please take a look
> at our Code Style guidelines
> (https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/Code%20Style)
> and Test Environment
> (https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/Test%20Environment)
> documentation.  Any substantial feature contribution like this will need to
> be accompanied by appropriate tests which I appreciate can be tricky for
> testing that requires on external resources I.e. SQL servers but you can use
> the approach we use for existing storage to provide developer configurable
> settings for test setup and skip tests where the test system is unavailable.
>
> And of course if you have questions about anything then please ask on the
> developer list which I've CC'd on this response, this is a subscription
> based list which you will need to subscribe to via
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
> Best Regards,
>
> Rob Vesse
>
> From: Miloš Chaloupka <cha...@ho...>
> Date: Monday, 10 February 2014 09:18
> To: Rob Vesse <rv...@do...>
> Subject: DotNetRDF
>
> Hi Rob,
>
>
>
> I have found you as an author of DotNetRDF so I hope I am contacting the
> right person. I have already written to Tomasz Pluskiewicz, but got no
> response yet, so I am not really sure, whether he even got the message.
>
>
>
> I am currently writing my master thesis "Querying RDF graphs stored in a
> relational database using SPARQL and R2RML" and I am choosing how I will
> write the implementation. I don't want to write a solution that will end as
> an academic work with no chance of real use so I think, that it would be
> nice to make it as a "part" of dotNetRDF. I want to implement it as a store,
> that will be queryable using SPARQL according to R2RML mapping. I can see
> that you have already listed several libraries and that is in fact the only
> thing I want. Maybe you want to ask why I am asking before I am starting the
> implementation, it is because my supervisor wants to make the implementation
> as a part of something bigger so I want to know whether it is possible. Are
> you interested in such storage implementation? And if so, do you have any
> demands?
>
>
>
> Thank you for your reply,
>
> best regards,
>
> Miloš Chaloupka
>
>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience.  Start now.
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>

[dotNetRDF-Develop] Issue TOOLS-360 has a new comment

[<tr...@do...>]

<p>A new comment has been added to the following issue.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Replace current .vdproj based installer with a WiX based installer</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Toolkit</td>
  </tr>
  <tr>
    <td><b>Created By:</b></td>
    <td>Rob Vesse</td>
  </tr>
  <tr>
    <td><b>Date:</b></td>
    <td>2014-02-13 01:05 PM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Making some progress, now able to build and run the installer locally and am now working towards having individual components installable</p></td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=360" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=360</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>

Re: [dotNetRDF-Develop] Toolkit installer

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

Yeah I've already made some progress on getting features selectable, haven't
refactored the project to include all features yet or get the default
feature set for custom installations behaving correctly yet but am making
progress

Once you have stuff for xamarin builds then we should definitely integrate
that for dotNetRDF and VDS.Common

Cheers,

Rob

From:  Kal Ahmed <ka...@ne...>
Reply-To:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Date:  Thursday, 13 February 2014 12:31
To:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Subject:  Re: [dotNetRDF-Develop] Toolkit installer

> 
> Cool! Happy to help out when I can, but I'm currently working on-site for a
> customer, so my time is a bit limited at the mo. :-(
> 
> Choosing what to install is a question of dividing up the features. You may
> also need to change the UI used by WiX to one that displays the feature tree
> to the user. Let me know if you want me to take a look.
> 
> By the way, I'm working on adding Xamarin support to the portable build of B*.
> For now I'm building local versions of vds-common and DNR. Once I have
> something working we could maybe look at updating the builds and nuget
> packages, but I'll aim to get stuff working and do a few integration tests
> first.
> 
> Cheers
> 
> Kal
> 
> On 13 Feb 2014 11:59, "Rob Vesse" <rv...@do...> wrote:
>> After a bit more digging I figured out how to change the directory things are
>> placed into so I have that figured out.
>> 
>> Next up is being able to select precisely which tools are installed
>> 
>> Rob
>> 
>> From:  Rob Vesse <rv...@do...>
>> Reply-To:  dotNetRDF Developer Discussion and Feature Request
>> <dot...@li...>
>> Date:  Thursday, 13 February 2014 11:46
>> To:  Kal Ahmed <ka...@ne...>
>> Cc:  dotNetRDF Developer Discussion and Feature Request
>> <dot...@li...>
>> Subject:  Re: [dotNetRDF-Develop] Toolkit installer
>> 
>>> Kal
>>> 
>>> So I finally had time to look at this some more, hard coding the SDK path
>>> has worked around the problem and I can successfully install and uninstall
>>> the toolkit.
>>> 
>>> One problem I notice is that I don't get quite the right layout on disk, for
>>> example the rdfEditor folder includes all the .xshd files but doesn't put
>>> them under the expected Syntax sub-directory which means the features
>>> related to these won't work correctly.  Similarily the StoreManager folder
>>> does not have an appropriate Plugins sub-directory.
>>> 
>>> I am happy to work on fixing these myself but not being familiar with WiX I
>>> can't understand how what is included is even getting decided?  It appears
>>> to relate to CoreFiles.wxs which appears to get automatically generated
>>> using the WiX heat tool so I don't understand how to change things.  Any
>>> pointers here would be welcome
>>> 
>>> Thanks,
>>> 
>>> Rob
>>> 
>>> From:  Kal Ahmed <ka...@ne...>
>>> Date:  Wednesday, 18 December 2013 22:11
>>> To:  Rob Vesse <rv...@do...>
>>> Subject:  Re: Toolkit installer
>>> 
>>>> Hi Rob,
>>>> 
>>>> It sounds like the GetFrameworkSdkPath task in the AfterBuild target is
>>>> getting the wrong thing (you could probably insert a message in there to
>>>> see if that is the case). However, I have no idea *why* that is happening
>>>> unless perhaps the msbuild process / nant process is running under an older
>>>> version of the .NET framework and is picking the wrong thing up there ?
>>>> Maybe for some reason it thinks it is running in a 32-bit environment ?
>>>> 
>>>> Sorry I can't shed more light on it. I vaguely remember having a problem
>>>> like this before but never getting to the bottom of it, I think I ended up
>>>> hardcoding the path instead of using the GetFrameworkSdkPath task.
>>>> 
>>>> Cheers
>>>> 
>>>> Kal
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Tue, Dec 17, 2013 at 3:01 PM, Rob Vesse <rv...@do...> wrote:
>>>>> Kal
>>>>> 
>>>>> The basic installer looks fine since it just puts stuff on disk, ideally
>>>>> it would also add command line shortcuts to the GUI tools to the Start
>>>>> Menu.
>>>>> 
>>>>> However personally I have been unable to build it so far, what I run into
>>>>> is an error about the Bootstrapper not being found:
>>>>> 
>>>>> Could not find required file 'setup.bin' in 'C:\Program Files\Microsoft
>>>>> SDKs\Windows\v7.0\Bootstrapper\Engine'
>>>>> 
>>>>> This mailing list thread
>>>>> (https://www.mail-archive.com/wix...@li.../msg33513.htm
>>>>> l) essentially seems to cover the problem I have which is that I have the
>>>>> Bootstrapper files but only under C:\Program Files (x86) and not under
>>>>> C:\Program files where WiX is looking
>>>>> 
>>>>> Have you ever run into this before?  Any idea how to fix it?
>>>>> 
>>>>> The above linked thread does have a suggested workaround but knowing
>>>>> nothing about WiX I haven't attempted it because I'm not sure what the
>>>>> implications of it are.
>>>>> 
>>>>> Btw work for integrating this into the solution is now on the TOOLS-360
>>>>> branch where it's included in the main solution though not yet in NAnt
>>>>> 
>>>>> Cheers,
>>>>> 
>>>>> Rob
>>>>> 
>>>>> From:  Kal Ahmed <ka...@ne...>
>>>>> Date:  Tuesday, 12 November 2013 16:38
>>>>> To:  Rob Vesse <rv...@do...>
>>>>> Subject:  Toolkit installer
>>>>> 
>>>>>> I've just pushed a couple of commits that add a basic version of the
>>>>>> installer. The project file is
>>>>>> Build\ToolkitInstaller\ToolkitInstaller.wixproj and there is also a VS
>>>>>> solution file (VS2012 format) for it.
>>>>>> 
>>>>>> It should be possible to build from the command line as long as you have
>>>>>> WiX 3.7 (or later) installed, and from VS if you have the necessary WiX
>>>>>> votive stuff installed (all part of the WiX installer now I think).
>>>>>> 
>>>>>> All it does is put the files on the disk  - as far as I could tell that
>>>>>> is all the original installer does, but if there are registry things or
>>>>>> other things you need the installer to do, let me know.
>>>>>> 
>>>>>> Things to do :
>>>>>> 
>>>>>> 1) It currently builds to set the default install into
>>>>>> ProgramFilesFolderPath which is "C:\Program Files" on x86 but is
>>>>>> "C:\Program File (x86)" on x64. As far as I have been able to work out
>>>>>> the only way around this with WiX is to build two versions of the MSI and
>>>>>> wrap them in a bootstrapper that chooses the correct version based on
>>>>>> installation platform. I've just done this for BrightstarDB and its
>>>>>> horrible and adds another bit of random GUI to the process as well as
>>>>>> doubling the installer size, so I haven't done that for now.
>>>>>> 
>>>>>> 2) Its not currently integrated into the NAnt build - I didn't want to
>>>>>> mess with that until the WiX installer is considered OK
>>>>>> 
>>>>>> 3) I wasn't sure how to set the version number. Currently it is
>>>>>> hard-coded in the .wixproj file as a Property (DotNetRdfVersion). If you
>>>>>> can point me in the right direction for getting hold of the build number
>>>>>> during the build process I can fix that up.
>>>>>> 
>>>>>> Cheers
>>>>>> 
>>>>>> Kal
>>>>>> -- 
>>>>>> Kal Ahmed
>>>>>> Director, Networked Planet Limited
>>>>>> e: kal...@ne...
>>>>>> w: www.networkedplanet.com <http://www.networkedplanet.com>
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Kal Ahmed
>>>> Director, Networked Planet Limited
>>>> e: kal...@ne...
>>>> w: www.networkedplanet.com <http://www.networkedplanet.com>
>>> ----------------------------------------------------------------------------
>>> -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1
>>> Runtime for Android apps. Now with support for Jelly Bean, Bluetooth,
>>> Mapview and more. Get your Android app in front of a whole new audience.
>>> Start now. 
>>> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
>>> _______________________________________________ dotNetRDF-develop mailing
>>> list 
>>> dot...@li...https://lists.sourceforge.net/lists/l
>>> istinfo/dotnetrdf-develop
>> 
>> 
----------------------------------------------------------------------------->>
-
>> Android apps run on BlackBerry 10
>> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
>> Now with support for Jelly Bean, Bluetooth, Mapview and more.
>> Get your Android app in front of a whole new audience.  Start now.
>> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
>> _______________________________________________
>> dotNetRDF-develop mailing list
>> dot...@li...
>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>> 
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1
> Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview
> and more. Get your Android app in front of a whole new audience.  Start now.
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk__
> _____________________________________________ dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

Re: [dotNetRDF-Develop] Toolkit installer

[Khalil A. <ka...@ne...>]

Cool! Happy to help out when I can, but I'm currently working on-site for a
customer, so my time is a bit limited at the mo. :-(

Choosing what to install is a question of dividing up the features. You may
also need to change the UI used by WiX to one that displays the feature
tree to the user. Let me know if you want me to take a look.

By the way, I'm working on adding Xamarin support to the portable build of
B*. For now I'm building local versions of vds-common and DNR. Once I have
something working we could maybe look at updating the builds and nuget
packages, but I'll aim to get stuff working and do a few integration tests
first.

Cheers

Kal
On 13 Feb 2014 11:59, "Rob Vesse" <rv...@do...> wrote:

> After a bit more digging I figured out how to change the directory things
> are placed into so I have that figured out.
>
> Next up is being able to select precisely which tools are installed
>
> Rob
>
> From: Rob Vesse <rv...@do...>
> Reply-To: dotNetRDF Developer Discussion and Feature Request <
> dot...@li...>
> Date: Thursday, 13 February 2014 11:46
> To: Kal Ahmed <ka...@ne...>
> Cc: dotNetRDF Developer Discussion and Feature Request <
> dot...@li...>
> Subject: Re: [dotNetRDF-Develop] Toolkit installer
>
> Kal
>
> So I finally had time to look at this some more, hard coding the SDK path
> has worked around the problem and I can successfully install and uninstall
> the toolkit.
>
> One problem I notice is that I don't get quite the right layout on disk,
> for example the rdfEditor folder includes all the .xshd files but doesn't
> put them under the expected Syntax sub-directory which means the features
> related to these won't work correctly.  Similarily the StoreManager folder
> does not have an appropriate Plugins sub-directory.
>
> I am happy to work on fixing these myself but not being familiar with WiX
> I can't understand how what is included is even getting decided?  It
> appears to relate to CoreFiles.wxs which appears to get automatically
> generated using the WiX heat tool so I don't understand how to change
> things.  Any pointers here would be welcome
>
> Thanks,
>
> Rob
>
> From: Kal Ahmed <ka...@ne...>
> Date: Wednesday, 18 December 2013 22:11
> To: Rob Vesse <rv...@do...>
> Subject: Re: Toolkit installer
>
> Hi Rob,
>
> It sounds like the GetFrameworkSdkPath task in the AfterBuild target is
> getting the wrong thing (you could probably insert a message in there to
> see if that is the case). However, I have no idea *why* that is happening
> unless perhaps the msbuild process / nant process is running under an older
> version of the .NET framework and is picking the wrong thing up there ?
> Maybe for some reason it thinks it is running in a 32-bit environment ?
>
> Sorry I can't shed more light on it. I vaguely remember having a problem
> like this before but never getting to the bottom of it, I think I ended up
> hardcoding the path instead of using the GetFrameworkSdkPath task.
>
> Cheers
>
> Kal
>
>
>
>
> On Tue, Dec 17, 2013 at 3:01 PM, Rob Vesse <rv...@do...> wrote:
>
>> Kal
>>
>> The basic installer looks fine since it just puts stuff on disk, ideally
>> it would also add command line shortcuts to the GUI tools to the Start Menu.
>>
>> However personally I have been unable to build it so far, what I run into
>> is an error about the Bootstrapper not being found:
>>
>> Could not find required file 'setup.bin' in 'C:\Program Files\Microsoft
>> SDKs\Windows\v7.0\Bootstrapper\Engine'
>>
>> This mailing list thread (
>> https://www.mail-archive.com/wix...@li.../msg33513.html)
>> essentially seems to cover the problem I have which is that I have the
>> Bootstrapper files but only under C:\Program Files (x86) and not under
>> C:\Program files where WiX is looking
>>
>> Have you ever run into this before?  Any idea how to fix it?
>>
>> The above linked thread does have a suggested workaround but knowing
>> nothing about WiX I haven't attempted it because I'm not sure what the
>> implications of it are.
>>
>> Btw work for integrating this into the solution is now on the TOOLS-360
>> branch where it's included in the main solution though not yet in NAnt
>>
>> Cheers,
>>
>> Rob
>>
>> From: Kal Ahmed <ka...@ne...>
>> Date: Tuesday, 12 November 2013 16:38
>> To: Rob Vesse <rv...@do...>
>> Subject: Toolkit installer
>>
>> I've just pushed a couple of commits that add a basic version of the
>> installer. The project file is
>> Build\ToolkitInstaller\ToolkitInstaller.wixproj and there is also a VS
>> solution file (VS2012 format) for it.
>>
>> It should be possible to build from the command line as long as you have
>> WiX 3.7 (or later) installed, and from VS if you have the necessary WiX
>> votive stuff installed (all part of the WiX installer now I think).
>>
>> All it does is put the files on the disk  - as far as I could tell that
>> is all the original installer does, but if there are registry things or
>> other things you need the installer to do, let me know.
>>
>> Things to do :
>>
>> 1) It currently builds to set the default install into
>> ProgramFilesFolderPath which is "C:\Program Files" on x86 but is
>> "C:\Program File (x86)" on x64. As far as I have been able to work out the
>> only way around this with WiX is to build two versions of the MSI and wrap
>> them in a bootstrapper that chooses the correct version based on
>> installation platform. I've just done this for BrightstarDB and its
>> horrible and adds another bit of random GUI to the process as well as
>> doubling the installer size, so I haven't done that for now.
>>
>> 2) Its not currently integrated into the NAnt build - I didn't want to
>> mess with that until the WiX installer is considered OK
>>
>> 3) I wasn't sure how to set the version number. Currently it is
>> hard-coded in the .wixproj file as a Property (DotNetRdfVersion). If you
>> can point me in the right direction for getting hold of the build number
>> during the build process I can fix that up.
>>
>> Cheers
>>
>> Kal
>> --
>> Kal Ahmed
>> Director, Networked Planet Limited
>> e: kal...@ne...
>> w: www.networkedplanet.com
>>
>>
>
>
> --
> Kal Ahmed
> Director, Networked Planet Limited
> e: kal...@ne...
> w: www.networkedplanet.com
>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1
> Runtime for Android apps. Now with support for Jelly Bean, Bluetooth,
> Mapview and more. Get your Android app in front of a whole new audience.
> Start now.
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk_______________________________________________dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
>
>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience.  Start now.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
>

[dotNetRDF-Develop] Issue TOOLS-360 has been updated by Rob Vesse

[<tr...@do...>]

<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Replace current .vdproj based installer with a WiX based installer</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Toolkit</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Progress changed from "40 %" to "60 %"
                                </li>
      </ul>
    </td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=360" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=360</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>

Re: [dotNetRDF-Develop] Toolkit installer

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

After a bit more digging I figured out how to change the directory things
are placed into so I have that figured out.

Next up is being able to select precisely which tools are installed

Rob

From:  Rob Vesse <rv...@do...>
Reply-To:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Date:  Thursday, 13 February 2014 11:46
To:  Kal Ahmed <ka...@ne...>
Cc:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Subject:  Re: [dotNetRDF-Develop] Toolkit installer

> Kal
> 
> So I finally had time to look at this some more, hard coding the SDK path has
> worked around the problem and I can successfully install and uninstall the
> toolkit.
> 
> One problem I notice is that I don't get quite the right layout on disk, for
> example the rdfEditor folder includes all the .xshd files but doesn't put them
> under the expected Syntax sub-directory which means the features related to
> these won't work correctly.  Similarily the StoreManager folder does not have
> an appropriate Plugins sub-directory.
> 
> I am happy to work on fixing these myself but not being familiar with WiX I
> can't understand how what is included is even getting decided?  It appears to
> relate to CoreFiles.wxs which appears to get automatically generated using the
> WiX heat tool so I don't understand how to change things.  Any pointers here
> would be welcome
> 
> Thanks,
> 
> Rob
> 
> From:  Kal Ahmed <ka...@ne...>
> Date:  Wednesday, 18 December 2013 22:11
> To:  Rob Vesse <rv...@do...>
> Subject:  Re: Toolkit installer
> 
>> Hi Rob,
>> 
>> It sounds like the GetFrameworkSdkPath task in the AfterBuild target is
>> getting the wrong thing (you could probably insert a message in there to see
>> if that is the case). However, I have no idea *why* that is happening unless
>> perhaps the msbuild process / nant process is running under an older version
>> of the .NET framework and is picking the wrong thing up there ? Maybe for
>> some reason it thinks it is running in a 32-bit environment ?
>> 
>> Sorry I can't shed more light on it. I vaguely remember having a problem like
>> this before but never getting to the bottom of it, I think I ended up
>> hardcoding the path instead of using the GetFrameworkSdkPath task.
>> 
>> Cheers
>> 
>> Kal
>> 
>> 
>> 
>> 
>> On Tue, Dec 17, 2013 at 3:01 PM, Rob Vesse <rv...@do...> wrote:
>>> Kal
>>> 
>>> The basic installer looks fine since it just puts stuff on disk, ideally it
>>> would also add command line shortcuts to the GUI tools to the Start Menu.
>>> 
>>> However personally I have been unable to build it so far, what I run into is
>>> an error about the Bootstrapper not being found:
>>> 
>>> Could not find required file 'setup.bin' in 'C:\Program Files\Microsoft
>>> SDKs\Windows\v7.0\Bootstrapper\Engine'
>>> 
>>> This mailing list thread
>>> (https://www.mail-archive.com/wix...@li.../msg33513.html)
>>> essentially seems to cover the problem I have which is that I have the
>>> Bootstrapper files but only under C:\Program Files (x86) and not under
>>> C:\Program files where WiX is looking
>>> 
>>> Have you ever run into this before?  Any idea how to fix it?
>>> 
>>> The above linked thread does have a suggested workaround but knowing nothing
>>> about WiX I haven't attempted it because I'm not sure what the implications
>>> of it are.
>>> 
>>> Btw work for integrating this into the solution is now on the TOOLS-360
>>> branch where it's included in the main solution though not yet in NAnt
>>> 
>>> Cheers,
>>> 
>>> Rob
>>> 
>>> From:  Kal Ahmed <ka...@ne...>
>>> Date:  Tuesday, 12 November 2013 16:38
>>> To:  Rob Vesse <rv...@do...>
>>> Subject:  Toolkit installer
>>> 
>>>> I've just pushed a couple of commits that add a basic version of the
>>>> installer. The project file is
>>>> Build\ToolkitInstaller\ToolkitInstaller.wixproj and there is also a VS
>>>> solution file (VS2012 format) for it.
>>>> 
>>>> It should be possible to build from the command line as long as you have
>>>> WiX 3.7 (or later) installed, and from VS if you have the necessary WiX
>>>> votive stuff installed (all part of the WiX installer now I think).
>>>> 
>>>> All it does is put the files on the disk  - as far as I could tell that is
>>>> all the original installer does, but if there are registry things or other
>>>> things you need the installer to do, let me know.
>>>> 
>>>> Things to do :
>>>> 
>>>> 1) It currently builds to set the default install into
>>>> ProgramFilesFolderPath which is "C:\Program Files" on x86 but is
>>>> "C:\Program File (x86)" on x64. As far as I have been able to work out the
>>>> only way around this with WiX is to build two versions of the MSI and wrap
>>>> them in a bootstrapper that chooses the correct version based on
>>>> installation platform. I've just done this for BrightstarDB and its
>>>> horrible and adds another bit of random GUI to the process as well as
>>>> doubling the installer size, so I haven't done that for now.
>>>> 
>>>> 2) Its not currently integrated into the NAnt build - I didn't want to mess
>>>> with that until the WiX installer is considered OK
>>>> 
>>>> 3) I wasn't sure how to set the version number. Currently it is hard-coded
>>>> in the .wixproj file as a Property (DotNetRdfVersion). If you can point me
>>>> in the right direction for getting hold of the build number during the
>>>> build process I can fix that up.
>>>> 
>>>> Cheers
>>>> 
>>>> Kal
>>>> -- 
>>>> Kal Ahmed
>>>> Director, Networked Planet Limited
>>>> e: kal...@ne...
>>>> w: www.networkedplanet.com <http://www.networkedplanet.com>
>> 
>> 
>> 
>> -- 
>> Kal Ahmed
>> Director, Networked Planet Limited
>> e: kal...@ne...
>> w: www.networkedplanet.com <http://www.networkedplanet.com>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1
> Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview
> and more. Get your Android app in front of a whole new audience.  Start now.
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk__
> _____________________________________________ dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

Re: [dotNetRDF-Develop] Toolkit installer

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

Kal

So I finally had time to look at this some more, hard coding the SDK path
has worked around the problem and I can successfully install and uninstall
the toolkit.

One problem I notice is that I don't get quite the right layout on disk, for
example the rdfEditor folder includes all the .xshd files but doesn't put
them under the expected Syntax sub-directory which means the features
related to these won't work correctly.  Similarily the StoreManager folder
does not have an appropriate Plugins sub-directory.

I am happy to work on fixing these myself but not being familiar with WiX I
can't understand how what is included is even getting decided?  It appears
to relate to CoreFiles.wxs which appears to get automatically generated
using the WiX heat tool so I don't understand how to change things.  Any
pointers here would be welcome

Thanks,

Rob

From:  Kal Ahmed <ka...@ne...>
Date:  Wednesday, 18 December 2013 22:11
To:  Rob Vesse <rv...@do...>
Subject:  Re: Toolkit installer

> Hi Rob,
> 
> It sounds like the GetFrameworkSdkPath task in the AfterBuild target is
> getting the wrong thing (you could probably insert a message in there to see
> if that is the case). However, I have no idea *why* that is happening unless
> perhaps the msbuild process / nant process is running under an older version
> of the .NET framework and is picking the wrong thing up there ? Maybe for some
> reason it thinks it is running in a 32-bit environment ?
> 
> Sorry I can't shed more light on it. I vaguely remember having a problem like
> this before but never getting to the bottom of it, I think I ended up
> hardcoding the path instead of using the GetFrameworkSdkPath task.
> 
> Cheers
> 
> Kal
> 
> 
> 
> 
> On Tue, Dec 17, 2013 at 3:01 PM, Rob Vesse <rv...@do...> wrote:
>> Kal
>> 
>> The basic installer looks fine since it just puts stuff on disk, ideally it
>> would also add command line shortcuts to the GUI tools to the Start Menu.
>> 
>> However personally I have been unable to build it so far, what I run into is
>> an error about the Bootstrapper not being found:
>> 
>> Could not find required file 'setup.bin' in 'C:\Program Files\Microsoft
>> SDKs\Windows\v7.0\Bootstrapper\Engine'
>> 
>> This mailing list thread
>> (https://www.mail-archive.com/wix...@li.../msg33513.html)
>> essentially seems to cover the problem I have which is that I have the
>> Bootstrapper files but only under C:\Program Files (x86) and not under
>> C:\Program files where WiX is looking
>> 
>> Have you ever run into this before?  Any idea how to fix it?
>> 
>> The above linked thread does have a suggested workaround but knowing nothing
>> about WiX I haven't attempted it because I'm not sure what the implications
>> of it are.
>> 
>> Btw work for integrating this into the solution is now on the TOOLS-360
>> branch where it's included in the main solution though not yet in NAnt
>> 
>> Cheers,
>> 
>> Rob
>> 
>> From:  Kal Ahmed <ka...@ne...>
>> Date:  Tuesday, 12 November 2013 16:38
>> To:  Rob Vesse <rv...@do...>
>> Subject:  Toolkit installer
>> 
>>> I've just pushed a couple of commits that add a basic version of the
>>> installer. The project file is
>>> Build\ToolkitInstaller\ToolkitInstaller.wixproj and there is also a VS
>>> solution file (VS2012 format) for it.
>>> 
>>> It should be possible to build from the command line as long as you have WiX
>>> 3.7 (or later) installed, and from VS if you have the necessary WiX votive
>>> stuff installed (all part of the WiX installer now I think).
>>> 
>>> All it does is put the files on the disk  - as far as I could tell that is
>>> all the original installer does, but if there are registry things or other
>>> things you need the installer to do, let me know.
>>> 
>>> Things to do :
>>> 
>>> 1) It currently builds to set the default install into
>>> ProgramFilesFolderPath which is "C:\Program Files" on x86 but is "C:\Program
>>> File (x86)" on x64. As far as I have been able to work out the only way
>>> around this with WiX is to build two versions of the MSI and wrap them in a
>>> bootstrapper that chooses the correct version based on installation
>>> platform. I've just done this for BrightstarDB and its horrible and adds
>>> another bit of random GUI to the process as well as doubling the installer
>>> size, so I haven't done that for now.
>>> 
>>> 2) Its not currently integrated into the NAnt build - I didn't want to mess
>>> with that until the WiX installer is considered OK
>>> 
>>> 3) I wasn't sure how to set the version number. Currently it is hard-coded
>>> in the .wixproj file as a Property (DotNetRdfVersion). If you can point me
>>> in the right direction for getting hold of the build number during the build
>>> process I can fix that up.
>>> 
>>> Cheers
>>> 
>>> Kal
>>> -- 
>>> Kal Ahmed
>>> Director, Networked Planet Limited
>>> e: kal...@ne...
>>> w: www.networkedplanet.com <http://www.networkedplanet.com>
> 
> 
> 
> -- 
> Kal Ahmed
> Director, Networked Planet Limited
> e: kal...@ne...
> w: www.networkedplanet.com <http://www.networkedplanet.com>

[dotNetRDF-Develop] Issue CORE-396 has been updated by Rob Vesse

[<tr...@do...>]

<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Support custom parameters for SparqlRemoteEndpoint and SparqlRemoteUpdateEndpoint</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Milestone changed from "1.0.4" to "Unscheduled"
                                </li>
        <li>Assigned to changed from "Unassigned" to "none"
                                </li>
      </ul>
    </td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=396" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=396</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>

[dotNetRDF-Develop] Issue VIRT-399 has been updated by Rob Vesse

[<tr...@do...>]

<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Recent Virtuoso releases are missing the bif:rdf_make_iid_of_qname() function</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll)</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Status changed from "In Progress" to "Completed"
                                </li>
        <li>Resolution changed from "Unassigned" to "Fixed"
                                </li>
        <li>Progress changed from "0 %" to "100 %"
                                </li>
      </ul>
    </td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=399" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=399</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>

Re: [dotNetRDF-Develop] DotNetRDF

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

Hi Milos

To be honest we've moved away from SQL backed storage because in the past it
hasn't proven that performant.  However providing a R2RML adaptor layer does
make a lot more sense and provides a better solution than what we've tried
in the past (which was based on storing triples natively in a SQL database).

I would suggest looking at implementing a IStorageProvider which also
implements IQueryableStorage if you are intending to support SPARQL.  Since
this likely involves some sort of dependency upon Tom's existing R2RML
library then this would be best implemented as a separate library in a
similar way to the existing Data.Virtuoso library because we want to mimize
dependencies in the core library.  I'd suggest reading up on the Storage API
(https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Storage%20API) if
you haven't already and taking a look at the implementations of existing
IStorageProviders.

Contribution wise I would suggest you create your own fork, work in there
and then submit pull request(s) as and when you have something you thing is
sufficiently stable for inclusion in the main project.  Please take a look
at our Code Style guidelines
(https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/Code%20Style)
and Test Environment
(https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/Test%20Enviro
nment) documentation.  Any substantial feature contribution like this will
need to be accompanied by appropriate tests which I appreciate can be tricky
for testing that requires on external resources I.e. SQL servers but you can
use the approach we use for existing storage to provide developer
configurable settings for test setup and skip tests where the test system is
unavailable.

And of course if you have questions about anything then please ask on the
developer list which I've CC'd on this response, this is a subscription
based list which you will need to subscribe to via
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

Best Regards,

Rob Vesse

From:  Miloš Chaloupka <cha...@ho...>
Date:  Monday, 10 February 2014 09:18
To:  Rob Vesse <rv...@do...>
Subject:  DotNetRDF

> Hi Rob,
>  
> I have found you as an author of DotNetRDF so I hope I am contacting the right
> person. I have already written to Tomasz Pluskiewicz, but got no response yet,
> so I am not really sure, whether he even got the message.
>  
> I am currently writing my master thesis "Querying RDF graphs stored in a
> relational database using SPARQL and R2RML" and I am choosing how I will write
> the implementation. I don't want to write a solution that will end as an
> academic work with no chance of real use so I think, that it would be nice to
> make it as a "part" of dotNetRDF. I want to implement it as a store, that will
> be queryable using SPARQL according to R2RML mapping. I can see that you have
> already listed several libraries and that is in fact the only thing I want.
> Maybe you want to ask why I am asking before I am starting the implementation,
> it is because my supervisor wants to make the implementation as a part of
> something bigger so I want to know whether it is possible. Are you interested
> in such storage implementation? And if so, do you have any demands?
>  
> Thank you for your reply,
> best regards,
> Miloš Chaloupka

[dotNetRDF-Develop] dotNetRDF-commits Digest, Vol 16, Issue 1

[<dot...@li...>]

Send dotNetRDF-commits mailing list submissions to
	dot...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits
or, via email, send a message with subject or body 'help' to
	dot...@li...

You can reach the person managing the list at
	dot...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dotNetRDF-commits digest..."


Today's Topics:

   1. commit/dotnetrdf: 2 new changesets (Bitbucket)
   2. commit/dotnetrdf: 3 new changesets (Bitbucket)
   3. commit/dotnetrdf: 4 new changesets (Bitbucket)
   4. commit/dotnetrdf: rvesse: Stub out attributes for declaring
      available RDF input types in assembly attributes (Bitbucket)
   5. commit/dotnetrdf: 2 new changesets (Bitbucket)
   6. commit/dotnetrdf: rvesse: Initial unit test cases and fix for
      CORE-398, this may be symptomatic of a wider problem of incorrect
      algebra compilation of some leave nodes in the Query AST (Bitbucket)
   7. commit/dotnetrdf: 4 new changesets (Bitbucket)
   8. commit/dotnetrdf: 7 new changesets (Bitbucket)
   9. commit/dotnetrdf: 5 new changesets (Bitbucket)


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

Message: 1
Date: Thu, 16 Jan 2014 16:17:56 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

2 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2ffd259c0caa/
Changeset:   2ffd259c0caa
User:        rvesse
Date:        2014-01-16 16:58:32
Summary:     Set version to 1.0.3.3062 for 1.0.3 pre-release build
Affected #:  13 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c0e03cc5f2e2/
Changeset:   c0e03cc5f2e2
User:        rvesse
Date:        2014-01-16 17:17:33
Summary:     Update Release Notes for NuGet packages
Affected #:  2 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 2
Date: Fri, 17 Jan 2014 09:44:18 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

3 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0bb1fb8c7439/
Changeset:   0bb1fb8c7439
User:        rvesse
Date:        2014-01-17 10:24:31
Summary:     Final prep for 1.0.3 release
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1e661983920b/
Changeset:   1e661983920b
User:        rvesse
Date:        2014-01-17 10:25:19
Summary:     Set revision to 3065 for 1.0.3 release
Affected #:  11 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4fccef597589/
Changeset:   4fccef597589
User:        rvesse
Date:        2014-01-17 10:43:41
Summary:     Added tag 1.0.3, 103 for changeset 1e661983920b
Affected #:  1 file

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 3
Date: Wed, 29 Jan 2014 04:32:37 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 4 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

4 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8e5df16373fa/
Changeset:   8e5df16373fa
Branch:      1.9
User:        rvesse
Date:        2014-01-20 05:16:10
Summary:     Merge latest changes into 1.9 branch
Affected #:  319 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3c3b0ab17a01/
Changeset:   3c3b0ab17a01
Branch:      1.9
User:        rvesse
Date:        2014-01-29 05:06:28
Summary:     Stub project for IO.Json module
Affected #:  4 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ad8d2bd3ad20/
Changeset:   ad8d2bd3ad20
Branch:      1.9
User:        rvesse
Date:        2014-01-29 05:26:42
Summary:     Get IO.Json module building
Affected #:  21 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/989fb3f12b49/
Changeset:   989fb3f12b49
Branch:      1.9
User:        rvesse
Date:        2014-01-29 05:31:59
Summary:     Clean up IO.Json module code a little
Affected #:  3 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 4
Date: Wed, 29 Jan 2014 04:48:34 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Stub out
	attributes for declaring available RDF input types in assembly
	attributes
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a3ecfb7a359c/
Changeset:   a3ecfb7a359c
Branch:      1.9
User:        rvesse
Date:        2014-01-29 05:48:23
Summary:     Stub out attributes for declaring available RDF input types in assembly attributes
Affected #:  3 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 5
Date: Thu, 30 Jan 2014 04:23:53 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

2 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4bf8f6f79fc9/
Changeset:   4bf8f6f79fc9
Branch:      1.9
User:        rvesse
Date:        2014-01-30 05:01:22
Summary:     Start setting up test projects for IO modules
Affected #:  10 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2a7d7120ff04/
Changeset:   2a7d7120ff04
Branch:      1.9
User:        rvesse
Date:        2014-01-30 05:23:39
Summary:     Start porting tests to new IO API
Affected #:  18 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 6
Date: Sat, 01 Feb 2014 21:32:46 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Initial unit
	test cases and fix for CORE-398, this may be symptomatic of a wider
	problem of incorrect algebra compilation of some leave nodes in the
	Query AST
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4f4350c3cb2a/
Changeset:   4f4350c3cb2a
Branch:      CORE-398
User:        rvesse
Date:        2014-02-01 22:32:31
Summary:     Initial unit test cases and fix for CORE-398, this may be symptomatic of a wider problem of incorrect algebra compilation of some leave nodes in the Query AST
Affected #:  3 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 7
Date: Thu, 06 Feb 2014 09:45:26 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 4 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

4 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e0abc846eea1/
Changeset:   e0abc846eea1
Branch:      VIRT-397
User:        rvesse
Date:        2014-02-06 10:28:49
Summary:     Fix VIRT-397 in the case where not a standards compliant SPARQL query, update tests to reflect changes in Virtuoso's behaviour regarding SPARQL Updates
Affected #:  3 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c7b57a79586c/
Changeset:   c7b57a79586c
Branch:      VIRT-397
User:        rvesse
Date:        2014-02-06 10:39:19
Summary:     Note VIRT-397 fix in change log
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/95ef92de7668/
Changeset:   95ef92de7668
User:        rvesse
Date:        2014-02-06 10:39:36
Summary:     Merge in VIRT-397 fixes
Affected #:  4 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c83df82e680d/
Changeset:   c83df82e680d
User:        rvesse
Date:        2014-02-06 10:41:05
Summary:     Note aparent Virtuoso bug relating to deleting blank nodes discovered while regression testing VIRT-397 fix
Affected #:  1 file

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 8
Date: Thu, 06 Feb 2014 10:46:33 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 7 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

7 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3d3dcd1fed9d/
Changeset:   3d3dcd1fed9d
Branch:      CORE-398
User:        rvesse
Date:        2014-02-06 10:47:33
Summary:     Merge latest fixes from default
Affected #:  5 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/58606f563733/
Changeset:   58606f563733
Branch:      CORE-398
User:        rvesse
Date:        2014-02-06 11:10:54
Summary:     Fix another bad algebra translation related to CORE-398
Affected #:  3 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c65f15d1dbec/
Changeset:   c65f15d1dbec
Branch:      CORE-398
User:        rvesse
Date:        2014-02-06 11:17:33
Summary:     Additional tests to verify CORE-398 bug interaction with inline data
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/24c2c4a94217/
Changeset:   24c2c4a94217
Branch:      CORE-398
User:        rvesse
Date:        2014-02-06 11:44:57
Summary:     Fix an inadvertent SO error in Service.ToString() caused by CORE-398 fix
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9b1da68e5b06/
Changeset:   9b1da68e5b06
Branch:      CORE-398
User:        rvesse
Date:        2014-02-06 11:45:31
Summary:     Note CORE-398 fix in Change Log
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c5d9d3b1d639/
Changeset:   c5d9d3b1d639
Branch:      CORE-398
User:        rvesse
Date:        2014-02-06 11:45:40
Summary:     Close CORE-398 branch
Affected #:  0 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/152b353efc61/
Changeset:   152b353efc61
User:        rvesse
Date:        2014-02-06 11:46:02
Summary:     Merge CORE-398 fixes
Affected #:  7 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 9
Date: Thu, 13 Feb 2014 11:06:37 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 5 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

5 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8406b4ca739b/
Changeset:   8406b4ca739b
User:        rvesse
Date:        2014-02-06 12:05:45
Summary:     Thrown an informative error when Full HTTP Debugging is enabled and the stream has been consumed
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2590083c77b3/
Changeset:   2590083c77b3
User:        rvesse
Date:        2014-02-06 15:10:00
Summary:     Add unit tests to try to reproduce a user error, not yet reproducible
Affected #:  7 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1579bda2635e/
Changeset:   1579bda2635e
Branch:      VIRT-399
User:        rvesse
Date:        2014-02-13 11:52:29
Summary:     Fix for VIRT-399
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e6254bd1ceff/
Changeset:   e6254bd1ceff
Branch:      VIRT-399
User:        rvesse
Date:        2014-02-13 11:55:27
Summary:     Note VIRT-399 fix in Change Log
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4af612aba8e2/
Changeset:   4af612aba8e2
User:        rvesse
Date:        2014-02-13 11:55:42
Summary:     Merge VIRT-399 fix to default
Affected #:  2 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience.  Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk

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

_______________________________________________
dotNetRDF-commits mailing list
dot...@li...
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits


End of dotNetRDF-commits Digest, Vol 16, Issue 1
************************************************

Re: [dotNetRDF-Develop] New SPIN library for dotNetRDF

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

Just to update everyone on this me and Max have been discussing the pull
request and bar clearing up one final code modification to the Core library
we should be able to merge this shortly.

Max likely has more work to do to complete the implementation but we should
have enough to start pushing out some pre-release builds to NuGet for people
to try out

Cheers,

Rob

From:  Max - Micrologiciel <ma...@mi...>
Reply-To:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Date:  Friday, 31 January 2014 15:31
To:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Subject:  [dotNetRDF-Develop] New SPIN library for dotNetRDF

> Hi Rob and everyone,
> 
> First I wish you all a happy new year and the best for 2014 (on the dead-line
> as usual ;)).
> 
> As I told Rob, I've been working on RDF access control and business rules
> issues for a while and as I worked and searched for useful
> tips/recommandations, SPIN rose as an evidence.
> 
> So I'm submitting (yet as a pull request) a first implementation of a SPIN
> processing engine for dotNetRDF.
> 
> As stated in the pull request message :
> 
>> The first issues that are addressed within this pull request are :
>> * the capability to work on a dataset with any non-SPIN-capable storage
>> provider that supports SPARQL 1.1 (including Leviathan processed datasets
>> wrapped within an InMemoryManager instance)
>> * complete isolation level with other API clients (inferred triples included)
>> while SPIN processing is performed and until the dataset changes are flushed,
>> * the capability to monitor updates on the dataset's graphs for subsequent
>> SPIN constructors/rules/constraints checks processing (only supported yet or
>> INSERT/DELETE DATA commands)
>> The main things that remain to be done are :
>> * to finalize the SPARQL updates rewriting to allow for any query form to be
>> monitored through the triples addition/removal temporary graphs design.
>> * to provide an implementation of the SPIN processing pipeline on Updates.
> 
> I would add that addressing update concurrency issues would in time be welcome
> if someone has any experience in this domain.
> 
> Note to those who would be interested to contribute on this:
> the implementation is based on Jena 's SPIN library (from TopBraid) so many
> classes are now unused and were just ported to c# for compilation need, but
> they are kept in the project for reference only until equvalent features have
> been provided.
> 
> Max.
> 
> 
>  
> ------------------------------------------------------------------------------
> WatchGuard Dimension instantly turns raw network data into actionable security
> intelligence. It gives you real-time visual feedback on key security issues
> and trends.  Skip the complicated setup - simply import a virtual appliance
> and go from zero to informed in seconds.
> http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk__
> _____________________________________________ dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

[dotNetRDF-Develop] Issue VIRT-399 has been updated by Rob Vesse

[<tr...@do...>]

<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Recent Virtuoso releases are missing the bif:rdf_make_iid_of_qname() function</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll)</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Milestone changed from "Unassigned" to "1.0.4"
                                </li>
      </ul>
    </td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=399" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=399</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>

[dotNetRDF-Develop] Issue VIRT-359 has been updated by Rob Vesse

[<tr...@do...>]

<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Upgrade Virtuoso ADO.Net providers to latest releases</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll)</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Milestone changed from "1.0.4" to "Unscheduled"
                                </li>
      </ul>
    </td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=359" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=359</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>

[dotNetRDF-Develop] Issue VIRT-399 has been updated by Rob Vesse

[<tr...@do...>]

<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Recent Virtuoso releases are missing the bif:rdf_make_iid_of_qname() function</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll)</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Status changed from "Confirmed" to "In Progress"
                                </li>
      </ul>
    </td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=399" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=399</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>

[dotNetRDF-Develop] Issue VIRT-399 has a new comment

[<tr...@do...>]

<p>A new comment has been added to the following issue.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Recent Virtuoso releases are missing the bif:rdf_make_iid_of_qname() function</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll)</td>
  </tr>
  <tr>
    <td><b>Created By:</b></td>
    <td>Rob Vesse</td>
  </tr>
  <tr>
    <td><b>Date:</b></td>
    <td>2014-02-10 09:25 AM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Heard back from the Virtuoso folks and this is due to the function no longer being accessible via the bif: prefix but it will be available via the sql: prefix instead and this will be backwards compatible so we will adopt this as a fix</p></td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=399" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=399</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>

Re: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()

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

No problem

Should you succeed in nailing down the cause (whether it is dotNetRDF or
otherwise) if you could let us know that would be much appreciated

Thanks,

Rob

From:  Rob Nicholls <ro...@co...>
Date:  Thursday, 6 February 2014 16:31
To:  Rob Vesse <rv...@do...>, 'dotNetRDF Developer Discussion and
Feature Request' <dot...@li...>
Subject:  RE: [dotNetRDF-Develop] Stackoverflow calling
QueryWithResultGraph()

> Thanks for your help Rob,
>  
> Yes ­ pretty much where we got to. It¹s totally sporadic, and hard to
> reproduce. It works sometimes, and not others ­ it either always works, or
> always stackoverflows, on multiple environments (irrelevant of build
> settings).
>  
> We first used a named graph, and now we don¹t. Left the queries (several
> hundred of them) using named graphs as doesn¹t (seem to, we¹re still learning)
> make any difference as you mention.
>  
> dotNetRDF > pulled via nuget
> Version: 1.0.3.0
> Description: API for manipulating RDF data (.Net 4.0)
>  
> Based on it probably being a environment or config related issue, and before
> you waste any more time, I¹ll try some more debugging off your code base
> (rather than release assemblies) and double checking our dependency graph to
> make it¹s not something else impacting.
>  
> The triple store is over a gigabyte I believe, so will try and avoid sending
> that over for the time being.
>  
> Many thanks.
>  
>  
> 
> From: Rob Vesse [mailto:rv...@do...]
> Sent: 06 February 2014 15:16
> To: dotNetRDF Developer Discussion and Feature Request
> Cc: Rob Nicholls
> Subject: Re: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()
>  
> 
> So I am pretty stumped on this as I've been completely unable to reproduce
> this after several hours of trying.
> 
>  
> 
> I checked whether you could easily hit a StackOverflow with the RDF/XML parser
> and you really can't.  I wrote unit tests which call the parser from 5,000
> levels deep of recursion and did not get a StackOverflow so I don't see how
> the data alone could cause the issue.
> 
>  
> 
> I've also put the data you provided into a local instance of Fuseki and ran
> the query against it using SparqlRemoteEndpoint.QueryWithResultGraph() and I
> cannot produce a StackOverflow.
> 
>  
> 
> Part of my problem is that I just don't seem to have quite the same setup as
> you, your query uses named graphs but your data does not include them so I had
> to modify the query slightly.  Yet I don't see how that would make any
> difference especially since the CONSTRUCT template remains identical between
> your query and mine so the data received should be identical.
> 
>  
> 
> You state that you've reproduced this in a console app so could you please
> provide your console app that reproduces the issue along with your raw data
> (assuming a TDB database zipping up the TDB folder would provide this) that I
> can run under the debugger on my system to see what is going on?
> 
> Failing that can you run under the debugger and capture what the stack trace
> is at the point where the StackOverflowException gets thrown? As otherwise I
> can't really do any further useful debugging on this.
> 
>  
> 
> Also can you please confirm again exactly the build of dotNetRDF being used?
> If you can look at the properties for the dotNetRDF dependency in VS and look
> at the Version and the Description strings and provide that information, the
> Description is particularly relevant because that will tell me exactly which
> of the core library builds you are using.
> 
>  
> 
> Thanks,
> 
>  
> 
> Rob
> 
>  
> 
> From: Rob Vesse <rv...@do...>
> Reply-To: dotNetRDF Developer Discussion and Feature Request
> <dot...@li...>
> Date: Thursday, 6 February 2014 11:12
> To: Rob Nicholls <ro...@co...>
> Cc: dotNetRDF Developer Discussion and Feature Request
> <dot...@li...>
> Subject: SPAM-LOW: Re: [dotNetRDF-Develop] Stackoverflow calling
> QueryWithResultGraph()
> 
>  
>> 
>> Thanks for the additional information, the RDF/XML is perfectly valid as you
>> noted.
>> 
>>  
>> 
>> That error is not really more descriptive, turning on the HTTP Full Debugging
>> consumes the response stream so the calling code then has an already closed
>> stream which causes different errors depending on the calling code.  I've
>> changed this behaviour in our default branch so that it'll now throw an error
>> informing you that the response stream was consumed and not available to
>> calling code.
>> 
>>  
>> 
>> The RDF/XML parser code does recurse heavily so I'm wondering if this file is
>> just under the stack limit when parsed in the rdfEditor but when called via
>> the SparqlRemoteEndpoint which itself has several levels of recursion tips it
>> over the edge.  I'm going to take the data you provided and debug this
>> further and will get back to you when I know more
>> 
>>  
>> 
>> Rob
>> 
>>  
>> 
>> From: Rob Nicholls <ro...@co...>
>> Date: Monday, 3 February 2014 13:46
>> To: Rob Vesse <rv...@do...>
>> Cc: 'dotNetRDF Developer Discussion and Feature Request'
>> <dot...@li...>
>> Subject: RE: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()
>> 
>>  
>>> 
>>> Ahh, missed that. Thanks.
>>>  
>>> Ok, now throwing a more descriptive error; XML parser, root element is
>>> missing.
>>>  
>>> Output attached.
>>>  
>>> I¹ve checked the RDF with your RDFeditor validator, no problems.
>>>  
>>> Is it feasibly a memory issue, based on the size of the RDF/XML? (I¹ve
>>> stripped the code right back to a simple console app using dotNetRDF ­ same
>>> result) Or maybe I¹m missing something obvious?
>>>  
>>> /Rob
>>>  
>>> 
>>> From: Rob Vesse [mailto:rv...@do...]
>>> Sent: 30 January 2014 19:16
>>> To: Rob Nicholls
>>> Cc: dotNetRDF Developer Discussion and Feature Request
>>> Subject: Re: [dotNetRDF-Develop] Stackoverflow calling
>>> QueryWithResultGraph()
>>>  
>>> 
>>> Ok, that's useful information.  Specific version of Fuseki should not be an
>>> issue since I don't see anything in the query that would trigger any known
>>> bugs in Fuseki/TDB/ARQ
>>> 
>>>  
>>> 
>>> Would be interesting to see what format Fuseki is returning the data in when
>>> called from dotNetRDF.  Could you run the query with HTTP Debugging turned
>>> on as detailed at [1] and provide the HTTP traces this produces to the
>>> console?
>>> 
>>>  
>>> 
>>> The full HTTP trace could be particularly useful in determining if there is
>>> something in the data serialisation of the results of this query that
>>> triggers a SO in one of the dotNetRDF parsers.
>>> 
>>>  
>>> 
>>> Thanks,
>>> 
>>>  
>>> 
>>> Rob
>>> 
>>>  
>>> 
>>> [1]: 
>>> https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/HowTo/Debug%20HTTP%20Communic
>>> ation.wiki#!debugging-http-communication
>>> 
>>>  
>>> 
>>>  
>>> 
>>> From: Rob Nicholls <ro...@co...>
>>> Date: Thursday, 30 January 2014 10:26
>>> To: Rob Vesse <rv...@do...>, 'dotNetRDF Developer Discussion and
>>> Feature Request' <dot...@li...>
>>> Subject: RE: [dotNetRDF-Develop] Stackoverflow calling
>>> QueryWithResultGraph()
>>> 
>>>  
>>>> 
>>>> dotnetRDF library to query (via .NET4.5 build)
>>>> Jena Fuseki for the Triple Store and Endpoint (I forget specific versions,
>>>> but will check if helpful)
>>>> mmx is our Dataset
>>>>  
>>>> Calling code is basically (omitted the noise):
>>>>  
>>>> _endpoint = new SparqlRemoteEndpoint(³http://jena:3030/mmx/query²);
>>>> IGraph graph = _endpoint.QueryWithResultGraph(thequery); // ß Stackoverflow
>>>> here
>>>>  
>>>> Where thequery is:
>>>>  
>>>> 
>>>>   1 PREFIX  dc:   <http://purl.org/dc/elements/1.1/>
>>>>   2 PREFIX  exif: <http://www.w3.org/2003/12/exif/ns/>
>>>>   3 PREFIX  rdfs: <http://www.w3.org/2000/01/rdf-schema#
>>>> <http://www.w3.org/2000/01/rdf-schema> >
>>>>   4 PREFIX  mmx:  <http://data.sciencemuseum.org.uk/def/ontology/>
>>>>   5 PREFIX  foaf: <http://xmlns.com/foaf/0.1/>
>>>>   6 PREFIX  rdf:  <http://www.w3.org/1999/02/22-rdf-syntax-ns#
>>>> <http://www.w3.org/1999/02/22-rdf-syntax-ns> >
>>>>   7 PREFIX  skos: <http://www.w3.org/2004/02/skos/core#
>>>> <http://www.w3.org/2004/02/skos/core> >
>>>>   8 PREFIX  dcterms: <http://purl.org/dc/terms/>
>>>>   9 
>>>>  10 CONSTRUCT 
>>>>  11   { ?ass mmx:relatedArchiveDocument
>>>> <http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .
>>>> 12     ?ass rdf:type mmx:Asset .
>>>> 13     ?ass dcterms:hasVersion ?ver .
>>>> 14     ?ver ?pred2 ?obj2 .
>>>> 15     ?ass ?p2 ?o2 .}
>>>> 16 WHERE
>>>> 17   {   { GRAPH ?g
>>>> 18           { ?ass mmx:relatedArchiveDocument
>>>> <http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .
>>>> 19             ?ass dcterms:hasVersion ?ver .
>>>> 20             ?ver ?pred2 ?obj2
>>>> 21           }
>>>> 22       }
>>>> 23     UNION
>>>> 24       { GRAPH ?g
>>>> 25           { ?ass mmx:relatedArchiveDocument
>>>> <http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .
>>>> 26             ?ass ?p2 ?o2
>>>> 27           }
>>>> 28       }
>>>> 29   }
>>>>  
>>>> Thought I¹d exclude the setup and query as, as mentioned, the query does
>>>> work (and did, only recently started throwing the exception ­ hence I
>>>> wondered if it was data, or maybe encoding, related based on how dotnetRDF
>>>> is parsingŠ).
>>>> 
>>>> The attached triples were the result of the construct from above, not the
>>>> entire triple store.
>>>>  
>>>> This all works fine for small result sets, it¹s just this particular query
>>>> returns 360 relatedArchiveDocument¹s and the library doesn¹t seem to like
>>>> it.
>>>>  
>>>> If it¹s nothing obvious, I will grab your source code and try and debug
>>>> further ­ can¹t tell much of what is happening within
>>>> QueryWithResultGraph() atm.
>>>>  
>>>> /Rob
>>>>  
>>>>  
>>>> 
>>>> From: Rob Vesse [mailto:rv...@do...]
>>>> Sent: 30 January 2014 17:12
>>>> To: dotNetRDF Developer Discussion and Feature Request
>>>> Cc: ro...@co...
>>>> Subject: Re: [dotNetRDF-Develop] Stackoverflow calling
>>>> QueryWithResultGraph()
>>>>  
>>>> 
>>>> Rob
>>>> 
>>>>  
>>>> 
>>>> You didn't include the query or any context of how you invoke the query so
>>>> we can't really offer any attempt at diagnosis.  Please provide a minimal
>>>> complete example.
>>>> 
>>>>  
>>>> 
>>>> Are the results you provided the results of a successful run of the
>>>> specific query or a dump of the entire test dataset?  Nothing looks
>>>> untoward with the data so likely some interaction with the specific query.
>>>> 
>>>>  
>>>> 
>>>> QueryWithResultGraph() implies use of SparqlRemoteEndpoint (whether
>>>> directly/indirectly) to query a remote service so can you provide the code
>>>> that invokes the query plus the specific problematic query.  The only kind
>>>> of query that springs to mind that could easily lead to a StackOverflow
>>>> would be a complex property path but without seeing the query I can't tell,
>>>> it may well be something innocuous hitting a rare corner case in our SPARQL
>>>> engine.
>>>> 
>>>>  
>>>> 
>>>> Also what can you tell us about the set up of that remote service since you
>>>> imply you control that as well.  Is the remote server using dotNetRDF to
>>>> host the data, if so what's the setup?
>>>> 
>>>>  
>>>> 
>>>> Or if it isn't under your control can you tell us anything about it e.g.
>>>> endpoint, server software if known etc
>>>> 
>>>>  
>>>> 
>>>> Thanks,
>>>> 
>>>>  
>>>> 
>>>> Rob Vesse
>>>> 
>>>>  
>>>> 
>>>> From: Rob Nicholls <ro...@co...>
>>>> Reply-To: dotNetRDF Developer Discussion and Feature Request
>>>> <dot...@li...>
>>>> Date: Thursday, 30 January 2014 05:44
>>>> To: <dot...@li...>
>>>> Subject: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()
>>>> 
>>>>  
>>>>> 
>>>>> Hi all,
>>>>>  
>>>>> I¹m receiving consistent stack overflows from QueryWithResultGraph(query)
>>>>> when using a specific query against our triple store. The query runs fine
>>>>> (within ms) and returns results ok.
>>>>>  
>>>>> Results returned from the triple store are in the attached file
>>>>> (queryresults.txt), not a huge amount of data to justify killing a 12GB
>>>>> web server, and it does occasionally function correctly on my developer
>>>>> machine (never when running the debugger though).
>>>>>  
>>>>> Can anyone offer any advice?
>>>>> Is this perhaps an issue with the data itself causing some kind of
>>>>> circular reference? Although doesn¹t explain why it occasionally works.
>>>>>  
>>>>> Using: 
>>>>> dotnetRdf 1.0.3 / .NET4.5
>>>>>  
>>>>> Many thanks,
>>>>> Rob
>>>>>  
>>>>> cogapp
>>>>>  
>>>>>  
>>>>> Rob Nicholls
>>>>> Senior Programmer
>>>>> +44 1273 821600
>>>>> www.cogapp.com <http://www.cogapp.com/>
>>>>>  
>>>>> Cogapp Brighton
>>>>> 21-33 Dyke Road, Brighton, BN1 3FE. UK
>>>>>  
>>>>> Cogapp New York
>>>>> 641 Lexington Avenue, 15th Floor, New York, NY 10022, USA
>>>>>  
>>>>> News 
>>>>> Pocahontas' portrait and letters from George Washington online: a
>>>>> responsive website for the Virginia Historical Society
>>>>> <http://www.vahistorical.org/> , just launched.
>>>>> 
>>>>> For regular Cogapp news, please follow us on Twitter
>>>>> <https://twitter.com/cogapp> .
>>>>>  
>>>>> --------------------------------------------------------------------------
>>>>> ---- WatchGuard Dimension instantly turns raw network data into actionable
>>>>> security intelligence. It gives you real-time visual feedback on key
>>>>> security issues and trends. Skip the complicated setup - simply import a
>>>>> virtual appliance and go from zero to informed in seconds.
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clkt
>>>>> rk_______________________________________________ dotNetRDF-develop
>>>>> mailing list dot...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>> -----------------------------------------------------------------------------
>> - Managing the Performance of Cloud-Based Applications Take advantage of what
>> the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper.
>> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk_
>> ______________________________________________ dotNetRDF-develop mailing list
>> dot...@li...
>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

Re: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()

[Rob N. <ro...@co...>]

Thanks for your help Rob,

 

Yes – pretty much where we got to. It’s totally sporadic, and hard to
reproduce. It works sometimes, and not others – it either always works, or
always stackoverflows, on multiple environments (irrelevant of build
settings).

 

We first used a named graph, and now we don’t. Left the queries (several
hundred of them) using named graphs as doesn’t (seem to, we’re still
learning) make any difference as you mention.

 

dotNetRDF > pulled via nuget

Version: 1.0.3.0

Description: API for manipulating RDF data (.Net 4.0)

 

Based on it probably being a environment or config related issue, and before
you waste any more time, I’ll try some more debugging off your code base
(rather than release assemblies) and double checking our dependency graph to
make it’s not something else impacting. 

 

The triple store is over a gigabyte I believe, so will try and avoid sending
that over for the time being.

 

Many thanks.

 

 

From: Rob Vesse [mailto:rv...@do...] 
Sent: 06 February 2014 15:16
To: dotNetRDF Developer Discussion and Feature Request
Cc: Rob Nicholls
Subject: Re: [dotNetRDF-Develop] Stackoverflow calling
QueryWithResultGraph()

 

So I am pretty stumped on this as I've been completely unable to reproduce
this after several hours of trying.

 

I checked whether you could easily hit a StackOverflow with the RDF/XML
parser and you really can't.  I wrote unit tests which call the parser from
5,000 levels deep of recursion and did not get a StackOverflow so I don't
see how the data alone could cause the issue.

 

I've also put the data you provided into a local instance of Fuseki and ran
the query against it using SparqlRemoteEndpoint.QueryWithResultGraph() and I
cannot produce a StackOverflow.

 

Part of my problem is that I just don't seem to have quite the same setup as
you, your query uses named graphs but your data does not include them so I
had to modify the query slightly.  Yet I don't see how that would make any
difference especially since the CONSTRUCT template remains identical between
your query and mine so the data received should be identical.

 

You state that you've reproduced this in a console app so could you please
provide your console app that reproduces the issue along with your raw data
(assuming a TDB database zipping up the TDB folder would provide this) that
I can run under the debugger on my system to see what is going on?

Failing that can you run under the debugger and capture what the stack trace
is at the point where the StackOverflowException gets thrown? As otherwise I
can't really do any further useful debugging on this.

 

Also can you please confirm again exactly the build of dotNetRDF being used?
If you can look at the properties for the dotNetRDF dependency in VS and
look at the Version and the Description strings and provide that
information, the Description is particularly relevant because that will tell
me exactly which of the core library builds you are using.

 

Thanks,

 

Rob

 

From: Rob Vesse <rv...@do...>
Reply-To: dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Date: Thursday, 6 February 2014 11:12
To: Rob Nicholls <ro...@co...>
Cc: dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Subject: SPAM-LOW: Re: [dotNetRDF-Develop] Stackoverflow calling
QueryWithResultGraph()

 

Thanks for the additional information, the RDF/XML is perfectly valid as you
noted.

 

That error is not really more descriptive, turning on the HTTP Full
Debugging consumes the response stream so the calling code then has an
already closed stream which causes different errors depending on the calling
code.  I've changed this behaviour in our default branch so that it'll now
throw an error informing you that the response stream was consumed and not
available to calling code.

 

The RDF/XML parser code does recurse heavily so I'm wondering if this file
is just under the stack limit when parsed in the rdfEditor but when called
via the SparqlRemoteEndpoint which itself has several levels of recursion
tips it over the edge.  I'm going to take the data you provided and debug
this further and will get back to you when I know more

 

Rob

 

From: Rob Nicholls <ro...@co...>
Date: Monday, 3 February 2014 13:46
To: Rob Vesse <rv...@do...>
Cc: 'dotNetRDF Developer Discussion and Feature Request'
<dot...@li...>
Subject: RE: [dotNetRDF-Develop] Stackoverflow calling
QueryWithResultGraph()

 

Ahh, missed that. Thanks.

 

Ok, now throwing a more descriptive error; XML parser, root element is
missing.

 

Output attached.

 

I’ve checked the RDF with your RDFeditor validator, no problems.

 

Is it feasibly a memory issue, based on the size of the RDF/XML? (I’ve
stripped the code right back to a simple console app using dotNetRDF – same
result) Or maybe I’m missing something obvious?

 

/Rob

 

From: Rob Vesse [mailto:rv...@do...] 
Sent: 30 January 2014 19:16
To: Rob Nicholls
Cc: dotNetRDF Developer Discussion and Feature Request
Subject: Re: [dotNetRDF-Develop] Stackoverflow calling
QueryWithResultGraph()

 

Ok, that's useful information.  Specific version of Fuseki should not be an
issue since I don't see anything in the query that would trigger any known
bugs in Fuseki/TDB/ARQ

 

Would be interesting to see what format Fuseki is returning the data in when
called from dotNetRDF.  Could you run the query with HTTP Debugging turned
on as detailed at [1] and provide the HTTP traces this produces to the
console?

 

The full HTTP trace could be particularly useful in determining if there is
something in the data serialisation of the results of this query that
triggers a SO in one of the dotNetRDF parsers.

 

Thanks,

 

Rob

 

[1]:
https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/HowTo/Debug%20HTTP%20Communic
ation.wiki#!debugging-http-communication

 

 

From: Rob Nicholls <ro...@co...>
Date: Thursday, 30 January 2014 10:26
To: Rob Vesse <rv...@do...>, 'dotNetRDF Developer Discussion and
Feature Request' <dot...@li...>
Subject: RE: [dotNetRDF-Develop] Stackoverflow calling
QueryWithResultGraph()

 

dotnetRDF library to query (via .NET4.5 build)

Jena Fuseki for the Triple Store and Endpoint (I forget specific versions,
but will check if helpful)

mmx is our Dataset

 

Calling code is basically (omitted the noise):

 

_endpoint = new SparqlRemoteEndpoint(“http://jena:3030/mmx/query”);

IGraph graph = _endpoint.QueryWithResultGraph(thequery); // ß Stackoverflow
here

 

Where thequery is:

 

  1 PREFIX  dc:   <http://purl.org/dc/elements/1.1/>

  2 PREFIX  exif: <http://www.w3.org/2003/12/exif/ns/>

  3 PREFIX  rdfs: <http://www.w3.org/2000/01/rdf-schema#
<http://www.w3.org/2000/01/rdf-schema> >

  4 PREFIX  mmx:  <http://data.sciencemuseum.org.uk/def/ontology/>

  5 PREFIX  foaf: <http://xmlns.com/foaf/0.1/>

  6 PREFIX  rdf:  <http://www.w3.org/1999/02/22-rdf-syntax-ns#
<http://www.w3.org/1999/02/22-rdf-syntax-ns> >

  7 PREFIX  skos: <http://www.w3.org/2004/02/skos/core#
<http://www.w3.org/2004/02/skos/core> >

  8 PREFIX  dcterms: <http://purl.org/dc/terms/>

  9 

 10 CONSTRUCT 

 11   { ?ass mmx:relatedArchiveDocument
<http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .

12     ?ass rdf:type mmx:Asset .

13     ?ass dcterms:hasVersion ?ver .

14     ?ver ?pred2 ?obj2 .

15     ?ass ?p2 ?o2 .}

16 WHERE

17   {   { GRAPH ?g

18           { ?ass mmx:relatedArchiveDocument
<http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .

19             ?ass dcterms:hasVersion ?ver .

20             ?ver ?pred2 ?obj2

21           }

22       }

23     UNION

24       { GRAPH ?g

25           { ?ass mmx:relatedArchiveDocument
<http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .

26             ?ass ?p2 ?o2

27           }

28       }

29   }

 

Thought I’d exclude the setup and query as, as mentioned, the query does
work (and did, only recently started throwing the exception – hence I
wondered if it was data, or maybe encoding, related based on how dotnetRDF
is parsing…).


The attached triples were the result of the construct from above, not the
entire triple store.

 

This all works fine for small result sets, it’s just this particular query
returns 360 relatedArchiveDocument’s and the library doesn’t seem to like
it.

 

If it’s nothing obvious, I will grab your source code and try and debug
further – can’t tell much of what is happening within QueryWithResultGraph()
atm.

 

/Rob

 

 

From: Rob Vesse [mailto:rv...@do...] 
Sent: 30 January 2014 17:12
To: dotNetRDF Developer Discussion and Feature Request
Cc: ro...@co...
Subject: Re: [dotNetRDF-Develop] Stackoverflow calling
QueryWithResultGraph()

 

Rob

 

You didn't include the query or any context of how you invoke the query so
we can't really offer any attempt at diagnosis.  Please provide a minimal
complete example.

 

Are the results you provided the results of a successful run of the specific
query or a dump of the entire test dataset?  Nothing looks untoward with the
data so likely some interaction with the specific query.

 

QueryWithResultGraph() implies use of SparqlRemoteEndpoint (whether
directly/indirectly) to query a remote service so can you provide the code
that invokes the query plus the specific problematic query.  The only kind
of query that springs to mind that could easily lead to a StackOverflow
would be a complex property path but without seeing the query I can't tell,
it may well be something innocuous hitting a rare corner case in our SPARQL
engine.

 

Also what can you tell us about the set up of that remote service since you
imply you control that as well.  Is the remote server using dotNetRDF to
host the data, if so what's the setup?

 

Or if it isn't under your control can you tell us anything about it e.g.
endpoint, server software if known etc

 

Thanks,

 

Rob Vesse

 

From: Rob Nicholls <ro...@co...>
Reply-To: dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Date: Thursday, 30 January 2014 05:44
To: <dot...@li...>
Subject: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()

 

Hi all,

 

I’m receiving consistent stack overflows from QueryWithResultGraph(query)
when using a specific query against our triple store. The query runs fine
(within ms) and returns results ok.

 

Results returned from the triple store are in the attached file
(queryresults.txt), not a huge amount of data to justify killing a 12GB web
server, and it does occasionally function correctly on my developer machine
(never when running the debugger though).

 

Can anyone offer any advice?

Is this perhaps an issue with the data itself causing some kind of circular
reference? Although doesn’t explain why it occasionally works.

 

Using: 

dotnetRdf 1.0.3 / .NET4.5

 

Many thanks,

Rob

 

cogapp

 

 

Rob Nicholls

Senior Programmer 

+44 1273 821600

 <http://www.cogapp.com/> www.cogapp.com

 

Cogapp Brighton

21-33 Dyke Road, Brighton, BN1 3FE. UK

 

Cogapp New York 

641 Lexington Avenue, 15th Floor, New York, NY 10022, USA 

 

News 

Pocahontas' portrait and letters from George Washington online: a responsive
website for the  <http://www.vahistorical.org/> Virginia Historical Society,
just launched.


For regular Cogapp news, please follow us on  <https://twitter.com/cogapp>
Twitter.

 

----------------------------------------------------------------------------
-- WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import a
virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991
<http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktr
k_______________________________________________>
&iu=/4140/ostg.clktrk_______________________________________________
dotNetRDF-develop mailing list dot...@li...
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop 

----------------------------------------------------------------------------
-- Managing the Performance of Cloud-Based Applications Take advantage of
what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231
<http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktr
k_______________________________________________>
&iu=/4140/ostg.clktrk_______________________________________________
dotNetRDF-develop mailing list dot...@li...
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop 

Re: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()

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

So I am pretty stumped on this as I've been completely unable to reproduce
this after several hours of trying.

I checked whether you could easily hit a StackOverflow with the RDF/XML
parser and you really can't.  I wrote unit tests which call the parser from
5,000 levels deep of recursion and did not get a StackOverflow so I don't
see how the data alone could cause the issue.

I've also put the data you provided into a local instance of Fuseki and ran
the query against it using SparqlRemoteEndpoint.QueryWithResultGraph() and I
cannot produce a StackOverflow.

Part of my problem is that I just don't seem to have quite the same setup as
you, your query uses named graphs but your data does not include them so I
had to modify the query slightly.  Yet I don't see how that would make any
difference especially since the CONSTRUCT template remains identical between
your query and mine so the data received should be identical.

You state that you've reproduced this in a console app so could you please
provide your console app that reproduces the issue along with your raw data
(assuming a TDB database zipping up the TDB folder would provide this) that
I can run under the debugger on my system to see what is going on?
Failing that can you run under the debugger and capture what the stack trace
is at the point where the StackOverflowException gets thrown? As otherwise I
can't really do any further useful debugging on this.

Also can you please confirm again exactly the build of dotNetRDF being used?
If you can look at the properties for the dotNetRDF dependency in VS and
look at the Version and the Description strings and provide that
information, the Description is particularly relevant because that will tell
me exactly which of the core library builds you are using.

Thanks,

Rob

From:  Rob Vesse <rv...@do...>
Reply-To:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Date:  Thursday, 6 February 2014 11:12
To:  Rob Nicholls <ro...@co...>
Cc:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Subject:  SPAM-LOW:  Re: [dotNetRDF-Develop] Stackoverflow calling
QueryWithResultGraph()

> Thanks for the additional information, the RDF/XML is perfectly valid as you
> noted.
> 
> That error is not really more descriptive, turning on the HTTP Full Debugging
> consumes the response stream so the calling code then has an already closed
> stream which causes different errors depending on the calling code.  I've
> changed this behaviour in our default branch so that it'll now throw an error
> informing you that the response stream was consumed and not available to
> calling code.
> 
> The RDF/XML parser code does recurse heavily so I'm wondering if this file is
> just under the stack limit when parsed in the rdfEditor but when called via
> the SparqlRemoteEndpoint which itself has several levels of recursion tips it
> over the edge.  I'm going to take the data you provided and debug this further
> and will get back to you when I know more
> 
> Rob
> 
> From:  Rob Nicholls <ro...@co...>
> Date:  Monday, 3 February 2014 13:46
> To:  Rob Vesse <rv...@do...>
> Cc:  'dotNetRDF Developer Discussion and Feature Request'
> <dot...@li...>
> Subject:  RE: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()
> 
>> Ahh, missed that. Thanks.
>>  
>> Ok, now throwing a more descriptive error; XML parser, root element is
>> missing.
>>  
>> Output attached.
>>  
>> I¹ve checked the RDF with your RDFeditor validator, no problems.
>>  
>> Is it feasibly a memory issue, based on the size of the RDF/XML? (I¹ve
>> stripped the code right back to a simple console app using dotNetRDF ­ same
>> result) Or maybe I¹m missing something obvious?
>>  
>> /Rob
>>  
>> 
>> From: Rob Vesse [mailto:rv...@do...]
>> Sent: 30 January 2014 19:16
>> To: Rob Nicholls
>> Cc: dotNetRDF Developer Discussion and Feature Request
>> Subject: Re: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()
>>  
>> 
>> Ok, that's useful information.  Specific version of Fuseki should not be an
>> issue since I don't see anything in the query that would trigger any known
>> bugs in Fuseki/TDB/ARQ
>> 
>>  
>> 
>> Would be interesting to see what format Fuseki is returning the data in when
>> called from dotNetRDF.  Could you run the query with HTTP Debugging turned on
>> as detailed at [1] and provide the HTTP traces this produces to the console?
>> 
>>  
>> 
>> The full HTTP trace could be particularly useful in determining if there is
>> something in the data serialisation of the results of this query that
>> triggers a SO in one of the dotNetRDF parsers.
>> 
>>  
>> 
>> Thanks,
>> 
>>  
>> 
>> Rob
>> 
>>  
>> 
>> [1]: 
>> https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/HowTo/Debug%20HTTP%20Communica
>> tion.wiki#!debugging-http-communication
>> 
>>  
>> 
>>  
>> 
>> From: Rob Nicholls <ro...@co...>
>> Date: Thursday, 30 January 2014 10:26
>> To: Rob Vesse <rv...@do...>, 'dotNetRDF Developer Discussion and
>> Feature Request' <dot...@li...>
>> Subject: RE: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()
>> 
>>  
>>> 
>>> dotnetRDF library to query (via .NET4.5 build)
>>> Jena Fuseki for the Triple Store and Endpoint (I forget specific versions,
>>> but will check if helpful)
>>> mmx is our Dataset
>>>  
>>> Calling code is basically (omitted the noise):
>>>  
>>> _endpoint = new SparqlRemoteEndpoint(³http://jena:3030/mmx/query²);
>>> IGraph graph = _endpoint.QueryWithResultGraph(thequery); // ß Stackoverflow
>>> here
>>>  
>>> Where thequery is:
>>>  
>>> 
>>>   1 PREFIX  dc:   <http://purl.org/dc/elements/1.1/>
>>>   2 PREFIX  exif: <http://www.w3.org/2003/12/exif/ns/>
>>>   3 PREFIX  rdfs: <http://www.w3.org/2000/01/rdf-schema#
>>> <http://www.w3.org/2000/01/rdf-schema> >
>>>   4 PREFIX  mmx:  <http://data.sciencemuseum.org.uk/def/ontology/>
>>>   5 PREFIX  foaf: <http://xmlns.com/foaf/0.1/>
>>>   6 PREFIX  rdf:  <http://www.w3.org/1999/02/22-rdf-syntax-ns#
>>> <http://www.w3.org/1999/02/22-rdf-syntax-ns> >
>>>   7 PREFIX  skos: <http://www.w3.org/2004/02/skos/core#
>>> <http://www.w3.org/2004/02/skos/core> >
>>>   8 PREFIX  dcterms: <http://purl.org/dc/terms/>
>>>   9 
>>>  10 CONSTRUCT 
>>>  11   { ?ass mmx:relatedArchiveDocument
>>> <http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .
>>> 12     ?ass rdf:type mmx:Asset .
>>> 13     ?ass dcterms:hasVersion ?ver .
>>> 14     ?ver ?pred2 ?obj2 .
>>> 15     ?ass ?p2 ?o2 .}
>>> 16 WHERE
>>> 17   {   { GRAPH ?g
>>> 18           { ?ass mmx:relatedArchiveDocument
>>> <http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .
>>> 19             ?ass dcterms:hasVersion ?ver .
>>> 20             ?ver ?pred2 ?obj2
>>> 21           }
>>> 22       }
>>> 23     UNION
>>> 24       { GRAPH ?g
>>> 25           { ?ass mmx:relatedArchiveDocument
>>> <http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .
>>> 26             ?ass ?p2 ?o2
>>> 27           }
>>> 28       }
>>> 29   }
>>>  
>>> Thought I¹d exclude the setup and query as, as mentioned, the query does
>>> work (and did, only recently started throwing the exception ­ hence I
>>> wondered if it was data, or maybe encoding, related based on how dotnetRDF
>>> is parsingŠ).
>>> 
>>> The attached triples were the result of the construct from above, not the
>>> entire triple store.
>>>  
>>> This all works fine for small result sets, it¹s just this particular query
>>> returns 360 relatedArchiveDocument¹s and the library doesn¹t seem to like
>>> it.
>>>  
>>> If it¹s nothing obvious, I will grab your source code and try and debug
>>> further ­ can¹t tell much of what is happening within QueryWithResultGraph()
>>> atm.
>>>  
>>> /Rob
>>>  
>>>  
>>> 
>>> From: Rob Vesse [mailto:rv...@do...]
>>> Sent: 30 January 2014 17:12
>>> To: dotNetRDF Developer Discussion and Feature Request
>>> Cc: ro...@co...
>>> Subject: Re: [dotNetRDF-Develop] Stackoverflow calling
>>> QueryWithResultGraph()
>>>  
>>> 
>>> Rob
>>> 
>>>  
>>> 
>>> You didn't include the query or any context of how you invoke the query so
>>> we can't really offer any attempt at diagnosis.  Please provide a minimal
>>> complete example.
>>> 
>>>  
>>> 
>>> Are the results you provided the results of a successful run of the specific
>>> query or a dump of the entire test dataset?  Nothing looks untoward with the
>>> data so likely some interaction with the specific query.
>>> 
>>>  
>>> 
>>> QueryWithResultGraph() implies use of SparqlRemoteEndpoint (whether
>>> directly/indirectly) to query a remote service so can you provide the code
>>> that invokes the query plus the specific problematic query.  The only kind
>>> of query that springs to mind that could easily lead to a StackOverflow
>>> would be a complex property path but without seeing the query I can't tell,
>>> it may well be something innocuous hitting a rare corner case in our SPARQL
>>> engine.
>>> 
>>>  
>>> 
>>> Also what can you tell us about the set up of that remote service since you
>>> imply you control that as well.  Is the remote server using dotNetRDF to
>>> host the data, if so what's the setup?
>>> 
>>>  
>>> 
>>> Or if it isn't under your control can you tell us anything about it e.g.
>>> endpoint, server software if known etc
>>> 
>>>  
>>> 
>>> Thanks,
>>> 
>>>  
>>> 
>>> Rob Vesse
>>> 
>>>  
>>> 
>>> From: Rob Nicholls <ro...@co...>
>>> Reply-To: dotNetRDF Developer Discussion and Feature Request
>>> <dot...@li...>
>>> Date: Thursday, 30 January 2014 05:44
>>> To: <dot...@li...>
>>> Subject: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()
>>> 
>>>  
>>>> 
>>>> Hi all,
>>>>  
>>>> I¹m receiving consistent stack overflows from QueryWithResultGraph(query)
>>>> when using a specific query against our triple store. The query runs fine
>>>> (within ms) and returns results ok.
>>>>  
>>>> Results returned from the triple store are in the attached file
>>>> (queryresults.txt), not a huge amount of data to justify killing a 12GB web
>>>> server, and it does occasionally function correctly on my developer machine
>>>> (never when running the debugger though).
>>>>  
>>>> Can anyone offer any advice?
>>>> Is this perhaps an issue with the data itself causing some kind of circular
>>>> reference? Although doesn¹t explain why it occasionally works.
>>>>  
>>>> Using: 
>>>> dotnetRdf 1.0.3 / .NET4.5
>>>>  
>>>> Many thanks,
>>>> Rob
>>>>  
>>>> cogapp
>>>>  
>>>>  
>>>> Rob Nicholls
>>>> Senior Programmer
>>>> +44 1273 821600
>>>> www.cogapp.com <http://www.cogapp.com/>
>>>>  
>>>> Cogapp Brighton
>>>> 21-33 Dyke Road, Brighton, BN1 3FE. UK
>>>>  
>>>> Cogapp New York
>>>> 641 Lexington Avenue, 15th Floor, New York, NY 10022, USA
>>>>  
>>>> News 
>>>> Pocahontas' portrait and letters from George Washington online: a
>>>> responsive website for the Virginia Historical Society
>>>> <http://www.vahistorical.org/> , just launched.
>>>> 
>>>> For regular Cogapp news, please follow us on Twitter
>>>> <https://twitter.com/cogapp> .
>>>>  
>>>> ---------------------------------------------------------------------------
>>>> --- WatchGuard Dimension instantly turns raw network data into actionable
>>>> security intelligence. It gives you real-time visual feedback on key
>>>> security issues and trends. Skip the complicated setup - simply import a
>>>> virtual appliance and go from zero to informed in seconds.
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktr
>>>> k_______________________________________________ dotNetRDF-develop mailing
>>>> list dot...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications Take advantage of what
> the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk__
> _____________________________________________ dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

Re: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()

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

Thanks for the additional information, the RDF/XML is perfectly valid as you
noted.

That error is not really more descriptive, turning on the HTTP Full
Debugging consumes the response stream so the calling code then has an
already closed stream which causes different errors depending on the calling
code.  I've changed this behaviour in our default branch so that it'll now
throw an error informing you that the response stream was consumed and not
available to calling code.

The RDF/XML parser code does recurse heavily so I'm wondering if this file
is just under the stack limit when parsed in the rdfEditor but when called
via the SparqlRemoteEndpoint which itself has several levels of recursion
tips it over the edge.  I'm going to take the data you provided and debug
this further and will get back to you when I know more

Rob

From:  Rob Nicholls <ro...@co...>
Date:  Monday, 3 February 2014 13:46
To:  Rob Vesse <rv...@do...>
Cc:  'dotNetRDF Developer Discussion and Feature Request'
<dot...@li...>
Subject:  RE: [dotNetRDF-Develop] Stackoverflow calling
QueryWithResultGraph()

> Ahh, missed that. Thanks.
>  
> Ok, now throwing a more descriptive error; XML parser, root element is
> missing.
>  
> Output attached.
>  
> I¹ve checked the RDF with your RDFeditor validator, no problems.
>  
> Is it feasibly a memory issue, based on the size of the RDF/XML? (I¹ve
> stripped the code right back to a simple console app using dotNetRDF ­ same
> result) Or maybe I¹m missing something obvious?
>  
> /Rob
>  
> 
> From: Rob Vesse [mailto:rv...@do...]
> Sent: 30 January 2014 19:16
> To: Rob Nicholls
> Cc: dotNetRDF Developer Discussion and Feature Request
> Subject: Re: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()
>  
> 
> Ok, that's useful information.  Specific version of Fuseki should not be an
> issue since I don't see anything in the query that would trigger any known
> bugs in Fuseki/TDB/ARQ
> 
>  
> 
> Would be interesting to see what format Fuseki is returning the data in when
> called from dotNetRDF.  Could you run the query with HTTP Debugging turned on
> as detailed at [1] and provide the HTTP traces this produces to the console?
> 
>  
> 
> The full HTTP trace could be particularly useful in determining if there is
> something in the data serialisation of the results of this query that triggers
> a SO in one of the dotNetRDF parsers.
> 
>  
> 
> Thanks,
> 
>  
> 
> Rob
> 
>  
> 
> [1]: 
> https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/HowTo/Debug%20HTTP%20Communicat
> ion.wiki#!debugging-http-communication
> 
>  
> 
>  
> 
> From: Rob Nicholls <ro...@co...>
> Date: Thursday, 30 January 2014 10:26
> To: Rob Vesse <rv...@do...>, 'dotNetRDF Developer Discussion and
> Feature Request' <dot...@li...>
> Subject: RE: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()
> 
>  
>> 
>> dotnetRDF library to query (via .NET4.5 build)
>> Jena Fuseki for the Triple Store and Endpoint (I forget specific versions,
>> but will check if helpful)
>> mmx is our Dataset
>>  
>> Calling code is basically (omitted the noise):
>>  
>> _endpoint = new SparqlRemoteEndpoint(³http://jena:3030/mmx/query²);
>> IGraph graph = _endpoint.QueryWithResultGraph(thequery); // ß Stackoverflow
>> here
>>  
>> Where thequery is:
>>  
>> 
>>   1 PREFIX  dc:   <http://purl.org/dc/elements/1.1/>
>>   2 PREFIX  exif: <http://www.w3.org/2003/12/exif/ns/>
>>   3 PREFIX  rdfs: <http://www.w3.org/2000/01/rdf-schema#
>> <http://www.w3.org/2000/01/rdf-schema> >
>>   4 PREFIX  mmx:  <http://data.sciencemuseum.org.uk/def/ontology/>
>>   5 PREFIX  foaf: <http://xmlns.com/foaf/0.1/>
>>   6 PREFIX  rdf:  <http://www.w3.org/1999/02/22-rdf-syntax-ns#
>> <http://www.w3.org/1999/02/22-rdf-syntax-ns> >
>>   7 PREFIX  skos: <http://www.w3.org/2004/02/skos/core#
>> <http://www.w3.org/2004/02/skos/core> >
>>   8 PREFIX  dcterms: <http://purl.org/dc/terms/>
>>   9 
>>  10 CONSTRUCT 
>>  11   { ?ass mmx:relatedArchiveDocument
>> <http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .
>> 12     ?ass rdf:type mmx:Asset .
>> 13     ?ass dcterms:hasVersion ?ver .
>> 14     ?ver ?pred2 ?obj2 .
>> 15     ?ass ?p2 ?o2 .}
>> 16 WHERE
>> 17   {   { GRAPH ?g
>> 18           { ?ass mmx:relatedArchiveDocument
>> <http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .
>> 19             ?ass dcterms:hasVersion ?ver .
>> 20             ?ver ?pred2 ?obj2
>> 21           }
>> 22       }
>> 23     UNION
>> 24       { GRAPH ?g
>> 25           { ?ass mmx:relatedArchiveDocument
>> <http://id.sciencemuseum.org.uk/archivedocument/smad-110001337> .
>> 26             ?ass ?p2 ?o2
>> 27           }
>> 28       }
>> 29   }
>>  
>> Thought I¹d exclude the setup and query as, as mentioned, the query does work
>> (and did, only recently started throwing the exception ­ hence I wondered if
>> it was data, or maybe encoding, related based on how dotnetRDF is parsingŠ).
>> 
>> The attached triples were the result of the construct from above, not the
>> entire triple store.
>>  
>> This all works fine for small result sets, it¹s just this particular query
>> returns 360 relatedArchiveDocument¹s and the library doesn¹t seem to like it.
>>  
>> If it¹s nothing obvious, I will grab your source code and try and debug
>> further ­ can¹t tell much of what is happening within QueryWithResultGraph()
>> atm.
>>  
>> /Rob
>>  
>>  
>> 
>> From: Rob Vesse [mailto:rv...@do...]
>> Sent: 30 January 2014 17:12
>> To: dotNetRDF Developer Discussion and Feature Request
>> Cc: ro...@co...
>> Subject: Re: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()
>>  
>> 
>> Rob
>> 
>>  
>> 
>> You didn't include the query or any context of how you invoke the query so we
>> can't really offer any attempt at diagnosis.  Please provide a minimal
>> complete example.
>> 
>>  
>> 
>> Are the results you provided the results of a successful run of the specific
>> query or a dump of the entire test dataset?  Nothing looks untoward with the
>> data so likely some interaction with the specific query.
>> 
>>  
>> 
>> QueryWithResultGraph() implies use of SparqlRemoteEndpoint (whether
>> directly/indirectly) to query a remote service so can you provide the code
>> that invokes the query plus the specific problematic query.  The only kind of
>> query that springs to mind that could easily lead to a StackOverflow would be
>> a complex property path but without seeing the query I can't tell, it may
>> well be something innocuous hitting a rare corner case in our SPARQL engine.
>> 
>>  
>> 
>> Also what can you tell us about the set up of that remote service since you
>> imply you control that as well.  Is the remote server using dotNetRDF to host
>> the data, if so what's the setup?
>> 
>>  
>> 
>> Or if it isn't under your control can you tell us anything about it e.g.
>> endpoint, server software if known etc
>> 
>>  
>> 
>> Thanks,
>> 
>>  
>> 
>> Rob Vesse
>> 
>>  
>> 
>> From: Rob Nicholls <ro...@co...>
>> Reply-To: dotNetRDF Developer Discussion and Feature Request
>> <dot...@li...>
>> Date: Thursday, 30 January 2014 05:44
>> To: <dot...@li...>
>> Subject: [dotNetRDF-Develop] Stackoverflow calling QueryWithResultGraph()
>> 
>>  
>>> 
>>> Hi all,
>>>  
>>> I¹m receiving consistent stack overflows from QueryWithResultGraph(query)
>>> when using a specific query against our triple store. The query runs fine
>>> (within ms) and returns results ok.
>>>  
>>> Results returned from the triple store are in the attached file
>>> (queryresults.txt), not a huge amount of data to justify killing a 12GB web
>>> server, and it does occasionally function correctly on my developer machine
>>> (never when running the debugger though).
>>>  
>>> Can anyone offer any advice?
>>> Is this perhaps an issue with the data itself causing some kind of circular
>>> reference? Although doesn¹t explain why it occasionally works.
>>>  
>>> Using: 
>>> dotnetRdf 1.0.3 / .NET4.5
>>>  
>>> Many thanks,
>>> Rob
>>>  
>>> cogapp
>>>  
>>>  
>>> Rob Nicholls
>>> Senior Programmer
>>> +44 1273 821600
>>> www.cogapp.com <http://www.cogapp.com/>
>>>  
>>> Cogapp Brighton
>>> 21-33 Dyke Road, Brighton, BN1 3FE. UK
>>>  
>>> Cogapp New York
>>> 641 Lexington Avenue, 15th Floor, New York, NY 10022, USA
>>>  
>>> News 
>>> Pocahontas' portrait and letters from George Washington online: a responsive
>>> website for the Virginia Historical Society <http://www.vahistorical.org/> ,
>>> just launched.
>>> 
>>> For regular Cogapp news, please follow us on Twitter
>>> <https://twitter.com/cogapp> .
>>>  
>>> ----------------------------------------------------------------------------
>>> -- WatchGuard Dimension instantly turns raw network data into actionable
>>> security intelligence. It gives you real-time visual feedback on key
>>> security issues and trends. Skip the complicated setup - simply import a
>>> virtual appliance and go from zero to informed in seconds.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
>>> _______________________________________________ dotNetRDF-develop mailing
>>> list dot...@li...
>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

[dotNetRDF-Develop] Issue CORE-398 has been updated by Rob Vesse

[<tr...@do...>]

<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Unexpected SPARQL query result for MINUS inside UNION and specifying named graph</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Status changed from "Confirmed" to "Completed"
                                </li>
        <li>Resolution changed from "Unassigned" to "Fixed"
                                </li>
        <li>Progress changed from "30 %" to "100 %"
                                </li>
      </ul>
    </td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=398" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=398</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>

[dotNetRDF-Develop] Issue CORE-398 has a new comment

[<tr...@do...>]

<p>A new comment has been added to the following issue.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Unexpected SPARQL query result for MINUS inside UNION and specifying named graph</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td><b>Created By:</b></td>
    <td>Rob Vesse</td>
  </tr>
  <tr>
    <td><b>Date:</b></td>
    <td>2014-02-06 10:47 AM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Fixed the other cases where this might occur and added unit tests to cover these cases, this problem should not be resolved</p></td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=398" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=398</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>

[dotNetRDF-Develop] Issue VIRT-399 has been added to a project you are monitoring.

[<tr...@do...>]

<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Recent Virtuoso releases are missing the bif:rdf_make_iid_of_qname() function</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll)</td>
  </tr>
  <tr>
    <td><b>Created By:</b></td>
    <td>Rob Vesse</td>
  </tr>
  <tr>
    <td><b>Milestone:</b></td>
    <td>Unassigned</td>
  </tr>
  <tr>
    <td><b>Category:</b></td>
    <td>Virtuoso Support</td>
  </tr>
  <tr>
    <td><b>Priority:</b></td>
    <td>Critical</td>
  </tr>
  <tr>
    <td><b>Type:</b></td>
    <td>Bug</td>
  </tr>
  <tr>
    <td><b>Description:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	In fixing VIRT-397 I discovered a bug in recent Virtuoso releases that is missing a key internal function we use to delete blank nodes by Virtuoso identifier. &nbsp;This means that currently if you use the Data.Virtuoso library with more recent Virtuoso releases you cannot delete blank nodes directly and can only delete them indirectly by other means e.g. deleting the entire graph</p>
<p>
	&nbsp;</p>
<p>
	Reported to the Virtuoso folks and awaiting a response</p></td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=399" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=399</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>