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-03-17 16:30:16
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for latest W3C drafts for TriG</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>Milestone changed from "Unscheduled" 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=354" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=354</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-03-17 16:30:08
|
<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 custom parameters for SparqlRemoteEndpoint and SparqlRemoteUpdateEndpoint</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>Milestone changed from "Unscheduled" to "1.0.5"
</li>
<li>Assigned to changed from "Unassigned" to "none"
</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=396" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=396</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Rob V. <rv...@do...> - 2014-03-14 11:52:26
|
Hi All We're pleased to announce the release of dotNetRDF 1.0.4 (http://www.dotnetrdf.org/blogitem.asp?blogID=80). This is a minor feature and bug fix release which adds support for RDF 1.1 NTriples and NQuads and fixes various reported bugs. Thanks as always to everyone who reported bugs/provided patches and helped produce this release. Cheers, Rob |
|
From: <tr...@do...> - 2014-03-07 17:03:29
|
<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>TriG Parser throws NPE for literals in collection</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-03-07 05:02 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=403" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=403</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-03-07 16:31:30
|
<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>TriG Parser throws NPE for literals in collection</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=403" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=403</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Rob V. <rv...@do...> - 2014-03-07 16:24:47
|
It was a bug pertaining to support for literals in collections, this is logged as CORE-403 (http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=403) and I'm working on the fix for it which should be fairly trivial Rob On 28/02/2014 16:21, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >To be clear I do mean rdf:List and not object lists. This works in >Turtle naturally: > >@prefix : <http://example/> . >:resource :predicate1 ( "a" "b" "c" ). >:resource :predicate2 ( :a :b :c ). > >But add a graph to make it TriG and the parser throws a >NullReferenceException. Checked only in rdfEditor currently. > >@prefix : <http://example/> . >:graph >{ > :resource :predicate1 ( "a" "b" "c" ). > :resource :predicate2 ( :a :b :c ). >} > >Or is this syntax not defined in the spec? > >Thanks, >Tom > >On Fri, Feb 28, 2014 at 5:05 PM, Rob Vesse <rv...@do...> wrote: >> Do you mean they aren't being permitted nested inside something else? >> >> That sounds like a possible bug, please file an issue or send me an >> example that fails >> >> Rob >> >> On 28/02/2014 11:00, "Tomasz Pluskiewicz" <tom...@gm...> >> wrote: >> >>>I see. The problem is with RDF lists. When in shortcut syntax they are >>>not recognized. >>> >>>Thanks, >>>Tom >>> >>>On Fri, Feb 28, 2014 at 11:42 AM, Rob Vesse <rv...@do...> >>>wrote: >>>> Tom >>>> >>>> We also don't yet support the latest TriG specification so the bug may >>>>be >>>> down to using a syntax feature that we don't support yet. >>>> >>>> Rob >>>> >>>> On 28/02/2014 10:26, "Tomasz Pluskiewicz" >>>><tom...@gm...> >>>> wrote: >>>> >>>>>Good news. Thanks! >>>>> >>>>>And this reminds me. We have found a bug in the TriG parser. Will >>>>>write an email to the other list. >>>>> >>>>>Tom >>>>> >>>>>On Fri, Feb 28, 2014 at 11:08 AM, Rob Vesse <rv...@do...> >>>>>wrote: >>>>>> Tom >>>>>> >>>>>> I have parsing support working on trunk with the NTriples and NQuads >>>>>> parsers defaulting to the new spec so they'll read the data in as >>>>>>UTF-8 >>>>>> rather than as ASCII. We're passing all the official RDF 1.1 tests >>>>>>for >>>>>> NTriples and NQuads but I can't guarantee there aren't any bugs >>>>>>introduced >>>>>> though the changes to support the new spec turned out to be >>>>>>relatively >>>>>> minor. >>>>>> >>>>>> The parser changes have been merged onto default and I'm continuing >>>>>>to >>>>>> work on the ntuples11 branch for the remainder of the implementation >>>>>>work. >>>>>> There's no output support for these formats yet but hopefully I'll >>>>>>get >>>>>> that done later today. >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Rob >>>>>> >>>>>> On 25/02/2014 10:22, "Rob Vesse" <rv...@do...> wrote: >>>>>> >>>>>>>Tom >>>>>>> >>>>>>>Yes the original NTriples and NQuads specifications only allow >>>>>>>ASCII, >>>>>>>this >>>>>>>was by design to make those formats canonical (since with UTF-8 you >>>>>>>can >>>>>>>potentially encode complex characters in multiple ways) and >>>>>>>facilitate >>>>>>>reliable data exchange across systems that didn't necessarily >>>>>>>support >>>>>>>non-ASCII data. >>>>>>> >>>>>>>Btw the reader only enforces ASCII encoding if you pass a filename >>>>>>>(I.e. >>>>>>>when it deals with opening the file stream), if you pass in a >>>>>>>pre-opened >>>>>>>StreamReader that is in a different encoding (I.e. UTF-8) it may >>>>>>>still >>>>>>>parse successfully though exact behaviour is hard to know in >>>>>>>advance. >>>>>>>It >>>>>>>will issue a warning about incorrect encoding (via the Warning >>>>>>>event) >>>>>>>and >>>>>>>it may error out on some native UTF-8 data since the tokeniser is >>>>>>>not >>>>>>>written to expect native UTF-8. >>>>>>> >>>>>>>The RDF 1.1 working group have published proposed recommendations >>>>>>>which >>>>>>>standardise NQuads & NTriples and part of the standardization is to >>>>>>>change >>>>>>>the encoding to UTF-8 but I haven't had chance to update dotNetRDF >>>>>>>to >>>>>>>support the updated specs yet. >>>>>>> >>>>>>>Since this is a breaking change to spec and current API behaviour >>>>>>>the >>>>>>>existing tokenizers and parsers would need to be modified so that >>>>>>>they >>>>>>>can >>>>>>>support either the new/old specification. An approach similar to >>>>>>>how >>>>>>>we >>>>>>>updated Turtle support where we implement the new specifications and >>>>>>>the >>>>>>>parsers default to the new spec mode and the writers implement the >>>>>>>new >>>>>>>spec but default to producing the old spec as output would be ideal. >>>>>>>This >>>>>>>is Postel's law in action if you're wondering why this is done. >>>>>>> >>>>>>>There are issues filed for these upgrades but I haven't had time to >>>>>>>implement them yet, I was considering trying to get these into the >>>>>>>next >>>>>>>release anyway and I have some time to start on this at the end of >>>>>>>the >>>>>>>week unless you want to attempt this yourself. See CORE-356 >>>>>>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356) for >>>>>>>NQuads >>>>>>>and CORE-355 >>>>>>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355) >>>>>>>for NTriples which include links to the updated specifications, see >>>>>>>the >>>>>>>comments for the most up to date spec links. >>>>>>> >>>>>>>Hope this clarifies things, >>>>>>> >>>>>>>Cheers, >>>>>>> >>>>>>>Rob >>>>>>> >>>>>>>On 25/02/2014 10:06, "Tomasz Pluskiewicz" >>>>>>><tom...@gm...> >>>>>>>wrote: >>>>>>> >>>>>>>>Hi Rob >>>>>>>> >>>>>>>>A colleague of mine has just discovered that the NQuadsParser reads >>>>>>>>file with ASCII encoding while all other use UTF-8. >>>>>>>> >>>>>>>>I understand that this is as described in the specification but why >>>>>>>>is >>>>>>>>that exactly? >>>>>>>> >>>>>>>>And what do you think about adding a option to the parsers so that >>>>>>>>alternative encodings can be used for reading dataset files? >>>>>>>> >>>>>>>>Cheers, >>>>>>>>Tom >>>>>>>> >>>>>>>>------------------------------------------------------------------- >>>>>>>>-- >>>>>>>>-- >>>>>>>>-- >>>>>>>>- >>>>>>>>---- >>>>>>>>Flow-based real-time traffic analytics software. Cisco certified >>>>>>>>tool. >>>>>>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow >>>>>>>>Analyzer >>>>>>>>Customize your own dashboards, set traffic alerts and generate >>>>>>>>reports. >>>>>>>>Network behavioral analysis & security monitoring. All-in-one tool. >>>>>>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/os >>>>>>>>tg >>>>>>>>.c >>>>>>>>lk >>>>>>>>t >>>>>>>>rk >>>>>>>>_______________________________________________ >>>>>>>>dotNetRDF-develop mailing list >>>>>>>>dot...@li... >>>>>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>-------------------------------------------------------------------- >>>>>>>-- >>>>>>>-- >>>>>>>-- >>>>>>>---- >>>>>>>Flow-based real-time traffic analytics software. Cisco certified >>>>>>>tool. >>>>>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow >>>>>>>Analyzer >>>>>>>Customize your own dashboards, set traffic alerts and generate >>>>>>>reports. >>>>>>>Network behavioral analysis & security monitoring. All-in-one tool. >>>>>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ost >>>>>>>g. >>>>>>>cl >>>>>>>kt >>>>>>>rk >>>>>>>_______________________________________________ >>>>>>>dotNetRDF-develop mailing list >>>>>>>dot...@li... >>>>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>--------------------------------------------------------------------- >>>>>>-- >>>>>>-- >>>>>>----- >>>>>> Flow-based real-time traffic analytics software. Cisco certified >>>>>>tool. >>>>>> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow >>>>>>Analyzer >>>>>> Customize your own dashboards, set traffic alerts and generate >>>>>>reports. >>>>>> Network behavioral analysis & security monitoring. All-in-one tool. >>>>>> >>>>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg >>>>>>.c >>>>>>lk >>>>>>trk >>>>>> _______________________________________________ >>>>>> dotNetRDF-develop mailing list >>>>>> dot...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>>> >>>>>---------------------------------------------------------------------- >>>>>-- >>>>>-- >>>>>---- >>>>>Flow-based real-time traffic analytics software. Cisco certified tool. >>>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>>>Customize your own dashboards, set traffic alerts and generate >>>>>reports. >>>>>Network behavioral analysis & security monitoring. All-in-one tool. >>>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg. >>>>>cl >>>>>kt >>>>>rk >>>>>_______________________________________________ >>>>>dotNetRDF-develop mailing list >>>>>dot...@li... >>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>>> >>>> >>>> >>>> >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>>----- >>>> Flow-based real-time traffic analytics software. Cisco certified tool. >>>> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>> Customize your own dashboards, set traffic alerts and generate >>>>reports. >>>> Network behavioral analysis & security monitoring. All-in-one tool. >>>> >>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.c >>>>lk >>>>trk >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>Flow-based real-time traffic analytics software. Cisco certified tool. >>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>Customize your own dashboards, set traffic alerts and generate reports. >>>Network behavioral analysis & security monitoring. All-in-one tool. >>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.cl >>>kt >>>rk >>>_______________________________________________ >>>dotNetRDF-develop mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Flow-based real-time traffic analytics software. Cisco certified tool. >> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >> Customize your own dashboards, set traffic alerts and generate reports. >> Network behavioral analysis & security monitoring. All-in-one tool. >> >>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clk >>trk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >-------------------------------------------------------------------------- >---- >Flow-based real-time traffic analytics software. Cisco certified tool. >Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >Customize your own dashboards, set traffic alerts and generate reports. >Network behavioral analysis & security monitoring. All-in-one tool. >http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clkt >rk >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: <tr...@do...> - 2014-03-07 16:19:33
|
<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>TriG Parser throws NPE for literals in collection</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-03-07 04:18 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Testing shows that it also does not like blank nodes with explicit names in collections which should also be permitted</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=403" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=403</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-03-07 16:12:58
|
<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>TriG Parser throws NPE for literals in collection</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.4</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Parsing</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>
As reported by Tom on the mailing list the TriG parser can throw a NPE when presented with a collection containing literals</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=403" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=403</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-03-07 16:11:19
|
<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>Formatting of SPARQL Queries containing UNION can result in invalid SPARQL syntax</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=402" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=402</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-03-07 15:29:07
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Formatting of SPARQL Queries containing UNION can result in invalid SPARQL syntax</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.4</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Query</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>
As reported on the mailing list at <a href="http://sourceforge.net/p/dotnetrdf/mailman/message/32041633/">http://sourceforge.net/p/dotnetrdf/mailman/message/32041633/</a> there is a bug in formatting some queries that contain UNION resulting in invalid SPARQL syntax being generated. This is particularly relevant for code that parses the SPARQL query for correctness before re-serializing it and passing in onto a remote system</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=402" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=402</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Tomasz P. <tom...@gm...> - 2014-02-28 16:22:39
|
To be clear I do mean rdf:List and not object lists. This works in
Turtle naturally:
@prefix : <http://example/> .
:resource :predicate1 ( "a" "b" "c" ).
:resource :predicate2 ( :a :b :c ).
But add a graph to make it TriG and the parser throws a
NullReferenceException. Checked only in rdfEditor currently.
@prefix : <http://example/> .
:graph
{
:resource :predicate1 ( "a" "b" "c" ).
:resource :predicate2 ( :a :b :c ).
}
Or is this syntax not defined in the spec?
Thanks,
Tom
On Fri, Feb 28, 2014 at 5:05 PM, Rob Vesse <rv...@do...> wrote:
> Do you mean they aren't being permitted nested inside something else?
>
> That sounds like a possible bug, please file an issue or send me an
> example that fails
>
> Rob
>
> On 28/02/2014 11:00, "Tomasz Pluskiewicz" <tom...@gm...>
> wrote:
>
>>I see. The problem is with RDF lists. When in shortcut syntax they are
>>not recognized.
>>
>>Thanks,
>>Tom
>>
>>On Fri, Feb 28, 2014 at 11:42 AM, Rob Vesse <rv...@do...> wrote:
>>> Tom
>>>
>>> We also don't yet support the latest TriG specification so the bug may
>>>be
>>> down to using a syntax feature that we don't support yet.
>>>
>>> Rob
>>>
>>> On 28/02/2014 10:26, "Tomasz Pluskiewicz" <tom...@gm...>
>>> wrote:
>>>
>>>>Good news. Thanks!
>>>>
>>>>And this reminds me. We have found a bug in the TriG parser. Will
>>>>write an email to the other list.
>>>>
>>>>Tom
>>>>
>>>>On Fri, Feb 28, 2014 at 11:08 AM, Rob Vesse <rv...@do...>
>>>>wrote:
>>>>> Tom
>>>>>
>>>>> I have parsing support working on trunk with the NTriples and NQuads
>>>>> parsers defaulting to the new spec so they'll read the data in as
>>>>>UTF-8
>>>>> rather than as ASCII. We're passing all the official RDF 1.1 tests
>>>>>for
>>>>> NTriples and NQuads but I can't guarantee there aren't any bugs
>>>>>introduced
>>>>> though the changes to support the new spec turned out to be relatively
>>>>> minor.
>>>>>
>>>>> The parser changes have been merged onto default and I'm continuing to
>>>>> work on the ntuples11 branch for the remainder of the implementation
>>>>>work.
>>>>> There's no output support for these formats yet but hopefully I'll
>>>>>get
>>>>> that done later today.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Rob
>>>>>
>>>>> On 25/02/2014 10:22, "Rob Vesse" <rv...@do...> wrote:
>>>>>
>>>>>>Tom
>>>>>>
>>>>>>Yes the original NTriples and NQuads specifications only allow ASCII,
>>>>>>this
>>>>>>was by design to make those formats canonical (since with UTF-8 you
>>>>>>can
>>>>>>potentially encode complex characters in multiple ways) and facilitate
>>>>>>reliable data exchange across systems that didn't necessarily support
>>>>>>non-ASCII data.
>>>>>>
>>>>>>Btw the reader only enforces ASCII encoding if you pass a filename
>>>>>>(I.e.
>>>>>>when it deals with opening the file stream), if you pass in a
>>>>>>pre-opened
>>>>>>StreamReader that is in a different encoding (I.e. UTF-8) it may still
>>>>>>parse successfully though exact behaviour is hard to know in advance.
>>>>>>It
>>>>>>will issue a warning about incorrect encoding (via the Warning event)
>>>>>>and
>>>>>>it may error out on some native UTF-8 data since the tokeniser is not
>>>>>>written to expect native UTF-8.
>>>>>>
>>>>>>The RDF 1.1 working group have published proposed recommendations
>>>>>>which
>>>>>>standardise NQuads & NTriples and part of the standardization is to
>>>>>>change
>>>>>>the encoding to UTF-8 but I haven't had chance to update dotNetRDF to
>>>>>>support the updated specs yet.
>>>>>>
>>>>>>Since this is a breaking change to spec and current API behaviour the
>>>>>>existing tokenizers and parsers would need to be modified so that they
>>>>>>can
>>>>>>support either the new/old specification. An approach similar to how
>>>>>>we
>>>>>>updated Turtle support where we implement the new specifications and
>>>>>>the
>>>>>>parsers default to the new spec mode and the writers implement the
>>>>>>new
>>>>>>spec but default to producing the old spec as output would be ideal.
>>>>>>This
>>>>>>is Postel's law in action if you're wondering why this is done.
>>>>>>
>>>>>>There are issues filed for these upgrades but I haven't had time to
>>>>>>implement them yet, I was considering trying to get these into the
>>>>>>next
>>>>>>release anyway and I have some time to start on this at the end of the
>>>>>>week unless you want to attempt this yourself. See CORE-356
>>>>>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356) for
>>>>>>NQuads
>>>>>>and CORE-355
>>>>>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355)
>>>>>>for NTriples which include links to the updated specifications, see
>>>>>>the
>>>>>>comments for the most up to date spec links.
>>>>>>
>>>>>>Hope this clarifies things,
>>>>>>
>>>>>>Cheers,
>>>>>>
>>>>>>Rob
>>>>>>
>>>>>>On 25/02/2014 10:06, "Tomasz Pluskiewicz"
>>>>>><tom...@gm...>
>>>>>>wrote:
>>>>>>
>>>>>>>Hi Rob
>>>>>>>
>>>>>>>A colleague of mine has just discovered that the NQuadsParser reads
>>>>>>>file with ASCII encoding while all other use UTF-8.
>>>>>>>
>>>>>>>I understand that this is as described in the specification but why
>>>>>>>is
>>>>>>>that exactly?
>>>>>>>
>>>>>>>And what do you think about adding a option to the parsers so that
>>>>>>>alternative encodings can be used for reading dataset files?
>>>>>>>
>>>>>>>Cheers,
>>>>>>>Tom
>>>>>>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>--
>>>>>>>--
>>>>>>>-
>>>>>>>----
>>>>>>>Flow-based real-time traffic analytics software. Cisco certified
>>>>>>>tool.
>>>>>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
>>>>>>>Customize your own dashboards, set traffic alerts and generate
>>>>>>>reports.
>>>>>>>Network behavioral analysis & security monitoring. All-in-one tool.
>>>>>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg
>>>>>>>.c
>>>>>>>lk
>>>>>>>t
>>>>>>>rk
>>>>>>>_______________________________________________
>>>>>>>dotNetRDF-develop mailing list
>>>>>>>dot...@li...
>>>>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>----------------------------------------------------------------------
>>>>>>--
>>>>>>--
>>>>>>----
>>>>>>Flow-based real-time traffic analytics software. Cisco certified tool.
>>>>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
>>>>>>Customize your own dashboards, set traffic alerts and generate
>>>>>>reports.
>>>>>>Network behavioral analysis & security monitoring. All-in-one tool.
>>>>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.
>>>>>>cl
>>>>>>kt
>>>>>>rk
>>>>>>_______________________________________________
>>>>>>dotNetRDF-develop mailing list
>>>>>>dot...@li...
>>>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>-----------------------------------------------------------------------
>>>>>--
>>>>>-----
>>>>> Flow-based real-time traffic analytics software. Cisco certified tool.
>>>>> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
>>>>> Customize your own dashboards, set traffic alerts and generate
>>>>>reports.
>>>>> Network behavioral analysis & security monitoring. All-in-one tool.
>>>>>
>>>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.c
>>>>>lk
>>>>>trk
>>>>> _______________________________________________
>>>>> dotNetRDF-develop mailing list
>>>>> dot...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>>>
>>>>------------------------------------------------------------------------
>>>>--
>>>>----
>>>>Flow-based real-time traffic analytics software. Cisco certified tool.
>>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
>>>>Customize your own dashboards, set traffic alerts and generate reports.
>>>>Network behavioral analysis & security monitoring. All-in-one tool.
>>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.cl
>>>>kt
>>>>rk
>>>>_______________________________________________
>>>>dotNetRDF-develop mailing list
>>>>dot...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>>
>>>
>>>
>>>
>>>
>>>
>>>-------------------------------------------------------------------------
>>>-----
>>> Flow-based real-time traffic analytics software. Cisco certified tool.
>>> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
>>> Customize your own dashboards, set traffic alerts and generate reports.
>>> Network behavioral analysis & security monitoring. All-in-one tool.
>>>
>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clk
>>>trk
>>> _______________________________________________
>>> dotNetRDF-develop mailing list
>>> dot...@li...
>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>
>>--------------------------------------------------------------------------
>>----
>>Flow-based real-time traffic analytics software. Cisco certified tool.
>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
>>Customize your own dashboards, set traffic alerts and generate reports.
>>Network behavioral analysis & security monitoring. All-in-one tool.
>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clkt
>>rk
>>_______________________________________________
>>dotNetRDF-develop mailing list
>>dot...@li...
>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
>
>
>
>
> ------------------------------------------------------------------------------
> Flow-based real-time traffic analytics software. Cisco certified tool.
> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
> Customize your own dashboards, set traffic alerts and generate reports.
> Network behavioral analysis & security monitoring. All-in-one tool.
> http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
|
|
From: <tr...@do...> - 2014-02-28 16:13:19
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for new variant of NQuads</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 "Completed"
</li>
<li>Progress changed from "80 %" 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=356" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Rob V. <rv...@do...> - 2014-02-28 16:08:22
|
Tom Writing support is now also available in default Rob On 28/02/2014 10:26, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Good news. Thanks! > >And this reminds me. We have found a bug in the TriG parser. Will >write an email to the other list. > >Tom > >On Fri, Feb 28, 2014 at 11:08 AM, Rob Vesse <rv...@do...> wrote: >> Tom >> >> I have parsing support working on trunk with the NTriples and NQuads >> parsers defaulting to the new spec so they'll read the data in as UTF-8 >> rather than as ASCII. We're passing all the official RDF 1.1 tests for >> NTriples and NQuads but I can't guarantee there aren't any bugs >>introduced >> though the changes to support the new spec turned out to be relatively >> minor. >> >> The parser changes have been merged onto default and I'm continuing to >> work on the ntuples11 branch for the remainder of the implementation >>work. >> There's no output support for these formats yet but hopefully I'll get >> that done later today. >> >> Cheers, >> >> Rob >> >> On 25/02/2014 10:22, "Rob Vesse" <rv...@do...> wrote: >> >>>Tom >>> >>>Yes the original NTriples and NQuads specifications only allow ASCII, >>>this >>>was by design to make those formats canonical (since with UTF-8 you can >>>potentially encode complex characters in multiple ways) and facilitate >>>reliable data exchange across systems that didn't necessarily support >>>non-ASCII data. >>> >>>Btw the reader only enforces ASCII encoding if you pass a filename (I.e. >>>when it deals with opening the file stream), if you pass in a pre-opened >>>StreamReader that is in a different encoding (I.e. UTF-8) it may still >>>parse successfully though exact behaviour is hard to know in advance. >>>It >>>will issue a warning about incorrect encoding (via the Warning event) >>>and >>>it may error out on some native UTF-8 data since the tokeniser is not >>>written to expect native UTF-8. >>> >>>The RDF 1.1 working group have published proposed recommendations which >>>standardise NQuads & NTriples and part of the standardization is to >>>change >>>the encoding to UTF-8 but I haven't had chance to update dotNetRDF to >>>support the updated specs yet. >>> >>>Since this is a breaking change to spec and current API behaviour the >>>existing tokenizers and parsers would need to be modified so that they >>>can >>>support either the new/old specification. An approach similar to how we >>>updated Turtle support where we implement the new specifications and the >>>parsers default to the new spec mode and the writers implement the new >>>spec but default to producing the old spec as output would be ideal. >>>This >>>is Postel's law in action if you're wondering why this is done. >>> >>>There are issues filed for these upgrades but I haven't had time to >>>implement them yet, I was considering trying to get these into the next >>>release anyway and I have some time to start on this at the end of the >>>week unless you want to attempt this yourself. See CORE-356 >>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356) for NQuads >>>and CORE-355 >>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355) >>>for NTriples which include links to the updated specifications, see the >>>comments for the most up to date spec links. >>> >>>Hope this clarifies things, >>> >>>Cheers, >>> >>>Rob >>> >>>On 25/02/2014 10:06, "Tomasz Pluskiewicz" <tom...@gm...> >>>wrote: >>> >>>>Hi Rob >>>> >>>>A colleague of mine has just discovered that the NQuadsParser reads >>>>file with ASCII encoding while all other use UTF-8. >>>> >>>>I understand that this is as described in the specification but why is >>>>that exactly? >>>> >>>>And what do you think about adding a option to the parsers so that >>>>alternative encodings can be used for reading dataset files? >>>> >>>>Cheers, >>>>Tom >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>>- >>>>---- >>>>Flow-based real-time traffic analytics software. Cisco certified tool. >>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>>Customize your own dashboards, set traffic alerts and generate reports. >>>>Network behavioral analysis & security monitoring. All-in-one tool. >>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.c >>>>lk >>>>t >>>>rk >>>>_______________________________________________ >>>>dotNetRDF-develop mailing list >>>>dot...@li... >>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>> >>> >>> >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>Flow-based real-time traffic analytics software. Cisco certified tool. >>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>Customize your own dashboards, set traffic alerts and generate reports. >>>Network behavioral analysis & security monitoring. All-in-one tool. >>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.cl >>>kt >>>rk >>>_______________________________________________ >>>dotNetRDF-develop mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Flow-based real-time traffic analytics software. Cisco certified tool. >> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >> Customize your own dashboards, set traffic alerts and generate reports. >> Network behavioral analysis & security monitoring. All-in-one tool. >> >>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clk >>trk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >-------------------------------------------------------------------------- >-- >-- >Flow-based real-time traffic analytics software. Cisco certified tool. >Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >Customize your own dashboards, set traffic alerts and generate reports. >Network behavioral analysis & security monitoring. All-in-one tool. >http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clkt >rk >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Rob V. <rv...@do...> - 2014-02-28 16:06:59
|
Do you mean they aren't being permitted nested inside something else? That sounds like a possible bug, please file an issue or send me an example that fails Rob On 28/02/2014 11:00, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >I see. The problem is with RDF lists. When in shortcut syntax they are >not recognized. > >Thanks, >Tom > >On Fri, Feb 28, 2014 at 11:42 AM, Rob Vesse <rv...@do...> wrote: >> Tom >> >> We also don't yet support the latest TriG specification so the bug may >>be >> down to using a syntax feature that we don't support yet. >> >> Rob >> >> On 28/02/2014 10:26, "Tomasz Pluskiewicz" <tom...@gm...> >> wrote: >> >>>Good news. Thanks! >>> >>>And this reminds me. We have found a bug in the TriG parser. Will >>>write an email to the other list. >>> >>>Tom >>> >>>On Fri, Feb 28, 2014 at 11:08 AM, Rob Vesse <rv...@do...> >>>wrote: >>>> Tom >>>> >>>> I have parsing support working on trunk with the NTriples and NQuads >>>> parsers defaulting to the new spec so they'll read the data in as >>>>UTF-8 >>>> rather than as ASCII. We're passing all the official RDF 1.1 tests >>>>for >>>> NTriples and NQuads but I can't guarantee there aren't any bugs >>>>introduced >>>> though the changes to support the new spec turned out to be relatively >>>> minor. >>>> >>>> The parser changes have been merged onto default and I'm continuing to >>>> work on the ntuples11 branch for the remainder of the implementation >>>>work. >>>> There's no output support for these formats yet but hopefully I'll >>>>get >>>> that done later today. >>>> >>>> Cheers, >>>> >>>> Rob >>>> >>>> On 25/02/2014 10:22, "Rob Vesse" <rv...@do...> wrote: >>>> >>>>>Tom >>>>> >>>>>Yes the original NTriples and NQuads specifications only allow ASCII, >>>>>this >>>>>was by design to make those formats canonical (since with UTF-8 you >>>>>can >>>>>potentially encode complex characters in multiple ways) and facilitate >>>>>reliable data exchange across systems that didn't necessarily support >>>>>non-ASCII data. >>>>> >>>>>Btw the reader only enforces ASCII encoding if you pass a filename >>>>>(I.e. >>>>>when it deals with opening the file stream), if you pass in a >>>>>pre-opened >>>>>StreamReader that is in a different encoding (I.e. UTF-8) it may still >>>>>parse successfully though exact behaviour is hard to know in advance. >>>>>It >>>>>will issue a warning about incorrect encoding (via the Warning event) >>>>>and >>>>>it may error out on some native UTF-8 data since the tokeniser is not >>>>>written to expect native UTF-8. >>>>> >>>>>The RDF 1.1 working group have published proposed recommendations >>>>>which >>>>>standardise NQuads & NTriples and part of the standardization is to >>>>>change >>>>>the encoding to UTF-8 but I haven't had chance to update dotNetRDF to >>>>>support the updated specs yet. >>>>> >>>>>Since this is a breaking change to spec and current API behaviour the >>>>>existing tokenizers and parsers would need to be modified so that they >>>>>can >>>>>support either the new/old specification. An approach similar to how >>>>>we >>>>>updated Turtle support where we implement the new specifications and >>>>>the >>>>>parsers default to the new spec mode and the writers implement the >>>>>new >>>>>spec but default to producing the old spec as output would be ideal. >>>>>This >>>>>is Postel's law in action if you're wondering why this is done. >>>>> >>>>>There are issues filed for these upgrades but I haven't had time to >>>>>implement them yet, I was considering trying to get these into the >>>>>next >>>>>release anyway and I have some time to start on this at the end of the >>>>>week unless you want to attempt this yourself. See CORE-356 >>>>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356) for >>>>>NQuads >>>>>and CORE-355 >>>>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355) >>>>>for NTriples which include links to the updated specifications, see >>>>>the >>>>>comments for the most up to date spec links. >>>>> >>>>>Hope this clarifies things, >>>>> >>>>>Cheers, >>>>> >>>>>Rob >>>>> >>>>>On 25/02/2014 10:06, "Tomasz Pluskiewicz" >>>>><tom...@gm...> >>>>>wrote: >>>>> >>>>>>Hi Rob >>>>>> >>>>>>A colleague of mine has just discovered that the NQuadsParser reads >>>>>>file with ASCII encoding while all other use UTF-8. >>>>>> >>>>>>I understand that this is as described in the specification but why >>>>>>is >>>>>>that exactly? >>>>>> >>>>>>And what do you think about adding a option to the parsers so that >>>>>>alternative encodings can be used for reading dataset files? >>>>>> >>>>>>Cheers, >>>>>>Tom >>>>>> >>>>>>--------------------------------------------------------------------- >>>>>>-- >>>>>>-- >>>>>>- >>>>>>---- >>>>>>Flow-based real-time traffic analytics software. Cisco certified >>>>>>tool. >>>>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>>>>Customize your own dashboards, set traffic alerts and generate >>>>>>reports. >>>>>>Network behavioral analysis & security monitoring. All-in-one tool. >>>>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg >>>>>>.c >>>>>>lk >>>>>>t >>>>>>rk >>>>>>_______________________________________________ >>>>>>dotNetRDF-develop mailing list >>>>>>dot...@li... >>>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>---------------------------------------------------------------------- >>>>>-- >>>>>-- >>>>>---- >>>>>Flow-based real-time traffic analytics software. Cisco certified tool. >>>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>>>Customize your own dashboards, set traffic alerts and generate >>>>>reports. >>>>>Network behavioral analysis & security monitoring. All-in-one tool. >>>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg. >>>>>cl >>>>>kt >>>>>rk >>>>>_______________________________________________ >>>>>dotNetRDF-develop mailing list >>>>>dot...@li... >>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>>> >>>> >>>> >>>> >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>>----- >>>> Flow-based real-time traffic analytics software. Cisco certified tool. >>>> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>> Customize your own dashboards, set traffic alerts and generate >>>>reports. >>>> Network behavioral analysis & security monitoring. All-in-one tool. >>>> >>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.c >>>>lk >>>>trk >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>Flow-based real-time traffic analytics software. Cisco certified tool. >>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>Customize your own dashboards, set traffic alerts and generate reports. >>>Network behavioral analysis & security monitoring. All-in-one tool. >>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.cl >>>kt >>>rk >>>_______________________________________________ >>>dotNetRDF-develop mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Flow-based real-time traffic analytics software. Cisco certified tool. >> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >> Customize your own dashboards, set traffic alerts and generate reports. >> Network behavioral analysis & security monitoring. All-in-one tool. >> >>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clk >>trk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >-------------------------------------------------------------------------- >---- >Flow-based real-time traffic analytics software. Cisco certified tool. >Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >Customize your own dashboards, set traffic alerts and generate reports. >Network behavioral analysis & security monitoring. All-in-one tool. >http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clkt >rk >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: <tr...@do...> - 2014-02-28 15:41: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>Add support for new variant of NTriples</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 "Completed"
</li>
<li>Progress changed from "95 %" 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=355" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355</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-02-28 12:47:44
|
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: Note RDF 1.1 NQuads support in Change Log (CORE-356) (Bitbucket) 2. commit/dotnetrdf: rvesse: Merge parsing support for RDF 1.1 NTriples and NQuads (CORE-355, CORE-356) (Bitbucket) 3. commit/dotnetrdf: 3 new changesets (Bitbucket) 4. commit/dotnetrdf: 4 new changesets (Bitbucket) 5. commit/dotnetrdf: 3 new changesets (Bitbucket) 6. commit/dotnetrdf: 2 new changesets (Bitbucket) 7. commit/dotnetrdf: rvesse: Merge latest RDF 1.1 NTuples and NQuads support onto default (CORE-355, CORE-356) (Bitbucket) 8. commit/dotnetrdf: rvesse: Ignore risky test (Bitbucket) 9. commit/dotnetrdf: rvesse: Merge latest (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Thu, 27 Feb 2014 16:35:38 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Note RDF 1.1 NQuads support in Change Log (CORE-356) 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/a7ab36f9426a/ Changeset: a7ab36f9426a Branch: ntuples11 User: rvesse Date: 2014-02-27 17:35:17 Summary: Note RDF 1.1 NQuads support in Change Log (CORE-356) 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: Thu, 27 Feb 2014 16:46:58 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Merge parsing support for RDF 1.1 NTriples and NQuads (CORE-355, CORE-356) 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/e5f48626c0d4/ Changeset: e5f48626c0d4 User: rvesse Date: 2014-02-27 17:46:34 Summary: Merge parsing support for RDF 1.1 NTriples and NQuads (CORE-355, CORE-356) Affected #: 176 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, 28 Feb 2014 11:09:31 -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/82e5aeb4e3ff/ Changeset: 82e5aeb4e3ff Branch: ntuples11 User: rvesse Date: 2014-02-28 11:43:28 Summary: Some fixes to NTriples tokenizer to correctly handle Blank Node IDs in the different NTriple syntaxes (CORE-355, CORE-356) Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/71b88484bfd3/ Changeset: 71b88484bfd3 Branch: ntuples11 User: rvesse Date: 2014-02-28 11:59:31 Summary: Some fixes to NTriples tokenizer literal handling to accept RDF 1.1 escapes (CORE-355, CORE-356) Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b31e863b389c/ Changeset: b31e863b389c Branch: ntuples11 User: rvesse Date: 2014-02-28 12:09:05 Summary: Some fixes to Turtle tokenizer literal handling to correctly support RDF 1.1 escapes, also some fixes for cross-platform builds related to NTriples and NQuads changes (CORE-355, CORE-356) 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: Fri, 28 Feb 2014 11:49:45 -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/3b38658a1140/ Changeset: 3b38658a1140 Branch: ntuples11 User: rvesse Date: 2014-02-28 12:19:21 Summary: Update sanity checking script to force a compile to check for cross platform build breaks and add appropriate dependencies to ensure ToolkitInstaller doesn't build too soon (TOOLS-360) Affected #: 12 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c09af802f4b2/ Changeset: c09af802f4b2 Branch: ntuples11 User: rvesse Date: 2014-02-28 12:22:29 Summary: Further improve sanity checking script to abort commit if code does not compile Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f123b7096a56/ Changeset: f123b7096a56 User: rvesse Date: 2014-02-28 12:24:36 Summary: Merge latest RDF 1.1 NTriples and NQuads support to default (CORE-355, CORE-356) Affected #: 21 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/cd0258707438/ Changeset: cd0258707438 Branch: ntuples11 User: rvesse Date: 2014-02-28 12:49:23 Summary: Fix broken StoreCountHandler tests and underyling bug in StoreCountHandler exposed by RDF 1.1 NQuads changes (CORE-356) 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: Fri, 28 Feb 2014 12:20:45 -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/cce6e759a99f/ Changeset: cce6e759a99f Branch: ntuples11 User: rvesse Date: 2014-02-28 13:11:18 Summary: Bunch of unit tests covering new NTriples 1.1 writing support, some of these currently fail (CORE-355) Affected #: 6 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c1905ad27f36/ Changeset: c1905ad27f36 Branch: ntuples11 User: rvesse Date: 2014-02-28 13:17:16 Summary: Fixes to NTriplesTokeniser to make it reject non-ASCII characters when using Original syntx (CORE-355, CORE-356) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b3c24157882b/ Changeset: b3c24157882b Branch: ntuples11 User: rvesse Date: 2014-02-28 13:20:21 Summary: More unit tests for NTriples 1.1 writing support (CORE-355) 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, 28 Feb 2014 12:30:03 -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/ae11ebfca7d2/ Changeset: ae11ebfca7d2 Branch: ntuples11 User: rvesse Date: 2014-02-28 13:28:39 Summary: Infrastructure towards supporting NQuads 1.1 output (CORE-356) Affected #: 13 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4b5f1f08ceee/ Changeset: 4b5f1f08ceee Branch: ntuples11 User: rvesse Date: 2014-02-28 13:29:35 Summary: Note RDF NTriples 1.1 and RDF NQuads 1.1 writing support in Change Log (CORE-355, CORE-356) 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: Fri, 28 Feb 2014 12:32:08 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Merge latest RDF 1.1 NTuples and NQuads support onto default (CORE-355, CORE-356) 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/d00fa6ae6b25/ Changeset: d00fa6ae6b25 User: rvesse Date: 2014-02-28 13:31:46 Summary: Merge latest RDF 1.1 NTuples and NQuads support onto default (CORE-355, CORE-356) Affected #: 27 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, 28 Feb 2014 12:45:48 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Ignore risky test 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/4f1c63e721d9/ Changeset: 4f1c63e721d9 Branch: ntuples11 User: rvesse Date: 2014-02-28 13:43:57 Summary: Ignore risky test 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: 9 Date: Fri, 28 Feb 2014 12:47:34 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Merge latest 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/53f00d59cbf7/ Changeset: 53f00d59cbf7 User: rvesse Date: 2014-02-28 13:47:12 Summary: Merge latest 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. ------------------------------ ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 16, Issue 4 ************************************************ |
|
From: <tr...@do...> - 2014-02-28 12:34:48
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for new variant of NTriples</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 "50 %" to "95 %"
</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=355" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355</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-02-28 12:34:24
|
<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>Add support for new variant of NTriples</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-02-28 12:33 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Writing support has been added with test coverage expanded to test 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=355" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355</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-02-28 12:33: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>Add support for new variant of NQuads</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-02-28 12:33 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Writing support has been added but has limited test coverage</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=356" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356</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-02-28 12:33:42
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for new variant of NQuads</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 "50 %" to "80 %"
</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=356" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Tomasz P. <tom...@gm...> - 2014-02-28 11:01:03
|
I see. The problem is with RDF lists. When in shortcut syntax they are not recognized. Thanks, Tom On Fri, Feb 28, 2014 at 11:42 AM, Rob Vesse <rv...@do...> wrote: > Tom > > We also don't yet support the latest TriG specification so the bug may be > down to using a syntax feature that we don't support yet. > > Rob > > On 28/02/2014 10:26, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>Good news. Thanks! >> >>And this reminds me. We have found a bug in the TriG parser. Will >>write an email to the other list. >> >>Tom >> >>On Fri, Feb 28, 2014 at 11:08 AM, Rob Vesse <rv...@do...> wrote: >>> Tom >>> >>> I have parsing support working on trunk with the NTriples and NQuads >>> parsers defaulting to the new spec so they'll read the data in as UTF-8 >>> rather than as ASCII. We're passing all the official RDF 1.1 tests for >>> NTriples and NQuads but I can't guarantee there aren't any bugs >>>introduced >>> though the changes to support the new spec turned out to be relatively >>> minor. >>> >>> The parser changes have been merged onto default and I'm continuing to >>> work on the ntuples11 branch for the remainder of the implementation >>>work. >>> There's no output support for these formats yet but hopefully I'll get >>> that done later today. >>> >>> Cheers, >>> >>> Rob >>> >>> On 25/02/2014 10:22, "Rob Vesse" <rv...@do...> wrote: >>> >>>>Tom >>>> >>>>Yes the original NTriples and NQuads specifications only allow ASCII, >>>>this >>>>was by design to make those formats canonical (since with UTF-8 you can >>>>potentially encode complex characters in multiple ways) and facilitate >>>>reliable data exchange across systems that didn't necessarily support >>>>non-ASCII data. >>>> >>>>Btw the reader only enforces ASCII encoding if you pass a filename (I.e. >>>>when it deals with opening the file stream), if you pass in a pre-opened >>>>StreamReader that is in a different encoding (I.e. UTF-8) it may still >>>>parse successfully though exact behaviour is hard to know in advance. >>>>It >>>>will issue a warning about incorrect encoding (via the Warning event) >>>>and >>>>it may error out on some native UTF-8 data since the tokeniser is not >>>>written to expect native UTF-8. >>>> >>>>The RDF 1.1 working group have published proposed recommendations which >>>>standardise NQuads & NTriples and part of the standardization is to >>>>change >>>>the encoding to UTF-8 but I haven't had chance to update dotNetRDF to >>>>support the updated specs yet. >>>> >>>>Since this is a breaking change to spec and current API behaviour the >>>>existing tokenizers and parsers would need to be modified so that they >>>>can >>>>support either the new/old specification. An approach similar to how we >>>>updated Turtle support where we implement the new specifications and the >>>>parsers default to the new spec mode and the writers implement the new >>>>spec but default to producing the old spec as output would be ideal. >>>>This >>>>is Postel's law in action if you're wondering why this is done. >>>> >>>>There are issues filed for these upgrades but I haven't had time to >>>>implement them yet, I was considering trying to get these into the next >>>>release anyway and I have some time to start on this at the end of the >>>>week unless you want to attempt this yourself. See CORE-356 >>>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356) for NQuads >>>>and CORE-355 >>>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355) >>>>for NTriples which include links to the updated specifications, see the >>>>comments for the most up to date spec links. >>>> >>>>Hope this clarifies things, >>>> >>>>Cheers, >>>> >>>>Rob >>>> >>>>On 25/02/2014 10:06, "Tomasz Pluskiewicz" <tom...@gm...> >>>>wrote: >>>> >>>>>Hi Rob >>>>> >>>>>A colleague of mine has just discovered that the NQuadsParser reads >>>>>file with ASCII encoding while all other use UTF-8. >>>>> >>>>>I understand that this is as described in the specification but why is >>>>>that exactly? >>>>> >>>>>And what do you think about adding a option to the parsers so that >>>>>alternative encodings can be used for reading dataset files? >>>>> >>>>>Cheers, >>>>>Tom >>>>> >>>>>----------------------------------------------------------------------- >>>>>-- >>>>>- >>>>>---- >>>>>Flow-based real-time traffic analytics software. Cisco certified tool. >>>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>>>Customize your own dashboards, set traffic alerts and generate reports. >>>>>Network behavioral analysis & security monitoring. All-in-one tool. >>>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.c >>>>>lk >>>>>t >>>>>rk >>>>>_______________________________________________ >>>>>dotNetRDF-develop mailing list >>>>>dot...@li... >>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>>> >>>> >>>> >>>> >>>>------------------------------------------------------------------------ >>>>-- >>>>---- >>>>Flow-based real-time traffic analytics software. Cisco certified tool. >>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>>Customize your own dashboards, set traffic alerts and generate reports. >>>>Network behavioral analysis & security monitoring. All-in-one tool. >>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.cl >>>>kt >>>>rk >>>>_______________________________________________ >>>>dotNetRDF-develop mailing list >>>>dot...@li... >>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>> >>> >>> >>> >>> >>>------------------------------------------------------------------------- >>>----- >>> Flow-based real-time traffic analytics software. Cisco certified tool. >>> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>> Customize your own dashboards, set traffic alerts and generate reports. >>> Network behavioral analysis & security monitoring. All-in-one tool. >>> >>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clk >>>trk >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >>-------------------------------------------------------------------------- >>---- >>Flow-based real-time traffic analytics software. Cisco certified tool. >>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>Customize your own dashboards, set traffic alerts and generate reports. >>Network behavioral analysis & security monitoring. All-in-one tool. >>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clkt >>rk >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2014-02-28 10:43:02
|
Tom We also don't yet support the latest TriG specification so the bug may be down to using a syntax feature that we don't support yet. Rob On 28/02/2014 10:26, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Good news. Thanks! > >And this reminds me. We have found a bug in the TriG parser. Will >write an email to the other list. > >Tom > >On Fri, Feb 28, 2014 at 11:08 AM, Rob Vesse <rv...@do...> wrote: >> Tom >> >> I have parsing support working on trunk with the NTriples and NQuads >> parsers defaulting to the new spec so they'll read the data in as UTF-8 >> rather than as ASCII. We're passing all the official RDF 1.1 tests for >> NTriples and NQuads but I can't guarantee there aren't any bugs >>introduced >> though the changes to support the new spec turned out to be relatively >> minor. >> >> The parser changes have been merged onto default and I'm continuing to >> work on the ntuples11 branch for the remainder of the implementation >>work. >> There's no output support for these formats yet but hopefully I'll get >> that done later today. >> >> Cheers, >> >> Rob >> >> On 25/02/2014 10:22, "Rob Vesse" <rv...@do...> wrote: >> >>>Tom >>> >>>Yes the original NTriples and NQuads specifications only allow ASCII, >>>this >>>was by design to make those formats canonical (since with UTF-8 you can >>>potentially encode complex characters in multiple ways) and facilitate >>>reliable data exchange across systems that didn't necessarily support >>>non-ASCII data. >>> >>>Btw the reader only enforces ASCII encoding if you pass a filename (I.e. >>>when it deals with opening the file stream), if you pass in a pre-opened >>>StreamReader that is in a different encoding (I.e. UTF-8) it may still >>>parse successfully though exact behaviour is hard to know in advance. >>>It >>>will issue a warning about incorrect encoding (via the Warning event) >>>and >>>it may error out on some native UTF-8 data since the tokeniser is not >>>written to expect native UTF-8. >>> >>>The RDF 1.1 working group have published proposed recommendations which >>>standardise NQuads & NTriples and part of the standardization is to >>>change >>>the encoding to UTF-8 but I haven't had chance to update dotNetRDF to >>>support the updated specs yet. >>> >>>Since this is a breaking change to spec and current API behaviour the >>>existing tokenizers and parsers would need to be modified so that they >>>can >>>support either the new/old specification. An approach similar to how we >>>updated Turtle support where we implement the new specifications and the >>>parsers default to the new spec mode and the writers implement the new >>>spec but default to producing the old spec as output would be ideal. >>>This >>>is Postel's law in action if you're wondering why this is done. >>> >>>There are issues filed for these upgrades but I haven't had time to >>>implement them yet, I was considering trying to get these into the next >>>release anyway and I have some time to start on this at the end of the >>>week unless you want to attempt this yourself. See CORE-356 >>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356) for NQuads >>>and CORE-355 >>>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355) >>>for NTriples which include links to the updated specifications, see the >>>comments for the most up to date spec links. >>> >>>Hope this clarifies things, >>> >>>Cheers, >>> >>>Rob >>> >>>On 25/02/2014 10:06, "Tomasz Pluskiewicz" <tom...@gm...> >>>wrote: >>> >>>>Hi Rob >>>> >>>>A colleague of mine has just discovered that the NQuadsParser reads >>>>file with ASCII encoding while all other use UTF-8. >>>> >>>>I understand that this is as described in the specification but why is >>>>that exactly? >>>> >>>>And what do you think about adding a option to the parsers so that >>>>alternative encodings can be used for reading dataset files? >>>> >>>>Cheers, >>>>Tom >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>>- >>>>---- >>>>Flow-based real-time traffic analytics software. Cisco certified tool. >>>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>>Customize your own dashboards, set traffic alerts and generate reports. >>>>Network behavioral analysis & security monitoring. All-in-one tool. >>>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.c >>>>lk >>>>t >>>>rk >>>>_______________________________________________ >>>>dotNetRDF-develop mailing list >>>>dot...@li... >>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>> >>> >>> >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>Flow-based real-time traffic analytics software. Cisco certified tool. >>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>Customize your own dashboards, set traffic alerts and generate reports. >>>Network behavioral analysis & security monitoring. All-in-one tool. >>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.cl >>>kt >>>rk >>>_______________________________________________ >>>dotNetRDF-develop mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Flow-based real-time traffic analytics software. Cisco certified tool. >> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >> Customize your own dashboards, set traffic alerts and generate reports. >> Network behavioral analysis & security monitoring. All-in-one tool. >> >>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clk >>trk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >-------------------------------------------------------------------------- >---- >Flow-based real-time traffic analytics software. Cisco certified tool. >Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >Customize your own dashboards, set traffic alerts and generate reports. >Network behavioral analysis & security monitoring. All-in-one tool. >http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clkt >rk >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2014-02-28 10:27:13
|
Good news. Thanks! And this reminds me. We have found a bug in the TriG parser. Will write an email to the other list. Tom On Fri, Feb 28, 2014 at 11:08 AM, Rob Vesse <rv...@do...> wrote: > Tom > > I have parsing support working on trunk with the NTriples and NQuads > parsers defaulting to the new spec so they'll read the data in as UTF-8 > rather than as ASCII. We're passing all the official RDF 1.1 tests for > NTriples and NQuads but I can't guarantee there aren't any bugs introduced > though the changes to support the new spec turned out to be relatively > minor. > > The parser changes have been merged onto default and I'm continuing to > work on the ntuples11 branch for the remainder of the implementation work. > There's no output support for these formats yet but hopefully I'll get > that done later today. > > Cheers, > > Rob > > On 25/02/2014 10:22, "Rob Vesse" <rv...@do...> wrote: > >>Tom >> >>Yes the original NTriples and NQuads specifications only allow ASCII, this >>was by design to make those formats canonical (since with UTF-8 you can >>potentially encode complex characters in multiple ways) and facilitate >>reliable data exchange across systems that didn't necessarily support >>non-ASCII data. >> >>Btw the reader only enforces ASCII encoding if you pass a filename (I.e. >>when it deals with opening the file stream), if you pass in a pre-opened >>StreamReader that is in a different encoding (I.e. UTF-8) it may still >>parse successfully though exact behaviour is hard to know in advance. It >>will issue a warning about incorrect encoding (via the Warning event) and >>it may error out on some native UTF-8 data since the tokeniser is not >>written to expect native UTF-8. >> >>The RDF 1.1 working group have published proposed recommendations which >>standardise NQuads & NTriples and part of the standardization is to change >>the encoding to UTF-8 but I haven't had chance to update dotNetRDF to >>support the updated specs yet. >> >>Since this is a breaking change to spec and current API behaviour the >>existing tokenizers and parsers would need to be modified so that they can >>support either the new/old specification. An approach similar to how we >>updated Turtle support where we implement the new specifications and the >>parsers default to the new spec mode and the writers implement the new >>spec but default to producing the old spec as output would be ideal. This >>is Postel's law in action if you're wondering why this is done. >> >>There are issues filed for these upgrades but I haven't had time to >>implement them yet, I was considering trying to get these into the next >>release anyway and I have some time to start on this at the end of the >>week unless you want to attempt this yourself. See CORE-356 >>(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356) for NQuads >>and CORE-355 (http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355) >>for NTriples which include links to the updated specifications, see the >>comments for the most up to date spec links. >> >>Hope this clarifies things, >> >>Cheers, >> >>Rob >> >>On 25/02/2014 10:06, "Tomasz Pluskiewicz" <tom...@gm...> >>wrote: >> >>>Hi Rob >>> >>>A colleague of mine has just discovered that the NQuadsParser reads >>>file with ASCII encoding while all other use UTF-8. >>> >>>I understand that this is as described in the specification but why is >>>that exactly? >>> >>>And what do you think about adding a option to the parsers so that >>>alternative encodings can be used for reading dataset files? >>> >>>Cheers, >>>Tom >>> >>>------------------------------------------------------------------------- >>>- >>>---- >>>Flow-based real-time traffic analytics software. Cisco certified tool. >>>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>>Customize your own dashboards, set traffic alerts and generate reports. >>>Network behavioral analysis & security monitoring. All-in-one tool. >>>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clk >>>t >>>rk >>>_______________________________________________ >>>dotNetRDF-develop mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >>-------------------------------------------------------------------------- >>---- >>Flow-based real-time traffic analytics software. Cisco certified tool. >>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>Customize your own dashboards, set traffic alerts and generate reports. >>Network behavioral analysis & security monitoring. All-in-one tool. >>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clkt >>rk >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2014-02-28 10:09:29
|
Tom I have parsing support working on trunk with the NTriples and NQuads parsers defaulting to the new spec so they'll read the data in as UTF-8 rather than as ASCII. We're passing all the official RDF 1.1 tests for NTriples and NQuads but I can't guarantee there aren't any bugs introduced though the changes to support the new spec turned out to be relatively minor. The parser changes have been merged onto default and I'm continuing to work on the ntuples11 branch for the remainder of the implementation work. There's no output support for these formats yet but hopefully I'll get that done later today. Cheers, Rob On 25/02/2014 10:22, "Rob Vesse" <rv...@do...> wrote: >Tom > >Yes the original NTriples and NQuads specifications only allow ASCII, this >was by design to make those formats canonical (since with UTF-8 you can >potentially encode complex characters in multiple ways) and facilitate >reliable data exchange across systems that didn't necessarily support >non-ASCII data. > >Btw the reader only enforces ASCII encoding if you pass a filename (I.e. >when it deals with opening the file stream), if you pass in a pre-opened >StreamReader that is in a different encoding (I.e. UTF-8) it may still >parse successfully though exact behaviour is hard to know in advance. It >will issue a warning about incorrect encoding (via the Warning event) and >it may error out on some native UTF-8 data since the tokeniser is not >written to expect native UTF-8. > >The RDF 1.1 working group have published proposed recommendations which >standardise NQuads & NTriples and part of the standardization is to change >the encoding to UTF-8 but I haven't had chance to update dotNetRDF to >support the updated specs yet. > >Since this is a breaking change to spec and current API behaviour the >existing tokenizers and parsers would need to be modified so that they can >support either the new/old specification. An approach similar to how we >updated Turtle support where we implement the new specifications and the >parsers default to the new spec mode and the writers implement the new >spec but default to producing the old spec as output would be ideal. This >is Postel's law in action if you're wondering why this is done. > >There are issues filed for these upgrades but I haven't had time to >implement them yet, I was considering trying to get these into the next >release anyway and I have some time to start on this at the end of the >week unless you want to attempt this yourself. See CORE-356 >(http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356) for NQuads >and CORE-355 (http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355) >for NTriples which include links to the updated specifications, see the >comments for the most up to date spec links. > >Hope this clarifies things, > >Cheers, > >Rob > >On 25/02/2014 10:06, "Tomasz Pluskiewicz" <tom...@gm...> >wrote: > >>Hi Rob >> >>A colleague of mine has just discovered that the NQuadsParser reads >>file with ASCII encoding while all other use UTF-8. >> >>I understand that this is as described in the specification but why is >>that exactly? >> >>And what do you think about adding a option to the parsers so that >>alternative encodings can be used for reading dataset files? >> >>Cheers, >>Tom >> >>------------------------------------------------------------------------- >>- >>---- >>Flow-based real-time traffic analytics software. Cisco certified tool. >>Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >>Customize your own dashboards, set traffic alerts and generate reports. >>Network behavioral analysis & security monitoring. All-in-one tool. >>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clk >>t >>rk >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > >-------------------------------------------------------------------------- >---- >Flow-based real-time traffic analytics software. Cisco certified tool. >Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >Customize your own dashboards, set traffic alerts and generate reports. >Network behavioral analysis & security monitoring. All-in-one tool. >http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clkt >rk >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: <tr...@do...> - 2014-02-27 16:51:38
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for new variant of NQuads</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 "Low" to "Normal"
</li>
<li>Status changed from "Planned" 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=356" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356</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.
