As you may have noticed, the web has evolved a set of common principles that are a mix of ratified standards and ad hoc practices. The notion of a Web Architecture was codified in a W3C technical report called “Architecture of the World Wide Web” http://www.w3.org/TR/2004/REC-webarch-20041215/ or simply ‘Web Architecture.’ Those projects and protocols that align with the ‘Web Architecture’ are more likely to be picked up and used than those that do not. As a result, the OAI Object Reuse and Exchange (ORE) project seeks to provide an infrastructure for web-based information systems that exploit and enhance the Web Architecture, and therefore overlay cleanly on the existing web.
In the past few months a new group has formed to tackle the problem of representing and exchanging complex digital objects in a web-based environment. I am proud to serve on the technical committee for this group and over the next few postings I’m aiming to introduce the library community to the work of the Open Archives Initiative Object Exchange and Reuse group and seek the feedback of the wisdom of this crowd.
Vision and Scope
Richard Rodgers presented this talk based on the work of he and MacKenzie Smith in the Digital Library Research Group at MIT. The original abstract of the presentation was:
Many questions are raised as previously unreachable digital content is found in and among new repositories–is each repository an island or a separately searchable resource? SIMILE (Semantic Interoperability of Metadata and Information in Unlike Environments) has developed an extensive ‘tool chain’ for gathering and manipulating data assets. Richard Rodgers and MacKenzie Smith, MIT, will demonstrate how tools developed by the SIMILE project can be used as powerful instruments for the federation, discovery, exploration, and curation of metadata.
Ron Murray (no relation) from the Library of Congress sent me this announcement about a joint NASA/Google partnership, which starts:
NASA Ames Research Center and Google have signed a Space Act Agreement that formally establishes a relationship to work together on a variety of challenging technical problems ranging from large-scale data management and massively distributed computing, to human-computer interfaces.
As the first in a series of joint collaborations, Google and Ames will focus on making the most useful of NASA’s information available on the Internet. Real-time weather visualization and forecasting, high-resolution 3-D maps of the moon and Mars, real-time tracking of the International Space Station and the space shuttle will be explored in the future.
Earlier this year, I was on a quest to hook a FEDORA content repository into the Sakai collaboration and learning environment. What looked at first to be a fairly easy integration turned out to be and I set the project aside for another time. Today brings word from Ian Boston of a JSR-170 implementation in Sakai:
On Friday, the Colorado Alliance of Research Libraries announced the creation of a consortium-wide digital repository project similar to that of the Ohio Digital Resource Commons.
Colorado Alliance Digital Repository Project Approved
The Board of Directors of the Colorado Alliance of Research Libraries has approved initial funding for a consortium-wide digital repository project at its October 19, 2006 meeting.
The Board of Directors of the Colorado Alliance of Research Libraries has approved initial funding for a consortium-wide digital repository project at its October 19, 2006 meeting. The project will use the Fedora open source software which was selected after a long evaluation process by the Institutional Repository Implementation Team, chaired by John Culshaw from the University of Colorado at Boulder.
I know I said I would only be taking “a day’s break” from posting about applying the Service Oriented Architecture pattern to library services but, well, real work gets in the way. Thoughts are still bubbling around — some of them have even reached draft form — but nothing new yet. In the meantime, though, take a look at this DLF Workshop on Developing a Services Framework for Digital Libraries to be held on Tuesday, November 07, 2006 in Boston. These sound like great outcomes:
OhioLINK was excited and privileged to participate in the second annual Google Summer of Code — a program to inspire young developers and provide students in Computer Science and related fields the opportunity to do work related to their academic pursuits during the summer, and to support existing open source projects and organizations. This is the first of three posts summarizing the efforts of three students; this one details the work of Juan Pablo Garcia Ortiz, a Ph.D. candidate at the University of Almeria in Spain, to build a JPEG2000 JPIP Streaming Server and Client Browser Viewer Applet. This is an edited version of his final report.
Some questions and observations that have come in through mechanisms other than blog comments on the analysis of the XTF/FEDORA integration. I’ve reproduced those here for the sake of completeness, but also be sure to go back to the first two entries in this series to read the comments there as well.
Indiana University’s Observations
As it turns out, Indiana University is considering much the same path. They have an existing FEDORA-based repository and a number of XTF projects that have been in development for a while. They, too, are looking to put these two technologies together and have a page on their project website with Digital Repository Architecture > Search”>IU’s observations of an XTF plus FEDORA (plus more!) combination.
This is a continuation of the investigation about integrating the California Digital Library’s XTF software into the FEDORA digital object repository that started earlier. This analysis looks at the textIndexer module in particular, starting with an overview of how textIndexer works now with filesystem-based objects and ending with an outline of how this could with reading objects from a FEDORA repository instead.
XTF’s Native File System handler
Natively, XTF wants to read content out of the file system. The core of the processing is done in these two class files: