-<!-- $Header: /home/cvsroot/yaz/doc/future.xml,v 1.1 2001-01-04 13:36:24 adam Exp $ -->
-<chapter><title>Future Directions</title>
+ <chapter id="future"><title>Future Directions</title>
-<para>
-We have a new and better version of the frontend server on the drawing
-board. Resources and external commitments will govern when we'll be
-able to do something real with it. Fetures should include greater
-flexibility, greter support for access/resource control, and easy
-support for Explain (possibly with Zebra as an extra database engine).
-</para>
+ <para>
+ We have a new and better version of the front-end server on the drawing
+ board. Resources and external commitments will govern when we'll be
+ able to do something real with it. Features should include greater
+ flexibility, greater support for access/resource control, and easy
+ support for Explain (possibly with Zebra as an extra database engine).
+ </para>
-<para>
-We now support all PDUs of Z39.50-1995. If there is one of the
-supporting structures that you need but can't find in the prt*.h
-files, send us a note; it may be on its way.
-</para>
+ <para>
+ &yaz; is a BER toolkit and as such should support all protocols
+ out there based on that. We'd like to see running ILL applications.
+ It shouldn't be that hard. Another thing that would be interesting is
+ LDAP. Maybe a generic framework for doing IR using both LDAP and
+ Z39.50 transparently.
+ </para>
-<para>
-The 'retrieval' module needs to be finalized and documented. We think
-it can form a useful resource for people dealing with complex record
-structures, but for now, you'll mostly have to chew through the code
-yourself to make use of it. Not acceptable.
-</para>
+ <para>
+ The SOAP implementation is incomplete. In the future we hope
+ to add more features to it. Perhaps make a WSDL/XML Schema compiler.
+ The authors of libxml2 are already working on XML Schema / RelaxNG
+ compilers so this may not be too hard.
+ </para>
-<para>
-Other than that, YAZ generally moves in the directions which appear to
-make the most people happy (including ourselves, as prime users of the
-software). If there's something you'd like to see in here, then drop
-us a note and let's see what we can come up with.
-</para>
-</chapter>
\ No newline at end of file
+ <para>
+ It would be neat to have a proper module mechanism for the Generic
+ Frontend Server so that backend would be dynamically
+ loaded (as shared objects / DLLs).
+ </para>
+
+ <para>
+ Other than that, &yaz; generally moves in the directions which appear to
+ make the most people happy (including ourselves, as prime users of the
+ software). If there's something you'd like to see in here, then drop
+ us a note and let's see what we can come up with.
+ </para>
+
+ </chapter>
+
+ <!-- Keep this comment at the end of the file
+ Local variables:
+ mode: sgml
+ sgml-omittag:t
+ sgml-shorttag:t
+ sgml-minimize-attributes:nil
+ sgml-always-quote-attributes:t
+ sgml-indent-step:1
+ sgml-indent-data:t
+ sgml-parent-document: "yaz.xml"
+ sgml-local-catalogs: nil
+ sgml-namecase-general:t
+ End:
+ -->
projects / yaz-moved-to-github.git / blobdiff