On 16/11/12 15:40, Lewis John Mcgibbney wrote:
Hi All,
I've recently been toiling over this thought at the back of my head.
Jena has legacy RDF parsers [0]... Any23 should aspire to provide and
therefore be the #1 RDF-based parsering library out there.
Jena has a large codebase, I just saw Andy's release... one aspect of
which concerns the deprecation of some features and/or support for
legacy(ish) stuff.
I personally feel that it is about time we took this further and
offered the Jena community an option of whether they would be
interesting in offloading some more of their legacy code (possibly
pulling any good/better parts back into Any23 in the process) by
adopting Any23 as their primary parer implementation.
Any thoughts?
Best
Lewis
[0]
http://jena.apache.org/documentation/javadoc/jena/index.html?com/hp/hpl/jena/rdf/arp/package-summary.html
Great to explore how we can collaborate. The "legacy" in the
announcement is some internal low-level bulk operations (a parser is
affected but the change is a few lines) and some migration support for
old style SPARQL Update.
[0] ARP (the RDF/XML parser) is not legacy. There are some other "not
legacy" parsers:
http://jena.apache.org/documentation/io/riot.html
together with a new I/O architecture:
http://mail-archives.apache.org/mod_mbox/jena-dev/201208.mbox/browser
which is now ready for migrating into the codebase (after a pause due
RDF-WG work and non-Apache time).
In particular, the parser pipeline is have been heavily tuned to get
load performance for TDB. (Long story to do with how Java I/O has
hidden costs.)
Andy
PS the Turtle parser is compliant with the latest RDF 1.1 spec and the
draft RDF 1.1 Turtle test suite.
