|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 08:30-09:00 | Registration | |||||||||||||||||
| 09:00- 09:10 | Welcome and Introduction | |||||||||||||||||
| 09:10 - 10:50 | Presentations - Part 1: Context
|
|||||||||||||||||
| 10:50-11:15 | Break | |||||||||||||||||
| 11:15-12:55 | Presentations - Part 2: Integration
|
|||||||||||||||||
| 12:55 - 13:55 | Lunch | |||||||||||||||||
| 13:55 - 15:35 | Presentations - Part 3: Support
|
|||||||||||||||||
| 15:35-16:00 | Break | |||||||||||||||||
| 16:00-17:00 | Panel discussions: Panel Discussion 1: What can the SRU implementers group do to improve integration? Panel Discussion 2: What can the outside world do to improve integration with SRU? |
|||||||||||||||||
| 17:00-18:30 | DRINKS! | |||||||||||||||||
Specifications such as OpenSearch facilitate interoperability by providing
standardised syntax for
searching. But the higher goal of interoperability at the semantic level
further requires a common means of
expressing rich queries. CQL (the Common Query Language of SRU) provides
this.
The OpenURL Framework for Context-Sensitive Services has now been endorsed as a NISO standard (Z39.88-2004). This new standard has broadened the potential scope of OpenURL implementation beyond the scholarly information community, with the possibility of extension by registration of new formats and profiles for new domains, as well as the introduction of an XML format. Furthermore, the OpenURL Framework has separated the details of the reference and its context, known as the ContextObject, from the means of transporting it across the network, which is the OpenURL. This separation enables use of the ContextObject within other applications. For example, if a ContextObject were to be embedded in a web page other applications, such as web browser extensions (e.g. Openly's OpenURL Referrer), could provide extra functionality. This has led to the recent development of the COinS ('ContextObject in SPANs') specification, which embeds a ContextObject within an HTML `span' element.
The UK JISC Information Environment Service Registry (IESR) publicises
collections of resources along with details of how to access them in a
machine-readable format, aiming to assist applications such as
metasearch portals to serve their users' interests. The presentation will
describe the content of IESR, captured according to a standards-based
metadata application profile, and its possible position within the wider
information environment sharing resource descriptions. IESR encompasses
multiple service types, in both its resource descriptions and its own
access interfaces. Consequent service integration issues that have become
apparent during the experience of developing IESR will be discussed.
For integration of services we are investigating which services are useful to be integrated with the results of SRU searches. We also investigate how to formalize the description of the access to these services and which parameters are needed for access to those services.
The presentation will cover various aspects of SRU update, indicating its niche as an interactive protocol alongside other mechanisms such as the OAI PMH push mecahnism and batch loading. Interaction scenarios with SRU/SRW will be examined and the current development between OCLC and OCLC PICA will be covered.
Abstract: EIMS is a catalog for EPA work products, projects and data. Providing access to catalog records in an efficient and accessible fashion has required us to track emerging standards for web-based search and provide commonly accepted simple xml representations. OpenSearch, a9's evolving standard for describing simple searches, has fit into existing RSS work easily, but SRU and particularly CQL shows its z39.50 heritage by handling our requirements for multi-field search. We describe our experience implementing OpenSearch and ongoing work with SRU/Opensearch hybrids for internal search and CQL for public access. Google, Microsoft, Apple and Yahoo have recently defined 'Widgets' and we describe our thoughts on how these fit with SRU and OpenSearch.
Fundamental to the concept of Library 2.0 is the shift from delivery of library services solely within the library building, or via the library's own web site, towards the embedding of discrete library functions within a range of contexts. This presentation and demonstration will illustrate how providing library services using SRU and related technologies can sustain an ecosystem of new and innovative applications.
D+ is a software framework that brokers the searching of resources in distributed repositories. It is based on, and extends the open source SRW/U Server developed at OCLC. In addition, the server also acts as an 'OpenURL friendly' target by supporting queries conforming to version 0.1 of the OpenURL standard, rather than CQL. The presentation will demonstrate the use of both query types in the context of a resource list application using D+ as the search web service.
Metasearch (or parallel search, federated search, broadcast search, cross-database search) refers to concurrent search and retrieval spanning multiple databases, sources, platforms, protocols, and vendors. It generally requires users to know how to select, access, and search specific databases. Metasearch research is aimed at creating an environment that helps users find what they need while minimizing what they need to know. The NISO Metasearch Initiative has been charged with identifying/developing standards/best practices to improve interoperability between metasearch engines and content providers, and identifying a simple search/retrieve protocol to help database providers more effectively interoperate with metasearching applications. The NISO committee is developing the Metasearch XML Gateway, MXG, based on SRU and CQL.
There has been a lot of activity on WebServices and now Service Oriented Architectures over the last half decade. Both of these terms are not particularly well defined. WebServices might be SOAP based or REST based; the latest efforts to define Service Oriented Architectures from OASIS has a definition which could also describe CORBA and DCOM; REST itself is often vague as to its meaning (e.g. SRU whilst often described as REST is really only REST-Like!). Attempts such as the Web Service Interoperability Profile have attempted to rectify some of the interoperability issues surrounding Web Services (particularly in the Web Service Description Language), but there are still issues especially as you move higher up the Web Service stack (UDDI, WS-Addressing etc.). This presentation with attempt to describe what all these acronyms mean and which ones are "safe" or "risky" from an interoperability perspective.
|
July 24, 2007 |