W3C home > Mailing lists > Public > www-rdf-interest@w3.org > April 2002

Re: Queries and report generation in RDF/N3

From: Sean B. Palmer <sean@mysterylights.com>
Date: Fri, 26 Apr 2002 01:54:02 +0100
Message-ID: <023901c1ecbc$ddb4b960$d8570150@localhost>
To: "Graham Klyne" <GK@NineByNine.org>
Cc: "RDF Interest group" <www-rdf-interest@w3.org>
> And there's yet another N3 parser in Python.

Looking through the code, I think that there are a few N3 features (e.g.
"-> x ->") that have been removed from the language, and I really don't
like new directive additions (e.g. @equivalence). Still, N3 is hardly the
most well defined and documented language in the world... :-)

That aside, I'm hoping that this parser will be swift and portable.
However, I tried it on some real-world N3 data [1], and got some odd

Calling parser
Syntax error at line 1, char 11
N3 directive error: Name expected
@prefix : <<<--
NextToken: :, TokenType: :
Syntax error at line 53, char 24
Error in statement: Invalid node: <uri> or qname expected
   :name "Attu"; :state "AK" .
x:BRW a:icao "KBRW"; a:i<<--
NextToken: :, TokenType: :
Syntax error at line 61, char 55
Expected '.' or end of input
   :name "Bettles"; :state "AK" .
x:BIG a:icao "KBIG"; a:iata "BIG"; :latitude "64.00"; :<<--
NextToken: ;, TokenType: ;

the data is valid, and CWM parses it just fine. Could you possibly check
this out for me? It seems as if it just doesn't allow the ":" prefix, which
is odd.

[1] http://infomesh.net/2001/12/map/data.n3

Kindest Regards,
Sean B. Palmer
@prefix : <http://purl.org/net/swn#> .
:Sean :homepage <http://purl.org/net/sbp/> .
Received on Thursday, 25 April 2002 20:54:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:35 UTC