/usr/share/doc/yaz-doc/future.html is in yaz-doc 4.2.18-1build1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 10. Future Directions</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="YAZ User's Guide and Reference"><link rel="up" href="index.html" title="YAZ User's Guide and Reference"><link rel="prev" href="comstack.summary.html" title="9. Summary and Synopsis"><link rel="next" href="reference.html" title="Reference"></head><body><link rel="stylesheet" type="text/css" href="common/style1.css"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 10. Future Directions</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="comstack.summary.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="reference.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 10. Future Directions"><div class="titlepage"><div><div><h2 class="title"><a name="future"></a>Chapter 10. Future Directions</h2></div></div></div><p>
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).
</p><p>
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.
</p><p>
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.
</p><p>
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).
</p><p>
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.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="comstack.summary.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="reference.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">9. Summary and Synopsis </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Reference</td></tr></table></div></body></html>
|