[saga-rg] Java implementation issues

[G.E.POUND at soton.ac.uk]

Andre,


> There are two major points:
>
>   - if you meet semantic problems with the API, we need
>     immediate feedback, as then the language independent spec
>     needs discussion.
>
>   - as you are the first writing a Java binding for SAGA,
>     you might consider that as a reference implementation.
>     In that case, you should keep the API absolutely free of
>     any project specific code etc.  Best see the
>     implementation as a basis for all future
>     implementations.  For C++ for example, we intend the
>     header files to be usable for other C++ implementations.
>
> One more remark: we are pretty sure that, in one or two
> years from now, the SAGA spec will undergo major revisions.
> That includes firstly a widening of scope, but might
> secondly also affect lok & feel.  So any reference
> implementation should be easily extensible in scope, and
> should, if possible, simple enough to change look and feel
> w/o the need for complete rewrite.

I will be developing the Java implementation to inform my understanding of
the sematics. However I will attempt to provide comments upon te language
independent draft swiftly.

I envision a Java implementation that comprises two parts; an interface
definition, and implementations of that interface for alternative
resources. The interface definition would be suitably lightweight to
provide a reference.

By developing an implementation at this stage I understand that there will
be changes until the API is finalised. However, I hope that this would
further Thilo's aim of speeding the delivery of a stable and usable API.

Graeme