RE: [search-ws] TAPIR

["LeVan,Ralph" <levan@oclc.org>]

I'd not seen it before.  I've printed off their document and will study
up on the subject.

At first glance, it's more about federated searching than local search
protocol, but the local protocol is important.  We could certainly talk
about Tapir being replaced with an SWS profile, but I doubt that that
community would be interested in making yet another change.  (Tapir
looks to be a recent successor to a pair of other protocols.)

More eventually.

Ralph

-----Original Message-----
From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov] 
Sent: Friday, November 09, 2007 9:40 AM
To: search-ws@lists.oasis-open.org
Subject: [search-ws] TAPIR

Are any of you familiar with the work that Ryan cites?

----- Original Message ----- 
From: "Ryan Scherle" <rscherle@INDIANA.EDU>
To: <ZNG@LISTSERV.LOC.GOV>
Sent: Wednesday, November 07, 2007 5:59 PM
Subject: Re: FW: [search-ws] Public Review of Search Web Services v1.0
Discussion Document


> Thanks for forwarding this, Ray.
>
> Now that I've moved into the biology community, I've become aware of
> the TAPIR search protocol (http://www.tdwg.org/activities/tapir/),
> which has much in common with SRU. I would love to see these two
> communities work together, and the SWS standardization process is a
> great time to see whether both can be merged into a single standard.
>
> I've started encouraging the TAPIR group to look at SRU, and I'll
> forward information about the Public Review to the TAPIR mailing list.
>
> I encourage SRU/SWS folks to look at the TAPIR specification to see
> whether any additional functionality would be useful for the SWS
> standard. One major difference is that TAPIR is database-oriented,
> while SRU is much more document-oriented. TAPIR allows client
> applications to specify a template for search responses, with the
> assumption that it is trivial to map between fields in a template and
> fields in the underlying database. I'm not sure whether there is an
> elegant way to reconcile the two models, but it's definitely worth
> some discussion.
>
> --- Ryan Scherle
>
>
> On Nov 7, 2007, at 3:27 PM, Ray Denenberg wrote:
>
> > ---------- Forwarded message ----------
> > Date: Wed, 7 Nov 2007 14:57:11 -0500
> > From: Mary McRae <mary.mcrae@oasis-open.org>
> > To: members@lists.oasis-open.org, tc-announce@lists.oasis-open.org
> > Cc: search-ws@lists.oasis-open.org
> > Subject: [search-ws] Public Review of Search Web Services v1.0
> > Discussion
> >     Document
> >
> > To OASIS members, Public Announce Lists:
> >
> > The OASIS Search Web Services TC has recently approved for public
> > review the
> > following Discussion Document:
> >
> > Search Web Services v1.0 Discussion Document
> >
> > This document: "Search Web Services Version 1.0  - Discussion
> > Document - 2
> > November 2007", was prepared by the OASIS Search Web Services TC as
a
> > strawman proposal, for public review, intended to generate
> > discussion and
> > interest. It has no official status; it is not a Committee Draft.
The
> > specification is based on the SRU (Search Retrieve via URL)
> > specification
> > which can be found at http://www.loc.gov/standards/sru/. It is
> > expected that
> > this standard, when published, will deviate from SRU. How much it
will
> > deviate cannot be predicted at this time. The fact that the SRU
> > spec is used
> > as a starting point for development should not be cause for concern
> > that
> > this might be an effort to rubberstamp or fasttrack SRU. The
> > committee hopes
> > to preserve the useful features of SRU, eliminate those that are not
> > considered useful, and add features that are not in SRU but are
> > considered
> > useful. The committee has decided to request OASIS to release this
> > as a
> > discussion document. Detailed review of this document is premature
> > at this
> > point and is not requested; feedback on the functionality and
> > approach is
> > solicited.  Feedback is requested by December 7.
> >
> > The public review starts today, 7 November 2007, and ends 7
> > December 2007.
> > This is an open invitation to comment. We strongly encourage
> > feedback from
> > potential users, developers and others, whether OASIS members or
> > not, for
> > the sake of improving the interoperability and quality of OASIS
> > work. Please
> > feel free to distribute this announcement within your organization
> > and to
> > other appropriate mail lists.
> >
> > More non-normative information about the specification and the
> > technical
> > committee may be found at the public home page of the TC at
> >
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=search-ws.
> > Comments may be submitted to the TC by any person through the use
> > of the
> > OASIS TC Comment Facility which can be located via the button
> > marked "Send A
> > Comment" at the top of that page, or directly at
> > http://www.oasis-open.org/committees/comments/index.php?
> > wg_abbrev=search-ws.
> >
> > Submitted comments (for this work as well as other works of that
> > TC) are
> > publicly archived and can be viewed at
> > http://lists.oasis-open.org/archives/search-ws-comment/. All
comments
> > submitted to OASIS are subject to the OASIS Feedback License, which
> > ensures
> > that the feedback you provide carries the same obligations at least
> > as the
> > obligations of the TC members.
> >
> > The specification document and related files are available here:
> >
> > Editable Source:
> > http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.doc
> >
> > PDF:
> > http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.pdf
> >
> > HTML:
> > http://docs.oasis-open.org/search-ws/v1.0/DiscussionDocument.html
> >
> >
> > OASIS and the Search Web Services TC welcome your comments.
> >
> >
> > ---------------------------------------------------
> > Mary P McRae
> > Manager of TC Administration, OASIS
> > email: mary.mcrae@oasis-open.org
> > web: www.oasis-open.org


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php