Jackie’s Weblog

去年11月20日John Blyberg 写了一篇ILS Customer Bill-of-Rights，随即Talis的Richard Wallis在公司Blog上做了相应回复。就这样，由ILS Customer Bill-of-Rights引发的一系列对话开始了，具体流程如下：

Blyberg: ILS Customer Bill-of-Rights

Wallis: An ILS Customer Bill-of-Rights

Blyberg: Talis responds to “Bill-of-Rights”

Wallis: ILS customer Bill-of-Rights – round two

Blyberg: ILS Customer Bill-of-Rights Discourse Continues

Wallis: The rise of the Platform – Continuing the Library 2.0 discourse with Blyberg

最后一篇Wallis写的也许可以算是John和Richard之间对话的终结。Wallis在此文的开头还特地添加了相关文章包括对话的导火线、对话各步骤及其他人的看法。下面我再加一些看到的其他人对此对话的看法：

Wallis – Blyberg : The supprt issue

ILS Architecture: Open vs Turnkey

A reply to the ILS Customer Bill of Rights

这么热闹的讨论，另一大厂商SirsiDynix怎么可以没有反映呢，Stephen Abram在Web 2.0, Library 2.0, and Librarian 2.0: Preparing for the 2.0 World中也针对性地作出了回应。因为全文还有其他内容，我就把相关的转贴在下面：

John Blyberg, at Ann Arbor District Library, has promulgated an ILS Customer Bill of Rights, which asks for four things:

   1. Open, read-only, direct access to the database

   2. A full-blown, W3C standards-based API to all read-write functions

   3. The option to run the ILS on hardware of our choosing, on servers that we administer

   4. High security standards

Many of the requested aspects of Library 2.0 are already available in the SirsiDynix ILS interfaces for those who choose to update to current versions. SirsiDynix systems (Unicorn and Horizon) are well prepared to adapt to the 2.0 world. SirsiDynix has for many years offered open and allowed read-only, direct access to the database.

SirsiDynix systems (Unicorn and Horizon) have a library of APIs, and we have offered API training for years for any client to write anything they can imagine or for which they need customization for their particular environment. Loads of our clients do APIs, and they share APIs among themselves all the time and present them to each other at the user group meetings and big CODI and SuperConferences. It’s not full blown W3C compliant yet, but we will be after the standard gets out there more fully.

SirsiDynix allows clients to use the hardware of their choosing, on servers that clients administer. Of course, there is no such thing as open hardware (yet?), but we try not to straightjacket our clients too much. We have always encouraged our customers to choose their own hardware within the specifications we have tested. We can’t promise the software will work on everything – especially those platforms and hardware we haven’t tested, but we’re pretty flexible. We do offer hosted solutions especially for those smaller libraries that don’t have the internal systems expertise. It’s a useful option.

Lastly, we have pretty high security standards, but we don’t think they’re high enough, especially in today’s challenging systems environments. Horizon 8.0 and Corinthian will be released in 2006 and have much higher security and two-way encryption standards. Unicorn 3.X has plans to implement higher security options as well.

While this list is largely focused on the systems librarian’s needs, it does provide a foundation for Library 2.0 for end-users as long as we have Librarian 2.0 in place.

相比较，Abram回答简洁干脆，同时还拼命夸自己产品并提一些无关痛痒的缺陷；Wallis则认真仔细，耐心地沟通，还比较可爱，在文中还用round two－第二回合。

我因为对ILS始终没有深刻全面的认识，大部分情况下还是作为读者来使用系统，于是对他们的对话也没有很深的体会。而且这场拉锯战比较长，Blyberg在ILS Customer Bill-of-Rights Discourse Continues最后说到，Headache anyone?是的，我头痛。

不过，需要认识到图书馆在2..0过程中与系统供应商的关系也是一个关键点。双方交流沟通必不可少。各个厂商对自己产品定位、销售策略等也要在2.0时代做相应转变。很高兴地是从这场对话中可以看到Talis和SirsiDynix都是有所准备。特别是Talis前段时间发布了纲领性的白皮书。此外，让我们看看国内的情况是如何：参见A catalog with service (奇正童话)。国内的北大方正、清华同方、上海金鑫等又是怎么面对目前形式的变化？