Menu
▾
▴
dotnetrdf-develop — Developer Discussion and Feature Request
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
(11) |
Mar
(17) |
Apr
(12) |
May
(2) |
Jun
(20) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(5) |
| 2011 |
Jan
(4) |
Feb
(1) |
Mar
(2) |
Apr
(2) |
May
(5) |
Jun
|
Jul
(12) |
Aug
(4) |
Sep
(5) |
Oct
(1) |
Nov
(38) |
Dec
(27) |
| 2012 |
Jan
(46) |
Feb
(182) |
Mar
(83) |
Apr
(22) |
May
(68) |
Jun
(47) |
Jul
(135) |
Aug
(84) |
Sep
(57) |
Oct
(45) |
Nov
(27) |
Dec
(61) |
| 2013 |
Jan
(59) |
Feb
(78) |
Mar
(66) |
Apr
(107) |
May
(27) |
Jun
(56) |
Jul
(53) |
Aug
(3) |
Sep
(19) |
Oct
(41) |
Nov
(44) |
Dec
(54) |
| 2014 |
Jan
(49) |
Feb
(72) |
Mar
(22) |
Apr
(41) |
May
(63) |
Jun
(27) |
Jul
(45) |
Aug
(12) |
Sep
(3) |
Oct
(8) |
Nov
(27) |
Dec
(16) |
| 2015 |
Jan
(3) |
Feb
(20) |
Mar
(6) |
Apr
(4) |
May
(15) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(16) |
May
(9) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <tr...@do...> - 2014-05-19 13:47:37
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SparqlQueryParser produces invalid FILTER(NOT EXISTS ..) expression from valid input.</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-05-19 02:46 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Duplicate of CORE-413</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=414" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=414</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-19 13:44:38
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SparqlQueryParser produces invalid FILTER(NOT EXISTS ..) expression from valid input.</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Sebastian Faubel</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unscheduled</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Normal</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
When I load a SPARQL query which contains FILTER NOT EXISTS { ?s ?p ?o } into the query parser, the generated query contains a FILTER(NOT EXISTS { ?s ?p ? o }) expression which is not valid SPARQL 1.1 syntax (http://www.w3.org/TR/sparql11-query/#rFilter) (tested in OpenLink Virtuoso). Bracketted expressions after the FILTER token are only allowed for numerical or logical expressions.. :)</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=415" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=415</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-19 13:44:29
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SparqlQueryParser produces invalid FILTER(NOT EXISTS ..) expression from valid input.</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Sebastian Faubel</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unscheduled</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Normal</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
When I load a SPARQL query which contains FILTER NOT EXISTS { ?s ?p ?o } into the query parser, the generated query contains a FILTER(NOT EXISTS { ?s ?p ? o }) expression which is not valid SPARQL 1.1 syntax (http://www.w3.org/TR/sparql11-query/#rFilter) (tested in OpenLink Virtuoso). Bracketted expressions after the FILTER token are only allowed for numerical or logical expressions.. :)</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=414" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=414</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-19 13:44:19
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SparqlQueryParser produces invalid FILTER(NOT EXISTS ..) expression from valid input.</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Sebastian Faubel</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unscheduled</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Normal</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
When I load a SPARQL query which contains FILTER NOT EXISTS { ?s ?p ?o } into the query parser, the generated query contains a FILTER(NOT EXISTS { ?s ?p ? o }) expression which is not valid SPARQL 1.1 syntax (http://www.w3.org/TR/sparql11-query/#rFilter) (tested in OpenLink Virtuoso). Bracketted expressions after the FILTER token are only allowed for numerical or logical expressions.. :)</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=413" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=413</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Zahra J. <jab...@gm...> - 2014-05-19 08:40:46
|
Hello, I am one of your site's fans! I have a question about using OWL file that is built with RDF\XML in Protege software.I don't know how can I use this OWL file in C#,and I want to use it in widows form in my project.If you can help me please answer immediately because I am in a hurry! Thanks for your attention. your sincerely, Zahra Jabalameli |
|
From: <tr...@do...> - 2014-05-16 13:18:13
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>NQuads export data doesn't include the 4th slot e.g. graph identifier with Fuseki</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Toolkit</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "In Progress" to "Completed"
</li>
<li>Issue Type changed from "Improvement" to "Bug"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Progress changed from "50 %" 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=409" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=409</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-16 13:18:00
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>NQuads export data doesn't include the 4th slot e.g. graph identifier with Fuseki</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Toolkit</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-05-16 02:17 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
In debugging this I spotted that it was possible for the default graph to be omitted from the output in some cases as well so I also fixed that as part of fixing this issue</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=409" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=409</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-16 13:01:01
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>NQuads export data doesn't include the 4th slot e.g. graph identifier with Fuseki</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Toolkit</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Unknown" to "In Progress"
</li>
<li>Progress changed from "0 %" to "50 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=409" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=409</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-16 13:00:45
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>NQuads export data doesn't include the 4th slot e.g. graph identifier with Fuseki</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Toolkit</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-05-16 01:59 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Confirmed that this is indeed a bug, it appears to apply to any store where the export is done in a streaming fashion</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=409" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=409</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-16 12:13:04
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Join linearisation breaks some queries with sequential left joins</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-05-16 01:12 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
An improved fix is now in default which will intelligently detect when it can and can't linearize left joins</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=406" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=406</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-16 12:12:34
|
<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>Join linearisation breaks some queries with sequential left joins</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "In Progress" to "Completed"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Progress changed from "75 %" 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=406" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=406</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-16 12:12:09
|
<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>Incorrect usage of == and != operator with Single.NaN and Double.NaN constants</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2"></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=412" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=412</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-16 12:05:56
|
<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>Incorrect usage of == and != operator with Single.NaN and Double.NaN constants</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-05-16 01:05 PM</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=412" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=412</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-16 12:05:43
|
<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>Incorrect usage of == and != operator with Single.NaN and Double.NaN constants</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "In Progress" to "Completed"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Progress changed from "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=412" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=412</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-16 12:01:20
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Incorrect usage of == and != operator with Single.NaN and Double.NaN constants</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>Title changed from "Incorrect usage of == and != operator with Single.NaN, Double.NaN and Float.NaN constants" to "Incorrect usage of == and != operator with Single.NaN and Double.NaN constants"
</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=412" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=412</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-16 11:56:11
|
<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>Incorrect usage of == and != operator with Single.NaN, Double.NaN and Float.NaN constants</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.5</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Core API</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Normal</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
As reported on the bugs list at <a href="http://sourceforge.net/p/dotnetrdf/mailman/message/32332452/">http://sourceforge.net/p/dotnetrdf/mailman/message/32332452/</a> we are incorrectly using the various NaN constants directly with the == and != operator which does not yield the correct behaviour (thanks .Net) so we need to change all relevant code to use the equivalent IsNaN() static methods</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=412" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=412</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <dot...@li...> - 2014-05-09 12:23:05
|
Send dotNetRDF-commits mailing list submissions to dot...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits or, via email, send a message with subject or body 'help' to dot...@li... You can reach the person managing the list at dot...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of dotNetRDF-commits digest..." Today's Topics: 1. commit/dotnetrdf: 2 new changesets (Bitbucket) 2. commit/dotnetrdf: 2 new changesets (Bitbucket) 3. commit/dotnetrdf: 5 new changesets (Bitbucket) 4. commit/dotnetrdf: 3 new changesets (Bitbucket) 5. commit/dotnetrdf: rvesse: Close branch ansell/add-link-to-bug-tracker-in-readmemd-1399421655743. (Bitbucket) 6. commit/dotnetrdf: rvesse: Close branch CORE-394. (Bitbucket) 7. commit/dotnetrdf: rvesse: Close branch CORE-378. (Bitbucket) 8. commit/dotnetrdf: 2 new changesets (Bitbucket) 9. commit/dotnetrdf: 3 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Wed, 07 May 2014 14:23:56 -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/6ae1bd5deea8/ Changeset: 6ae1bd5deea8 Branch: ansell/add-link-to-bug-tracker-in-readmemd-1399421655743 User: ansell Date: 2014-05-07 02:17:10 Summary: Add link to Bug tracker in README.md Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d9a230835baf/ Changeset: d9a230835baf User: rvesse Date: 2014-05-07 16:23:49 Summary: Merged in ansell/dotnetrdf/ansell/add-link-to-bug-tracker-in-readmemd-1399421655743 (pull request #28) Add link to Bug tracker in README.md Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Wed, 07 May 2014 16:20:29 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/56060580dfbf/ Changeset: 56060580dfbf Branch: CORE-410 User: rvesse Date: 2014-05-07 18:13:06 Summary: Failing test that demonstrates CORE-410 Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c8a86fea088a/ Changeset: c8a86fea088a Branch: CORE-410 User: rvesse Date: 2014-05-07 18:19:59 Summary: Fix for specific bug in CORE-410, needs additional unit tests for related cases Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 3 Date: Thu, 08 May 2014 08:38:31 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 5 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 5 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2cbe03d71b49/ Changeset: 2cbe03d71b49 Branch: CORE-410 User: rvesse Date: 2014-05-08 10:27:53 Summary: Further improvements to fully address CORE-410 Affected #: 6 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/7ca067f40c75/ Changeset: 7ca067f40c75 Branch: CORE-410 User: rvesse Date: 2014-05-08 10:28:43 Summary: Note CORE-410 fix in Change Log Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6d2c34f901a9/ Changeset: 6d2c34f901a9 User: rvesse Date: 2014-05-08 10:31:10 Summary: Merge CORE-410 fixes to default Affected #: 6 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/058c3233f34a/ Changeset: 058c3233f34a User: rvesse Date: 2014-05-08 10:36:06 Summary: Improve test case for CORE-410 Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/62bf71275efb/ Changeset: 62bf71275efb User: rvesse Date: 2014-05-08 10:38:02 Summary: Merge Peter Ansell's README tweak 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: Thu, 08 May 2014 09:23:32 -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/a3c571a83454/ Changeset: a3c571a83454 Branch: CORE-411 User: rvesse Date: 2014-05-08 11:02:28 Summary: Improvements to error message for excess tokens for a triple pattern (CORE-411) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b11f6cff3557/ Changeset: b11f6cff3557 Branch: CORE-411 User: rvesse Date: 2014-05-08 11:03:22 Summary: Note CORE-411 improvement in Change Log Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/03aba3489b57/ Changeset: 03aba3489b57 User: rvesse Date: 2014-05-08 11:05:16 Summary: Merge CORE-411 improvements 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: 5 Date: Thu, 08 May 2014 09:29:08 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Close branch ansell/add-link-to-bug-tracker-in-readmemd-1399421655743. 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/d6c50af9e68f/ Changeset: d6c50af9e68f Branch: ansell/add-link-to-bug-tracker-in-readmemd-1399421655743 User: rvesse Date: 2014-05-08 11:29:03 Summary: Close branch ansell/add-link-to-bug-tracker-in-readmemd-1399421655743. 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: 6 Date: Thu, 08 May 2014 09:29:54 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Close branch CORE-394. 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/873af09ae858/ Changeset: 873af09ae858 Branch: CORE-394 User: rvesse Date: 2014-05-08 11:29:49 Summary: Close branch CORE-394. 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: 7 Date: Thu, 08 May 2014 09:30:33 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Close branch CORE-378. 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/bec18ee3b227/ Changeset: bec18ee3b227 Branch: CORE-378 User: rvesse Date: 2014-05-08 11:30:28 Summary: Close branch CORE-378. Affected #: 0 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 8 Date: Fri, 09 May 2014 10:44:04 -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/0c48b741edd0/ Changeset: 0c48b741edd0 Branch: CORE-406 User: rvesse Date: 2014-05-09 10:34:36 Summary: Bring CORE-406 back up to date with default Affected #: 9 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c60d39efb73c/ Changeset: c60d39efb73c Branch: CORE-406 User: rvesse Date: 2014-05-09 12:38:56 Summary: Add FixedVariables and FloatingVariables properties to all relevant classes as part of work towards better identifying linear vs non-linear left joins (CORE-406) Affected #: 50 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 9 Date: Fri, 09 May 2014 12:22:56 -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/3668c1249350/ Changeset: 3668c1249350 Branch: CORE-406 User: rvesse Date: 2014-05-09 13:38:40 Summary: Start adding variable classification tests (CORE-406) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5f1144176f52/ Changeset: 5f1144176f52 Branch: CORE-406 User: rvesse Date: 2014-05-09 13:54:23 Summary: More variable classification tests (CORE-406) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ecc3a2722cc4/ Changeset: ecc3a2722cc4 Branch: CORE-406 User: rvesse Date: 2014-05-09 14:19:47 Summary: Start to improve LeftJoin to only avoid linerazation when unsafe (CORE-406) 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. ------------------------------ ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 19, Issue 2 ************************************************ |
|
From: <tr...@do...> - 2014-05-08 09:24:36
|
<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>Error message for too many tokens for triple pattern needs to be more detailed</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-05-08 10:23 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Improvement to error message now on default, error messages now include details of the offending tokens</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=411" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=411</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-08 09:23:57
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Error message for too many tokens for triple pattern needs to be more detailed</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=411" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=411</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-08 08:44:17
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SPARQL/XML from Sesame Workbench contains an extra attribute</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "In Progress" to "Completed"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Progress changed from "90 %" to "100 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=410" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=410</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-08 08:44:17
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SPARQL/XML from Sesame Workbench contains an extra attribute</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-05-08 09:36 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Fixed in default, SPARQL Results XML parser will now merely issue a warning and ignore custom attributes</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=410" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=410</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-07 16:21:14
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SPARQL/XML from Sesame Workbench contains an extra attribute</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Confirmed" to "In Progress"
</li>
<li>Progress changed from "0 %" to "90 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=410" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=410</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-07 16:06:26
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SPARQL/XML from Sesame Workbench contains an extra attribute</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Description changed from "<p>
A user on StackOverflow reported having issues parsing the SPARQL/Results XML generated by Sesame Workbench when using dotNetRDF.</p>
<p>
http://stackoverflow.com/questions/23471782/unable-to-parse-a-sparql-result-set-since-a-literal-element-has-too-many-attri</p>
<p>
The current design for Sesame Workbench relies on XSLT to render HTML. For historical reasons this has included an extra attribute to specify a qname for the datatype for literals and a qname for URIs.</p>
<p>
Would it be possible to relax the cardinality constraints in the SPARQL/Results XML Parser on the expected number of attributes and ignore unrecognised attributes as long as all of the essential attributes are present?</p>
<p>
The extra attribute doesn't get inserted if they request the result directly from a Sesame Server or they programmatically serialise the result (by default) so this only happens when they query the Workbench UI but it has happened once so far!</p>
<p>
</p>" to "<p>
A user on StackOverflow reported having issues parsing the SPARQL/Results XML generated by Sesame Workbench when using dotNetRDF.</p>
<p>
<a href="http://stackoverflow.com/questions/23471782/unable-to-parse-a-sparql-result-set-since-a-literal-element-has-too-many-attri">http://stackoverflow.com/questions/23471782/unable-to-parse-a-sparql-result-set-since-a-literal-element-has-too-many-attri</a></p>
<p>
The current design for Sesame Workbench relies on XSLT to render HTML. For historical reasons this has included an extra attribute to specify a qname for the datatype for literals and a qname for URIs.</p>
<p>
Would it be possible to relax the cardinality constraints in the SPARQL/Results XML Parser on the expected number of attributes and ignore unrecognised attributes as long as all of the essential attributes are present?</p>
<p>
The extra attribute doesn't get inserted if they request the result directly from a Sesame Server or they programmatically serialise the result (by default) so this only happens when they query the Workbench UI but it has happened once so far!</p>
<p>
</p>"
</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=410" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=410</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-07 15:56:21
|
<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>Error message for too many tokens for triple pattern needs to be more detailed</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.5</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Parsing</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Normal</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
As shown in the question at <a href="http://stackoverflow.com/questions/23520917/dotnetrdf-sparql-query-to-get-subjects-with-a-specific-resource/23522578#23522578">http://stackoverflow.com/questions/23520917/dotnetrdf-sparql-query-to-get-subjects-with-a-specific-resource/23522578#23522578</a> the error message when a user has too many tokens to form a valid triple pattern is not overly helpful because it doesn't present the value of the token that caused the problem nor does it explain how the user might resolve the issue.</p>
<p>
It would be useful if the error message included the value of the offending token and suggested that there may be punctuation missing</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=411" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=411</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-05-07 14:25:33
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>SPARQL/XML from Sesame Workbench contains an extra attribute</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Priority changed from "Normal" to "Low"
</li>
<li>Status changed from "Unknown" to "Confirmed"
</li>
<li>Milestone changed from "Unassigned" to "1.0.5"
</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=410" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=410</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
48 messages has been excluded from this view by a project administrator.
