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: <dot...@li...> - 2014-05-07 14:24:05
|
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: rvesse: Merged default into CORE-405 (Bitbucket) 3. commit/dotnetrdf: rvesse: Merged default into CORE-406 (Bitbucket) 4. commit/dotnetrdf: 2 new changesets (Bitbucket) 5. commit/dotnetrdf: rvesse: Update depdencies to latest versions and update NuSpec files appropriately (CORE-405) (Bitbucket) 6. commit/dotnetrdf: 9 new changesets (Bitbucket) 7. commit/dotnetrdf: 4 new changesets (Bitbucket) 8. commit/dotnetrdf: 2 new changesets (Bitbucket) 9. commit/dotnetrdf: rvesse: Merged in ansell/dotnetrdf/ansell/add-link-to-bug-tracker-in-readmemd-1399421655743 (pull request #28) (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Thu, 10 Apr 2014 17:01:29 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/229d5038da52/ Changeset: 229d5038da52 User: kal_ahmed Date: 2014-04-04 16:15:55 Summary: Added a node comparer that can compare virtual nodes on their VirtualID. This avoids the need to materialize virtual nodes just to add them to a MultiDictionary structure. Affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/044cb53714c1/ Changeset: 044cb53714c1 User: kal_ahmed Date: 2014-04-09 19:18:07 Summary: Added missing IVirtualIdComparable test to FastVirtualNodeComparer. Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Thu, 10 Apr 2014 17:02:13 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Merged default into CORE-405 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/34453b339a20/ Changeset: 34453b339a20 Branch: CORE-405 User: rvesse Date: 2014-04-10 19:02:08 Summary: Merged default into CORE-405 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: Thu, 10 Apr 2014 17:02:34 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Merged default into CORE-406 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/e5f88fae6fe1/ Changeset: e5f88fae6fe1 Branch: CORE-406 User: rvesse Date: 2014-04-10 19:02:29 Summary: Merged default into CORE-406 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: 4 Date: Tue, 15 Apr 2014 04:37:16 -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/6ec29c8852aa/ Changeset: 6ec29c8852aa Branch: CORE-405 User: rvesse Date: 2014-04-15 06:27:07 Summary: Upgrade dependencies to latest (CORE-405) Affected #: 32 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/45e51847f409/ Changeset: 45e51847f409 Branch: CORE-405 User: rvesse Date: 2014-04-15 06:36:33 Summary: Remove defunct projects Affected #: 8 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, 18 Apr 2014 05:27:27 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Update depdencies to latest versions and update NuSpec files appropriately (CORE-405) 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/63c9402df11a/ Changeset: 63c9402df11a Branch: CORE-405 User: rvesse Date: 2014-04-18 07:26:16 Summary: Update depdencies to latest versions and update NuSpec files appropriately (CORE-405) Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 6 Date: Fri, 18 Apr 2014 06:08:07 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 9 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 9 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/72f3fc7f3510/ Changeset: 72f3fc7f3510 User: rvesse Date: 2014-04-18 07:29:40 Summary: Merge latest dependency improvements from CORE-405 branch Affected #: 47 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5d8c2d212254/ Changeset: 5d8c2d212254 Branch: CORE-408 User: rvesse Date: 2014-04-18 07:43:40 Summary: Add user submitted failing test from CORE-408 Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2c37b518e8ad/ Changeset: 2c37b518e8ad Branch: CORE-408 User: rvesse Date: 2014-04-18 07:46:12 Summary: Additional tests and fixes for CORE-408 Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/eb8e396c17c6/ Changeset: eb8e396c17c6 User: rvesse Date: 2014-04-18 07:47:31 Summary: Merge CORE-408 fixes to default Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a8e56bee87ce/ Changeset: a8e56bee87ce User: rvesse Date: 2014-04-18 07:50:25 Summary: Note recent changes in Change Log (CORE-405, CORE-408) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/904d9ba345ac/ Changeset: 904d9ba345ac Branch: CORE-407 User: rvesse Date: 2014-04-18 08:02:55 Summary: Add failing test to demonstrate CORE-407 bug Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2e0988441fe8/ Changeset: 2e0988441fe8 Branch: CORE-407 User: rvesse Date: 2014-04-18 08:04:45 Summary: Trivial fix for CORE-407 Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/88cb657a9efe/ Changeset: 88cb657a9efe Branch: CORE-407 User: rvesse Date: 2014-04-18 08:06:09 Summary: Note CORE-407 fix in Change Log Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6eda05a380f2/ Changeset: 6eda05a380f2 User: rvesse Date: 2014-04-18 08:07:35 Summary: Merge CORE-407 fix to default Affected #: 3 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 7 Date: Fri, 02 May 2014 10:30:59 -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/51d5f5057f0c/ Changeset: 51d5f5057f0c Branch: CORE-405 User: rvesse Date: 2014-05-02 12:22:08 Summary: Update Json.Net dependency to 6.0.3 (CORE-405) Affected #: 30 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/03eca0d41fed/ Changeset: 03eca0d41fed User: rvesse Date: 2014-05-02 12:26:49 Summary: Merge CORE-405 changes into default Affected #: 30 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d311ecc3e957/ Changeset: d311ecc3e957 Branch: CORE-405 User: rvesse Date: 2014-05-02 12:29:07 Summary: Close CORE-405 branch Affected #: 0 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/62d4949fd334/ Changeset: 62d4949fd334 User: rvesse Date: 2014-05-02 12:30:32 Summary: Merge closed CORE-405 branch Affected #: 0 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 8 Date: Fri, 02 May 2014 11:05: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/f5d8bfb098fb/ Changeset: f5d8bfb098fb User: rvesse Date: 2014-05-02 12:38:40 Summary: Note other changes in NuSpec release notes (CORE-407, CORE-408) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d0fbd7bcfc72/ Changeset: d0fbd7bcfc72 Branch: CORE-406 User: rvesse Date: 2014-05-02 13:03:18 Summary: Bring CORE-406 up to date Affected #: 50 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: Wed, 07 May 2014 14:23:56 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Merged in ansell/dotnetrdf/ansell/add-link-to-bug-tracker-in-readmemd-1399421655743 (pull request #28) 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/d9a230835baf/ Changeset: d9a230835baf User: rvesse Date: 2014-05-07 16:23:49 Summary: Merged in ansell/dotnetrdf/ansell/add-link-to-bug-tracker-in-readmemd-1399421655743 (pull request #28) Add link to Bug tracker in README.md 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. ------------------------------ ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 19, Issue 1 ************************************************ |
|
From: <tr...@do...> - 2014-05-07 00:34:46
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SPARQL/XML from Sesame Workbench contains an extra attribute</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Peter Ansell</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unassigned</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>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
A user on StackOverflow reported having issues parsing the SPARQL/Results XML generated by Sesame Workbench when using dotNetRDF.</p>
<p>
http://stackoverflow.com/questions/23471782/unable-to-parse-a-sparql-result-set-since-a-literal-element-has-too-many-attri</p>
<p>
The current design for Sesame Workbench relies on XSLT to render HTML. For historical reasons this has included an extra attribute to specify a qname for the datatype for literals and a qname for URIs.</p>
<p>
Would it be possible to relax the cardinality constraints in the SPARQL/Results XML Parser on the expected number of attributes and ignore unrecognised attributes as long as all of the essential attributes are present?</p>
<p>
The extra attribute doesn't get inserted if they request the result directly from a Sesame Server or they programmatically serialise the result (by default) so this only happens when they query the Workbench UI but it has happened once so far!</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=410" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=410</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-05-02 10:57:02
|
Ok, these targets are now removed and I am right up to date with Json.Net now Rob From: Kal Ahmed <ka...@ne...> Reply-To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: Wednesday, 9 April 2014 18:50 To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Subject: Re: [dotNetRDF-Develop] What .Net profiles should we support going forward? > I would be surprised if many people are using WP7 and SL4 for development any > longer. BrightstarDB does have these targets, but I'm considering removing > them too in favour of PCL builds that target WP8 and SL5. If you took them out > of DotNetRDF, I would have the perfect excuse! :-) > > I have done some building with Xamarin libraries and I chose to go for Profile > 158 which is portable-net45+sl5+wp80+win8+MonoAndroid10+MonoTouch10. I think > that should be compatible with your selected profile (though the whole profile > thing is just an opaque mess). > > I hit the problem of incompatible SL versions. If you take out the mono* > targets you are forced to include SL4 (you end up with Profile 154 which is > portable-net45+sl4+wp80+win8) Your approach of having the none mono profile > *not* include SL at all is probably the way to go. I may well do the same with > BrightstarDB. > > As for client profile, as far as I'm away this is all totally upward > compatible with full profile, isn't it ? If so then I have no problem with > those modules that don't need full profile being built with client profile. > The only thing I would say is be careful of imposing a limitation on yourself > that you will regret later! > > Cheers > > Kal > > > > > On Wed, Apr 9, 2014 at 2:22 PM, Rob Vesse <rv...@do...> wrote: >> 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 >> >> ----------------------------------------------------------------------------->> - >> 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-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com <http://www.networkedplanet.com> > ------------------------------------------------------------------------------ > 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-develop mailing list dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: <tr...@do...> - 2014-05-02 10:55:55
|
<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-05-02 11:55 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Pre-release packages are now available</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-05-02 10:33:39
|
<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-05-02 11:32 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
This is now fixed in default, I have upgraded to the very latest Json.Net version and updated our PCL build to use Profile 136 which aligns with what Json.Net supports</p>
<p>
</p>
<p>
I'll push out a pre-release package later today for people to test</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-05-02 10:32:36
|
<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 "In Progress" to "Completed"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Progress changed from "90 %" to "100 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=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: Miloš C. <cha...@ho...> - 2014-04-20 18:42:23
|
Hi Tomasz and Rob, After some time I am writing again. I had done some development and the first version of library core is nearly to be finished - it will support only a small subset of features (for master thesis I want effectively query the queries containing only triples, but as effectively as possible). I have signed for PhD study, and there I will continue in the work. You can see the current version on https://bitbucket.org/slupka/dotnetr2rmlstore . (The code is not yet documented, because there i salso some refactor needed, but in a month, it will change). And I want to ask you, Tomasz, whether you could check a bug https://bitbucket.org/r2rml4net/core/issue/17/joinconditions-returning-all-join . I am using the last unstable version from nuget (the stable version has not a proper reference to the dotNetRDF library, so it cannot be rewritten in .config file to a newer version). It seems to me, that I won't need any change in the dotNetRDF library, only minor things in R2R2ML library. And maybe in the future we can discuss an optimization, because now I need some code to duplicate and slightly modify (because it is not public or does not have an usable interface for me). It will need much more optimization, but I think that it will be usable in future (especially for presenting data already stored in RDBMS). Best Regards, Miloš -----Original Message----- From: plo...@gm... [mailto:plo...@gm...] On Behalf Of Tomasz Pluskiewicz Sent: Thursday, February 13, 2014 2:34 PM To: dotNetRDF Developer Discussion and Feature Request Cc: Miloš Chaloupka Subject: Re: [dotNetRDF-Develop] DotNetRDF Hi Miloš, Yes I did get your email! Thank you and sorry for late reply. I have been thinking long ago about using the R2RML mapping to translate SPARQL into SQL. Unfortunately there is always little time and more pressing issues and eventually I haven't even finished R2RML.net in 100%. However I will be happy to help with your project shall you desire to use the R2RML.net mapping as input and dotNetRDF as the query processor. As Rob said in his response, you could implement the existing interfaces to read through an input SQL query and transform it to SPARQL. There you will need the mappings. Most difficult is probably the actual algorithm for converting one query into another. Other than that of course you will need a way to process the SPARQL query. dotNetRDF parses it into a nice abstract model so you should be fine. Lastly you will eventually need a way to produce SQL queries for different DBMS flavours. On the mapping side you would have to make sure that R2RML.net exposes all the required mapping data. If you need any changes I encourage you to fork my repository and we'll try to adjust it to your needs. Regards, Tom PS There's also a blog posts which briefly discusses a way to do what you try to achive: http://antoniogarrote.wordpress.com/2011/01/10/translating-sparql-queries-into-sql-using-r2rml/ On Thu, Feb 13, 2014 at 12:09 PM, Rob Vesse <rv...@do...> wrote: > Hi Milos > > To be honest we've moved away from SQL backed storage because in the > past it hasn't proven that performant. However providing a R2RML > adaptor layer does make a lot more sense and provides a better > solution than what we've tried in the past (which was based on storing triples natively in a SQL database). > > I would suggest looking at implementing a IStorageProvider which also > implements IQueryableStorage if you are intending to support SPARQL. > Since this likely involves some sort of dependency upon Tom's existing > R2RML library then this would be best implemented as a separate > library in a similar way to the existing Data.Virtuoso library because > we want to mimize dependencies in the core library. I'd suggest > reading up on the Storage API > (https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Storage%20AP > I) if you haven't already and taking a look at the implementations of > existing IStorageProviders. > > Contribution wise I would suggest you create your own fork, work in > there and then submit pull request(s) as and when you have something > you thing is sufficiently stable for inclusion in the main project. > Please take a look at our Code Style guidelines > (https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/Code%20 > Style) > and Test Environment > (https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/Test%20 > Environment) documentation. Any substantial feature contribution like > this will need to be accompanied by appropriate tests which I > appreciate can be tricky for testing that requires on external > resources I.e. SQL servers but you can use the approach we use for > existing storage to provide developer configurable settings for test > setup and skip tests where the test system is unavailable. > > And of course if you have questions about anything then please ask on > the developer list which I've CC'd on this response, this is a > subscription based list which you will need to subscribe to via > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > Best Regards, > > Rob Vesse > > From: Miloš Chaloupka <cha...@ho...> > Date: Monday, 10 February 2014 09:18 > To: Rob Vesse <rv...@do...> > Subject: DotNetRDF > > Hi Rob, > > > > I have found you as an author of DotNetRDF so I hope I am contacting > the right person. I have already written to Tomasz Pluskiewicz, but > got no response yet, so I am not really sure, whether he even got the message. > > > > I am currently writing my master thesis "Querying RDF graphs stored in > a relational database using SPARQL and R2RML" and I am choosing how I > will write the implementation. I don't want to write a solution that > will end as an academic work with no chance of real use so I think, > that it would be nice to make it as a "part" of dotNetRDF. I want to > implement it as a store, that will be queryable using SPARQL according > to R2RML mapping. I can see that you have already listed several > libraries and that is in fact the only thing I want. Maybe you want to > ask why I am asking before I am starting the implementation, it is > because my supervisor wants to make the implementation as a part of > something bigger so I want to know whether it is possible. Are you > interested in such storage implementation? And if so, do you have any demands? > > > > Thank you for your reply, > > best regards, > > Miloš Chaloupka > > > ---------------------------------------------------------------------- > -------- > Android apps run on BlackBerry 10 > Introducing the new BlackBerry 10.2.1 Runtime for Android apps. > Now with support for Jelly Bean, Bluetooth, Mapview and more. > Get your Android app in front of a whole new audience. Start now. > http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg. > clktrk _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: <tr...@do...> - 2014-04-18 16:41: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>NQuads export data doesn't include the 4th slot e.g. graph identifier with Fuseki</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Toolkit</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Priority changed from "Unassigned" to "Normal"
</li>
<li>Status changed from "Unassigned" to "Unknown"
</li>
<li>Affected Milestone changed from "Unassigned" to "1.0.4"
</li>
<li>Assigned to changed from "Unassigned" to "Rob Vesse"
</li>
<li>Owner changed from "Unassigned" to "PaulZH"
</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=409" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=409</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-18 16:40:49
|
<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>NQuads export data doesn't include the 4th slot e.g. graph identifier with Fuseki</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Toolkit</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-04-18 05:39 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I haven't had time to look at this yet but one question that comes to mine is do you have the union default graph mode enabled for your dataset?</p>
<p>
</p>
<p>
If this is the case then I would expect to see named graph contents written both as triples and as quads</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=409" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=409</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-18 14:34:05
|
<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>NQuads export data doesn't include the 4th slot e.g. graph identifier with Fuseki</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Toolkit</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>PaulZH</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unassigned</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Store Manager</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Unassigned</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Having a Fuseki store containing multiple graphs.</p>
<p>
The Store manager lists the graphs as expected.</p>
<p>
However when exporting the full store to NQuads, I only get 3 slots filled in with the graph information lacking.</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=409" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=409</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-18 06:07: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>CONSTRUCT with empty WHERE but concrete template gives incorrect empty results</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"></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=407" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=407</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-18 06:07:16
|
<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>CONSTRUCT with empty WHERE but concrete template gives incorrect empty results</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-18 07:06 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Treatment of IdentityMultiset was indeed the problem, this is now fixed in default</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=407" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=407</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-18 06:06:52
|
<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>CONSTRUCT with empty WHERE but concrete template gives incorrect empty results</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Confirmed" to "Completed"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Progress changed from "0 %" to "100 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=407" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=407</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-18 05:58:56
|
<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>Support custom parameters for SparqlRemoteEndpoint and SparqlRemoteUpdateEndpoint</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 "1.0.5" to "1.0.6"
</li>
<li>Assigned to changed from "Unassigned" to "none"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=396" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=396</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-18 05:58:15
|
<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 support for latest W3C drafts for TriG</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 "1.0.5" to "1.0.6"
</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=354" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=354</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-18 05:58:09
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for latest W3C drafts for TriG</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-18 06:57 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Bumped to 1.0.6</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=354" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=354</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-18 05:55:47
|
<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>Support custom parameters for SparqlRemoteEndpoint and SparqlRemoteUpdateEndpoint</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-18 06:54 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Bumped to 1.0.6</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=396" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=396</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-18 05:54:01
|
<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-18 06:53 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
This is mostly fixed in default, we've upgraded our PCL build to Profile 136 and dropped our SL4 and WP7 builds. This has allowed us to upgrade our Json.Net dependency to the latest 6.0.2 release successfully</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-18 05:53:03
|
<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>Progress changed from "0 %" to "90 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=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-18 05:52:25
|
<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>SparqlQueryParser returns incorrect query when Uri containing dollar sign is passed as a parameter</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 "Completed"
</li>
<li>Milestone changed from "Unassigned" to "1.0.5"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Assigned to changed from "Unassigned" to "Rob Vesse"
</li>
<li>Progress changed from "0 %" to "100 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=408" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=408</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-18 05:52:16
|
<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>SparqlQueryParser returns incorrect query when Uri containing dollar sign is passed as a parameter</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-18 06:51 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Thanks for reporting this, this was a bug in our parameter injection logic that caused the wrong value to get injected when the value to be injected contained a $ sign. This has been fixed on our default branch and will be included in our next release</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=408" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=408</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-15 13:33:51
|
<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>SparqlQueryParser returns incorrect query when Uri containing dollar sign is passed as a parameter</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>DawidZ</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unassigned</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Version: 1.0.4.3225</p>
<p>
.NET: 4.5.1</p>
<p>
</p>
<p>
Bug can be reproduced with the following test:</p>
<p>
</p>
<div>
[Test]</div>
<div>
public void SparqlQueryParserHandlesDollarSignInUriParameter()</div>
<div>
{</div>
<div>
const string queryString = @"SELECT ?p ?o WHERE { @subject ?p ?o . }";</div>
<div>
const string expectedCondition = @"<http://dbpedia.org/resource/$_(film)> ?p ?o";</div>
<div>
var uri = new Uri("http://dbpedia.org/resource/$_(film)");</div>
<div>
</div>
<div>
var parametrizedQueryString = new SparqlParameterizedString(queryString);</div>
<div>
parametrizedQueryString.SetUri("subject", uri);</div>
<div>
var sparqlQuery = new SparqlQueryParser().ParseFromString(parametrizedQueryString);</div>
<div>
</div>
<div>
Assert.That(sparqlQuery.ToString(), Contains.Substring(expectedCondition));</div>
<div>
}</div></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=408" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=408</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-14 16:19:04
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>CONSTRUCT with empty WHERE but concrete template gives incorrect empty results</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-14 05:18 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
My guess is that the problem lies in how we treat IdentityMultiset when processing CONSTRUCT results or it could be broader than that and we aren't treating IdentityMultiset correctly when translating to SparqlResultSet. Needs more investigation to confirm what the problem is but should be a trivial fix once the cause is confirmed.</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=407" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=407</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-14 16:17:52
|
<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>CONSTRUCT with empty WHERE but concrete template gives incorrect empty results</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>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>
Reported via direct email (despite me having told said user to report to the mailing list multiple times already), the following query gives an empty result when it should return a single triple:</p>
<p>
</p>
<p>
<span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;">PREFIX dc: <</span><a href="http://purl.org/dc/elements/1.1/" style="font-family: Calibri; font-size: medium;">http://purl.org/dc/elements/1.1/</a><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;">></span><br style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;" />
<span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;">CONSTRUCT</span><br style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;" />
<span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;">{</span><br style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;" />
<span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;"><</span><a href="http://learningsparql.com/ns/data/book312" style="font-family: Calibri; font-size: medium;">http://learningsparql.com/ns/data/book312</a><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;">> dc:title "Jabez Easterbrook" . </span><br style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;" />
<span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;">}</span><br style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;" />
<span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;">WHERE</span><br style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;" />
<span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;">{}</span></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=407" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=407</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: Khalil A. <ka...@ne...> - 2014-04-09 18:22:14
|
I would be surprised if many people are using WP7 and SL4 for development any longer. BrightstarDB does have these targets, but I'm considering removing them too in favour of PCL builds that target WP8 and SL5. If you took them out of DotNetRDF, I would have the perfect excuse! :-) I have done some building with Xamarin libraries and I chose to go for Profile 158 which is portable-net45+sl5+wp80+win8+MonoAndroid10+MonoTouch10. I think that should be compatible with your selected profile (though the whole profile thing is just an opaque mess). I hit the problem of incompatible SL versions. If you take out the mono* targets you are forced to include SL4 (you end up with Profile 154 which is portable-net45+sl4+wp80+win8) Your approach of having the none mono profile *not* include SL at all is probably the way to go. I may well do the same with BrightstarDB. As for client profile, as far as I'm away this is all totally upward compatible with full profile, isn't it ? If so then I have no problem with those modules that don't need full profile being built with client profile. The only thing I would say is be careful of imposing a limitation on yourself that you will regret later! Cheers Kal On Wed, Apr 9, 2014 at 2:22 PM, Rob Vesse <rv...@do...> wrote: > 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 > > > ------------------------------------------------------------------------------ > 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-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > -- Kal Ahmed Director, Networked Planet Limited e: kal...@ne... w: www.networkedplanet.com |
48 messages has been excluded from this view by a project administrator.
