Integration of Daisy in non-Java environments.

In GSOC 2006 we had a student that created a PHP library.

Daisy has a language-neutral HTTP/XML-based API to access its stand-alone repository server.

Daisy has also (of course) a native Java API wich can work in-JVM or remotely (transparently communicating over the HTTP/XML API), as illustrated in this diagram. Currently most Daisy-API usage (that we are aware of) makes use of these Java APIs.

It would be interesting to integrate facilities for the publication of content stored in the Daisy repository in non-Java-environments. For example Ruby(-on-Rails), Python or Mono/.NET.

In the first place content publication facilities (i.e. retrieval only) would be interesting, but support for updating content would also be interesting.

You could start out by experimenting a little bit with doing HTTP calls, and some XSL-based (or whatever) styling in the target language of choice. However, the goal of this project should rather be the development of a library or framework which makes such things quick and simple to use. Probably some useful feedback about the usability of Daisy's HTTP-API will also evolve from this project.

For use with Mono or .NET, it would also be interesting if the existing repository client Java code could be run transparently on these VMs.

If you are interested in this project, you should:

• have knowledge about the target language of choice, since Daisy developers won't be able to help you much with that
• have knowledge about XML and related technologies (XML namespaces, XSL), and the APIs to process them in the selected language (or be willing to learn about them on your own)
• much Java knowledge is not really needed, since you could consider the repository server to be a black-box