Brian Hancock and Michael J. Giarlo
The delivery of documents on the Web has moved beyond the restrictions of the traditional Web markup language, HTML. HTML’s static tags cannot deal with the variety of data…
Abstract
The delivery of documents on the Web has moved beyond the restrictions of the traditional Web markup language, HTML. HTML’s static tags cannot deal with the variety of data formats now beginning to be exchanged between various entities, whether corporate or institutional. XML solves many of the problems by allowing arbitrary tags, which describe the content for a particular audience or group. At the Center for Electronic Texts in the Humanities the Latin texts of Lector Longinquus are being transformed to XML in readiness for the expected new standard. To allow existing browsers to render these texts, a Java program is used to transform the XML to HTML on the fly.
Details
Keywords
Antonio Barrera, Parmit Chilana, Kevin Clarke and Michael Giarlo
To report on the 2007 Code4Lib conference held February 27‐March 2nd in Athens Georgia.
Abstract
Purpose
To report on the 2007 Code4Lib conference held February 27‐March 2nd in Athens Georgia.
Design/methodology/approach
Provides a review of the conference and some background on the Code4Lib community.
Findings
The Code4Lib conference is developed by the open Code4Lib community. The single track program included a pre‐conference, keynote sessions, scheduled presentations, lighting talks, and breakout sessions.
Originality/value
A conference report reviewing some of the trends in development, within libraries which should appeal to programmers and management alike.
Details
Keywords
Now that XML is five years old, is it time for e‐libraries to start exploiting its full potential by delivering it to the end user rather than converting it to HTML first? What…
Abstract
Now that XML is five years old, is it time for e‐libraries to start exploiting its full potential by delivering it to the end user rather than converting it to HTML first? What, if any, would be the advantages to users and providers? Could browsers cope? And is it worth the bother?
Details
Keywords
It was not love at first sight when I met my first markup language sometime in the 1980s. But XML is different. It has a rich and flexible tag‐set that lets it function as a…
Abstract
It was not love at first sight when I met my first markup language sometime in the 1980s. But XML is different. It has a rich and flexible tag‐set that lets it function as a database. It is also starting to have tools that allow Web‐based display with standard browsers. Describing XML is not easy, but four aspects seem particularly important: separation of data; tool development; standards; and preservation.