1 <chapter id="future"><title>Future Directions</title>
4 We have a new and better version of the front-end server on the drawing
5 board. Resources and external commitments will govern when we'll be
6 able to do something real with it. Features should include greater
7 flexibility, greater support for access/resource control, and easy
8 support for Explain (possibly with Zebra as an extra database engine).
12 &yaz; is a BER toolkit and as such should support all protocols
13 out there based on that. We'd like to see running ILL applications.
14 It shouldn't be that hard. Another thing that would be interesting is
15 LDAP. Maybe a generic framework for doing IR using both LDAP and
20 The SOAP implementation is incomplete. In the future we hope
21 to add more features to it. Perhaps make a WSDL/XML Schema compiler.
22 The authors of libxml2 are already working on XML Schema / RelaxNG
23 compilers so this may not be too hard.
27 It would be neat to have a proper module mechanism for the Generic
28 Frontend Server so that backend would be dynamically
29 loaded (as shared objects / DLLs).
33 Other than that, &yaz; generally moves in the directions which appear to
34 make the most people happy (including ourselves, as prime users of the
35 software). If there's something you'd like to see in here, then drop
36 us a note and let's see what we can come up with.
41 <!-- Keep this comment at the end of the file
46 sgml-minimize-attributes:nil
47 sgml-always-quote-attributes:t
50 sgml-parent-document: "yaz.xml"
51 sgml-local-catalogs: nil
52 sgml-namecase-general:t