Re: [dotNetRDF-bugs] JsonParser bug

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

Hi Aleksandr

 

This is now fixed and your test case added.

 

The main problem with JSON is that the formats are fully standardised so
some implementations do things slightly differently from others.  Have
applied your fixes so should be compatible with most implementations now.

 

Thanks again,

 

Rob Vesse

dotNetRDF Lead Developer

================================================================

Developer Discussion & Feature Request -
dot...@li...

Bug Reports - dot...@li...

User Help & Support - dot...@li...

 

Website: http://www.dotnetrdf.org

User Guide: http://www.dotnetrdf.org/content.asp?pageID=User%20Guide

API: http://www.dotnetrdf.org/api/

================================================================

 

 

 

From: Aleksandr A. Zaripov [mailto:za...@tp...] 
Sent: 17 February 2010 05:22
To: dot...@li...
Subject: [dotNetRDF-bugs] JsonParser bug

 

Hi

RdfJsonParser and SparqlJsonParser have bug in parsing literal. Default
sparql endpoint of virtuoso returns them with "xml:lang" attribute, but in
this parsers waits for only "lang" token.
It seems to me, that line 251 of RdfJsonParser should be

else if (token.Equals("lang") || token.Equals("xml:lang"))

and line 508 of SparqlJsonParser

else if (token.Equals("lang") || token.Equals("xml:lang"))

The example of ontology attached to this mail.

Query should be like

select distinct ?comment where { ?s rdfs:comment ?comment }

Thanks, Alexander A. Zaripov
za...@tp...