ray denenberg rob sanderson “ key standards updates ” sru project briefing april 4, 2006;...

Ray Ray DenenbergDenenberg

Rob Rob SandersonSanderson

“Key Standards Updates”

SRU

Project Project BriefingBriefing

April 4, 2006; WashingtonApril 4, 2006; Washington

SRU Events Version 1.1 February 2004

Several Editorial Board Meetings

Implementors Meetings: June 2005, Chicago March 2006, The Hague

Results/Decisions

Results/Decisions Administrative

Name Changes Profiles/

Relationships OpenURL OAI OpenSearch

Standardization

Results/Decisions Administrative



Standardization

Technical Indexes (Context

Sets) Proximity Sort Extensions Diagnostics Parameters

(Results/Decisions Administrative



Standardization

Technical Indexes (Context

Sets) Proximity Sort Extensions Diagnostics Parameters

Name Name ChangesChanges

SRW SRU

Search Retrieve Web Search Retrieve Web ServiceService

Search Retrieve via URLSearch Retrieve via URL

SRW SRU SRU over SOAP


Formerly SRWFormerly SRW

SRU SRU over SOAP SRU POST



newnew

SRU SRU over SOAP SRU Post CQL Common Query Language

SRU SRU over SOAP SRU Post CQL Common Query Language

Contextual Query Language

Summary SRU SRU over SOAP SRU Post CQL Contextual Query Language


newnew

samesame

Context SetsContext Sets

What is a Context Set? For purposes of this discussion: a context set For purposes of this discussion: a context set

gives context to an index (a search access gives context to an index (a search access point); e.g:point); e.g:

dc.title = catdc.title = cat vs. vs. mods.title = catmods.title = cat

Proposed Context Sets MODS

MARC

OpenURL

mods mods.title=“Paradise Lost”

Marc marc.245$a = “Paradise Lost”

OpenURL openurl.btitle=“Paradise Lost”

MODS set For bibliographic searching. Indexes based on MODS.

MODS used for reference semantics. But does not presume that the data being

searched is MODS. Analogous to Z39.50 bib-1 and MARC.

Working group to be established.

MARC set

For searching on specific MARC fields, subfields, and substrings.

For users familiar and more comfortable with the MARC format, who prefer to formulate queries using MARC vocabulary.

OpenURL Context Set A set of indexes corresponding to

OpenURL keys, for book, journal, dissertation, patent, etc.

For resolvers: receive an openURL and wish to locate the desired item via SRU.

not intended for general bibliographic searching.

Proposed Context Sets: Resolution

Proposed Context Sets: Resolution

MODS

MARC

OpenURL

bib setbib set

profileprofile

Summary bib

bib.title=“Paradise Lost” Marc

marc.245$a = “Paradise Lost”

OpenURL Profile

OpenURL OpenURL ProfileProfile

OpenURL Profile will prescribe a mapping from bibliographic

indexes to OpenURL keys.


indexes to OpenURL keys. Hopefully will be taken on by the bib working group.


indexes to OpenURL keys. Hopefully will be taken on by the bib working group.

may also specify how an SRU response can facilitate the client process of formulating an OpenURL.

OpenURL Scenarios Scenario 1:

resolver receives OpenURL wants to formulate an SRU request

Scenario 2:

SRU client receives a record wants to create an OpenURL

Scenario 2 SRU client receives a record and wants to create an

OpenURL where the object described by that record is to be the referent.

Client requests the record for that item in the appropriate OpenURL schema -- for example:

Books: http://www.openurl.info/registry/docs/xsd/info:ofi/fmt:xml:xsd:book

Journals http://www.openurl.info/registry/docs/xsd/info:ofi/fmt:xml:xsd:journal

Then uses that record directly, to formulate an OpenURL request.

SRU Standardization

What to standardize? How?

What to Standardize: SRU CQL ZeeRex Scan

SRU: SRU itself SRU over SOAP (formerly SRW) SRU POST

CQL ZeeRex Scan

PhilosophyPhilosophy

Premise

“The world clearly needs a (single,) well-defined, powerful protocol for searching by URL with results returned in XML.”

-- Mike Taylor

The world needs a standard protocol for searching by URL with results returned in XML.

Competing protocols are being developed.

One of these will drive this standardization effort if SRU does not.

And if so, it won’t meet our needs.

And Therefore…. SRU needs to drive this effort.

It needs to involve the other interested communities.

In conclusion …..

Conclusion

SRU standardization needs to be in a mainstream standards body.

OASISOASIS

OASISOASISOrganization for the AdvancementOrganization for the Advancement

of Structured Information Standardsof Structured Information Standards

OASIS Founded 1993: “SGML Open”

5,000+ participantsrepresenting over 600+ organizations 100 countries

Produces Web services standards

More than any other organization. standards for security, e-business, and specific

applications.

OASIS Neutral ground for merging competing de facto

standards into an industry standard.

Lightweight process to: promote industry consensus unite disparate efforts.

OASIS Cycle public-list

Technical Committee

Standard

OASIS public-list process Discuss the formation of an OASIS

TC.

Develop a charter.

Technical Committee to Determine: Is there consensus across communities that a harmonized

standard would emerge from an OASIS TC; -- or

Are there intrinsic, insurmountable differences of opinion? Would other parties (A9 etc.) participate?

How much change will input from other parties introduce?

How long will it take to get to a committee draft? The version prior to public comment and a vote of all OASIS

members

OASIS Cycle

Public List About 3 months.

Technical Committee About 6 months.

Committee Draft to standard

About 3 months.

SRU Cycle Version 1.2

formalize the easy changes into SRU version 1.2.

Version 2.0 Take the more complex problems into the

standardization process.

Possible Standardization Sequence

OASIS Fast Track in NISO Fast Track in ISO

Thank you!Thank you!

Now Now Rob…..Rob…..

ray denenberg rob sanderson “ key standards updates ” sru project briefing april 4, 2006;...

Documents