Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Final dh2013 interoperability

3,560 views

Published on

Published in: Education, Travel
  • Be the first to comment

  • Be the first to like this

Final dh2013 interoperability

  1. 1. 1 DH 2013, Nebraska Practical Interoperability: The Map of Early Modern London and Internet Shakespeare Editions Janelle Jenstad and Martin Holmes University of Victoria mapoflondon.uvic.ca
  2. 2. 2 Loose couplings
  3. 3. 3 MoEML and ISE ● On UVic servers ● Overlapping teams ● Mutual need
  4. 4. 4 The Map of Early Modern London ● Maps streets, sites and boundaries of London 1560-1640 ● Interface based on Agas Map ● Includes (1) gazetteer, (2) encyclopedia of London people and places, (3) library of primary source texts, (4) edition of A Survey of London ● Pure TEI XML throughout
  5. 5. 5 Mapping toponyms
  6. 6. 6 Library
  7. 7. 7 Dramatic extracts
  8. 8. 8 Internet Shakespeare Editions ● Open-source digital anthology ● Also hosts and incubates Queen's Men's Editions and Digital Renaissance Editions ● Goal: all plays of Shakespeare and contemporaries, 1500-1640 ● SGML and non-standard XML :-(
  9. 9. 9 Frequency of toponyms The London locations in Richard III on the Agas Map, sized according to the number of references to them.
  10. 10. 10 Research questions ● How typical is Shakespeare's invocation of London? ● How do his characters move through the urban environment? ● What is the relationship between London and the court? ● How does this vision compare to other playwrights and to historians?
  11. 11. 11 Integration? Interoperability? Interchange? Is it reasonable to ask editors to revisit their "finished" work? ● Can we overcome the significant programming differences?
  12. 12. 12 Initial assumptions ● First rule of collaboration: You're on your own. ● The ISE agenda is not MoEML's agenda. ● MoEML can't ask the ISE editors to tag their texts. ● MoEML can't depend on the ISE programmers to implement things for us. ● We must beware of making features on our site dependent on functionality on theirs.
  13. 13. 13 Loose coupling ● We take the ISE texts and tag them. ● We generate sets of links based on through line numbers (TLNs). ● We store the links in our database. ● We only depend on the fact that links to TLNs on their website work.
  14. 14. 14 The (rather unrealistic) plan
  15. 15. 15 Manual tagging and NER
  16. 16. 16 Manual tagging and NER
  17. 17. 17 Manual tagging and NER
  18. 18. 18 Manual tagging and NER
  19. 19. 19 Manual tagging and NER
  20. 20. 20 Manual tagging and NER
  21. 21. 21 Manual tagging and NER
  22. 22. 22 Manual tagging and NER
  23. 23. 23 Manual tagging and NER
  24. 24. 24 Results ● 4 plays: – Richard II and Richard III (modern spelling) – Henry VIII and Henry VI Part 2 (old spelling) ● 495 placenames marked up ● 95 linked to Map of Early Modern London placeography
  25. 25. 25 Performance of NER engine
  26. 26. 26 Difficulties for NER tagger ● <stage>Enter Yorke, Salisbury, and Warwick.</stage> ● "Was not your husband / In Margaret's battle at St Albans slain?" ● Spelling variation ("Tower" versus "Towre") ● Capitalization is unhelpful in old-spelling texts. ● Short utterances confuse it: – Queen Margaret: Richard. – Richard: <LOC>Ha</LOC>?
  27. 27. 27 The showstopper problem ● Henry VI pt 2: – 210 placenames in the text – tagger tagged 109 places, of which 106 were correct – 29 of these were "England" and 38 "France" – Among placenames missed: ● 48 were in Britain ● 20 of these were key London locations (Bedlam, Southwark, London Bridge & Smithfield)
  28. 28. 28 Is it worth using NER for this? ● No. ● Possibly. – It can function as a check on manual tagging. ● Yes. – 75 "city plays" are eventually coming...
  29. 29. 29 Happy endings ● Second rule of collaboration: nobody wants to be left out. ● Now the ISE editors have seen how we're linking to their plays, they want to tag placenames for themselves. ● We'll just be able to harvest their tags for MoEML.
  30. 30. 30 Functional interoperability ISE guidelines: Internal Links to MoEML's London Locations We are moving towards interoperability with The Map of Early Modern London (MoEML). If your play includes references to London locations, you will identify each London location using the ilink element and the unique MoEML identifier for the location....
  31. 31. 31 ISE guidelines, cont. The purpose of this tagging is two-fold: (1) it will allow us to visualize the London locations in a play using a MoEML map in the ISE/DRE/QME environment, and (2) it will allow MoEML to import London references in ISE/DRE/QME plays into its database of literary references (with a link back to the ISE).
  32. 32. 32 ISE/DRE/QME tagging <ilink component="geo" href="mol:CHEA2">Cheapside</link> ISE will have various instructions in its "geo" component (England, France, Europe, London, stage geometry) All we need is the mol:XXXX# and the TLN
  33. 33. 33 Should we continue to use NER? ISE wants to use tags only in modern critical editions. ISE editions of 1 Henry IV, 2 Henry IV, and Henry V are “done.” 500+ plays in DRE

×