openRDF.org Issue Tracker

[RIO-72] There is no way to specify "preserveBNodeIDs" property when doing RDF import

Tue, 1 Dec 2009 18:35:05 +0100 (CET)

* There is now way to pass pre-created to RepositoryConnection.add(Reader|InputStream|File) method with this option enabled.
* Both RDFParserBase and RDFInserter have preserveBNodeIDs property. In the first class it is false by default, in the second is true by default. There should be a single place for this functionality.

Nice to have feature:
- renumerateBNodeIDs property for RDFWriter, which should re-number nodes like "n1", "n2", "n3" ([see forum|http://sourceforge.net/mailarchive/forum.php?thread_name=4B139FB4.5080809%40mail.ru&forum_name=sesame-general])

[RIO-69] N3 and Turtle media types need updating

Tue, 7 Jul 2009 19:00:29 +0200 (CEST)

The MIME / media / content types for N3 and Turtle are currently defined as text/rdf+n3 and application/x-turtle respectively: http://repo.aduna-software.org/svn/org.openrdf/sesame/trunk/core/rio/api/src/main/java/org/openrdf/rio/RDFFormat.java .

They need to be updated to text/n3 and text/turtle. For Turtle see the latest specification at http://www.w3.org/TeamSubmission/turtle/#sec-mediaReg . The N3 specification is a bit buggy with regard to that, it switches between text/rdf+n3 and text/n3: http://www.w3.org/TeamSubmission/n3/ . However see also http://www.w3.org/blog/SW/2008/01/15/w3c_team_submission_on_n3_and_turtle , http://chatlogs.planetrdf.com/swig/2009-04-01.html#T14-00-16 and some more discussion on http://lists.w3.org/Archives/Public/semantic-web/2009May/0021.html .

Since RDFFormat accepts a collection of MIME types perhaps it would be even better to add the old ones as well so that the right parser can be selected for data served with the old types. For Turtle the type application/turtle could be added to such a collection as well, as it was the primary type mentioned on http://www.dajobe.org/2004/01/turtle/2007-11-20/#sec-mime .

[RIO-59] Add a stylesheet to the RDF/XML serialized data

Mon, 30 Jul 2007 15:18:10 +0200 (CEST)

RDF/XML is sometimes unreadable for human beings, so we developped an XSL that render it nicely. We had to extends the RDFXML writer to incorporate it to the data. Might be cleaner and useful to other rio user to integrate it into the RDFXMLWriter.

[RIO-53] Turtle Parser does not update location

Fri, 3 Nov 2006 06:10:20 +0100 (CET)

The Turtle Parser only updates the line location at the beginning of the file and when skipping lines.

[RIO-47] Reduce memory requirements for verifying uniqueness of rdf:ID attributes

Wed, 14 Jun 2006 12:24:04 +0200 (CEST)

Source: http://www.openrdf.org/forum/mvnforum/viewthread?thread=967

The RDF/XML specification requires the values of rdf:ID attributes combined with the applicable base URI to be unique within a single RDF/XML document[1]. The RDF/XML parser currently stores these ID-base URI-combinations as URIs in a HashMap. As a result, a considerable amount of memory is needed to be able to parse documents that contain large amounts of rdf:ID attributes, such as the Uniprot benchmark files[2]. As the number of base URIs normally is much smaller than the number of IDs it is possible to reduce the memory requirements by storing the IDs per base URI so that the base URI only needs to be stored once.

[1] http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/#section-constraints-id
[2] http://expasy3.isb-sib.ch/~ejain//rdf/data-for-benchmarks/

[RIO-43] N3Parser

Mon, 13 Apr 2009 06:34:08 +0200 (CEST)

Is a N3Parser planned?
It would be nice, since we can write n3 files!

[RIO-29] blank node handling in parsers doesn't scale

Wed, 21 Sep 2005 12:54:57 +0200 (CEST)

The processing of blank nodes in Rio's parsers doesn't scale for documents with huge amount of named blank nodes in it. The reason for this is that the parsers keep track of all encountered named blank nodes as they may be referenced again later in the document. As blank node names scope to the entire document, the same blank node name must map to the same blank node objects. Possibly the best way to solve this is to do the mapping in an external handler. One such handler might use a database or the file system to store mapping information instead of keeping this information in main memory.

[RIO-5] character check in NTriplesParser

Wed, 2 Mar 2005 11:15:43 +0100 (CET)

The NTriplesParser does not check that the parsed characters are legal N-Triples characters. I.e. characters like ä or ô are accepted without warning but they are not legal N-Triples characters.

[RIO-1] XML Literal normalization

Wed, 2 Mar 2005 11:15:14 +0100 (CET)

XML literal normalization is not implemented yet.