X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Ffuture.xml;h=517ec3f0b1296f11d9c44aba01194296cf26b30c;hb=3ac26d1524a5f5988adfa2f40c00a0d0e3094978;hp=52be2ddd4f611820854e9af4647858ea9f25d7a0;hpb=ab0fd2f75e554d1c9c0e722abf073f9840f7739b;p=yaz-moved-to-github.git diff --git a/doc/future.xml b/doc/future.xml index 52be2dd..517ec3f 100644 --- a/doc/future.xml +++ b/doc/future.xml @@ -1,6 +1,6 @@ - + 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,14 +8,14 @@ flexibility, greater support for access/resource control, and easy support for Explain (possibly with Zebra as an extra database engine). - + 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. @@ -23,7 +23,7 @@ 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 @@ -31,7 +31,7 @@ us a note and let's see what we can come up with. - +