dotnetrdf-develop — Developer Discussion and Feature Request

[dotNetRDF-Develop] Issue CORE-391 has been added to a project you are monitoring.

[<tr...@do...>]

<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>UriLoader.Load() can swallow parser errors in builds that support caching</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.3</td>
  </tr>
  <tr>
    <td><b>Category:</b></td>
    <td>Parsing</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>
	Initially prompted by a discussion with David Shugars I have identified a bug in UriLoader.Load() where it can swallow parser errors rather than propagating them upwards meaning the user gets an empty graph when they should have seen an exception leaving them confused because they think the request succeeded when in fact it didn&#39;t</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=391" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=391</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>

Re: [dotNetRDF-Develop] Store manager improvements

[Eugen F <feu...@ya...>]

Hi Rob,

I pulled the changes from that tool branch locally (sync the url of that tool branch with my local repository) and now I see your changes. (i hope it's the correct process).

I'm now sure what is the advantage of flat buttons over tabs, but since the functionality is the same seems ok to me.

About the issue: "Currently the query results overwrite each other," , this is exactly what i want. Consider i make some changes to a query (like you do for example in sql management studio), but that query is not final and I gradually improve it, then I don't care about the previous results until i can write the correct query and i don't want to close the old results tab/window each time. Before the current changes I had to manually go and close each MDI window each time I ran a query, and that is very strange to me. If I would want to see previous results then i would create a new connection from current, copy the query, maybe change it, then  run it, keeping old result in prev window (and associated with the exact query that generated them).
Another solution would be to add a new Run(tab) button that would open new tabs as you said (keeping the current Run button that overwrites).
But there is an issue to consider: a query and the results form a pair, if we have many results for some query that include older forms of it then it's kind of strange, because for those older results  i lost the query that generated them, so ideally for each results i should see the query that generated them.

In any case I would like to have the functionality to overwrite old results.

Regarding the entities feature i think I'll better explain here:
(or only the problem here: http://stackoverflow.com/questions/10251802/sparql-query-to-retrieve-all-objects-and-properties)

Consider having a list of persons, each person subject of the rdf:type :Person, and each person having one or more of the properties: :Age, :Name, :FullName, :Email, and so on. Now i want to write a query that gives me all the persons and their properties without knowing in advance the properties; 

If i know the properties the final query would look like:
select ?person ?name ?age ..
where {
?person rdf:type :Person.
optional(?person :Name ?name).
optional(?person :hasAge ?age).
....

}
But if i don't know the properties i first need to find them, then manually create the query above.
What i did is take the first variable from a query, get all the properties for that list of variables and then dynamically create the query.
In the above example the user would write a query like:
select ?person
where {
?person rdf:type :Person.
}
then i would transform this into a query to get all the predicates for all ?person so running the first query results in a response like:
predicate, nr of usages

:Name, 2
:Age, 3
:Email, 1

so now i can programaticaly create a new query:

select ?person ?name ?age ..
where {......

What I did wrong i think is that I actually executed the final query, and I think it's better to actually make a button that generates this final query from the initial one and let the user execute it, because in this way he can remove some of the properties.
So for the user input:
select ?person
where {
?person rdf:type :Person.
}
i would press a button and get as an output a new query:
select ?person ?name ?age ..
where { optional(......







On Wednesday, December 11, 2013 2:09 PM, Rob Vesse <rv...@do...> wrote:
 
Eugen

Generally I like the changes, I have a few suggestions for improvements.

Firstly since the tabs act mainly as buttons to quickly focus on a specific connection I'd suggest using FlatButtons Appearance for the tabs.  I've already made this change in the main repository, note that I've moved the changes onto the TOOLS-390 branch in the main repository, if you can pull my changes to your fork and then make any further changes in that branch instead of default that would be much appreciated.

Currently the query results overwrite each other, so if I run subsequent queries the previous query results are hidden.  It might be a nice idea to have a tab control within the results area and have each new query add a tab preferably with some way to view in each result tab what query produced the results, this would also need the ability to close result tabs that are no longer needed.

Another nice feature to have would be the ability to detach results into a separate window when desired though I'm less fussed about this.

I'm not really sure what the entities feature is doing since it didn't seem to do much in my testing, I'd like to understand exactly what this is attempting to do.  Wrt to the code for this it would be better to use the SparqlParameterizedString class for constructing the queries rather than String.Format() and string concatenation.  See the Representing Queries section at https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Querying%20with%20SPARQL for an example of using this class.

Note that you can get the namespaces associated with the existing query by using the NamespaceMap property and the Base URI using the BaseUri property, you can then simply copy these to your SparqlParameterizedString instance avoiding the need to do this by string extraction.  (Actually it doesn't have a BaseUri property, I'll add that soon)

In general I'm wondering that if you are looking to give a more entity centric view of the data in a store whether it wouldn't be better to add this functionality as a new entities tab and develop entity viewer controls and associated tasks specifically for this rather than reusing the Query Tab?

Cheers,

Rob
From:  Rob Vesse <rv...@do...>
Reply-To:  dotNetRDF Developer Discussion and Feature Request <dot...@li...>
Date:  Tuesday, 10 December 2013 16:12
To:  dotNetRDF Developer Discussion and Feature Request <dot...@li...>
Subject:  Re: [dotNetRDF-Develop] Store manager improvements


Thanks for that, I've pulled your changes locally and will try and take a proper look at them tomorrow.  I've glanced over the code changes and everything looks OK but I haven't got as far as running the revised UI yet.
>
>
>When I do review properly I'll try and look at the entities query stuff and see if there is any way to make it more efficient.
>
>
>Thanks for spotting the bug in BaseEndpoint, I introduced this by accident with a recent commit and it should now be fixed again with my most recent commits
>
>
>Cheers,
>
>
>Rob
>
>From:  Eugen F <feu...@ya...>
>Reply-To:  Eugen F <feu...@ya...>
>Date:  Tuesday, 10 December 2013 09:46
>To:  Rob Vesse <rv...@do...>
>Cc:  dotNetRDF Developer Discussion and Feature Request <dot...@li...>
>Subject:  Re: [dotNetRDF-Develop] Store manager improvements
>
>
>
>I've updated the repository, so maybe you can check the changes.
>>
>>Note that there is a change in BaseEnpoint "throw new ArgumentException("HTTP Mode can only be GET/POST, derived implementations should override this property if they wish to support more methods");" that I had to comment in order to make the version from repository connect to an endpoint. (no relation to my changes).
>>
>>Also I tried to make an external endpoint work with that entities change, but i only get timeouts...because of the complex query i think.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>On Monday, December 9, 2013 2:50 PM, Rob Vesse <rv...@do...> wrote:
>> 
>>Eugen
>>
>>
>>Forking a Mercurial repository copies all branches, however if you could commit your changes to the default branch that would be best
>>
>>
>>Thanks,
>>
>>
>>Rob
>>
>>
>>From:  Eugen F <feu...@ya...>
>>Reply-To:  Eugen F <feu...@ya...>
>>Date:  Monday, 9 December 2013 12:20
>>To:  Rob Vesse <rv...@do...>
>>Subject:  Re: [dotNetRDF-Develop] Store manager improvements
>>
>>
>>
>>I have made the changes so it's now both MDI and tabs, forked repository at https://bitbucket.org/feugen24/storemanager_tabs. Still I'm not sure it's the correct version because there were lots of tags when creating the fork, so i picked the "dynamic" that was selected by default. I assumed dynamic means (latest). 
>>>
>>>If it's ok i'll update this one.
>>>
>>>
>>>
>>>
>>>On Sunday, December 8, 2013 5:33 PM, Rob Vesse <rv...@do...> wrote:
>>> 
>>>Hi Eugen
>>>
>>>
>>>Thanks for the detailed email, yes there are advantages to a tabbed interface though I suspect some users (like myself) may prefer to have the MDI interface still.
>>>
>>>
>>>What would be ideal from my perspective would be to integrate this such that users can switch between the modes as desired, so users who prefer the current interface can continue to use it and those that like the new interface can use that instead.  Or even to have it such that you can dock connections into a tabbed interface as and when desired.
>>>
>>>
>>>The changes all sound useful but I haven't previewed them at all because I'm afraid I'm not going to run a compiled executable from someone who's emailing me for the very first time even if it does pass the virus checker.  If you can provide either a link to the git repository, a patch against latest trunk or ideally a mercurial fork that would be fantastic.  We use Mercurial for our development with our main repository hosted on BitBucket at http://bitbucket.org/dotnetrdf/dotnetrdf – if you can fork the code on BitBucket, transfer your changes to there and then open a pull request that would be the best way for us to see and review your changes.
>>>
>>>
>>>Btw this is a subscription list, your email was moderated through and you've been CC'd on this initial reply but if you could subscribe at https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop so you can participate in this discussion going forward without us having to manually CC you each time that would be much appreciated.
>>>
>>>
>>>Thanks,
>>>
>>>
>>>Rob
>>>
>>>
>>>From:  Eugen F <feu...@ya...>
>>>Reply-To:  Eugen F <feu...@ya...>, dotNetRDF Developer Discussion and Feature Request <dot...@li...>
>>>Date:  Saturday, 7 December 2013 11:42
>>>To:  "dot...@li..." <dot...@li...>
>>>Subject:  [dotNetRDF-Develop] Store manager improvements
>>>
>>>
>>>
>>>Hi,
>>>>
>>>>
>>>>I'm working with store manager and because of the midi interface it's difficult to interact with it, meaning each time i create a connection a new window is created, then when I run a query another window, rerun a query...new window, then close the one of the first query run and so on.
>>>>
>>>>
>>>>So i think the approach in sql server management studio or brightstardb polaris tool is much better. Both have tabs for each new connection, and when i rerun a query only results change (no new window).
>>>>So i made the following changes:
>>>>- when a connection is opened a new tab page is created and I add StoreManagerForm as a child to it
>>>>- each tab has a close btn 
>>>>
>>>>The rest of the functionality is the same except for query tab where:
>>>>- i added a splitter control where panel 1 has query window , panel 2 has query results (both for graph and resultset)
>>>>
>>>>- i added a new button for orientation ( --| ) so we can change the orientation of the splitter ( vertical mode is v helpful on wide screens with few columns on results)
>>>>- i removed "query" word from all buttons to occupy less space (i think it's obvious since we are in query window tab)
>>>>
>>>>- i changed AutoSizeColumnsMode to AllCells (previous was DisplayedCells but i had problems with it when large uri's where not in current view)
>>>>
>>>>
>>>>I also added a feature (in query tab) to expand a query for some subjects so i can see all the properties and values of those subjects. This allows a user to see similar results as sql server in case he has entities. For example if a user is using Entityframework api from brightstardb he can the select entities of rdf:type "Car" and see all car entities with values, in a table.
>>>>- i added a new checkbox "AsEntities" that allows this feature when checked (it takes first variable from the current query as entity id/subject)
>>>>
>>>>It transforms user query to get all properties and the dynamically creates a query to get the entities.
>>>>- i also added a numeric control next to the checkbox with default value of 1. This was necessary because in may case I have some predicates that are entities themselves and i need to filter those out. (a group by is used to filter predicates using that default value of 1)
>>>>
>>>>
>>>>I've attached the working version so you can play with it. I worked on a local git source control using latest 102 source code.
>>>>Let me know what you think of the changes, and if it's ok, how to send/publish the source code. I've not really worked on any open source project so i don't know the flow.------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk_______________________________________________ dotNetRDF-develop mailing list dot...@li...https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>>
>>>
>>
>>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk_______________________________________________ dotNetRDF-develop mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop 
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
dotNetRDF-develop mailing list
dot...@li...
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

Re: [dotNetRDF-Develop] Store manager improvements

[Rob V. <rv...@do...>]

Eugen

Generally I like the changes, I have a few suggestions for improvements.

Firstly since the tabs act mainly as buttons to quickly focus on a specific
connection I'd suggest using FlatButtons Appearance for the tabs.  I've
already made this change in the main repository, note that I've moved the
changes onto the TOOLS-390 branch in the main repository, if you can pull my
changes to your fork and then make any further changes in that branch
instead of default that would be much appreciated.

Currently the query results overwrite each other, so if I run subsequent
queries the previous query results are hidden.  It might be a nice idea to
have a tab control within the results area and have each new query add a tab
preferably with some way to view in each result tab what query produced the
results, this would also need the ability to close result tabs that are no
longer needed.

Another nice feature to have would be the ability to detach results into a
separate window when desired though I'm less fussed about this.

I'm not really sure what the entities feature is doing since it didn't seem
to do much in my testing, I'd like to understand exactly what this is
attempting to do.  Wrt to the code for this it would be better to use the
SparqlParameterizedString class for constructing the queries rather than
String.Format() and string concatenation.  See the Representing Queries
section at 
https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Querying%20with%20S
PARQL for an example of using this class.

Note that you can get the namespaces associated with the existing query by
using the NamespaceMap property and the Base URI using the BaseUri property,
you can then simply copy these to your SparqlParameterizedString instance
avoiding the need to do this by string extraction.  (Actually it doesn't
have a BaseUri property, I'll add that soon)

In general I'm wondering that if you are looking to give a more entity
centric view of the data in a store whether it wouldn't be better to add
this functionality as a new entities tab and develop entity viewer controls
and associated tasks specifically for this rather than reusing the Query
Tab?

Cheers,

Rob

From:  Rob Vesse <rv...@do...>
Reply-To:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Date:  Tuesday, 10 December 2013 16:12
To:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Subject:  Re: [dotNetRDF-Develop] Store manager improvements

> Thanks for that, I've pulled your changes locally and will try and take a
> proper look at them tomorrow.  I've glanced over the code changes and
> everything looks OK but I haven't got as far as running the revised UI yet.
> 
> When I do review properly I'll try and look at the entities query stuff and
> see if there is any way to make it more efficient.
> 
> Thanks for spotting the bug in BaseEndpoint, I introduced this by accident
> with a recent commit and it should now be fixed again with my most recent
> commits
> 
> Cheers,
> 
> Rob
> 
> From:  Eugen F <feu...@ya...>
> Reply-To:  Eugen F <feu...@ya...>
> Date:  Tuesday, 10 December 2013 09:46
> To:  Rob Vesse <rv...@do...>
> Cc:  dotNetRDF Developer Discussion and Feature Request
> <dot...@li...>
> Subject:  Re: [dotNetRDF-Develop] Store manager improvements
> 
>> I've updated the repository, so maybe you can check the changes.
>> 
>> Note that there is a change in BaseEnpoint "throw new ArgumentException("HTTP
>> Mode can only be GET/POST, derived implementations should override this
>> property if they wish to support more methods");" that I had to comment in
>> order to make the version from repository connect to an endpoint. (no
>> relation to my changes).
>> 
>> Also I tried to make an external endpoint work with that entities change, but
>> i only get timeouts...because of the complex query i think.
>> 
>> 
>> 
>> 
>>  
>>  
>>  
>>  
>>  
>>   On Monday, December 9, 2013 2:50 PM, Rob Vesse <rv...@do...>
>> wrote:
>>   
>>   
>> Eugen
>> 
>> Forking a Mercurial repository copies all branches, however if you could
>> commit your changes to the default branch that would be best
>> 
>> Thanks,
>> 
>> Rob
>> 
>> From:  Eugen F <feu...@ya...>
>> Reply-To:  Eugen F <feu...@ya...>
>> Date:  Monday, 9 December 2013 12:20
>> To:  Rob Vesse <rv...@do...>
>> Subject:  Re: [dotNetRDF-Develop] Store manager improvements
>> 
>>> I have made the changes so it's now both MDI and tabs, forked repository at
>>> https://bitbucket.org/feugen24/storemanager_tabs. Still I'm not sure it's
>>> the correct version because there were lots of tags when creating the fork,
>>> so i picked the "dynamic" that was selected by default. I assumed dynamic
>>> means (latest).
>>> If it's ok i'll update this one.
>>>  
>>>  
>>>  
>>>  
>>>  
>>>   On Sunday, December 8, 2013 5:33 PM, Rob Vesse <rv...@do...>
>>> wrote:
>>>   
>>>   
>>> Hi Eugen
>>> 
>>> Thanks for the detailed email, yes there are advantages to a tabbed
>>> interface though I suspect some users (like myself) may prefer to have the
>>> MDI interface still.
>>> 
>>> What would be ideal from my perspective would be to integrate this such that
>>> users can switch between the modes as desired, so users who prefer the
>>> current interface can continue to use it and those that like the new
>>> interface can use that instead.  Or even to have it such that you can dock
>>> connections into a tabbed interface as and when desired.
>>> 
>>> The changes all sound useful but I haven't previewed them at all because I'm
>>> afraid I'm not going to run a compiled executable from someone who's
>>> emailing me for the very first time even if it does pass the virus checker.
>>> If you can provide either a link to the git repository, a patch against
>>> latest trunk or ideally a mercurial fork that would be fantastic.  We use
>>> Mercurial for our development with our main repository hosted on BitBucket
>>> at http://bitbucket.org/dotnetrdf/dotnetrdf ­ if you can fork the code on
>>> BitBucket, transfer your changes to there and then open a pull request that
>>> would be the best way for us to see and review your changes.
>>> 
>>> Btw this is a subscription list, your email was moderated through and you've
>>> been CC'd on this initial reply but if you could subscribe at
>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop so you can
>>> participate in this discussion going forward without us having to manually
>>> CC you each time that would be much appreciated.
>>> 
>>> Thanks,
>>> 
>>> Rob
>>> 
>>> From:  Eugen F <feu...@ya...>
>>> Reply-To:  Eugen F <feu...@ya...>, dotNetRDF Developer Discussion and
>>> Feature Request <dot...@li...>
>>> Date:  Saturday, 7 December 2013 11:42
>>> To:  "dot...@li..."
>>> <dot...@li...>
>>> Subject:  [dotNetRDF-Develop] Store manager improvements
>>> 
>>>> Hi,
>>>> 
>>>> I'm working with store manager and because of the midi interface it's
>>>> difficult to interact with it, meaning each time i create a connection a
>>>> new window is created, then when I run a query another window, rerun a
>>>> query...new window, then close the one of the first query run and so on.
>>>> 
>>>> So i think the approach in sql server management studio or brightstardb
>>>> polaris tool is much better. Both have tabs for each new connection, and
>>>> when i rerun a query only results change (no new window).
>>>> So i made the following changes:
>>>> - when a connection is opened a new tab page is created and I add
>>>> StoreManagerForm as a child to it
>>>> - each tab has a close btn
>>>> The rest of the functionality is the same except for query tab where:
>>>> - i added a splitter control where panel 1 has query window , panel 2 has
>>>> query results (both for graph and resultset)
>>>> - i added a new button for orientation ( --| ) so we can change the
>>>> orientation of the splitter ( vertical mode is v helpful on wide screens
>>>> with few columns on results)
>>>> - i removed "query" word from all buttons to occupy less space (i think
>>>> it's obvious since we are in query window tab)
>>>> - i changed AutoSizeColumnsMode to AllCells (previous was DisplayedCells
>>>> but i had problems with it when large uri's where not in current view)
>>>> 
>>>> I also added a feature (in query tab) to expand a query for some subjects
>>>> so i can see all the properties and values of those subjects. This allows a
>>>> user to see similar results as sql server in case he has entities. For
>>>> example if a user is using Entityframework api from brightstardb he can the
>>>> select entities of rdf:type "Car" and see all car entities with values, in
>>>> a table.
>>>> - i added a new checkbox "AsEntities" that allows this feature when checked
>>>> (it takes first variable from the current query as entity id/subject)
>>>> It transforms user query to get all properties and the dynamically creates
>>>> a query to get the entities.
>>>> - i also added a numeric control next to the checkbox with default value of
>>>> 1. This was necessary because in may case I have some predicates that are
>>>> entities themselves and i need to filter those out. (a group by is used to
>>>> filter predicates using that default value of 1)
>>>> 
>>>> I've attached the working version so you can play with it. I worked on a
>>>> local git source control using latest 102 source code.
>>>> Let me know what you think of the changes, and if it's ok, how to
>>>> send/publish the source code. I've not really worked on any open source
>>>> project so i don't know the flow.
>>>> ---------------------------------------------------------------------------
>>>> --- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps
>>>> with a single code base. Download it for free now!
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktr
>>>> k_______________________________________________ dotNetRDF-develop mailing
>>>> list 
>>>> dot...@li...https://lists.sourceforge.net/lists/
>>>> listinfo/dotnetrdf-develop
>>> 
>>> 
>>>   
>>>  
>>>   
>>>  
>> 
>> 
>>   
>>  
>>   
>>  
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk___
> ____________________________________________ dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

[dotNetRDF-Develop] dotNetRDF-commits Digest, Vol 14, Issue 2

[<dot...@li...>]

Send dotNetRDF-commits mailing list submissions to
	dot...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits
or, via email, send a message with subject or body 'help' to
	dot...@li...

You can reach the person managing the list at
	dot...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dotNetRDF-commits digest..."


Today's Topics:

   1. commit/dotnetrdf: 3 new changesets (Bitbucket)
   2. commit/dotnetrdf: 2 new changesets (Bitbucket)
   3. commit/dotnetrdf: rvesse: Stub out design for a reusable
      Connection Management control (CORE-377) (Bitbucket)
   4. commit/dotnetrdf: 3 new changesets (Bitbucket)
   5. commit/dotnetrdf: 4 new changesets (Bitbucket)
   6. commit/dotnetrdf: 9 new changesets (Bitbucket)
   7. commit/dotnetrdf: rvesse: Note upcoming tabbed	interface
      changes (TOOLS-390) (Bitbucket)
   8. commit/dotnetrdf: 6 new changesets (Bitbucket)


----------------------------------------------------------------------

Message: 1
Date: Fri, 06 Dec 2013 14:16:29 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

3 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e8bf85d89f5a/
Changeset:   e8bf85d89f5a
Branch:      CORE-377
User:        rvesse
Date:        2013-12-06 15:04:29
Summary:     Split StardogConnectionDefinition into 1.x and 2.x classes (CORE-377)
Affected #:  4 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/87890b01a61f/
Changeset:   87890b01a61f
Branch:      CORE-377
User:        rvesse
Date:        2013-12-06 15:10:02
Summary:     Make connection settings scrollable when necessary (CORE-377)
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b738d69ee985/
Changeset:   b738d69ee985
Branch:      CORE-377
User:        rvesse
Date:        2013-12-06 15:15:44
Summary:     Fix resixing New Connection form (CORE-377)
Affected #:  2 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



------------------------------

Message: 2
Date: Fri, 06 Dec 2013 17:25:59 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

2 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/311c19eb665f/
Changeset:   311c19eb665f
Branch:      CORE-377
User:        rvesse
Date:        2013-12-06 18:14:47
Summary:     Make Edit Connection form fully resizable (CORE-377)
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ad53b6da5463/
Changeset:   ad53b6da5463
Branch:      CORE-377
User:        rvesse
Date:        2013-12-06 18:25:40
Summary:     Stub out design for new Connection Management interface (CORE-377)
Affected #:  5 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



------------------------------

Message: 3
Date: Fri, 06 Dec 2013 17:32:40 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Stub out design
	for a reusable Connection Management control (CORE-377)
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/fdff1522f430/
Changeset:   fdff1522f430
Branch:      CORE-377
User:        rvesse
Date:        2013-12-06 18:32:24
Summary:     Stub out design for a reusable Connection Management control (CORE-377)
Affected #:  4 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



------------------------------

Message: 4
Date: Sat, 07 Dec 2013 11:50:49 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

3 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/70c8a5d6f841/
Changeset:   70c8a5d6f841
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-07 12:49:16
Summary:     Stub out a container class for managing everything about a connection that StoreManager may need to know (TOOLS-377)
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/7e37ee4cfeac/
Changeset:   7e37ee4cfeac
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-07 12:49:42
Summary:     Update project file (TOOLS-377)
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ee0b6e355183/
Changeset:   ee0b6e355183
Branch:      CORE-377
User:        rvesse
Date:        2013-12-07 12:50:04
Summary:     Renamed to TOOLS-377, use that branch instead
Affected #:  0 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



------------------------------

Message: 5
Date: Sat, 07 Dec 2013 13:11:55 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 4 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

4 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c2b5ed6f3c80/
Changeset:   c2b5ed6f3c80
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-07 13:06:53
Summary:     More implementation of new Connection class (TOOLS-377)
Affected #:  4 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0f75e8b1456a/
Changeset:   0f75e8b1456a
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-07 13:30:28
Summary:     Finish initial implementation of Connection class (TOOLS-377)
Affected #:  4 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/06ff3314e821/
Changeset:   06ff3314e821
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-07 13:59:27
Summary:     Add classes to StoreManager.Core for managing a Graph of connection instances (TOOLS-377)
Affected #:  5 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/88c4f513f643/
Changeset:   88c4f513f643
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-07 14:11:30
Summary:     More work on connection graphs and their associated classes (TOOLS-377)
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: 6
Date: Tue, 10 Dec 2013 14:10:54 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 9 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

9 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/cc46d07ceb44/
Changeset:   cc46d07ceb44
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-09 15:35:58
Summary:     Add Copy() method implementations to all IConnectionDefinition implementations (TOOLS-377)
Affected #:  11 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/903d5f47be8f/
Changeset:   903d5f47be8f
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-09 15:39:40
Summary:     Add missing license headers (TOOLS-377)
Affected #:  10 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/89edf7643919/
Changeset:   89edf7643919
Branch:      CORE-376
User:        rvesse
Date:        2013-12-09 16:47:42
Summary:     Still trying to get Stardog native Update working, still no luck (CORE-376)
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9847756b911b/
Changeset:   9847756b911b
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-09 16:52:04
Summary:     ActiveConnectionsGraph class for storing open connections (TOOLS-377)
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d07ab3df4bfe/
Changeset:   d07ab3df4bfe
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-09 17:11:02
Summary:     Minor tweak to About Form (TOOLS-377)
Affected #:  3 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/007767b0f710/
Changeset:   007767b0f710
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-09 17:58:50
Summary:     Add appropriate events to Connection and IConnectionsGraph to make them easier to use in data bound contexts, more implementation on the ConnectionManagementListView control (TOOLS-377)
Affected #:  7 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/7d70b1a386f5/
Changeset:   7d70b1a386f5
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-09 18:24:43
Summary:     More work on the ConnectionManagementListView control (TOOLS-377)
Affected #:  5 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8a71324045ab/
Changeset:   8a71324045ab
User:        rvesse
Date:        2013-12-10 15:09:18
Summary:     Fix BaseEndpoint ArgumentException caused by over-zealous resharpering
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/89f0061861c1/
Changeset:   89f0061861c1
Branch:      TOOLS-377
User:        rvesse
Date:        2013-12-10 15:09:46
Summary:     Merge in latest changes from default (TOOLS-377)
Affected #:  1 file

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



------------------------------

Message: 7
Date: Tue, 10 Dec 2013 14:49:05 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Note upcoming
	tabbed	interface changes (TOOLS-390)
To: dot...@li...
Message-ID: <201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d80a5fe2db7f/
Changeset:   d80a5fe2db7f
Branch:      TOOLS-390
User:        rvesse
Date:        2013-12-10 15:48:26
Summary:     Note upcoming tabbed interface changes (TOOLS-390)
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: 8
Date: Wed, 11 Dec 2013 11:55:19 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 6 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

6 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/bd016b7da357/
Changeset:   bd016b7da357
Branch:      CORE-376
User:        rvesse
Date:        2013-12-10 15:53:35
Summary:     Merge in fixes from default (CORE-376)
Affected #:  4 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d0ed5bd40dfa/
Changeset:   d0ed5bd40dfa
User:        feugen24
Date:        2013-12-10 10:33:52
Summary:     Added tabs, query splitter, entities dynamic query
Affected #:  16 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6877b676c9eb/
Changeset:   6877b676c9eb
Branch:      TOOLS-390
User:        rvesse
Date:        2013-12-10 16:15:01
Summary:     Merge in Eugen F's tabbed interface contributions for testing (TOOLS-390)
Affected #:  16 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/68ec85866181/
Changeset:   68ec85866181
Branch:      TOOLS-390
User:        rvesse
Date:        2013-12-10 18:21:24
Summary:     Fix minor compile error (TOOLS-390)
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/aa5b4670c7ce/
Changeset:   aa5b4670c7ce
Branch:      TOOLS-390
User:        rvesse
Date:        2013-12-11 12:53:16
Summary:     Use flat button style for connection tabs (TOOLS-390)
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8ea74ea0384e/
Changeset:   8ea74ea0384e
User:        rvesse
Date:        2013-12-11 12:54:53
Summary:     Merge heads on default (TOOLS-390)
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.



------------------------------

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk

------------------------------

_______________________________________________
dotNetRDF-commits mailing list
dot...@li...
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits


End of dotNetRDF-commits Digest, Vol 14, Issue 2
************************************************

[dotNetRDF-Develop] Issue TOOLS-390 has been updated by Rob Vesse

[<tr...@do...>]

<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 tabbed interface for Store Manager</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>Progress changed from "0 %" to "20 %"
                                </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=390" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=390</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>

[dotNetRDF-Develop] Issue TOOLS-390 has a new comment

[<tr...@do...>]

<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 tabbed interface for Store Manager</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-12-10 05:21 PM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Had an initial look and it looks alright, have a few suggestions which I will pass onto Eugen to see what he thinks:</p>
<ul>
	<li>
		Instead of tabs with quick links to connections simple use another menu strip and add toolbar buttons</li>
	<li>
		Use SparqlParameterizedString to build the entity queries</li>
	<li>
		Move entity query features into a new Explore tab</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=390" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=390</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>

Re: [dotNetRDF-Develop] Store manager improvements

[Rob V. <rv...@do...>]

Thanks for that, I've pulled your changes locally and will try and take a
proper look at them tomorrow.  I've glanced over the code changes and
everything looks OK but I haven't got as far as running the revised UI yet.

When I do review properly I'll try and look at the entities query stuff and
see if there is any way to make it more efficient.

Thanks for spotting the bug in BaseEndpoint, I introduced this by accident
with a recent commit and it should now be fixed again with my most recent
commits

Cheers,

Rob

From:  Eugen F <feu...@ya...>
Reply-To:  Eugen F <feu...@ya...>
Date:  Tuesday, 10 December 2013 09:46
To:  Rob Vesse <rv...@do...>
Cc:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Subject:  Re: [dotNetRDF-Develop] Store manager improvements

> I've updated the repository, so maybe you can check the changes.
> 
> Note that there is a change in BaseEnpoint "throw new ArgumentException("HTTP
> Mode can only be GET/POST, derived implementations should override this
> property if they wish to support more methods");" that I had to comment in
> order to make the version from repository connect to an endpoint. (no relation
> to my changes).
> 
> Also I tried to make an external endpoint work with that entities change, but
> i only get timeouts...because of the complex query i think.
> 
> 
> 
> 
>  
>  
>  
>  
>  
>   On Monday, December 9, 2013 2:50 PM, Rob Vesse <rv...@do...> wrote:
>   
>   
> Eugen
> 
> Forking a Mercurial repository copies all branches, however if you could
> commit your changes to the default branch that would be best
> 
> Thanks,
> 
> Rob
> 
> From:  Eugen F <feu...@ya...>
> Reply-To:  Eugen F <feu...@ya...>
> Date:  Monday, 9 December 2013 12:20
> To:  Rob Vesse <rv...@do...>
> Subject:  Re: [dotNetRDF-Develop] Store manager improvements
> 
>> I have made the changes so it's now both MDI and tabs, forked repository at
>> https://bitbucket.org/feugen24/storemanager_tabs. Still I'm not sure it's the
>> correct version because there were lots of tags when creating the fork, so i
>> picked the "dynamic" that was selected by default. I assumed dynamic means
>> (latest). 
>> If it's ok i'll update this one.
>>  
>>  
>>  
>>  
>>  
>>   On Sunday, December 8, 2013 5:33 PM, Rob Vesse <rv...@do...>
>> wrote:
>>   
>>   
>> Hi Eugen
>> 
>> Thanks for the detailed email, yes there are advantages to a tabbed interface
>> though I suspect some users (like myself) may prefer to have the MDI
>> interface still.
>> 
>> What would be ideal from my perspective would be to integrate this such that
>> users can switch between the modes as desired, so users who prefer the
>> current interface can continue to use it and those that like the new
>> interface can use that instead.  Or even to have it such that you can dock
>> connections into a tabbed interface as and when desired.
>> 
>> The changes all sound useful but I haven't previewed them at all because I'm
>> afraid I'm not going to run a compiled executable from someone who's emailing
>> me for the very first time even if it does pass the virus checker.  If you
>> can provide either a link to the git repository, a patch against latest trunk
>> or ideally a mercurial fork that would be fantastic.  We use Mercurial for
>> our development with our main repository hosted on BitBucket at
>> http://bitbucket.org/dotnetrdf/dotnetrdf ­ if you can fork the code on
>> BitBucket, transfer your changes to there and then open a pull request that
>> would be the best way for us to see and review your changes.
>> 
>> Btw this is a subscription list, your email was moderated through and you've
>> been CC'd on this initial reply but if you could subscribe at
>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop so you can
>> participate in this discussion going forward without us having to manually CC
>> you each time that would be much appreciated.
>> 
>> Thanks,
>> 
>> Rob
>> 
>> From:  Eugen F <feu...@ya...>
>> Reply-To:  Eugen F <feu...@ya...>, dotNetRDF Developer Discussion and
>> Feature Request <dot...@li...>
>> Date:  Saturday, 7 December 2013 11:42
>> To:  "dot...@li..."
>> <dot...@li...>
>> Subject:  [dotNetRDF-Develop] Store manager improvements
>> 
>>> Hi,
>>> 
>>> I'm working with store manager and because of the midi interface it's
>>> difficult to interact with it, meaning each time i create a connection a new
>>> window is created, then when I run a query another window, rerun a
>>> query...new window, then close the one of the first query run and so on.
>>> 
>>> So i think the approach in sql server management studio or brightstardb
>>> polaris tool is much better. Both have tabs for each new connection, and
>>> when i rerun a query only results change (no new window).
>>> So i made the following changes:
>>> - when a connection is opened a new tab page is created and I add
>>> StoreManagerForm as a child to it
>>> - each tab has a close btn
>>> The rest of the functionality is the same except for query tab where:
>>> - i added a splitter control where panel 1 has query window , panel 2 has
>>> query results (both for graph and resultset)
>>> - i added a new button for orientation ( --| ) so we can change the
>>> orientation of the splitter ( vertical mode is v helpful on wide screens
>>> with few columns on results)
>>> - i removed "query" word from all buttons to occupy less space (i think it's
>>> obvious since we are in query window tab)
>>> - i changed AutoSizeColumnsMode to AllCells (previous was DisplayedCells but
>>> i had problems with it when large uri's where not in current view)
>>> 
>>> I also added a feature (in query tab) to expand a query for some subjects so
>>> i can see all the properties and values of those subjects. This allows a
>>> user to see similar results as sql server in case he has entities. For
>>> example if a user is using Entityframework api from brightstardb he can the
>>> select entities of rdf:type "Car" and see all car entities with values, in a
>>> table.
>>> - i added a new checkbox "AsEntities" that allows this feature when checked
>>> (it takes first variable from the current query as entity id/subject)
>>> It transforms user query to get all properties and the dynamically creates a
>>> query to get the entities.
>>> - i also added a numeric control next to the checkbox with default value of
>>> 1. This was necessary because in may case I have some predicates that are
>>> entities themselves and i need to filter those out. (a group by is used to
>>> filter predicates using that default value of 1)
>>> 
>>> I've attached the working version so you can play with it. I worked on a
>>> local git source control using latest 102 source code.
>>> Let me know what you think of the changes, and if it's ok, how to
>>> send/publish the source code. I've not really worked on any open source
>>> project so i don't know the flow.
>>> ----------------------------------------------------------------------------
>>> -- Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps
>>> with a single code base. Download it for free now!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
>>> _______________________________________________ dotNetRDF-develop mailing
>>> list 
>>> dot...@li...https://lists.sourceforge.net/lists/l
>>> istinfo/dotnetrdf-develop
>> 
>> 
>>   
>>  
>>   
>>  
> 
> 
>   
>  
>   
>  

[dotNetRDF-Develop] Issue TOOLS-390 has been added to a project you are monitoring.

[<tr...@do...>]

<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>Provide a tabbed interface for Store Manager</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.4</td>
  </tr>
  <tr>
    <td><b>Category:</b></td>
    <td>Store Manager</td>
  </tr>
  <tr>
    <td><b>Priority:</b></td>
    <td>Normal</td>
  </tr>
  <tr>
    <td><b>Type:</b></td>
    <td>Improvement</td>
  </tr>
  <tr>
    <td><b>Description:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	A user on the developers list has suggested that Store Manager would be more user friendly if it had a tabbed interface rather than a multi-window interface, there is a contributed patch for this available in a fork at&nbsp;<a href="https://bitbucket.org/feugen24/storemanager_tabs">https://bitbucket.org/feugen24/storemanager_tabs</a></p>
<p>
	This task tracks the work to review and integrate that patch</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=390" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=390</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>

Re: [dotNetRDF-Develop] Store manager improvements

[Eugen F <feu...@ya...>]

I've updated the repository, so maybe you can check the changes.

Note that there is a change in BaseEnpoint "throw new ArgumentException("HTTP Mode can only be GET/POST, derived implementations should override this property if they wish to support more methods");" that I had to comment in order to make the version from repository connect to an endpoint. (no relation to my changes).

Also I tried to make an external endpoint work with that entities change, but i only get timeouts...because of the complex query i think.








On Monday, December 9, 2013 2:50 PM, Rob Vesse <rv...@do...> wrote:
 
Eugen

Forking a Mercurial repository copies all branches, however if you could commit your changes to the default branch that would be best

Thanks,

Rob

From:  Eugen F <feu...@ya...>
Reply-To:  Eugen F <feu...@ya...>
Date:  Monday, 9 December 2013 12:20
To:  Rob Vesse <rv...@do...>
Subject:  Re: [dotNetRDF-Develop] Store manager improvements


I have made the changes so it's now both MDI and tabs, forked repository at https://bitbucket.org/feugen24/storemanager_tabs. Still I'm not sure it's the correct version because there were lots of tags when creating the fork, so i picked the "dynamic" that was selected by default. I assumed dynamic means (latest). 
>
>If it's ok i'll update this one.
>
>
>
>
>On Sunday, December 8, 2013 5:33 PM, Rob Vesse <rv...@do...> wrote:
> 
>Hi Eugen
>
>
>Thanks for the detailed email, yes there are advantages to a tabbed interface though I suspect some users (like myself) may prefer to have the MDI interface still.
>
>
>What would be ideal from my perspective would be to integrate this such that users can switch between the modes as desired, so users who prefer the current interface can continue to use it and those that like the new interface can use that instead.  Or even to have it such that you can dock connections into a tabbed interface as and when desired.
>
>
>The changes all sound useful but I haven't previewed them at all because I'm afraid I'm not going to run a compiled executable from someone who's emailing me for the very first time even if it does pass the virus checker.  If you can provide either a link to the git repository, a patch against latest trunk or ideally a mercurial fork that would be fantastic.  We use Mercurial for our development with our main repository hosted on BitBucket at http://bitbucket.org/dotnetrdf/dotnetrdf – if you can fork the code on BitBucket, transfer your changes to there and then open a pull request that would be the best way for us to see and review your changes.
>
>
>Btw this is a subscription list, your email was moderated through and you've been CC'd on this initial reply but if you could subscribe at https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop so you can participate in this discussion going forward without us having to manually CC you each time that would be much appreciated.
>
>
>Thanks,
>
>
>Rob
>
>
>From:  Eugen F <feu...@ya...>
>Reply-To:  Eugen F <feu...@ya...>, dotNetRDF Developer Discussion and Feature Request <dot...@li...>
>Date:  Saturday, 7 December 2013 11:42
>To:  "dot...@li..." <dot...@li...>
>Subject:  [dotNetRDF-Develop] Store manager improvements
>
>
>
>Hi,
>>
>>
>>I'm working with store manager and because of the midi interface it's difficult to interact with it, meaning each time i create a connection a new window is created, then when I run a query another window, rerun a query...new window, then close the one of the first query run and so on.
>>
>>
>>So i think the approach in sql server management studio or brightstardb polaris tool is much better. Both have tabs for each new connection, and when i rerun a query only results change (no new window).
>>So i made the following changes:
>>- when a connection is opened a new tab page is created and I add StoreManagerForm as a child to it
>>- each tab has a close btn 
>>
>>The rest of the functionality is the same except for query tab where:
>>- i added a splitter control where panel 1 has query window , panel 2 has query results (both for graph and resultset)
>>
>>- i added a new button for orientation ( --| ) so we can change the orientation of the splitter ( vertical mode is v helpful on wide screens with few columns on results)
>>- i removed "query" word from all buttons to occupy less space (i think it's obvious since we are in query window tab)
>>
>>- i changed AutoSizeColumnsMode to AllCells (previous was DisplayedCells but i had problems with it when large uri's where not in current view)
>>
>>
>>I also added a feature (in query tab) to expand a query for some subjects so i can see all the properties and values of those subjects. This allows a user to see similar results as sql server in case he has entities. For example if a user is using Entityframework api from brightstardb he can the select entities of rdf:type "Car" and see all car entities with values, in a table.
>>- i added a new checkbox "AsEntities" that allows this feature when checked (it takes first variable from the current query as entity id/subject)
>>
>>It transforms user query to get all properties and the dynamically creates a query to get the entities.
>>- i also added a numeric control next to the checkbox with default value of 1. This was necessary because in may case I have some predicates that are entities themselves and i need to filter those out. (a group by is used to filter predicates using that default value of 1)
>>
>>
>>I've attached the working version so you can play with it. I worked on a local git source control using latest 102 source code.
>>Let me know what you think of the changes, and if it's ok, how to send/publish the source code. I've not really worked on any open source project so i don't know the flow.------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk_______________________________________________ dotNetRDF-develop mailing list dot...@li...https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
>

Re: [dotNetRDF-Develop] Store manager improvements

[Rob V. <rv...@do...>]

Eugen

Forking a Mercurial repository copies all branches, however if you could
commit your changes to the default branch that would be best

Thanks,

Rob

From:  Eugen F <feu...@ya...>
Reply-To:  Eugen F <feu...@ya...>
Date:  Monday, 9 December 2013 12:20
To:  Rob Vesse <rv...@do...>
Subject:  Re: [dotNetRDF-Develop] Store manager improvements

> I have made the changes so it's now both MDI and tabs, forked repository at
> https://bitbucket.org/feugen24/storemanager_tabs. Still I'm not sure it's the
> correct version because there were lots of tags when creating the fork, so i
> picked the "dynamic" that was selected by default. I assumed dynamic means
> (latest). 
> If it's ok i'll update this one.
>  
>  
>  
>  
>  
>   On Sunday, December 8, 2013 5:33 PM, Rob Vesse <rv...@do...> wrote:
>   
>   
> Hi Eugen
> 
> Thanks for the detailed email, yes there are advantages to a tabbed interface
> though I suspect some users (like myself) may prefer to have the MDI interface
> still.
> 
> What would be ideal from my perspective would be to integrate this such that
> users can switch between the modes as desired, so users who prefer the current
> interface can continue to use it and those that like the new interface can use
> that instead.  Or even to have it such that you can dock connections into a
> tabbed interface as and when desired.
> 
> The changes all sound useful but I haven't previewed them at all because I'm
> afraid I'm not going to run a compiled executable from someone who's emailing
> me for the very first time even if it does pass the virus checker.  If you can
> provide either a link to the git repository, a patch against latest trunk or
> ideally a mercurial fork that would be fantastic.  We use Mercurial for our
> development with our main repository hosted on BitBucket at
> http://bitbucket.org/dotnetrdf/dotnetrdf ­ if you can fork the code on
> BitBucket, transfer your changes to there and then open a pull request that
> would be the best way for us to see and review your changes.
> 
> Btw this is a subscription list, your email was moderated through and you've
> been CC'd on this initial reply but if you could subscribe at
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop so you can
> participate in this discussion going forward without us having to manually CC
> you each time that would be much appreciated.
> 
> Thanks,
> 
> Rob
> 
> From:  Eugen F <feu...@ya...>
> Reply-To:  Eugen F <feu...@ya...>, dotNetRDF Developer Discussion and
> Feature Request <dot...@li...>
> Date:  Saturday, 7 December 2013 11:42
> To:  "dot...@li..."
> <dot...@li...>
> Subject:  [dotNetRDF-Develop] Store manager improvements
> 
>> Hi,
>> 
>> I'm working with store manager and because of the midi interface it's
>> difficult to interact with it, meaning each time i create a connection a new
>> window is created, then when I run a query another window, rerun a
>> query...new window, then close the one of the first query run and so on.
>> 
>> So i think the approach in sql server management studio or brightstardb
>> polaris tool is much better. Both have tabs for each new connection, and when
>> i rerun a query only results change (no new window).
>> So i made the following changes:
>> - when a connection is opened a new tab page is created and I add
>> StoreManagerForm as a child to it
>> - each tab has a close btn
>> The rest of the functionality is the same except for query tab where:
>> - i added a splitter control where panel 1 has query window , panel 2 has
>> query results (both for graph and resultset)
>> - i added a new button for orientation ( --| ) so we can change the
>> orientation of the splitter ( vertical mode is v helpful on wide screens with
>> few columns on results)
>> - i removed "query" word from all buttons to occupy less space (i think it's
>> obvious since we are in query window tab)
>> - i changed AutoSizeColumnsMode to AllCells (previous was DisplayedCells but
>> i had problems with it when large uri's where not in current view)
>> 
>> I also added a feature (in query tab) to expand a query for some subjects so
>> i can see all the properties and values of those subjects. This allows a user
>> to see similar results as sql server in case he has entities. For example if
>> a user is using Entityframework api from brightstardb he can the select
>> entities of rdf:type "Car" and see all car entities with values, in a table.
>> - i added a new checkbox "AsEntities" that allows this feature when checked
>> (it takes first variable from the current query as entity id/subject)
>> It transforms user query to get all properties and the dynamically creates a
>> query to get the entities.
>> - i also added a numeric control next to the checkbox with default value of
>> 1. This was necessary because in may case I have some predicates that are
>> entities themselves and i need to filter those out. (a group by is used to
>> filter predicates using that default value of 1)
>> 
>> I've attached the working version so you can play with it. I worked on a
>> local git source control using latest 102 source code.
>> Let me know what you think of the changes, and if it's ok, how to
>> send/publish the source code. I've not really worked on any open source
>> project so i don't know the flow.
>> -----------------------------------------------------------------------------
>> - Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps
>> with a single code base. Download it for free now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk_
>> ______________________________________________ dotNetRDF-develop mailing list
>> dot...@li...https://lists.sourceforge.net/lists/li
>> stinfo/dotnetrdf-develop
> 
> 
>   
>  
>   
>  

Re: [dotNetRDF-Develop] Store manager improvements

[Rob V. <rv...@do...>]

Hi Eugen

Thanks for the detailed email, yes there are advantages to a tabbed
interface though I suspect some users (like myself) may prefer to have the
MDI interface still.

What would be ideal from my perspective would be to integrate this such that
users can switch between the modes as desired, so users who prefer the
current interface can continue to use it and those that like the new
interface can use that instead.  Or even to have it such that you can dock
connections into a tabbed interface as and when desired.

The changes all sound useful but I haven't previewed them at all because I'm
afraid I'm not going to run a compiled executable from someone who's
emailing me for the very first time even if it does pass the virus checker.
If you can provide either a link to the git repository, a patch against
latest trunk or ideally a mercurial fork that would be fantastic.  We use
Mercurial for our development with our main repository hosted on BitBucket
at http://bitbucket.org/dotnetrdf/dotnetrdf ­ if you can fork the code on
BitBucket, transfer your changes to there and then open a pull request that
would be the best way for us to see and review your changes.

Btw this is a subscription list, your email was moderated through and you've
been CC'd on this initial reply but if you could subscribe at
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop so you can
participate in this discussion going forward without us having to manually
CC you each time that would be much appreciated.

Thanks,

Rob

From:  Eugen F <feu...@ya...>
Reply-To:  Eugen F <feu...@ya...>, dotNetRDF Developer Discussion and
Feature Request <dot...@li...>
Date:  Saturday, 7 December 2013 11:42
To:  "dot...@li..."
<dot...@li...>
Subject:  [dotNetRDF-Develop] Store manager improvements

> Hi,
> 
> I'm working with store manager and because of the midi interface it's
> difficult to interact with it, meaning each time i create a connection a new
> window is created, then when I run a query another window, rerun a query...new
> window, then close the one of the first query run and so on.
> 
> So i think the approach in sql server management studio or brightstardb
> polaris tool is much better. Both have tabs for each new connection, and when
> i rerun a query only results change (no new window).
> So i made the following changes:
> - when a connection is opened a new tab page is created and I add
> StoreManagerForm as a child to it
> - each tab has a close btn
> The rest of the functionality is the same except for query tab where:
> - i added a splitter control where panel 1 has query window , panel 2 has
> query results (both for graph and resultset)
> - i added a new button for orientation ( --| ) so we can change the
> orientation of the splitter ( vertical mode is v helpful on wide screens with
> few columns on results)
> - i removed "query" word from all buttons to occupy less space (i think it's
> obvious since we are in query window tab)
> - i changed AutoSizeColumnsMode to AllCells (previous was DisplayedCells but i
> had problems with it when large uri's where not in current view)
> 
> I also added a feature (in query tab) to expand a query for some subjects so i
> can see all the properties and values of those subjects. This allows a user to
> see similar results as sql server in case he has entities. For example if a
> user is using Entityframework api from brightstardb he can the select entities
> of rdf:type "Car" and see all car entities with values, in a table.
> - i added a new checkbox "AsEntities" that allows this feature when checked
> (it takes first variable from the current query as entity id/subject)
> It transforms user query to get all properties and the dynamically creates a
> query to get the entities.
> - i also added a numeric control next to the checkbox with default value of 1.
> This was necessary because in may case I have some predicates that are
> entities themselves and i need to filter those out. (a group by is used to
> filter predicates using that default value of 1)
> 
> I've attached the working version so you can play with it. I worked on a local
> git source control using latest 102 source code.
> Let me know what you think of the changes, and if it's ok, how to send/publish
> the source code. I've not really worked on any open source project so i don't
> know the flow.
> ------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a
> single code base. Download it for free now!
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk__
> _____________________________________________ dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

[dotNetRDF-Develop] Issue TOOLS-377 has a new comment

[<tr...@do...>]

<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>Improve connection management for Favourite and Recent connections in StoreManager</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-12-07 01:12 PM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Have started work on 2 and 3, turning into a slightly more comprehensive refactor of connection management but that isn&#39;t a bad thing</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=377" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=377</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>

[dotNetRDF-Develop] Issue TOOLS-377 has been updated by Rob Vesse

[<tr...@do...>]

<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>Improve connection management for Favourite and Recent connections in StoreManager</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>Progress changed from "0 %" to "40 %"
                                </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=377" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=377</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>

[dotNetRDF-Develop] Issue TOOLS-377 has a new comment

[<tr...@do...>]

<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>Improve connection management for Favourite and Recent connections in StoreManager</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-12-06 02:14 PM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Both parts of Item 1 are implemented, I haven&#39;t started on the other Items yet</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=377" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=377</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>

[dotNetRDF-Develop] Issue CORE-389 has a new comment

[<tr...@do...>]

<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>WITH DELETE WHERE incorrectly permitted</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-12-06 01:55 PM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Trivial fix applied to default</p></td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=389" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=389</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>

[dotNetRDF-Develop] Issue CORE-389 has been updated by Rob Vesse

[<tr...@do...>]

<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>WITH DELETE WHERE incorrectly permitted</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=389" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=389</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>

[dotNetRDF-Develop] dotNetRDF-commits Digest, Vol 14, Issue 1

[<dot...@li...>]

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: rvesse: Fix for GraphBenchmaker to
      recognize and allow configuration of Graph types with different
      Triple collection instances (Bitbucket)
   2. commit/dotnetrdf: 2 new changesets (Bitbucket)
   3. commit/dotnetrdf: rvesse: Couple more tests for	CORE-386
      (Bitbucket)
   4. commit/dotnetrdf: 2 new changesets (Bitbucket)
   5. commit/dotnetrdf: rvesse: Fix a subtle bug in Left Join
      Product evaluation that was cause additional incorrect results to
      be produced from the join (CORE-386) (Bitbucket)
   6. commit/dotnetrdf: rvesse: Ensure all Timeout properties state
      that the unit is milliseconds (CORE-387) (Bitbucket)
   7. commit/dotnetrdf: 3 new changesets (Bitbucket)
   8. commit/dotnetrdf: rvesse: Add async implementation of SPARQL
      Update for Stardog, currently untested (CORE-376) (Bitbucket)
   9. commit/dotnetrdf: 3 new changesets (Bitbucket)


----------------------------------------------------------------------

Message: 1
Date: Sat, 23 Nov 2013 16:23:24 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Fix for
	GraphBenchmaker to recognize and allow configuration of Graph types
	with different Triple collection instances
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b409893a2154/
Changeset:   b409893a2154
Branch:      1.9
User:        rvesse
Date:        2013-11-23 17:23:07
Summary:     Fix for GraphBenchmaker to recognize and allow configuration of Graph types with different Triple collection instances
Affected #:  11 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



------------------------------

Message: 2
Date: Tue, 26 Nov 2013 09:59:01 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets
To: dot...@li...
Message-ID: <201...@ap...>
Content-Type: text/plain; charset="utf-8"

2 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/790b59f6ed42/
Changeset:   790b59f6ed42
User:        rvesse
Date:        2013-11-26 10:49:25
Summary:     Add unit tests based on CORE-386 discussion
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d634ba28882f/
Changeset:   d634ba28882f
User:        rvesse
Date:        2013-11-26 10:58:43
Summary:     Expand unit tests from CORE-386 with more cases and more queries
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: Tue, 26 Nov 2013 10:18:44 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Couple more
	tests for	CORE-386
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/31a637d1831f/
Changeset:   31a637d1831f
User:        rvesse
Date:        2013-11-26 11:18:29
Summary:     Couple more tests for CORE-386
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: Wed, 27 Nov 2013 10:30:35 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

2 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/468c40c17fd0/
Changeset:   468c40c17fd0
User:        rvesse
Date:        2013-11-27 10:33:01
Summary:     Correction based on continuining CORE-386 discussion
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/475d5c89f3da/
Changeset:   475d5c89f3da
User:        rvesse
Date:        2013-11-27 11:30:06
Summary:     Revise test cases for CORE-386 to show that they are failing, not sure if this is a bug orthat we are interpreting the specification correctly and other libraries are not
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: 5
Date: Wed, 27 Nov 2013 16:30:35 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Fix a subtle
	bug in Left Join Product evaluation that was cause additional
	incorrect results to be produced from the join (CORE-386)
To: dot...@li...
Message-ID: <201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9a87cc59631a/
Changeset:   9a87cc59631a
User:        rvesse
Date:        2013-11-27 17:30:14
Summary:     Fix a subtle bug in Left Join Product evaluation that was cause additional incorrect results to be produced from the join (CORE-386)
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: 6
Date: Fri, 06 Dec 2013 11:38:37 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Ensure all
	Timeout properties state that the unit is milliseconds (CORE-387)
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/77c8d1b052f6/
Changeset:   77c8d1b052f6
User:        rvesse
Date:        2013-12-06 12:38:17
Summary:     Ensure all Timeout properties state that the unit is milliseconds (CORE-387)
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: 7
Date: Fri, 06 Dec 2013 12:38:46 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

3 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/39c785475ec2/
Changeset:   39c785475ec2
Branch:      CORE-376
User:        rvesse
Date:        2013-12-06 13:09:28
Summary:     Initial pass at synchronous SPARQL Update implementation for Stardog (CORE-376), currently fails tests so HTTP Storage error reporting has been enhanced to include more information in error message
Affected #:  3 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b4cfebf190f5/
Changeset:   b4cfebf190f5
Branch:      CORE-376
User:        rvesse
Date:        2013-12-06 13:14:37
Summary:     Minor fix to update test cases which shows the sync update implementation for Stardog does appear to be correct (CORE-376)
Affected #:  3 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f279e6e9b91f/
Changeset:   f279e6e9b91f
Branch:      CORE-376
User:        rvesse
Date:        2013-12-06 13:38:23
Summary:     Start writing tests for Stardog update support, tests currently fail due to apparent bugs in Stardog's SPARQL Update implementation (CORE-376)
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: 8
Date: Fri, 06 Dec 2013 12:43:58 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Add async
	implementation of SPARQL Update for Stardog, currently untested
	(CORE-376)
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6b3b8520f232/
Changeset:   6b3b8520f232
Branch:      CORE-376
User:        rvesse
Date:        2013-12-06 13:43:43
Summary:     Add async implementation of SPARQL Update for Stardog, currently untested (CORE-376)
Affected #:  1 file

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



------------------------------

Message: 9
Date: Fri, 06 Dec 2013 13:56:16 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets
To: dot...@li...
Message-ID: <201...@ap...>
Content-Type: text/plain; charset="utf-8"

3 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9b0ad4723b11/
Changeset:   9b0ad4723b11
Branch:      CORE-389
User:        rvesse
Date:        2013-12-06 14:55:24
Summary:     Fix and unit test for CORE-389
Affected #:  3 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ec98f924eb0b/
Changeset:   ec98f924eb0b
Branch:      CORE-389
User:        rvesse
Date:        2013-12-06 14:55:32
Summary:     Close the CORE-389 branch
Affected #:  0 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/de1b048c68ee/
Changeset:   de1b048c68ee
User:        rvesse
Date:        2013-12-06 14:55:47
Summary:     Merge in CORE-389 fix
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.



------------------------------

------------------------------------------------------------------------------
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk

------------------------------

_______________________________________________
dotNetRDF-commits mailing list
dot...@li...
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits


End of dotNetRDF-commits Digest, Vol 14, Issue 1
************************************************

[dotNetRDF-Develop] Issue CORE-389 has been added to a project you are monitoring.

[<tr...@do...>]

<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>WITH DELETE WHERE incorrectly permitted</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.3</td>
  </tr>
  <tr>
    <td><b>Category:</b></td>
    <td>Update</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>
	Currently we are allowing the shorthand DELETE WHERE form to be used with a WITH clause which is invalid per the SPARQL specification, we should correct this.</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=389" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=389</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>

[dotNetRDF-Develop] Issue CORE-376 has been updated by Rob Vesse

[<tr...@do...>]

<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 native SPARQL Update for Stardog 2.0 connections</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Progress changed from "40 %" to "70 %"
                                </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=376" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=376</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>

[dotNetRDF-Develop] Issue CORE-376 has a new comment

[<tr...@do...>]

<p>A new comment has been added to the following issue.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Support native SPARQL Update for Stardog 2.0 connections</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-12-06 12:43 PM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Have both synchronous and asynchronous implementations written on the CORE-376 branch, not yet fully tested because I&#39;ve encountered some possible bugs in the Stardog SPARQL Update implementation</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=376" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=376</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>

[dotNetRDF-Develop] Issue CORE-376 has been updated by Rob Vesse

[<tr...@do...>]

<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 native SPARQL Update for Stardog 2.0 connections</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Status changed from "Planned" to "In Progress"
                                </li>
        <li>Progress changed from "0 %" to "40 %"
                                </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=376" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=376</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>

[dotNetRDF-Develop] Issue CORE-387 has a new comment

[<tr...@do...>]

<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>Clarify that the BaseEndpoint.Timeout attribute is in milliseconds</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-12-06 11:36 AM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Fixed in default</p></td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=387" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=387</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>

[dotNetRDF-Develop] Issue CORE-387 has been updated by Rob Vesse

[<tr...@do...>]

<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>Clarify that the BaseEndpoint.Timeout attribute is in milliseconds</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 "Completed"
                                </li>
        <li>Assigned to changed from "Unassigned" to "none"
                                </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=387" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=387</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>

[dotNetRDF-Develop] Issue TOOLS-385 has a new comment

[<tr...@do...>]

<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>Store Manager unable to return results when non-printable characters are part of result</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-12-06 10:12 AM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	Walter</p>
<p>
	The download you reference is in a non-RDF based XML format so I presume you either transform this to RDF somehow or Entagen Extra does this for you? &nbsp;Since I don&#39;t have access to the actual data I can&#39;t attempt to reproduce myself.</p>
<p>
	&nbsp;</p>
<p>
	However looking at the error message again I believe this is not a bug in dotNetRDF rather an error in the data coming from Entagen Extra, this may either be down to bad data at ingest time or Entagen Extra failing to generate valid XML correctly. &nbsp;From <a href="http://www.w3.org/TR/xml/#charsets">Section 2.2 of the XML Specification</a>&nbsp;only the following characters are considered valid in XML:</p>
<table class="scrap" style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: medium;" summary="Scrap">
	<tbody>
		<tr valign="baseline">
			<td>
				<code>Char</code></td>
			<td>
				&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td>
			<td>
				<code>#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]</code><br />
				&nbsp;</td>
		</tr>
	</tbody>
</table>
<p>
	Which makes the character the error references an invalid character since it is not in this range.</p>
<p>
	Assuming that Entagen Extra is producing SPARQL XML Results then dotNetRDF is prefectly correct in rejecting the data since the XML itself is invalid, likely the error is bubbling up from System.Xml. &nbsp;You can confirm if this is the case by viewing the error trace associated with the failed task, right click on the task and select&nbsp;<strong>View Error Trace</strong> or click the equivalent button from the Task Information dialogue for the failed task (which is where you got the query and algebra you pasted into your original report).</p>
<p>
	If this is not the case then I would need to see that error trace (and preferably your actual data as well) to be able to proceed with any further investigation.</p>
<p>
	&nbsp;</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=385" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=385</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>

[dotNetRDF-Develop] Issue TOOLS-385 has a new comment

[<tr...@do...>]

<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>Store Manager unable to return results when non-printable characters are part of result</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Toolkit</td>
  </tr>
  <tr>
    <td><b>Created By:</b></td>
    <td>Walter</td>
  </tr>
  <tr>
    <td><b>Date:</b></td>
    <td>2013-12-06 01:31 AM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
 Hi Rob,</p>
<p>
 Thanks for your reply. We are using an internal&nbsp;Entagen Extera server for the query. You may find a copy of the DrugBank here <a href="http://www.drugbank.ca">www.drugbank.ca</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=385" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=385</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>