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...> - 2012-12-03 20:10: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>Querying dates from Virtuoso</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>2012-12-03 08:09 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Per my previous comment this was a Json.Net perculiarity with it auto-identifying the valid string wrapped date as a special token type causing issues for the parser. This has been fixed in default</p>
<p>
</p>
<p>
For future reference code is in Mercurial and available at BitBucket - http://bitbucket.org/dotnetrdf/dotnetrdf so you can always fork and send us a pull request if you have a patch for an issue. </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=290" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=290</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...> - 2012-12-03 20:02:20
|
<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>Querying dates from Virtuoso</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Dimitri</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2012-12-03 08:01 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Many thanks! In any case my little hack has solved my problem for now. But I hope that the info helps and, also, it will be cooler when we can just use the library directly from Nuget :)</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=290" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=290</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...> - 2012-12-03 19:39:49
|
<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>dotNetRDF.ClientProfile.Net35 doesn't build in Release</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "New" to "Confirmed"
</li>
<li>Milestone changed from "Unscheduled" to "0.9.0 RC 4"
</li>
<li>Assigned to changed from "none" to "Tomasz Pluskiewicz"
</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=291" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=291</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...> - 2012-12-03 19:39:31
|
<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>dotNetRDF.ClientProfile.Net35 doesn't build in Release</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>2012-12-03 07:38 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Yes, any compilation constants defined for the Debug configuration (bar DEBUG and TRACE) should be replicated to the Release configuration</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=291" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=291</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...> - 2012-12-03 19:36:15
|
<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>Querying dates from Virtuoso</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>2012-12-03 07:35 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I'm not so sure this is a Virtuoso problem on further investigation, it may actually be a Json.Net perculiarity instead</p>
<p>
Raw dates are not allowed in JSON and would be encoded in strings (thus meeting the SPARQL JSON spec) so it looks like it may be the case that Json.Net is simply being smart and identifying certain strings as belonging to certain types. I will write up a few test cases to confirm this and then put in place appropriate fixes.</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=290" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=290</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...> - 2012-12-03 18:55:09
|
<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>dotNetRDF.ClientProfile.Net35 doesn't build in Release</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Tomasz Pluskiewicz</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unscheduled</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Build, Release and Testing</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 have noticed that dotNetRDF.ClientProfile.Net35 won't build in Release configuration. It fails at the usages of HtmlTextWriter, where it is missing in the System.Web.IO. </p>
<p>
It seems that missing is the NO_WEB compile constant. Is that all there is to it?</p>
<p>
Tom</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=291" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=291</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...> - 2012-12-03 18:49:35
|
<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>Querying dates from Virtuoso</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Dimitri</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2012-12-03 06:48 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Hi Rob,</p>
<p>
Indeed maybe Virtuoso does not conform to the specification. I have tested dotNetRDF with 4store as well, and, when doing so, I didn't encounter this issue. So I wasn't sure whether I should report a bug or a suggested improvement. All I have noticed is that the query works without any problems if this little json token peculiarity of Virtuoso is "excused" :)</p>
<p>
Best regards,</p>
<p>
Dimitri</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=290" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=290</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...> - 2012-12-03 18:03:11
|
<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>Querying dates from Virtuoso</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>2012-12-03 06:02 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I'm not sure if this is actually a bug or whether Virtuoso is producing invalid SPARQL JSON, the <a href="http://www.w3.org/TR/sparql11-results-json/">specification</a> shows all the data encoding RDF terms as being enclosed in JSON strings.</p>
<p>
However the specification does not say anything explicit about whether using native JSON terms like dates, integers, booleans etc is acceptable. I will investigate further and get back to you on this</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=290" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=290</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...> - 2012-12-03 18:00:51
|
<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>Querying dates from Virtuoso</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Milestone changed from "none" to "0.9.0 RC 4"
</li>
<li>Affected Milestone changed from "none" to "0.8.2 RC 3"
</li>
<li>Assigned to changed from "none" 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=290" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=290</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...> - 2012-12-01 11:31:42
|
<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>Querying dates from Virtuoso</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Dimitri</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>none</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Parsing</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 everyone,</p>
<p>
I have had some trouble querying dates using VDS.RDF.Query.SparqlRemoteEndpoint and connecting to a Virtuoso server.</p>
<p>
The following code</p>
<p>
</p>
<div>
<em>var endp = new VDS.RDF.Query.SparqlRemoteEndpoint(new Uri("http://localhost:8890/sparql"));</em></div>
<div>
</div>
<div>
<em> var dateResult = endp.QueryWithResultSet(@"</em></div>
<div>
<em> prefix res: <http://localhost/rdf/resource/></em></div>
<div>
<em> prefix onto: <http://localhost/rdf/ontology#></em></div>
<div>
<em> select str(?date) as ?date1 where {res:AvoidTheBugListed onto:hasDate ?date}</em></div>
<div>
<em> ");</em></div>
<div>
</div>
<div>
<em> var datefound = DateTime.Parse(dateResult[0][0].ToString());</em></div>
<div>
</div>
<div>
causes the following error:</div>
<div>
</div>
<div>
<div>
<em>VDS.RDF.Parsing.RdfParseException : [Line 4 Column 73] Date</em></div>
<div>
<em>Unexpected Token 'Date' encountered, expected a Property Value describing one of the properties of an Variable Binding</em></div>
<div>
<em> at VDS.RDF.Parsing.SparqlJsonParser.Error(SparqlJsonParserContext context, String message) in SparqlJsonParser.cs: line 754</em></div>
<div>
<em> at VDS.RDF.Parsing.SparqlJsonParser.ParseBoundVariable(SparqlJsonParserContext context, String var, SparqlResult r) in SparqlJsonParser.cs: line 589</em></div>
<div>
<em> at VDS.RDF.Parsing.SparqlJsonParser.ParseBinding(SparqlJsonParserContext context) in SparqlJsonParser.cs: line 531</em></div>
<div>
<em> at VDS.RDF.Parsing.SparqlJsonParser.ParseBindings(SparqlJsonParserContext context) in SparqlJsonParser.cs: line 498</em></div>
<div>
<em> at VDS.RDF.Parsing.SparqlJsonParser.ParseResults(SparqlJsonParserContext context) in SparqlJsonParser.cs: line 456</em></div>
<div>
<em> at VDS.RDF.Parsing.SparqlJsonParser.ParseBody(SparqlJsonParserContext context) in SparqlJsonParser.cs: line 381</em></div>
<div>
<em> at VDS.RDF.Parsing.SparqlJsonParser.ParseResultSetObject(SparqlJsonParserContext context) in SparqlJsonParser.cs: line 195</em></div>
<div>
<em> at VDS.RDF.Parsing.SparqlJsonParser.Parse(TextReader input, ISparqlResultsHandler handler) in SparqlJsonParser.cs: line 146</em></div>
<div>
<em> at VDS.RDF.Parsing.SparqlJsonParser.Load(ISparqlResultsHandler handler, TextReader input) in SparqlJsonParser.cs: line 116</em></div>
<div>
<em> at VDS.RDF.Parsing.SparqlJsonParser.Load(ISparqlResultsHandler handler, StreamReader input) in SparqlJsonParser.cs: line 125</em></div>
<div>
<em> at VDS.RDF.Query.SparqlRemoteEndpoint.QueryWithResultSet(ISparqlResultsHandler handler, String sparqlQuery) in SparqlRemoteEndpoint.cs: line 337</em></div>
<div>
<em> at VDS.RDF.Query.SparqlRemoteEndpoint.QueryWithResultSet(String sparqlQuery) in SparqlRemoteEndpoint.cs: line 293</em></div>
<div>
<em> at DotNetRdfDatesVirtuoso.DateTests.SelectDate() in DateTests.cs: line 18</em></div>
</div>
<p>
</p>
<p>
</p>
<p>
On my local installation, I have managed to circumvent this by changing the dotNetRDF library source code.</p>
<p>
In the file dotNetRdf/Parsing/SparqlJsonParser.cs, line 587 I have changed the following code:</p>
<p>
</p>
<div>
<em>if (context.Input.TokenType != JsonToken.String)</em></div>
<div>
<em>{</em></div>
<div>
<em> throw Error(context, "Unexpected Token '" + context.Input.TokenType.ToString() + "' encountered, expected a Property Value describing one of the properties of an Variable Binding");</em></div>
<div>
<em>}</em></div>
<div>
</div>
<div>
to this</div>
<div>
</div>
<div>
<div>
<em>if (context.Input.TokenType != JsonToken.String && context.Input.TokenType != JsonToken.Date)</em></div>
<div>
<em>{</em></div>
<div>
<em> throw Error(context, "Unexpected Token '" + context.Input.TokenType.ToString() + "' encountered, expected a Property Value describing one of the properties of an Variable Binding");</em></div>
<div>
<em>}</em></div>
<div>
</div>
<div>
and everything seems to work fine.</div>
<div>
</div>
<div>
The version of the dotNetRdf library I have performed the change on is 0.7.2</div>
<div>
</div>
<div>
I have made the same test on 0.8.2 and the same problem arises, so the fix should work there to.</div>
<div>
</div>
<div>
The Virtuoso version I am using is 06.01.3127</div>
<div>
</div>
<div>
If it would be best for the project, I could perform this sort of improvements in a branch in the future and ask for your approval but I am not sure if my fix is even correct at this point (it just works for me) :)</div>
<div>
</div>
<div>
Best regards,</div>
<div>
</div>
<div>
Dimitri</div>
<div>
</div>
</div>
<p>
</p>
<p>
</p>
<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=290" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=290</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...> - 2012-11-30 17:13:25
|
Hi Rob I have just commited a quick fix to the main repo. I added a new test file and this time added the licence header manually. What is the way to do that automatically? Thanks, Tom |
|
From: <tr...@do...> - 2012-11-26 18:04:53
|
<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>Update SPARQL Endpoint implementations to pass all the SPARQL 1.1 Protocol Tests</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 "none" 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=289" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=289</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...> - 2012-11-26 18:04:45
|
<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>Update SPARQL Endpoint implementations to pass all the SPARQL 1.1 Protocol Tests</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>2012-11-26 06:03 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Marking as Fixed, while there are some tests still failing these all appear to pertain to sequences of actions not being properly reflected which I suspect is a bug elsewhere or with the test runner (since for a couple of the sequences executing manually yields the correct result)</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=289" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=289</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...> - 2012-11-19 21:24:02
|
Thanks Rob
1. It seems that I have most of SPARQL 1.0 already and a portion of
SPARQL 1.1 in place. Out of what you have listed I'm currently missing
REGEX, ORDER BY and constructors.
2. I have just thought that maybe we could split the methods over two
namespaces so that it is possible to choose which syntax a user wants.
For example the current namespace VDS.RDF.Query.Builder will contain
only SPARQL 1.0 and to get the SPARQL 1.1 one would include
VDS.RDF.Query.Builder.Sparql11. Or maybe this isn't necessary?
3. I'm also struggling with the expression types for string methods.
Until recently it seems to have worked fine but the problem is with
string/simple/plain literals. Today I have decided to remove the
SimpleLiteralExpression class because it doesn't play well with the
typed string expression. Instead I use simpy LiteralExpression which
is also base for other typed literals. This means that it will be
possible to call for example
Builder.LangMatches( Builder.Constant(10), "fr")
which doesn't make sense but I can't figure a good way to make the API
strict enough but not too complicated. The expression builder is
already quite grown.
4. Another thing I have been considering the API change for some
expression type, most notably for string functions. With the exception
of IN function all methods are static extensions of ExpressionBuilder
class. IN on the other hand is invoked on any other expression.
However I wonder whether it would be more user-friendly if more of the
functions would be built in context of expressions and not expression
builder (which is unused in implementation in most of the cases
anyway). Examples could be LANG or STRLEN. So instead of
Builder.Lang(variable) or Buidler.StrLen(variable)
the user would call simply
variable.GetLang() or variable.GetStrLen()
What do you think?
5. Also I'm not sure is for the best are quite numerous overloads
especially for string functions. I didn't have an issue with that
until I implemented SUBSTR some time last week, which has two or three
parameters. The first can be variable or string expression, and the
second and third can be variable, int expression or simply integers.
This gives a total of 18 overloads and I start to think it's a code
smell. Should remove the ones which take int parameters?
6. Lastly the I would like to ask you about constants. How much does
it matter in SPARQL whether a literal is typed or not. I mean "str" vs
"str"^^xsd:string or 5 vs "5"^^xsd:int. In any what is you opinion,
which should be created by the expression builder? When user calls
Builder.Constant("str"), Builder.Constant(5) or
Builder.Constant(DateTime.Now)?
On Sat, Nov 17, 2012 at 12:18 AM, Rob Vesse <rv...@do...> wrote:
> Here's a quick guide
>
> SPARQL 1.0
> - Graph Patterns - OPTIONAL, GRAPH, UNION
> - FILTER
> - Expressions - BOUND, ISIRI, ISBLANK, ISLITERAL, STR, LANG, DATATYPE, ||,
> &&, =, SAMETERM, LANGMATCHES, REGEX, >, >=, <, <=, XPath constructors
> (xsd:boolean, xsd:integer etc)
> - Solution Modifiers - ORDER BY, LIMIT, OFFSET
>
> SPARQL 1.1 - As SPARQL 1.0 plus the following
> - Graph Patterns - Sub-SELECT, MINUS, SERVICE, VALUES, EXISTS and NOT
> EXISTS (these last two are in FILTER only)
> - Expressions - IF, COALESCE, NOT EXISTS, EXISTS, IN, NOT IN, ISNUMERIC,
> IRI, BNODE, STRDT, STRLANG, UUID, STRUUID, STRLEN, SUBSTR, UCASE, LCASE,
> STRSTARTS, STRENDS, CONTAINS, STRBEFORE, STRAFTER, ENCODE_FOR_URI, CONCAT,
> REPLACE, ABS, ROUND, CEIL, FLOOR, RAND, NOW, YEAR, MONTH, DAY, HOURS,
> MINUTES, SECONDS, TIMEZONE, TZ, MD5, SHA1, SHA256, SHA384, SHA512
> - Solution Modifiers - GROUP BY, HAVING, VALUES
> - Aggregate Expressions - AVG, COUNT, GROUP_CONCAT, MAX, MIN, SAMPLE
>
> So clearly SPARQL 1.0 is much smaller
>
> Hope this helps,
>
> Rob
>
> On 11/15/12 2:39 AM, "Tomasz Pluskiewicz" <tom...@gm...>
> wrote:
>
>>Can do. Can you point me to a concise comparison between SPARQL 1.0 and
>>1.1.
>>
>>Or maybe you could quickly draft what you think should come first and
>>what cant wait?
>>
>>Thanks,
>>Tom
>>
>>On Thu, Nov 15, 2012 at 1:50 AM, Rob Vesse <rv...@do...> wrote:
>>> May have spoken too soon on the 0.8.0 release, the proposed
>>> recommendations for SPARQL 1.1 just came out so I'm going to try and get
>>> some final compatibility and bug fixing for this done before the next
>>> release.
>>>
>>> On the fluent query front maybe it would be sufficient to have a partial
>>> API in place for 0.8.0. By partial I mean something that supported the
>>> major constructs of the language (WHERE, OPTIONAL, GRAPH, UNION,
>>>SERVICE,
>>> FILTER etc) with a limited set of expressions supported. Something that
>>> just covered the SPARQL 1.0 operators would be sufficient and we can
>>>flesh
>>> out to the full SPARQL 1.1 set in later releases.
>>>
>>> How does this sound?
>>>
>>> Rob
>>>
>>> On 11/11/12 9:53 AM, "Tomasz Pluskiewicz" <tom...@gm...>
>>> wrote:
>>>
>>>>I don't mind an earlier release.
>>>>
>>>>Regarding the Fluent API I think we could get it out in 8.1 or so. At
>>>>this point maybe it will be good to define some kind of a road map
>>>>internally. SPARQL has many features and it is possible to implement
>>>>some in the first go and add more later on. I would be good to decide
>>>>what should be delivered at first. As we all know time is limited and
>>>>I'm working hard to get the code thoroughly tested. Especially in the
>>>>arithmetic and logical operators where there is a multitude of
>>>>possible combinations and each one needs a operator overload for the
>>>>API to be complete and most user-friendly.
>>>>
>>>>If you haven't noticed, I am maintaining a documentation of the API's
>>>>features on a wiki [1]. If you guys could find some spare time to have
>>>>a look at it and maybe offer suggestions that would be great.
>>>>
>>>>Thanks,
>>>>Tom
>>>>
>>>>[1] https://bitbucket.org/romanticweb/dotnetrdf/wiki/
>>>>
>>>>On Fri, Nov 9, 2012 at 8:06 PM, Rob Vesse <rv...@do...> wrote:
>>>>> Hey All
>>>>>
>>>>> Would anyone object if I went ahead and made the 0.8.0 release
>>>>>sometime
>>>>>next
>>>>> week?
>>>>>
>>>>> There's a whole bunch of bug fixes in there, updates to SPARQL 1.1
>>>>> compliance and general improvements to SPARQL implementation plus
>>>>> significant fixes and updates to the Query.FullText library.
>>>>>
>>>>> I had originally thought that we might get the Fluent Query API in
>>>>>this
>>>>> release but looking at what Tom's got so far (which is great btw) it's
>>>>> clearly a much bigger lift than I first thought. I'd rather push that
>>>>>to
>>>>> unscheduled and have it be merged in as and when Tom thinks it's ready
>>>>> rather than holding back a useful (and primarily bug fix) release.
>>>>>
>>>>> Any other thoughts/objections?
>>>>>
>>>>> Rob
>>>>>
>>>>>
>>>>>-----------------------------------------------------------------------
>>>>>--
>>>>>-----
>>>>> Everyone hates slow websites. So do we.
>>>>> Make your web apps faster with AppDynamics
>>>>> Download AppDynamics Lite for free today:
>>>>> http://p.sf.net/sfu/appdyn_d2d_nov
>>>>> _______________________________________________
>>>>> dotNetRDF-develop mailing list
>>>>> dot...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>>>>
>>>>
>>>>------------------------------------------------------------------------
>>>>--
>>>>----
>>>>Everyone hates slow websites. So do we.
>>>>Make your web apps faster with AppDynamics
>>>>Download AppDynamics Lite for free today:
>>>>http://p.sf.net/sfu/appdyn_d2d_nov
>>>>_______________________________________________
>>>>dotNetRDF-develop mailing list
>>>>dot...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>>
>>>
>>>
>>>
>>>
>>>
>>>-------------------------------------------------------------------------
>>>-----
>>> Monitor your physical, virtual and cloud infrastructure from a single
>>> web console. Get in-depth insight into apps, servers, databases, vmware,
>>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>>> Pricing starts from $795 for 25 servers or applications!
>>> http://p.sf.net/sfu/zoho_dev2dev_nov
>>> _______________________________________________
>>> dotNetRDF-develop mailing list
>>> dot...@li...
>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>
>>--------------------------------------------------------------------------
>>----
>>Monitor your physical, virtual and cloud infrastructure from a single
>>web console. Get in-depth insight into apps, servers, databases, vmware,
>>SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>>Pricing starts from $795 for 25 servers or applications!
>>http://p.sf.net/sfu/zoho_dev2dev_nov
>>_______________________________________________
>>dotNetRDF-develop mailing list
>>dot...@li...
>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
>
>
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
|
|
From: Steve . <mo...@ho...> - 2012-11-18 19:23:45
|
I have an ontology on Knoodl that I need to integrate into an ASP.Net MVC4 web application using ReadAsync method of HttpClient ... (webApi using .Net 4.5) How to fix the exception that I get ?? No MediaTypeFormatter is available to read an object of type 'JArray' from content with media type 'application/sparql-results+json Pointers to how to add a custom MediaTypeFormatter to my solution, please ... or any other way to get this done ?? Hate to have to resort to XML when Json is an option. Articles like this http://byterot.blogspot.com/2012/04/aspnet-web-api-series-part-5.html are helpful, but a bit confusing to me. Thanks,Steve |
|
From: Rob V. <rv...@do...> - 2012-11-16 23:19:17
|
Here's a quick guide SPARQL 1.0 - Graph Patterns - OPTIONAL, GRAPH, UNION - FILTER - Expressions - BOUND, ISIRI, ISBLANK, ISLITERAL, STR, LANG, DATATYPE, ||, &&, =, SAMETERM, LANGMATCHES, REGEX, >, >=, <, <=, XPath constructors (xsd:boolean, xsd:integer etc) - Solution Modifiers - ORDER BY, LIMIT, OFFSET SPARQL 1.1 - As SPARQL 1.0 plus the following - Graph Patterns - Sub-SELECT, MINUS, SERVICE, VALUES, EXISTS and NOT EXISTS (these last two are in FILTER only) - Expressions - IF, COALESCE, NOT EXISTS, EXISTS, IN, NOT IN, ISNUMERIC, IRI, BNODE, STRDT, STRLANG, UUID, STRUUID, STRLEN, SUBSTR, UCASE, LCASE, STRSTARTS, STRENDS, CONTAINS, STRBEFORE, STRAFTER, ENCODE_FOR_URI, CONCAT, REPLACE, ABS, ROUND, CEIL, FLOOR, RAND, NOW, YEAR, MONTH, DAY, HOURS, MINUTES, SECONDS, TIMEZONE, TZ, MD5, SHA1, SHA256, SHA384, SHA512 - Solution Modifiers - GROUP BY, HAVING, VALUES - Aggregate Expressions - AVG, COUNT, GROUP_CONCAT, MAX, MIN, SAMPLE So clearly SPARQL 1.0 is much smaller Hope this helps, Rob On 11/15/12 2:39 AM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Can do. Can you point me to a concise comparison between SPARQL 1.0 and >1.1. > >Or maybe you could quickly draft what you think should come first and >what cant wait? > >Thanks, >Tom > >On Thu, Nov 15, 2012 at 1:50 AM, Rob Vesse <rv...@do...> wrote: >> May have spoken too soon on the 0.8.0 release, the proposed >> recommendations for SPARQL 1.1 just came out so I'm going to try and get >> some final compatibility and bug fixing for this done before the next >> release. >> >> On the fluent query front maybe it would be sufficient to have a partial >> API in place for 0.8.0. By partial I mean something that supported the >> major constructs of the language (WHERE, OPTIONAL, GRAPH, UNION, >>SERVICE, >> FILTER etc) with a limited set of expressions supported. Something that >> just covered the SPARQL 1.0 operators would be sufficient and we can >>flesh >> out to the full SPARQL 1.1 set in later releases. >> >> How does this sound? >> >> Rob >> >> On 11/11/12 9:53 AM, "Tomasz Pluskiewicz" <tom...@gm...> >> wrote: >> >>>I don't mind an earlier release. >>> >>>Regarding the Fluent API I think we could get it out in 8.1 or so. At >>>this point maybe it will be good to define some kind of a road map >>>internally. SPARQL has many features and it is possible to implement >>>some in the first go and add more later on. I would be good to decide >>>what should be delivered at first. As we all know time is limited and >>>I'm working hard to get the code thoroughly tested. Especially in the >>>arithmetic and logical operators where there is a multitude of >>>possible combinations and each one needs a operator overload for the >>>API to be complete and most user-friendly. >>> >>>If you haven't noticed, I am maintaining a documentation of the API's >>>features on a wiki [1]. If you guys could find some spare time to have >>>a look at it and maybe offer suggestions that would be great. >>> >>>Thanks, >>>Tom >>> >>>[1] https://bitbucket.org/romanticweb/dotnetrdf/wiki/ >>> >>>On Fri, Nov 9, 2012 at 8:06 PM, Rob Vesse <rv...@do...> wrote: >>>> Hey All >>>> >>>> Would anyone object if I went ahead and made the 0.8.0 release >>>>sometime >>>>next >>>> week? >>>> >>>> There's a whole bunch of bug fixes in there, updates to SPARQL 1.1 >>>> compliance and general improvements to SPARQL implementation plus >>>> significant fixes and updates to the Query.FullText library. >>>> >>>> I had originally thought that we might get the Fluent Query API in >>>>this >>>> release but looking at what Tom's got so far (which is great btw) it's >>>> clearly a much bigger lift than I first thought. I'd rather push that >>>>to >>>> unscheduled and have it be merged in as and when Tom thinks it's ready >>>> rather than holding back a useful (and primarily bug fix) release. >>>> >>>> Any other thoughts/objections? >>>> >>>> Rob >>>> >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>>----- >>>> Everyone hates slow websites. So do we. >>>> Make your web apps faster with AppDynamics >>>> Download AppDynamics Lite for free today: >>>> http://p.sf.net/sfu/appdyn_d2d_nov >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>Everyone hates slow websites. So do we. >>>Make your web apps faster with AppDynamics >>>Download AppDynamics Lite for free today: >>>http://p.sf.net/sfu/appdyn_d2d_nov >>>_______________________________________________ >>>dotNetRDF-develop mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >-------------------------------------------------------------------------- >---- >Monitor your physical, virtual and cloud infrastructure from a single >web console. Get in-depth insight into apps, servers, databases, vmware, >SAP, cloud infrastructure, etc. Download 30-day Free Trial. >Pricing starts from $795 for 25 servers or applications! >http://p.sf.net/sfu/zoho_dev2dev_nov >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: <tr...@do...> - 2012-11-15 23:00:57
|
<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>Update SPARQL Endpoint implementations to pass all the SPARQL 1.1 Protocol Tests</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>2012-11-15 10:59 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Latest fixes improve score to 31/35</p>
<p>
All remaining failures relate to operation sequences not giving the expected query result</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=289" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=289</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...> - 2012-11-15 10:39:57
|
Can do. Can you point me to a concise comparison between SPARQL 1.0 and 1.1. Or maybe you could quickly draft what you think should come first and what cant wait? Thanks, Tom On Thu, Nov 15, 2012 at 1:50 AM, Rob Vesse <rv...@do...> wrote: > May have spoken too soon on the 0.8.0 release, the proposed > recommendations for SPARQL 1.1 just came out so I'm going to try and get > some final compatibility and bug fixing for this done before the next > release. > > On the fluent query front maybe it would be sufficient to have a partial > API in place for 0.8.0. By partial I mean something that supported the > major constructs of the language (WHERE, OPTIONAL, GRAPH, UNION, SERVICE, > FILTER etc) with a limited set of expressions supported. Something that > just covered the SPARQL 1.0 operators would be sufficient and we can flesh > out to the full SPARQL 1.1 set in later releases. > > How does this sound? > > Rob > > On 11/11/12 9:53 AM, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>I don't mind an earlier release. >> >>Regarding the Fluent API I think we could get it out in 8.1 or so. At >>this point maybe it will be good to define some kind of a road map >>internally. SPARQL has many features and it is possible to implement >>some in the first go and add more later on. I would be good to decide >>what should be delivered at first. As we all know time is limited and >>I'm working hard to get the code thoroughly tested. Especially in the >>arithmetic and logical operators where there is a multitude of >>possible combinations and each one needs a operator overload for the >>API to be complete and most user-friendly. >> >>If you haven't noticed, I am maintaining a documentation of the API's >>features on a wiki [1]. If you guys could find some spare time to have >>a look at it and maybe offer suggestions that would be great. >> >>Thanks, >>Tom >> >>[1] https://bitbucket.org/romanticweb/dotnetrdf/wiki/ >> >>On Fri, Nov 9, 2012 at 8:06 PM, Rob Vesse <rv...@do...> wrote: >>> Hey All >>> >>> Would anyone object if I went ahead and made the 0.8.0 release sometime >>>next >>> week? >>> >>> There's a whole bunch of bug fixes in there, updates to SPARQL 1.1 >>> compliance and general improvements to SPARQL implementation plus >>> significant fixes and updates to the Query.FullText library. >>> >>> I had originally thought that we might get the Fluent Query API in this >>> release but looking at what Tom's got so far (which is great btw) it's >>> clearly a much bigger lift than I first thought. I'd rather push that >>>to >>> unscheduled and have it be merged in as and when Tom thinks it's ready >>> rather than holding back a useful (and primarily bug fix) release. >>> >>> Any other thoughts/objections? >>> >>> Rob >>> >>> >>>------------------------------------------------------------------------- >>>----- >>> Everyone hates slow websites. So do we. >>> Make your web apps faster with AppDynamics >>> Download AppDynamics Lite for free today: >>> http://p.sf.net/sfu/appdyn_d2d_nov >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >> >>-------------------------------------------------------------------------- >>---- >>Everyone hates slow websites. So do we. >>Make your web apps faster with AppDynamics >>Download AppDynamics Lite for free today: >>http://p.sf.net/sfu/appdyn_d2d_nov >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2012-11-15 00:51:12
|
May have spoken too soon on the 0.8.0 release, the proposed recommendations for SPARQL 1.1 just came out so I'm going to try and get some final compatibility and bug fixing for this done before the next release. On the fluent query front maybe it would be sufficient to have a partial API in place for 0.8.0. By partial I mean something that supported the major constructs of the language (WHERE, OPTIONAL, GRAPH, UNION, SERVICE, FILTER etc) with a limited set of expressions supported. Something that just covered the SPARQL 1.0 operators would be sufficient and we can flesh out to the full SPARQL 1.1 set in later releases. How does this sound? Rob On 11/11/12 9:53 AM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >I don't mind an earlier release. > >Regarding the Fluent API I think we could get it out in 8.1 or so. At >this point maybe it will be good to define some kind of a road map >internally. SPARQL has many features and it is possible to implement >some in the first go and add more later on. I would be good to decide >what should be delivered at first. As we all know time is limited and >I'm working hard to get the code thoroughly tested. Especially in the >arithmetic and logical operators where there is a multitude of >possible combinations and each one needs a operator overload for the >API to be complete and most user-friendly. > >If you haven't noticed, I am maintaining a documentation of the API's >features on a wiki [1]. If you guys could find some spare time to have >a look at it and maybe offer suggestions that would be great. > >Thanks, >Tom > >[1] https://bitbucket.org/romanticweb/dotnetrdf/wiki/ > >On Fri, Nov 9, 2012 at 8:06 PM, Rob Vesse <rv...@do...> wrote: >> Hey All >> >> Would anyone object if I went ahead and made the 0.8.0 release sometime >>next >> week? >> >> There's a whole bunch of bug fixes in there, updates to SPARQL 1.1 >> compliance and general improvements to SPARQL implementation plus >> significant fixes and updates to the Query.FullText library. >> >> I had originally thought that we might get the Fluent Query API in this >> release but looking at what Tom's got so far (which is great btw) it's >> clearly a much bigger lift than I first thought. I'd rather push that >>to >> unscheduled and have it be merged in as and when Tom thinks it's ready >> rather than holding back a useful (and primarily bug fix) release. >> >> Any other thoughts/objections? >> >> Rob >> >> >>------------------------------------------------------------------------- >>----- >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_nov >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >-------------------------------------------------------------------------- >---- >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics >Download AppDynamics Lite for free today: >http://p.sf.net/sfu/appdyn_d2d_nov >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2012-11-15 00:49:03
|
Ok I have done that Did run into some trouble with the fact that we had both separately closed one of your bug fix branches in our repos so I had to strip your branch close from my repo before pushing changes but seems to have worked fine Rob On 11/12/12 12:27 PM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Don't think so. > >The only way I think of is that you manually pull from >https://bitbucket.org/romanticweb/dotnetrdf and push to the main repo. > >Tom > >On Mon, Nov 12, 2012 at 8:43 PM, Rob Vesse <rv...@do...> wrote: >> If you're having problems with the larger pull request can you send me a >> pull request with just that one change set? >> >> Rob >> >> On 11/9/12 11:54 AM, "Tomasz Pluskiewicz" <tom...@gm...> >> wrote: >> >>>Great stuff. I just have a little fix. It is included in the pull >>>request I've just created. >>> >>>Tom >>> >>>On Wed, Nov 7, 2012 at 7:24 PM, Rob Vesse <rv...@do...> wrote: >>>> Hey All >>>> >>>> I've just completed a refactoring of how we manage dependencies in the >>>> project. All external dependencies are now obtained via NuGet and >>>>there is >>>> no longer a Dependencies folder checked into source control. >>>> >>>> I've also changed how we do the alternative builds of the libraries so >>>>the >>>> main solution now has projects included to build the libraries for all >>>> supported platforms. The alternative builds get synced up with the >>>>main >>>> build by a pre-build event so when you add/remove something to/from >>>>the >>>>main >>>> build on the next compile of the alternative builds the change(s) will >>>>be >>>> automatically pulled in for you (though VS will make you reload the >>>> project). >>>> >>>> Note this does however mean that you will now need to have >>>>Silverlight 4 >>>> Tools for VS and Windows Phone 7.1 Tools for VS installed to build the >>>> solution correctly. >>>> >>>> Hopefully this makes building things much easier for people since all >>>>the >>>> libraries can now be built directly from Visual Studio >>>> >>>> Rob >>>> >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>>----- >>>> LogMeIn Central: Instant, anywhere, Remote PC access and management. >>>> Stay in control, update software, and manage PCs from one command >>>>center >>>> Diagnose problems and improve visibility into emerging IT issues >>>> Automate, monitor and manage. Do more in less time with Central >>>> http://p.sf.net/sfu/logmein12331_d2d >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>Everyone hates slow websites. So do we. >>>Make your web apps faster with AppDynamics >>>Download AppDynamics Lite for free today: >>>http://p.sf.net/sfu/appdyn_d2d_nov >>>_______________________________________________ >>>dotNetRDF-develop mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >-------------------------------------------------------------------------- >---- >Monitor your physical, virtual and cloud infrastructure from a single >web console. Get in-depth insight into apps, servers, databases, vmware, >SAP, cloud infrastructure, etc. Download 30-day Free Trial. >Pricing starts from $795 for 25 servers or applications! >http://p.sf.net/sfu/zoho_dev2dev_nov >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2012-11-12 20:28:13
|
Don't think so. The only way I think of is that you manually pull from https://bitbucket.org/romanticweb/dotnetrdf and push to the main repo. Tom On Mon, Nov 12, 2012 at 8:43 PM, Rob Vesse <rv...@do...> wrote: > If you're having problems with the larger pull request can you send me a > pull request with just that one change set? > > Rob > > On 11/9/12 11:54 AM, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>Great stuff. I just have a little fix. It is included in the pull >>request I've just created. >> >>Tom >> >>On Wed, Nov 7, 2012 at 7:24 PM, Rob Vesse <rv...@do...> wrote: >>> Hey All >>> >>> I've just completed a refactoring of how we manage dependencies in the >>> project. All external dependencies are now obtained via NuGet and >>>there is >>> no longer a Dependencies folder checked into source control. >>> >>> I've also changed how we do the alternative builds of the libraries so >>>the >>> main solution now has projects included to build the libraries for all >>> supported platforms. The alternative builds get synced up with the main >>> build by a pre-build event so when you add/remove something to/from the >>>main >>> build on the next compile of the alternative builds the change(s) will >>>be >>> automatically pulled in for you (though VS will make you reload the >>> project). >>> >>> Note this does however mean that you will now need to have Silverlight 4 >>> Tools for VS and Windows Phone 7.1 Tools for VS installed to build the >>> solution correctly. >>> >>> Hopefully this makes building things much easier for people since all >>>the >>> libraries can now be built directly from Visual Studio >>> >>> Rob >>> >>> >>>------------------------------------------------------------------------- >>>----- >>> LogMeIn Central: Instant, anywhere, Remote PC access and management. >>> Stay in control, update software, and manage PCs from one command center >>> Diagnose problems and improve visibility into emerging IT issues >>> Automate, monitor and manage. Do more in less time with Central >>> http://p.sf.net/sfu/logmein12331_d2d >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >> >>-------------------------------------------------------------------------- >>---- >>Everyone hates slow websites. So do we. >>Make your web apps faster with AppDynamics >>Download AppDynamics Lite for free today: >>http://p.sf.net/sfu/appdyn_d2d_nov >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2012-11-12 19:44:03
|
If you're having problems with the larger pull request can you send me a pull request with just that one change set? Rob On 11/9/12 11:54 AM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Great stuff. I just have a little fix. It is included in the pull >request I've just created. > >Tom > >On Wed, Nov 7, 2012 at 7:24 PM, Rob Vesse <rv...@do...> wrote: >> Hey All >> >> I've just completed a refactoring of how we manage dependencies in the >> project. All external dependencies are now obtained via NuGet and >>there is >> no longer a Dependencies folder checked into source control. >> >> I've also changed how we do the alternative builds of the libraries so >>the >> main solution now has projects included to build the libraries for all >> supported platforms. The alternative builds get synced up with the main >> build by a pre-build event so when you add/remove something to/from the >>main >> build on the next compile of the alternative builds the change(s) will >>be >> automatically pulled in for you (though VS will make you reload the >> project). >> >> Note this does however mean that you will now need to have Silverlight 4 >> Tools for VS and Windows Phone 7.1 Tools for VS installed to build the >> solution correctly. >> >> Hopefully this makes building things much easier for people since all >>the >> libraries can now be built directly from Visual Studio >> >> Rob >> >> >>------------------------------------------------------------------------- >>----- >> LogMeIn Central: Instant, anywhere, Remote PC access and management. >> Stay in control, update software, and manage PCs from one command center >> Diagnose problems and improve visibility into emerging IT issues >> Automate, monitor and manage. Do more in less time with Central >> http://p.sf.net/sfu/logmein12331_d2d >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >-------------------------------------------------------------------------- >---- >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics >Download AppDynamics Lite for free today: >http://p.sf.net/sfu/appdyn_d2d_nov >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Yossi C. <yos...@li...> - 2012-11-12 19:29:29
|
MessageHi Rob, I got Hugh Williams reply, indeed a comprehensive one (we will check it ASAP). In any event, thanks a lot for your quick response. Best, Yossi. From: Rob Vesse Sent: Monday, November 12, 2012 7:16 PM To: dotNetRDF Developer Discussion and Feature Request Subject: Re: [dotNetRDF-Develop] VirtuosoManager problem when accessing from client on an IPV6 network Hi Yossi I'm afraid I can't really help you here since this sounds very much like a Virtuoso specific configuration issue rather than an issue with dotNetRDF itself I see you already posted the same question at http://boards.openlinksw.com/phpBB3/viewtopic.php?f=14&t=1204 and it looks like Hugh Williams gave a fairly comprehensive answer on server config issues to check. Also as he points out there is no IPv6 support in the current open source version of Virtuoso in which case you would either have to use IPv4 or an IPv6 proxy to connect. Rob From: COHEN YOSSI <yo...@ra...> Reply-To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: Sunday, November 11, 2012 5:40 AM To: "'dot...@li...'" <dot...@li...> Subject: [dotNetRDF-Develop] VirtuosoManager problem when accessing from client on an IPV6 network Hi, - Connecting to Virtuoso from localhost works like a charm (using dotNetRDF VirtuosoManager). - Trying to access it (e.g., ListGraphs) from a client on another machine on the same intrAnet fails with the message: "An address incompatible with the request protocol was used" followed by the [IPV6] of the machine hosting Virtuoso. Is there a workaround? Am I doing somthing wrong? Best, Yossi Cohen Technical Lead Smart Intelligence Systems ------------------------------------------------------------------------------ This message (including any attachments) issued by RAFAEL- ADVANCED DEFENSE SYSTEMS LTD. (hereinafter "RAFAEL") contains confidential information intended for a specific individual and purpose, may constitute information that is privileged or confidential or otherwise protected from disclosure. If you are not the intended recipient, you should contact us immediately and thereafter delete this message from your system. You are hereby notified that any disclosure, copying, dissemination, distribution or forwarding of this message, or the taking of any action based on it, is strictly prohibited. If you have received this e-mail in error, please notify us immediately by e-mail mailto:la...@ra... and completely delete or destroy any and all electronic or other copies of the original message and any attachments thereof. ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov_______________________________________________ dotNetRDF-develop mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop -------------------------------------------------------------------------------- ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov -------------------------------------------------------------------------------- _______________________________________________ dotNetRDF-develop mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2012-11-12 17:17:32
|
Hi Yossi I'm afraid I can't really help you here since this sounds very much like a Virtuoso specific configuration issue rather than an issue with dotNetRDF itself I see you already posted the same question at http://boards.openlinksw.com/phpBB3/viewtopic.php?f=14&t=1204 and it looks like Hugh Williams gave a fairly comprehensive answer on server config issues to check. Also as he points out there is no IPv6 support in the current open source version of Virtuoso in which case you would either have to use IPv4 or an IPv6 proxy to connect. Rob From: COHEN YOSSI <yo...@ra...> Reply-To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: Sunday, November 11, 2012 5:40 AM To: "'dot...@li...'" <dot...@li...> Subject: [dotNetRDF-Develop] VirtuosoManager problem when accessing from client on an IPV6 network > Message > Hi, > > - Connecting to Virtuoso from localhost works like a charm (using dotNetRDF > VirtuosoManager). > - Trying to access it (e.g., ListGraphs) from a client on another machine on > the same intrAnet fails with the message: > "An address incompatible with the request protocol was used" followed by > the [IPV6] of the machine hosting Virtuoso. > > Is there a workaround? > Am I doing somthing wrong? > > Best, > Yossi Cohen > Technical Lead > Smart Intelligence Systems > > > > This message (including any attachments) issued by RAFAEL- ADVANCED DEFENSE > SYSTEMS LTD. (hereinafter "RAFAEL") contains confidential information intended > for a specific individual and purpose, may constitute information that is > privileged or confidential or otherwise protected from disclosure. If you are > not the intended recipient, you should contact us immediately and thereafter > delete this message from your system. You are hereby notified that any > disclosure, copying, dissemination, distribution or forwarding of this > message, or the taking of any action based on it, is strictly prohibited. If > you have received this e-mail in error, please notify us immediately by e-mail > mailto:la...@ra... and completely delete or destroy any and all > electronic or other copies of the original message and any attachments > thereof. > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. Make your web apps faster with > AppDynamics Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov____________________________________________ > ___ dotNetRDF-develop mailing list dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2012-11-11 17:53:53
|
I don't mind an earlier release. Regarding the Fluent API I think we could get it out in 8.1 or so. At this point maybe it will be good to define some kind of a road map internally. SPARQL has many features and it is possible to implement some in the first go and add more later on. I would be good to decide what should be delivered at first. As we all know time is limited and I'm working hard to get the code thoroughly tested. Especially in the arithmetic and logical operators where there is a multitude of possible combinations and each one needs a operator overload for the API to be complete and most user-friendly. If you haven't noticed, I am maintaining a documentation of the API's features on a wiki [1]. If you guys could find some spare time to have a look at it and maybe offer suggestions that would be great. Thanks, Tom [1] https://bitbucket.org/romanticweb/dotnetrdf/wiki/ On Fri, Nov 9, 2012 at 8:06 PM, Rob Vesse <rv...@do...> wrote: > Hey All > > Would anyone object if I went ahead and made the 0.8.0 release sometime next > week? > > There's a whole bunch of bug fixes in there, updates to SPARQL 1.1 > compliance and general improvements to SPARQL implementation plus > significant fixes and updates to the Query.FullText library. > > I had originally thought that we might get the Fluent Query API in this > release but looking at what Tom's got so far (which is great btw) it's > clearly a much bigger lift than I first thought. I'd rather push that to > unscheduled and have it be merged in as and when Tom thinks it's ready > rather than holding back a useful (and primarily bug fix) release. > > Any other thoughts/objections? > > Rob > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > 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.
