Menu
▾
▴
dotnetrdf-develop — Developer Discussion and Feature Request
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
(11) |
Mar
(17) |
Apr
(12) |
May
(2) |
Jun
(20) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(5) |
| 2011 |
Jan
(4) |
Feb
(1) |
Mar
(2) |
Apr
(2) |
May
(5) |
Jun
|
Jul
(12) |
Aug
(4) |
Sep
(5) |
Oct
(1) |
Nov
(38) |
Dec
(27) |
| 2012 |
Jan
(46) |
Feb
(182) |
Mar
(83) |
Apr
(22) |
May
(68) |
Jun
(47) |
Jul
(135) |
Aug
(84) |
Sep
(57) |
Oct
(45) |
Nov
(27) |
Dec
(61) |
| 2013 |
Jan
(59) |
Feb
(78) |
Mar
(66) |
Apr
(107) |
May
(27) |
Jun
(56) |
Jul
(53) |
Aug
(3) |
Sep
(19) |
Oct
(41) |
Nov
(44) |
Dec
(54) |
| 2014 |
Jan
(49) |
Feb
(72) |
Mar
(22) |
Apr
(41) |
May
(63) |
Jun
(27) |
Jul
(45) |
Aug
(12) |
Sep
(3) |
Oct
(8) |
Nov
(27) |
Dec
(16) |
| 2015 |
Jan
(3) |
Feb
(20) |
Mar
(6) |
Apr
(4) |
May
(15) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(16) |
May
(9) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <tr...@do...> - 2013-03-05 17:56:58
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Evaluate whether any of the BrightstarDB patches should be incorporated into the code base</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-03-05 05:56 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Ok, I think that 2371 was already incorporated into the codebase some time ago. Similar for 2369 since the Silverlight build works fine and that patch appears to be already in the codebase. As suspected 2156 is obsolete since the JoinedSet stuff got abandonded.</p>
<p>
</p>
<p>
I will look at 2029 and 2181 in more detail</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=332" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=332</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-03-05 17:56: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>rdfConvert does not propogate namespaces when converting from a Graph to a Dataset</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>2013-03-05 05:41 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Fixing the underlying issue <a href="http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=334">CORE-334</a> fixes this issue, fixed in commit <a href="https://bitbucket.org/dotnetrdf/dotnetrdf/commits/07b024239b872ddc474144bed1844fabaeb6f473">https://bitbucket.org/dotnetrdf/dotnetrdf/commits/07b024239b872ddc474144bed1844fabaeb6f473</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=333" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=333</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-03-05 17:42:55
|
<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>rdfConvert does not propogate namespaces when converting from a Graph to a Dataset</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>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=333" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=333</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-03-05 17:41:37
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>StoreHandler does not propogate namespaces</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-03-05 05:39 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Turns out to be a relatively simple fix, fixed in commit <a href="https://bitbucket.org/dotnetrdf/dotnetrdf/commits/07b024239b872ddc474144bed1844fabaeb6f473">https://bitbucket.org/dotnetrdf/dotnetrdf/commits/07b024239b872ddc474144bed1844fabaeb6f473</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=334" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=334</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-03-05 17:41:21
|
<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>StoreHandler does not propogate namespaces</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>Affected Milestone changed from "Unassigned" to "0.4.1 Beta"
</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=334" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=334</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-03-05 17:33:45
|
<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>StoreHandler does not propogate namespaces</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.0</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Handlers API</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>
In debugging <a href="http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?pid=333">TOOLS-333</a> it was determined that the root cause was that the StoreHandler used to load in RDF datasets didn't correctly propogate namespaces defined in the file to the graphs parsed from the data.</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=334" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=334</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-03-05 17:31:27
|
<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>rdfConvert does not propogate namespaces when converting from a Graph to a Dataset</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>Milestone:</b></td>
<td>1.0.0 Stable</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>rdfConvert</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>
Andrew Matthews reported an issue with rdfConvert losing prefixes when going from a Graph to a Dataset format - see <a href="http://answers.semanticweb.com/questions/21420/compression-settings-for-rdfconvertexe">http://answers.semanticweb.com/questions/21420/compression-settings-for-rdfconvertexe</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=333" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=333</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-03-05 09:20:59
|
<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>Evaluate whether any of the BrightstarDB patches should be incorporated into the code base</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Kal</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-03-05 09:20 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
You can almost certainly ignore the patches in the obsolete subdirectory. Take a look at patchlog.txt to see our notes on each patch. The last time we reviewed these against the dotNetRDF code base was some time around the 0.9 release of dotNetRDF.</p>
<p>
My take on the patches:</p>
<p>
2029_20120125_libraries_core_query_SPARQLExpressionParser.cs.patch : this is required to allow the use of long integer data types as RDF literals. The impact on other code seems pretty low.</p>
<p>
2156_20120320_libraries_core_query_algebra_Set.cs.patch : this has almost certainly been obsoleted by work done since then. I dont' think this is a critical patch</p>
<p>
2181_20120516_libraries_core_core.patch : this is a useful API extension that we made use of to enable BrightstarDB to make better use of the dotNetRDF parsers (I forget the exact context now, but I think it was to allow us to not use buffered token queues on the mobile build). It has a low impact on other code and I would recommend it.</p>
<p>
2369_20120813_libraries_core.silverlight_compatibility_SilverlightCompatability.cs.patch : this may have been done by now in the core dotNetRDF code, but it is a required patch to get the Silverlight build to work properly.</p>
<p>
2371_20120912_libraries_core_query_algebra_LazyBgp.cs.patch : Can't comment on this one, perhaps Graham can shed some light, but I think Graham and Rob had a bit of discussion around this when we first hit the issue.</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=332" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=332</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-03-05 05:23:32
|
<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>Evaluate whether any of the BrightstarDB patches should be incorporated into the code base</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.0</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Build, Release and Testing</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Normal</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I noticed that the recently opened source BrightstarDB has a bunch of patches for dotnetrdf at <a href="https://github.com/BrightstarDB/BrightstarDB/tree/master/src/dotnetrdf/patches">https://github.com/BrightstarDB/BrightstarDB/tree/master/src/dotnetrdf/patches</a></p>
<p>
Most of these seem to be against the old SVN so it is unclear which if any are still relevant, needs evaluating and determing whether any/all of them should be incorporated</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=332" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=332</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...> - 2013-03-04 19:59:09
|
Hey Kal Yes I agree, I think that this is likely more developer friendly in the long term Rob From: Kal Ahmed <ka...@ne...> Date: Monday, March 4, 2013 11:54 AM To: Rob Vesse <rv...@do...> Subject: Re: Portable Class Library update > Hi Rob, > > Just wondered if you have any further thoughts about the API thing before I > spend a lot of time hacking it one way or the other. The more I think about it > the more I think it makes sense to make the PCL API a subset of the full > dotNetRDF API and actually take out the APIs that require the File class - > e.g. if you want to see what it takes to port code that runs on the "native" > .NET 4.0 version of dotNetRDF over to a portable class library project for a > metro app, then you will get a bunch of compile time errors rather than having > to review your API usage call by call. > > K > > > On Fri, Mar 1, 2013 at 9:37 AM, Khalil Ahmed <ka...@ne...> wrote: >> Hi Rob, >> >> Thanks for the feedback. I do see what you mean about keeping the API >> consistent. My concern is that Intellisense won't pick up on a method not >> being implemented, which will mean that developers writing against the PCL >> version will have to be really careful about how they use the API to avoid >> run-time errors. I think that may be why MS decided that for their PCL stuff >> they would just take the APIs out entirely. I'm not sure if it is possible to >> / how to mark a method as not supported in PCL via docstrings, but if that is >> something that can be done, that may help - so I'll have a look to see if I >> can find anything. I'm happy to go either way on this, but I feel that the >> developer experience might be better if PCL only exposes a subset of the API >> rather than exposing APIs that throw PlatformNotSupportedExceptions (because >> there will be *a lot* of them :-) >> >> In terms of timing, I'm not totally sure yet how long it will take - VS says >> I've got about 200 compiler errors in the core library to resolve. Then I >> guess the next step will be to get as many of the tests working with PCL as >> the API changes allow. So there may be something that is more an untested >> alpha than a stable library with all the tests in place. I'll hopefully have >> a bit of time this weekend to have a bash through the remaining API changes >> (one way or the other) and that may then give a clearer view of if its then >> just a case of making a reduced unit test suite or if there are any more >> fundamental issues lurking in there. >> >> Cheers >> >> Kal >> >> >> On Thu, Feb 28, 2013 at 5:30 PM, Rob Vesse <rv...@do...> wrote: >>> Hey Kal >>> >>> Sounds excellent, comments inline: >>> >>> From: Kal Ahmed <ka...@ne...> >>> Date: Thursday, February 28, 2013 2:16 AM >>> To: Rob Vesse <rv...@do...> >>> Subject: Portable Class Library update >>> >>>> Hi Rob, >>>> >>>> I'm slowly making progress on the PCL version of the core library. There >>>> are a couple of things I want to run by you to make sure I don't spend a >>>> lot of time hacking up the API in ways you don't like :) >>>> >>>> 1) I'm targeting a pretty broad set of platforms, SL4+, .NET 4+, Windows >>>> Phone 7.1+ and Metro; rather than going for just the latest (e.g. SL5, .NET >>>> 4.5, WP8, Metro) the main downside I can see to that is no support for C#5 >>>> stuff like async/wait and maybe a few core windows APIs that are >>>> implemented in the later versions. >>> >>> I am happy with this, I specifically haven't used async/await anywhere in >>> the codebase so that we don't have to maintain two versions of the code to >>> work on the older and newer platforms. Regardless async/await is just >>> syntactic sugar around the .Net async support. >>> >>>> >>>> 2) PCL has no System.IO.File implementation. I guess because the different >>>> platforms do file I/O differently. As far as I can see there are two >>>> choices here: >>>> a) Create an abstraction and then implement it in a separate >>>> platform-specific assembly on each of the platforms (this is the approach >>>> that the PCLContrib folks have taken) >>>> b) Remove the dependency on the File class from the portable build of >>>> dotNetRDF. What this means in effect is using #defines to remove all APIs >>>> that take a file name and leave only those that take a Stream or Reader >>>> class. >>>> I have opted for (b) because it will leave a smaller, cleaner API - it >>>> removes a bit of utility and forces the app to do the stream management and >>>> just pass us streams. >>> >>> Yes I like (b) as an option >>> >>> Are you just eliminating methods entirely in those builds or are you going >>> down the path of having them throw a PlatformNotSupportedException? I don't >>> mind if you do the former but I think long term it would be nicer to users >>> if we do everything the latter way as it means the API looks identical >>> across platforms. Ideally we should only be eliminating methods entirely >>> where they reference a type that is not available on a platform. If they >>> merely use something internally that is not available we should prefer >>> PlatformNotSupportedException. >>> >>> I realize that I am guilty of doing the former for stuff like the Storage >>> API so I will file myself an issue to remedy that :) >>> >>>> >>>> >>>> 3) For some platforms async versions of APIs will probably be useful. I've >>>> not really made a start on that yet and I don't plan to until I have some >>>> binaries compiled and tested with the existing synchronous APIs - my >>>> feeling is that app developers can wrap the synchronous calls up if they >>>> need async for now. >>> >>> Yes, there are async APIs for some obvious things but these are fairly >>> limited. Longer term we should discuss what else might need an async API >>> >>>> >>>> 4) I have added a couple of #define symbols. PORTABLE indicates a PCL build >>>> (though the portable project also sets the SILVERLIGHT flag to avoid having >>>> to change masses of #if !SILVERLIGHT conditions). NO_FILE is used to >>>> conditionally drop those methods that rely on System.IO.File to open a >>>> stream. >>> >>> Ok, per my earlier comment it may make more sense to comment out the >>> implementation and throw a PlatformNotSupportedException advising users of >>> the alternative API to use instead. >>> >>>> >>>> I still have quite a lot of typing to do to get rid of those pesky file >>>> APIs (and it is mostly just typing), but I hope that in a few days I'll be >>>> able to at push something functional into my clone of the source tree. >>>> >>>> If you have strong feelings about the file APIs or about the need for >>>> adding async versions of APIs, now would be a good time to let me know :) >>> >>> Bar the point on removing methods vs throwing PlatformNotSupported all >>> sounds good. >>> >>> Do you have a rough idea when this might be ready? It would be awesome to >>> get this into the 1.0.0 release if we can >>> >>> Rob >>> >>>> >>>> Cheers >>>> >>>> Kal >>>> -- >>>> Kal Ahmed >>>> Director, Networked Planet Limited >>>> e: kal...@ne... >>>> w: www.networkedplanet.com <http://www.networkedplanet.com> >> >> >> >> -- >> Kal Ahmed >> Director, Networked Planet Limited >> e: kal...@ne... >> w: www.networkedplanet.com <http://www.networkedplanet.com> > > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com <http://www.networkedplanet.com> |
|
From: <tr...@do...> - 2013-03-02 18:03: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>Integrate documentation repository into wiki</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Website, Documentation and Infrastructure</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-02-28 06:29 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
This has now been completed, all relevant content is exposed via wiki pages</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=321" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=321</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...> - 2013-03-02 17:05:06
|
Hey Kal Sounds excellent, comments inline: From: Kal Ahmed <ka...@ne...> Date: Thursday, February 28, 2013 2:16 AM To: Rob Vesse <rv...@do...> Subject: Portable Class Library update > Hi Rob, > > I'm slowly making progress on the PCL version of the core library. There are a > couple of things I want to run by you to make sure I don't spend a lot of time > hacking up the API in ways you don't like :) > > 1) I'm targeting a pretty broad set of platforms, SL4+, .NET 4+, Windows Phone > 7.1+ and Metro; rather than going for just the latest (e.g. SL5, .NET 4.5, > WP8, Metro) the main downside I can see to that is no support for C#5 stuff > like async/wait and maybe a few core windows APIs that are implemented in the > later versions. I am happy with this, I specifically haven't used async/await anywhere in the codebase so that we don't have to maintain two versions of the code to work on the older and newer platforms. Regardless async/await is just syntactic sugar around the .Net async support. > > 2) PCL has no System.IO.File implementation. I guess because the different > platforms do file I/O differently. As far as I can see there are two choices > here: > a) Create an abstraction and then implement it in a separate > platform-specific assembly on each of the platforms (this is the approach that > the PCLContrib folks have taken) > b) Remove the dependency on the File class from the portable build of > dotNetRDF. What this means in effect is using #defines to remove all APIs that > take a file name and leave only those that take a Stream or Reader class. > I have opted for (b) because it will leave a smaller, cleaner API - it removes > a bit of utility and forces the app to do the stream management and just pass > us streams. Yes I like (b) as an option Are you just eliminating methods entirely in those builds or are you going down the path of having them throw a PlatformNotSupportedException? I don't mind if you do the former but I think long term it would be nicer to users if we do everything the latter way as it means the API looks identical across platforms. Ideally we should only be eliminating methods entirely where they reference a type that is not available on a platform. If they merely use something internally that is not available we should prefer PlatformNotSupportedException. I realize that I am guilty of doing the former for stuff like the Storage API so I will file myself an issue to remedy that :) > > > 3) For some platforms async versions of APIs will probably be useful. I've not > really made a start on that yet and I don't plan to until I have some binaries > compiled and tested with the existing synchronous APIs - my feeling is that > app developers can wrap the synchronous calls up if they need async for now. Yes, there are async APIs for some obvious things but these are fairly limited. Longer term we should discuss what else might need an async API > > 4) I have added a couple of #define symbols. PORTABLE indicates a PCL build > (though the portable project also sets the SILVERLIGHT flag to avoid having to > change masses of #if !SILVERLIGHT conditions). NO_FILE is used to > conditionally drop those methods that rely on System.IO.File to open a stream. Ok, per my earlier comment it may make more sense to comment out the implementation and throw a PlatformNotSupportedException advising users of the alternative API to use instead. > > I still have quite a lot of typing to do to get rid of those pesky file APIs > (and it is mostly just typing), but I hope that in a few days I'll be able to > at push something functional into my clone of the source tree. > > If you have strong feelings about the file APIs or about the need for adding > async versions of APIs, now would be a good time to let me know :) Bar the point on removing methods vs throwing PlatformNotSupported all sounds good. Do you have a rough idea when this might be ready? It would be awesome to get this into the 1.0.0 release if we can Rob > > Cheers > > Kal > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com <http://www.networkedplanet.com> |
|
From: <dot...@li...> - 2013-02-28 18:33:20
|
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: Upgrade VDS.Web.Server dependency to 1.0.1 to pick up fix for URL decoding issue and thus fix TOOLS-324 (Bitbucket) 3. commit/dotnetrdf: 7 new changesets (Bitbucket) 4. commit/dotnetrdf: 5 new changesets (Bitbucket) 5. commit/dotnetrdf: 6 new changesets (Bitbucket) 6. commit/dotnetrdf: 3 new changesets (Bitbucket) 7. commit/dotnetrdf: 4 new changesets (Bitbucket) 8. commit/dotnetrdf: rvesse: Forgot to save final changes to XML comments (CORE-319) (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Tue, 26 Feb 2013 00:54:22 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d075a3110965/ changeset: d075a3110965 user: rvesse date: 2013-02-26 01:47:00 summary: Appropriately bump library versions to 1.0.0.0, thought I had done this previously affected #: 18 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c15b127f7c43/ changeset: c15b127f7c43 user: rvesse date: 2013-02-26 01:53:29 summary: Fix for TOOLS-323, rdfServer now correctly POSTs updates 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: Tue, 26 Feb 2013 18:04:22 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Upgrade VDS.Web.Server dependency to 1.0.1 to pick up fix for URL decoding issue and thus fix TOOLS-324 To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1fc0a354d1b7/ changeset: 1fc0a354d1b7 user: rvesse date: 2013-02-26 19:03:56 summary: Upgrade VDS.Web.Server dependency to 1.0.1 to pick up fix for URL decoding issue and thus fix TOOLS-324 affected #: 6 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: Tue, 26 Feb 2013 20:06:44 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 7 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 7 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/899288ca4f97/ changeset: 899288ca4f97 user: rvesse date: 2013-02-26 20:31:14 summary: Some XML comment clean up affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/91205f5ae06c/ changeset: 91205f5ae06c user: rvesse date: 2013-02-26 20:32:39 summary: Fix missing references for some utilities affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/be4bbd3bf2f0/ changeset: be4bbd3bf2f0 user: rvesse date: 2013-02-26 20:42:49 summary: Fix up some more XML comments (CORE-319) affected #: 12 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/df48b1457b01/ changeset: df48b1457b01 user: rvesse date: 2013-02-26 20:54:26 summary: Add some missing XML comments (CORE-319) affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/983e807e44ea/ changeset: 983e807e44ea user: rvesse date: 2013-02-26 20:59:07 summary: Finish XML comments for HtmlTextWriter (CORE-319) affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1a97531e4567/ changeset: 1a97531e4567 user: rvesse date: 2013-02-26 21:03:09 summary: Add XML comments for HtmlTextWriter (CORE-319) affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/826cd8bb0207/ changeset: 826cd8bb0207 user: rvesse date: 2013-02-26 21:06:26 summary: Add XML commnets for HtmlTextWriterStyle (CORE-319) affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 4 Date: Tue, 26 Feb 2013 20:34:06 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 5 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 5 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/af45ff74842d/ changeset: af45ff74842d user: rvesse date: 2013-02-26 21:12:22 summary: Add XML comments for HtmlTextWriterTarg (CORE-319) affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c188ad7e3652/ changeset: c188ad7e3652 user: rvesse date: 2013-02-26 21:16:01 summary: Add some missing XML comments (CORE-319) affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/102599134f98/ changeset: 102599134f98 user: rvesse date: 2013-02-26 21:16:53 summary: Remove defunct internal class InternalXmlWriter affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/34f5b06a03a4/ changeset: 34f5b06a03a4 user: rvesse date: 2013-02-26 21:30:08 summary: Clean up a bunch more XML comments (CORE-319) affected #: 15 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d84650a4e168/ changeset: d84650a4e168 user: rvesse date: 2013-02-26 21:33:51 summary: Clean up yet more XML comments (CORE-319) affected #: 6 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 5 Date: Wed, 27 Feb 2013 01:18:56 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 6 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 6 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2b01baa09439/ changeset: 2b01baa09439 user: rvesse date: 2013-02-27 01:31:20 summary: Resolve all resolvable XML doc warnings for Core Library Client Profile build (CORE-319) affected #: 14 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f755f555198a/ changeset: f755f555198a user: rvesse date: 2013-02-27 01:33:51 summary: Resolve all resolvable XML doc warnings for Core Library builds (CORE-319) affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6ec5904d44a4/ changeset: 6ec5904d44a4 user: rvesse date: 2013-02-27 01:36:34 summary: Resolve all resolvable XML doc warnings for Data.Virtuoso and Query.FullText builds (CORE-319) affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/901dcf265990/ changeset: 901dcf265990 user: rvesse date: 2013-02-27 01:39:01 summary: Fix a missimg using statement that was causing an XML doc warning (CORE-319) affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5b23ff8ce56d/ changeset: 5b23ff8ce56d user: rvesse date: 2013-02-27 02:14:05 summary: Start adding missing XML documentation to rdfEditor.Core (CORE-319) affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/166c5eb8e61f/ changeset: 166c5eb8e61f user: rvesse date: 2013-02-27 02:18:38 summary: More documentation comments for rdfEditor.Core (CORE-319) affected #: 6 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: Wed, 27 Feb 2013 20:51:41 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 3 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/60ffbe984ee3/ changeset: 60ffbe984ee3 user: rvesse date: 2013-02-27 21:14:07 summary: Add XML comments for Document class of rdfEditor.Core (CORE-319) affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4ae9c8d5b5c5/ changeset: 4ae9c8d5b5c5 user: rvesse date: 2013-02-27 21:35:32 summary: Add XML comments for the DocumentManager class of rdfEditor.Core (CORE-319) affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c5e18d8a178e/ changeset: c5e18d8a178e user: rvesse date: 2013-02-27 21:51:24 summary: Add lots more XML comments to rdfEditor.Core (CORE-319) 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: 7 Date: Thu, 28 Feb 2013 01:13:45 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 4 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 4 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/90556c19d5f2/ changeset: 90556c19d5f2 user: rvesse date: 2013-02-28 01:30:41 summary: Add XML comments for various auto-completers in rdfEditor.Core (CORE-319) affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/782f76ab5a45/ changeset: 782f76ab5a45 user: rvesse date: 2013-02-28 01:47:11 summary: Yet more XML comments for rdfEditor.Core (CORE-319) affected #: 8 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/84a9de337242/ changeset: 84a9de337242 user: rvesse date: 2013-02-28 02:02:04 summary: Fix all resolvable XML comment warnings with rdfEditor.Core (CORE-319) affected #: 8 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/37e4ef1b7e5b/ changeset: 37e4ef1b7e5b user: rvesse date: 2013-02-28 02:13:28 summary: About half the XML comments for rdfEditor.Core.Wpf (CORE-319) 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: 8 Date: Thu, 28 Feb 2013 18:16:19 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Forgot to save final changes to XML comments (CORE-319) To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/99a240510fda/ changeset: 99a240510fda user: rvesse date: 2013-02-28 19:15:58 summary: Forgot to save final changes to XML comments (CORE-319) 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. ------------------------------ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 5, Issue 3 *********************************************** |
|
From: <tr...@do...> - 2013-02-28 18:32: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>Integrate documentation repository into wiki</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Website, Documentation and Infrastructure</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 "Completed"
</li>
<li>Progress changed from "60 %" 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=321" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=321</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-02-26 19:51:07
|
<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>Add a IsTypedAs() extension method for IValuedNode</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.1</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Low</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
IsTypedAs() would be an extension method useful in SPARQL expression and operator evaluation which determines whether a node has a given type.</p>
<p>
It may also be useful to include a IsValidNumeric() extension method</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=328" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=328</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-02-26 18:22:17
|
<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>Switch to SparseTrie for URI Interning</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.1</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Core API</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>
Switching to using SparseTrie over the standard Trie implementation for URI Interning should give significant memory and performance improvements.</p>
<p>
However SparseTrie is new and relatively untested so we will do this post 1.0.0</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=330" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=330</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-02-26 18:20:42
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add a HasLanguage and HasDataType properties to ILiteralNode</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.9.0 Beta</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Core API</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>
If we want to properly support RDF 1.1 where language specified literals have implicit datatype of rdf:langString we need to change how we check whether a literal has a language tag and datatype at various points where we process it esp. wrt. serialization</p>
<p>
Adding these new properties would make this much easier</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=329" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=329</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-02-26 18:19:06
|
<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 a IsTypedAs() extension method for IValuedNode</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>Related issue changed from "" to "Added"
</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=328" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=328</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-02-26 18:16:04
|
<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>Use null instead of RdfQueryException to propogate type errors in SPARQL Expression Evaluation</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.1.0</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>Refactor</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Currently we use RdfQueryException to propogate type errors through expression evaluation. However using exceptions to control flow is always more expensive than other alternatives.</p>
<p>
</p>
<p>
We should instead be using null to denote an error/unbound. We will need to carefully comb the expressions codebase in order to make this refactor to ensure that code treats nulls correctly as errors. There may also be some places where it is still legitimate to throw an error.</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=327" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=327</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-02-26 18:13:49
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Support durations in all comparison operators</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>Parent issue changed from "" to "Added"
</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=326" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=326</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-02-26 18:12:55
|
<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>Support durations in all comparison operators</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.1</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Normal</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>New Feature</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Once <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=325">CORE-325</a> has been resolved we should add support for using these operators on durations since we already allow this for the existing ISparqlOperator based operators</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=326" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=326</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-02-26 18:09: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>Make all SPARQL Operators extensible</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.1</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Refactor</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Currently only +, -, * and / are managed by the ISparqlOperator APIs and as such are the only operators that may be extended</p>
<p>
This task is to refactor the implementations of the rest of the operators i.e. =, !=, <, <=, >, >= and ! onto the ISparqlOperator APIs</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=325" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=325</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-02-26 18:07:59
|
<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>SPARQL Updates do not work through rdfServer</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>2013-02-26 06:06 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Fixed by picking up VDS.Web.Server 1.0.1 which fixes the issue in URL decoding</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=324" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=324</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-02-26 18:07:57
|
<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>SPARQL Updates do not work through rdfServer</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>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=324" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=324</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-02-26 18:07:26
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SPARQL Updates do not work through rdfServer</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>Title changed from "Updated do not work through rdfServer" to "SPARQL Updates do not work through rdfServer"
</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=324" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=324</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.
