Sarven is correct in that Turtle as currently specified does not permit leading digits in the local part of a Qname
The in progress Turtle standardization effort of the W3C RDF Working Group (http://www.w3.org/TR/turtle/) is proposing revisions to the Turtle spec that will eventually allow this. I don't believe we have a writer currently that can write Turtle in the new format - can you confirm this Andy? Even if we did I suspect it would not be the default as for backwards compatibility and maximum interoperability of systems it will make sense to consume the new standard by default on reads but respect the old standard on writes (Postel's law in action) Rob Rob Vesse -- YarcData.com -- A Division of Cray Inc Software Engineer, Bay Area m: 925.960.3941 | o: 925.264.4729 | @: rve...@yarcdata.com | Skype: rvesse 6210 Stoneridge Mall Rd | Suite 120 | Pleasanton CA, 94588 On 4/30/12 5:42 AM, "Sarven Capadisli" <i...@csarven.ca> wrote: >On 12-04-30 01:02 PM, Looser Dominic wrote: >> Dear Jena Community >> >> >> >> I want to mint uri's of the form http://foo/123<http://foo/123> . >> >> If I set the prefix with >> >> model.setNsPrefix("foo", "http://foo/) >> >> and serialize into turtle, the uris stay like the are. >> >> model.shortForm(http://foo/123) gives the expected foo:123. >> >> Why does Jena behave that way and is there a way to circumvent it? >> >> >> >> Best, >> >> Dominic > >I don't know the inner workings of Jena, however, > >http://www.w3.org/TeamSubmission/turtle/#name states that the name part >of a QName can't start with a digit. > >-Sarven >
