X-Git-Url: http://git.indexdata.com/?p=yaz-moved-to-github.git;a=blobdiff_plain;f=doc%2Ffuture.xml;h=517ec3f0b1296f11d9c44aba01194296cf26b30c;hp=7278081b5862ef65d5169912000be83051d02499;hb=bd7e251dac1b07c54884d26295f66b90cfb23131;hpb=3b3deb4d093d747360a5eb0e02c6b4e9c8a89b84 diff --git a/doc/future.xml b/doc/future.xml index 7278081..517ec3f 100644 --- a/doc/future.xml +++ b/doc/future.xml @@ -1,6 +1,6 @@ - - Future Directions - + + Future Directions + 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 @@ -8,20 +8,22 @@ flexibility, greater support for access/resource control, and easy support for Explain (possibly with Zebra as an extra database engine). - - - 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. - - + 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. - + + + &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 intersting is + LDAP. Maybe a generic framework for doing IR using both LDAP and + Z39.50 transparently. + + Other than that, YAZ generally moves in the directions which appear to make the most people happy (including ourselves, as prime users of the @@ -29,7 +31,7 @@ us a note and let's see what we can come up with. - +