Java Dependencies

[scottw]

Just a small one: The Java library depends on the Jena SPARQL library
just for a few vocab URIs for FOAF
(com.hp.hpl.jena.sparql.vocabulary.FOAF).

When building a foresite.jar I copied over this one class to remove
the dependency on the whole SPARQL package; it may be worthwhile just
copying over the FOAF NS constants into foresite.

[Richard Jones]

Hi Scott,

I'm reticent to do this for a couple of reasons. Firstly that I'm not
sure of the licensing and re-distribution issues for the Jena code. By
using maven to pull the dependency down at build time we avoid all of
those problems. Secondly, it is the long-term aim of the project to
include a SPARQL interface for querying ore objects, and that will
require the rest of the Jena SPARQL library anyway.

Thanks for getting involved in the code, it is greatly appreciated! Any
other requests for features or functions or API improvements?

Cheers,

Richard

--
=======================================================================
Richard Jones | Hewlett-Packard Limited
Research Engineer, HP Labs | registered office:
Bristol, UK | Cain Road, Bracknell,
| Berks, RG12 1HN.
| Registered No: 690597 England
eml: richard...@hp.com -------------------------------------
blg: http://chronicles-of-richard.blogspot.com/
-----------------------------------------------------------------------
The contents of this message and any attachments to it are confidential
and may be legally privileged. If you have received this message in
error, you should delete it from your system immediately and advise the
sender. To any recipient of this message within HP, unless otherwise
stated you should consider this message and attachments as "HP
CONFIDENTIAL".
========================================================================