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> |