Menu
▾
▴
dotnetrdf-develop — Developer Discussion and Feature Request
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
(11) |
Mar
(17) |
Apr
(12) |
May
(2) |
Jun
(20) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(5) |
| 2011 |
Jan
(4) |
Feb
(1) |
Mar
(2) |
Apr
(2) |
May
(5) |
Jun
|
Jul
(12) |
Aug
(4) |
Sep
(5) |
Oct
(1) |
Nov
(38) |
Dec
(27) |
| 2012 |
Jan
(46) |
Feb
(182) |
Mar
(83) |
Apr
(22) |
May
(68) |
Jun
(47) |
Jul
(135) |
Aug
(84) |
Sep
(57) |
Oct
(45) |
Nov
(27) |
Dec
(61) |
| 2013 |
Jan
(59) |
Feb
(78) |
Mar
(66) |
Apr
(107) |
May
(27) |
Jun
(56) |
Jul
(53) |
Aug
(3) |
Sep
(19) |
Oct
(41) |
Nov
(44) |
Dec
(54) |
| 2014 |
Jan
(49) |
Feb
(72) |
Mar
(22) |
Apr
(41) |
May
(63) |
Jun
(27) |
Jul
(45) |
Aug
(12) |
Sep
(3) |
Oct
(8) |
Nov
(27) |
Dec
(16) |
| 2015 |
Jan
(3) |
Feb
(20) |
Mar
(6) |
Apr
(4) |
May
(15) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(16) |
May
(9) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <tr...@do...> - 2013-12-05 22:34:25
|
<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>Store Manager unable to return results when non-printable characters are part of result</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>2013-12-05 10:31 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Btw I notice you mention that you run the query against a server containing the DrugBank information, this implies that you aren't running against the public endpoint rather the data hosted in your own system. If this is the case it would be useful to know what system you are using.</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=385" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=385</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>
|
|
From: <tr...@do...> - 2013-12-05 14:15:48
|
<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>Status changed from "Planned" to "In Progress"
</li>
<li>Assigned to changed from "Unassigned" to "Kal"
</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>
|
|
From: <tr...@do...> - 2013-12-05 14:14:12
|
<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>2013-12-05 02:10 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Kal has started some work on this, need to review what he's done so far to see that it's equivalent to the existing installer and decide what (if anything) else needs adding to the installer</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>
|
|
From: <tr...@do...> - 2013-12-01 11:37:08
|
<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>Inconsistent GraphUri in SparqlResultSet</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>Priority changed from "Normal" to "Low"
</li>
<li>Status changed from "Unassigned" to "Closed"
</li>
<li>Resolution changed from "Unassigned" to "Won't Fix"
</li>
<li>Assigned to changed from "Unassigned" to "Rob Vesse"
</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=388" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=388</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>
|
|
From: <tr...@do...> - 2013-12-01 11:35:58
|
<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>Inconsistent GraphUri in SparqlResultSet</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>2013-12-01 11:33 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
It's probably not the expected behaviour so this is a Won't Fix Having a BaseUri property on IGraph and corresponding Graph and GraphUri properties on INode have proven over the years to be poor design decisions which necessitate all sorts of messy hacks around the codebase particularly in SPARQL and especially when blank nodes are involved. The intent is ultimately to remove these things entirely and get rid of much of the awkwardness they entail.</p>
<p>
The behaviour wrt to SPARQL is not something that was ever intended nor specifically designed for and should not be relied upon as a way to determine which graph a bound value originated from. The only reliable way to do that is to use SPARQL itself and use GRAPH ?g clauses.</p>
<p>
</p>
<p>
Looking at your queries the specific problem is that the filtered query results in the optimizer substituing the constant for ?s and then using BIND to make sure the variable remains exposed outside of that portion of the query. BIND (and project expresisons in general) are almost certainly guaranteed to not preserve the GraphUri.</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=388" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=388</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>
|
|
From: <tr...@do...> - 2013-12-01 11:28:38
|
<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>Clarify that the BaseEndpoint.Timeout attribute is in milliseconds</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 "Unassigned" to "Confirmed"
</li>
<li>Milestone changed from "Unassigned" to "1.0.3"
</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=387" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=387</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>
|
|
From: <tr...@do...> - 2013-12-01 11:28:29
|
<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>Clarify that the BaseEndpoint.Timeout attribute is in milliseconds</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>2013-12-01 11:25 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Patches or pull requests are always welcome</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=387" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=387</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>
|
|
From: <tr...@do...> - 2013-11-29 19:29:46
|
<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>Inconsistent GraphUri in SparqlResultSet</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>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Normal</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I understand that one cannot expect the INode.GraphUri attribute to always be populated in SparqlResultSet (eg. queries on a SPARQL endpoint).</p>
<p>
However the attribute seems to be inconsistantly populated as it populated when both:</p>
<ol>
<li>
BaseUri is set before loading data into a graph</li>
<li>
SPARQL query does not contain a FILTER clause</li>
</ol>
<p>
I am not sure if this behavior is expected or not ?</p>
<p>
Unit tests attached.</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=388" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=388</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>
|
|
From: <tr...@do...> - 2013-11-28 16:28:45
|
<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>Clarify that the BaseEndpoint.Timeout attribute is in milliseconds</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>Core API</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Low</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
The documentation of the BaseEndpoint.Timeout attribute mentions that the default timeout is 30 seconds, but the unit is actually milliseconds and no unit is specified in the documentation.</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=387" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=387</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>
|
|
From: <tr...@do...> - 2013-11-27 16:50:46
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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>Date:</b></td>
<td>2013-11-27 04:48 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Thanks for the quick fix and your overall great work on dotNetRDF!</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-27 16:32:58
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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>2013-11-27 04:30 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
This is now fixed, thanks for reporting this and bearing with me while I figured out what was wrong</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-27 16:32:34
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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 "90 %" 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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-27 16:18:51
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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>2013-11-27 04:16 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I can now confirm that this is indeed a bug in dotNetRDF's implementation of OPTIONAL but it only affects cases where there is a cross product. As I suggested before the fix is pretty trivial and once I've run regression tests to make sure this doesn't break any other tests which are inadvertently relying on the incorrect behaviour I'll push up the fix for this.</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-27 16:17:12
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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 "New" to "Confirmed"
</li>
<li>Progress changed from "100 %" to "90 %"
</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-27 11:10:05
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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 "Closed" to "New"
</li>
<li>Resolution changed from "Invalid" to "-- Select Resolution --"
</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-27 11:09:41
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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>2013-11-27 11:06 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I have requested clarifiaction from Andy Seaborne on which interpretation is right, I understand now where dotNetRDF and ARQ differ and it should be relatively easy to fix if this is indeed a dotNetRDF bug.</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-27 10:25:09
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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>2013-11-27 10:22 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Reopening as there does appear to be some issue here, having ported the test cases to Jena I can confirm that the original query does work in Jena. Until I can confirm with Andy if this is the expected behaviour and not a bug in Jena I'll leave this bug open.</p>
<p>
</p>
<p>
Btw yes you are correct that the inverted query is not valid for all cases.</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-26 20:27:46
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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>Date:</b></td>
<td>2013-11-26 08:25 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
By the way, I am not sure that your simplified query is equivalent. For example when adding the triple (r1, r1, r2) to g0, your first query does not return it while your second query does.</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-26 16:01:07
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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>Date:</b></td>
<td>2013-11-26 03:58 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Hi Rob,</p>
<p>
Thank you very much for the insight, it makes sense.</p>
<p>
Before opening this issue, I checked with 2 other SPARQL implementations including Jena ARQ 2.11.0 and I got a different behavior than with dotNetRDF.</p>
<p>
As you are also a Jena commiter, would it be possible for you to reproduce what I got using Jena ? I could then open an issue there if the behavior is indeed different.</p>
<p>
We could follow up by email and I could send you the Jena unit test if you are interested, as this is not directly related to dotNetRDF development.</p>
<p>
Thanks,</p>
<p>
Alexandre</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-26 10:01:46
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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 "New" to "Closed"
</li>
<li>Milestone changed from "Unassigned" to "1.0.3"
</li>
<li>Resolution changed from "Unassigned" to "Invalid"
</li>
<li>Assigned to changed from "Unassigned" to "Rob Vesse"
</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-26 10:00:54
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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>2013-11-26 09:58 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I have incorporated the unit tests with the corrected queries into our unit tests and have also added a NOT EXISTS based variant to the tests as well. I'll go ahead and close this issue as invalid.</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-26 09:49:23
|
<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 results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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>2013-11-26 09:46 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
The behaviour is entirely correct, the problem is that your OPTIONAL query is not appropriately formulated.</p>
<p>
By using different variables inside the OPTIONAL you get a cross product like so (before FILTERING):</p>
<p>
1 => ?s = r1, ?p = r1, ?o = r1, ?s0 = r1, ?p0 = r1, ?o0 = r1</p>
<p>
2 => ?s = r1, ?p = r1, ?o = r1, ?s0 = r2, ?p0 = r2, ?o0 = r2</p>
<p>
3 => ?s = r2, ?p = r2, ?o = r2, ?s0 = r1, ?p0 = r1, ?o0 = r1</p>
<p>
4 => ?s = r2, ?p = r2, ?o = r2, ?s0 = r2, ?p0 = r2, ?o0 = r2</p>
<p>
The FILTER inside the OPTIONAL applies over this cross product but because it is an OPTIONAL solutions that fail the filter still maintain the LHS components so after FILTERing you get the following:</p>
<p>
1 => ?s = r1, ?p = r1, ?o = r1</p>
<p>
2 => ?s = r1, ?p = r1, ?o = r1, ?s0 = r2, ?p0 = r2, ?o0 = r2</p>
<p>
3 => ?s = r2, ?p = r2, ?o = r2, ?s0 = r1, ?p0 = r1, ?o0 = r1</p>
<p>
4 => ?s = r2, ?p = r2, ?o = r2</p>
<p>
And then your FILTER(!BOUND(?s0)) eliminates rows 2 and 3 still leaving you with rows 1 and 4. So what you want to do here is to avoid the cross product by having at least one common variable, in fact you only need to leave one variable different to still have the additional variable to test !BOUND() on like so:</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
SELECT *</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
WHERE</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
{</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
GRAPH <http://g1></p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
{</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
?s ?p ?o .</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
}</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
OPTIONAL</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
{</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
GRAPH <http://g0> { ?s ?p ?o0 . }</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
FILTER (SAMETERM(?o, ?o0))</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
}</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
FILTER(!BOUND(?o0))</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
}</p>
<div>
</div>
<p>
By the way you can simplify even further by inverting the SAMETERM and moving it outside the OPTIONAL instead of using !BOUND like so:</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
SELECT *</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
WHERE</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
{</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
GRAPH <http://g1></p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
{</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
?s ?p ?o .</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
}</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
OPTIONAL</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
{</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
GRAPH <http://g0> { ?s ?p ?o0 . }</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
}</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
FILTER (!SAMETERM(?o, ?o0))</p>
<p style="margin: 0px; font-size: 9.5px; font-family: Consolas; color: rgb(180, 38, 26);">
}</p>
<div>
</div>
<p>
Hope this helps</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <tr...@do...> - 2013-11-25 22:02:10
|
<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>Unexpected SPARQL results with the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" query pattern</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>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Hi,</p>
<p>
I think I found a bug related to the SPARQL query engine but I am not 100% sure.</p>
<p>
I am computing the delta between two graphs in memory (TripleStore class) using a SPARQL query.</p>
<ul>
<li>
When using the MINUS operator, it works as expected.</li>
<li>
When using the "OPTIONAL { ... FILTER (sameTerm) } FILTER (!bound)" pattern, I get unexpected results under some circumstances I have not pinpointed yet</li>
</ul>
<p>
Please see the attached unit test. Note that:</p>
<ul>
<li>
Expected results are obtained when removing one of the two triples from the Turtle data string.</li>
<li>
Expected results are obtained when asserting triples instead of parsing them (as far as I tried).</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=386" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=386</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>
|
|
From: <dot...@li...> - 2013-11-23 16:04:38
|
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: 3 new changesets (Bitbucket) 2. commit/dotnetrdf: 5 new changesets (Bitbucket) 3. commit/dotnetrdf: rvesse: Prepare for 1.0.3 dev cycle (Bitbucket) 4. commit/dotnetrdf: 4 new changesets (Bitbucket) 5. commit/dotnetrdf: rvesse: Test to demonstrate that certain characters in URIs are preserved internally (Bitbucket) 6. commit/dotnetrdf: rvesse: More tests for Sesame and AllegroGraph to try and pin down a possible reported bug, not reproduced but did fix another bug that the new tests highlighted (Bitbucket) 7. commit/dotnetrdf: 2 new changesets (Bitbucket) 8. commit/dotnetrdf: 3 new changesets (Bitbucket) 9. commit/dotnetrdf: 3 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Thu, 14 Nov 2013 14:16:25 -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/7570381ebb1a/ Changeset: 7570381ebb1a User: rvesse Date: 2013-11-14 14:41:55 Summary: Final 1.0.2 release preparation Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/838619144d6c/ Changeset: 838619144d6c User: rvesse Date: 2013-11-14 15:15:43 Summary: Added tag 1.0.2 for changeset 7570381ebb1a Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ef99f7e228ca/ Changeset: ef99f7e228ca User: rvesse Date: 2013-11-14 15:15:51 Summary: Added tag 102 for changeset 7570381ebb1a 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: 2 Date: Thu, 14 Nov 2013 17:15:51 -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/a2ba21f82338/ Changeset: a2ba21f82338 Branch: 1.9 User: rvesse Date: 2013-11-14 16:48:53 Summary: Merge 1.0.2 release from default Affected #: 56 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c533b6ff4028/ Changeset: c533b6ff4028 Branch: 1.9 User: rvesse Date: 2013-11-14 16:58:26 Summary: Almost got the obvious errors in IO Core resolved Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d0ede21ea986/ Changeset: d0ede21ea986 Branch: 1.9 User: rvesse Date: 2013-11-14 17:35:11 Summary: More refactoring in IO Core to get it closer to a buildable state Affected #: 20 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3e3454ca732e/ Changeset: 3e3454ca732e Branch: 1.9 User: rvesse Date: 2013-11-14 17:50:17 Summary: Got through the initial glut of IO Core errors, now triggered another glut Affected #: 22 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/337f1741fad2/ Changeset: 337f1741fad2 Branch: 1.9 User: rvesse Date: 2013-11-14 18:15:01 Summary: Start working my way through the new glut of IO Core errors Affected #: 23 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: 3 Date: Thu, 21 Nov 2013 14:00:00 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Prepare for 1.0.3 dev cycle 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/5c74717a817e/ Changeset: 5c74717a817e User: rvesse Date: 2013-11-21 14:59:42 Summary: Prepare for 1.0.3 dev cycle Affected #: 36 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: Thu, 21 Nov 2013 14:07:52 -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/1d36e0b138e2/ Changeset: 1d36e0b138e2 Branch: CORE-383 User: rvesse Date: 2013-11-21 15:04:20 Summary: Apply Austin Barton's patch for creating populated SparqlResultSet instances (CORE-383) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c3e3ef96f882/ Changeset: c3e3ef96f882 Branch: CORE-383 User: rvesse Date: 2013-11-21 15:05:59 Summary: Close CORE-383 branch now patch is applied Affected #: 0 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9cd0c5e335c5/ Changeset: 9cd0c5e335c5 User: rvesse Date: 2013-11-21 15:06:17 Summary: Merge CORE-383 fixes into default Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ce3206c16740/ Changeset: ce3206c16740 User: rvesse Date: 2013-11-21 15:07:11 Summary: Note CORE-383 patch in Change Log 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: 5 Date: Fri, 22 Nov 2013 13:41:25 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Test to demonstrate that certain characters in URIs are preserved internally 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/432352d29eb5/ Changeset: 432352d29eb5 User: rvesse Date: 2013-11-22 14:41:08 Summary: Test to demonstrate that certain characters in URIs are preserved internally 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: 6 Date: Fri, 22 Nov 2013 14:35:07 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: More tests for Sesame and AllegroGraph to try and pin down a possible reported bug, not reproduced but did fix another bug that the new tests highlighted 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/0e1089aa1910/ Changeset: 0e1089aa1910 User: rvesse Date: 2013-11-22 15:34:51 Summary: More tests for Sesame and AllegroGraph to try and pin down a possible reported bug, not reproduced but did fix another bug that the new tests highlighted Affected #: 4 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: Fri, 22 Nov 2013 14:58: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/8fc15b078bae/ Changeset: 8fc15b078bae Branch: 1.9 User: rvesse Date: 2013-11-22 15:55:55 Summary: Get most profiles of the Core library to build, some work required to get Silverlight based builds to work Affected #: 22 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4466f1c74096/ Changeset: 4466f1c74096 Branch: 1.9 User: rvesse Date: 2013-11-22 15:58:40 Summary: Get Silverlight based Core library profiles to build 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: 8 Date: Fri, 22 Nov 2013 16:17:14 -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/e9ac2b56f255/ Changeset: e9ac2b56f255 Branch: 1.9 User: rvesse Date: 2013-11-22 16:42:48 Summary: More progress on getting the IO Core buildable Affected #: 22 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b3f954ae787a/ Changeset: b3f954ae787a Branch: 1.9 User: rvesse Date: 2013-11-22 16:52:45 Summary: Fix a bunch more obvious errors in IO Core Affected #: 16 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/562cff08e130/ Changeset: 562cff08e130 Branch: 1.9 User: rvesse Date: 2013-11-22 17:16:55 Summary: Yet more work on getting IO Core towards buildable 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: Sat, 23 Nov 2013 16:04:28 -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/381ae631bac7/ Changeset: 381ae631bac7 Branch: 1.9 User: rvesse Date: 2013-11-23 15:54:48 Summary: Down to under 100 errors in IO Core Affected #: 11 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b8bb563ed5df/ Changeset: b8bb563ed5df Branch: 1.9 User: rvesse Date: 2013-11-23 16:57:56 Summary: Get IO Core buildable and GraphBenchmarker buildable Affected #: 35 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5f01bb009735/ Changeset: 5f01bb009735 Branch: 1.9 User: rvesse Date: 2013-11-23 17:04:10 Summary: Minor bug fix to IO Core 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. ------------------------------ ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 13, Issue 2 ************************************************ |
|
From: <tr...@do...> - 2013-11-21 14:08:59
|
<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>Allow direct creation of populated SparqlResultSet instances</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>2013-11-21 02:06 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Patch applied</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=383" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=383</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>
|
48 messages has been excluded from this view by a project administrator.
