RE: [Sparql4j-devel] XML parsing

[Seaborne, A. <and...@hp...>]

-------- Original Message --------
> From: Timo Westkamper <>
> Date: 21 December 2005 10:13
>=20
> Hello.
>=20
> I have added basic SAX based result parsing (SELECT results) into CVS.

There is a mismatch between the JDBC paradigm and the SAX paradigm.  =
JDBC is purely driven by the client application and there are no =
mandator call backs.  SAX is driven by the rate of arrival as given by =
the parser so it migh have to accumulate results until the client is =
ready.

There could be a bounded pipe between application and SAX code but I =
found it simpler to use a StAX parser (Woodstox) because the whole =
results-consuming process is then determined by the application.  It is =
as easy to write StAX code as to write SAX code.

ARQ does this - the code is in ARQ CVS:

:pserver:ano...@cv...:/cvsroot/jena/

Module ARQ
Package com.hp.hpl.jena.query.resultset

>=20
> What is your opinion on including a lightweight RDF API for passing =
RDF
> nodes around?=20

For handling SELECT queries, we don't need a full API.  We need to be =
able to handle RDF terms, but not triples.

For CONSTRUCT, etc, it might be better to properly link the result to =
the local RDf toolkit of choice (e.g. via an InputStream).  c.f. SQL =
Blobs/Clobs.

	Andy

>=20
> Br,
> Timo Westk=E4mper.