Skip to content

Markup 1: HTML, XML, EpiDoc

Monica Berti edited this page Mar 31, 2018 · 14 revisions

Sunoikisis Digital Classics Spring/Summer 2018

Session 3. Markup I: HTML, XML, EpiDoc

Thursday Feb 8, 2018, 16h00-17h15 Greenwich Mean Time

Convenors: Gabriel Bodard (Institute of Classical Studies), Monica Berti (Leipzig), Martina Filosa (Köln)

YouTube link: https://youtu.be/NuwHT_jw50k

Slides: Combined slides (PDF)

Description

In this session we will discuss markup languages with a focus on HTML, XML, and EpiDoc. The session is complementary to Markup 2 (Feb. 22).

  1. In the first part we will introduce markup languages describing the difference among presentational markup, procedural markup, and descriptive markup. We will also briefly introduce recent lightweight markup languages, as for example Markdown.
  2. The second section will take a step back and look at pre-digital, arbitrary markup schemes, and what the underlying information the marks are attempting to communicate. How does digital markup build on and convert the semantics of these schemes to machine-readable form?
  3. The final section will show some structural and semantic markup in a digital text edition, focusing on the layout of text and demonstrating the use of the Oxygen XML editor.

Seminar readings

Other resources

Essay title

tba

Exercise

  1. Please install the Oxygen XML editor and register for a demo license. This will allow you to use this software for free for 30 days, but thereafter you would have to pay to continue to use it.
  2. Choose a short ancient or other primary source, either in the original language or in English translation, and transcribe this text into an empty XML file. Without applying any existing schema, add XML tags to structure and annotate your document, choosing those features that you believe are important and worth recording.
  3. Think about issues including: presentational, procedural and descriptive features of your encoding; the scalability of this exercise; whether anyone else would understand your markup (and if that matters); unique features against interoperability. What choices might you make differently with a different kind of text?
Clone this wiki locally