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-09-17 22:42:26
|
<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>SparqlRemoteEndpoint async methods don't propagate errors correctly</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 "In Progress" to "Completed"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</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=370" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370</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-09-17 22:42:14
|
<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>SparqlRemoteEndpoint async methods don't propagate errors correctly</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-09-17 11:41 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Have done this for all other APIs, the error propagation mechanism is not great for some of these right now (we pass the exception back as a wrapped object in the state parameter of the callback so that we still provide the original state information</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=370" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=370</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-09-17 22:24:01
|
<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>VirtuosoManager.ListGraphs() does not support some special Virtuoso URIs</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>1.0.1</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Virtuoso Support</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>
The VirtuosoManager implementation of ListGraphs() does not always function correctly because Virtuoso uses some weird graph URIs which dotNetRDF either discards silently or rejects as an error. The VirtuosoManager code should marshal these into a form that dotNetRDF can work with and unmarshal whatever wrappering we use back into Virtuoso form as necessary.</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=375" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=375</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-09-13 05:25:04
|
<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>Exception raised while parsing an UpdateCommand with FILTER EXISTS clause</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Max</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-09-13 06:05 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Hi Rob,</p>
<p>
No problem, I can in the meantime use a subsequent DELETE query that filters out the unwanted triples. It's not optimal but it still gives the intended result.</p>
<p>
And also good luck with your relocation ;)</p>
<p>
Max.</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=373" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=373</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-09-12 22:22:33
|
<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>Form URL Encoded POSTs should explicitly state UTF-8 charset where appropriate</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>Milestone:</b></td>
<td>1.0.1</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Storage</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>
Reported by Matthias Schwalbe on the bugs list - <a href="http://sourceforge.net/p/dotnetrdf/mailman/message/31394185/">http://sourceforge.net/p/dotnetrdf/mailman/message/31394185/</a></p>
<p>
When we POST form URL encoded content we are often posting UTF-8 content and the default character set for form URL encoded is ISO-8859-1 (Latin 1) which can cause encoding issues on the receiving end. Thus wherever appropriate code needs to explicitly state the character set for form URL encoded content in the Content-Type header.</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=374" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=374</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-09-12 22:17:37
|
<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>Exception raised while parsing an UpdateCommand with FILTER EXISTS clause</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-09-12 11:16 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Yes I will take a look at this and suspect it is not too hard to fix, I am in the middle or relocating countries (and contintents) this month so I likely won't have time to look at this properly until early October</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=373" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=373</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-09-10 14:29:58
|
<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>Exception raised while parsing an UpdateCommand with FILTER EXISTS clause</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Max</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>Unassigned</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 Rob,</p>
<p>
I'm trying to build an access-controlled TripleStore with DotNetRdf. So I try to dispatch an rdf input triples into different graphs using SPARQL Updates.</p>
<p>
When I use a (NOT?) EXISTS filter pattern like in the following query :</p>
<p>
PREFIX myschema: <http://www.example.com/schema#><br />
INSERT {<br />
GRAPH <data:public> {<br />
?s ?p ?o<br />
}<br />
} WHERE {<br />
GRAPH <input:source> {<br />
?s ?p ?o .<br />
} .<br />
FILTER( NOT EXISTS {<br />
{?p a myschema:PrivateProperty}<br />
UNION { ?s a myschema:PrivateResource }<br />
UNION { ?o a myschema:PrivateResource }<br />
})<br />
}<br />
</p>
<p>
I get an exception from the query parser and this stack trace :</p>
<p>
<strong>VDS.RDF.Parsing.RdfParseException: Unable to parse an EXISTS/NOT EXISTS as there is no Query Parser to call into</strong><br />
à VDS.RDF.Query.SparqlExpressionParser.TryParseBuiltInCall(Queue`1 tokens) dans D:\Projects\dotnetrdf\Libraries\core\net40\Query\SparqlExpressionParser.cs:ligne 803<br />
à VDS.RDF.Query.SparqlExpressionParser.TryParsePrimaryExpression(Queue`1 tokens) dans D:\Projects\dotnetrdf\Libraries\core\net40\Query\SparqlExpressionParser.cs:ligne 440<br />
à VDS.RDF.Query.SparqlExpressionParser.TryParseUnaryExpression(Queue`1 tokens) dans D:\Projects\dotnetrdf\Libraries\core\net40\Query\SparqlExpressionParser.cs:ligne 370<br />
à VDS.RDF.Query.SparqlExpressionParser.TryParseMultiplicativeExpression(Queue`1 tokens) dans D:\Projects\dotnetrdf\Libraries\core\net40\Query\SparqlExpressionParser.cs:ligne 330<br />
à VDS.RDF.Query.SparqlExpressionParser.TryParseAdditiveExpression(Queue`1 tokens) dans D:\Projects\dotnetrdf\Libraries\core\net40\Query\SparqlExpressionParser.cs:ligne 301<br />
à VDS.RDF.Query.SparqlExpressionParser.TryParseNumericExpression(Queue`1 tokens) dans D:\Projects\dotnetrdf\Libraries\core\net40\Query\SparqlExpressionParser.cs:ligne 295<br />
à VDS.RDF.Query.SparqlExpressionParser.TryParseRelationalExpression(Queue`1 tokens) dans D:\Projects\dotnetrdf\Libraries\core\net40\Query\SparqlExpressionParser.cs:ligne 255<br />
à VDS.RDF.Query.SparqlExpressionParser.TryParseValueLogical(Queue`1 tokens) dans D:\Projects\dotnetrdf\Libraries\core\net40\Query\SparqlExpressionParser.cs:ligne 249<br />
à VDS.RDF.Query.SparqlExpressionParser.TryParseConditionalAndExpression(Queue`1 tokens) dans D:\Projects\dotnetrdf\Libraries\core\net40\Query\SparqlExpressionParser.cs:ligne 224<br />
à VDS.RDF.Query.SparqlExpressionParser.TryParseConditionalOrExpression(Queue`1 tokens) dans D:\Projects\dotnetrdf\Libraries\core\net40\Query\SparqlExpressionParser.cs:ligne 200<br />
à VDS.RDF.Query.SparqlExpressionParser.Parse(Queue`1 tokens) dans D:\Projects\dotnetrdf\Libraries\core\net40\Query\SparqlExpressionParser.cs:ligne 188<br />
à VDS.RDF.Parsing.SparqlQueryParser.TryParseExpression(SparqlQueryParserContext context, Boolean commasTerminate, Boolean asTerminates) dans D:\Projects\dotnetrdf\Libraries\core\net40\Parsing\SparqlQueryParser.cs:ligne 2556<br />
à VDS.RDF.Parsing.SparqlQueryParser.TryParseExpression(SparqlQueryParserContext context, Boolean commasTerminate) dans D:\Projects\dotnetrdf\Libraries\core\net40\Parsing\SparqlQueryParser.cs:ligne 2500<br />
à VDS.RDF.Parsing.SparqlQueryParser.TryParseFilterExpression(SparqlQueryParserContext context, GraphPattern p) dans D:\Projects\dotnetrdf\Libraries\core\net40\Parsing\SparqlQueryParser.cs:ligne 2302<br />
à VDS.RDF.Parsing.SparqlQueryParser.TryParseFilterClause(SparqlQueryParserContext context, GraphPattern p) dans D:\Projects\dotnetrdf\Libraries\core\net40\Parsing\SparqlQueryParser.cs:ligne 2219<br />
à VDS.RDF.Parsing.SparqlQueryParser.TryParseTriplePatterns(SparqlQueryParserContext context, GraphPattern p) dans D:\Projects\dotnetrdf\Libraries\core\net40\Parsing\SparqlQueryParser.cs:ligne 1557<br />
à VDS.RDF.Parsing.SparqlQueryParser.TryParseTriplePatterns(SparqlQueryParserContext context, GraphPattern p) dans D:\Projects\dotnetrdf\Libraries\core\net40\Parsing\SparqlQueryParser.cs:ligne 1626<br />
à VDS.RDF.Parsing.SparqlQueryParser.TryParseGraphPattern(SparqlQueryParserContext context, Boolean requireOpeningLeftBracket) dans D:\Projects\dotnetrdf\Libraries\core\net40\Parsing\SparqlQueryParser.cs:ligne 1443<br />
à VDS.RDF.Parsing.SparqlUpdateParser.TryParseInsertCommand(SparqlUpdateParserContext context, Boolean allowData) dans D:\Projects\dotnetrdf\Libraries\core\net40\Parsing\SparqlUpdateParser.cs:ligne 717<br />
à VDS.RDF.Parsing.SparqlUpdateParser.ParseInternal(SparqlUpdateParserContext context) dans D:\Projects\dotnetrdf\Libraries\core\net40\Parsing\SparqlUpdateParser.cs:ligne 307<br />
à VDS.RDF.Parsing.SparqlUpdateParser.Parse(TextReader input) dans D:\Projects\dotnetrdf\Libraries\core\net40\Parsing\SparqlUpdateParser.cs:ligne 185<br />
à VDS.RDF.Parsing.SparqlUpdateParser.ParseFromString(String updates) dans D:\Projects\dotnetrdf\Libraries\core\net40\Parsing\SparqlUpdateParser.cs:ligne 221<br />
à VDS.RDF.TripleStore.ExecuteUpdate(String update) dans D:\Projects\dotnetrdf\Libraries\core\net40\Core\TripleStore.cs:ligne 530</p>
<p>
If I understand, the SparqlExpressionParser._exprParser instance that is used is not configured properly but I'm lost to why and how to correct this.</p>
<p>
Could you have a peek on this one, please ?</p>
<p>
Thanks in advance,<br />
Max.</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=373" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=373</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-08-19 19:39:09
|
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: tpluscode: break dependency on nuget targets so that they can be executed separately (Bitbucket) 3. commit/dotnetrdf: tpluscode: mark parsing speed explicit so it is completely omitted on build server (Bitbucket) 4. commit/dotnetrdf: tpluscode: again, testing HttpUtility should only be done for portable library (Bitbucket) 5. commit/dotnetrdf: tpluscode: remove old old broken url decode implementation (Bitbucket) 6. commit/dotnetrdf: rvesse: Properly align IsSafeCharacter() with RFC 3986 (Bitbucket) 7. commit/dotnetrdf: 4 new changesets (Bitbucket) 8. commit/dotnetrdf: 2 new changesets (Bitbucket) 9. commit/dotnetrdf: rvesse: Add base declaration to DOAP file (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Sun, 28 Jul 2013 18:16: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/ea5dcadb35ee/ Changeset: ea5dcadb35ee User: tpluscode Date: 2013-07-28 19:05:33 Summary: exlude a test which is pointless on non-portable build Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6f5ccb5c58a6/ Changeset: 6f5ccb5c58a6 User: tpluscode Date: 2013-07-28 19:09:57 Summary: many false negatives from resharper when potrable lib didn't reference System.* Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ac3ec0d1131e/ Changeset: ac3ec0d1131e User: tpluscode Date: 2013-07-28 20:14:32 Summary: refactored the UrlEncoding test 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: Sun, 28 Jul 2013 19:19:06 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: tpluscode: break dependency on nuget targets so that they can be executed separately 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/ecaa39cc4366/ Changeset: ecaa39cc4366 User: tpluscode Date: 2013-07-28 21:17:53 Summary: break dependency on nuget targets so that they can be executed separately 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: Sun, 28 Jul 2013 19:48:08 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: tpluscode: mark parsing speed explicit so it is completely omitted on build server 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/b099e6120b29/ Changeset: b099e6120b29 User: tpluscode Date: 2013-07-28 21:48:01 Summary: mark parsing speed explicit so it is completely omitted on build server 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: 4 Date: Tue, 30 Jul 2013 18:42:17 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: tpluscode: again, testing HttpUtility should only be done for portable library 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/ed381db2d02e/ Changeset: ed381db2d02e User: tpluscode Date: 2013-07-29 21:05:35 Summary: again, testing HttpUtility should only be done for portable library should not URL encode hyphens 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: 5 Date: Wed, 31 Jul 2013 16:30:10 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: tpluscode: remove old old broken url decode implementation 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/6ae7423f1312/ Changeset: 6ae7423f1312 User: tpluscode Date: 2013-07-31 18:26:12 Summary: remove old old broken url decode implementation 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: Mon, 05 Aug 2013 22:39:39 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Properly align IsSafeCharacter() with RFC 3986 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/918d6319cda2/ Changeset: 918d6319cda2 User: rvesse Date: 2013-08-06 00:39:24 Summary: Properly align IsSafeCharacter() with RFC 3986 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: 7 Date: Mon, 19 Aug 2013 18:42:13 -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/62ef76c64a5d/ Changeset: 62ef76c64a5d User: rvesse Date: 2013-08-19 20:20:57 Summary: Import final state of RDF WG Turtle test suite Affected #: 169 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4ba0b4b92471/ Changeset: 4ba0b4b92471 User: rvesse Date: 2013-08-19 20:24:32 Summary: Update project to have latest state of Turtle suite reflected in it Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/37e93bee3561/ Changeset: 37e93bee3561 User: rvesse Date: 2013-08-19 20:37:27 Summary: Fix up a couple of tests which require @base directives or de-UTF-8ing Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ff286bb169ce/ Changeset: ff286bb169ce User: rvesse Date: 2013-08-19 20:41:56 Summary: Fix Turtle tokenizer to allow for comment immediatedly after a Prefixed Name, this brings Turtle test suite compliance back to 100% 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: Mon, 19 Aug 2013 19:34:51 -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/ac1dc85f7aa3/ Changeset: ac1dc85f7aa3 User: rvesse Date: 2013-08-19 21:07:37 Summary: Add DOAP file for project Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3371022e80ce/ Changeset: 3371022e80ce User: rvesse Date: 2013-08-19 21:34:41 Summary: Minor tweak to DOAP file 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: 9 Date: Mon, 19 Aug 2013 19:39:00 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Add base declaration to DOAP file 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/9c8098dcd2ed/ Changeset: 9c8098dcd2ed User: rvesse Date: 2013-08-19 21:38:50 Summary: Add base declaration to DOAP file 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. ------------------------------ ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 11, Issue 1 ************************************************ |
|
From: Rob V. <rv...@do...> - 2013-08-19 19:15:14
|
The dotNetRDF project would like to report our implementation of the working groups Turtle recommendation. The EARL report may be downloaded at http://www.dotnetrdf.org/downloads/earl-turtle-v101-2013-08-19.ttl As of our next release (1.0.1) we pass all the tests, our current release (1.0.0) fails just 2 tests currently. Regards, Rob Vesse On 8/9/13 11:56 PM, "Eric Prud'hommeaux" <er...@w3...> wrote: >Please re-submit implementations reports for Turtle so you can > 1. Help us push Turtle to final Recommendation status. > 2. Raise public awareness of your implementation. >The tests are listed in a manifest.ttl file at ><http://www.w3.org/2013/TurtleTests/> > >Reports are in a language called EARL and should look like [[ > @prefix doap: <http://usefulinc.com/ns/doap#>. > @prefix earl: <http://www.w3.org/ns/earl#>. > @prefix foaf: <http://xmlns.com/foaf/0.1/>. > @prefix test: <http://swobjects.org/test_Turtle-WG.sh>. > @prefix dct: <http://purl.org/dc/terms/>. > @prefix xsd: <http://www.w3.org/2001/XMLSchema#>. > @prefix t: ><https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/tests-ttl/manifest >.ttl#>. > > <> foaf:primaryTopic <@@my program> ; > dct:issued "@@datetime"^^xsd:dateTime ; > foaf:maker <@@your foaf page> . > > <@@my program> > a doap:Project ; > doap:name "SWObjects" ; > doap:homepage <http://swobjects.org/> . > > <@@your foaf page> a foaf:Person ; > foaf:name "@@your name" ; > foaf:mbox <mailto:@@your email> ; > foaf:homepage <@@your homepage> . >]] >followed by an EARL assertion for each test, a la [[ > [] a earl:Assertion ; earl:test t:IRI_subject ; earl:subject <@@my >program> ; earl:assertedBy test: ; earl:result [ earl:outcome >earl:@@passed/failed; dct:date '@@datetime'^^xsd:dateTime ] . >]] Please see ><http://kasei.us/code/rdf-trine/rdf-trine-turtle-2013-03-01.ttl> >for an example. > >The CR comments wiki page has a list of currently submitted >implementations, but those will need to be re-run with this final >version of the tests. ><http://www.w3.org/2011/rdf-wg/wiki/Turtle_Candidate_Recommendation_Commen >ts#Implementations> > >-- >-ericP > |
|
From: Rob V. <rv...@do...> - 2013-08-05 22:22:52
|
Just to close the loop on this we should be leaving hyphen alone >From RFC 3986 Section 2.1 - http://tools.ietf.org/html/rfc3986#section-2.3 For consistency, percent-encoded octets in the ranges of ALPHA (%41-%5A and %61-%7A), DIGIT (%30-%39), hyphen (%2D), period (%2E), underscore (%5F), or tilde (%7E) should not be created by URI producers and, when found in a URI, should be decoded to their corresponding unreserved characters by URI normalizers. I'll check the implementation and make sure all those characters are marked as safe by our implementations Rob On 7/30/13 11:42 AM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Okay, we're all set then :) > >On Mon, Jul 29, 2013 at 10:48 PM, Rob Vesse <rv...@do...> wrote: >> While being standards compliant is nicest being compatible with System >>is >> the goal of the code. >> >> However for the + vs %20 I would always choose to use %20 even if it >> differs from the System behavior, as well as better standards compliance >> there is also the issue that Uri.UnescapeDataString() doesn't decode + >>to >> %20 which tends to break stuff. >> >> Rob >> >> On 7/29/13 12:05 PM, "Tomasz Pluskiewicz" <tom...@gm...> >> wrote: >> >>>All right. >>> >>>I will fix the hyphen encoding. >>> >>>Regarding spaces and multiple encodings I was just wondering whether >>>the intention was to implement the HttpUtility to be compatible with >>>the System one or more standards compliant. I understand that the >>>latter is intuitively more desirable but it's not so simple. If so I >>>guess it should remain as is but the fact should be clearly >>>documented. >>> >>>Tom >>> >>>On Mon, Jul 29, 2013 at 6:47 PM, Rob Vesse <rv...@do...> wrote: >>>> Comments inline: >>>> >>>> On 7/28/13 7:32 PM, "Tomasz Pluskiewicz" >>>><tom...@gm...> >>>> wrote: >>>> >>>>>Hi Rob >>>>> >>>>>I've noticed a problem with a portable library test on TeamCity: >>>>>http://ci.dotnetrdf.org/viewLog.html?buildId=432&tab=buildResultsDiv&b >>>>>ui >>>>>ld >>>>>TypeId=bt2#testNameId1576347966166389640 >>>>> >>>>>I've been trying to crack this and for that I am refactoring this code >>>>>so that there are some actual assertions and I've noticed some >>>>>discrepancies between VDS.RDF.HttpUtility and System.Web.HttpUtility >>>>>UrlEncode method: >>>>> >>>>>1. The portable code encodes the hyphen sign, which System class >>>>>leaves >>>>>intact >>>>>2. The portable code encodes spaces as %20 and System class encodes >>>>>spaces as + >>>>>3. The portable code leaves % intact and System class encodes % and >>>>>%20 >>>>>Are these differences by design? >>>> >>>> Hyphen sign should probably be left alone, may be an error in the >>>>range >>>>of >>>> characters considered safe. >>>> >>>> While since that code was touched, 2 is better behavior because space >>>>as + >>>> is not strictly speaking a valid URL encoding and is more an archaic >>>> behavior or old browser and servers, %20 for spaces should be the >>>>norm. >>>> >>>> As for 3 that is trickier, URL encoding and decoding is very error >>>>prone >>>> if done multiple times. I thing my implementation left already >>>>percent >>>> encoded terms encoded (or at least if they looked like already encoded >>>> things) whereas the System implementation just re-encodes things if >>>>run >>>> multiple times. >>>> >>>> Rob >>>> >>>>> >>>>>Regards, >>>>>Tom >>>>> >>>>>---------------------------------------------------------------------- >>>>>-- >>>>>-- >>>>>---- >>>>>See everything from the browser to the database with AppDynamics >>>>>Get end-to-end visibility with application monitoring from AppDynamics >>>>>Isolate bottlenecks and diagnose root cause in seconds. >>>>>Start your free trial of AppDynamics Pro today! >>>>>http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.c >>>>>lk >>>>>tr >>>>>k >>>>>_______________________________________________ >>>>>dotNetRDF-bugs mailing list >>>>>dot...@li... >>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-bugs >>>> >>>> >>>> >>>> >>>> >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>>----- >>>> Get your SQL database under version control now! >>>> Version control is standard for application code, but databases havent >>>> caught up. So what steps can you take to put your SQL databases under >>>> version control? Why should you start doing it? Read more to find out. >>>> >>>>http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.cl >>>>kt >>>>rk >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>Get your SQL database under version control now! >>>Version control is standard for application code, but databases havent >>>caught up. So what steps can you take to put your SQL databases under >>>version control? Why should you start doing it? Read more to find out. >>>http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clk >>>tr >>>k >>>_______________________________________________ >>>dotNetRDF-develop mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Get your SQL database under version control now! >> Version control is standard for application code, but databases havent >> caught up. So what steps can you take to put your SQL databases under >> version control? Why should you start doing it? Read more to find out. >> >>http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clkt >>rk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >-------------------------------------------------------------------------- >---- >Get your SQL database under version control now! >Version control is standard for application code, but databases havent >caught up. So what steps can you take to put your SQL databases under >version control? Why should you start doing it? Read more to find out. >http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktr >k >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2013-07-30 18:43:33
|
Okay, we're all set then :) On Mon, Jul 29, 2013 at 10:48 PM, Rob Vesse <rv...@do...> wrote: > While being standards compliant is nicest being compatible with System is > the goal of the code. > > However for the + vs %20 I would always choose to use %20 even if it > differs from the System behavior, as well as better standards compliance > there is also the issue that Uri.UnescapeDataString() doesn't decode + to > %20 which tends to break stuff. > > Rob > > On 7/29/13 12:05 PM, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>All right. >> >>I will fix the hyphen encoding. >> >>Regarding spaces and multiple encodings I was just wondering whether >>the intention was to implement the HttpUtility to be compatible with >>the System one or more standards compliant. I understand that the >>latter is intuitively more desirable but it's not so simple. If so I >>guess it should remain as is but the fact should be clearly >>documented. >> >>Tom >> >>On Mon, Jul 29, 2013 at 6:47 PM, Rob Vesse <rv...@do...> wrote: >>> Comments inline: >>> >>> On 7/28/13 7:32 PM, "Tomasz Pluskiewicz" <tom...@gm...> >>> wrote: >>> >>>>Hi Rob >>>> >>>>I've noticed a problem with a portable library test on TeamCity: >>>>http://ci.dotnetrdf.org/viewLog.html?buildId=432&tab=buildResultsDiv&bui >>>>ld >>>>TypeId=bt2#testNameId1576347966166389640 >>>> >>>>I've been trying to crack this and for that I am refactoring this code >>>>so that there are some actual assertions and I've noticed some >>>>discrepancies between VDS.RDF.HttpUtility and System.Web.HttpUtility >>>>UrlEncode method: >>>> >>>>1. The portable code encodes the hyphen sign, which System class leaves >>>>intact >>>>2. The portable code encodes spaces as %20 and System class encodes >>>>spaces as + >>>>3. The portable code leaves % intact and System class encodes % and %20 >>>>Are these differences by design? >>> >>> Hyphen sign should probably be left alone, may be an error in the range >>>of >>> characters considered safe. >>> >>> While since that code was touched, 2 is better behavior because space >>>as + >>> is not strictly speaking a valid URL encoding and is more an archaic >>> behavior or old browser and servers, %20 for spaces should be the norm. >>> >>> As for 3 that is trickier, URL encoding and decoding is very error prone >>> if done multiple times. I thing my implementation left already percent >>> encoded terms encoded (or at least if they looked like already encoded >>> things) whereas the System implementation just re-encodes things if run >>> multiple times. >>> >>> Rob >>> >>>> >>>>Regards, >>>>Tom >>>> >>>>------------------------------------------------------------------------ >>>>-- >>>>---- >>>>See everything from the browser to the database with AppDynamics >>>>Get end-to-end visibility with application monitoring from AppDynamics >>>>Isolate bottlenecks and diagnose root cause in seconds. >>>>Start your free trial of AppDynamics Pro today! >>>>http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk >>>>tr >>>>k >>>>_______________________________________________ >>>>dotNetRDF-bugs mailing list >>>>dot...@li... >>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-bugs >>> >>> >>> >>> >>> >>> >>>------------------------------------------------------------------------- >>>----- >>> Get your SQL database under version control now! >>> Version control is standard for application code, but databases havent >>> caught up. So what steps can you take to put your SQL databases under >>> version control? Why should you start doing it? Read more to find out. >>> >>>http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clkt >>>rk >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >>-------------------------------------------------------------------------- >>---- >>Get your SQL database under version control now! >>Version control is standard for application code, but databases havent >>caught up. So what steps can you take to put your SQL databases under >>version control? Why should you start doing it? Read more to find out. >>http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktr >>k >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2013-07-29 20:49:43
|
While being standards compliant is nicest being compatible with System is the goal of the code. However for the + vs %20 I would always choose to use %20 even if it differs from the System behavior, as well as better standards compliance there is also the issue that Uri.UnescapeDataString() doesn't decode + to %20 which tends to break stuff. Rob On 7/29/13 12:05 PM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >All right. > >I will fix the hyphen encoding. > >Regarding spaces and multiple encodings I was just wondering whether >the intention was to implement the HttpUtility to be compatible with >the System one or more standards compliant. I understand that the >latter is intuitively more desirable but it's not so simple. If so I >guess it should remain as is but the fact should be clearly >documented. > >Tom > >On Mon, Jul 29, 2013 at 6:47 PM, Rob Vesse <rv...@do...> wrote: >> Comments inline: >> >> On 7/28/13 7:32 PM, "Tomasz Pluskiewicz" <tom...@gm...> >> wrote: >> >>>Hi Rob >>> >>>I've noticed a problem with a portable library test on TeamCity: >>>http://ci.dotnetrdf.org/viewLog.html?buildId=432&tab=buildResultsDiv&bui >>>ld >>>TypeId=bt2#testNameId1576347966166389640 >>> >>>I've been trying to crack this and for that I am refactoring this code >>>so that there are some actual assertions and I've noticed some >>>discrepancies between VDS.RDF.HttpUtility and System.Web.HttpUtility >>>UrlEncode method: >>> >>>1. The portable code encodes the hyphen sign, which System class leaves >>>intact >>>2. The portable code encodes spaces as %20 and System class encodes >>>spaces as + >>>3. The portable code leaves % intact and System class encodes % and %20 >>>Are these differences by design? >> >> Hyphen sign should probably be left alone, may be an error in the range >>of >> characters considered safe. >> >> While since that code was touched, 2 is better behavior because space >>as + >> is not strictly speaking a valid URL encoding and is more an archaic >> behavior or old browser and servers, %20 for spaces should be the norm. >> >> As for 3 that is trickier, URL encoding and decoding is very error prone >> if done multiple times. I thing my implementation left already percent >> encoded terms encoded (or at least if they looked like already encoded >> things) whereas the System implementation just re-encodes things if run >> multiple times. >> >> Rob >> >>> >>>Regards, >>>Tom >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>See everything from the browser to the database with AppDynamics >>>Get end-to-end visibility with application monitoring from AppDynamics >>>Isolate bottlenecks and diagnose root cause in seconds. >>>Start your free trial of AppDynamics Pro today! >>>http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk >>>tr >>>k >>>_______________________________________________ >>>dotNetRDF-bugs mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-bugs >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Get your SQL database under version control now! >> Version control is standard for application code, but databases havent >> caught up. So what steps can you take to put your SQL databases under >> version control? Why should you start doing it? Read more to find out. >> >>http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clkt >>rk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >-------------------------------------------------------------------------- >---- >Get your SQL database under version control now! >Version control is standard for application code, but databases havent >caught up. So what steps can you take to put your SQL databases under >version control? Why should you start doing it? Read more to find out. >http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktr >k >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2013-07-29 19:11:40
|
Oh and by the way any idea why the decoding fails on TeamCity but works fine on my machine? If fails on line 938 [1]. I guess the percent sign is to blame but I'm baffled... Thanks, Tom [1] https://bitbucket.org/dotnetrdf/dotnetrdf/src/b099e6120b29a9a0a83a1425c1fae6e73f81aa18/Testing/unittest/Core/BasicTests1.cs?at=default#cl-938 On Mon, Jul 29, 2013 at 9:05 PM, Tomasz Pluskiewicz <tom...@gm...> wrote: > All right. > > I will fix the hyphen encoding. > > Regarding spaces and multiple encodings I was just wondering whether > the intention was to implement the HttpUtility to be compatible with > the System one or more standards compliant. I understand that the > latter is intuitively more desirable but it's not so simple. If so I > guess it should remain as is but the fact should be clearly > documented. > > Tom > > On Mon, Jul 29, 2013 at 6:47 PM, Rob Vesse <rv...@do...> wrote: >> Comments inline: >> >> On 7/28/13 7:32 PM, "Tomasz Pluskiewicz" <tom...@gm...> >> wrote: >> >>>Hi Rob >>> >>>I've noticed a problem with a portable library test on TeamCity: >>>http://ci.dotnetrdf.org/viewLog.html?buildId=432&tab=buildResultsDiv&build >>>TypeId=bt2#testNameId1576347966166389640 >>> >>>I've been trying to crack this and for that I am refactoring this code >>>so that there are some actual assertions and I've noticed some >>>discrepancies between VDS.RDF.HttpUtility and System.Web.HttpUtility >>>UrlEncode method: >>> >>>1. The portable code encodes the hyphen sign, which System class leaves >>>intact >>>2. The portable code encodes spaces as %20 and System class encodes >>>spaces as + >>>3. The portable code leaves % intact and System class encodes % and %20 >>>Are these differences by design? >> >> Hyphen sign should probably be left alone, may be an error in the range of >> characters considered safe. >> >> While since that code was touched, 2 is better behavior because space as + >> is not strictly speaking a valid URL encoding and is more an archaic >> behavior or old browser and servers, %20 for spaces should be the norm. >> >> As for 3 that is trickier, URL encoding and decoding is very error prone >> if done multiple times. I thing my implementation left already percent >> encoded terms encoded (or at least if they looked like already encoded >> things) whereas the System implementation just re-encodes things if run >> multiple times. >> >> Rob >> >>> >>>Regards, >>>Tom >>> >>>-------------------------------------------------------------------------- >>>---- >>>See everything from the browser to the database with AppDynamics >>>Get end-to-end visibility with application monitoring from AppDynamics >>>Isolate bottlenecks and diagnose root cause in seconds. >>>Start your free trial of AppDynamics Pro today! >>>http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktr >>>k >>>_______________________________________________ >>>dotNetRDF-bugs mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-bugs >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Get your SQL database under version control now! >> Version control is standard for application code, but databases havent >> caught up. So what steps can you take to put your SQL databases under >> version control? Why should you start doing it? Read more to find out. >> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2013-07-29 19:05:49
|
All right. I will fix the hyphen encoding. Regarding spaces and multiple encodings I was just wondering whether the intention was to implement the HttpUtility to be compatible with the System one or more standards compliant. I understand that the latter is intuitively more desirable but it's not so simple. If so I guess it should remain as is but the fact should be clearly documented. Tom On Mon, Jul 29, 2013 at 6:47 PM, Rob Vesse <rv...@do...> wrote: > Comments inline: > > On 7/28/13 7:32 PM, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>Hi Rob >> >>I've noticed a problem with a portable library test on TeamCity: >>http://ci.dotnetrdf.org/viewLog.html?buildId=432&tab=buildResultsDiv&build >>TypeId=bt2#testNameId1576347966166389640 >> >>I've been trying to crack this and for that I am refactoring this code >>so that there are some actual assertions and I've noticed some >>discrepancies between VDS.RDF.HttpUtility and System.Web.HttpUtility >>UrlEncode method: >> >>1. The portable code encodes the hyphen sign, which System class leaves >>intact >>2. The portable code encodes spaces as %20 and System class encodes >>spaces as + >>3. The portable code leaves % intact and System class encodes % and %20 >>Are these differences by design? > > Hyphen sign should probably be left alone, may be an error in the range of > characters considered safe. > > While since that code was touched, 2 is better behavior because space as + > is not strictly speaking a valid URL encoding and is more an archaic > behavior or old browser and servers, %20 for spaces should be the norm. > > As for 3 that is trickier, URL encoding and decoding is very error prone > if done multiple times. I thing my implementation left already percent > encoded terms encoded (or at least if they looked like already encoded > things) whereas the System implementation just re-encodes things if run > multiple times. > > Rob > >> >>Regards, >>Tom >> >>-------------------------------------------------------------------------- >>---- >>See everything from the browser to the database with AppDynamics >>Get end-to-end visibility with application monitoring from AppDynamics >>Isolate bottlenecks and diagnose root cause in seconds. >>Start your free trial of AppDynamics Pro today! >>http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktr >>k >>_______________________________________________ >>dotNetRDF-bugs mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-bugs > > > > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2013-07-29 16:59:43
|
Comments inline: On 7/28/13 7:32 PM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi Rob > >I've noticed a problem with a portable library test on TeamCity: >http://ci.dotnetrdf.org/viewLog.html?buildId=432&tab=buildResultsDiv&build >TypeId=bt2#testNameId1576347966166389640 > >I've been trying to crack this and for that I am refactoring this code >so that there are some actual assertions and I've noticed some >discrepancies between VDS.RDF.HttpUtility and System.Web.HttpUtility >UrlEncode method: > >1. The portable code encodes the hyphen sign, which System class leaves >intact >2. The portable code encodes spaces as %20 and System class encodes >spaces as + >3. The portable code leaves % intact and System class encodes % and %20 >Are these differences by design? Hyphen sign should probably be left alone, may be an error in the range of characters considered safe. While since that code was touched, 2 is better behavior because space as + is not strictly speaking a valid URL encoding and is more an archaic behavior or old browser and servers, %20 for spaces should be the norm. As for 3 that is trickier, URL encoding and decoding is very error prone if done multiple times. I thing my implementation left already percent encoded terms encoded (or at least if they looked like already encoded things) whereas the System implementation just re-encodes things if run multiple times. Rob > >Regards, >Tom > >-------------------------------------------------------------------------- >---- >See everything from the browser to the database with AppDynamics >Get end-to-end visibility with application monitoring from AppDynamics >Isolate bottlenecks and diagnose root cause in seconds. >Start your free trial of AppDynamics Pro today! >http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktr >k >_______________________________________________ >dotNetRDF-bugs mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-bugs |
|
From: Kevin <ke...@th...> - 2013-07-27 13:46:50
|
Tom, Thanks for the response as I would like to get started. Unfortunately I am new to developing with others online and just learning Mercurial. I have a fork of dotnetrdf (spin/dotnetrdf), which I updated just now. This update puts me at tag 100 which comes after 1.0.1-prerelease2278, and the last update was done by you (File "Testing/unitest/Parsing/LoaderTests.cs"). TortoiseHg is now at 2732 (2625a91c3104), which may be the sha1 you requested? I am editing files that Rob has started to implementing SPIN for dotnetrdf. Since I need the source to both edit and follow execution how is NuGet applicable? Are you suggest I just get the ".dll" with NuGet and try to develop outside of the dotnetrdf source code? Assuming I am on the right track checking out the latest code via TortoiseHg (Mercurial), how do I fix my compile issue? Updating the source did not change the build hang I encounter(In VS2012 I am right clicking Core/dotNetRDF and selecting build). This worked fine in my old code "2303 (a6174b925e81)" and I could even debug that solution. Perhaps there is some dependency I am missing. If you had a simple installation of VS2012 and just grabbed the latest code would everything just compile? The online overview of TeamCity looked impressive, but are you suggesting I learn/use this tool? The installation overview speaks of starting its server, which I assume is managed by 1 person? Would I tell TeamCity to use VS2012 or ANT to build? This may be a little much for my requirements. Thanks, Kevin -----Original Message----- From: Tomasz Pluskiewicz [mailto:tom...@gm...] Sent: Saturday, July 27, 2013 3:14 AM To: dotNetRDF Developer Discussion and Feature Request Subject: Re: [dotNetRDF-Develop] Unable to compile dotNetRDF (Rev 2701) Hi Kevin Actually wouldn't you prefer to fetch dotNetRDF fom NuGet instead? We could finally get the prerelease packages published from TeamCity so that when there are changes to the Fluent API, you would just update your packagae version. By the way, numeric revision are of little value because they are local to your repo. Please include the revision sha1 hashes. Thanks, Tom On Sat, Jul 27, 2013 at 5:10 AM, Kevin <ke...@th...> wrote: > Rob/Tom, > > > > Now that Fluent SPARQL has made it into dotNetRDF I am ready to try > and develop SPIN for dotNetRDF. I downloaded the latest source (Rev > 2701), but when I attempt to compile in VS2012 it hangs. I have a > copy of the code base (REV 2303) and everything compiles fine. Just > glancing around I notice big changes like the move toward a portable > library project. Can you help determine the issue or some VS2012 log > tricks to report the problem. I don't remember ever explicitly > downloading "Silverlight Developer Tools" or "Windows Phone Developer > Tools", but again my REV2303 works fine. To simplify the problem I > noticed if I just try to build project dotNetRDF it passes on 2303, > but fails on 2701 (See Output logs below). At this point I have just > downloaded Rev2701 with TortoiseHg, and then ran Build Clean/Build in VS2012 to produce this problem. > > > > System Setup: VS2012 on Windows 8 with NuGet > > > > Build (Rev 2701) dotNetRDF project (HANG) : > > 1>------ Build started: Project: dotNetRDF, Configuration: Debug Any > 1>CPU > ------ > > > > Build (Rev 2303) dotNetRDF project (Pass) : > > > > 1>------ Build started: Project: dotNetRDF, Configuration: Debug Any > 1>CPU > ------ > > 1> All packages listed in packages.config are already installed. > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Core\SubTreeIndexedTripleCollection.cs(223,21 ,223,59): > warning CS0618: > 'VDS.Common.Collections.MultiDictionary<VDS.RDF.Triple,object>.TryGetK > ey(VDS.RDF.Triple, out VDS.RDF.Triple)' is obsolete: 'TryGetKey() is > included for historical reasons and will be removed in future > versions' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Core\TreeIndexedTripleCollection.cs(273,21,27 3,59): > warning CS0618: > 'VDS.Common.Collections.MultiDictionary<VDS.RDF.Triple,object>.TryGetK > ey(VDS.RDF.Triple, out VDS.RDF.Triple)' is obsolete: 'TryGetKey() is > included for historical reasons and will be removed in future > versions' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Algebra\BaseMultiset.cs(891,32,891,40): > warning CS1591: Missing XML comment for publicly visible type or > member 'VDS.RDF.Query.Algebra.BaseMultiset.ToString()' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(42,1 6,42,39): > warning CS1591: Missing XML comment for publicly visible type or > member 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.SetDistinctnessComparer()' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(44,1 6,44,39): > warning CS1591: Missing XML comment for publicly visible type or > member 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.SetDistinctnessComparer(Syste m.Collections.Generic.IEnumerable<string>)' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(49,2 1,49,27): > warning CS1591: Missing XML comment for publicly visible type or > member > 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.Equals(VDS.RDF.Query.Al > gebra.ISet, > VDS.RDF.Query.Algebra.ISet)' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(61,2 0,61,31): > warning CS1591: Missing XML comment for publicly visible type or > member 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.GetHashCode(VDS.RDF.Query.Alg ebra.ISet)' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Core\TripleCollection.cs(113,21,113,59): > warning CS0618: > 'VDS.Common.Collections.MultiDictionary<VDS.RDF.Triple,object>.TryGetK > ey(VDS.RDF.Triple, out VDS.RDF.Triple)' is obsolete: 'TryGetKey() is > included for historical reasons and will be removed in future > versions' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Aggregates\Sparql\GroupConcatAggregate. cs(119,35,119,48): > warning CS1591: Missing XML comment for publicly visible type or > member > 'VDS.RDF.Query.Aggregates.Sparql.GroupConcatAggregate.ValueInternal(VD > S.RDF.Query.SparqlEvaluationContext, > int)' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Configuration\StorageFactories.cs(155,47,155, 61): > warning CS0618: 'VDS.RDF.Storage.DydraConnector' is obsolete: 'The > dotNetRDF team does not recommend usage of Dydra because their API > frequently exhibits inconsistency, transient failures and other errors' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Configuration\StorageFactories.cs(159,47,159, 61): > warning CS0618: 'VDS.RDF.Storage.DydraConnector' is obsolete: 'The > dotNetRDF team does not recommend usage of Dydra because their API > frequently exhibits inconsistency, transient failures and other errors' > > 1> dotNetRDF -> C:\Users\Kevin\Documents\Visual Studio > 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\bin\Debug\dotNetRDF.dll > > ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped > ========== > > > > Thanks, > > Kevin > > > ---------------------------------------------------------------------- > -------- See everything from the browser to the database with > AppDynamics Get end-to-end visibility with application monitoring from > AppDynamics Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.c > lktrk _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > ---------------------------------------------------------------------------- -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ dotNetRDF-develop mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: <dot...@li...> - 2013-07-27 12:40:44
|
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: rvesse: Make rest of async methods in SparqlRemoteEndpoint use AsyncError to pass back errors (CORE-370) (Bitbucket) 3. commit/dotnetrdf: 4 new changesets (Bitbucket) 4. commit/dotnetrdf: 5 new changesets (Bitbucket) 5. commit/dotnetrdf: 2 new changesets (Bitbucket) 6. commit/dotnetrdf: 2 new changesets (Bitbucket) 7. commit/dotnetrdf: rvesse: Add set of unit tests which verify DESCRIBE and default graph interaction to validate that a bug report is invalid (CORE-372) (Bitbucket) 8. commit/dotnetrdf: tpluscode: remove slv-async-sparql project from solution (Bitbucket) 9. commit/dotnetrdf: 2 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Jul 2013 22:54:37 -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/31fa4ac01d28/ Changeset: 31fa4ac01d28 Branch: CORE-370 User: rvesse Date: 2013-07-12 00:44:15 Summary: Introduce AsyncError class a wrapper that can be passed back as the state for async callback APIs that don't have a better error handling contract to indicate both the error and the original state passed to the async method (CORE-370) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1b214aaac693/ Changeset: 1b214aaac693 Branch: CORE-370 User: rvesse Date: 2013-07-12 00:50:55 Summary: Start swapping over SparqlRemoteEndpoint code to pass back AsyncError in the state when appropriate (CORE-370) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6c0254065321/ Changeset: 6c0254065321 Branch: CORE-370 User: rvesse Date: 2013-07-12 00:54:16 Summary: Disable more tests that use APIs unavailable on PCL builds (CORE-371) 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: Thu, 11 Jul 2013 22:58:20 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Make rest of async methods in SparqlRemoteEndpoint use AsyncError to pass back errors (CORE-370) 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/02a6e95be957/ Changeset: 02a6e95be957 Branch: CORE-370 User: rvesse Date: 2013-07-12 00:58:09 Summary: Make rest of async methods in SparqlRemoteEndpoint use AsyncError to pass back errors (CORE-370) 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: Fri, 12 Jul 2013 22:40: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/c29162b7d44e/ Changeset: c29162b7d44e Branch: CORE-370 User: rvesse Date: 2013-07-12 20:53:19 Summary: Fix SparqlRemoteUpdateEndpoint to propagate async errors appropriately using AsyncError state (CORE-370) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/baff9754cb64/ Changeset: baff9754cb64 Branch: CORE-370 User: rvesse Date: 2013-07-12 21:16:30 Summary: Clean up more async error propagation (CORE-370) Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4d54e34f030f/ Changeset: 4d54e34f030f Branch: CORE-370 User: rvesse Date: 2013-07-13 00:31:02 Summary: More async error propagation changes (CORE-370) Affected #: 13 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/03769514fe17/ Changeset: 03769514fe17 User: rvesse Date: 2013-07-13 00:39:03 Summary: Merge async error propagation improvements from CORE-370 branch Affected #: 39 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: Fri, 12 Jul 2013 22:44:42 -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/b33003ff4cba/ Changeset: b33003ff4cba Branch: CORE-371 User: rvesse Date: 2013-07-13 00:43:04 Summary: Merge CORE-370 changes into CORE-371 branch Affected #: 19 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/cdc79f92384b/ Changeset: cdc79f92384b Branch: CORE-371 User: rvesse Date: 2013-07-13 00:43:14 Summary: Close CORE-371 branch Affected #: 0 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8bf8b17e26e2/ Changeset: 8bf8b17e26e2 Branch: CORE-370 User: rvesse Date: 2013-07-13 00:43:35 Summary: Merge in closed CORE-371 branch to clean up commit graph Affected #: 0 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9918d9e3017f/ Changeset: 9918d9e3017f Branch: CORE-370 User: rvesse Date: 2013-07-13 00:43:58 Summary: Close CORE-370 branch Affected #: 0 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a0185c038209/ Changeset: a0185c038209 User: rvesse Date: 2013-07-13 00:44:19 Summary: Merge in closed CORE-370 branch to clean up commit graph Affected #: 0 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: Fri, 12 Jul 2013 23:12:24 -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/384a730955d2/ Changeset: 384a730955d2 User: rvesse Date: 2013-07-13 00:49:23 Summary: Note recent changes in Change Log (CORE-303, CORE-370, CORE-371) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/43d49e76bebf/ Changeset: 43d49e76bebf User: rvesse Date: 2013-07-13 01:07:45 Summary: Fix the sanity-check.bat hook script to also block commits where files are missing. Add a what-changed.bat script for use as a post-commit hook which prints details of last commit 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: 6 Date: Tue, 16 Jul 2013 16:35:29 -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/2064a7c50804/ Changeset: 2064a7c50804 Branch: sparql-ops User: rvesse Date: 2013-07-13 01:14:14 Summary: Merge latest work from default to sparql-ops branch Affected #: 53 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/25cbab229627/ Changeset: 25cbab229627 User: rvesse Date: 2013-07-16 18:35:09 Summary: Add a couple of tests to try and repro a mailing list reported issue 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: 7 Date: Thu, 18 Jul 2013 14:08:53 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Add set of unit tests which verify DESCRIBE and default graph interaction to validate that a bug report is invalid (CORE-372) 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/6281c6b92b83/ Changeset: 6281c6b92b83 User: rvesse Date: 2013-07-18 16:08:26 Summary: Add set of unit tests which verify DESCRIBE and default graph interaction to validate that a bug report is invalid (CORE-372) 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: Sat, 27 Jul 2013 09:39:44 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: tpluscode: remove slv-async-sparql project from solution 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/42845beec939/ Changeset: 42845beec939 User: tpluscode Date: 2013-07-27 11:01:35 Summary: remove slv-async-sparql project from solution 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: 9 Date: Sat, 27 Jul 2013 12:40:34 -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/908d74547d9e/ Changeset: 908d74547d9e User: tpluscode Date: 2013-07-27 14:37:24 Summary: split test cases Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2625a91c3104/ Changeset: 2625a91c3104 User: tpluscode Date: 2013-07-27 14:40:24 Summary: assembly name is the same for portable build 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. ------------------------------ ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 10, Issue 3 ************************************************ |
|
From: Tomasz P. <tom...@gm...> - 2013-07-27 08:14:40
|
Hi Kevin Actually wouldn't you prefer to fetch dotNetRDF fom NuGet instead? We could finally get the prerelease packages published from TeamCity so that when there are changes to the Fluent API, you would just update your packagae version. By the way, numeric revision are of little value because they are local to your repo. Please include the revision sha1 hashes. Thanks, Tom On Sat, Jul 27, 2013 at 5:10 AM, Kevin <ke...@th...> wrote: > Rob/Tom, > > > > Now that Fluent SPARQL has made it into dotNetRDF I am ready to try and > develop SPIN for dotNetRDF. I downloaded the latest source (Rev 2701), but > when I attempt to compile in VS2012 it hangs. I have a copy of the code > base (REV 2303) and everything compiles fine. Just glancing around I notice > big changes like the move toward a portable library project. Can you help > determine the issue or some VS2012 log tricks to report the problem. I > don't remember ever explicitly downloading "Silverlight Developer Tools" or > "Windows Phone Developer Tools", but again my REV2303 works fine. To > simplify the problem I noticed if I just try to build project dotNetRDF it > passes on 2303, but fails on 2701 (See Output logs below). At this point I > have just downloaded Rev2701 with TortoiseHg, and then ran Build Clean/Build > in VS2012 to produce this problem. > > > > System Setup: VS2012 on Windows 8 with NuGet > > > > Build (Rev 2701) dotNetRDF project (HANG) : > > 1>------ Build started: Project: dotNetRDF, Configuration: Debug Any CPU > ------ > > > > Build (Rev 2303) dotNetRDF project (Pass) : > > > > 1>------ Build started: Project: dotNetRDF, Configuration: Debug Any CPU > ------ > > 1> All packages listed in packages.config are already installed. > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Core\SubTreeIndexedTripleCollection.cs(223,21,223,59): > warning CS0618: > 'VDS.Common.Collections.MultiDictionary<VDS.RDF.Triple,object>.TryGetKey(VDS.RDF.Triple, > out VDS.RDF.Triple)' is obsolete: 'TryGetKey() is included for historical > reasons and will be removed in future versions' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Core\TreeIndexedTripleCollection.cs(273,21,273,59): > warning CS0618: > 'VDS.Common.Collections.MultiDictionary<VDS.RDF.Triple,object>.TryGetKey(VDS.RDF.Triple, > out VDS.RDF.Triple)' is obsolete: 'TryGetKey() is included for historical > reasons and will be removed in future versions' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Algebra\BaseMultiset.cs(891,32,891,40): > warning CS1591: Missing XML comment for publicly visible type or member > 'VDS.RDF.Query.Algebra.BaseMultiset.ToString()' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(42,16,42,39): > warning CS1591: Missing XML comment for publicly visible type or member > 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.SetDistinctnessComparer()' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(44,16,44,39): > warning CS1591: Missing XML comment for publicly visible type or member > 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.SetDistinctnessComparer(System.Collections.Generic.IEnumerable<string>)' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(49,21,49,27): > warning CS1591: Missing XML comment for publicly visible type or member > 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.Equals(VDS.RDF.Query.Algebra.ISet, > VDS.RDF.Query.Algebra.ISet)' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(61,20,61,31): > warning CS1591: Missing XML comment for publicly visible type or member > 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.GetHashCode(VDS.RDF.Query.Algebra.ISet)' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Core\TripleCollection.cs(113,21,113,59): > warning CS0618: > 'VDS.Common.Collections.MultiDictionary<VDS.RDF.Triple,object>.TryGetKey(VDS.RDF.Triple, > out VDS.RDF.Triple)' is obsolete: 'TryGetKey() is included for historical > reasons and will be removed in future versions' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Query\Aggregates\Sparql\GroupConcatAggregate.cs(119,35,119,48): > warning CS1591: Missing XML comment for publicly visible type or member > 'VDS.RDF.Query.Aggregates.Sparql.GroupConcatAggregate.ValueInternal(VDS.RDF.Query.SparqlEvaluationContext, > int)' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Configuration\StorageFactories.cs(155,47,155,61): > warning CS0618: 'VDS.RDF.Storage.DydraConnector' is obsolete: 'The dotNetRDF > team does not recommend usage of Dydra because their API frequently exhibits > inconsistency, transient failures and other errors' > > 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\Configuration\StorageFactories.cs(159,47,159,61): > warning CS0618: 'VDS.RDF.Storage.DydraConnector' is obsolete: 'The dotNetRDF > team does not recommend usage of Dydra because their API frequently exhibits > inconsistency, transient failures and other errors' > > 1> dotNetRDF -> C:\Users\Kevin\Documents\Visual Studio > 2012\Projects\SpinDotNetRdf > (Rev2303)\Libraries\core\net40\bin\Debug\dotNetRDF.dll > > ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== > > > > Thanks, > > Kevin > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Kevin <ke...@th...> - 2013-07-27 03:26:08
|
Rob/Tom, Now that Fluent SPARQL has made it into dotNetRDF I am ready to try and develop SPIN for dotNetRDF. I downloaded the latest source (Rev 2701), but when I attempt to compile in VS2012 it hangs. I have a copy of the code base (REV 2303) and everything compiles fine. Just glancing around I notice big changes like the move toward a portable library project. Can you help determine the issue or some VS2012 log tricks to report the problem. I don't remember ever explicitly downloading "Silverlight Developer Tools" or "Windows Phone Developer Tools", but again my REV2303 works fine. To simplify the problem I noticed if I just try to build project dotNetRDF it passes on 2303, but fails on 2701 (See Output logs below). At this point I have just downloaded Rev2701 with TortoiseHg, and then ran Build Clean/Build in VS2012 to produce this problem. System Setup: VS2012 on Windows 8 with NuGet Build (Rev 2701) dotNetRDF project (HANG) : 1>------ Build started: Project: dotNetRDF, Configuration: Debug Any CPU ------ Build (Rev 2303) dotNetRDF project (Pass) : 1>------ Build started: Project: dotNetRDF, Configuration: Debug Any CPU ------ 1> All packages listed in packages.config are already installed. 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\Core\SubTreeIndexedTripleCollection.cs(223,21 ,223,59): warning CS0618: 'VDS.Common.Collections.MultiDictionary<VDS.RDF.Triple,object>.TryGetKey(VDS .RDF.Triple, out VDS.RDF.Triple)' is obsolete: 'TryGetKey() is included for historical reasons and will be removed in future versions' 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\Core\TreeIndexedTripleCollection.cs(273,21,27 3,59): warning CS0618: 'VDS.Common.Collections.MultiDictionary<VDS.RDF.Triple,object>.TryGetKey(VDS .RDF.Triple, out VDS.RDF.Triple)' is obsolete: 'TryGetKey() is included for historical reasons and will be removed in future versions' 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\Query\Algebra\BaseMultiset.cs(891,32,891,40): warning CS1591: Missing XML comment for publicly visible type or member 'VDS.RDF.Query.Algebra.BaseMultiset.ToString()' 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(42,1 6,42,39): warning CS1591: Missing XML comment for publicly visible type or member 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.SetDistinctnessComparer()' 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(44,1 6,44,39): warning CS1591: Missing XML comment for publicly visible type or member 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.SetDistinctnessComparer(Syste m.Collections.Generic.IEnumerable<string>)' 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(49,2 1,49,27): warning CS1591: Missing XML comment for publicly visible type or member 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.Equals(VDS.RDF.Query.Algebra. ISet, VDS.RDF.Query.Algebra.ISet)' 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\Query\Algebra\SetDistinctnessComparer.cs(61,2 0,61,31): warning CS1591: Missing XML comment for publicly visible type or member 'VDS.RDF.Query.Algebra.SetDistinctnessComparer.GetHashCode(VDS.RDF.Query.Alg ebra.ISet)' 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\Core\TripleCollection.cs(113,21,113,59): warning CS0618: 'VDS.Common.Collections.MultiDictionary<VDS.RDF.Triple,object>.TryGetKey(VDS .RDF.Triple, out VDS.RDF.Triple)' is obsolete: 'TryGetKey() is included for historical reasons and will be removed in future versions' 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\Query\Aggregates\Sparql\GroupConcatAggregate. cs(119,35,119,48): warning CS1591: Missing XML comment for publicly visible type or member 'VDS.RDF.Query.Aggregates.Sparql.GroupConcatAggregate.ValueInternal(VDS.RDF. Query.SparqlEvaluationContext, int)' 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\Configuration\StorageFactories.cs(155,47,155, 61): warning CS0618: 'VDS.RDF.Storage.DydraConnector' is obsolete: 'The dotNetRDF team does not recommend usage of Dydra because their API frequently exhibits inconsistency, transient failures and other errors' 1>C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\Configuration\StorageFactories.cs(159,47,159, 61): warning CS0618: 'VDS.RDF.Storage.DydraConnector' is obsolete: 'The dotNetRDF team does not recommend usage of Dydra because their API frequently exhibits inconsistency, transient failures and other errors' 1> dotNetRDF -> C:\Users\Kevin\Documents\Visual Studio 2012\Projects\SpinDotNetRdf (Rev2303)\Libraries\core\net40\bin\Debug\dotNetRDF.dll ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== Thanks, Kevin |
|
From: <tr...@do...> - 2013-07-18 14:20: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>Describe query not returning the correct triples</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 "Closed"
</li>
<li>Resolution changed from "Unassigned" to "Invalid"
</li>
<li>Assigned to changed from "Unassigned" to "Rob Vesse"
</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=372" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=372</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-07-18 14:19:19
|
<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>Describe query not returning the correct triples</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-07-18 03:18 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
This behaviour is by design, the reason it worked back in 0.5.0 and now doesn't is that way back in 0.7.0 we made the decision to change our default behaviour around the default graph to better align with the SPARQL standard and the default behaviour of other popular SPARQL tools.</p>
<p>
To understand why the query no longer works you need to understand how we now treat the default graph. An in-memory store has a single unnamed graph and a collection of named graphs, prior to 0.7.0 if you didn't explicitly specify a default graph we took it to be what is commonly called the union default graph. So queries that specified no default graph actually operated over all graphs (both named and unnamed) in the store. From 0.7.0 onwards the behaviour changed so unless explicitly specified the default graph is only the unnamed graph of the store.</p>
<p>
What this means in the case of your DESCRIBE query is that the WHERE clause uses a GRAPH clause to access a named graph so is able to access the data in that graph. But then when we come to attempt to form the description of your resource we are only looking at the default graph which is the unnamed graph and happens to be empty in your example so you end up with an empty description.</p>
<p>
The reason a SELECT works fine is that the WHERE clause is using a GRAPH clause so again sees the data in your named graph but in the case of a SELECT we then simply return that data.</p>
<p>
Your DESCRIBE query can be rewritten to give a non-empty description by making the named graph the default graph for the query e.g.</p>
<p>
DESCRIBE ?s FROM <http://graph> WHERE { ?s <http://dummy/pred> <http://dummy/world> }</p>
<p>
Hope this helps,</p>
<p>
Rob</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=372" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=372</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-07-18 08:52: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>Describe query not returning the correct triples</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Ray Stannard</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.1</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>
Hi</p>
<p>
I am use the InMemoryManager for unit testing. I have upgraded dotNetRDF from version 0.5 to 1.0.1.2533 and this has broken a couple of our tests. I can show the isue in the following code:-</p>
<div>
<div>
var store = new InMemoryManager();</div>
<div>
</div>
<div>
store.Update(@"CREATE GRAPH <http://dummy/graph>");</div>
<div>
</div>
<div>
var g = new Graph();</div>
<div>
</div>
<div>
var s = g.CreateUriNode(new Uri("http://dummy/hello"));</div>
<div>
var p = g.CreateUriNode(new Uri("http://dummy/pred"));</div>
<div>
var o = g.CreateUriNode(new Uri("http://dummy/world"));</div>
<div>
</div>
<div>
g.Assert(new Triple(s, p, o));</div>
<div>
</div>
<div>
store.UpdateGraph("http://dummy/graph", g.Triples, null);</div>
<div>
</div>
<div>
var result = (Graph)store.Query(@"describe ?s where { graph <http://dummy/graph> { ?s <http://dummy/pred> <http://dummy/world> } }");</div>
<div>
</div>
<div>
Assert.AreEqual(1, result.Triples.Count); // Fails incorrectly</div>
<div>
</div>
<div>
Am I missing something? If I swap the Describe for a Select, it works OK.</div>
<div>
</div>
<div>
Thanks</div>
<div>
</div>
<div>
Ray</div>
</div>
<p>
</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=372" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=372</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: Tomasz P. <tom...@gm...> - 2013-07-16 19:32:19
|
Oh Contrib was just a suggestion and it can be created anytime. For now Jerin, I think it hould your personal repo. Are you fine with BitBucket? I though I could actually ignore the obsolete branch and just extract the relevent repository parts until 0.7.1. That is the last commit when Data.Sql was still present and we could start from there. On Tue, Jul 16, 2013 at 9:21 PM, Rob Vesse <rv...@do...> wrote: > Feel free to attempt this, this may be complicated by the fact that the > code was on Trunk and later moved to the obsolete branch and then deleted > from Trunk. You will likely need to fiddle with the branch and file maps > somewhat to get this to work properly. > > Would it be the end of the world if the history was lost in the new repo? > The history still exists in the main repo and we can make reference back > to it but if someone wants to resurrect it as a separate community > maintained module they just need the base code to start from and then it > builds new history as it is updated. You can get this by updating to the > relevant branch and then copying the relevant directories. > > In terms of code integration it was a IGenericIOManager implementation > (which was refactored to IStorageProvider) so there will be some code > updates to be done to make it compile against dotNetRDF 1.0.0 > There would also be some work to get the different framework targeting > project files to work since that was before the refactoring to do it all > within VS with pre-build events for sync ups. > > A dotNetRDF.Contrib still seems somewhat heavyweight and implies some > level of oversight by the core team, given that Data.Sql was something I > explicitly chose to deprecate having it under a Contrib module kinda seems > a little odd in that regard. Maybe we can discuss the general Contrib > concept (what it would be, how it would work etc) in a separate thread and > not conflate it with this thread? > > Rob > > From: Tomasz Pluskiewicz <tom...@gm...> > Reply-To: dotNetRDF Developer Discussion and Feature Request < > dot...@li...> > Date: Tuesday, July 16, 2013 11:19 AM > To: dotNetRDF Developer Discussion and Feature Request < > dot...@li...> > Cc: Jerin Lee <not...@bi...> > Subject: Re: [dotNetRDF-Develop] [Bitbucket] Suggestion about Data.Sql > part (direct message) > > Hi Rob, Jerin > > I can't recall how the Data.Sql fit in the old code. If possible I would > extract the relevant part of the repository using the convert plugin > (similarily to what we did with the svn->hg migration). This would give you > a new repo/project with all then add dotNetRDF reference from NuGet and > it's almost done. Finally a new project could be created. Maybe it's a good > moment for dotNetRDF.Contrib? > > What do you guys think. Would you like me to try such migration? > > Regards, > Tom > > > On Tue, Jul 16, 2013 at 7:00 PM, Rob Vesse <rv...@do...> wrote: > >> Hi Jerin >> >> The beauty of version control is the code still exists you just have to >> go back in time. >> >> You can find it in the closed obsolete branch in Mercurial, from a clone >> of our repository (https://bitbucket.org/dotnetrdf/dotnetrdf) run the >> following: >> >> hg up –C obsolete >> >> There you can find the code under Libraries\data.sql >> >> Or if you prefer just download the 0.7.0 source which was the last >> release to include the library in an not completely deprecated state ( >> http://www.dotnetrdf.org/downloads/dotnetrdf_library_source_070_beta.zip) >> >> The main difference between the Hash and Simple stores was in how node >> and graph IDs are looked up, see the GetNodeID and GetGraphID procedure >> definitions. In the hash store we used a computed column to hash data to >> an integer which makes looking up existing IDs a function call and then a >> simple index scan. With the simple store we don't use hashes so have to do >> full/partial value based lookup which can be a lot slower. The simple >> store was designed for backwards compatibility with earlier SQL Server >> versions that didn't support hash functions, the Simple 2000 store is the >> simple store done without computed columns which didn't support what we >> need in SQL Server 2000. >> >> It would likely need some clean up before it can be thrown up on >> BitBucket to get it to compile with the latest Core, use NuGet for >> dependencies etc. and you are welcome to do that if you wish, I'm afraid I >> don't have time to do it myself. >> >> Rob >> >> From: Jerin Lee <not...@bi...> >> Date: Saturday, July 13, 2013 11:45 PM >> To: Rob Vesse <rv...@do...> >> Subject: Fwd: [Bitbucket] Suggestion about Data.Sql part (direct message) >> >> You are receiving this email because you're an administrator of the >> dotnetrdf team. >> [image: taurenshaman] *Jerin Lee* sent you a message: Hello, guys. I >> love dotNetRdf very much. 3rd storage solution is a little complicated for >> a individual developer. So I wanna try it with sql. I know you sotpped the >> Data.Sql part. But my suggestion is that you can put the code to a seperate >> project at bitbucket/github, so that you give the choosing right to >> developers/users. Also maybe someone will maintain and forward it. P.S. I >> viewed the resource sql file in dotNetRDF.Data.Sql.dll using JustDecompile. >> Do you have some doc or words to describe the difference between >> AdoHashStore.sql and AdoSimpleStore.sql. Thank you for your time. Best >> wishes! >> Team email forwarding can be configured from the groups >> administration page<https://bitbucket.org/account/user/dotnetrdf/groups/> [image: >> Bitbucket] <https://bitbucket.org> >> >> >> >> ------------------------------------------------------------------------------ >> See everything from the browser to the database with AppDynamics >> Get end-to-end visibility with application monitoring from AppDynamics >> Isolate bottlenecks and diagnose root cause in seconds. >> Start your free trial of AppDynamics Pro today! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics Get > end-to-end visibility with application monitoring from AppDynamics Isolate > bottlenecks and diagnose root cause in seconds. Start your free trial of > AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk_______________________________________________dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > |
|
From: Rob V. <rv...@do...> - 2013-07-16 19:22:59
|
Feel free to attempt this, this may be complicated by the fact that the code was on Trunk and later moved to the obsolete branch and then deleted from Trunk. You will likely need to fiddle with the branch and file maps somewhat to get this to work properly. Would it be the end of the world if the history was lost in the new repo? The history still exists in the main repo and we can make reference back to it but if someone wants to resurrect it as a separate community maintained module they just need the base code to start from and then it builds new history as it is updated. You can get this by updating to the relevant branch and then copying the relevant directories. In terms of code integration it was a IGenericIOManager implementation (which was refactored to IStorageProvider) so there will be some code updates to be done to make it compile against dotNetRDF 1.0.0 There would also be some work to get the different framework targeting project files to work since that was before the refactoring to do it all within VS with pre-build events for sync ups. A dotNetRDF.Contrib still seems somewhat heavyweight and implies some level of oversight by the core team, given that Data.Sql was something I explicitly chose to deprecate having it under a Contrib module kinda seems a little odd in that regard. Maybe we can discuss the general Contrib concept (what it would be, how it would work etc) in a separate thread and not conflate it with this thread? Rob From: Tomasz Pluskiewicz <tom...@gm...> Reply-To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: Tuesday, July 16, 2013 11:19 AM To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Cc: Jerin Lee <not...@bi...> Subject: Re: [dotNetRDF-Develop] [Bitbucket] Suggestion about Data.Sql part (direct message) > Hi Rob, Jerin > > I can't recall how the Data.Sql fit in the old code. If possible I would > extract the relevant part of the repository using the convert plugin > (similarily to what we did with the svn->hg migration). This would give you a > new repo/project with all then add dotNetRDF reference from NuGet and it's > almost done. Finally a new project could be created. Maybe it's a good moment > for dotNetRDF.Contrib? > > What do you guys think. Would you like me to try such migration? > > Regards, > Tom > > > On Tue, Jul 16, 2013 at 7:00 PM, Rob Vesse <rv...@do...> wrote: >> Hi Jerin >> >> The beauty of version control is the code still exists you just have to go >> back in time. >> >> You can find it in the closed obsolete branch in Mercurial, from a clone of >> our repository (https://bitbucket.org/dotnetrdf/dotnetrdf) run the following: >> >> hg up C obsolete >> >> There you can find the code under Libraries\data.sql >> >> Or if you prefer just download the 0.7.0 source which was the last release to >> include the library in an not completely deprecated state >> (http://www.dotnetrdf.org/downloads/dotnetrdf_library_source_070_beta.zip) >> >> The main difference between the Hash and Simple stores was in how node and >> graph IDs are looked up, see the GetNodeID and GetGraphID procedure >> definitions. In the hash store we used a computed column to hash data to an >> integer which makes looking up existing IDs a function call and then a simple >> index scan. With the simple store we don't use hashes so have to do >> full/partial value based lookup which can be a lot slower. The simple store >> was designed for backwards compatibility with earlier SQL Server versions >> that didn't support hash functions, the Simple 2000 store is the simple store >> done without computed columns which didn't support what we need in SQL Server >> 2000. >> >> It would likely need some clean up before it can be thrown up on BitBucket to >> get it to compile with the latest Core, use NuGet for dependencies etc. and >> you are welcome to do that if you wish, I'm afraid I don't have time to do it >> myself. >> >> Rob >> >> From: Jerin Lee <not...@bi...> >> Date: Saturday, July 13, 2013 11:45 PM >> To: Rob Vesse <rv...@do...> >> Subject: Fwd: [Bitbucket] Suggestion about Data.Sql part (direct message) >> >>> >>> >>> >>> You are receiving this email because you're an administrator of the >>> dotnetrdf team. >>> >>> >>> >>> >>> Jerin Lee sent you a message: >>> Hello, guys. I love dotNetRdf very much. 3rd storage solution is a little >>> complicated for a individual developer. So I wanna try it with sql. I know >>> you sotpped the Data.Sql part. But my suggestion is that you can put the >>> code to a seperate project at bitbucket/github, so that you give the >>> choosing right to developers/users. Also maybe someone will maintain and >>> forward it. P.S. I viewed the resource sql file in dotNetRDF.Data.Sql.dll >>> using JustDecompile. Do you have some doc or words to describe the >>> difference between AdoHashStore.sql and AdoSimpleStore.sql. Thank you for >>> your time. Best wishes! >>> >>> >>> >>> Team email forwarding can be configured from the groups >>> administration page <https://bitbucket.org/account/user/dotnetrdf/groups/> >>> <https://bitbucket.org> >>> >>> ---------------------------------------------------------------------------- >>> -- >>> See everything from the browser to the database with AppDynamics >>> Get end-to-end visibility with application monitoring from AppDynamics >>> Isolate bottlenecks and diagnose root cause in seconds. >>> Start your free trial of AppDynamics Pro today! >>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>> >>> ---------------------------------------------------------------------------- >>> -- See everything from the browser to the database with AppDynamics Get >>> end-to-end visibility with application monitoring from AppDynamics Isolate >>> bottlenecks and diagnose root cause in seconds. Start your free trial of >>> AppDynamics Pro today! >>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk_ >>> ______________________________________________ dotNetRDF-develop mailing >>> list dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> |
|
From: Rob V. <rv...@do...> - 2013-07-16 18:46:23
|
Sorry that was not meant to be included, was a temporary project to debug CORE-370 Needs to be removed from the solution and I need to write up some unit tests that cover the bug Rob On 7/16/13 11:36 AM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi Rob > >I looked at TeamCity and there is a project missing called >slv-async-sparql.csproj. > >The relative path indicates that it sits outside of the main folder >structure, which would explain why it didn't end up in the repo. > >Regards, >Tom > >-------------------------------------------------------------------------- >---- >See everything from the browser to the database with AppDynamics >Get end-to-end visibility with application monitoring from AppDynamics >Isolate bottlenecks and diagnose root cause in seconds. >Start your free trial of AppDynamics Pro today! >http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktr >k >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
48 messages has been excluded from this view by a project administrator.
