text:
60 years ago
The "Roll-in-Rink" is open again after being closed for a month for repair and re-decoration. Owner Jerry Hett reports the rink is open each Thursday and Sunday evening.
Marion High School's presentation of "Fog in the Valley" received a highly superior rating Thursday at the annual CVL play festival held at Florence High School. Members of cast are Theodora Longhofer, Michael Brodhead, Shirley Tiemeier, Dwight Fruechting, Jay Fisher, and Anita Collett. The play will be entered in the district meet in March.
Earl Priebe, manager of the Marion J.C. Penney store, announced last week that he had sent his resignation to the company for reasons of health. New manager, W.A. King, arrived this week to take over operation of the store.
A wedding of wide interest was held Jan. 25 at St. John's Lutheran Church, Tampa, when Miss Edna Rhode, daughter of Mr. and Mrs. Wm. Rhode, became the bride of Paul Backhus, son of Mr. and Mrs. Wm. Backus, Hope.
The whole Marion community received one of its deepest shocks in recent years at the word of the death Sunday night of Alvin Propp, popular young manager of Marion Equipment Company. His death is a severe blow and loss to the community, as well as a grievous loss to family and friends. He was 43 years of age.


text:
As problems go, It grows every time you turn around. Just how are you going to deal with all of these new devices? Suddenly everything is internet ready and your site has to accommodate them all. Figuring out how to deal with Netscape and IE were nothing compared to what is coming up. People will soon be viewing your site with a text browser that only show 6 lines at a time. Forget graphics. Your site has to be reduced to the basics. Html is not good for these new browsers so you have to learn a new markup language. When web services and SOAP become mainstream you may not be presenting your data in a browser at all. The worst part is that you have to write all of these So, how do you support all of these new devices, manage to keep your data consistent and actually keep your sanity?
One of your largest problems is html. Html is is presentation oriented. When you write html the focus is on how the page will look. The actual data in the page is secondary to the layout. There are now many tools to help make web pages look nice but they do not help make sense of the data contained in the pages.
XML, in contrast, is data oriented. When you create an XML document you focus on what the data is without concern for layout or presentation. Once you have the data and its structure down, you then write stylesheets and focus on how the data will be presented. The great thing about this approach is that you can present the same data in different ways. XML can greatly reduce the amount of work you need to do ensure that your data stays consistent no matter what media your users are using. This may not be particularly useful for your home page but it can do amazing things to help manage volumes of company data, documentation, contacts, schedules or orders.
This tutorial will guide you through setting up Tomcat and Cocoon to serve XML pages, then you will create a DTD, XML file and three XSL stylesheets so that you can view your data in your desktop browser, a cell phone browser and a pdf file. Before getting started you should be warned that writing pages in XML requires more time up front than HTML. By the end of the tutorial you will see the value in taking the extra time.
At the end of this tutorial you will have:
1. Installed and configured Tomcat to serve up xml documents
2. Installed Cocoon to process xml documents and format it according to your xsl documents.
3. Created a dtd to define the structure of you xml document.
4. Created an xml document containing an address book entry.
5. Created three xsl files to format the xml document in HTML,WML and pdf formats
{mospagebreak title=Getting the tools} If you do not already have java installed you will need jdk 1.1 or higher. You can get the Linux jdk from http://blackdown.org
For this tutorial you will need:
Tomcat 3.2.1
For this tutorial we will use the binary build. Get it at http://jakarta.apache.org/site/binindex.html. In a production environment you would also want to download the Apache web server and configure Apache and Tomcat to work together. In the interest of keeping this tutorial a reasonable length we will not be configuring Tomcat and Apache to work together. So you will be accessing Tomcat directly using port 8080 instead of the usual port 80. If you want to configure Apache to pass requests on to Tomcat see the documentation at the jakarta web site.
UP SDK from phone.com (now openware.com)
Unfortunately you must register before downloading the sdk and it only works on Windows. If you are going through this tutorial in Linux you will need another Windows machine to use the phone browser. Get it at http://www.phone.com/products/index.html
{mospagebreak title=Installing Tomcat} Tomcat is the Apache Group's Java Servlet and JavaServer Page server. We need Tomcat for the Cocoon servlet to run.
Installing Tomcat is straight forward: all you need to do is unpack the file you downloaded, set JAVA_HOME and TOMCAT_HOME variables and start Tomcat.
The first step is to unpack Tomcat:
$ cd /usr/local/ $ gunzip jakarta-tomcat-3.2.1.tar.gz $ tar -xvf jakarta-tomcat-3.2.1.tar
Then set up your environment:
$ JAVA_HOME=/path/to/jdk $ TOMCAT_HOME=/usr/local/jakarta-tomcat-3.2.1 $ export TOMCAT_HOME JAVA_HOME
You can add these lines to the file $TOMCAT_HOME/bin/tomcat.sh just above the first 'if' statement if you do not feel like setting these variable everytime.
That is all you need to do, Tomcat is ready to run. To start Tomcat cd to $TOMCAT_HOME/bin
and run:
$ ./startup.sh
After a few moments you should see two lines that look like this:
2001-01-26 12:25:02 - PoolTcpConnector: Starting HttpConnectionHandler on 8080 2001-01-26 12:25:02 - PoolTcpConnector: Starting Ajp12ConnectionHandler on 8007
When you see these line Tomcat is running and ready to serve. Open up a browser
and go to http://localhost:8080 and run a couple samples to make sure that Tomcat
is working properly. Run at least one servlet and one jsp sample. If you get any
errors check your environment and restart Tomcat.
{mospagebreak title=Installing Cocoon} Cocoon is Apache's XML publishing engine. Cocoon will read your xml file and format it according to the layout defined in your XSL files. The Cocoon distribution includes the cocoon.jar file and a set of jar files that help cocoon read and format xml files. Installing Cocoon is not much more complicated than installing Tomcat. You need to copy all of the jar files to a place where Tomcat knows to find them and update Tomcat's configuration.
First unpack Cocoon and change to the Cocoon directory:
$ tar -xzf Cocoon-1.8.2.tar.gz $ cd cocoon-1.8.2
Next copy all of the jar files in lib/ to $TOMCAT_HOME/lib
$ cp lib/*.jar $TOMCAT_HOME/lib $ cp bin/cocoon.jar $TOMCAT_HOME/lib
Tomcat 3.2.1 will automatically load all of the jar files found in $TOMCAT_HOME/lib so you do not have to add these to your CLASSPATH. However, if you are using java 1.2 or higher you will also need to add $JAVA_HOME/lib/tools.jar to your CLASSPATH. Cocoon uses tools.jar for page compilation. If you do not want to add tools.jar to your profile add this line to $TOMCAT_HOME/bin/tomcat.sh:
export CLASSPATH=$CLASSPATH:$JAVA_HOME/lib/tools.jar
The next step is to add a Context for Cocoon to Tomcat's server.xml file. This tells Tomcat to create a context for Cocoon. It also tells Tomcat where to find the cocoon files and what url path cocoon should be launched from. Change to $TOMCAT_HOME/conf and use an editor to open server.xml
At the bottom of the file you will see this tag </ContextManager>. Above that
tag add these two lines:
<Context path="/cocoon" docBase="webapps/cocoon" debug="0" reloadable="true"> </Context>
This tells Tomcat to create a context for cocoon with the path /cocoon. Whenever
/cocoon is called Tomcat will look for the files in $TOMCAT_HOME/webapps/cocoon.
Of course at this point there is no webapps/cocoon directory so let's create that
$ mkdir $TOMCAT_HOME/webapps/cocoon $ mkdir $TOMCAT_HOME/webapps/cocoon/WEB-INF
The WEB-INF directory is part of the servlet 2.2 specification. According to the specification the WEB-INF directory should contain a file called web.xml which defines your servlets and any parameters the serlvets need. Most servlet engines will not strictly enforce these standards but trying to work around it will usually give you more headaches than solutions.
The next step is to copy the cocoon web.xml file and cocoon.properties files
to your WEB-INF directory and copy the sample files to the webapps directory.
$ cd /path/to/cocoon-1.8 $ cp src/WEB-INF/web.xml $TOMCAT_HOME/webapps/cocoon/WEB-INF/ $ cp conf/cocoon.properties $TOMCAT_HOME/webapps/cocoon/WEB-INF/ $ cp -R samples/ $TOMCAT_HOME/webapps/cocoon/samples
The last thing you need to do is edit the web.xml file you just copied. Open
$TOMCAT_HOME/webapps/cocoon/WEB-INF/web.xml in an editor. You will see the line:
Change it to:
Now stop and start Tomcat.
$ $TOMCAT_HOME/bin/shutdown.sh $ $TOMCAT_HOME/bin/startup.sh
While Tomcat is loading you will see:
2001-01-26 01:35:04 - ContextManager: Adding context Ctx( /cocoon )
If you see this then everything is good. Open a browser and go to http://localhost:8080/cocoon
and try some of the samples. Not all of the samples are meant to be viewed in
a browser so don't worry if you get errors with some of them. If you can see hello-page.xml
then everything is working.
{mospagebreak title=Defining your document} Your server environment is ready to go. Now we can actually start creating xml files. The first step is to create a Document Type Definition (dtd). The dtd tells the xml parser what information is allowed in the xml file and defines the format of the data. If the xml file does not fit into the constraints of the dtd the xml parser will give you an error and stop parsing the document. In our example we are creating a 'contact' element which has a name, address, phone number and email address. The dtd will define which tags must be part of a contact element and what kind of data will be in each tag.
It is not actually necessary to create a dtd for such a simple xml file, but it is important to use dtds when you are creating more sophisticated documents. Advantages of using dtds are that they ensure that your xml files are valid and well-formed and that you have all of the required data in the document. Using dtds also helps create standardization. Once you have created a dtd for a 'contact' it can be used in any place where contact information is required. This helps ensure that your data is consistent through out the company. Dtds also make it easier to communicate your data structures to others. If someone wants to interact with your applications or web site, for example, you could use dtds to show them your data structures.
To create your dtd, change directories to $TOMCAT_HOME/webapps/cocoon and create a directory called 'address'. Then change directories to address, create a file called contact.dtd and open it up in a text editor
The first step is to define you root element:
<!ELEMENT contact (name,address,phone,e-mail)>
In the line above we defined an element called contact which contains the elements name, address, phone and e-mail. Any time we use this dtd we must have a contact element which contains all of the child elements.
Next we will define the name element:
<!ELEMENT name (first-name,last-name)> <!ELEMENT first-name (#PCDATA)> <!ELEMENT last-name (#PCDATA)>
The first line defines the name element as containing first-name and last-name elements. The next two lines define first-name and last-name elements as text elements.
Following the same logic we can fill in the address, phone and e-mail elements.
<!ELEMENT address (street,city,state,country)> <!ELEMENT street (#PCDATA)> <!ELEMENT city (#PCDATA)> <!ELEMENT state (#PCDATA)> <!ELEMENT country (#PCDATA)> <!ELEMENT phone (#PCDATA)> <!ELEMENT e-mail (#PCDATA)>
The entire dtd looks like this:
 <!ELEMENT contact (name,address,phone,e-mail)> <!ELEMENT name (first-name,last-name)> <!ELEMENT first-name (#PCDATA)> <!ELEMENT last-name (#PCDATA)> <!ELEMENT address (street,city,state,country)> <!ELEMENT street (#PCDATA)> <!ELEMENT city (#PCDATA)> <!ELEMENT state (#PCDATA)> <!ELEMENT country (#PCDATA)> <!ELEMENT phone (#PCDATA)> <!ELEMENT e-mail (#PCDATA)>
{mospagebreak title=Creating your xml file} Now that we know what our data should look like we create the xml file. According to the dtd our xml file must contain all of these elements in (more or less) this structure:
<contact> <name> <first-name></first-name> <last-name></last-name> </name> <address> <street></street> <city></city> <state></state> <country></country> </address> <phone></phone> <e-mail></e-mail> </contact>
To begin create a file called homer.xml and open it in a text editor. The first
line of the xml file is the XML declaration:
<?xml version="1.0"?>
Every xml and xsl document should begin with the XML declaration. This declares that this is an xml document and which version of xml you are using.
Tags of the form <?…?> are processing instructions (PI). Processing instructions are instructions that are passed to the application that will be using the xml document. The first word after the <? is called the target which is the application that the instructions will be passed to. The rest of the PI contains the instructions to be passed to the target. In this case the target is the xml application and we are telling it that we are using xml version 1.0.
The next is our document type declaration. This is where we associate our xml
file with the dtd we created. All declarations use the tag <!…>. The document
type declaration looks like:
<!DOCTYPE contact SYSTEM "contact.dtd">
Next we want to add a PI for cocoon so that Cocoon knows that we want it to perform
stylesheet transformations for us:
<?cocoon-process type="xslt"?>
Finally we can populate our file with data. At this point filling in the data is pretty simple, just add data values between the tags:
<contact> <name> <first-name>Homer</first-name> <last-name>Simpson</last-name> </name> <address> <street>122 West 1st Avenue</street> <city>Springfield</city> <state>ZZ</state> <country>USA</country> </address> <phone>1-555-555-1111</phone> <e-mail>firstname.lastname@example.com</e-mail> </contact>
With properly defined dtds and an xml template filling in data should be a relatively painless task.{mospagebreak title=Viewing your document in an HTML browser} We now have our xml file and a dtd to verify the validity of the document. You could view the xml file in an HTML browser but it would be quite uninteresting. The browser will load the xml file exactly as it appears in the text file. Your data will be presented correctly but users will want it to be more readable. Our next step is to create a stylesheet that contains HTML formatting information so that you can view the xml document as an html document.
To begin create a file called 'address-html.xsl' and open it using a text editor.
As always the first line of the file is:
<?xml version="1.0"?> Next we declare our document element and namespace by adding this line: <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
The first part of the tag (xsl:stylesheet) is called the document element. Basically
it tells the xml processor that the following document is an xsl:stylesheet. To
close the document element we must end our document with:
All data in the document must be enclosed within these tags.
The next part of the tag (xmlns:xsl="http://www.w3.org/1999/XSL/Transform") declares
the namespace. XMLNamespaces (xmlns) are used to provide a way for the xml parser
to make sense out of colliding vocabularies. Trying to create a namespace that
is guaranteed to be unique in any and every context would be impossible. Without
xmlns it is likely that your tags will collide with other tags at some point.
For example suppose in our contact book we wanted to add the contact's job title.
To do this we would add:
<title>Nuclear Technician</title>
to our xml file and update the dtd. We now have a problem because HTML also uses the tags <title> </title> but it means something totally different. The XMLNamespace is used to sort out which tags are which. As an aside, the link ("http://www.w3.org/1999/XSL/Transform) does not actually point to anything.
Next we create our first xsl template. A template is a set of instructions and literal results that are executed when certain conditions are met by the processor. The first template we will create lays out the HTML page:
<xsl:template match="contact">   <title> <xsl:value-of select="name/last-name"/> <xsl:text>, </xsl:text> <xsl:value-of select="name/first-name"/> </title>   <xsl:apply-templates/>   </xsl:template>
The match="contact" attribute of the template tag tells the processor to use the following template when it comes across a contact element.
The statement <xsl:value-of select=" "> is where we actually select data from the xml document. In this case we select name/last-name, name/first-name and use that for the title of page. You must also use <xsl:text> some text </xsl:text> where you want regular text in the HTML. With this template the title of the page will be "Simpson, Homer". Otherwise the template contains standard HTML that will layout the page. In the body of the HTML page we use xsl:apply-templates to tell the processor to apply the templates for the other elements of the xml document.
To fill in the body of the html document we will create templates for each of the elements of the xml document.
<xsl:template match="name">
 <xsl:apply-templates/>
 </xsl:template> Matches the name elements and formats the name with an h1 tag. <xsl:template match="address"> <xsl:text>Address: </xsl:text>
 <xsl:value-of select="street"/>
 <xsl:value-of select="city"/>
 <xsl:value-of select="state"/>
 <xsl:value-of select="country"/>
 </xsl:template>
This simply matches the address element and prints out each address element line
by line.
<xsl:template match="phone">
 <xsl:text>Phone number: </xsl:text> <xsl:apply-templates/> </xsl:template> <xsl:template match="e-mail">
 <xsl:text>Email: </xsl:text>  <xsl:attribute name="href"> <xsl:text>mailto:</xsl:text><xsl:apply-templates/> </xsl:attribute> <xsl:apply-templates/>  </xsl:template>
The last two templates match phone and e-mail and print the data out. For each element we grab the data, add some text and add it to the result tree. In the template that matches e-mail we also add html formatting to add a mailto: link to the e-mail address. The user only has to click on the email address link to create an email addressed to the contact. Since this page will be viewed in a web browser it seems likely that the user will want to send an email to the contact so why not make is easier?
Now that we have an xml and xsl document we need to tell the xml document to
use the xsl stylesheet. To do this open up homer.xml in a browser and add the
following processing instruction under the cocoon-process PI (<?cocoon-process
<?xml-stylesheet href="address-html.xsl? type="text/xsl"?>
Everything is ready for viewing your first xml/xsl page in a browser. If tomcat is not running start it up and point your browser to the following URL:
If you see any Cocoon errors read it carefully. The error messages are generally quite good at telling you what is wrong. Xml is much more strict than html. Among other things case if followed strictly and all tags must be properly terminated. If you have xml syntax problems, Cocoon will usually tell you what is wrong.
{mospagebreak title=Viewing your document in a WAP browser} One of the key features of xml is that you can view the same data in a variety of formats. Once you have created a contact book wouldn't it be nice to be able to use the same contact book whenever and wherever you need to look up a contact? Rather than writing conversion tools to reformat your contact for each media you can use different stylesheets on the same data.
As the use of web enabled cell phone and PDAs grows this approach can save you a lot of headaches. The standard for cell phone browsers is (for better or worse) wireless markup language (wml). We want to make our contact accessible from a cell phone browser. To do this we must now create a stylesheet for wml browsers. Create a file called 'address-wml.xsl' and open it in an editor.
The xsl instructions are essentially the same but we are now using wml constructs.
The top of the stylesheet adds a processing-instruction for the type text/wml
so the wml can be interpreted and formatted.
<?xml version="1.0"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="contact"> <xsl:processing-instruction name="cocoon-format"> type="text/wml" </xsl:processing-instruction>
The body is a mix of xsl and wml instead of html but is quite similar otherwise. Because users will be viewing this page on a cell phone browser we should rethink the presentation of the data. Taking the small screen and intended use of the page into consideration the first page will only show the name and phone number. If the cell phone user wants more contact information there is a link to the full contact info.
<wml> <card id="index" title="Your Contacts">
 Phone Book

 </card> <card id="contact" title="Phone Book">
 <xsl:value-of select="name/first-name"/> <xsl:text> </xsl:text> <xsl:value-of select="name/last-name"/>
 <xsl:value-of select="phone"/> <do type="accept" label="More"> <go href="#Address"/> </do>
 </card> <card id="Address" title="address">
  <xsl:value-of select="name/first-name"/> <xsl:text> </xsl:text> <xsl:value-of select="name/last-name"/>
 <xsl:value-of select="address/street"/>
 <xsl:value-of select="address/city"/>
 <xsl:value-of select="address/state"/>
 <xsl:value-of select="address/country"/>
 Main <do type="prev"> <prev/> </do>
 </card> </wml> </xsl:template> </xsl:stylesheet>
As with the html stylesheet you need to tell the xml processor to use addres-wml.xsl
when a phone browser accesses the page. To do this open up homer.xml in an editor
and add the following line:
<?xml-stylesheet href="address-wml.xsl? type="text/xsl? media="wap"?>
Simply put, this line tells cocoon to use address-wml.xsl for formatting instructions when the media requesting the page is a wap browser.
Open up your phone.com browser and point it to the same URL you used to view the html page.
The data is the same but we have changed the document layout to make it more
useful in a cell phone browser. We do not have all of the information in one page.
Instead the first page shows the contacts name and phone number only. Assuming
that a cell phone user is most likely to look up a phone number lets show the
phone number first and not clutter up the small screen.
{mospagebreak title=Viewing your file as a pdf} The last thing we do in this tutorial is convert the xml to a pdf file. Creating a pdf file is great when your users might want to keep or print a copy of the data. Since pdfs are not editable they are a great way to provide users with a document that they will not be able to accidentally (or purposely) modify later.
For pdf generation we will use FOP from Apache. FOP takes in an xml document,
an FO stylesheet and outputs a pdf. FOP is actually a separate project from cocoon
but the FOP jar is included in the cocoon distribution so you do not need to add
anything new to the project. There are a lot of similarities with html or wml
stylesheets but you will notice that the formatting is much more specific. You
need to create a file called address-pdf.xsl and open it in a text browser. Begin
the file with the usual xsl:stylesheet PI but you also need to say that you will
be using the xml namespaces for xml and fo:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
Use an xsl template to match the contact item and add a processing-instruction for the type text/xslfo.
<xsl:template match="contact"> <xsl:processing-instruction name="cocoon-format"> type="text/xslfo"</xsl:processing-instruction>
For any fo file you first need an fo:root element. The fo:root element is essentially
the same as the root xsl:template. It defines page layouts, page sequences and
host of optional text formatting instructions.
<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
Every fo:root must have one fo:layout-master-set. The fo:layout-master-set defines
the layout specification including page margins.
<fo:layout-master-set> <fo:simple-page-master page-master-name="single" margin-top="2cm" margin-bottom="2cm" margin-left="2.5cm" margin-right="2.5cm"> <fo:region-body margin-bottom="3cm"/> <fo:region-after extent="1.5cm"/> </fo:simple-page-master> </fo:layout-master-set>
Next add an fo:page-sequence to define how to create the pages within the document.
Your entire document can be within one fo:page-sequence or you can use different
page-sequence for sections.
<fo:page-sequence> <fo:sequence-specification> <fo:sequence-specifier-alternating page-master-first="single" page-master-odd="single" page-master-even="single"/> </fo:sequence-specification>
Next you need to add fo:flow to output the text. In our file we are applying
the templates from the xml result tree.
<fo:flow> <xsl:apply-templates/> </fo:flow> </fo:page-sequence> Close the fo:root and xsl:template </fo:root> </xsl:template>
Finally we create xsl:templates for the elements of our contact item. In each
template we have an fo:block which is used to define font, font size, alignment,
<xsl:template match="name"> <fo:block font-size="12pt" text-align="justified"> <xsl:apply-templates/> </fo:block> </xsl:template> <xsl:template match="address"> <fo:block font-size="12pt" text-align="justified"> <xsl:apply-templates/> </fo:block> </xsl:template> <xsl:template match="phone"> <fo:block font-size="12pt" text-align-last="justified"> <xsl:apply-templates/> </fo:block> </xsl:template> <xsl:template match="e-mail"> <fo:block font-size="12pt" space-before.optimum="12pt" text-align="justified"> <xsl:apply-templates/> </fo:block> </xsl:template> </xsl:stylesheet>
You will notice that the xsl syntax is similar to previous xml files but with
fo formatting instruction. Now all that needs to be done is to tell your xml file
to use address-pdf.xsl. For simplicity open homer.xml and replace:
<?xml-stylesheet href="address-html.xsl" type="text/xsl"?>
<?xml-stylesheet href="address-pdf.xsl" type="text/xsl"?>
It is possible to have both the pdf and html file generated at the same time and have the pdf downloaded from a link in the html page but it is not a straight forward as you might think. I will save that for another day. All that is left for you now is to point your browser to http://localhost:8080/address/homer.xml. If you have an Acrobat plugin the pdf should load automatically. If you do not have a plugin you should be prompted to download the file. Once downloaded open Acrobat to view the file.
That covers this tutorial. If everything has gone well you have a good idea of
how powerful xml can be. Hopefully it can help you manage your data and make your
life a little easier

subset: commoncrawl


text:
Project Team
Principal Investigator: Deborah McGrady
Principal Investigator: Benjamin Albritton, Abstract
Research Assistant: Elizabeth Erickson, Abstract
Research Assistant: Rachel Geer, Abstract
Symposium Schedule - April 2013
Participating Scholars
Jennifer Bain, Associate Professor of Music Theory at Dalhousie University, has published numerous articles on the music of Guillaume de Machaut, as well as on chant and on the reception of the music of Hildegard of Bingen in book collections, The New Catholic Encyclopedia, and in various musicology journals. She recently edited a special early music issue of the Journal of Music Theory, and has co-edited a forthcoming collection of essays on Guillaume de Machaut with Deborah McGrady (Brill).
Maureen Boulton, Professor of French (University of Notre Dame), is interested in the relation between narrative and lyric poetry and in religious literature. She has published two editions, The Song in the Story a study of lyric insertions, and collaborated with Ruth Dean on Anglo-Norman Literature. A Guide to Texts and Manuscripts. She is currently completing Piety and Persecutions (translations of Anglo-Norman texts for The French of England in Translation), and Pious Fictions a study of vernacular lives of Christ.
Mark Cruse is Associate Professor of French at Arizona State University. His research focuses on the relationship between literature, material culture, and performance in Francophone realms from the twelfth to fifteenth centuries. He has published in Gesta, Studies in Iconography, and The Senses and Society on subjects including heraldry, writing tablets, and theater manuscripts. His book Illuminating the Roman d'Alexandre (Oxford, Bodleian Library, MS Bodley 264): The Manuscript as Monument will be published by Boydell and Brewer in fall 2011.
Lawrence Earp is professor of music at the University of Wisconsin-Madison. He is the author of Guillaume de Machaut: A Guide to Research (1995). His published articles have focused on music in late medieval France and the reception of medieval music. Current projects include an introduction to a planned facsimile edition of the Ferrell-Vogüé Machaut manuscript.
Domenic Leo presently teaches art history at Youngstown State University. He holds degrees in French and Linguistics from Georgetown University, a Royal Diploma from Christie's, and an MA and PhD in art history from the Institute of Fine Arts, NYU. He specializes in late medieval secular manuscript illumination and is currently working as art historical commentator on two Machaut projects: an edition of his complete works and a facsimile. He also has a book in progress on marginalia in a manuscript with the Vows of the Peacock poem.
Kate Maxwell is currently a postdoctoral fellow in the Centre for Multimodality and Cultural Change at the University of Agder, Norway, working on a project entitled 'Multimodal Machaut: Manuscript, Print, and Digital receptions of the Oeuvre' (for more details see skatemaxwell.wordpress.com). In 2009 she was awarded her PhD by the university of Glasgow for her thesis "Guillaume de Machaut and the mise en page of medieval French sung verse". Recent publications include an article on the use of Memory in Machaut manuscripts and the Voir Dit for the volume Memory in Medieval France (ed. Meredith Cohen, Elma Brenner, and Mary Franklin-Brown, Ashgate, 2013), an article on Machaut's lays in Manuscripts and Printed Books in Europe, 1350-1550: Packaging, Presentation and Consumption (ed. Emma Cayley and Sarah Powell, Exeter University Press, in press), and the graphic composition "Performing Notation, Notation Performing" in Notations 21 (ed. Theresa Tisano, New York: Mark Batty, 2009). She is currently co-editing a volume entitled Performance and the Page which considers the manuscript presentation of medieval works.
Elizaveta Strakhov is a doctoral candidate in Comparative Literature at the University of Pennsylvania working on a dissertation provisionally entitled "Channeling War: Poetics and Politics in the Pennsylvania Manuscript" that uses the lyric anthology University of Pennsylvania Codex 902 (formerly French 15) to open up questions surrounding political factionalism, linguistic diversity and shared poetic culture in England and France during the Hundred Years War. She has an article on Chaucer and Statius forthcoming in Chaucer and Fame, ed. Isabel Davis and Catherine Nall (Boydell & Brewer) and an article on Machaut and Chaucer forthcoming in Machaut's Legacy: The Judgment
Poetry Tradition in Late Medieval Literature, ed. Burt Kimmelman and R. Barton Palmer (University of Florida Press).
Helen Swift is Fellow and Tutor in Medieval French at St Hilda's College, University of Oxford. Having initially focused on questions of gender representation in the late medieval querelle des femmes (Gender, Writing, and Performance: Men Defending Women in Late Medieval France (1440-1538), OUP, 2008), she now draws on this corpus, in conjunction with later-fourteenth-century material, to consider broader issues of text-image relations, patronage practices, voice, and first-person identity in narrative poetry of the period.
Anna Zayaruznaya is interested in the relationship between text and music in late-medieval song. She is currently at work on a book which explores the roles played by monstrous and hybrid imagery in the motets of Machaut , Philippe de Vitry, and their contemporaries. An Assistant Professor in the department of music at Princeton University, she teaches courses in medieval and renaissance music and the history of musical notation.


text:
Jump to navigation
The Hagley Digital Archives provides online access to selected items from the Hagley Library's collection of images, documents, and publications related to the history of business, technology, and society.
Rebecca Webb (Pennock) Lukens
Lukens Steel Company
From a portrait painted about 1820
Lukens, Rebecca Pennock, 1794-1854
still image
1 print : b&w
reformatted digital
Audiovisual Collections and Digital Initiatives Department, Hagley Museum and Library
Lukens Steel Company photographs (Accession 1972.360)
Box 2, Folder 'Portraits: Lukens Family & Huston Family and Business Associates'
[Description and dates], Hagley ID, Box/folder number, Lukens Steel Company photographs (Accession 1972.360), Audiovisual Collections and Digital Initiatives Department, Hagley Museum and Library, Wilmington, DE 19807
Access to this item is provided for educational and research purposes only. The user assumes responsibility for obtaining permission from the copyright holder to publish or distribute this image. If you would like more information, please contact email@example.com


text:
May 30, 2013
May 30, 2013, Seattle, Wash. - Following the success of the International Academy of Design & Technology-Seattle's (IADT-Seattle) 2012 IMAGINE Portfolio Gallery & Fashion Show at the Museum of Flight, IADT-Seattle is once again about to step it up a notch! At 5:30 p.m. on Friday, September 20, 2013 the doors of the iconic Stewart Street Room at the Macy's downtown Seattle location will open to welcome IADT - Seattle students, faculty, friends, industry partners, and the public at large to celebrate a night of design, technology and fashion.
The evening will begin with the 2nd Annual all program IMAGINE Portfolio Gallery at 5:30 p.m. On display will be the work of students and alumni from each of the Design & Technology programs. The gallery is open to the public and there is no cost to attend.
The 8th Annual IMAGINE Fashion Show begins with the VIP Reception and early seating starting at 7 p.m. with the runway show starting at 8:00 p.m. The fashion show will be directed this year by Latasha Haskins of NW Pageant Pro. Tickets for the fashion show will be available for purchase soon!
"IMAGINE is IADT's much anticipated annual show. The inclusion of the Portfolio Gallery has brought this event to a new level, and provides an opportunity for us to introduce the community to our students," stated Khaled Sakalla, Campus President.
The evening will be filled with excitement from the moment one steps into the Stewart Street Room to the finale when the gallery and show award winners are announced.
For more information on sponsorship opportunities and tickets, please contact us at email@example.com or call 206.565.1865.
The Stewart Street Room is located on the Third floor in Macy's downtown location at (1601 Third Avenue, Seattle, WA 98101)
Once again, IMAGINE is partnering with the Career Education Scholarship Fund - www.CESfund.org. Proceeds from the show to benefit IADT-Seattle students. Last year $10,000 was donated to the fund.
About the International Academy of Design and Technology in Seattle
With more than 30 years as an established institution, the International Academy of Design and Technology offers students a hands-on education with experienced faculty dedicated to providing students with the necessary skills, knowledge, support and guidance to pursue fulfilling career opportunities in the design and technology fields. The Seattle campus (IADT-Seattle), which opened in 2004, offers degree programs in Fashion Design, Interior Design, Graphic Design, Digital Media Production, Fashion Merchandising, Game Production, Information Technology, Web Design and Development, and Software Engineering Technology. Students also have the opportunity to take a portion of their coursework online through IADT-Online. The school is accredited by the Accrediting Council for Independent Colleges and Schools (ACICS). ACICS is a national accrediting agency recognized by the United States Department of Education. Find disclosures on graduation rates, student financial obligations and more at www.iadt.edu/disclosures. IADT-Seattle cannot guarantee employment or salary and is a member of the Career Education Corporation (NASDAQ:CECO) network of universities, colleges and schools. For more information call 206.575.1865 or visit www.iadt.edu/Seattle.
By providing your mobile number, you agree to receive text messages from International Academy of Design & Technology via its mobile text message provider. You may opt out of receiving messages by texting the word STOP to 94576, or simply reply with the word STOP to any text message you receive from International Academy of Design & Technology.
While CEC or its mobile text message provider will not charge end users for receiving/responding to promotional messages, depending on the terms of your mobile phone plan, you may incur a cost from your mobile service carrier to receive and respond to any promotional text messages (standard messaging and data rates/fees and other charges may apply). Charges will appear on your mobile phone bill or will be deducted from pre-paid amounts. Current participating/supported carriers are: Alltel, AT&T, Boost, Cellcom, Cellular One, Cellular South, Cincinnati Bell, Cricket, Element Wireless, Golden State Cellular, iWireless, Metro PCS, Nextel, nTelos, Plateau Wireless, Sprint, T-Mobile, US Cellular, Verizon Wireless, Viaero Wireless, Virgin, and more.
Copyright ©
IADT. All rights reserved. No information may be duplicated without IADT's permission.
The IADT logo is a registered trademark of Career Education Corporation. IADT cannot guarantee employment or salary.
IADT-Online: Not all programs are available to residents of all states.
Valid GED or high school diploma required for admission.
Privacy Statement | Legal Terms and Conditions | Sitemap


text:
Shorpy is funded by you. Help by purchasing a print or contributing. Learn more.
Our holdings include hundreds of glass and film negatives/transparencies that we've scanned ourselves; in addition, many other photos on this site were extracted from reference images (high-resolution tiffs) in the Library of Congress research archive. (To query the database click here.) They are adjusted, restored and reworked by your webmaster in accordance with his aesthetic sensibilities before being downsized and turned into the jpegs you see here. All of these images (including "derivative works") are protected by copyright laws of the United States and other jurisdictions and may not be sold, reproduced or otherwise used for commercial purposes without permission.
Vintage photos of:
Black-and-white historical photos from the American Civil War. Wet plate collodion glass plate negatives exposed by Mathew Brady, Alexander Gardner, Timothy O'Sullivan and other noted Civil War photographers. There are hundreds of photos in this gallery.


text:
Local athletes punch tickets to state meet
Several local track and field athletes punched their tickets to the state meet as they placed in the top two at the Section 7A Track and Field Championships held at Griggs Field on the campus of the University of Minnesota Duluth on Friday, May 31. The State A Meet is at Hamline University, St. Paul, on June 7 and 8 with events beginning at 3 p.m.
The Moose Lake-Willow River boys placed second with 66 points while the Rebel girls placed fifth with 47 points. Esko won the boys team competition with 110.50 points while International Falls won the girls team title with 129 points.
The following represents those individuals and relay teams to place in the top six at the meet. *State meet qualifiers.
Girls 200-meter dash - Karina Cisar, ML-WR, 5th, 27.79.
Girls 800-meter run - Mackenzi Louzek, ML-WR, 3rd, 2:25.57.
Boys 800-meter run - *Ben Moonen, ML-WR, 2nd, 2:00.83.
Girls 1,600-meter run - *Nicole Tekippe, ML-WR, 1st, 5:21.82.
Girls 3,200-meter run - *Nicole Tekippe, ML-WR, 1st, 11:40.14.
Boys 110-meter hurdles - *Michael Pender, ML-WR, 2nd, 15.70.
300-meter hurdles - *Michael Pender, 1st, 41.78.
Girls 4X100-meter relay - ML-WR, Shaelyn Halverson, Taylor Miller, Hannah Race, Holly Mattison, 6th, 54.82.
Boys 4X100-meter relay - ML-WR, Jon Evenson, Isaac Coil, Ben Moonen, Josh Petterson, 3rd, 45.90.
Boys 4X200-meter relay - *ML-WR, Jon Evenson, Josh Pettersen, Isaac Coil, Michael Pender, 1st, 1:34.99.
Girls 4X400-meter relay, ML-WR, Hayley Johnson, Karina Cisar, Kiersten Evenson, Mackenzi Louzek, 5th, 4:27.47.
Boys, 4X400-meter relay - David Moonen, Jon Evenson, Isaac Coil, Ben Moonen, 4th, 3:38.08.
Girls 4X800-meter relay - ML-WR, Hayley Johnson, Tori Walczynski, Libbie Ring, Mackenzi Louzek, 4th, 10:21.12.
Boys high jump - Jake Disterhaupt, ML-WR, 3rd, 5-10.
Boys long jump - *Jon Evenson, ML-WR, 1st, 20-6.50.
Boys discus throw - *Brady Youngberg, Barnum - 2nd, 136-00.


text:
Re-imagining Shakespeare - Hamlet (program 2)
Pincsak, Cecily
Schiedler, Greg
Wiseman, Kathy
Dixon, Laura
MetadataShow full item record
William Shakespeare was no stranger to collaboration. More than a few of his plays were co-authored with fellow dramatists or adapted by others in the process of publication, while performances of his works have always depended on the efforts of actors, investors, and even audiences. Indeed, in his time, Shakespeare was part of a commercial company, the Lord Chamberlain's Men, and later, the King's Men. Bringing his works to both light and life has therefore always required the imaginative labor of many.
This exhibition represents the cross-discipline collaboration of more than sixty of Drake's students. After studying several of the Bard's plays, students in Sarah Hogan's Reading Shakespeare courses (ENG 058) worked in small groups to direct and perform scenes from "The Merchant of Venice", "Hamlet", and "Twelfth Night". They then collectively drafted a series of short essays on their imagined full-length productions. These modern adaptations, explained in the collaboratively-authored programs, ranged from a "Hamlet" set in the impoverished town of Denmark, South Carolina, to a "Twelfth Night" that explores the gender politics of corporate America. Students in the Graphic Design Two courses (ART 116) taught by Hilary Williams then worked in pairs to create theater posters and program covers that drew on these materials for inspiration and interpretation. All along the way, students have shared ideas, debated visions, and re-imagined Shakespeare.


text:
|HiFiMan RE-400 In-Ear Monitor Review
|Tuesday, 05 March 2013
Page 2 of 2
ListeningTo put them through their paces, I used the RE-400 with several devices -- including an Apple iPhone 4S, a Blackberry Curve, a Google Nexus 7 tablet, an HP Windows 7 Laptop, and a Droid Razr M -- and in many different settings such as the gym, my office, and when generally out and about.
The RE-400 were extremely comfortable and a pleasure to use from an ergonomic standpoint. I found the fit of the tips to be excellent. Although these do not have active "noise cancelling" circuitry, they provided a very good seal, keeping out ambient noise. The cables proved to be quite sturdy and tangle free. I don't think there will be any durability issues with these in ears.
To get right to it, I thought the RE-400 sounded really good. Midrange was rich, detailed, and quite natural sounding. Top end was smooth as butter, neither rolled off nor edgy. And the bass was just right, with good definition. However, these would not be considered for bass freaks who prefer low end rattle over control.
What I found impressive about the RE-400 was they sounded consistently good across all musical genres and all devices used. Of course, the better the source material, the more they extracted. I probably had the most fun with the RE-400 using Amazon's new AutoRip service. With the appropriate app, you can stream or download 256 kbps MP3s of any qualifying CD purchased from Amazon. I had access to over 300 albums, and the MP3 stream was surprisingly good.
Comparing the RE-400 to the Paradigm SHIFT buds was interesting. The Paradigms, which cost $30 more than the HiFiMan, also double as a volume control and microphone. The Paradigms were definitely a bit darker sounding, with a bit of thickness in the mid-bass. I think the HiFiMan was more down-the-middle neutral, and more delicate sounding. Overall, they were a bit lighter on their feet.
I really only have one minor nitpick with the RE-400. I wish there was color coding for Right and Left channels, instead of the tiny R and L marking on each monitor. Other than this slight ergonomic oversight, the RE-400's were a hassle free.
The HiFiMan RE-400 are finely crafted in-ears. Stylish, terrific sounding, well made, and very fairly priced. I really found nothing to complain about, save for no easily visible markings for R/L channels. Everything else was beyond reproach given its reasonable price. I noted in prior reviews that I had unfortunately blown money on very expensive, trendy IEMs only to deal with ill-fitting buds and fatiguing sound.
HiFiMan is pushing the envelope on comfort, sound, and build with the RE-400. Those interested in higher end, less portable models should investigate the rest of the line. Going forward, they will be my reference for their price point. The HiFiMan RE 400 in-ear monitors are a clean, clear window into the music, and a great value. Very much recommended.
HiFiMAN RE-400 In-Ear Monitors: $99
Driver: 8.5mm
Impedance: 32 OHM+/- 3.2
Sensitivity: 102dB/1mW
Rated power: 10mW
Maximum power: 30 mW
Frequency response: 15 ~22 KHZ