Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home/roominhi/public_html/wp-content/plugins/revslider/includes/operations.class.php on line 2159

Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home/roominhi/public_html/wp-content/plugins/revslider/includes/operations.class.php on line 2163

Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home/roominhi/public_html/wp-content/plugins/revslider/includes/output.class.php on line 2813

Warning: Cannot modify header information - headers already sent by (output started at /home/roominhi/public_html/wp-content/plugins/revslider/includes/operations.class.php:2159) in /home/roominhi/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/roominhi/public_html/wp-content/plugins/revslider/includes/operations.class.php:2159) in /home/roominhi/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/roominhi/public_html/wp-content/plugins/revslider/includes/operations.class.php:2159) in /home/roominhi/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/roominhi/public_html/wp-content/plugins/revslider/includes/operations.class.php:2159) in /home/roominhi/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/roominhi/public_html/wp-content/plugins/revslider/includes/operations.class.php:2159) in /home/roominhi/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/roominhi/public_html/wp-content/plugins/revslider/includes/operations.class.php:2159) in /home/roominhi/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/roominhi/public_html/wp-content/plugins/revslider/includes/operations.class.php:2159) in /home/roominhi/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/roominhi/public_html/wp-content/plugins/revslider/includes/operations.class.php:2159) in /home/roominhi/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831
{"id":77,"date":"2015-11-14T16:55:07","date_gmt":"2015-11-14T16:55:07","guid":{"rendered":"http:\/\/roominhistory.com\/?page_id=77"},"modified":"2015-11-23T17:12:47","modified_gmt":"2015-11-23T17:12:47","slug":"the-encoding","status":"publish","type":"page","link":"https:\/\/roominhistory.com\/the-encoding\/","title":{"rendered":"The Encoding"},"content":{"rendered":"
<\/div>
<\/div>

This project uses TEI markup, building on decades of discussion about how to represent a wide range of textualities. Many of these uses are unmodified. For example, elements like <persName>, <placeName>, <title>, and <quote> are used to\u00a0record references to persons, places, texts, and quotations.\u00a0Making Room in History\u00a0<\/em>also uses @ref and @source to link to a bibliography and a personography, making it possible to track historical figures across multiple\u00a0texts and to record details of citation and intertextuality. I am currently developing\u00a0internal documentation for the project\u00a0to\u00a0provide a fuller account of its encoding practices.<\/p>\n

In addition to some\u00a0unmodified\u00a0TEI encoding, this project also incorporates several customized elements and attributes, which I have developed\u00a0out of my previous research<\/a> into the literary and historiographic cultures of early modern Britain and Ireland. The most significant of these\u00a0customizations, with their uses and intentions, are described below. This discussion assumes some familiarity with the TEI; those who have not worked with text encoding may find David Birnbaum’s excellent “What is XML and why should humanists care? An even gentler introduction to XML<\/a>” helpful.<\/p>\n

@localType<\/strong><\/h1>\n

This attribute is used to record the labels of texts and sections of texts as\u00a0given in the texts themselves. It works along with @type, which has a more standardized list of values. This combination\u00a0allows @type values for <div> and <text> that are generalizable, while also recording the\u00a0particular\u00a0terms that texts use to describe\u00a0themselves. For example, a collection of poems might be labeled “certain verses” by the text itself; this specificity can be recorded with @localType, while the division is also labeled with the general @type of “poemGroup”.<\/p>\n

\"\"<\/a>

Sample encoding: @localType<\/em><\/p><\/div>\n

<textKind><\/strong><\/h1>\n

This element is designed to record the labels writers apply to the texts and textual materials that they discuss (by contrast with @localType, which records\u00a0internal textual identifications).\u00a0The range and density of <textKind>s that are used to describe historical materials demonstrate early modern writers\u2019 interest in historiographical taxonomy and investment in discussing the boundaries of the discipline. Some <textKind>s make claims about the truth-value of the work they describe, some are focused on form, and some on content\u2014many can be very flexible.<\/p>\n

The name of the element derives from the ways that early modern texts were taxonomized, by “kind” or “sort”. For example, Edward Leigh’s Foelix Consortium <\/em>asserts that:<\/p>\n

\n

Just or perfect History is of three kindes, according to the\u00a0nature of the object which it propounds to represent; for it\u00a0either represents some portion of time, or some memorable\u00a0person, or some famous Act. The first we call Chronicles or Annals; the second Lives; the third Relations. (46).<\/p>\n<\/blockquote>\n

Margaret Cavendish offers a different historiographic taxonomy in the preface to her 1667\u00a0Life of William Cavendish<\/a><\/em>:<\/p>\n

\n

Although there be many sorts of histories, yet these three\u00a0are the chiefest: 1. a General History 2. A National History. 3. Particular History. (n. pag.)<\/p>\n<\/blockquote>\n

The terms that early modern writers used to label their sources and materials often shaped their disciplinary claims, as in the example below, in which John Clapham’s 1606 Historie of Great Britannie<\/a>\u00a0<\/em>distinguishes the “poeticall fictions” and “feigned legends” that have contaminated Arthurian traditions from “Historie,” which, he says “ought to be a Register of things, either truely done, or at least, warrantable by probabilitie” (200). This example also shows how, by using <persName> and <rs> with @ref, the individual persons mentioned in the text can linked to a personography and associated with this historical narrative and all the markup applied to it.<\/p>\n

\"\"<\/a>

Example encoding from John Clapham’s <\/em>Historie of\u00a0Great\u00a0Britannie<\/p><\/div>\n

Below\u00a0are some sample <textKinds>, all from James Ware’s 1633 collection of Irish histories, Two Histories of Ireland<\/a><\/i>.<\/p>\n