N3 parse errors with language qualified literals and empty string literals
Reported by John Fieber | January 21st, 2009 @ 07:50 PM
Language qualifiers need to allow hyphen characters, for example:
"foobar"@en-US
Reference: http://www.dajobe.org/2004/01/turtle/#language
Empty string literals need to be permitted, reference: http://www.dajobe.org/2004/01/turtle/#string
Comments and changes to this ticket
-
John Fieber January 21st, 2009 @ 07:50 PM
- Assigned user set to “Tom Morris”
-
Tom Morris January 22nd, 2009 @ 03:34 PM
- State changed from “new” to “open”
Thanks for the report, John. I'm quite busy at the moment, but I will apply the patch (and fix a few other bits) then release a new gem soon.
-
Tom Morris February 2nd, 2009 @ 10:09 PM
- State changed from “open” to “resolved”
(from [e8334fbc084cbae875dda509a17ab5779e9e8c1c]) applied John Fieber's patches to the Notation3 functionality from Lighthouse tickets [#6 state:resolved] and [#7 state:resolved] http://github.com/tommorris/redd...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
RDF library written in Ruby.
People watching this ticket
John Fieber
Tom Morris
Attachments
Referenced by
-
6
N3 parse errors with language qualified literals and empty string literals
(from [e8334fbc084cbae875dda509a17ab5779e9e8c1c]) applied...
-
7
Global name space pollution
(from [e8334fbc084cbae875dda509a17ab5779e9e8c1c]) applied...