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: Rob V. <rv...@do...> - 2013-03-15 20:45:35
|
Hey Yes I think using the Fluent Query API for helping to convert the RDF representation back into queries would likely make life much easier. Rob On 3/15/13 1:19 PM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi Kevin, Rob > >I have been thinking about SPIN for a very long time. And I have >actually very recently read somehere on answeres.semanticweb.com about >using SPIN to implement OWL reasoning. > >Ever since I had started that fluent SPARQL I thought it could >actually be a good base to easily go from SPIN RDF representation to >actual queries. > >I know that the implementation is far from complete. I have been busy >with a multitude of other tasks but if it could prove useful in >implementing SPIN it would be great. Actually one of my goals I did >have in mind was to use Fluent SPARQL for SPIN. Especially that >working with query strings or low-level SPARQL API will be far from >developer-friendly in te long run IMO. > >Kevin, please have a look at my fork, where I have been documenting my >work on a wiki: http://bitbucket.org/romanticweb/dotnetrdf/wiki/Home > >What do you guys think? > >Thank, >Tom > >On Fri, Mar 15, 2013 at 8:57 PM, Rob Vesse <rv...@do...> wrote: >> Hey Kevin >> >> Discussion inline: >> >> From: Kevin <ke...@th...> >> Date: Wednesday, March 13, 2013 7:40 PM >> To: Rob Vesse <rv...@do...> >> Subject: Integrating SPIN into dotnetrdf >> >> Rob, >> >> >> >> First thank you for your quality work you have done with the dotnetrdf >> project. I have seen a few different posts about your initiative to >> integrate SPIN into dotnetrdf (ie. SPIN Post). After much reading on >>the >> subject it really seems that SPIN would really propel/complement >>dotnetrdf. >> I believe SPIN not only makes up for the missing OWL inference (Via SPIN >> OWL-RL implementation), it also can expand to suit the modelers >>imagination. >> The fact that the rules are in SPARQL makes for an unbeatable solution. >> Should it matter my current effort involves query a Virtuoso database >>(Some >> owl support) with dotnetrdf. I would really appreciate you taking a >>look at >> the questions below: >> >> >> >> -Have you made any further progress on integrating SPIN into dotnetrdf? >> Would you allow me to have the source code in its current state? Could >>I >> possibly be a contributor on this cause as I am not really equipped for >>the >> full task? In any case I would appreciate any source code which I >>could use >> as a learning tool. >> >> >> No I haven't had time to do anything on SPIN for a long time now. I've >>been >> primarily concentrating on getting core features stabilized such as the >> SPARQL engine which are obviously fairly key to building stuff like >>SPIN on >> top. >> >> However I still don't have time to work on SPIN directly so if you want >>to >> work on this please feel free, find the code in the mercurial >>repository at >> https://bitbucket.org/dotnetrdf/dotnetrdf >> >> The previous and very minimal SPIN stub is under Libraries\Query\Spin, >> create your own fork and then you can send pull requests as and when you >> have something to >> >> The key things that need to be done to get the core of SPIN implemented >>are >> as follows: >> >> Update the current spin-sparql-syntax.ttl to a current version, it >>likely >> doesn't represent the current version of the spec (this is primarily a >> convenience reference for developers) >> Finish the existing stubs for converting queries into their SPIN RDF >> representation (see SpinSyntax.cs) >> Write code to turn a RDF encoding of a SPIN query into a query >> >> The middle one would be the easiest to start with since there is already >> some partial stubs to get you started. >> >> >> >> -From the available TopQuadrant documentation I have tried to deduce how >> dotnetrdf might implement SPIN. According to SPIN tutrial, TopBraid >>finds >> all SPIN inferecer rules and runs them when you hit play. Would >>dotnetrdf >> SPIN inferencer only run the rules that are associated with the class >> structure being queried? Basically I am confused how dotnetrdf decides >> when/how/which SPIN rules to run for a given query. >> >> >> That's an implementation detail, we would control how and when rules get >> run. We need to get the basic implementation of SPIN done first before >>this >> aspect of things gets implemented anyway. >> >> >> >> -How much of SPIN could dotnetrdf possibly support.? It appears SPIN >> contains Inference Rules, Constraint Checking, and ability to Isolate >>rules >> for certain conditions. Also the TopBraid tool seems to have >>"User-Defined >> SPARQL functions" and "SPIN Query Templates". I imagine dotnetrdf would >> have to keep up with any SPIN improvements. >> >> >> All of those are supportable in some shape of form, until we have the >>core >> of SPIN up and running we can't really implement those. Most of those >> features run on top of the SPIN core and so will ultimately just be >> implementation details once we have a core to build upon. User defined >> SPARQL functions are basically just SPARQL queries that return a single >> value and query templates are just parameterized queries both of which >>the >> existing SPARQL engine is capable of supporting in one way or another. >>So >> it is just a case of exposing that functionality in the SPIN style. >> >> Hope this is enough to get you started, if not please let us know, >> >> Rob >> >> >> >> Regards, >> >> Kevin >> >> >> >>------------------------------------------------------------------------- >>----- >> 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_mar >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >-------------------------------------------------------------------------- >---- >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics >Download AppDynamics Lite for free today: >http://p.sf.net/sfu/appdyn_d2d_mar >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2013-03-15 20:20:08
|
Hi Kevin, Rob I have been thinking about SPIN for a very long time. And I have actually very recently read somehere on answeres.semanticweb.com about using SPIN to implement OWL reasoning. Ever since I had started that fluent SPARQL I thought it could actually be a good base to easily go from SPIN RDF representation to actual queries. I know that the implementation is far from complete. I have been busy with a multitude of other tasks but if it could prove useful in implementing SPIN it would be great. Actually one of my goals I did have in mind was to use Fluent SPARQL for SPIN. Especially that working with query strings or low-level SPARQL API will be far from developer-friendly in te long run IMO. Kevin, please have a look at my fork, where I have been documenting my work on a wiki: http://bitbucket.org/romanticweb/dotnetrdf/wiki/Home What do you guys think? Thank, Tom On Fri, Mar 15, 2013 at 8:57 PM, Rob Vesse <rv...@do...> wrote: > Hey Kevin > > Discussion inline: > > From: Kevin <ke...@th...> > Date: Wednesday, March 13, 2013 7:40 PM > To: Rob Vesse <rv...@do...> > Subject: Integrating SPIN into dotnetrdf > > Rob, > > > > First thank you for your quality work you have done with the dotnetrdf > project. I have seen a few different posts about your initiative to > integrate SPIN into dotnetrdf (ie. SPIN Post). After much reading on the > subject it really seems that SPIN would really propel/complement dotnetrdf. > I believe SPIN not only makes up for the missing OWL inference (Via SPIN > OWL-RL implementation), it also can expand to suit the modelers imagination. > The fact that the rules are in SPARQL makes for an unbeatable solution. > Should it matter my current effort involves query a Virtuoso database (Some > owl support) with dotnetrdf. I would really appreciate you taking a look at > the questions below: > > > > -Have you made any further progress on integrating SPIN into dotnetrdf? > Would you allow me to have the source code in its current state? Could I > possibly be a contributor on this cause as I am not really equipped for the > full task? In any case I would appreciate any source code which I could use > as a learning tool. > > > No I haven't had time to do anything on SPIN for a long time now. I've been > primarily concentrating on getting core features stabilized such as the > SPARQL engine which are obviously fairly key to building stuff like SPIN on > top. > > However I still don't have time to work on SPIN directly so if you want to > work on this please feel free, find the code in the mercurial repository at > https://bitbucket.org/dotnetrdf/dotnetrdf > > The previous and very minimal SPIN stub is under Libraries\Query\Spin, > create your own fork and then you can send pull requests as and when you > have something to > > The key things that need to be done to get the core of SPIN implemented are > as follows: > > Update the current spin-sparql-syntax.ttl to a current version, it likely > doesn't represent the current version of the spec (this is primarily a > convenience reference for developers) > Finish the existing stubs for converting queries into their SPIN RDF > representation (see SpinSyntax.cs) > Write code to turn a RDF encoding of a SPIN query into a query > > The middle one would be the easiest to start with since there is already > some partial stubs to get you started. > > > > -From the available TopQuadrant documentation I have tried to deduce how > dotnetrdf might implement SPIN. According to SPIN tutrial, TopBraid finds > all SPIN inferecer rules and runs them when you hit play. Would dotnetrdf > SPIN inferencer only run the rules that are associated with the class > structure being queried? Basically I am confused how dotnetrdf decides > when/how/which SPIN rules to run for a given query. > > > That's an implementation detail, we would control how and when rules get > run. We need to get the basic implementation of SPIN done first before this > aspect of things gets implemented anyway. > > > > -How much of SPIN could dotnetrdf possibly support.? It appears SPIN > contains Inference Rules, Constraint Checking, and ability to Isolate rules > for certain conditions. Also the TopBraid tool seems to have "User-Defined > SPARQL functions" and "SPIN Query Templates". I imagine dotnetrdf would > have to keep up with any SPIN improvements. > > > All of those are supportable in some shape of form, until we have the core > of SPIN up and running we can't really implement those. Most of those > features run on top of the SPIN core and so will ultimately just be > implementation details once we have a core to build upon. User defined > SPARQL functions are basically just SPARQL queries that return a single > value and query templates are just parameterized queries both of which the > existing SPARQL engine is capable of supporting in one way or another. So > it is just a case of exposing that functionality in the SPIN style. > > Hope this is enough to get you started, if not please let us know, > > Rob > > > > Regards, > > Kevin > > > ------------------------------------------------------------------------------ > 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_mar > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Rob V. <rv...@do...> - 2013-03-15 19:58:27
|
Hey Kevin Discussion inline: From: Kevin <ke...@th...> Date: Wednesday, March 13, 2013 7:40 PM To: Rob Vesse <rv...@do...> Subject: Integrating SPIN into dotnetrdf > Rob, > > First thank you for your quality work you have done with the dotnetrdf > project. I have seen a few different posts about your initiative to integrate > SPIN into dotnetrdf (ie. SPIN Post > <http://answers.semanticweb.com/questions/537/experiences-with-spin> ). After > much reading on the subject it really seems that SPIN would really > propel/complement dotnetrdf. I believe SPIN not only makes up for the missing > OWL inference (Via SPIN OWL-RL implementation), it also can expand to suit the > modelers imagination. The fact that the rules are in SPARQL makes for an > unbeatable solution. Should it matter my current effort involves query a > Virtuoso database (Some owl support) with dotnetrdf. I would really > appreciate you taking a look at the questions below: > > -Have you made any further progress on integrating SPIN into dotnetrdf? Would > you allow me to have the source code in its current state? Could I possibly > be a contributor on this cause as I am not really equipped for the full task? > In any case I would appreciate any source code which I could use as a learning > tool. No I haven't had time to do anything on SPIN for a long time now. I've been primarily concentrating on getting core features stabilized such as the SPARQL engine which are obviously fairly key to building stuff like SPIN on top. However I still don't have time to work on SPIN directly so if you want to work on this please feel free, find the code in the mercurial repository at https://bitbucket.org/dotnetrdf/dotnetrdf The previous and very minimal SPIN stub is under Libraries\Query\Spin, create your own fork and then you can send pull requests as and when you have something to The key things that need to be done to get the core of SPIN implemented are as follows: * Update the current spin-sparql-syntax.ttl to a current version, it likely doesn't represent the current version of the spec (this is primarily a convenience reference for developers) * Finish the existing stubs for converting queries into their SPIN RDF representation (see SpinSyntax.cs) * Write code to turn a RDF encoding of a SPIN query into a query The middle one would be the easiest to start with since there is already some partial stubs to get you started. > > -From the available TopQuadrant documentation I have tried to deduce how > dotnetrdf might implement SPIN. According to SPIN tutrial > <http://dallemang.typepad.com/my_weblog/2010/08/extending-owl-rl-.html> , > TopBraid finds all SPIN inferecer rules and runs them when you hit play. > Would dotnetrdf SPIN inferencer only run the rules that are associated with > the class structure being queried? Basically I am confused how dotnetrdf > decides when/how/which SPIN rules to run for a given query. That's an implementation detail, we would control how and when rules get run. We need to get the basic implementation of SPIN done first before this aspect of things gets implemented anyway. > > -How much of SPIN could dotnetrdf possibly support.? It appears SPIN contains > Inference Rules, Constraint Checking, and ability to Isolate rules for certain > conditions. Also the TopBraid tool seems to have "User-Defined SPARQL > functions" and "SPIN Query Templates". I imagine dotnetrdf would have to keep > up with any SPIN improvements. All of those are supportable in some shape of form, until we have the core of SPIN up and running we can't really implement those. Most of those features run on top of the SPIN core and so will ultimately just be implementation details once we have a core to build upon. User defined SPARQL functions are basically just SPARQL queries that return a single value and query templates are just parameterized queries both of which the existing SPARQL engine is capable of supporting in one way or another. So it is just a case of exposing that functionality in the SPIN style. Hope this is enough to get you started, if not please let us know, Rob > > Regards, > Kevin |
|
From: <tr...@do...> - 2013-03-12 18:32:12
|
<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>Ontology API does not return OWL Datatype properties correctly</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=339" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=339</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-11 22:32:00
|
<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>Ontology API does not return OWL Datatype properties correctly</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>Ontology API</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>
A user reported an issue on the mailing list of not being able to select OWL datatype properties with the Ontology API - <a href="http://sourceforge.net/mailarchive/forum.php?thread_name=1363038847.67805.YahooMailNeo%40web124505.mail.ne1.yahoo.com&forum_name=dotnetrdf-support">http://sourceforge.net/mailarchive/forum.php?thread_name=1363038847.67805.YahooMailNeo%40web124505.mail.ne1.yahoo.com&forum_name=dotnetrdf-support</a></p>
<p>
A quick look in the code shows that the constant for the OWL datatype property URI is incorrect, we need to fix this and add more tests for this part of the API to catch any similiar issues.</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=339" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=339</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-11 20:37:53
|
I wanted to get the release out for the end of the month so you have a couple of weeks Rob On 3/11/13 1:33 PM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi Rob, > >Sure, I'd like to contribute the Configuration API changes. I had some >other tasks during the weekend but this won't take too long. What's my >deadline for this? :) > >Tom > >On Mon, Mar 11, 2013 at 8:51 PM, Rob Vesse <rv...@do...> wrote: >> Hey All >> >> Here is the current status on 1.0.0 as I see it, if anyone has anything >>else >> they want to get into 1.0.0 now would be a good time to speak up >> >> In terms of new features there are a couple of minor ones: >> >> AllegroGraphConnector now supports native SPARQL Update (tested against >> AllegroGraph 4.x on EC2) >> ITokenisingParser interface for token based parsers allows configuring >>the >> TokenQueueMode after a parser is instantiated >> TreeIndexedTripleCollection now has the option of completely >>configurable >> indices >> >> Plus there is the usual swathe of bug fixes, the only one that may be >> affecting people is that I found a bug where GROUP BY could give >>completely >> incorrect results for some kinds of query, mainly interactions with >>other >> clauses like VALUES and GRAPH. >> >> I ran a full regression suite at the end of last week including all the >> supported 3rd party stores I have access to installations of >>(everything but >> 4store right now). Apart from Dydra which appears to be completely >>broken >> (on their end and because of which I have marked DydraConnector as >>obsolete) >> everything is working fine. >> >> Documentation wise I've ported most stuff over to the BitBucket wiki >>which >> is a much nicer platform to work with and as part of that I've >> updated/rewritten/expanded various aspects. >> >> Thanks to Tom for already trawling through it and correcting a few >>typos and >> errors on my part. I have a couple more things to add/update there but >>I >> think I am mostly done. If you have time to review and point out any >> glaring omissions in the documentation or even better to add >>documentation >> yourself that would be great. >> >> Remaining work wise I have some clean up and fixes for the Toolkit to >>get in >> but otherwise I think I am done for 1.0.0. Tom do you want to sneak in >>that >> Configuration API suggestion since that seems fairly minor and very >>useful? >> >> Rob >> >> >>------------------------------------------------------------------------- >>----- >> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester >> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the >> endpoint security space. For insight on selecting the right partner to >> tackle endpoint security challenges, access the full report. >> http://p.sf.net/sfu/symantec-dev2dev >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >-------------------------------------------------------------------------- >---- >Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester >Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the >endpoint security space. For insight on selecting the right partner to >tackle endpoint security challenges, access the full report. >http://p.sf.net/sfu/symantec-dev2dev >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2013-03-11 20:34:45
|
Hi Rob, Sure, I'd like to contribute the Configuration API changes. I had some other tasks during the weekend but this won't take too long. What's my deadline for this? :) Tom On Mon, Mar 11, 2013 at 8:51 PM, Rob Vesse <rv...@do...> wrote: > Hey All > > Here is the current status on 1.0.0 as I see it, if anyone has anything else > they want to get into 1.0.0 now would be a good time to speak up > > In terms of new features there are a couple of minor ones: > > AllegroGraphConnector now supports native SPARQL Update (tested against > AllegroGraph 4.x on EC2) > ITokenisingParser interface for token based parsers allows configuring the > TokenQueueMode after a parser is instantiated > TreeIndexedTripleCollection now has the option of completely configurable > indices > > Plus there is the usual swathe of bug fixes, the only one that may be > affecting people is that I found a bug where GROUP BY could give completely > incorrect results for some kinds of query, mainly interactions with other > clauses like VALUES and GRAPH. > > I ran a full regression suite at the end of last week including all the > supported 3rd party stores I have access to installations of (everything but > 4store right now). Apart from Dydra which appears to be completely broken > (on their end and because of which I have marked DydraConnector as obsolete) > everything is working fine. > > Documentation wise I've ported most stuff over to the BitBucket wiki which > is a much nicer platform to work with and as part of that I've > updated/rewritten/expanded various aspects. > > Thanks to Tom for already trawling through it and correcting a few typos and > errors on my part. I have a couple more things to add/update there but I > think I am mostly done. If you have time to review and point out any > glaring omissions in the documentation or even better to add documentation > yourself that would be great. > > Remaining work wise I have some clean up and fixes for the Toolkit to get in > but otherwise I think I am done for 1.0.0. Tom do you want to sneak in that > Configuration API suggestion since that seems fairly minor and very useful? > > Rob > > ------------------------------------------------------------------------------ > Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester > Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the > endpoint security space. For insight on selecting the right partner to > tackle endpoint security challenges, access the full report. > http://p.sf.net/sfu/symantec-dev2dev > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: <tr...@do...> - 2013-03-11 19:54: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>rdfServer does not correctly respect the configuration file provided</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>rdfServer</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>
In conducting some testing on rdfServer I determined that it does not actually correctly respect the configuration file.</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=338" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=338</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-11 19:52:08
|
Hey All Here is the current status on 1.0.0 as I see it, if anyone has anything else they want to get into 1.0.0 now would be a good time to speak up In terms of new features there are a couple of minor ones: * AllegroGraphConnector now supports native SPARQL Update (tested against AllegroGraph 4.x on EC2) * ITokenisingParser interface for token based parsers allows configuring the TokenQueueMode after a parser is instantiated * TreeIndexedTripleCollection now has the option of completely configurable indices Plus there is the usual swathe of bug fixes, the only one that may be affecting people is that I found a bug where GROUP BY could give completely incorrect results for some kinds of query, mainly interactions with other clauses like VALUES and GRAPH. I ran a full regression suite at the end of last week including all the supported 3rd party stores I have access to installations of (everything but 4store right now). Apart from Dydra which appears to be completely broken (on their end and because of which I have marked DydraConnector as obsolete) everything is working fine. Documentation wise I've ported most stuff over to the BitBucket wiki which is a much nicer platform to work with and as part of that I've updated/rewritten/expanded various aspects. Thanks to Tom for already trawling through it and correcting a few typos and errors on my part. I have a couple more things to add/update there but I think I am mostly done. If you have time to review and point out any glaring omissions in the documentation or even better to add documentation yourself that would be great. Remaining work wise I have some clean up and fixes for the Toolkit to get in but otherwise I think I am done for 1.0.0. Tom do you want to sneak in that Configuration API suggestion since that seems fairly minor and very useful? Rob |
|
From: Rob V. <rv...@do...> - 2013-03-08 17:41:28
|
Yes that is a good idea
There is no reason why we can't make ConfigurationLoader so that it can
also be an instance class, so your example becomes:
// alternatively this could take a preloaded IGraph instance
ConfigurationLoader config = new ConfigurationLoader("configuration.ttl");
// string for blank node ID
var endpoint = config.Load<SparqlRemoteEndpoint>("sparql");
// URI for URI nodes
var store =
config.Load<ITripleStore>(UriFactory.Create("http://example.com/store));
Then like you say the instance methods would just call the static methods.
Rob
On 3/7/13 4:58 AM, "Tomasz Pluskiewicz" <tom...@gm...>
wrote:
>Hi All
>
>I have just been fiddling with the Configuration API and I have a
>lesser suggestion regarding its user-friendliness.
>
>The current API would remain intact but for a simpler usage it could
>be wrapped with a helper class so that the user can do this:
>
>// alternatively this could take a preloaded IGraph instance
>ConfigurationHelper config = new ConfigurationHelper("configuration.ttl");
>// string for blank node ID
>var endpoint = config.Load<SparqlRemoteEndpoint>("sparql");
>// URI for URI nodes
>var store =
>config.Load<ITripleStore>(UriFactory.Create("http://example.com/store));
>
>This way the user won't have to drag the configuration IGraph
>everywhere, create nodes INodes and manually cast objects to desired
>types.
>
>The name ConfigurationHelper is hideous and just an example. Guess we
>could come up with something better :).
>
>What do you think?
>
>Thanks,
>Tom
>
>--------------------------------------------------------------------------
>----
>Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
>Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
>endpoint security space. For insight on selecting the right partner to
>tackle endpoint security challenges, access the full report.
>http://p.sf.net/sfu/symantec-dev2dev
>_______________________________________________
>dotNetRDF-develop mailing list
>dot...@li...
>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
|
|
From: <tr...@do...> - 2013-03-07 21:09:03
|
<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>VALUES and GROUP BY may interact incorrectly</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-07 08:37 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
The fix turned out to be very simple one liner, in fixing this I also noticed a bug in GRAPH implementation when you had GRAPH { } so I fixed that as well.</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=336" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=336</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-07 20:39:20
|
<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>VALUES and GROUP BY may interact incorrectly</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=336" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=336</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-07 20:18:31
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>VALUES and GROUP BY may interact incorrectly</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>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>
In checking some SPARQ corner cases I noticed the following bug, the first query works fine:</p>
<p>
</p>
<p>
</p>
<div>
SELECT ?a</div>
<div>
WHERE</div>
<div>
{</div>
<div>
VALUES ( ?a)</div>
<div>
{</div>
<div>
( 1 )</div>
<div>
( 2 )</div>
<div>
}</div>
<div>
}</div>
<div>
</div>
<div>
However adding a GROUP BY causes it to return no results:</div>
<div>
</div>
<div>
<div>
SELECT ?a</div>
<div>
WHERE</div>
<div>
{</div>
<div>
VALUES ( ?a)</div>
<div>
{</div>
<div>
( 1 )</div>
<div>
( 2 )</div>
<div>
}</div>
<div>
} GROUP BY ?a</div>
<div>
</div>
<div>
This is likely a bug in the implementation of the VALUES clause</div>
</div>
<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=336" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=336</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Tomasz P. <tom...@gm...> - 2013-03-07 12:59:06
|
Hi All
I have just been fiddling with the Configuration API and I have a
lesser suggestion regarding its user-friendliness.
The current API would remain intact but for a simpler usage it could
be wrapped with a helper class so that the user can do this:
// alternatively this could take a preloaded IGraph instance
ConfigurationHelper config = new ConfigurationHelper("configuration.ttl");
// string for blank node ID
var endpoint = config.Load<SparqlRemoteEndpoint>("sparql");
// URI for URI nodes
var store = config.Load<ITripleStore>(UriFactory.Create("http://example.com/store));
This way the user won't have to drag the configuration IGraph
everywhere, create nodes INodes and manually cast objects to desired
types.
The name ConfigurationHelper is hideous and just an example. Guess we
could come up with something better :).
What do you think?
Thanks,
Tom
|
|
From: <dot...@li...> - 2013-03-07 01:07:10
|
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: 25 new changesets (Bitbucket) 2. commit/dotnetrdf: 16 new changesets (Bitbucket) 3. commit/dotnetrdf: 6 new changesets (Bitbucket) 4. commit/dotnetrdf: 2 new changesets (Bitbucket) 5. commit/dotnetrdf: 8 new changesets (Bitbucket) 6. commit/dotnetrdf: 2 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Wed, 06 Mar 2013 01:11:39 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 25 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 25 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/10076a7cf9ab/ changeset: 10076a7cf9ab branch: 1.9 user: rvesse date: 2013-03-06 00:43:13 summary: Merge latest changes from default affected #: 28 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0d4b40d511c5/ changeset: 0d4b40d511c5 branch: 1.9 user: rvesse date: 2013-03-06 00:57:27 summary: Create a trimmed down solution for working on the 2.0 refactor in the 1.9 branch affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b3ecd47ce264/ changeset: b3ecd47ce264 branch: 1.9 user: rvesse date: 2013-03-06 01:02:12 summary: Stub out new solution structure affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/759435028115/ changeset: 759435028115 branch: 1.9 user: rvesse date: 2013-03-06 01:06:13 summary: Stub for dotNetRDF.IO Core library affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/011af1e9ebe0/ changeset: 011af1e9ebe0 branch: 1.9 user: rvesse date: 2013-03-06 01:12:56 summary: Start moving content into Core IO module affected #: 128 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2139ca27c831/ changeset: 2139ca27c831 branch: 1.9 user: rvesse date: 2013-03-06 01:13:26 summary: Start moving content into Core IO module affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/94266bae4fbf/ changeset: 94266bae4fbf branch: 1.9 user: rvesse date: 2013-03-06 01:16:23 summary: Import writing APIs into Core IO module affected #: 65 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e9238527087e/ changeset: e9238527087e branch: 1.9 user: rvesse date: 2013-03-06 01:16:52 summary: Don't include formatting APIs in Core IO module since most of these will live in the Core module affected #: 23 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b85bb5375cf5/ changeset: b85bb5375cf5 branch: 1.9 user: rvesse date: 2013-03-06 01:18:42 summary: Importing MIME types manager to IO Core module affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ae2758e44f31/ changeset: ae2758e44f31 branch: 1.9 user: rvesse date: 2013-03-06 01:21:11 summary: Rename MimeTypesHelper to IOManager affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b52e9acd18c0/ changeset: b52e9acd18c0 branch: 1.9 user: rvesse date: 2013-03-06 01:24:58 summary: Move more relevant stuff to Core IO module affected #: 7 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e26fe442ce96/ changeset: e26fe442ce96 branch: 1.9 user: rvesse date: 2013-03-06 01:28:26 summary: Use hg move rather than hg copy so future merges from default will work nicely affected #: 252 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/92013dfc0c53/ changeset: 92013dfc0c53 branch: 1.9 user: rvesse date: 2013-03-06 01:29:03 summary: Use hg move rather than hg copy so future merges from default will work nicely affected #: 24 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0499f7fc5e7d/ changeset: 0499f7fc5e7d branch: 1.9 user: rvesse date: 2013-03-06 01:29:35 summary: Use hg move rather than hg copy so future merges from default will work nicely affected #: 58 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/766617316e4e/ changeset: 766617316e4e branch: 1.9 user: rvesse date: 2013-03-06 01:31:04 summary: Use hg move rather than hg copy so future merges from default will work nicely affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3e7b042a8c2e/ changeset: 3e7b042a8c2e branch: 1.9 user: rvesse date: 2013-03-06 01:31:31 summary: Use hg move rather than hg copy so future merges from default will work nicely affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4ee4afcd5845/ changeset: 4ee4afcd5845 branch: 1.9 user: rvesse date: 2013-03-06 01:33:59 summary: Removing defunct things from Core module affected #: 7 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1097e0b73215/ changeset: 1097e0b73215 branch: 1.9 user: rvesse date: 2013-03-06 01:34:36 summary: Move more stuff to IO Core module affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2183baeba947/ changeset: 2183baeba947 branch: 1.9 user: rvesse date: 2013-03-06 01:34:51 summary: Removing defunct things from Core module affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e6818e19220b/ changeset: e6818e19220b branch: 1.9 user: rvesse date: 2013-03-06 01:35:30 summary: Move more stuff to IO Core module affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/7756b4d6b509/ changeset: 7756b4d6b509 branch: 1.9 user: rvesse date: 2013-03-06 01:35:58 summary: Removing defunct things from Core module affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d8310ce7a656/ changeset: d8310ce7a656 branch: 1.9 user: rvesse date: 2013-03-06 01:44:57 summary: Move Storage API into Storage Core module affected #: 84 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/bc58abffe1a8/ changeset: bc58abffe1a8 branch: 1.9 user: rvesse date: 2013-03-06 01:54:03 summary: Stub project for SPARQL Core module affected #: 6 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a1347e8f0023/ changeset: a1347e8f0023 branch: 1.9 user: rvesse date: 2013-03-06 01:59:44 summary: Stub for Web Core module affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/975a50ac65dd/ changeset: 975a50ac65dd branch: 1.9 user: rvesse date: 2013-03-06 02:00:51 summary: Move Web APIs to Web Core module affected #: 59 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Wed, 06 Mar 2013 19:33:46 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 16 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 16 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/7bc88939fdbd/ changeset: 7bc88939fdbd branch: 1.9 user: rvesse date: 2013-03-06 18:54:27 summary: Add updated version of SyncProjects to use with getting the modules into shape affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2be41caabcf3/ changeset: 2be41caabcf3 branch: 1.9 user: rvesse date: 2013-03-06 19:02:36 summary: Add SyncProjects build events to various new modules affected #: 10 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d5992d5ce0e9/ changeset: d5992d5ce0e9 branch: 1.9 user: rvesse date: 2013-03-06 19:11:19 summary: More module rearrangement affected #: 6 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1e27e10d7f93/ changeset: 1e27e10d7f93 branch: 1.9 user: rvesse date: 2013-03-06 19:17:08 summary: More module reorg affected #: 9 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/fe4f07fc2cc2/ changeset: fe4f07fc2cc2 branch: 1.9 user: rvesse date: 2013-03-06 19:21:55 summary: Trying to sort of the Formatting API split between Core module and SPARQL Core module affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/84075fb62849/ changeset: 84075fb62849 branch: 1.9 user: rvesse date: 2013-03-06 19:22:45 summary: Move Serialization stuff back into Core module affected #: 8 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/dd358a38c2fd/ changeset: dd358a38c2fd branch: 1.9 user: rvesse date: 2013-03-06 19:27:50 summary: More module reorg affected #: 8 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0e8178e11de2/ changeset: 0e8178e11de2 branch: 1.9 user: rvesse date: 2013-03-06 19:28:58 summary: More module reorg affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/12747aa0f6f0/ changeset: 12747aa0f6f0 branch: 1.9 user: rvesse date: 2013-03-06 19:29:40 summary: More module reorg affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/57e2a53378e1/ changeset: 57e2a53378e1 branch: 1.9 user: rvesse date: 2013-03-06 19:33:50 summary: More module reorg affected #: 7 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/91f0d16290a5/ changeset: 91f0d16290a5 branch: 1.9 user: rvesse date: 2013-03-06 19:39:42 summary: Getting more stuff moved into the correct modules affected #: 17 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ab33d1bd60e5/ changeset: ab33d1bd60e5 branch: 1.9 user: rvesse date: 2013-03-06 19:46:01 summary: Throw out stuff that is being removed in 1.9 affected #: 13 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2378fac5ac03/ changeset: 2378fac5ac03 branch: 1.9 user: rvesse date: 2013-03-06 19:51:35 summary: Move more stuff over to SPARQL Core module affected #: 7 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/611f6f8d3b2e/ changeset: 611f6f8d3b2e branch: 1.9 user: rvesse date: 2013-03-06 19:59:50 summary: Almost reorged everything irrelevant out of Core module affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6b3b16e93f87/ changeset: 6b3b16e93f87 branch: 1.9 user: rvesse date: 2013-03-06 20:31:53 summary: Got everything obviously irrelevant out of Core module affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d5d449faf4b2/ changeset: d5d449faf4b2 branch: 1.9 user: rvesse date: 2013-03-06 20:33:17 summary: Move relevant static options out to specific modules affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 3 Date: Wed, 06 Mar 2013 22:21:08 -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/9385c550871a/ changeset: 9385c550871a branch: 1.9 user: rvesse date: 2013-03-06 20:49:35 summary: Move Configuration API into own module, more some other stuff to correct modules affected #: 60 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/78ffaebeebb5/ changeset: 78ffaebeebb5 branch: 1.9 user: rvesse date: 2013-03-06 21:08:34 summary: Some refactoring in the Core module affected #: 26 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4383cf573ff4/ changeset: 4383cf573ff4 branch: 1.9 user: rvesse date: 2013-03-06 21:19:44 summary: Reorging some more stuff in the Core module, added a new Specifications namespace affected #: 25 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f47a030ae66c/ changeset: f47a030ae66c branch: 1.9 user: rvesse date: 2013-03-06 23:08:06 summary: Move a couple more things out to other modules affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/dfd24b6b5f4f/ changeset: dfd24b6b5f4f branch: 1.9 user: rvesse date: 2013-03-06 23:08:58 summary: Fix error in ThreadSafeGraphCollection affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/025e6714ec70/ changeset: 025e6714ec70 branch: 1.9 user: rvesse date: 2013-03-06 23:20:05 summary: Move more stuff around modules affected #: 15 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: Wed, 06 Mar 2013 22:33:44 -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/2c07554fc330/ changeset: 2c07554fc330 branch: 1.9 user: rvesse date: 2013-03-06 23:28:41 summary: Rearrange some more stuff so the Core module builds affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/484ff0def2b9/ changeset: 484ff0def2b9 branch: 1.9 user: rvesse date: 2013-03-06 23:33:31 summary: Add missing license headers affected #: 14 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: Thu, 07 Mar 2013 00:59:41 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 8 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 8 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6866226ce6e4/ changeset: 6866226ce6e4 branch: 1.9 user: rvesse date: 2013-03-06 23:36:25 summary: Some experimental reorg affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9a1ba4a1b60b/ changeset: 9a1ba4a1b60b branch: 1.9 user: rvesse date: 2013-03-06 23:57:45 summary: Start implementing the new IGraphStore interface affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/fde2df13ad9b/ changeset: fde2df13ad9b branch: 1.9 user: rvesse date: 2013-03-07 01:26:06 summary: Complete stub BaseGraphStore implementation affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2a0a1443d6b1/ changeset: 2a0a1443d6b1 branch: 1.9 user: rvesse date: 2013-03-07 01:29:18 summary: Tidy a couple of XML comments affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1cf2962bb5ad/ changeset: 1cf2962bb5ad branch: 1.9 user: rvesse date: 2013-03-07 01:56:53 summary: Add abstract tests for graph contract affected #: 8 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/cdeecc97df85/ changeset: cdeecc97df85 branch: 1.9 user: rvesse date: 2013-03-07 01:57:40 summary: Reorg testing projects affected #: 6 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/099b27e14834/ changeset: 099b27e14834 branch: 1.9 user: rvesse date: 2013-03-07 01:58:01 summary: Reorg testing projects affected #: 6 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/66ed966d9f1b/ changeset: 66ed966d9f1b branch: 1.9 user: rvesse date: 2013-03-07 01:59:06 summary: Reorg testing projects 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: Thu, 07 Mar 2013 01:07:00 -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/e858c63d1049/ changeset: e858c63d1049 branch: 1.9 user: rvesse date: 2013-03-07 02:04:08 summary: Start fleshing out graph tests more affected #: 10 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6e39568dc0c0/ changeset: 6e39568dc0c0 branch: 1.9 user: rvesse date: 2013-03-07 02:06:47 summary: Note changes in Change Log 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. ------------------------------ ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 6, Issue 2 *********************************************** |
|
From: <tr...@do...> - 2013-03-06 08:52:13
|
<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>Provide a Portable Class Library build of dotNetRDF</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-06 08:51 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I now have code compiling without error in my fork of the core library code (https://bitbucket.org/kal_ahmed/dotnetrdf). Next step is to look into getting as many unit tests as possible running on the PCL build. My plan is to run the unit tests as a .NET 4.0 unit test project that uses the PCL version of the core library - this is instead of trying to get a Silverlight/Metro/Windows Phone test framework running and integrated with the build (those might be interesting things to try out later, but for now I'm going to assume that if the PCL build passes unit tests in a .NET 4.0 test framework, then the code itself is sound for deployment on the other platforms too).</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=303" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=303</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 21:44: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>Document Global Options</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-03-05 09:43 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
This is now written up at <a href="https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Global%20Options">https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Global%20Options</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=335" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=335</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 21:44:58
|
<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>Document Global Options</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 "Added"
</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=335" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=335</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 20:50:54
|
<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>Document Global Options</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>Milestone:</b></td>
<td>1.0.x Releases</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Core API</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Documentation Missing</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
dotNetRDF has a set of global options provided by the Options class, some of these are documented on individual wiki pages but many are not documented at all. This task is to add a single page which covers all the global options.</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=335" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=335</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <dot...@li...> - 2013-03-05 20:47:59
|
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: 2 new changesets (Bitbucket) 3. commit/dotnetrdf: rvesse: Some final XML comment clean up (CORE-319) (Bitbucket) 4. commit/dotnetrdf: rvesse: Finish XML comments for rdfEditor.Core.Wpf (CORE-319) (Bitbucket) 5. commit/dotnetrdf: 2 new changesets (Bitbucket) 6. commit/dotnetrdf: 2 new changesets (Bitbucket) 7. commit/dotnetrdf: rvesse: Update Change Log to note latest fixes (TOOLS-333, CORE-334, CORE-308) (Bitbucket) 8. commit/dotnetrdf: 4 new changesets (Bitbucket) 9. commit/dotnetrdf: rvesse: Note incorporation of relevant BrightstarDB patches in Change Log (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Thu, 28 Feb 2013 18:20:35 -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/b948fa35670c/ changeset: b948fa35670c branch: 1.9 user: rvesse date: 2013-02-28 19:19:54 summary: Merge latest changes from default to 1.9 branch affected #: 142 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/65b63a4c9c33/ changeset: 65b63a4c9c33 branch: medusa user: rvesse date: 2013-02-28 19:20:18 summary: Merge latest changes from default to medusa branch affected #: 142 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Thu, 28 Feb 2013 18:51:11 -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/3379b402ed04/ changeset: 3379b402ed04 user: rvesse date: 2013-02-28 19:49:29 summary: Update ReadMe to note updated repository locations affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/860934283956/ changeset: 860934283956 user: rvesse date: 2013-02-28 19:51:02 summary: Add CodePlex to repository links 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: 3 Date: Thu, 28 Feb 2013 18:07:23 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Some final XML comment clean up (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/ebba0798061b/ changeset: ebba0798061b user: rvesse date: 2013-02-28 19:07:01 summary: Some final XML comment clean up (CORE-319) 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: 4 Date: Thu, 28 Feb 2013 17:42:38 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Finish XML comments for rdfEditor.Core.Wpf (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/298ec11231ff/ changeset: 298ec11231ff user: rvesse date: 2013-02-28 18:40:16 summary: Finish XML comments for rdfEditor.Core.Wpf (CORE-319) 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: 5 Date: Fri, 01 Mar 2013 23:32:39 -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/fcb25e92cffd/ changeset: fcb25e92cffd user: rvesse date: 2013-03-02 00:26:39 summary: Fix a compiler error with rdfEditor affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b26ef4683777/ changeset: b26ef4683777 user: rvesse date: 2013-03-02 00:32:27 summary: Slightly abstract some code to make it easier to refactor in the future (CORE-330) 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: Tue, 05 Mar 2013 17:37:18 -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/f8eab2f3ad7a/ changeset: f8eab2f3ad7a user: rvesse date: 2013-03-04 22:01:12 summary: Fix an issue where error messages under rdfServer could be truncated affected #: 7 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/07b024239b87/ changeset: 07b024239b87 user: rvesse date: 2013-03-05 18:36:57 summary: Fix a bug where StoreHandler would not propogate prefixes correctly when parsing datasets (CORE-334), this meant that rdfConvert would lose prefixes when going from Graphs to Datasets (CORE-333) affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 7 Date: Tue, 05 Mar 2013 17:51:30 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Update Change Log to note latest fixes (TOOLS-333, CORE-334, CORE-308) 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/1377409227a9/ changeset: 1377409227a9 user: rvesse date: 2013-03-05 18:51:15 summary: Update Change Log to note latest fixes (TOOLS-333, CORE-334, CORE-308) 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: 8 Date: Tue, 05 Mar 2013 20:34:33 -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/6f3b1280c8ac/ changeset: 6f3b1280c8ac user: rvesse date: 2013-03-05 19:27:02 summary: Incoporate a variant of BrightstarDB patch 2029 into the SPARQL Expression parser and add relevant unit tests (CORE-332) affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ce44824adb23/ changeset: ce44824adb23 user: rvesse date: 2013-03-05 19:44:10 summary: Work on incorporating a more general solution for BrightstarDB patch 2181, adds a ITokenisingParser interface which allows the TokenQueueMode to be get/set via a property. Adds a ApplyParserOptions() to MimeTypesHelper which once incorporated will set the appropriate token queue mode on returned parsers (CORE-332) affected #: 8 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d0365ec5c006/ changeset: d0365ec5c006 user: rvesse date: 2013-03-05 19:50:35 summary: Convert remaining tokeniser based parsers to implement ITokenisingParser (CORE-332) affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/db79db80093f/ changeset: db79db80093f user: rvesse date: 2013-03-05 20:00:27 summary: Wire up MimeTypesHelper.ApplyWriterOptions() throughout GetParser() methods (CORE-332) 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: 9 Date: Tue, 05 Mar 2013 20:47:51 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Note incorporation of relevant BrightstarDB patches in Change Log 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/cf90a147e281/ changeset: cf90a147e281 user: rvesse date: 2013-03-05 21:47:42 summary: Note incorporation of relevant BrightstarDB patches in Change Log 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 6, Issue 1 *********************************************** |
|
From: <tr...@do...> - 2013-03-05 20:40:24
|
<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>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 colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Planned" to "Completed"
</li>
<li>Affected Milestone changed from "Unassigned" to "0.9.0 RC 4"
</li>
<li>Resolution changed from "Unassigned" to "Completed"
</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=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 20:39: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>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-03-05 08:39 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
So 2029 is applied as of <a href="https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6f3b1280c8ac390b25b7ca15d7fc95537cf6d22a">https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6f3b1280c8ac390b25b7ca15d7fc95537cf6d22a</a></p>
<p>
</p>
<p>
2181 is integrated in a slightly different way in a series of commits, there is now an Options.DefaultTokenQueueMode which may be used to set the default queue mode for tokenising parsers. All relevant parsers now implement ITokenisingParser and expose a TokenQueueMode property which can be used to change the desired queue mode. MimeTypesHelper has a new helper method ApplyParserOptions() which is used by all the GetParser() methods to apply global options onto returned parsers. Relevant parsers will use the Options.DefaultTokenQueueMode as their default queue mode anyway.</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 18:29:20
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>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 06:28 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
2029 is definitely needed though I made the required fix a different way to generalize it to work with all numeric types, this is now applied to the codebase</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 18:06: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>Provide a Portable Class Library build of dotNetRDF</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>Assigned to changed from "Unassigned" to "Kal"
</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=303" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=303</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 18:00:04
|
<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>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=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>
|
48 messages has been excluded from this view by a project administrator.
