LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  June 2005

ZNG June 2005

Subject:

Re: srw/u next steps

From:

Mike Taylor <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Thu, 30 Jun 2005 14:05:28 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (111 lines)

> Date: Tue, 28 Jun 2005 10:35:09 -0500
> From: Eric Lease Morgan <[log in to unmask]>
>
> SRW/U next steps

Thanks, Eric, both for leading this discussion and for posting the
summary. I have only two comments to make, one technical and one
organisational.

--

First point -- technical:

> Learning from OAI's success
> [...]
> 1. a well-defined problem statement - OAI did and
> does not try to be everything to everybody. It is a
> one-trick pony allowing people to expose and harvest
> metadata.

I will go further and say that an enormous amount of the credit for
OAI's success must go to the specifications, which are contained in:
* a single document, which
* avoids abstractions, and
* is replete with examples
In stark contrast, someone coming to SRW/U has to read _a lot_ of
documentation, and understand a lot of abstractions. We are not too
bad on the examples, but we could do better.

My contention is that much of the perceived complexity, which requires
the multiplicity of documents, is down to SRW (as opposed to SRU). I
draw attention particularly to the affect that the WSDL file for SRW
requires SIX other schema files. Fine for computer scientists, not so
fine for software engineers, even less fine for decision-making
executives. If we focussed exclusively on the URL-based version of
our protocol, things would simplify remarkably. In particular, we
could then write a single document that avoids abstractions and is
replete with examples.

This is what lies behind the question I asked on Day Two of the ZING
Forum: "Why do we need both SRU and SRW?" I found it _very_ telling
that when I asked the follow-up question, "Who needs SRW?", _no-one_
was willing to step forward and say they are using it for anything. I
think Ralph's experiments with Beowulf-clustering ZING servers also
show pretty conclusively that the technical arguments in favour of SRU
are stronger than those for SRW.

(The only person who argued on Day Two that SRW should be retained was
Matthew. I do feel for him, as it has been his thankless task to
maintain the WSDL and schemas for all this time, and it must be hard
to imagine that work being discarded. Still and all, I don't think
that would be reason enough for the ZING initiative to keep carting
around baggage that no-one is actually using.)

So my modest-but-radical proposal is that we dump SRW completely, and
then simplify the documentation of SRU down as far as possible. Also,
we could then give SRU a nicer, non-TLA name, such as SearchURL.

I welcome discussion.

--

Second point -- organisational:

> "What can we do to make more people aware of the benefits of this
> search and retrieve protocol?" Some of the ideas included:
>
> * brand it
> * create five-minute Powerpoint show
> * create X profile
> * get grant funding
> * implement a conformance tester
> * make it a formal standard
> * make X more SRW/U services available
> * write "gentle" guides

The fourth of these, "get grant funding", is not really something to
do to make people aware of SRU; it's more of an enabler for the
others. It was I who raised this subject on Day One, due to the
furstration of being a small software house that has lots to give to
this kind of initiative, but no way to fund more involvement -- in
fact, I keep thinking I need to do _less_ on SRU rather than more.

Specifically, given a reasonable level of funding, Index Data people
including myself could do a pretty darned good job of making
presentations at conferences, creating profiles, implementing
conformance testers, raising running SRU services and writing "gentle
guide" documents -- I think we have the track record to prove that.
But we simply cannot plough the time and effort into these activities
that they demand when an organisation our size doesn't have the cash
slopping around to fund such things.

What SRU really needs is for a big, well-funded and highly visible
organisation (e.g. OCLC, ProQuest, Serial Solutions) to get right
behind it and start to invest a modest amount in making it happen. I
am pretty confident that if that happened, then people would step up
to the plate to offer their services in SRU evangelism (and, no, I
don't just mean Index Data people!)

Hope that's thought-provoking.

 _/|_ ___________________________________________________________________
/o ) \/ Mike Taylor <[log in to unmask]> http://www.miketaylor.org.uk
)_v__/\ "First fork() emulation and now select()? If we are not careful,
         in ten years or so NT/W2K/W2010 will be almost as useful as UNIX
         was in mid-1980s" -- Jarkko Hietaniemi.

--
Listen to free demos of soundtrack music for film, TV and radio
        http://www.pipedreaming.org.uk/soundtrack/

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager