<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="/topics-files/atom2xhtml.xsl" type="text/xsl"?>
<!-- This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers. -->
<feed xmlns="http://www.w3.org/2005/Atom"
><title
>Blog@Case Topics: tei</title
><link rel="self" href="http://blog.case.edu/topics/tei"
 /><id
>http://blog.case.edu/topics/tei</id
><category term="tei" label="tei"
 /><contributor
><name
>Richard Wisneski</name
><email
>richard.wisneski@case.edu</email
><uri
>http://blog.case.edu/rlw54</uri
></contributor
><updated
>2012-01-19T18:14:21Z</updated
><entry
><title
>TEI Manuscript Project</title
><link href="http://blog.case.edu/rlw54/2012/01/19/tei_manuscript_project"
 /><id
>http://blog.case.edu/rlw54/2012/01/19/tei_manuscript_project</id
><published
>2012-01-19T17:52:31Z</published
><updated
>2012-01-19T18:14:21Z</updated
><category term="TEI" label="TEI"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>WRHS MANUSCRIPT PROJECT 
<strong>Dublin Core (DC) and MODS Templates:</strong> 1. 
<a href="http://blog.case.edu/rlw54/2012/01/19/wrhsmsdcTemplate2010.xml" target="_blank">Dublin Core Template</a> 2. 
<a href="http://blog.case.edu/rlw54/2012/01/19/wrhsmsmodstemplate.xml" target="_blank">MODS Template</a> 
<strong>Dublin Core Examples:</strong> A. 
<a href="http://blog.case.edu/rlw54/2012/01/19/wrhsms06205dc.xml" target="_blank">wrhsms 06-205</a> B. 
<a href="http://blog.case.edu/rlw54/2012/01/19/wrhsms05151dc.xml" target="_blank">wrhsms 05-151</a> C. 
<a href="http://blog.case.edu/rlw54/2012/01/19/wrhsms06189dc.xml" target="_blank">wrhsms 06-189</a> D. 
<a href="http://blog.case.edu/rlw54/2012/01/19/wrhsms04102dc.xml" target="_blank">wrhsms 04-102</a> 
<strong>MODS Examples:</strong> A. 
<a href="http://blog.case.edu/rlw54/2012/01/19/wrhsms06205mods.xml" target="_blank">wrhsms 06-205</a> B. 
<a href="http://blog.case.edu/rlw54/2012/01/19/wrhsms05151mods.xml" target="_blank">wrhsms 05-151</a> C. 
<a href="http://blog.case.edu/rlw54/2012/01/19/wrhsms06189mods.xml" target="_blank">wrhsms 06-189</a> D. 
<a href="http://blog.case.edu/rlw54/2012/01/19/wrhsms04102mods.xml" target="_blank">wrhsms 04-102</a> 
<strong>Useful Resources</strong> &#226;&#8364;&#162; Whittlesey, Charles W. Early history of Cleveland, Ohio, including papers and other matter relating to the adjacent country. AVAILABLE ON GOOGLE BOOKS &#226;&#8364;&#162; The Encyclopedia of Cleveland History: http://ech.cwru.edu/ &#226;&#8364;&#162; Whittlesey, Charles W. Early history of Cleveland, Ohio, including papers and other matter relating to the adjacent country. AVAILABLE ON GOOGLE BOOKS &#226;&#8364;&#162; Library of Congress Subject Headings &#226;&#8364;&#162; Thesaurus of Geographic Names (TGN)</div
></content
><author
><name
>Richard Wisneski</name
><email
>richard.wisneski@case.edu</email
><uri
>http://blog.case.edu/rlw54</uri
></author
></entry
><entry
><title
>Notes from TEI seminar, Univ. of Maryland, Jan. 2011</title
><link href="http://blog.case.edu/rlw54/2011/01/19/notes_from_tei_seminar_univ_of_maryland_jan_2011"
 /><id
>http://blog.case.edu/rlw54/2011/01/19/notes_from_tei_seminar_univ_of_maryland_jan_2011</id
><published
>2011-01-19T21:05:13Z</published
><updated
>2011-01-25T15:42:30Z</updated
><category term="TEI" label="TEI"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<u>Projects using Contextualization:</u>
<ul>
<li>
<a href="http://voices.iit.edu/">Voices of the Holocaust</a>:</li>
<li>
<a href="http://www.encyclopedia.chicagohistory.org/">Encyclopedia of Chicago History</a>
</li>
<li>
<a href="http://swinburnearchive.indiana.edu/swinburne/www/swinburne/">Swinburne Project</a>
</li>
<li>http://webapp-devel.dlib.indiana.edu/swinburne/</li>
<li>
<a href="http://golf.services.brown.edu/sandbox/names/interface/wheatley.poems.html">Phyllis Wheatley Poems</a> (uses xslt, javascript,php, css)</li>
<li>
<a href="http://www.eafsd.org/">Early American Foreign Database</a>
</li>
<li>
<a href="http://www.ucl.ac.uk/transcribe-bentham/">Transcribe Bentham project</a> (very cool)</li>
<li style="list-style: none">
<div style="margin-left: 2em">
<u>Contextual information</u> ID'ing things and names in text: places, people, books, etc. Info about things named in text, such as birth dates, geo locations, date published, etc., can be placed in separate orthographies, with links from texts to entries in ographies Interpretive info, such as themes, keywords, and thematic interpretations, can also be placed in ographies P5 allows for linked data 
<u>Ographies</u>: personography, placeography, bibliography element &#226;&#8364;&#8220; referring element. E.g. that owner 
<u>MLA thesaurus for genre:</u> http://www.mla.org/publications/bibliography/howtouse_mlabiblio/howtosearchmlabiblio#mla 
<u>RBMS authorities:</u> http://www.rbms.info/committees/bibliographic_standards/controlled_vocabularies/introductions/ProvenanceIntro.htm 
<u>OCLC terminologies project:</u> http://www.oclc.org/terminologies/ Use oXygen plug-ins: to get list from, for example, MLA thesaurus Pointer element &#226;&#8364;&#8220; used for linking to bibliographies See: http://www.cpen.com/start 
<u>Google book ngrams:</u> http://ngrams.googlelabs.com/ 
<u>Token-x:</u> http://jetson.unl.edu:8080/cocoon/tokenx/index.html?file=../xml/base.xml Trait, state, event &#226;&#8364;&#8220; generic elements in personography Ography vs. controlled vocabulary http://www.geonames.org/ Have @type on every div, name, and link (Syd Bauman's rule) Word-ography &#226;&#8364;&#8220; for glossary https://wiki.dlib.indiana.edu/display/vwwp/Home http://oaap.rice.edu/ http://mith.umd.edu/staff/dreside/RaiseXML/# http://pltplp.net/2000/10/xmlsite.html XTF: http://xtf.cdlib.org/ geocoding: http://code.google.com/apis/maps/documentation/geocoding/ http://geocoder.us/ CollateX: http://collatex.sourceforge.net/ --to produce a critical apparatus. compares texts (very cool). Crowdsourcing Documentary Transcription: Scripto: http://scripto.org/ w3c xslt tutorial: http://www.w3schools.com/xsl/ notes: authorial (by source text author),editorial (author's editor), temp notes (internal to project; not for public consumption), textual (notes by project manager on entire text), wwp notes (local public notes; internal editorial notes)</div>
</li>
</ul>
</div
></content
><author
><name
>Richard Wisneski</name
><email
>richard.wisneski@case.edu</email
><uri
>http://blog.case.edu/rlw54</uri
></author
></entry
><entry
><title
>TEI Rendering Samples</title
><link href="http://blog.case.edu/rlw54/2010/03/12/tei_rendering_samples"
 /><id
>http://blog.case.edu/rlw54/2010/03/12/tei_rendering_samples</id
><published
>2010-03-12T20:23:16Z</published
><updated
>2010-09-28T18:49:45Z</updated
><category term="TEI" label="TEI"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>MODS record in HTML: 
<a href="http://blog.case.edu/rlw54/2010/03/12/brolifmodsoutputtest.html" target="_blank">brolif00-mods</a> TEI document rendered in HTML: 
<a href="http://blog.case.edu/rlw54/2010/03/12/flelab00.html" target="_blank">flelab00-html</a> Raw MODS record: 
<a href="http://blog.case.edu/rlw54/2010/09/28/wrhsms05136mods.xml" target="_blank">wrhsms05136</a></div
></content
><author
><name
>Richard Wisneski</name
><email
>richard.wisneski@case.edu</email
><uri
>http://blog.case.edu/rlw54</uri
></author
></entry
><entry
><title
>XML Intermediate Workshop</title
><link href="http://blog.case.edu/rlw54/2010/02/14/xml_intermediate_workshop"
 /><id
>http://blog.case.edu/rlw54/2010/02/14/xml_intermediate_workshop</id
><published
>2010-02-14T22:43:08Z</published
><updated
>2011-03-02T16:59:10Z</updated
><category term="TEI" label="TEI"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<u>Documents For Intermediate XML Workshop: Schemas, XPATH, XSLT</u> 
<a href="http://blog.case.edu/rlw54/2011/03/02/book.xml" target="_blank">Books XML file</a> 
<a href="http://blog.case.edu/rlw54/2011/03/02/bookschema.xsd" target="_blank">Schema for books XML file</a> 
<a href="http://blog.case.edu/rlw54/2011/03/02/wrhsms02039march2011.xml" target="_blank">book TEI file</a> 
<a href="http://blog.case.edu/rlw54/2010/02/14/bookdtd.dtd" target="_blank">DTD for book XML file</a></div
></content
><author
><name
>Richard Wisneski</name
><email
>richard.wisneski@case.edu</email
><uri
>http://blog.case.edu/rlw54</uri
></author
></entry
><entry
><title
>Workshop material</title
><link href="http://blog.case.edu/rlw54/2010/02/04/workshop_material"
 /><id
>http://blog.case.edu/rlw54/2010/02/04/workshop_material</id
><published
>2010-02-04T13:55:21Z</published
><updated
>2010-11-18T16:40:16Z</updated
><category term="TEI" label="TEI"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<u>TEI Workshop material</u> 
<a href="http://blog.case.edu/rlw54/2010/11/17/wrhsms05121forclass.xml" target="_blank">wrhsms05121rough</a> 
<a href="http://blog.case.edu/rlw54/2010/11/18/wrhsms05121.xml" target="_blank">wrhsms05121done</a> 
<a href="http://blog.case.edu/rlw54/2010/02/04/container5folder153.xml" target="_blank">manuscript in xml</a> 
<a href="http://blog.case.edu/rlw54/2010/02/04/container5folder153.html" target="_blank">same manuscript in html</a> 
<a href="http://blog.case.edu/rlw54/2010/02/04/TEIheader-BPG-feb2010.doc" target="_blank">TEI Header Guidelines</a> 
<a href="http://blog.case.edu/rlw54/2010/02/04/newTemplate-feb2010.xml" target="_blank">TEI header template</a> 
<a href="http://blog.case.edu/rlw54/2010/02/04/newTemplateExample-feb2010.xml" target="_blank">TEI header example</a> 
<a href="http://blog.case.edu/rlw54/2010/02/04/clecle00-raw.xml" target="_blank">clecle00 draft file</a> 
<a href="http://blog.case.edu/rlw54/2010/02/04/bolfew00-example.xml" target="_blank">bolfew00 draft file</a> 
<a href="http://blog.case.edu/rlw54/2010/02/04/container5folder137-raw.txt" target="_blank">manuscript-draft (folder 137)</a> 
<a href="http://blog.case.edu/rlw54/2010/02/04/container5folder153.txt" target="_blank">manuscript-draft (folder 153)</a> 
<a href="http://blog.case.edu/rlw54/2010/03/23/molout00sample2010.xml" target="_blank">molout00 draft</a></div
></content
><author
><name
>Richard Wisneski</name
><email
>richard.wisneski@case.edu</email
><uri
>http://blog.case.edu/rlw54</uri
></author
></entry
><entry
><title
>Advanced TEI Seminar</title
><link href="http://blog.case.edu/rlw54/2010/01/20/advanced_tei_seminar"
 /><id
>http://blog.case.edu/rlw54/2010/01/20/advanced_tei_seminar</id
><published
>2010-01-20T14:39:54Z</published
><updated
>2010-01-25T14:32:57Z</updated
><category term="TEI" label="TEI"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<strong>Advanced TEI Seminar, UMD, January 20-22</strong> -- Issue: integrating manuscripts with print text. -- Issue: typed manuscripts, with handwritten additions, notes, etc.: how to mark these features -- Issue of commentary and notation for textual nuances. -- 
<a href="http://wwptei.pbworks.com/f/geneticTEI.doc.html" target="_blank">Encoding Model for Genetic Editions</a> -- 
<a href="http://www.openannotation.org/" target="_blank">open annotation collaboration</a> -- 
<a href="http://www.zvon.org/xxl/XSLTreference/Output/index.html" target="_blank">XSLT Reference</a> -- encoding to the stylesheet is bad practice -- revision narrative is important and necessary 1. The Beck Center for Electronic Collections Alice Hickcox, Emory University Woodruff Library, Emory University The Beck Center, a part of Woodruff Library at Emory University, has long had an interest in the Lady Gregory portion of the Gregory Family papers in the Manuscript, Archives, and Rare Book Library (MARBL) in Woodruff Library. There are several items in the collection that are unpublished, and we look forward to working with these. http://beck.library.emory.edu/ http://womenwriters.library.emory.edu/ 
<a href="http://beck.library.emory.edu/ladygregory/xml/gregory46-ff1_1-2.xml" target="_blank">xml example</a> 2. Margaret Sanger Papers Esther Katz and Cathy Moran Hajo, New York University The Margaret Sanger Papers is a scholarly editing project located at New York University&#226;&#8364;&#8482;s History Department, with staff also working at the Sophia Smith Collection at Smith College. Founded in 1987 to gather, preserve, identify and publish the papers of America&#226;&#8364;&#8482;s best-known birth control activist, the project is working with a collection of over 95,000 letters, speeches, diaries, pamphlets, reports and other documents ranging in date from 1911-1966. The project completed a two-series microfilm edition of 101 reels and indexed Sanger materials on a third microfilm collection of 145 reels made by the Library of Congress, storing general metadata on the documents in a database. Our goal is to develop digital version of our publications that can work with one another. We also hope to digitally publish thematic selections of documents that provide in-depth text analysis and interpretation or link the documents with analysis or texts from other collections. 
<a href="http://www.nyu.edu/projects/sanger/webedition/app/documents/search.php" target="_blank">Search</a> created on: title date document type (e.g. article, document, interview, review, autograph, typed draft, etc.) subject index full text -- 
<a href="http://wardepartmentpapers.org/" target="_blank">Papers of the War Department</a> -- Omeka interacts with WordPress -- 
<a href="http://www.nyu.edu/projects/sanger/webedition/app/" target="_blank">Public Writings of Margaret Sanger</a> 3. Melville Electronic Library John Bryant, Hofstra University 
<a href="http://rotunda.upress.virginia.edu/melville/" target="_blank">Typee: Fluid Edition</a> -- diplomatic transcription (typography to represent what you see on screen), base version (final reading text of the manuscript, sans all the crossouts, additions, and so on) -- in dual up-down frames -- shows revision sequence. Revision narrative then tells the story of the sequence. -- how to encode false starts versus 4. Dickinson Electronic Archive Julie Enszer, University of Maryland 
<a href="http://www.emilydickinson.org/cartoon/carindex.html" target="_blank">Dickinson, Cartoonist</a> 5. Folger Shakespeare Library Jim Kuhn and Heather Wolfe, Folger Shakespeare Library These advanced seminars will assist Folger staff in properly evaluating TEI-based project proposals that require access to Folger collection material, and in planning for future transcription of Folger manuscript collections that have been digitized. We are also in the process of expanding upon our in-house online paleography transcription program, in the hopes of making it a publicly accessible site. We anticipate that TEI-encoding will be an important component of this project. Guidelines here: http://quartos.org/info/encoding.html Personography: http://www.tei-c.org/Activities/Workgroups/PERS/ image markup tool: http://tapor.uvic.ca/~mholmes/image_markup/ (very cool open-source program) -- issue: how to show time sequence in manuscript encoding 6. American Memory Project Susan Garfinkel, Jurretta Jordan Heckscher, Library of Congress We are engaged in a demonstration project to present items from the Library of Congress&#226;&#8364;&#8482;s American Memory Historical Collections, http://memory.loc.gov, in alternative formats that expand their potential uses for digital scholarship and education. Our project&#226;&#8364;&#8482;s present focus is the markup of a single digitized source, the manuscript Civil War diaries of 
<a href="http://memory.loc.gov/ammem/tafthtml/tafthome.html" target="_blank">Horatio Nelson Taft</a>, volume 1. We are interested in exploring multiple tagging schema for this document that enable users to sort its contents by theme or topic. 
<a href="http://www.yale.edu/hraf/outline.htm" target="_blank">Human Relations Area Files</a> -- Interestingly, they have the same problem I do. These 2 librarians alone are doing the encoding, relying on interns on occasion. Extremely difficult (sometimes frustrating) to devote time to such work in addition to other duties and responsibilities. Staffing is crucial. 
<u>EXTRA:</u> http://beck.library.emory.edu/greatwar/postcards/index.php x include file interp data in separate file. each XML file would would point to that interp file. -- 
<a href="http://exist.sourceforge.net/" target="_blank">eXist</a>. XML database system. You can use stylesheets with it. -- 
<a href="http://www.djangoproject.com/" target="_blank">django</a> -- http://www.wwp.brown.edu/encoding/seminars/umd2010/handouts/index.html 
<u>Diplomatic and Normalized</u> -- There are two versions of the transcription, diplomatic and normalized. The diplomatic version attempts, as far as is practicable, to present the manuscript as it actually appears. The normalized transcription is a more readable version, which eschews many of the conventions of the original manuscript. The diplomatic version is to be considered definitive -- 
<a href="http://wiki.tei-c.org/index.php/Category:Customization" target="_blank">ODD file and schema</a>. Schema defines validity. ODD (one document does it all) is the documentation expressing relationship between schema and XML document, _and_ customizes the schema. ODD file is like a TEI document. It has TEI header, then documentation discussing the schema, then it builds a schema that is related to the TEI schema. shows what elements are being acted upon (e.g. deleted from schema) -- why use this rather than the full schema? Answer: stacking overflow error. Your system may not be able to handle all the elements. -- http://sourceforge.net/projects/tei/files/ -- http://www.tei-c.org/release/xml/tei/stylesheet/xsltdoc/ -- http://www.lgpn.ox.ac.uk/online/documents/TEIXML -- I just figured out how to transform a TEI file to HTML and PDF. It is at first glance easy, but later, extremely challenging. -- Personography and placeography. Should point to external XML file (Cleveland Encyclopedia should be converted to XML). -- LC geographical name authority file. You can use this for placeography eventually. http://authorities.loc.gov/</div
></content
><author
><name
>Richard Wisneski</name
><email
>richard.wisneski@case.edu</email
><uri
>http://blog.case.edu/rlw54</uri
></author
></entry
><entry
><title
>XML vs. Databases</title
><link href="http://blog.case.edu/rlw54/2008/08/28/xml_vs_databases"
 /><id
>http://blog.case.edu/rlw54/2008/08/28/xml_vs_databases</id
><published
>2008-08-28T13:29:35Z</published
><updated
>2008-08-28T13:38:20Z</updated
><category term="TEI" label="TEI"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>The following excerpt from Julia Flanders, from Brown University's Women's Writer's Project, and the links she offers, provide an interesting discussion of "XML vs. Databases." J. Flanders: "I should also say in advance (before anyone reads the more detailed screed below) that we're teaching XML and TEI for a reason, which is that they help us work with text in a way that respects both its nuance and our own interest in that nuance. So my own personal recommendation for representing textual information is to use XML on principle, because (regardless of what tools are available right now) in the long run it's the right kind of approach. However, it's worth understanding the broader context, which I will try to sketch below. "Database tools and XML tools differ in the kinds of things they're good at (and this is where the readings may come in handy, to give concreteness to this point). In addition, database structures and XML structures differ somewhat in their emphasis: database structures emphasize what is regular and predictable about your data (e.g. the fact that every individual commenter has a name, address, and gender). XML structures emphasize what is less regular and predictable about your data (e.g. the fact that the comment might or might not include praise for the exhibit, references to other exhibits, references to specific artists of interest, statements about being inspired, etc., and also the fact that the comment might contain an unpredictable number of paragraphs). For your data, which has a fairly regular and predictable structure, the difference is comparatively minor. For other kinds of data, though, the difference might be great: it would be much more difficult and bizarre to express the structure of a novel using a database." 
<u>Article Links</u>
<ul>
<li>
<a href="http://www.rpbourret.com/xml/XMLAndDatabases.htm" target="_blank">XML and databases</a>
</li>
<li>
<a href="http://www.rpbourret.com/xml/UseCases.htm" target="_blank">Going Native: Use Cases for Native XML Databases</a>
</li>
<li>
<a href="http://www.xml.com/pub/a/2001/10/31/nativexmldb.html" target="_blank">Introduction to Native XML Databases</a>
</li>
<li>
<a href="http://www.xmlmind.com/qizx/xml_vs_relational.html" target="_blank">Why Use a Native XML Database</a>
</li>
</ul></div
></content
><author
><name
>Richard Wisneski</name
><email
>richard.wisneski@case.edu</email
><uri
>http://blog.case.edu/rlw54</uri
></author
></entry
><entry
><title
>NINES-TEI Workshop -- Day 3</title
><link href="http://blog.case.edu/rlw54/2008/07/24/ninestei_workshop_day_3"
 /><id
>http://blog.case.edu/rlw54/2008/07/24/ninestei_workshop_day_3</id
><published
>2008-07-24T18:32:35Z</published
><updated
>2008-07-24T21:17:36Z</updated
><category term="TEI" label="TEI"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Notes from Day 3 of NINES-TEI Conference: _Customization the TEI schema: options_ --Select modules --Delete unnecessary elements --Add new elements or attributes --Change element or attribute names --Constrain attribute values (constrain data early and often. Tighter you make the schema, the fewer errors you'll have. But, don't contrain too much). --Constrain structure --Manipulate functional groupings of elements --Produce an internationalized version of the TEI _Contextual Information_ Information we know that is relevant to an understanding of the text: --The identity of things named in the text: people, places, books, etc. --Information about things named in the text: birthdates, geographical locations, date published, etc. --Interpretive information: themes, keywords --Normalization of measurements, dates, etc. _Contextual Information in the TEI_ The TEI provides several different structures for encoding contextual information: --&#226;&#8364;&#8482;Ographies: prosopography (personography), gazetteers(placeography),orgography, bibliography --keywords applied to the text as a whole --thematic or interpretive information applied to specific places in the text --attributes for supplying normalized values _Personography_ --Like a local name authority file --Can be simple or very detailed --Can be kept in your encoded file or externally --Includes specific elements for the most common data --Also includes general elements for the unforeseen _Placeography (Gazetteer)_ Key points: --Very similar to personography...but for places! --Can be linked to maps via geographic information data * use XLST for organization, CSS for display, database (e.g. Oracle, Lucene) for search capabilities. Do in-house, NOT via outsourcing _Successful Digital Projects_ --Well-planned workflow (planning before execution, communication mechanisms, etc.) --Phased approach (show progress early on) --Successful staff plan (needs versus practicality) --Realistic technical implementation plan (identify tools at the cale you need. Oracle database?) --Funding... _Workflow Issues_ Source --&gt; Transcription --&gt; Corrected Transcription --&gt; HTML output information gain should go to "corrected transcripton." "Information loss" may occur at HTML output. _Workflows that Make Sense_ 1. Craft approach detail initial capture by hand (i.e. you encode it) --&gt; review and error correction --&gt; interface created that allows you to do various things 2. Expertise in the Craft Approach detail initial capture by hand (i.e. you encode it) --&gt; review and error correction --&gt; scholarly and technical expertise interacts with review-and-error correction --&gt; display 3. Phased Approach simple initial capture (not detailed capture; could be automated via OCR capture) --&gt; simple error correction (e.g. spell-checking) and standard publication tools that do simple searches (e.g. search on author) --&gt; simple reading and search interface output --&gt; then do more advanced information (i.e. add to the XML markup) --&gt; new output Occurs often in large projects _Project Life Cycle: Starting Out_ 1. initial idea. Essentially volunteer 2. Seed funding (e.g. NEH DHSG) 3. Implementation that works, with a real audience. Requires serious funding (NEH, Mellon, Gettey, NSF,...) 4. Discover flaws and re-do; get funding because it's still an interesting project 5. wrap up and archive; institutional funding via institutional repository -OR- sustainability model for on-going project ad infinitum --&gt; ongoing redevelopment/new prototypes</div
></content
><author
><name
>Richard Wisneski</name
><email
>richard.wisneski@case.edu</email
><uri
>http://blog.case.edu/rlw54</uri
></author
></entry
><entry
><title
>NINES-TEI Workshop -- Day 2</title
><link href="http://blog.case.edu/rlw54/2008/07/23/ninestei_workshop_day_2"
 /><id
>http://blog.case.edu/rlw54/2008/07/23/ninestei_workshop_day_2</id
><published
>2008-07-23T14:09:50Z</published
><updated
>2008-07-23T18:48:47Z</updated
><category term="TEI" label="TEI"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Notes from 2nd day at NINES -- TEI workshop at Miami U. of Ohio XML A vocabulary and a grammar Example: --DocBook is a markup language for writing books vocabulary includes: article, title, and paragraph grammar states: "paragraph" is not allowed inside "title" Extensible Not a language, but a meta-language --methods of defining markup language --syntax for expressing markup language Gives us methods to define a markup language XML has no tags of its own, but instead defines teh syntax of tags; it defines no vocabulary or grammar of its own, but does tell you how to define a vocabulary and grammar XML languages varry greatly --many different purposes (financial data, linguistics, literary texts,...) --many different kinds of markup (structure, content, interpretation,...) --many different user communities (IRS, literary scholars, librarians,...) XML is --easy to understand --non-proprietary plaint-text (i.e. no particular company owns this. Plus, no binary data, such as opening a JPEG in MSWord or NotePad. Btw, RTF is problematic, because it's a MS format; MS can do away with it): --human readable --software independent --hardware independent --(relatively) easy to write a parser for --widespread: very well supported by both commercial and open source software Definition of... Parser--the software that differentiates markup from document. XML is a metalanguage --no tags or attributes of its own --instead, a set of rules ofor definning tags and attributes --imposes no constraints on elements and attributs in document --instead, defines how rules for such constraints are written Everything is Delimited Text is divided into elements --elements by start- and end-tags --start tags by &lt;...&gt; --end tags by &lt;/...&gt; --special case: short-hand for an element with no content. = Everything's Delimited: attributes Elements have attributes Users can turn on or turn off the stuff within the brackets (quantity=, unit=) when searching. Everything's Delimited: Character References To refer to a character that is not on your keyboard, delimit its ISO 10646 (or Unicode) code-point with: --&#0; and ; for decimal values, or --&#0; and ; for hexadecimal values Well-Formedness Simple set of rules on document syntax: --single "root" element (meaning, the one at the top of the tree/box) --every element has a start- and an end-tag (or is an empty tag) --no elements overlap NOTE: XML is not a perfect representation, but it gives us strategic ways to model information. One solution to overlap use the TEI part=attribute to work around this problem --"I" is for initital, "F" is for final. Validity A valid XML document follows the rules of a schema that describes a particular markup language: --lexicon or available voculary: elements and attributes --grammar for how teh lexicon is used: ruls for nesting, sequencing, etc. e.g. a paragraph can be inside a chapter, but a chapter cannot be inside a pragraph e.g. a chapter must begin with a heading followed by at lesat one paragraph --there exist variuos schema languages with which you can describe an XML grmmar, each with advantages and disadvantages. --in order to be valid, an instance must be well-formed --a well-formed document need not be valid You have to pass the well-formed test first, then do the validity check! You can be well-formed and yet not valid; you cannot be valid and not well-formed. Namespaces --a way to use tag vocabularies from diffferent markup languages --allows for specialization of markup languages (by discipline, by function) --good for metadat: can use TEI header in a METS record --good for speciailized markup: e.g. MusicML --No need for every markup language to handle everything * Make use of www.unicode.org _Challenges of Markup_ 3 Critical areas: --overlapping structures --images and figurality --materiality of the text</div
></content
><author
><name
>Richard Wisneski</name
><email
>richard.wisneski@case.edu</email
><uri
>http://blog.case.edu/rlw54</uri
></author
></entry
><entry
><title
>NINES Workship -- TEI</title
><link href="http://blog.case.edu/rlw54/2008/07/22/nines_workship_tei"
 /><id
>http://blog.case.edu/rlw54/2008/07/22/nines_workship_tei</id
><published
>2008-07-22T16:52:51Z</published
><updated
>2008-07-22T16:54:10Z</updated
><category term="TEI" label="TEI"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Notes from NINES Workshop, Miami University of Ohio, July 22-24, 2008: Motives for TEI -- to store info for long term -- to analyse info -- to share info Granularity Longevity What is TEI --technically: a standards organization for humanities text encoding --organizationally: an inter'l membership consortium --socially: a community of people and projects TEI founded in 2000. Members pay annual fee, pays for editorial work, outreach, workshops Formal declarations for encoding language. Constraints for how you can encode. Guidelines are thick; not everything is needed. P5 released Nov. 2007. Current version. Substantial shift. NEH cares about practical interchange than technical aspects. P4 and P5 have many of the same elements, but P5 is differrent from P4 in that: --P5 introduces some new elements --P5 fixes some errors from P4 (e.g. postscript element) --P5 doesn't change much for the encoder, but it does for how the texts are displayed, and the way its language is expressed. How you do customizations is very different in P5 from P4. TEI Guidelines --can be applied strictly or loosely --Can adapt to local conditions --Designed as a sett of modules that can be selected as needed --Not unlike a human language in some respect Vocabulary to use experimentally and exploratory. TEI is modular. Drama, verse, etc. TEI provides the tools. You have to ask: what is my project? What are my needs? What level of granularity do I want? Areas of Usage --digital libraries and digital archives --literary and cultural materials --scholarly editions --manuscript collections and descriptions --dictionaries --language corpora --historical documents --anthropplogy and social sciences --authoring --linguistics --many other areas... See, for example, projects on William Blake, Herman Melville, Poetress Archive (Miami Univ. of Ohio), Women's Writer's Project (Brown Univ.) Customization The proces of altering the TEI schema and documentation to match your needs. changes include: --choosing which parts to use or omit --changing the name of elements or attributes --restricting the values of attributes --adding new elements --adding new attributes "interchange" crucial element of TEI. Goal is meaningful exchange. Sources of Info --WWP seminars site --TEI web site --TEI listserv (TEI-L) --Colleagues at other projects</div
></content
><author
><name
>Richard Wisneski</name
><email
>richard.wisneski@case.edu</email
><uri
>http://blog.case.edu/rlw54</uri
></author
></entry
></feed
>
