1 <?xml version="1.0" standalone="no"?>
2 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN"
3 "http://www.oasis-open.org/docbook/xml/4.1/docbookx.dtd"
5 <!ENTITY % local SYSTEM "local.ent">
7 <!ENTITY % entities SYSTEM "entities.ent">
9 <!ENTITY % common SYSTEM "common/common.ent">
12 <!-- $Id: book.xml,v 1.10 2007-04-10 15:12:51 quinn Exp $ -->
15 <title>Pazpar2 - User's Guide and Reference</title>
17 <firstname>Sebastian</firstname><surname>Hammer</surname>
20 <firstname>Adam</firstname><surname>Dickmeiss</surname>
22 <releaseinfo>&version;</releaseinfo>
24 <year>©right-year;</year>
25 <holder>Index Data</holder>
29 Pazpar2 is a high-performance, user interface-independent, data
30 model-independent metasearching
31 middleware featuring merging, relevance ranking, record sorting,
35 This document is a guide and reference to Pazpar version &version;.
40 <imagedata fileref="common/id.png" format="PNG"/>
43 <imagedata fileref="common/id.eps" format="EPS"/>
50 <chapter id="introduction">
51 <title>Introduction</title>
53 Pazpar2 is a stand-alone metasearch client with a webservice API, designed
54 to be used either from a browser-based client (JavaScript, Flash, Java,
55 etc.), from from server-side code, or any combination of the two.
56 Pazpar2 is a highly optimized client designed to
57 search many resources in parallel. It implements record merging,
58 relevance-ranking and sorting by arbitrary data content, and facet
59 analysis for browsing purposes. It is designed to be data model
60 independent, and is capable of working with MARC, DublinCore, or any
61 other XML-structured response format -- XSLT is used to normalize and extract
62 data from retrieval records for display and analysis. It can be used
63 against any server which supports the Z39.50 protocol. Proprietary
64 backend modules can be used to support a large number of other protocols
65 (please contact Index Data for further information about this).
68 Additional functionality such as
69 user management, attractive displays are expected to be implemented by
70 applications that use pazpar2. Pazpar2 is user interface independent.
71 Its functionality is exposed through a simple REST-style webservice API,
72 designed to be simple to use from an Ajax-enbled browser, Flash
73 animation, Java applet, etc., or from a higher-level server-side language
74 like PHP or Java. Because session information can be shared between
75 browser-based logic and your server-side scripting, there is tremendous
76 flexibility in how you implement your business logic on top of pazpar2.
79 Once you launch a search in pazpar2, the operation continues behind the
80 scenes. Pazpar2 connects to servers, carries out searches, and
81 retrieves, deduplicates, and stores results internally. Your application
82 code may periodically inquire about the status of an ongoing operation,
83 and ask to see records or other result set facets. Result become
84 available immediately, and it is easy to build end-user interfaces which
85 feel extremely responsive, even when searching more than 100 servers
89 Pazpar2 is designed to be highly configurable. Incoming records are
90 normalized to XML/UTF-8, and then further normalized using XSLT to a
91 simple internal representation that is suitable for analysis. By
92 providing XSLT stylesheets for different kinds of result records, you
93 can tune pazpar2 to work against different kinds of information
94 retrieval servers. Finally, metadata is extracted, in a configurable
95 way, from this internal record, to support display, merging, ranking,
96 result set facets, and sorting. Pazpar2 is not bound to a specific model
97 of metadata, such as DublinCore or MARC -- by providing the right
98 configuration, it can work with a number of different kinds of data in
99 support of many different applications.
102 Pazpar2 is designed to be efficient and scalable. You can set it up to
103 search several hundred targets in parallel, or you can use it to support
104 hundreds of concurrent users. It is implemented with the same attention
105 to performance and economy that we use in our indexing engines, so that
106 you can focus on building your application, without worrying about the
107 details of metasearch logic. You can devote all of your attention to
108 usability and let pazpar2 do what it does best -- metasearch.
111 If you wish to connect to commercial or other databases which do not
112 support open standards, please contact Index Data. We have a licensing
113 agreement with a third party vendor which will enable pazpar2 to access
114 thousands of online databases, in addition the vast number of catalogs
115 and online services that support the Z39.50 protocol.
118 Pazpar2 is our attempt to re-think the traditional paradigms for
119 implementing and deploying metasearch logic, with an uncompromising
120 approach to performance, and attempting to make maximum use of the
121 capabilities of modern browsers. The demo user interface that
122 accompanies the distribution is but one example. If you think of new
123 ways of using pazpar2, we hope you'll share them with us, and if we
124 can provide assistance with regards to training, design, programming,
125 integration with different backends, hosting, or support, please don't
126 hesitate to contact us. If you'd like to see functionality in pazpar2
127 that is not there today, please don't hesitate to contact us. It may
128 already be in our development pipeline, or there might be a
129 possibility for you to help out by sponsoring development time or
130 code. Either way, get in touch and we will give you straight answers.
136 Pazpar2 is covered by the GNU license version 2.
137 See <xref linkend="license"/> for further information.
141 <chapter id="installation">
142 <title>Installation</title>
144 Pazpar2 depends on the following tools/libraries:
146 <varlistentry><term><ulink url="&url.yaz;">YAZ</ulink></term>
149 The popular Z39.50 toolkit for the C language. YAZ must be
150 compiled with Libxml2/Libxslt support.
157 In order to compile Pazpar2 an ANSI C compiler is
158 required. The requirements should be the same as for YAZ.
161 <section id="installation.unix">
162 <title>Installation on Unix (from Source)</title>
164 Here is a quick step-by-step guide on how to compile the
165 tools that Pazpar2 uses. Only few systems have none of the required
166 tools binary packages. If, for example, Libxml2/libxslt are already
167 installed as development packages use these.
171 Ensure that the development libraries + header files are
172 available on your system before compiling Pazpar2. For installation
173 of YAZ, refer to the YAZ installation chapter.
176 gunzip -c pazpar2-version.tar.gz|tar xf -
185 <section id="installation.debian">
186 <title>Installation on Debian GNU/Linux</title>
188 All dependencies for Pazpar2 are available as
189 <ulink url="&url.debian;">Debian</ulink>
190 packages for the sarge (stable in 2005) and etch (testing in 2005)
194 The procedures for Debian based systems, such as
195 <ulink url="&url.ubuntu;">Ubuntu</ulink> is probably similar
198 apt-get install libyaz-dev
201 With these packages installed, the usual configure + make
202 procedure can be used for Pazpar2 as outlined in
203 <xref linkend="installation.unix"/>.
209 <title>Using pazpar2</title>
211 This chapter provides a general introduction to the use and deployment of pazpar2.
214 <section id="architecture">
215 <title>Pazpar2 and your systems architecture</title>
217 Pazpar2 is designed to provide asynchronous, behind-the-scenes
218 metasearching functionality to your application, exposing this
219 functionality using a simple webservice API that can be accessed
220 from any number of development environments. In particular, it is
221 possible to combine pazpar2 either with your server-side dynamic
222 website scripting, with scripting or code running in the browser, or
223 with any combination of the two. Pazpar2 is an excellent tool for
224 building advanced, Ajax-based user interfaces for metasearch
225 functionality, but it isn't a requirement -- you can choose to use
226 pazpar2 entirely as a backend to your regular server-side scripting.
227 When you do use pazpar2 in conjunction
228 with browser scripting (JavaScript/Ajax, Flash, applets, etc.), there are
229 special considerations.
233 Pazpar2 implements a simple but efficient HTTP server, and it is
234 designed to interact directly with scripting running in the browser
235 for the best possible performance, and to limit overhead when
236 several browser clients generate numerous webservice requests.
237 However, it is still desirable to use a conventional webserver,
238 such as Apache, to serve up graphics, HTML documents, and
239 server-side scripting. Because the security sandbox environment of
240 most browser-side programming environments only allows communication
241 with the server from which the enclosing HTML page or object
242 originated, pazpar2 is designed so that it can act as a transparent
243 proxy in front of an existing webserver (see <xref
244 linkend="pazpar2_conf"/> for details). In this mode, all regular
245 HTTP requests are transparently passed through to your webserver,
246 while pazpar2 only intercepts search-related webservice requests.
250 If you want to expose your combined service on port 80, you can
251 either run your regular webserver on a different port, a different
252 server, or a different IP address associated with the same server.
256 Sometimes, it may be necessary to implement functionality on your
257 regular webserver that makes use of search results, for example to
258 implement data import functionality, emailing results, history
259 lists, personal citation lists, interlibrary loan functionality
260 ,etc. Fortunately, it is simple to exchange information between
261 pazpar2, your browser scripting, and backend server-side scripting.
262 You can send a session ID and possibly a record ID from your browser
263 code to your server code, and from there use pazpar2s webservice API
264 to access result sets or individual records. You could even 'hide'
265 all of pazpar2s functionality between your own API implemented on
266 the server-side, and access that from the browser or elsewhere. The
267 possibilities are just about endless.
271 <section id="data_model">
272 <title>Your data model</title>
274 Pazpar2 does not have a preconceived model of what makes up a data
275 model. There are no assumption that records have specific fields or
276 that they are organized in any particular way. The only assumption
277 is that data comes packaged in a form that the software can work
278 with (presently, that means XML or MARC), and that you can provide
279 the necessary information to massage it into pazpar2's internal
284 Handling retrieval records in pazpar2 is a two-step process. First,
285 you decide which data elements of the source record you are
286 interested in, and you specify any desired massaging or combining of
287 elements using an XSLT stylesheet (MARC records are automatically
288 normalized to MARCXML before this step). If desired, you can run
289 multiple XSLT stylesheets in series to accomplish this, but the
290 output of the last one should be a representation of the record in a
291 schema that pazpar2 understands.
295 The intermediate, internal representation of the record looks like
298 <record xmlns="http://www.indexdata.com/pazpar2/1.0"
299 mergekey="title The Shining author King, Stephen">
301 <metadata type="title">The Shining</metadata>
303 <metadata type="author">King, Stephen</metadata>
305 <metadata type="kind">ebook</metadata>
307 <!-- ... and so on -->
311 As you can see, there isn't much to it. There are really only a few
312 important elements to this file.
316 Elements should belong to the namespace
317 http://www.indexdata.com/pazpar2/1.0. If the root node contains the
318 attribute 'mergekey', then every record that generates the same
319 merge key (normalized for case differences, white space, and
320 truncation) will be joined into a cluster. In other words, you
321 decide how records are merged. If you don't include a merge key,
322 records are never merged. The 'metadata' elements provide the meat
323 of the elements -- the content. the 'type' attribute is used to
324 match each element against processing rules that determine what
325 happens to the data element next.
329 The next processing step is the extraction of metadata from the
330 intermediate representation of the record. This is governed by the
331 'metadata' elements in the 'service' section of the configuration
332 file. See <xref linkend="config-server"/> for details. The metadata
333 in the retrieval record ultimately drives merging, sorting, ranking,
334 the extraction of browse facets, and display, all configurable.
338 <section id="client">
339 <title>Client development</title>
341 You can use pazpar2 from any environment that allows you to use
342 webservices. The initial goal of the software was to support
343 Ajax-based applications, but there literally are no limits to what
344 you can do. You can use pazpar2 from Javascript, Flash, Java, etc.,
345 on the browser side, and from any development environment on the
346 server side, and you can pass session tokens and record IDs freely
347 around between these environments to build sophisticated applications.
348 Use your imagination.
352 The webservice API of pazpar2 is described in detail in <xref
353 linkend="pazpar2_protocol"/>.
357 In brief, you use the 'init' command to create a session, a
358 temporary workspace which carries information about the current
359 search. You start a new search using the 'search' command. Once the
360 search has been started, you can follow its progress using the
361 'stat', 'bytarget', 'termlist', or 'show' commands. Detailed records
362 can be fetched using the 'record' command.
366 <section id="nonstandard">
367 <title>Connecting to non-standard resources</title>
369 Pazpar2 uses Z39.50 as its switchboard language -- i.e. as far as it
370 is concerned, all resources speak Z39.50. It is, however, equipped
371 to handle a broad range of different server behavior, through
372 configurable query mapping and record normalization. If you develop
373 configuration, stylesheets, etc., for a new type of resources, we
374 encourage you to share your work.
378 For a growing number of resources, Z39.50 is all you need. Over the
379 last few years, a number of commercial, full-text resources have
380 implemented Z39.50. These can be used through pazpar2 with little or
381 no effort. Resources that use non-standard record formats will
382 require a bit of XSLT work, but that's all.
386 But what about resources that don't support Z39.50 at all? The NISO
387 SRU protocol is slowly gathering steam. Other resources might
388 support OpenSearch, private, XML/HTTP-based protocols, or something
389 else entirely. Some databases exist only as web user interfaces and
390 will require screen-scraping. Still others exist only as static
391 files, or perhaps as databases supporting the OAI-PMH protocol.
392 There is hope! Read on.
395 </chapter> <!-- Using pazpar2 -->
397 <reference id="reference">
398 <title>Reference</title>
401 The material in this chapter is drawn directly from the individual
408 <appendix id="license"><title>License</title>
410 <section id="gpl"><title>GPL</title>
414 Copyright © ©right-year; Index Data.
418 Pazpar2 is free software; you can redistribute it and/or modify it under
419 the terms of the GNU General Public License as published by the Free
420 Software Foundation; either version 2, or (at your option) any later
425 Pazpar2 is distributed in the hope that it will be useful, but WITHOUT ANY
426 WARRANTY; without even the implied warranty of MERCHANTABILITY or
427 FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
432 You should have received a copy of the GNU General Public License
433 along with Pazpar2; see the file LICENSE. If not, write to the
434 Free Software Foundation, 59 Temple Place - Suite 330, Boston, MA
439 GNU GENERAL PUBLIC LICENSE
442 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
443 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
444 Everyone is permitted to copy and distribute verbatim copies
445 of this license document, but changing it is not allowed.
449 The licenses for most software are designed to take away your
450 freedom to share and change it. By contrast, the GNU General Public
451 License is intended to guarantee your freedom to share and change free
452 software--to make sure the software is free for all its users. This
453 General Public License applies to most of the Free Software
454 Foundation's software and to any other program whose authors commit to
455 using it. (Some other Free Software Foundation software is covered by
456 the GNU Library General Public License instead.) You can apply it to
459 When we speak of free software, we are referring to freedom, not
460 price. Our General Public Licenses are designed to make sure that you
461 have the freedom to distribute copies of free software (and charge for
462 this service if you wish), that you receive source code or can get it
463 if you want it, that you can change the software or use pieces of it
464 in new free programs; and that you know you can do these things.
466 To protect your rights, we need to make restrictions that forbid
467 anyone to deny you these rights or to ask you to surrender the rights.
468 These restrictions translate to certain responsibilities for you if you
469 distribute copies of the software, or if you modify it.
471 For example, if you distribute copies of such a program, whether
472 gratis or for a fee, you must give the recipients all the rights that
473 you have. You must make sure that they, too, receive or can get the
474 source code. And you must show them these terms so they know their
477 We protect your rights with two steps: (1) copyright the software, and
478 (2) offer you this license which gives you legal permission to copy,
479 distribute and/or modify the software.
481 Also, for each author's protection and ours, we want to make certain
482 that everyone understands that there is no warranty for this free
483 software. If the software is modified by someone else and passed on, we
484 want its recipients to know that what they have is not the original, so
485 that any problems introduced by others will not reflect on the original
486 authors' reputations.
488 Finally, any free program is threatened constantly by software
489 patents. We wish to avoid the danger that redistributors of a free
490 program will individually obtain patent licenses, in effect making the
491 program proprietary. To prevent this, we have made it clear that any
492 patent must be licensed for everyone's free use or not licensed at all.
494 The precise terms and conditions for copying, distribution and
497 GNU GENERAL PUBLIC LICENSE
498 TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
500 0. This License applies to any program or other work which contains
501 a notice placed by the copyright holder saying it may be distributed
502 under the terms of this General Public License. The "Program", below,
503 refers to any such program or work, and a "work based on the Program"
504 means either the Program or any derivative work under copyright law:
505 that is to say, a work containing the Program or a portion of it,
506 either verbatim or with modifications and/or translated into another
507 language. (Hereinafter, translation is included without limitation in
508 the term "modification".) Each licensee is addressed as "you".
510 Activities other than copying, distribution and modification are not
511 covered by this License; they are outside its scope. The act of
512 running the Program is not restricted, and the output from the Program
513 is covered only if its contents constitute a work based on the
514 Program (independent of having been made by running the Program).
515 Whether that is true depends on what the Program does.
517 1. You may copy and distribute verbatim copies of the Program's
518 source code as you receive it, in any medium, provided that you
519 conspicuously and appropriately publish on each copy an appropriate
520 copyright notice and disclaimer of warranty; keep intact all the
521 notices that refer to this License and to the absence of any warranty;
522 and give any other recipients of the Program a copy of this License
523 along with the Program.
525 You may charge a fee for the physical act of transferring a copy, and
526 you may at your option offer warranty protection in exchange for a fee.
528 2. You may modify your copy or copies of the Program or any portion
529 of it, thus forming a work based on the Program, and copy and
530 distribute such modifications or work under the terms of Section 1
531 above, provided that you also meet all of these conditions:
533 a) You must cause the modified files to carry prominent notices
534 stating that you changed the files and the date of any change.
536 b) You must cause any work that you distribute or publish, that in
537 whole or in part contains or is derived from the Program or any
538 part thereof, to be licensed as a whole at no charge to all third
539 parties under the terms of this License.
541 c) If the modified program normally reads commands interactively
542 when run, you must cause it, when started running for such
543 interactive use in the most ordinary way, to print or display an
544 announcement including an appropriate copyright notice and a
545 notice that there is no warranty (or else, saying that you provide
546 a warranty) and that users may redistribute the program under
547 these conditions, and telling the user how to view a copy of this
548 License. (Exception: if the Program itself is interactive but
549 does not normally print such an announcement, your work based on
550 the Program is not required to print an announcement.)
552 These requirements apply to the modified work as a whole. If
553 identifiable sections of that work are not derived from the Program,
554 and can be reasonably considered independent and separate works in
555 themselves, then this License, and its terms, do not apply to those
556 sections when you distribute them as separate works. But when you
557 distribute the same sections as part of a whole which is a work based
558 on the Program, the distribution of the whole must be on the terms of
559 this License, whose permissions for other licensees extend to the
560 entire whole, and thus to each and every part regardless of who wrote it.
562 Thus, it is not the intent of this section to claim rights or contest
563 your rights to work written entirely by you; rather, the intent is to
564 exercise the right to control the distribution of derivative or
565 collective works based on the Program.
567 In addition, mere aggregation of another work not based on the Program
568 with the Program (or with a work based on the Program) on a volume of
569 a storage or distribution medium does not bring the other work under
570 the scope of this License.
572 3. You may copy and distribute the Program (or a work based on it,
573 under Section 2) in object code or executable form under the terms of
574 Sections 1 and 2 above provided that you also do one of the following:
576 a) Accompany it with the complete corresponding machine-readable
577 source code, which must be distributed under the terms of Sections
578 1 and 2 above on a medium customarily used for software interchange; or,
580 b) Accompany it with a written offer, valid for at least three
581 years, to give any third party, for a charge no more than your
582 cost of physically performing source distribution, a complete
583 machine-readable copy of the corresponding source code, to be
584 distributed under the terms of Sections 1 and 2 above on a medium
585 customarily used for software interchange; or,
587 c) Accompany it with the information you received as to the offer
588 to distribute corresponding source code. (This alternative is
589 allowed only for noncommercial distribution and only if you
590 received the program in object code or executable form with such
591 an offer, in accord with Subsection b above.)
593 The source code for a work means the preferred form of the work for
594 making modifications to it. For an executable work, complete source
595 code means all the source code for all modules it contains, plus any
596 associated interface definition files, plus the scripts used to
597 control compilation and installation of the executable. However, as a
598 special exception, the source code distributed need not include
599 anything that is normally distributed (in either source or binary
600 form) with the major components (compiler, kernel, and so on) of the
601 operating system on which the executable runs, unless that component
602 itself accompanies the executable.
604 If distribution of executable or object code is made by offering
605 access to copy from a designated place, then offering equivalent
606 access to copy the source code from the same place counts as
607 distribution of the source code, even though third parties are not
608 compelled to copy the source along with the object code.
610 4. You may not copy, modify, sublicense, or distribute the Program
611 except as expressly provided under this License. Any attempt
612 otherwise to copy, modify, sublicense or distribute the Program is
613 void, and will automatically terminate your rights under this License.
614 However, parties who have received copies, or rights, from you under
615 this License will not have their licenses terminated so long as such
616 parties remain in full compliance.
618 5. You are not required to accept this License, since you have not
619 signed it. However, nothing else grants you permission to modify or
620 distribute the Program or its derivative works. These actions are
621 prohibited by law if you do not accept this License. Therefore, by
622 modifying or distributing the Program (or any work based on the
623 Program), you indicate your acceptance of this License to do so, and
624 all its terms and conditions for copying, distributing or modifying
625 the Program or works based on it.
627 6. Each time you redistribute the Program (or any work based on the
628 Program), the recipient automatically receives a license from the
629 original licensor to copy, distribute or modify the Program subject to
630 these terms and conditions. You may not impose any further
631 restrictions on the recipients' exercise of the rights granted herein.
632 You are not responsible for enforcing compliance by third parties to
635 7. If, as a consequence of a court judgment or allegation of patent
636 infringement or for any other reason (not limited to patent issues),
637 conditions are imposed on you (whether by court order, agreement or
638 otherwise) that contradict the conditions of this License, they do not
639 excuse you from the conditions of this License. If you cannot
640 distribute so as to satisfy simultaneously your obligations under this
641 License and any other pertinent obligations, then as a consequence you
642 may not distribute the Program at all. For example, if a patent
643 license would not permit royalty-free redistribution of the Program by
644 all those who receive copies directly or indirectly through you, then
645 the only way you could satisfy both it and this License would be to
646 refrain entirely from distribution of the Program.
648 If any portion of this section is held invalid or unenforceable under
649 any particular circumstance, the balance of the section is intended to
650 apply and the section as a whole is intended to apply in other
653 It is not the purpose of this section to induce you to infringe any
654 patents or other property right claims or to contest validity of any
655 such claims; this section has the sole purpose of protecting the
656 integrity of the free software distribution system, which is
657 implemented by public license practices. Many people have made
658 generous contributions to the wide range of software distributed
659 through that system in reliance on consistent application of that
660 system; it is up to the author/donor to decide if he or she is willing
661 to distribute software through any other system and a licensee cannot
664 This section is intended to make thoroughly clear what is believed to
665 be a consequence of the rest of this License.
667 8. If the distribution and/or use of the Program is restricted in
668 certain countries either by patents or by copyrighted interfaces, the
669 original copyright holder who places the Program under this License
670 may add an explicit geographical distribution limitation excluding
671 those countries, so that distribution is permitted only in or among
672 countries not thus excluded. In such case, this License incorporates
673 the limitation as if written in the body of this License.
675 9. The Free Software Foundation may publish revised and/or new versions
676 of the General Public License from time to time. Such new versions will
677 be similar in spirit to the present version, but may differ in detail to
678 address new problems or concerns.
680 Each version is given a distinguishing version number. If the Program
681 specifies a version number of this License which applies to it and "any
682 later version", you have the option of following the terms and conditions
683 either of that version or of any later version published by the Free
684 Software Foundation. If the Program does not specify a version number of
685 this License, you may choose any version ever published by the Free Software
688 10. If you wish to incorporate parts of the Program into other free
689 programs whose distribution conditions are different, write to the author
690 to ask for permission. For software which is copyrighted by the Free
691 Software Foundation, write to the Free Software Foundation; we sometimes
692 make exceptions for this. Our decision will be guided by the two goals
693 of preserving the free status of all derivatives of our free software and
694 of promoting the sharing and reuse of software generally.
698 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
699 FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
700 OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
701 PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
702 OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
703 MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
704 TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
705 PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
706 REPAIR OR CORRECTION.
708 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
709 WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
710 REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
711 INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
712 OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
713 TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
714 YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
715 PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
716 POSSIBILITY OF SUCH DAMAGES.
718 END OF TERMS AND CONDITIONS
725 <!-- Keep this comment at the end of the file
730 sgml-minimize-attributes:nil
731 sgml-always-quote-attributes:t
734 sgml-parent-document: nil
735 sgml-local-catalogs: nil
736 sgml-namecase-general:t