X-Git-Url: http://git.indexdata.com/?p=yaz-moved-to-github.git;a=blobdiff_plain;f=doc%2Ffuture.xml;h=875741e96f10228ea7e488138e5dc931afe802df;hp=937c7f318f4304af036af7a18a9e5b63d05f3064;hb=053367cbe356fb3ce0def34b065dae589d700daf;hpb=33c05384cfbca55da4ff97e5b2047b16596c72f7 diff --git a/doc/future.xml b/doc/future.xml index 937c7f3..875741e 100644 --- a/doc/future.xml +++ b/doc/future.xml @@ -1,4 +1,3 @@ - Future Directions @@ -10,24 +9,33 @@ - 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. + &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. - 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. + 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. - Other than that, YAZ generally moves in the directions which appear to + 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). + + + + 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. +