CrossTech

OASIS has just announced a technical committee for standardising search services. This from the Call for Participation:

b. Purpose

To define Search and Retrieval Web Services, combining various current and
ongoing web service activities.

Within recent years there has been a growth in activity in the development of
web service definitions for search and retrieval applications. These include
SRU, a web service based in part on the NISO/ISO Search and Retrieval standards;
the Amazon OpenSearch, which defines a means of describing and automating search
web forms; as well as many proprietary definitions (e.g. the Google and MSN
Search APIs). There are also a number of activities for defining abstract search
APIs that can be mapped onto multiple implementations either within native code
or onto remote procedural calls and web services, such as ZOOM (Z39.50 Object
Oriented Model); SQI (Simple Query Interface), an IEEE standard developed for
searching and retrieval in the IMS (Instructional Management Systems) space; and
OSIDs (Open Service Interface Definitions from the Open Knowledge Initiative.
While abstract APIs would be out of scope, these would inform the work to
increase interoperability and compatibility.

Posted by Tony Hammond at 05:48 AM | Permalink | Comments (1)

Please see the details of the IDF Annual Meeting and a related Handle System Workshop in Washington, DC on June 21 which may be of interest - http://www.crossref.org/crweblog/2007/06/international_doi_foundation_a.html

Posted by Ed Pentz at 07:38 AM | Permalink | Comments (0)

Last week we had a second face-to-face of the OAI-ORE (Open Archives Initiative – Object Reuse and Exchange) Technical Committee in New York, the meeting being hosted courtesy of Google. (Hence the snap here taken from the terrace of Google's canteen with its gorgeous view of midtown Manhattan. And the food's not too shabby either. ;~)

The main input to the meeting was this discussion document: Compound Information Objects: The OAI-ORE Perspective. This document we feel has now reached a level of maturity that we wanted to share with a wider audience. We invite feedback either directly at ore@openarchives.org or indirectly via yours truly.

The document attempts to describe the problem domain - that of describing a scholarly publication as an aggregation of resources on the Web - and to put that squarely into the Web architecture context. What the initiative is seeking to provide is machine descriptions of those resources and their relationships, something that we are inclining to call "resource maps" and as underpinning we are making use of the notion of "named graphs" from ongoing semantic web research. Essentially these resource maps are machine-readable descriptions of participating resources (in a scholarly object - both core resources and related resources) and the relationships between those resources, the whole set of assertions about those resources being named (i.e. having a URI as identifier) and having provenance information attached, e.g. publisher, date of publication, version information (still under discussion). It is envisaged that these compound object descriptions may be available in a variety of serializations from a published, object-specific URL (i.e. a good old-fashioned Web address) but some honest-to-goodness XML serialization is a likely to be one of the candidates. No surprises here, then.

Below is a schematic from the paper which shows the publication of a resource map (or named graph) corresponding to the compound object which logically represents a scholarly publication. For those objects of immediate interest to CrossRef these would likely be identified with DOI's although there is no restriction in OAI-ORE on the identifier to be used - other than it be a URI.

Update: For a couple posts from some other members of the ORE TC see here (Peter Murray, OhioLINK) and here (Pete Johnston, Eduserv).

Posted by Tony Hammond at 06:03 AM | Permalink | Comments (0)