This is a straightforward thing for people who know what they are doing. It is only a reminder to me, who didn’t.
The journals I publish using TEI XML use the tei:figDesc element to populate the alt and title attributes of html:img.
Until today, these results in very odd looking tool tips, where the text was spread all over the place, e.g.
The problem was being caused by the OxygenXML editor’s pretty-print feature and how that was being transformed to the title and alt attributes. Read the rest of this entry »
A great statement today in Slate by Siva Vaidhyanathan about the value of public research:
We Americans take these institutions for granted. We assume that private enterprise generates what is so casually called “innovation” all by itself. It does not. The Web browser you are using to read this essay was invented at the University of Illinois at Urbana-Champaign. The code that makes this page possible was invented at a publicly funded academic research center in Switzerland. That search engine you use many times a day, Google, was made possible by a grant from the National Science Foundation to support Stanford University. You didn’t get polio in your youth because of research done in the early 1950s at Case Western Reserve. California wine is better because of the University of California at Davis. Hollywood movies are better because of UCLA. And your milk was not spoiled this morning because of work done at the University of Wisconsin at Madison.
These things did not just happen because someone saw a market opportunity and investors and inventors rushed off to meet it. That’s what happens in business-school textbooks. In the real world, we roll along, healthy and strong, in the richest nation in the world because some very wise people decided decades ago to invest in institutions that serve no obvious short-term purpose. The results of the work we do can take decades to matter—if at all. Most of what we do fails. Some succeeds. The system is terribly inefficient. And it’s supposed to be that way.
Along the way, we share some time and energy with brilliant and ambitious young people from around the world.
Important to realise this is also a selective list. Other things generated in whole or in part by publicly funded researchers and institutions include Unicode and XML.
Can anybody think of others?
We are trying to build a single stylesheet to work with the documents of two independent journals. In order to get a sense of the work involved, we wanted to create a catalogue of all elements used in the published articles. This means loading as input document directories’ worth of files and then going through extracting and sorting the elements across all the input documents.
Here’s the stylesheet that did it for us. It is probably not maximally optimised, but it currently does what we need.
<app>element is used to group together readings that constitute a textual variation. The element has three children: Read the rest of this entry »
- model.pPartTranscriptional Read the rest of this entry »
First posted December 15, 2006 http://people.uleth.ca/~daniel.odonnell/Research/disciplinary-impact-and-technological-obsolescence-in-digital-medieval-studies. Published in The Blackwell Companion to the Digital Humanities, ed. Susan Schriebman and Ray Siemens. 2007.
In May 2004, I attended a lecture by Elizabeth Solopova at a workshop at the University of Calgary on the past and present of digital editions of medieval works1. The lecture looked at various approaches to the digitisation of medieval literary texts and discussed a representative sample of the most significant digital editions of English medieval works then available: the Wife of Bath’s Prologue from the Canterbury Tales Project (Robinson and Blake 1996), Murray McGillivray’s Book of the Duchess (McGillivray 1997), Kevin Kiernan’s Electronic Beowulf (Kiernan 1999), and the first volume of the Piers Plowman Electronic Archive (Adams et al. 2000). Solopova herself is an experienced digital scholar and the editions she was discussing had been produced by several of the most prominent digital editors then active. The result was a master class in humanities computing: an in-depth look at mark-up, imaging, navigation and interface design, and editorial practice in four exemplary editions.