Issue 127 in rdflib: N3 parser complains about @base statement

27 views
Skip to first unread message

rdf...@googlecode.com

unread,
May 8, 2010, 2:43:03 AM5/8/10
to rdfli...@googlegroups.com
Status: New
Owner: ----

New issue 127 by dorian.taylor.lists: N3 parser complains about @base
statement
http://code.google.com/p/rdflib/issues/detail?id=127

What steps will reproduce the problem?
1. Create an N3 file with a @base keyword
2. parse it with Graph().parse('file', format='n3')
3. Crash and burn

What is the expected output? What do you see instead?

Traceback (most recent call last):
File "./four-part-scan.py", line 23, in <module>
g.parse('../log/durr.n3', format='n3')
File "build/bdist.linux-i686/egg/rdflib/Graph.py", line 890, in parse
File "build/bdist.linux-i686/egg/rdflib/Graph.py", line 713, in parse
File "build/bdist.linux-i686/egg/rdflib/syntax/parsers/N3Parser.py", line
32, in parse
File "build/bdist.linux-i686/egg/rdflib/syntax/parsers/n3p/n3proc.py",
line 119, in parse
File "build/bdist.linux-i686/egg/rdflib/syntax/parsers/n3p/n3p.py", line
83, in parse
ValueError: Found @base when expecting a
http://www.w3.org/2000/10/swap/grammar/n3#document .
todoStack=[['http://www.w3.org/2000/10/swap/grammar/n3#document', []]]

What version of the product are you using? On what operating system?

rdflib 2.4.2 on Ubuntu 9.04

Please provide any additional information below.

Notwithstanding not working, that BNF-in-RDF looks pretty slick! I may have
to try it out sometime.

--
You received this message because you are subscribed to the Google Groups "rdflib-dev" group.
To post to this group, send email to rdfli...@googlegroups.com.
To unsubscribe from this group, send email to rdflib-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rdflib-dev?hl=en.

rdf...@googlecode.com

unread,
May 8, 2010, 4:24:23 AM5/8/10
to rdfli...@googlegroups.com
Updates:
Status: Duplicate
Mergedinto: 22

Comment #1 on issue 127 by gromgull: N3 parser complains about @base
statement
http://code.google.com/p/rdflib/issues/detail?id=127

This was fixed in trunk - which will be released very very soon! :)
Reply all
Reply to author
Forward
0 new messages