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...> - 2014-04-09 13:35:52
|
<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>Resolve issues with Json.Net dependency</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-04-09 02:35 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Added a blog post about this - <a href="http://www.dotnetrdf.org/blogitem.asp?blogID=81">http://www.dotnetrdf.org/blogitem.asp?blogID=81</a> - and there is a mailing list thread on what .Net profiles we should support going forward - <a href="http://sourceforge.net/p/dotnetrdf/mailman/message/32205903/">http://sourceforge.net/p/dotnetrdf/mailman/message/32205903/</a></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=405" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405</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...> - 2014-04-09 13:26:23
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Resolve issues with Json.Net dependency</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>FHaag</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-04-09 02:25 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
For further reference: I now managed to repair the solution that was temporarily made uncompileable by the broken dependency reference: In the NuGet package management console (available e.g. in the SharpDevelop GUI), I first invoked</p>
<p>
uninstall-package Newtonsoft.Json -force -ProjectName ...</p>
<p>
for each project that uses dotNetRDF (the -force flag is necessary as Newtonsoft.Json is a dependency of dotNetRDF and NuGet will otherwise refuse to remove the package), and then</p>
<p>
install-package Newtonsoft.Json -ProjectName ... -Version 5.0.8</p>
<p>
After this, my solution compiles fine again.</p>
<p>
I am, however, a bit wary of what will happen when I use the NuGet update feature the next time.</p>
<p>
@comment: Certainly, restricting the upper version number is just a workaround, but it is one that prevents users who update their packages from NuGet now from renderng their projects uncompileable.</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=405" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405</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: Rob V. <rv...@do...> - 2014-04-09 13:23:07
|
Hi All So the discussions in the last week or two about issues with NuGet dependency conflicts involving Json.Net highlights that our choice of .Net profiles is somewhat behind the times. The Json.Net folks have moved to only supporting standard .Net plus PCL I.e. they¹ve dropped Windows Phone and Silverlight specific builds The problem for us is this means we can¹t upgrade dependencies for our Windows Phone and Silverlight builds so first question is should we drop those builds entirely? Particularly since we¹re targeting deprecated versions of those platforms (Windows Phone 7) in some cases. The next problem is that our PCL build targets an older PCL profile that no longer aligns with Json.Net so we can¹t upgrade dependencies for that build either currently. So the second question is should we update our PCL profile to align with more recent profiles? For reference the current Json.Net builds support the following PCL profiles: * portable-net40+sl5+wp80+win8+monotouch+monoandroid * portable-net45+wp80+win8 Would there be any objections to moving our PCL targets to align with these? Another longer term point, on the 1.9 branch I¹m already working on modularising the code so some of the new modules will no longer need to be Full Profile since they won¹t need anything not in Client Profile. Therefore I¹m also thinking we should start to only target Client Profile where possible which will require fewer builds to be maintained What do people think of these ideas? Cheers, Rob |
|
From: <tr...@do...> - 2014-04-09 13:12:51
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Resolve issues with Json.Net dependency</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-04-09 02:12 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
There is a branch which has an experimental fix for this based on the approach you point out. The problem is that really this is only a workaround and we need to consider what .Net build profiles we should continue to support going forward to better align with the profiles our dependencies support</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=405" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405</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...> - 2014-04-09 13:11: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>Join linearisation breaks some queries with sequential left joins</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-04-09 02:10 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
A basic fix for this is in the place, the downside is that it will harm performance for some queries that aren't affected by this bug. It should be possible to make the fix less draconian so that queries that aren't affected by this can still take advantage of join linearization</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=406" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=406</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...> - 2014-04-09 13:09:32
|
<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>Join linearisation breaks some queries with sequential left joins</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Confirmed" to "In Progress"
</li>
<li>Progress changed from "0 %" to "75 %"
</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=406" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=406</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...> - 2014-04-09 12:45:46
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Resolve issues with Json.Net dependency</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>FHaag</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-04-09 01:44 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
According to <a href="http://docs.nuget.org/docs/reference/versioning#Specifying_Version_Ranges_in_.nuspec_Files">the docs</a>, it should be sufficient to specify</p>
<p>
[5.0.8,6.0)</p>
<p>
as the version range for the Newtonsoft.Json package reference.</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=405" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405</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...> - 2014-04-09 12:36:27
|
<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>Resolve issues with Json.Net dependency</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>FHaag</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-04-09 01:35 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Hi, are there any news, such as a temporary bugfix NuGet package that limits the Newtonsoft.Json Nuget version to 5.0.8? I just ran the regular package update on a large solution just to notice afterwards that the dependencies don't match up any more, and inspecting the currently used versions of dotNetRDF and Newtonsoft.Json showed me just what you outline above.</p>
<p>
Thanks!</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405</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...> - 2014-04-08 23:29:18
|
Send dotNetRDF-commits mailing list submissions to dot...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits or, via email, send a message with subject or body 'help' to dot...@li... You can reach the person managing the list at dot...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of dotNetRDF-commits digest..." Today's Topics: 1. commit/dotnetrdf: 2 new changesets (Bitbucket) 2. commit/dotnetrdf: 4 new changesets (Bitbucket) 3. commit/dotnetrdf: rvesse: Some infrastructure ready to refactor IRdfReader to introduce new IParserProfile argument (Bitbucket) 4. commit/dotnetrdf: 7 new changesets (Bitbucket) 5. commit/dotnetrdf: 2 new changesets (Bitbucket) 6. commit/dotnetrdf: 2 new changesets (Bitbucket) 7. commit/dotnetrdf: 3 new changesets (Bitbucket) 8. commit/dotnetrdf: rvesse: Update solutions and projects for VS 2013 (Bitbucket) 9. commit/dotnetrdf: 2 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Fri, 21 Mar 2014 14:44: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/d5a59738ba9d/ Changeset: d5a59738ba9d Branch: 1.9 User: rvesse Date: 2014-03-21 15:14:31 Summary: Add Silverlight 4 build of IO Core Affected #: 8 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3adf55f69aee/ Changeset: 3adf55f69aee Branch: 1.9 User: rvesse Date: 2014-03-21 15:44:03 Summary: Get Silverlight 4 and Windows Phone 7 builds of IO Core working Affected #: 12 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Fri, 21 Mar 2014 16:10:03 -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/0440816371ed/ Changeset: 0440816371ed Branch: 1.9 User: rvesse Date: 2014-03-21 15:56:32 Summary: Alternative build profiles for IO JSON library Affected #: 18 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9384e42796fe/ Changeset: 9384e42796fe Branch: 1.9 User: rvesse Date: 2014-03-21 15:58:33 Summary: Alternative build profiles for IO JSON library Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/14bb30007928/ Changeset: 14bb30007928 Branch: 1.9 User: rvesse Date: 2014-03-21 16:17:02 Summary: Work on making quality factors for RDF formats configurable (CORE-379) Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ce5a744256bc/ Changeset: ce5a744256bc Branch: 1.9 User: rvesse Date: 2014-03-21 17:09:41 Summary: Properly support configurable quality for MIME type definitions (CORE-379) Affected #: 4 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 3 Date: Fri, 21 Mar 2014 16:35:04 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Some infrastructure ready to refactor IRdfReader to introduce new IParserProfile argument 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/0cf37169f3c5/ Changeset: 0cf37169f3c5 Branch: 1.9 User: rvesse Date: 2014-03-21 17:34:44 Summary: Some infrastructure ready to refactor IRdfReader to introduce new IParserProfile argument Affected #: 12 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, 28 Mar 2014 10:36:41 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 7 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 7 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a383ee18060b/ Changeset: a383ee18060b Branch: 1.9 User: rvesse Date: 2014-03-24 17:36:53 Summary: Start incorporating IParserProfile into IRdfReader contract Affected #: 14 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/781ccb869431/ Changeset: 781ccb869431 Branch: 1.9 User: rvesse Date: 2014-03-24 18:00:08 Summary: Start stripping out historical and unecessary explicit use of StreamReader wherever possible and slimming down the IRdfReader interface accordingly Affected #: 18 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/754caffa2442/ Changeset: 754caffa2442 Branch: 1.9 User: rvesse Date: 2014-03-24 18:06:39 Summary: More work on stripping out unecessary explicit use of StreamReader where possible Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3e17b966fc24/ Changeset: 3e17b966fc24 Branch: 1.9 User: rvesse Date: 2014-03-25 18:05:42 Summary: More work to remove unecessary explicit usage of StreamReader as far as possible Affected #: 49 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a2d4e3034865/ Changeset: a2d4e3034865 Branch: 1.9 User: rvesse Date: 2014-03-26 17:48:43 Summary: Refactoring to specify IBlankNodeGenerator via IParserProfile Affected #: 19 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/7feeccc8c7c9/ Changeset: 7feeccc8c7c9 Branch: 1.9 User: rvesse Date: 2014-03-27 16:18:35 Summary: Propogate IParserProfile to IRdfHandler as part of parsing process Affected #: 13 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/cb225b2e5f0e/ Changeset: cb225b2e5f0e Branch: 1.9 User: rvesse Date: 2014-03-27 16:24:36 Summary: Start fixing up tests now initial Base URI may be injected via IParserProfile 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: Fri, 28 Mar 2014 12:17:06 -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/df87546613c0/ Changeset: df87546613c0 Branch: 1.9 User: rvesse Date: 2014-03-28 12:54:51 Summary: Improve EqualityHelper and ComparisonHelper to support Relative URIs and to account for RDF 1.1 changes to literals Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9ac729428fb1/ Changeset: 9ac729428fb1 Branch: 1.9 User: rvesse Date: 2014-03-28 13:14:03 Summary: More work on trying to fix up the test suite Affected #: 5 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: Mon, 31 Mar 2014 10:16:45 -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/81511d05d96d/ Changeset: 81511d05d96d User: rvesse Date: 2014-03-31 11:39:23 Summary: Prepare for next development cycle Affected #: 20 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3fbc0f7f7784/ Changeset: 3fbc0f7f7784 User: rvesse Date: 2014-03-31 12:14:34 Summary: Add version validation to release process 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: Wed, 02 Apr 2014 15:42:45 -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/1e5de19642f7/ Changeset: 1e5de19642f7 User: rvesse Date: 2014-04-02 16:55:29 Summary: Tweak for TestTools so MTA Thread errors are better reported Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/56bab47e806e/ Changeset: 56bab47e806e Branch: CORE-405 User: rvesse Date: 2014-04-02 17:06:32 Summary: Initial bump of dependencies to latest versions (where possible) (CORE-405) Affected #: 32 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a2d4f6742df4/ Changeset: a2d4f6742df4 Branch: CORE-405 User: rvesse Date: 2014-04-02 17:41:34 Summary: Tweaks to defined NuGet package dependencies that should resolve the issues with conflicting Json.Net dependencies for most profiles (CORE-405) Affected #: 11 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 8 Date: Fri, 04 Apr 2014 12:48:36 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Update solutions and projects for VS 2013 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/cf03a510e140/ Changeset: cf03a510e140 Branch: 1.9 User: rvesse Date: 2014-04-04 14:48:19 Summary: Update solutions and projects for VS 2013 Affected #: 5 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 9 Date: Tue, 08 Apr 2014 23:29:05 -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/35ce21e29756/ Changeset: 35ce21e29756 Branch: CORE-406 User: rvesse Date: 2014-04-09 01:14:57 Summary: Add failing test to demonstrate CORE-406 bug with OPTIONAL join linearization Affected #: 7 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/bc2c30d0da9c/ Changeset: bc2c30d0da9c Branch: CORE-406 User: rvesse Date: 2014-04-09 01:23:31 Summary: Apply fix for CORE-406 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. ------------------------------ ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 18, Issue 1 ************************************************ |
|
From: <tr...@do...> - 2014-04-08 12:56:31
|
<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>Join linearisation breaks some queries with sequential left joins</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.5</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
As demonstrated by this mailing list thread - <a href="http://sourceforge.net/p/dotnetrdf/mailman/message/32200405/">http://sourceforge.net/p/dotnetrdf/mailman/message/32200405/</a> - there is a bug where multiple OPTIONAL clauses at the same level can cause incorrect results due to interactions with the join linerisation we perform.</p>
<p>
The fix should be to not linearize nested left joins</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=406" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=406</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...> - 2014-04-02 15:10: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>Resolve issues with Json.Net dependency</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-04-02 04:09 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
A short term workaround is probably just to restrict the dependency version for the appropriate builds to 5.0.8 and to upgrade builds that can be updated to 6.x</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=405" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405</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...> - 2014-04-02 15:01:41
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Resolve issues with Json.Net dependency</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-04-02 04:00 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Speaking specifically to Json.Net they appear to have removed specific packages for Silverlight and Windows in favour of PCL packages instead. It may be sensible for us to take the same route as they will reduce the number of projects and packages we need to maintain going forward</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=405" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405</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...> - 2014-04-02 15:00: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>Resolve issues with Json.Net dependency</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-04-02 03:59 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Was going to try and look at this today but NuGet is currently having issues so the package feeds are down and I can't upgrade the dependencies</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=405" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405</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...> - 2014-04-02 14:53:37
|
<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>Resolve issues with Json.Net dependency</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Confirmed" to "In Progress"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405</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...> - 2014-04-02 13:17:34
|
<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>Resolve issues with Json.Net dependency</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.5</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Build, Release and Testing</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Critical</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Various users have reported issues with installing recent versions of dotNetRDF with NuGet because of dependency conflicts with Json.Net. The Netwonsoft.Json NuGet package now has a 6.x line while we are currently using the 5.x line, in various circumstances NuGet will install the 6.x line instead of the 5.x line</p>
<p>
</p>
<p>
Ideally we will resolve this by moving to the 6.x line, in the past when I've experimented with this I've run into issues because of changes in what profiles Json.Net are now packaging their builds for. Resolving the issue may mean some refactoring of the .Net profiles that we build for.</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=405" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=405</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: Eugen F <feu...@ya...> - 2014-04-02 13:07:03
|
I had same problem, but I added reference to "Newtonsoft.json" 4.5.0 assembly version/5.0.8 file version, the one that comes with Dnr 1.4 download instead of Nuget...as a temporary fix. I also tried getting specific version 4.5.0 from Nuget but it wasn't available. On Tuesday, April 1, 2014 10:48 PM, "mar...@ko..." <mar...@ko...> wrote: Hi Tom, Visual Studio offered to do what you suggested -- add bindingRedirect's -- which I accepted, but then at some point Visual Studio would no longer automatically copy the Newtonsoft.json dll to the output directory. I finally just ripped out all traces of the previous version of Newtonsoft.json from all my project files rather than try to fully debug the root causes. -Mark Mark D. Wood | Personalized Imaging R&D Kodak Alaris| 2400 Mt. Read Blvd. | Rochester, NY . Subject: Re: [dotNetRDF-Develop] dotNetRDF version number ________________________________ Hi Mark We also bumped into versioning problems with Newtonsoft.Json. We added a binding redirect to app.configs like below and there haven't been any problems. Is this what you have done too? <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" /> </dependentAssembly> </assemblyBinding> </runtime> Regards, Tom On Tue, Apr 1, 2014 at 2:45 PM, <mar...@ko...> wrote: That in fact is the issue. Thanks for shedding some light on the situation. I am using another NuGet-managed library that also has a dependency on Newtonsoft.json; when I updated that library recently, I believe it pulled the latest version of Newtonsoft.json, which appears to be what triggered this issue. I am now forcing dotNetRDF 1.0.4 to use Json 6.0.1 which seems to be working once I finished cajoling Visual Studio. NuGet lists the dotNetRDF dependency as simply >= 5.0.8 of Newtonsoft.json. I know almost nothing about NuGet mechanics, but taking a look at https://docs.nuget.org/docs/reference/versioningI wonder if you do need to constrain more tightly which version of Newtonsoft.json you are using? The way I read it, NuGet will update across major releases unless the dependency explicitly says not to? Thanks again, -mark Mark D. Wood | Personalized Imaging R&D Kodak Alaris| 2400 Mt. Read Blvd. | Rochester, NY . From: Tomasz Pluskiewicz <tom...@gm...> To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: 04/01/2014 11:05 AM From: Rob Vesse <rv...@do...> To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: 04/01/2014 04:36 AM Subject: Re: [dotNetRDF-Develop] dotNetRDF version number ________________________________ Mark Was NuGet trying to use Newtonsoft.Json 6.x by any chance? We’re currently still building against 5.x and haven’t upgraded yet because they appear to have changed what .Net profiles they are building for so upgrading isn’t a simple push button action for us and requires some build and packaging refactoring on our part. I had thought NuGet wasn’t supposed to grab different major releases though it is possible that if your code depends on the 6.x line of Netwtonsoft.Json this would cause dependency conflicts Rob From: <mar...@ko...> Reply-To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: Monday, 31 March 2014 18:59 To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Subject: Re: [dotNetRDF-Develop] dotNetRDF version number Thanks; sounds good. In updating to the latest version of the dotNetRDF library, NuGet gave me a hard time with the Newtonsoft.json dependency, requiring me to manually patch some things, and I noticed the discrepancy in the dotnetRDF dll version number. (Am I the only one running into problems w/ Newtonsoft.json? I had to fight to get NuGet/Visual Studio to go with the latest version of that particular library). -Mark Mark D. Wood | Personalized Imaging R&D Kodak Alaris| 2400 Mt. Read Blvd. | Rochester, NY . From: Rob Vesse <rv...@do...> To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: 03/31/2014 05:41 AM Subject: Re: [dotNetRDF-Develop] dotNetRDF version number ________________________________ No it is not, it was an oversight in the release process on my part. I’ll look at adding validation to our release process that ensures that this cannot happen in future. The code that is published is however the 1.0.4.3225 release. Note that there is not necessarily a requirement that the assembly versions correspond to the NuGet package versions though we usually try to ensure this. Rob From: <mar...@ko...> Reply-To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: Friday, 28 March 2014 22:07 To: <dot...@li...> Subject: [dotNetRDF-Develop] dotNetRDF version number Is it intentional that the dotNetRDF dll file/product version number is still at 1.0.3.0, even though we're at version 1.0.4.3225? -Mark Mark D. Wood | Personalized Imaging R&D Kodak Alaris| 2400 Mt. Read Blvd. | Rochester, NY . ------------------------------------------------------------------------------ _______________________________________________ dotNetRDF-develop mailing list dot...@li...https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop------------------------------------------------------------------------------ _______________________________________________ dotNetRDF-develop mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop ------------------------------------------------------------------------------ _______________________________________________ dotNetRDF-develop mailing list dot...@li...https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop------------------------------------------------------------------------------ _______________________________________________ dotNetRDF-develop mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop ------------------------------------------------------------------------------ _______________________________________________ dotNetRDF-develop mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop ------------------------------------------------------------------------------ _______________________________________________ dotNetRDF-develop mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop ------------------------------------------------------------------------------ _______________________________________________ dotNetRDF-develop mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: <efi...@gm...> - 2014-03-28 10:32:57
|
Hi, I want to announce two projects: 1)* DynamicSPARQL* - dynamically scaffolds SPARQL queries.It can be effectively used when you need to write code to dynamically construct SPARQL queries. For example GUI that has a search form. Please visit project wiki pages https://github.com/Efimster/DynamicSPARQL/wiki Available through NuGet https://www.nuget.org/packages/DynamicSPARQL/ 2) *LINQtoSPARQL *- specific LINQ to SPARQL. Dynamically scaffolds SPARQL queries by using LINQ style. Please visit project wiki pages https://github.com/Efimster/LINQtoSPARQL/wiki . Available through NuGet https://www.nuget.org/packages/LINQtoSPARQL/ Regards, Efim |
|
From: <tr...@do...> - 2014-03-21 16:37:34
|
<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>Add configurable quality values for MimeTypeDefinition</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-03-21 04:36 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Implemented for RDF formats on the 1.9 branch, not yet implemented for SPARQL result formats</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=379" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=379</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...> - 2014-03-21 16:37:00
|
<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>Add configurable quality values for MimeTypeDefinition</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>Progress changed from "0 %" to "50 %"
</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=379" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=379</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...> - 2014-03-21 15:17:18
|
<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>Add configurable quality values for MimeTypeDefinition</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 "Planned" to "In Progress"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=379" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=379</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...> - 2014-03-21 15:08:50
|
<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>Add configurable quality values for MimeTypeDefinition</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 "Unscheduled" to "1.9.0 Beta"
</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=379" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=379</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...> - 2014-03-21 14:09:23
|
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: Additional unit tests for NQuads output (CORE-356) (Bitbucket) 3. commit/dotnetrdf: 2 new changesets (Bitbucket) 4. commit/dotnetrdf: 6 new changesets (Bitbucket) 5. commit/dotnetrdf: 3 new changesets (Bitbucket) 6. commit/dotnetrdf: 4 new changesets (Bitbucket) 7. commit/dotnetrdf: 2 new changesets (Bitbucket) 8. commit/dotnetrdf: 2 new changesets (Bitbucket) 9. commit/dotnetrdf: 3 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Fri, 28 Feb 2014 15:38:40 -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/50f18a91b919/ Changeset: 50f18a91b919 User: rvesse Date: 2014-02-28 16:31:59 Summary: Additional unit tests for RDF 1.1 NTriples and NQuads writing support (CORE-355, CORE-356) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4f2995ce1c2d/ Changeset: 4f2995ce1c2d Branch: ntuples11 User: rvesse Date: 2014-02-28 16:35:05 Summary: Merge latest from default Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f0d5253fbec2/ Changeset: f0d5253fbec2 Branch: ntuples11 User: rvesse Date: 2014-02-28 16:38:12 Summary: Fix various test regressions caused by CORE-401 fix, adjust test cases to match fixed behaviour Affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Fri, 28 Feb 2014 15:59:52 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Additional unit tests for NQuads output (CORE-356) 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/b35da639a1b2/ Changeset: b35da639a1b2 Branch: ntuples11 User: rvesse Date: 2014-02-28 16:59:27 Summary: Additional unit tests for NQuads output (CORE-356) Affected #: 5 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 3 Date: Fri, 28 Feb 2014 16:07:30 -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/58cbb26fd593/ Changeset: 58cbb26fd593 Branch: ntuples11 User: rvesse Date: 2014-02-28 17:04:45 Summary: Close RDF NTuples 1.1 branch since the work is now essentially complete (CORE-355, CORE-356) Affected #: 0 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b37d1707735f/ Changeset: b37d1707735f User: rvesse Date: 2014-02-28 17:06:57 Summary: Merge in RDF 1.1 NTuples support (CORE-355, CORE-356) Affected #: 7 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 4 Date: Fri, 07 Mar 2014 16:23:47 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 6 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 6 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/406c0814873f/ Changeset: 406c0814873f Branch: CORE-402 User: rvesse Date: 2014-03-07 16:29:03 Summary: Unit tests that demonstrate the CORE-402 bug Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/36c94e51e8e4/ Changeset: 36c94e51e8e4 Branch: CORE-402 User: rvesse Date: 2014-03-07 16:55:44 Summary: Work on fixing the formatting of UNION graph patterns (CORE-402) Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1c00f0023829/ Changeset: 1c00f0023829 Branch: CORE-402 User: rvesse Date: 2014-03-07 16:56:44 Summary: Note CORE-402 as fixed in Change Log Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/628333b6e675/ Changeset: 628333b6e675 User: rvesse Date: 2014-03-07 16:58:49 Summary: Merge in CORE-402 fixes Affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/183cfdd826db/ Changeset: 183cfdd826db Branch: CORE-403 User: rvesse Date: 2014-03-07 17:14:12 Summary: Unit tests and fix for CORE-403 bug, fixes the TriG parser to correctly allow literals in collections Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/bc39f7654c8b/ Changeset: bc39f7654c8b Branch: CORE-403 User: rvesse Date: 2014-03-07 17:22:43 Summary: More unit tests for TriG collection parsing, fixes a bug with it not allowing blank nodes with explicit IDs in collections either (CORE-403) 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: Fri, 07 Mar 2014 16:59:12 -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/0d361c38d2f5/ Changeset: 0d361c38d2f5 Branch: CORE-403 User: rvesse Date: 2014-03-07 17:25:19 Summary: Further unit tests for CORE-403 Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e09829772fce/ Changeset: e09829772fce Branch: CORE-403 User: rvesse Date: 2014-03-07 17:30:35 Summary: Note CORE-403 fix in Change Log Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f620eb0ccacd/ Changeset: f620eb0ccacd User: rvesse Date: 2014-03-07 17:33:11 Summary: Merge in CORE-403 fixes to collection parsing for TriG Affected #: 4 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 6 Date: Fri, 14 Mar 2014 10:28:25 -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/b2688d0fe1ec/ Changeset: b2688d0fe1ec Branch: 1.9 User: rvesse Date: 2014-03-13 17:08:08 Summary: Merge latest changes from default Affected #: 227 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/afe35ca62299/ Changeset: afe35ca62299 User: rvesse Date: 2014-03-14 11:22:05 Summary: Add appropriate canonical MIME types for RDF 1.1 NTriples and NQuads (CORE-355,CORE-356) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e82f16cbd2db/ Changeset: e82f16cbd2db User: rvesse Date: 2014-03-14 11:24:32 Summary: Add NTriples11Formatter (CORE-355) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/34d6dd5a60c5/ Changeset: 34d6dd5a60c5 User: rvesse Date: 2014-03-14 11:26:01 Summary: Add NQuads 1.1 Formatter (CORE-356) 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: Fri, 14 Mar 2014 10:54:49 -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/fb4cb9c22100/ Changeset: fb4cb9c22100 User: rvesse Date: 2014-03-14 11:30:16 Summary: Note additional NTuples 1.1 related changes in Change Log (CORE-355,CORE-356) Affected #: 11 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3a41bcb82d52/ Changeset: 3a41bcb82d52 User: rvesse Date: 2014-03-14 11:54:23 Summary: Prepare for 1.0.4 release Affected #: 27 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 8 Date: Fri, 14 Mar 2014 11:23:59 -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/6f63817a58bc/ Changeset: 6f63817a58bc User: rvesse Date: 2014-03-14 12:09:31 Summary: Add support for RDF 1.1 NTriples and NQuads syntaxes to rdfEditor (CORE-355,CORE-356) Affected #: 16 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6c23d427de97/ Changeset: 6c23d427de97 User: rvesse Date: 2014-03-14 12:23:12 Summary: Added tag 1.0.4, 104, 1.0.4.3225 for changeset 6f63817a58bc 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: Fri, 21 Mar 2014 14:09:12 -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/053688fe7c0f/ Changeset: 053688fe7c0f User: rvesse Date: 2014-03-17 17:32:03 Summary: Prepare for next development cycle Affected #: 15 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/bfe799e209e6/ Changeset: bfe799e209e6 Branch: 1.9 User: rvesse Date: 2014-03-21 15:08:34 Summary: Forget 1.9 solution to break hg copy tracking Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a8a97dd38e68/ Changeset: a8a97dd38e68 Branch: 1.9 User: rvesse Date: 2014-03-21 15:08:50 Summary: Re-add 1.9 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. ------------------------------ ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 17, Issue 1 ************************************************ |
|
From: <tr...@do...> - 2014-03-21 14:06:39
|
<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>Blank nodes not created correctly for loaded graph after restarting program</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Priority changed from "Unassigned" to "Low"
</li>
<li>Status changed from "Unassigned" to "Confirmed"
</li>
<li>Milestone changed from "Unassigned" to "1.9.0 Beta"
</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=404" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=404</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...> - 2014-03-21 14:06:24
|
<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>Blank nodes not created correctly for loaded graph after restarting program</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-03-21 02:05 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Yes this is a bug and I'm pretty certain I know what is going on. However this may not be fixable in the 1.x APIs because of various legacy design decisions around blank nodes and node scoping. I will take a look and see if there is an easy fix for this specific case of the problem but the general problem is not fixable in the 1.x API.</p>
<p>
</p>
<p>
There is ongoing work on the 2.x API which should resolve the problem though the SPARQL engine has yet to be ported forward to the 2.x API so I can't confirm at this time whether this does resolve the 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=404" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=404</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...> - 2014-03-21 10:23:11
|
<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>Blank nodes not created correctly for loaded graph after restarting program</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Marek Obitko</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unassigned</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Update</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>
Steps to reproduce (see also code below):</p>
<p>
1. Create data with a blank node, for example using INSERT DATA { [ <http://mapping/left> "item1"; <http://mapping/right> "item2" ] }</p>
<p>
2. Save to file</p>
<p>
3. Stop and start the program again (important, this doesn't happen in one run)</p>
<p>
4. Add another blank node, e.g. by INSERT DATA { [ <http://mapping/left> "item3"; <http://mapping/right> "item4" ] }</p>
<p>
5. Observe that the new blank node is merged with the original blank node. When multiple blank nodes are created, they are merged together one by one. It seems (but doesn't have to be) that the problem is that the numbering autosX ID of blank node starts with the same X, even if autosX already exists in the loaded graph.</p>
<p>
</p>
<p>
Not using any 3rd party storage. See also examples below.</p>
<p>
</p>
<p>
Code demonstrating the bug is as follows:</p>
<p>
public void DemonstrateBug()<br />
{<br />
if (!File.Exists(@"c:\mapping1.xml"))<br />
{<br />
// first pass - create blank node<br />
IGraph graph = new Graph();<br />
TripleStore tripleStore = new TripleStore();<br />
tripleStore.Add(graph);<br />
SparqlUpdateParser parser = new SparqlUpdateParser();<br />
SparqlParameterizedString cmdString = new SparqlParameterizedString();<br />
<br />
cmdString.CommandText = @"INSERT DATA { [ <http://mapping/left> ""item1""; <http://mapping/right> ""item2"" ] }";<br />
<br />
SparqlUpdateCommandSet cmds = parser.ParseFromString(cmdString);<br />
LeviathanUpdateProcessor processor = new LeviathanUpdateProcessor(tripleStore);<br />
processor.ProcessCommandSet(cmds);<br />
<br />
RdfXmlWriter rdfXmlWriter = new RdfXmlWriter();<br />
rdfXmlWriter.Save(graph, @"c:\mapping1.xml");<br />
rdfXmlWriter.Save(graph, @"c:\mapping.xml");<br />
}<br />
else<br />
{<br />
// second pass - read file and add a new blank node<br />
IGraph graph = new Graph();<br />
TripleStore tripleStore = new TripleStore();<br />
tripleStore.Add(graph);<br />
<br />
RdfXmlParser rdfXmlParser = new RdfXmlParser();<br />
rdfXmlParser.Load(graph, @"c:\mapping.xml");<br />
<br />
SparqlUpdateParser parser = new SparqlUpdateParser();<br />
SparqlParameterizedString cmdString = new SparqlParameterizedString();<br />
<br />
cmdString.CommandText = @"INSERT DATA { [ <http://mapping/left> ""item3""; <http://mapping/right> ""item4"" ] }";<br />
<br />
SparqlUpdateCommandSet cmds = parser.ParseFromString(cmdString);<br />
LeviathanUpdateProcessor processor = new LeviathanUpdateProcessor(tripleStore);<br />
processor.ProcessCommandSet(cmds);<br />
<br />
RdfXmlWriter rdfXmlWriter = new RdfXmlWriter();<br />
rdfXmlWriter.Save(graph, @"c:\mapping.xml");<br />
rdfXmlWriter.Save(graph, @"c:\mapping2.xml");<br />
}<br />
}</p>
<p>
</p>
<p>
The first run produces</p>
<p>
<rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><br />
<rdf:Description rdf:nodeID="autos1"><br />
<ns0:left xmlns:ns0="http://mapping/">item1</ns0:left><br />
<ns1:right xmlns:ns1="http://mapping/">item2</ns1:right><br />
</rdf:Description><br />
</rdf:RDF></p>
<p>
and the second run produces incorrectly</p>
<p>
<rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:ns0="http://mapping/" xmlns:ns1="http://mapping/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><br />
<rdf:Description rdf:nodeID="autos1"><br />
<ns1:left>item1</ns1:left><br />
<ns1:left>item3</ns1:left><br />
<ns1:right>item2</ns1:right><br />
<ns1:right>item4</ns1:right><br />
</rdf:Description><br />
</rdf:RDF></p>
<p>
but I would expect correct</p>
<p>
<rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:ns0="http://mapping/" xmlns:ns1="http://mapping/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><br />
<rdf:Description rdf:nodeID="autos1"><br />
<ns1:left>item1</ns1:left><br />
<ns1:right>item2</ns1:right><br />
</rdf:Description><br />
<rdf:Description rdf:nodeID="autos2"><br />
<ns1:left>item3</ns1:left><br />
<ns1:right>item4</ns1:right><br />
</rdf:Description><br />
</rdf:RDF></p>
<p>
which is produced when the code above is run twice within one program run.</p>
<p>
Thanks for looking at it!</p>
<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=404" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=404</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
48 messages has been excluded from this view by a project administrator.
