NewtFire logo: a mosaic rendering of a firebelly newt
newtFire {dh|ds}
Maintained by: Elisa E. Beshero-Bondar (ebb8 at pitt.edu) Creative Commons License Last modified: Tuesday, 29-Aug-2017 13:30:31 UTC. Powered by firebellies.

Scenario and Goals

This assignment should give you more experience with writing well-formed XML, but of a different kind from our first exercise. You will design XML code to mark and store information in historical and cultural resources. Imagine yourself as a curator of historical letters by an author from a past century, building a digital resource that makes this author's personal letters available to read and search for interesting kinds of information. The kinds of information you choose to mark and collect are up to you, but think of the code you design for this assignment as the basis for coding many more letters writen by the same person.

Choosing a document, and coding it in <oXygen/>

Choose the text of one letter linked on one of the following websites (click through until you see a complete letter), and copy its text into a new XML document in <oXygen/>. Then, mark it up in well-formed XML, using your own system of tagging, as seems appropriate, to code the structure and the content of the document. Important: Save and name your XML document according to the File Conventions and be sure it as the proper .xml file extension before you upload to Courseweb!

Options:

Advice on writing the XML code

As with the first assignment, there is no single way to do this exercise, but we want you to think about how you nest levels of information (elements within elements), and the relationship between elements and attributes in XML.

Keep in mind as you code that you should not alter the base text of the file. Also, the line breaks and white spaces you can see when you copy and paste are not sufficient to preserve its structural features because XML will normalize these unless they are separated and marked in angle brackets. You will need to apply markup to indicate the basic structural components of the letter, for example, its dateline, greeting, body paragraphs, closer. We expect you to code more than that so that you are also collecting any information you find worth preserving as a curator: (For example, what kinds of information do you see in this letter that would be interesting to collect about, say, people, places, events from this author's life and times? Or what do you find interesting in this document to mark? Slang terms? Parts of speech? What looks interesting to you?) Your element and attribute names should be useful category markers, not simply reproducing the text of the letter but labelling its pieces in a way that helps identify particular kinds of information.

You can write XML comment tags to talk to us when we read your code. Write your own comments about decisions you are making in your code, and to leave us messages and questions: <!--ebb: Here is a sample comment tag -->.

When, where, and how to submit the assignment

Check and make sure you saved your file following our homework file naming rules, including giving it a .xml file extension. Submit your XML file on Courseweb, in the folder labelled “Upload Assignments Here”, before our next class.