Menu
▾
▴
dotnetrdf-develop
|
From: Rob V. <rv...@do...> - 2013-04-19 21:18:15
|
Hey All I was originally going to try and push out 1.0.0 but I have decided to delay by another week or two to try and get some extra stuff done. In particular some of the stuff in the CORE-314 branch (latest Turtle spec support) highlighted another error in GraphMatcher and some general bugs in Turtle parsing beyond those related to meeting the latest spec. I have code in that branch passing the bulk of the tests (259 passed, 14 failed, 15 indeterminate) and nothing fails fatally (I.e. stack traces) right now so it's already in fairly good shape. I will likely merge what I have so far to default anyway since it improves Turtle support even if it isn't yet perfect and fixes the aforementioned issues. There is also the CORE-346 branch which has a new ReadWriteSparqlConnector which is the update capable version of SparqlConnector which is stable and passing the new tests I wrote for it. I would also like to at least look at CORE-349 (a bug with * in property paths) in case there is a trivial fix there. Anything else small and self contained that people would like to get into 1.0.0 if they can? Rob |
|
From: Tomasz P. <tom...@gm...> - 2013-04-21 06:48:55
|
I was thinking that maybe the fluent queries could be merged back to trunk. Even though incomplete, should be in a stable enought state and we could get some user feedback. Other than that I noticed that latest Turtle/Sparql changes caused Silverlight builds to fail. I was able to fix one of those issues in commit 085ea4cc65d7 (missing Char methods in SL), but I'm not sure how to approach the other (you used SparqlConnectorLoadMethod in StorageFactory). Looks like like I could comment it out but I'm not sure. Tom On Fri, Apr 19, 2013 at 11:17 PM, Rob Vesse <rv...@do...> wrote: > Hey All > > I was originally going to try and push out 1.0.0 but I have decided to delay > by another week or two to try and get some extra stuff done. > > In particular some of the stuff in the CORE-314 branch (latest Turtle spec > support) highlighted another error in GraphMatcher and some general bugs in > Turtle parsing beyond those related to meeting the latest spec. I have code > in that branch passing the bulk of the tests (259 passed, 14 failed, 15 > indeterminate) and nothing fails fatally (I.e. stack traces) right now so > it's already in fairly good shape. I will likely merge what I have so far > to default anyway since it improves Turtle support even if it isn't yet > perfect and fixes the aforementioned issues. > > There is also the CORE-346 branch which has a new ReadWriteSparqlConnector > which is the update capable version of SparqlConnector which is stable and > passing the new tests I wrote for it. > > I would also like to at least look at CORE-349 (a bug with * in property > paths) in case there is a trivial fix there. > > Anything else small and self contained that people would like to get into > 1.0.0 if they can? > > Rob > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Rob V. <rv...@do...> - 2013-04-30 20:49:47
|
Hey Tom Thanks for fixing these things I ended up merging the CharHelper stuff back into UnicodeSpecsHelper since it made more sense for them to be there. Yes the SparqlConnectorLoadMethod is not necessary under Silverlight because the two classes that use it are not supported on that platform. I am going to save fluent query for 1.0.1, as part of 1.0.1 I want to get your NUnit changes merged into default and convert over fluent-query test infrastructure as part of that. That will also give me time to play with fluent query properly and write up/transfer documentation for it into the main wiki I think 1.0.0 is now ready to go, I have pushed off some stuff that could have been worked on to later releases in the interests of getting a new release out at the end of the week since there are many bug fixes and improvements I would like to get into the hands of users before starting to pump in new features again. Rob On 4/20/13 11:48 PM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >I was thinking that maybe the fluent queries could be merged back to >trunk. Even though incomplete, should be in a stable enought state and >we could get some user feedback. > >Other than that I noticed that latest Turtle/Sparql changes caused >Silverlight builds to fail. I was able to fix one of those issues in >commit 085ea4cc65d7 (missing Char methods in SL), but I'm not sure how >to approach the other (you used SparqlConnectorLoadMethod in >StorageFactory). Looks like like I could comment it out but I'm not >sure. > >Tom > >On Fri, Apr 19, 2013 at 11:17 PM, Rob Vesse <rv...@do...> wrote: >> Hey All >> >> I was originally going to try and push out 1.0.0 but I have decided to >>delay >> by another week or two to try and get some extra stuff done. >> >> In particular some of the stuff in the CORE-314 branch (latest Turtle >>spec >> support) highlighted another error in GraphMatcher and some general >>bugs in >> Turtle parsing beyond those related to meeting the latest spec. I have >>code >> in that branch passing the bulk of the tests (259 passed, 14 failed, 15 >> indeterminate) and nothing fails fatally (I.e. stack traces) right now >>so >> it's already in fairly good shape. I will likely merge what I have so >>far >> to default anyway since it improves Turtle support even if it isn't yet >> perfect and fixes the aforementioned issues. >> >> There is also the CORE-346 branch which has a new >>ReadWriteSparqlConnector >> which is the update capable version of SparqlConnector which is stable >>and >> passing the new tests I wrote for it. >> >> I would also like to at least look at CORE-349 (a bug with * in property >> paths) in case there is a trivial fix there. >> >> Anything else small and self contained that people would like to get >>into >> 1.0.0 if they can? >> >> Rob >> >> >>------------------------------------------------------------------------- >>----- >> Precog is a next-generation analytics platform capable of advanced >> analytics on semi-structured data. The platform includes APIs for >>building >> apps and a phenomenal toolset for data science. Developers can use >> our toolset for easy data analysis & visualization. Get a free account! >> http://www2.precog.com/precogplatform/slashdotnewsletter >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >-------------------------------------------------------------------------- >---- >Precog is a next-generation analytics platform capable of advanced >analytics on semi-structured data. The platform includes APIs for building >apps and a phenomenal toolset for data science. Developers can use >our toolset for easy data analysis & visualization. Get a free account! >http://www2.precog.com/precogplatform/slashdotnewsletter >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X