Draft Specifications of OAI Object Reuse and Exchange Now Available

ORE logoLast night, Herbert Van de Sompel announced the availability of the draft specifications and user guide for Object Reuse and Exchange (ORE). This effort, under the auspices of the Open Archives Initiative (OAI), seeks to define a standard for the description and exchange of aggregations of web resources.

Update to ‘Embedded Web Video in a Standards-Compliant, Accessible, and Successful Way’

With the release of Microsoft’s Windows Media Player version 11, the Microsoft Media Server (MMS) protocol is officially no longer supported. (Except, of course, for the confusing/amusing footnote on that page that says ‘mms://’ URIs are “highly recommended” as a protocol rollover URL — only Microsoft can at the same time make something deprecated and highly recommended.) As Ryan Eby noted earlier this year, those generating ASX files for Windows Media Player need to adjust their scripts.

Working With the Web Architecture

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.

Embedded Web Video in a Standards-Compliant, Accessible, and Successful Way

The word “Successful” in the title, when juxtaposed with “Standards-Compliant” and “Accessible,” should be big, bold and flashing (except that the flashing style would then go against web accessibility best practice). The goal is to embed a video clip into a web page that validates as “XHTML4.01 Transitional”, includes a Closed Captioning text track to be displayed in the web page, and could be viewed in one of three flavors: Windows Media, QuickTime, and Real. And the content being presented is about using accessible technologies in the classroom, so it had to be “right.” This task was much harder than I thought, and I’ll offer much harder than it should have been. Piecing together sources too numerous to mention, I managed to make it happen … with just a few caveats. Here, documented for all time, or at least until dltj.org goes away or the next major browser/streaming-client revision (which ever comes first) is how it can be done.