<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Pelagios - Medium]]></title>
        <description><![CDATA[Pelagios provides online resources and a community for using open data methods to link and explore historical places - Medium]]></description>
        <link>https://medium.com/pelagios?source=rss----3471255e9353---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Pelagios - Medium</title>
            <link>https://medium.com/pelagios?source=rss----3471255e9353---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:22:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/pelagios" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Introducing: Ajax Multi-Commentary]]></title>
            <link>https://medium.com/pelagios/introducing-ajax-multi-commentary-3c18bf0ca5d3?source=rss----3471255e9353---4</link>
            <guid isPermaLink="false">https://medium.com/p/3c18bf0ca5d3</guid>
            <category><![CDATA[distant-reading]]></category>
            <category><![CDATA[corpus-analysis]]></category>
            <category><![CDATA[ocr]]></category>
            <category><![CDATA[close-reading]]></category>
            <category><![CDATA[annotations]]></category>
            <dc:creator><![CDATA[Pelagios]]></dc:creator>
            <pubDate>Tue, 30 Nov 2021 07:55:21 GMT</pubDate>
            <atom:updated>2021-11-30T07:54:50.322Z</atom:updated>
            <content:encoded><![CDATA[<p>By Matteo Romanello</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fz9Y_q84eEgZH7Xs6IxPwg.jpeg" /><figcaption>Photo credits: © Fondation Hardt, Vandoeuvres, 2019.</figcaption></figure><p>The <a href="https://mromanello.github.io/ajax-multi-commentary/">Ajax Multi-Commentary</a> is a research project led by Matteo Romanello at the University of Lausanne, department of Classics and Archeology, and funded by the Swiss National Science Foundation.</p><p>This project deals with the scholarly tradition of writing commentaries about literary works, a tradition that goes back almost as long as those texts themselves — from the famous Alexandrian reception of Homer’s epics to Dante’s <em>Divina Commedia</em>, the <em>Talmud</em> or Shakespeare’s tragedies. In a nutshell, a commentary is a collection of glosses presenting the reader with any information that is deemed important for the reading and understanding of a given text (e.g., translation; metrical scansion; remarks about the <em>mise en scène</em>; bibliographic references to primary and secondary literature <em>ad locum</em>).</p><p>The <strong>Ajax Multi-Commentary project</strong> explores the notion of <em>digital multi-commentary</em> by taking the commentary’s tradition of Sophocles’ <em>Ajax </em>as a case study, which consists of about 15 commentaries, written in several language (Latin, English French, German, and Italian) and published between 1835 and 2011. Focusing on the historical and epistemological dimension of this body of commentaries, the project will study the history of this genre and of its exegetic practices, and in particular how the various commentaries have contributed to shaping our reading and understanding of this text. In fact, when considered from a history of science perspective, each commentary is a fossilized testimony of reading and understanding a literary text as a historically-situated intellectual process.</p><p>In order to enable an epistemological study of this corpus of commentaries, a <strong>digital multi-commentary</strong> is being developed to read, compare and analyze this tragedy’s commentary tradition. Layout detection and OCR of the digitized commentaries constitute the first necessary steps for the creation of multi-commentary interfaces for both close and distant reading. Further processing steps will entail the linking of the commentary section (or lemma) with the portion of text it refers to, the alignment of commentaries with one another, as well as the semi-automatic enrichment of the commentary sections (e.g. by means of named entity processing and citation mining).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c18bf0ca5d3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pelagios/introducing-ajax-multi-commentary-3c18bf0ca5d3">Introducing: Ajax Multi-Commentary</a> was originally published in <a href="https://medium.com/pelagios">Pelagios</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Early steps in digitally mapping Pausanias’s Description of Greece]]></title>
            <link>https://medium.com/pelagios/early-steps-in-digitally-mapping-pausaniass-description-of-greece-548301b2a54d?source=rss----3471255e9353---4</link>
            <guid isPermaLink="false">https://medium.com/p/548301b2a54d</guid>
            <category><![CDATA[visualisation]]></category>
            <category><![CDATA[geography]]></category>
            <category><![CDATA[text]]></category>
            <category><![CDATA[linked-data]]></category>
            <category><![CDATA[narrative]]></category>
            <dc:creator><![CDATA[Elton Barker]]></dc:creator>
            <pubDate>Wed, 06 Oct 2021 10:37:39 GMT</pubDate>
            <atom:updated>2021-10-06T08:58:17.168Z</atom:updated>
            <content:encoded><![CDATA[<p>Sometime in the second century CE, Pausanias of Magnesia wrote the <em>Periegesis Hellados</em> (<em>Description of Greece</em>). Representing a unique deep dive into ancient Greece’s built environment to the level of individual statues and paintings, this text projects a tour of the Greek mainland in ten books, from Attica (I) to Phocis (X), taking in a clockwise circuit around the Peloponnese (Figure 1). However, as Pausanias reveals in a rare methodological statement (1.39.3), he records not only the sights (<em>theōrēmata</em>) but also the stories (<em>logoi</em>) about them, whether because something of interest had happened in this or that place or because the person to whom a statue, say, had been dedicated had done something of interest. Cutting across and rerouting the narrative’s “relentless linearity” are Pausanias’s movements in and through <em>time</em>, from the contemporary period of living under Rome to an era when heroes walked the earth, establishing institutions and rituals still practised in Pausanias’s day.</p><p>Figure 1. A map showing the areas by book covered in Pausanias’s <em>Description of Greece</em>, openly licenced from Harvard Library (<a href="https://dash.harvard.edu/handle/1/40939994">https://dash.harvard.edu/handle/1/40939994</a>).</p><figure><img alt="A visualisation showing how the ten books of Pausanias map on to the Greek mainland, starting with Attica (Book 1), going clockwise around the Peloponnese (Books 2–8), and ending in Phocis (Book 10)." src="https://cdn-images-1.medium.com/max/923/0*Zr6MgZr5dLFVVq2D" /></figure><p>In spite of appearances, then, tracing his itinerary around mainland Greece is far from straightforward and presents many challenges to digital mapping. Conventional software like GIS, whose capability of aggregating data by location has made it indispensable for historical geography, is less well equipped to deal with narrative space. In this blog post, I want to sketch out two ways in which the <a href="http://periegesis.org/"><em>Digital Periegesis</em></a> project is bringing to the fore spatial patterns underpinning Pausanias’s text, using Book 1 as a case study, while also developing digital tools and methods for research into textual geographies more broadly. In both cases, we draw on the work of <a href="https://pelagios.org/">Pelagios</a>, the humanities <a href="https://www.ontotext.com/knowledgehub/fundamentals/linked-data-linked-open-data/">Linked Data</a> initiative that is helping domain experts produce resources that can be connected to each other by references to place.</p><p>First, to capture the spatial information in Pausanias’s narrative we use Pelagios’s free open-source tool, <a href="https://recogito.pelagios.org/">Recogito</a>. (For a comprehensive guide to Recogito’s functionality see the <a href="https://github.com/pelagios/pelagios.github.io/wiki">GitHub Tutorial</a>.) For our purposes, it enables us to identify spatial features mentioned in the text — places, objects in space, peoples — and align those references to a global authority file. For Pausanias, such an authority record is provided by the <a href="https://pleiades.stoa.org/">Pleiades gazetteer</a>, which assigns unique stable identifiers (<a href="https://en.wikipedia.org/wiki/Uniform_Resource_Identifier">URIs</a>) for the places of the ancient world. We also use Recogito’s tagging feature to provide more information about the place or object, especially its type — whether it is part of built or physical environment, for example, or whether it is a temple, statue or painting, etc. In addition, we use tags to classify the moments in his narrative when Pausanias pauses his itinerary to relate an account about a particular place, person or event. Rather than using our own modern dating system of BCE/CE to label these shifts in time, we use a broad-brush temporal anchor based on critical moments in Greek history, which would have been recognisable to his readership, such as the Persian or Peloponnesian Wars.</p><p>What does the semantic geo-annotation and tagging of Pausanias allow us to do? Well, first, because of their alignment to gazetteer records, we can map the places in Pausanias in a far more accurate, comprehensive and granular way than was possible before. Figure 2, for example, shows all the places mentioned in the first book of the <em>Periegesis</em>. If we recall that Book I is devoted to a “tour” of Attica (the region around and including Athens), the spatial footprint of the narrative is striking. The book in fact refers to places and peoples from across the Greco-Roman world and beyond, to Britain in the far west to India in the far east.</p><p>Figure 2. Places and objects mentioned in Pausanias’s <em>Periegesis</em> Book 1. Book 1 is about Attica (see Figure 1), right?</p><figure><img alt="A visualisation with the text of Pausanias on the right and a map of the places mentioned in the whole narrative (of Book 1) on the left. The map shows a concentration of places in the area of the Greek mainland and the Aegean Sea, but places are spread over the Mediterranean and beyond." src="https://cdn-images-1.medium.com/max/680/0*Pe0kNMzSRcwhFi4M" /></figure><p>Because of our temporal tagging system, we can visualize the same information in different ways. Consider, for example, Figure 3a, which is filtered using the label “period of the Macedonians”, i.e., when various Macedonian-based powers held hegemony over the Mediterranean — from around “338 BCE”, when Philip of Macedon defeated the combined Greek forces at Chaeronea, to “146 BCE”, when Rome sacked Corinth. Paying particular attention to the “timeline” of the narrative at the bottom right, it’s clear the critical role this period of history plays in Pausanias’s account of Attica, particularly in his description of the space of the Athenian agora (the second and third peaks in highlight on the timeline).</p><p>Figure 3a. Book I places filtered by the temporal label “Macedonian War”, with the section in which Pausanias describes the Athenian agora highlighted in the timeline</p><figure><img alt="The same visualisation as before, only now filtered by the time category “Macedonian Wars”. The map shows places mentioned in relation to this category concentrated especially on the Greek mainland, the Ionian coast (of modern-day Turkey), Rome and Egypt." src="https://cdn-images-1.medium.com/max/680/0*fFhxYN5Qd8dRbzR0" /></figure><p>We may compare this to the map now filtered by the “time of the heroes” — i.e. all those places/objects that Pausanias describes in relation to the heroic age. The heroes are a constant presence, but they especially crowd in as the book nears its end, as Attica’s borders with Megara come under particular scrutiny.</p><p>Figure 3b. Book I places filtered by the temporal label “heroic age”.</p><figure><img alt="The same visualisation as before, only now filtered by the time category “the heroic age”. The map shows places mentioned in relation to this category concentrated especially on the Greek mainland, northern Aegean, the Black Sea and Crete." src="https://cdn-images-1.medium.com/max/679/0*ilQfpRT6vEyr7vte" /></figure><p>These maps have barely scratched the surface of Pausanias’s description, but I want to move on to my second point, which is about the new <a href="http://pelagios.org/peripleo-lite/">Peripleo</a>*, the visualization tool used to create these figures, again developed by Pelagios’s <a href="https://medium.com/u/a5bca09bc68e">Rainer Simon</a>. To a certain extent, Figures 2 and 3 could have been created in a GIS — after all GIS specializes in showing spatial breadth and density. But being able to feature the text within the mapping interface already provides important additional functionality. This aspect really comes into its own when switching from the “map all places” mode to “places in view” (see Figure 4). As well as seeing all places mentioned in the book, you can read through the narrative and see the places mentioned section-by-section. Such a view is particularly powerful for a text like Pausanias’s, which is, for a large part, “itinerary” based. So, you can “follow” Pausanias’s movements through the civic space of Athens.</p><p>Figure 4. The itinerary view, showing Pausanias’s route through the Athenian agora</p><figure><img alt="A visusalisation, now showing a particular section of the text and the places mentioned within that section alongside it. The passage in focus is Book 1.8.1, the Athenian agora, and the map sketches out Pausanias’s journey through it." src="https://cdn-images-1.medium.com/max/679/0*q1fN3LMdTTJqTac_" /></figure><p>But that’s not all. We may recall that marking up the place references in Pausanias using Recogito involved not only identifying their mention in the text but also their alignment to a global authority — specifically a record of a place in a gazetteer with a unique identifier or URI. By virtue of this two-step process of <a href="https://www.ontotext.com/knowledgehub/fundamentals/semantic-annotation/">semantic annotation</a>, we can publish our work as Linked Data.</p><p>Peripleo can take advantage of the research possibilities this format provides in at least two ways. First, you can link from Pausanias’s text to other online resources which refer to the same places mentioned and which have also been marked up as Linked Data (i.e. have used the same gazetteer URI for the places mentioned). Figure 5 provides a very simple example. It shows a building mentioned by Pausanias — the Erechtheion — which was located on the Acropolis (Figure 5a). By virtue of having aligned this reference to the appropriate record in Pleiades means that not only can we locate it on a map; we can also link to its <a href="https://pleiades.stoa.org/places/750203268">record in Pleiades</a>. And, not only that: we can also access the information found there, including links to further resources produced and curated by other online resources (Figure 5b). In this way, we can better contextualize the reference in Pausanias and start to bring together other information that could have a bearing on our understanding of its description and function within Pausanias’s narrative.</p><p>Figure 5a. Linking from the reference in Pausanias…</p><figure><img alt="A visualisation showing Pausanias’s text on the right (1.26.5) in his description of the Athenian Acropolis, and a map of the places mentioned in that passage, highlighting the Erechtheion." src="https://cdn-images-1.medium.com/max/1024/0*q0lKaOWaOifqOoGO" /></figure><p>Figure 5b. …to the record in Pleiades</p><figure><img alt="The entry on the Erechtheion in the Pleiades gazetteer for the ancient world, including a full description of the monument and further bibliography." src="https://cdn-images-1.medium.com/max/987/0*BybHploWAezyQndi" /></figure><p>Second, more interestingly (and potentially more radical), by clicking on the Pelagios Network logo in the bottom left of the map interface, you can reveal other places <em>not mentioned</em> in Pausanias, but which are found in the vicinity of those he does describe. (They show up because these resources have also been produced as Linked Data, using Pleaides URIs.) For example, Figure 6 shows the “other places” located in the vicinity of Pausanias’s description (at 1.18.7) of the famous Temple of Olympian Zeus in Athens. Notable among these is the equally famous Arch of Hadrian, which Pausanias fails to mention, even though he would have had to walk right past it to get to the Temple of Zeus! As the classicist, <a href="https://zenon.dainst.org/Record/001455144/TOC">Tim Whitmarsh has argued</a>, Hadrian’s arch was critical in demarcating Athens both spatially and temporally, drawing a distinction in the very topography of Athens between its ancient western part (or “city of Theseus”) and its Roman present in the east (the “city of Hadrian”). By erasing this arch from (his) record, Pausanias is implicitly deconstructing and reconfiguring the imperial space of Athens.</p><figure><img alt="A visualisation showing Pausanias’s description of the Temple of Olympian Zeus in Athens (1.18.7) and a map of the places mentioned in that passage. In addition, however, the map also shows the other monuments and objects that appear in the material record of that area (as documented by other resource providers, including the excavations of the American School at Athens), which Pausanias doesn’t mention. This includes the Arch of Hadrian." src="https://cdn-images-1.medium.com/max/679/0*AWdOEXh5HrwCyMwW" /></figure><p>With this last example, we are getting a little closer to better exploiting the power of linked data, where we’ll be able to compare Pausanias’s description of objects to other resources about them and start to note and explore the gaps, the silences more systematically.</p><p>To sum up: both Recogito and Peripleo are opensource tools, which are free to use, don’t require any specialist software to be downloaded, and work in your browser. Moreover, both are really easy to use. (I say that with some confidence, since I can use them!) On the one hand, Recogito enables you to do semantic geo-annotation for the purposes of producing linked open data. But, while it’s designed for semantically annotating place information in a range of digital documents (not only texts, but also maps and databases), you can also use it to markup many different kinds of information, notably (but not limited to) people and events. On the other hand, Peripleo enables you to discover, search and explore those resources that have been published as linked open (geo)data. In other words, it can help you “trace” the historical representations of place or objects. In fact, the Digital Periegesis example in Peripleo is one of the first implementations of the emerging “<a href="https://github.com/LinkedPasts/linked-traces-format">Linked Traces</a>” format, developed by <a href="https://medium.com/u/9f5695a520af">Karl Grossner</a> of the <a href="https://whgazetteer.org/">World Historical Gazetteer</a>’ in collaboration with Pelagios’s <a href="https://medium.com/u/a5bca09bc68e">Rainer Simon</a>, to enable the tracing of not only textual geographies but also the histories of artefacts, peoples and events in space. (The idea is that eventually we will be able to go seamlessly from annotating in Recogito to using Peripleo to visualize our annotations and to link to any other resources produced using the same Linked Traces format, which we may want to compare and explore.)</p><p>One final take-home point. It’s the nature of digital resources that applications don’t stand still but continually evolve. This is one reason why development is no longer planned or run by a small core-team relying on external funding (“Pelagios the project”) but is now in the hands of the community (the Partners of the <a href="https://medium.com/u/f96d74f645aa">Pelagios</a>Network). The new Peripleo has been made possible through a small grant (£5K) from my institution (The Open University), which was used to fund the creation of a lightweight visualization environment for the annotations that we made on the Digital Periegesis, as one of the Partner projects of the Pelagios Network. Work on Recogito is proceeding in a similar way (i.e. it’s now funded by individual Pelagios Partners), and is already leading to the exciting new development of embeddable annotation interfaces Recogito, in which we won’t take our data to Recogito so much as take Recogito to our data. For annotating images, this work is going under the name of <a href="https://recogito.github.io/annotorious/">Annotorious</a>, while for texts it’s <a href="https://github.com/recogito/recogito-js">RecogitoJS</a>. In what ways and directions these tools and methods for producing and using Linked (geo)Data will develop further will be up to you.</p><p>*A short note on Peripleo. The old <a href="https://peripleo.pelagios.org/">Peripleo</a> (developed in 2017) suffered from being too closely identified with Pelagios, as if it were somehow the “telos” of our initiative. But Peripleo was only ever (meant to be) a demonstrator of what you could do if data were linked. As a result, the datasets “in” Peripleo are random. It’s true that there’s a preponderance of ancient world resources, because they’re the people with whom we worked most closely at the beginning. But essentially we worked with anyone who approached us! And many people did approach us, and continue to do so, because Peripleo is a nice visualisation of linked datasets (as well as providing the spatial footprint of collections). Yet the randomness of the resources meant that apples were being compared (/linked) to pears. Moreover, there was a more pressing problem. Pelagios was never meant to be a portal or an aggregator — “the one ring to rule them all” — where people went to explore interconnected resources. This for us is the very antithesis to the idea of linked data as decentred, non-hierarchical, community directed. Hence the transformation of Pelagios “the project” into the community owned and directed PelagiosNetwork — since in our view linked data is as much about linking people as it is about linking resources. Which brings me back to the new Peripleo. Our view is that there won’t be “one” Peripleo. Rather, it’ll be a robust but flexible (web browser) app that can be used to bring together the linked data resources that any one person is interested in exploring further.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=548301b2a54d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pelagios/early-steps-in-digitally-mapping-pausaniass-description-of-greece-548301b2a54d">Early steps in digitally mapping Pausanias’s Description of Greece</a> was originally published in <a href="https://medium.com/pelagios">Pelagios</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing: TimeCapsule]]></title>
            <link>https://medium.com/pelagios/introducing-timecapsule-3468a281438b?source=rss----3471255e9353---4</link>
            <guid isPermaLink="false">https://medium.com/p/3468a281438b</guid>
            <category><![CDATA[time]]></category>
            <category><![CDATA[network-partner]]></category>
            <category><![CDATA[visualization]]></category>
            <dc:creator><![CDATA[Pelagios]]></dc:creator>
            <pubDate>Mon, 27 Sep 2021 12:23:34 GMT</pubDate>
            <atom:updated>2021-09-27T12:29:08.482Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MAKPMBFLT6BkZ210idKAyQ.jpeg" /><figcaption>image credit: Adrian Hernandez on Unsplash</figcaption></figure><p>TimeCapsule is a project directed by Johanna Drucker at UCLA, Department of Information Studies and Design|Media Arts.</p><h4>Overview</h4><p>This project supports humanistic and hermeneutic approaches to modeling various modes of temporality and chronology by creating a graphical platform in which to create, display, analyze, and interpret temporal schema. The platform is designed to produce as well as display structured data, and consists of a paintbox of basic components (lines, intervals, points) with attributes (extension, inflections, scale) that can be customized to fit domain-specific and project-driven needs. The modes of temporal and chronological modeling include experiential, narrative, biographical, and discursive sources of information based in texts, data, and images that are part of the human cultural record. The guiding principle of the project is that time-keeping systems from the empirical sciences are not suited to the analysis and representation of interpretative work in the humanities.</p><h4>Inflections: Interpretative interactions with data</h4><p>If we consider data practice a central concern for the humanities, we need to find ways to account for the interpretive steps carried out with computational resources. At the moment, the discursive engagement with digital interfaces is largely carried out via textually annotated screenshots and narrated screen recordings. There is only limited support to attach arguments to specific display states or data elements. Since interactivity and thus dynamic display are crucial qualities of digital interfaces there is a need to connect the changeable character of interfaces with humanistic practices. For this purpose, we propose inflection as the intentional alteration of the display and underlying data to make a point, advance a story, highlight evidence, etc. Other than the existing interaction techniques provided for data visualization, inflections are interpretive and discursive interactions that are meant to be saved, shared, and shown. To realize this vision, interpretative capabilities need to be baked into the stack, whose layers could be threefold into: interface, concept, and storage. Inflections are performed in the interface, reflected at the conceptual level, and saved and shared via networked storage. The realization of inflection requires collaborative and interdisciplinary design, conceptualization, and prototyping.</p><h4>Work outline</h4><p>The work that needs doing is on three levels:</p><ul><li>interface: ideate visualization/interaction designs for different inflections</li><li>concept: think through, talk over, and write down</li><li>storage: engineer an efficient backend, settle on formats</li></ul><p>The three levels:</p><p>Interface level:</p><p>Workspace: Contains the basic paintbox of graphical tools for doing interpretative work by creating timelines directly or from data, but supporting interpretative modification through inflections, attributes, and other features. The basic components are lines, points, intervals that support actions by the user and encode behaviors (e.g. elastic timelines, variable metrics, causal relations). The goal is to create an intuitive, simple but extensible, graphical system linked to stored, modifiable, data structures.</p><p>Potential inflections with the respective interactions (behaviors of the elements and actions by the user)</p><p>· Present: add, remove, hide</p><p>· Emphasize: highlight, increase size, increase saliency</p><p>· Aggregate: group or collapse multiple items</p><p>· Focus: Zoom in, filter display</p><p>· Connect: Add links, move closer together</p><p>· Interact: Attract, repel, absorb, vary dependently in other ways</p><p>Conceptual level:</p><p>These are the descriptive, formal schema for understanding experiential,</p><p>narrative, discursive and chronological temporalities that support analysis and study of project and discipline specific models. The ChronoJSON outline is one possible direction for developing this facet of the research.</p><p>Storage level:</p><p>Data: These are the structured data formats for storage, transfer, analysis, display of temporal schema and express the graphical features of the workspace and the conceptual components of descriptive or analytic schema in a formal way. These include mark-up schemes and other structured data.</p><p>Library: This is the collection of historical and contemporary visualizations and text documents that serve as research objects and from which graphical structures, conceptual schema, and/or data structures are abstracted for interpretation and study.</p><p>Each of these components is based on formal structures that allow them to be integrated in the workspace, cross-walked to other data schemes, and customized for individual projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3468a281438b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pelagios/introducing-timecapsule-3468a281438b">Introducing: TimeCapsule</a> was originally published in <a href="https://medium.com/pelagios">Pelagios</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond Translation: Building Better Greek Scholars]]></title>
            <link>https://medium.com/pelagios/beyond-translation-building-better-greek-scholars-561ab331a1bc?source=rss----3471255e9353---4</link>
            <guid isPermaLink="false">https://medium.com/p/561ab331a1bc</guid>
            <category><![CDATA[visualisation]]></category>
            <category><![CDATA[recogito]]></category>
            <category><![CDATA[the-odyssey]]></category>
            <category><![CDATA[spatial-humanities]]></category>
            <dc:creator><![CDATA[Pelagios]]></dc:creator>
            <pubDate>Thu, 02 Sep 2021 08:40:25 GMT</pubDate>
            <atom:updated>2021-09-03T12:52:42.111Z</atom:updated>
            <content:encoded><![CDATA[<p>by Josh Kemp</p><p>Before embarking on my most recent project, I was honored to have the opportunity to work with <a href="https://recogito.pelagios.org/">Recogi</a>to once before — mapping the Catalog of Ships passage from Homer’s <em>Iliad </em>(2.494–759). This is an accessible text due to the high volume of locations where Achaeans sailed from, so it gave a great example of the capabilities of the geo-referencing function of Recogito. I was immediately engaged with the platform and hoped to work with it again, so I jumped at the chance to tackle the <em>Odyssey</em> as a Summer 2021 Research Fellow through the generous funding of the Furman University Office of Undergraduate Research, under the supervision of Dr. Chiara Palladino.</p><p>The goal was to have a large set of data that could allow an in-depth exploration of the <em>Odyssey</em>’s peoples and places: I used Recogito to annotate the text, and then exported the resulting data into the <a href="https://beyond-translation.scaife-viewer.org/">Scaife Viewer 2.0</a>, creating a publicly available integrated version of the text in the original Ancient Greek, with maps and links for all named entities. The <a href="https://scaife.perseus.org/">Scaife Viewer</a> has been an essential element of my journey learning Attic Greek, and in the spirit of “passing it on” I thought it could be very beneficial to add annotation data to help the next generation of students approach the <em>Odyssey</em> from the original Greek</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nu_wVoPoBMKRHflWe7Lz2g.png" /><figcaption><em>Figure 1. The Scaife Viewer features helpful learning tools such as side-by-side display of the Greek and English texts (this is Murray’s Greek and English editions).</em></figcaption></figure><p>I successfully combed all twenty-four books of the <em>Odyssey</em>. I used the 1919 Ancient Greek edition edited by A.T. Murray, Vols. 1–2 (available at</p><p><a href="https://scaife.perseus.org/reader/urn:cts:greekLit:tlg0012.tlg002.perseus-grc2">https://scaife.perseus.org/reader/urn:cts:greekLit:tlg0012.tlg002.perseus-grc2</a>), which was imported book by book from the Scaife Viewer using the Recogito CTS service. I then proceeded by systematically annotating all named entities in each book.</p><p>There were three different entity types I annotated: places (both real and mythological), ethnonyms, and personal names. Tagging places and ethnonyms derived from different regions on a map together was quite interesting, especially considering that I annotated each book separately. This gave me the opportunity to see where the story took place as it progressed across each book, which can be beneficial for students attempting to visualize Odysseus’ journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/1*tpSZl7XbDYLwqXVyHS3RgA.png" /><figcaption><em>Figure 2. Here is an example map from Book III, which predominantly features the retelling of the Trojan War.</em></figcaption></figure><p>Any student that is studying the <em>Odyssey</em> probably has a working knowledge of the Greek gods and other important mythological figures, yet this is an epic with nine different characters that have names beginning with “Eury-”. This is just an example of the hundreds of characters named across all twenty-four books, some of whom are only mentioned once or twice. Even with characters who do little to impact the plot, I understood that there could be great benefit from providing background information. I created a separate vocabulary file by manually matching people in the <em>Odyssey </em>with the corresponding Wikipedia entries and used the “Tagging Vocabulary” feature in Recogito to create an authoritative tagset that I used to annotate every person in the text. Some minor characters (such as suitors whose only mentions came when Odysseus or his companions killed them) did not have a unique Wikipedia entry, but any other occurrence was matched with a link that would take the reader directly to the appropriate page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*qAdQGz6UuJHQkLeX4Z8dRw.png" /><figcaption><em>Figure 3. This is the complete tag list from Book III. Since Telemachus is with Nestor in Pylos hearing stories of his father’s efforts in the Trojan War, they are the two most mentioned characters.</em></figcaption></figure><p>The goal of the project is without a doubt accessibility. There have been many maps of Odysseus’ journey, and anyone can research a character that they are unfamiliar with, but I wanted to contribute to the development of a tool that makes students comfortable with and excited about learning Attic Greek by studying the <em>Odyssey</em>. Therefore, after completing the annotations, I exported the data from Recogito and sent them to the <a href="https://scaife.perseus.org/about">Scaife Viewer team</a>, which is currently working on Scaife 2.0, a new reading interface for ancient texts that integrates multiple annotation types, including translation alignment, metrical annotation, syntax trees, grammatical information, and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ggQYsFd-jNStsoPli8LLZA.png" /><figcaption><em>Figure 4. This example from Odyssey 1.1–10 contains two named entities — Troy and the Titan Hyperion.</em></figcaption></figure><p>The new interface, previously sponsored through a Mellon Foundation Grant, is currently being developed within the framework of the NEH-funded <em>Beyond Translation</em> project. The resulting interface integrates the text with all the data resulting from my annotations: it enables the reader to visualize personal and place names in the original ancient Greek, to explore a map of all the places mentioned in each passage, and to gather additional information about people named through our Wikipedia references.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*WwmR5yEx_FAj0je9wxRP5w.png" /><figcaption><em>Figure 5. An overview of the map on the side, with a list of named entities that appear in the passage.</em></figcaption></figure><p>Having geographical, historical, and the Scaife lexicon’s grammatical information all in the same module can provide that accessible learning environment, and you can find it <a href="https://beyond-translation.scaife-viewer.org/reader/urn:cts:greekLit:tlg0012.tlg002.perseus-grc2:1?mode=named-entities&amp;rs=mapStateVertical">here</a>.</p><p>Author: Josh Kemp, Classics major, Undergraduate. Furman University.</p><p>Contacts: Josh <a href="/service/mailto:josh.kemp@furman.edu">josh.kemp@furman.edu</a>; <br>Chiara Palladino <a href="/service/mailto:chiara.palladino@furman.edu">chiara.palladino@furman.edu</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=561ab331a1bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pelagios/beyond-translation-building-better-greek-scholars-561ab331a1bc">Beyond Translation: Building Better Greek Scholars</a> was originally published in <a href="https://medium.com/pelagios">Pelagios</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing the Manar al-Athar Photo-Archive]]></title>
            <link>https://medium.com/pelagios/introducing-the-manar-al-athar-photo-archive-a1739af87853?source=rss----3471255e9353---4</link>
            <guid isPermaLink="false">https://medium.com/p/a1739af87853</guid>
            <category><![CDATA[photo-archives]]></category>
            <category><![CDATA[roman-and-islamic-history]]></category>
            <category><![CDATA[archaeology]]></category>
            <category><![CDATA[gazetteer]]></category>
            <category><![CDATA[linked-open-data]]></category>
            <dc:creator><![CDATA[Pelagios]]></dc:creator>
            <pubDate>Mon, 23 Aug 2021 10:12:24 GMT</pubDate>
            <atom:updated>2021-08-23T10:16:52.129Z</atom:updated>
            <content:encoded><![CDATA[<p>written by Miranda Williams</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q7KD74YLdN9jgxqF3vi8wA.jpeg" /><figcaption>Screenshot of the Manar Al-Athar archive main page</figcaption></figure><p><a href="http://www.manar-al-athar.ox.ac.uk/">The Manar al-Athar Photo-Archive</a>, based in the Faculty of Classics at the University of Oxford, provides high resolution, searchable images for teaching, research, and publication. These images of archaeological sites and buildings, cover the areas of the former Roman empire which later came under Islamic rule, such as Syro-Palestine/the Levant, Egypt and North Africa, as well as some adjoining regions. The chronological range is from circa 300 BCE through the Islamic period.</p><p>The photo-archive is structured geographically around curated, sequenced photo-sets for individual sites and/or buildings which allow users to understand a whole building or site and visually place key details in context. Each photograph is stored with its description, credit line, and other information in its metadata, which is downloaded together with the image file and is visible in applications such as Adobe Bridge or Lightroom. Photographs of material in majority Arabic speaking countries are labelled bilingually, in both Arabic and English, to facilitate local use.</p><p>In collaboration with Pelagios, Manar al-Athar intends to embed GPS coordinates, alternative site names and Uniform Resource Identifiers (URIs) for sites for which the photo-archive holds photographs into the image metadata via a bespoke script and interface which will enable the semi-automatic collation of this data. The data will then be made accessible to users both via the Manar al-Athar website and via the download of individual image files. Embedding this information will also facilitate the location of individual Manar al-Athar resources through web searches as well as the creation of a map interface for the website. The addition of this supplementary metadata to Manar al-Athar photographs will be undertaken progressively, one geographical region at a time, starting with Libya, a region for which Manar al-Athar is currently substantially expanding its coverage.</p><p>We look forward to collaborating with the Pelagios Network on this project, and learning from other network partners.</p><p>Contact us at: <a href="/service/mailto:manar@classics.ox.ac.uk">manar@classics.ox.ac.uk</a></p><p>Follow us on social media: <a href="https://twitter.com/ManarAlAthar">@ManarAlAthar</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1739af87853" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pelagios/introducing-the-manar-al-athar-photo-archive-a1739af87853">Introducing the Manar al-Athar Photo-Archive</a> was originally published in <a href="https://medium.com/pelagios">Pelagios</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[nodegoat: Creating Connected Data]]></title>
            <link>https://medium.com/pelagios/nodegoat-creating-connected-data-5020e7028ebe?source=rss----3471255e9353---4</link>
            <guid isPermaLink="false">https://medium.com/p/5020e7028ebe</guid>
            <category><![CDATA[data-modeling]]></category>
            <category><![CDATA[data-mapping]]></category>
            <category><![CDATA[gazetteer]]></category>
            <category><![CDATA[linked-data]]></category>
            <dc:creator><![CDATA[LAB1100]]></dc:creator>
            <pubDate>Mon, 09 Aug 2021 10:12:45 GMT</pubDate>
            <atom:updated>2021-08-09T10:12:45.864Z</atom:updated>
            <content:encoded><![CDATA[<p>nodegoat is a web-based research environment for the humanities. nodegoat allows scholars to build datasets based on their own data model and offers relational modes of analysis with spatial and chronological forms of contextualisation. By combining these elements within one environment, scholars are able to instantly process, analyse and visualise complex datasets relationally, diachronically and spatially.</p><p>Research projects use nodegoat to store, map, and analyse their data. Some projects have a focused scope, like the ‘<a href="https://nodegoat.net/usecase.p/372.m/29/mapping-visions-of-rome">Mapping Visions of Rome</a>’ project of Susanna de Beer which maps an inner city literary landscape of Rome based on (Renaissance) Latin poetry. Other projects take a much broader scope, like Pelagios member ‘<a href="https://medium.com/pelagios/manto-mapping-greek-myth-bbcfcbfe356">MANTO</a>’ which builds a digital dataset of Greek myth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vQ8M5YDO7Zu8GbCBJH-P_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WiraR2_7sB5o3MR7VdGNiQ.png" /><figcaption>Susanna de Beer has been using nodegoat to text tag (Renaissance) Latin poetry related to the city and symbol of Rome. As a spin-off of this project she published the website ‘<a href="https://devereeuwigdestad.nl/">De vereeuwigde stad</a>’ (‘The eternal city’) that can be used as an interactive tour guide for exploring the literary landscape of Rome.</figcaption></figure><p>nodegoat allows scholars to work on their data in a platform independent manner. Data can be exported to open formats like CSV or ODT. RESTful APIs can be configured to share data as JSON or JSON-LD. These features will help to integrate data that has been created in nodegoat projects with other projects in the Pelagios network.</p><p>nodegoat is used by many researchers to build datasets that did not exist before. We have added features to make connecting this newly created data to other resources as straightforward as possible. nodegoat can be configured to connect to any API or SPARQL endpoint to retrieve URIs. Once these connections are in place, data from these endpoints can be fetched and stored in nodegoat.</p><p>Creating a project specific gazetteer is a good use case for these Linked Data connectivity features. When a project starts to create their data collection in nodegoat, they can either ingest spatial data from resources like Pleiades, the iDAI Gazetteer, or GeoNames, or they enter new locations from their own sources and connect these to existing spatial resources. The API of the iDAI Gazetteer can be configured as a Linked Data Resource in nodegoat so this data can be queried from within the nodegoat interface. This <a href="https://nodegoat.net/guides/externalidentifiers">nodegoat Guide</a> describes how such a connection can be set up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JsU0YDjiJh_SeDbwisJqYw.png" /><figcaption>This Object Descriptions uses a Linked Data Resource that <a href="https://gazetteer.dainst.org/search.json?q=forum%20hadriani&amp;type=queryString&amp;offset=0&amp;limit=10">sends requests to the iDAI Gazettee</a>r based on the entered input.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5020e7028ebe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pelagios/nodegoat-creating-connected-data-5020e7028ebe">nodegoat: Creating Connected Data</a> was originally published in <a href="https://medium.com/pelagios">Pelagios</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MANTO: mapping Greek myth]]></title>
            <link>https://medium.com/pelagios/manto-mapping-greek-myth-bbcfcbfe356?source=rss----3471255e9353---4</link>
            <guid isPermaLink="false">https://medium.com/p/bbcfcbfe356</guid>
            <category><![CDATA[mythology]]></category>
            <category><![CDATA[gazetteer]]></category>
            <category><![CDATA[linked-open-geodata]]></category>
            <category><![CDATA[linked-open-data]]></category>
            <dc:creator><![CDATA[Rebecca Kahn]]></dc:creator>
            <pubDate>Mon, 02 Aug 2021 12:16:23 GMT</pubDate>
            <atom:updated>2021-08-02T12:40:00.831Z</atom:updated>
            <content:encoded><![CDATA[<p>Written by Greta Hawes and Scott Smith</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*IUB3YKfALTgSXb7Akaeb1Q.png" /></figure><p>In its original conception <a href="https://www.manto-myth.org/manto">MANTO</a> was, and remains, an initiative to model the data of Greek myth and to map both its relevance to and its impact on the landscape of the ancient Mediterranean.</p><p>Like many, this project developed out of frustration and sought to fill a hole: there wasn’t any way of easily seeing the places associated with various Greek heroes, or all the myths associated with particular places. In a process that took well over a year, we developed a standardised vocabulary for expressing the many and various ways that myths, places and objects interact, and have so far used this to capture data from four major sources of ancient myth: Homer’s <em>Iliad, </em>Hesiod’s <em>Theogony, </em>Apollodoros’ <em>Library, </em>and Pausanias’ <em>Description of Greece. </em>We are in the process of adding or refining the data from other works as well (e.g. tragedy, Apollonios’ <em>Argonautica</em>).</p><p>Somewhat ironically given our frustration at the difficulties organising mythic data by place (rather than the more traditional approach of organising them by people), one of the most formidable aspects of the project so far has been creating an authoritative digital dataset of mythical names. Our list now comprises some 3600 individuals and groups, <a href="https://www.manto-myth.org/blog/a-dataset-of-mythical-names-with-stable-uris">paired with stable URIs</a>. MANTO’s entities are now, thanks to the work of Brady Kiesling, <a href="https://www.wikidata.org/wiki/Property:P9736">a Wikidata property</a>. Further discussion about dealing with mythical entities can be found in this <a href="https://www.manto-myth.org/blog">blog</a> about the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D4qeUDMEUshjf4vH0SmV2Q.png" /></figure><p>This is a truly collaborative project. We have benefitted from the advice and support of many others in Classics and Digital Humanities, including many members of the Pelagios community. We have also been fortunate to have had a group of patient and enthusiastic students working alongside us collecting data and helping refine the data structure.</p><p>MANTO is built in <a href="https://nodegoat.net/">Nodegoat</a>, a new Pelagios partner. Finding this platform was a game-changer for the project. Its platform provides the ideal data collection environment: reliable, cost-effective, and precisely customisable to our specific needs. The public interface for MANTO <a href="https://manto.unh.edu/viewer.p/60/2616/scenario/1/geo">is now available</a>, and we welcome feedback.</p><p>Finally, a word about unintended consequences. Although our modest goal was to provide a way to visualise the mythical storyworld, MANTO has become something larger, almost as a by-product of our original aims: a modern and fully digital mythographical encyclopedia that can be manipulated by users to collect the data they want. Its usefulness, we think, will grow as more texts are included in the database, and we are hopeful that both scholars of the ancient world and other enthusiasts will find something of interest in our work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbcfcbfe356" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pelagios/manto-mapping-greek-myth-bbcfcbfe356">MANTO: mapping Greek myth</a> was originally published in <a href="https://medium.com/pelagios">Pelagios</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pelagios Introduces: Activity Lead Virginia Boyero- on annotation, games and history.]]></title>
            <link>https://medium.com/pelagios/pelagios-introduces-activity-lead-virginia-boyero-on-annotation-games-and-history-e4e3ad3ea7f2?source=rss----3471255e9353---4</link>
            <guid isPermaLink="false">https://medium.com/p/e4e3ad3ea7f2</guid>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[pelagios-introduces]]></category>
            <category><![CDATA[semantic-annotation]]></category>
            <dc:creator><![CDATA[Pelagios]]></dc:creator>
            <pubDate>Mon, 12 Jul 2021 08:07:20 GMT</pubDate>
            <atom:updated>2021-07-12T13:13:23.813Z</atom:updated>
            <content:encoded><![CDATA[<p>By Virginia Boyero</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*3x5mI8_9Pe1WsFHWt2j2bA.jpeg" /><figcaption>The 2019 exhibition <a href="https://www.imarabe.org/en/exhibitions/age-old-cities">Age Old Cities</a>, at the Arab World Institute, Paris, invited visitors to explore four ancient cities via virtual reality tools originally developed for gaming.</figcaption></figure><p>The <a href="https://pelagios.org/activities/annotation/">Annotation activity</a> is one of the core elements of the Pelagios network and I was privileged to be asked to lead it for a while as its coordinator. My background is mixed, originally a historian with an inclination for archaeology, who then turned video game developer. Somewhat unexpectedly I have spent most of my professional career in games production, hooked on the fast-paced multidisciplinary development of AAA games such as <a href="https://en.wikipedia.org/wiki/Tom_Clancy%27s_The_Division">The Division</a> and <a href="https://en.wikipedia.org/wiki/Tom_Clancy%27s_The_Division_2">The Division 2</a>. During the last few years I managed the Narrative, Audio and Localization teams, with very close and often conflicting dependencies that span from the early story conception to the final touches of translation and voice recordings. Making a plan that fits all puzzle pieces together, on budget and on schedule are some of the main challenges in games production, and there are many processes that can be applied to digital humanities tools development. Working with distributed teams is no longer unusual; coordinating progress at regular periods such as in between activity meetings is not very different from working in sprints; reviewing the initiatives taken by the different projects linked to Annotation at regular intervals is important to keep a central vision.</p><p>It might not be easy to achieve in reality, but increasing collaboration between game studios and institutions can lead to extraordinary tools and user experiences in the digital humanities and heritage sectors, uniting the expertise and efficient production cycles from software development with the immense content and defined applications in academia and museums. A few <a href="https://store.steampowered.com/app/1025500/AgeOld_Cities_VR/">examples</a> show the type of <a href="https://store.steampowered.com/app/1341280/NotreDame_de_Paris_Journey_Back_in_Time/">experiences</a> that can be achieved, and the possibilities are endless.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4e3ad3ea7f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pelagios/pelagios-introduces-activity-lead-virginia-boyero-on-annotation-games-and-history-e4e3ad3ea7f2">Pelagios Introduces: Activity Lead Virginia Boyero- on annotation, games and history.</a> was originally published in <a href="https://medium.com/pelagios">Pelagios</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Janelle Jenstad on Urban Gazetteer Design]]></title>
            <link>https://medium.com/pelagios/janelle-jenstad-on-urban-gazetteer-design-698852e55bea?source=rss----3471255e9353---4</link>
            <guid isPermaLink="false">https://medium.com/p/698852e55bea</guid>
            <category><![CDATA[history]]></category>
            <category><![CDATA[london]]></category>
            <category><![CDATA[gazetteer]]></category>
            <dc:creator><![CDATA[Karl Grossner]]></dc:creator>
            <pubDate>Sat, 19 Sep 2020 17:21:29 GMT</pubDate>
            <atom:updated>2020-09-20T19:11:59.556Z</atom:updated>
            <content:encoded><![CDATA[<p>On September 9th, the <a href="https://pelagios.org/activities/gazetteers/">Pelagios Network Gazetteer Activity</a> group hosted an online talk by <a href="https://janellejenstad.com/">Dr. Janelle Jenstad</a> of the University of Victoria, titled “<em>Urban Gazetteer Design: Principles for Disambiguating Places and Toponyms.</em>” Dr. Jenstad shared experiences and lessons learned directing development of the <a href="https://mapoflondon.uvic.ca/"><strong>Map of Early Modern London</strong></a><strong> </strong>project she initiated in 2009, and her talk was followed by an hour or so of fruitful discussion.</p><p>Some notes about questions and points raised in the discussion appear below the video and PDF links, and there are links to relevant projects below that.</p><p>The video recording here begins with slide 6, a minute or so in. The full PDF slide deck is available below.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F459727944%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F459727944&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F960453760_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/b4ac3a1821c54a22df7bd9d2aafad6b4/href">https://medium.com/media/b4ac3a1821c54a22df7bd9d2aafad6b4/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*88ZQKiD9zgRzUj_xzpVM6A.png" /><figcaption><a href="https://drive.google.com/file/d/19rcraG8eTzjVS3ZgyMn_sVp_ALwy-Nxa/view?usp=sharing">PDF slides</a></figcaption></figure><h3>Questions and discussion notes</h3><p><em>NOTE: Questions and answers are paraphrased and not direct quotes</em></p><p><strong>Q</strong>: To what extent are the design principles for disambiguating Places and Toponyms specific to *urban* gazetteers, as opposed to gazetteers in general? <br><strong>A</strong>: I suspect that the need to disambiguate increases as place becomes smaller and more granular. Repeated names would be more common.</p><p><strong>Q</strong>: How do you deal with places that change? Both the city itself but also spaces within the city, especially districts, buildings, roads, rivers?<br><strong>A</strong>: In MoEML, in many cases this is handled with multiple records for the same location <br><strong>Comment</strong>: Would temporal scoping help? E.g. in <a href="https://github.com/LinkedPasts/linked-places">Linked Places format</a>, temporal scoping is possible for places as a whole, for geometries, place types, and for relations to other places.</p><p><strong>Q</strong>: To what extent do you think it is the case that Space-Time <em>&lt;SameAs&gt;</em> Place-Time? E.g. “This was the Thames, but now the city has been built over it”: space becomes different places over time.<br><strong>A</strong>: Space-Time <strong>is not</strong> <em>&lt;SameAs&gt;</em> Place-Time</p><p><strong>Q</strong>: Have you faced the issue of verticality within places? that is, do different levels within the same building need to be disambiguated and how to do that?<br><strong>A</strong>: A problem with GIS is it captures x, y, but not a good job of capturing z. London now 14 feet higher than in medieval times. Capture “Feet above sea level?”<br><strong>Comment</strong>: Perhaps a “level filter” for buildings would be useful</p><p><strong>Q</strong>: Would you be interested in turning MoEML also into a kind of ontology/controlled vocabulary of London place names that other projects could link to and share? (like the pleiades gazetteer for pelagios/peripleo).<br><strong>A</strong>: Absolutely. Note that place data from MoEML is already a gazetteer option within Pelagios’ <a href="http://recogito.pelagios.org/">Recogito annotation platform</a>. Also, MoEML has a published controlled vocabulary, developed since 2005.<br><strong>Comment</strong>: MoEML as linked data is used for the <a href="https://reademed.mpiwg-berlin.mpg.de/street/ludgate-street-london">Reading Early Medicine</a> database</p><p><strong>Comment thread</strong>: Indigenous names for places are often absent in official records; some places are apparently unnamed, but are in fact named<br>[Bill Pascoe]: <a href="http://tlcmap.org/ghap/">Gazetteer of Historical Australian Placenames</a> “hoping to enable decolonisation of the gazetteer by enabling user contributions.” <br><strong>CF</strong>: Reuben Rose-Redwood’s scholarship on toponymy and indigenous placenames (and pseudo-indigenous toponyms like “the Salish Sea”)<br><strong>CF</strong>: the work of John E. Bishop who has done quite valuable research on this question with the ‘James Bay’ Cree in North Central Turtle Island.</p><p><strong>Q</strong>: Is there a correlation between particular place types and particular problem types? Is it possible to frame toward building best practices?<br><strong>A</strong>: This talk in part frames issues this way; see the slides on challenges of ‘platial’ characteristics</p><h3>Relevant urban historical project links</h3><ul><li><a href="https://druid.datalegend.net/ATM-DEMO/ATM-CLARIAH-DEMO">Amsterdam Time Machine</a></li><li>In <a href="https://reademed.mpiwg--berlin.mpg.de/">Reading Early Medicine</a> project (by Elaine Leong and Mary Fissell) we have place information from imprints of early modern books and we would like to link those to a map like MoEML (and to other projects talking about the same places).</li><li>In the <a href="http://periegesis.org/">Digital Periegesis</a> project, we’re annotating Pausanias’s 2C CE Description of Greece in Recogito (the Greek text in TEI), using a local version of Recogito to “link to” other datasets with information about Classical / Hellenistic Athens, namely <a href="https://topostext.org/">Topostext</a>, the <a href="https://arachne.dainst.org/project/databasepausanias">German Archaeological Database</a>, <a href="https://dipylon.org/en/2018/05/07/judith-binders-opus-magnum/">Judith Binder’s art historical database</a></li><li><a href="https://palp.p-lod.umasscreate.net/">Pompeii Artistic Landscape Project</a> growing out from the <a href="https://digitalhumanities.umass.edu/pbmp/">Pompeii Bibliography and Mapping Project</a> (<a href="https://arcg.is/1TDX1H">map</a>)</li><li><a href="https://www.emelbourne.net.au/index.html">Encyclopedia of Melbourne</a> (Prof Andrew May)</li><li><a href="http://tlcmap.org/ghap/">TLCMap Gazetteer of Historical Australian Placenames</a> is relevant but not focused on urban)</li><li><a href="http://taxrolls.github.io/">Tax Rolls of Medieval Paris</a> (‘very early stages’) — light on LoD and gazetteer info yet, but geodata / making a formal urban gazetteer to go alongside it is very important to the project</li><li><a href="https://medievallondoners.ace.fordham.edu/search/">Medieval Londoners Database</a>: a project to link information from various sources for medieval Londoners [John McEwan]</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=698852e55bea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pelagios/janelle-jenstad-on-urban-gazetteer-design-698852e55bea">Janelle Jenstad on Urban Gazetteer Design</a> was originally published in <a href="https://medium.com/pelagios">Pelagios</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pelagios in the Indian Subcontinent:]]></title>
            <link>https://medium.com/pelagios/pelagios-in-the-indian-subcontinent-94fef92ad4a5?source=rss----3471255e9353---4</link>
            <guid isPermaLink="false">https://medium.com/p/94fef92ad4a5</guid>
            <category><![CDATA[maps]]></category>
            <category><![CDATA[linked-data]]></category>
            <category><![CDATA[annotations]]></category>
            <dc:creator><![CDATA[Katherine Bellamy]]></dc:creator>
            <pubDate>Wed, 11 Mar 2020 10:31:14 GMT</pubDate>
            <atom:updated>2020-03-11T10:31:14.176Z</atom:updated>
            <content:encoded><![CDATA[<h4>Exploring Colonial Cartographies and Toponyms in India</h4><p>Our project began by identifying a range of high quality digitised maps of the subcontinent, all created and published in Europe. Of these, six maps were selected for annotation; these maps were published between 1714 and 1894 and contained English, Dutch, French translations of Indian toponyms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aPX5bAwBqPfAMVhHCOgC4A.png" /><figcaption>Maps selected for annotation, from <a href="https://www.davidrumsey.com/">David Rumsey Historical Map Collection</a>. From left to right: <a href="https://www.davidrumsey.com/luna/servlet/detail/RUMSEY~8~1~291653~90063178:11--Madras--South-,-Mysore,-and-Coo?sort=Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No&amp;qvq=q:Madras%20(South)%2C%20Mysore%2C%20and%20Coorg;sort:Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No;lc:RUMSEY~8~1&amp;mi=0&amp;trs=2">Madras (South), Mysore, and Coorg</a>; <a href="https://www.davidrumsey.com/luna/servlet/detail/RUMSEY~8~1~297952~90069508:L--Inde-De-ca-Le-Gange?sort=Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No&amp;qvq=q:L%27%20Inde%20De%20ca%20Le%20Gange;sort:Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No;lc:RUMSEY~8~1&amp;mi=0&amp;trs=2">L’Inde ca Le Gange</a>; <a href="https://www.davidrumsey.com/luna/servlet/detail/RUMSEY~8~1~2911~300047:Malabar,-Coromandel,-costes-?sort=Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No&amp;qvq=q:image_no%3D4764085;sort:Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No;lc:RUMSEY~8~1&amp;mi=0&amp;trs=1">Malabar, Coromandel, costes</a>; <a href="https://www.davidrumsey.com/luna/servlet/detail/RUMSEY~8~1~28699~1120936:L-Inde-?sort=Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No&amp;qvq=q:image_no%3D%222174035%22;sort:Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No;lc:RUMSEY~8~1&amp;mi=0&amp;trs=1">L’Inde</a>; <a href="https://www.davidrumsey.com/luna/servlet/detail/RUMSEY~8~1~253237~5518803:Prequ-ile-de-L-Inde-?sort=Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No&amp;qvq=q:image_no%3D%224697026%22;sort:Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No;lc:RUMSEY~8~1&amp;mi=0&amp;trs=1">Prequ’ile de L’Inde;</a> <a href="https://www.davidrumsey.com/luna/servlet/detail/RUMSEY~8~1~317083~90085859:Vol--I--Asia--Part-1--Plate-4?sort=Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No&amp;qvq=q:%3Dindia%20AND%20date%3D1700...1800%20;sort:Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No;lc:RUMSEY~8~1&amp;mi=146&amp;trs=309">Vol. I. Asia. Part 1. Plate 4</a></figcaption></figure><p>Our aim was to trace continuities and discontinuities in the assignment of place-names and to gather clues about the transliteration of place-names and categories from Indian language into European cartographies. Annotation focused on the southern part of the subcontinent from the Deccan south and created a gazetteer containing 1932 annotations. Geographic tags were assigned for all annotated places. The majority were settlements, regions, rivers, mountain ranges, and coastal regions. Stylistic, graphical elements of text and symbols were also tagged. Exploration of these tags is an opportunity for future research into the graphic conventions of colonial cartographies of Southern India.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qvsvBHE3mpH5D-HpIgJ4SA.png" /><figcaption>Automatically and manually assigned place names corresponding to each individual historic map.</figcaption></figure><p>With such a large number of annotations, we decided to focus disambiguation on the Carnatic and Coromandel coasts on the south east of the subcontinent. 335 toponyms that could not be assigned automatically using Recogito’s in-built gazetteers were investigated manually, primarily using Google Maps and mapmyindia.com. Of these, 232 were successfully disambiguated and identified, extending the gazetteer for the subcontinent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YD1ZX5g_wPYEF2LHTTnc2w.png" /><figcaption>Map showing all automatically and manually assigned placenames from all annotated historic maps.</figcaption></figure><p>The full gazetteer created by the project is available <a href="https://livelancsac-my.sharepoint.com/:x:/g/personal/bellamy2_lancaster_ac_uk/EQYnu5Y6ZF5OjuRTXAu6mgUB073UCIB5ARkdb1sJQf9j6g?e=59gyRp">here</a>. Metadata is provided on the second sheet for the eight spreadsheet columns. The gazetteer includes a transcription of the toponyms as they appear on the map, universally unique identifier, latitude, longitude and tags assigned to describe annotated entity (e.g. settlement, italics, underlined). Time-management required a limit to be set for each disambiguation. A maximum of 15 minutes was spent assigning co-ordinates for toponyms. A designation of confidence for the disambiguated toponyms is provided, 1 for definite and 0 to indicate a degree of uncertainty. Colonial contexts present considerable complexity for disambiguation; some toponyms were untraceable. Around 1000 settlement toponyms could not be assigned locations either using Geonames or through disambiguation due to both the complexity of the corpus, and time constraints. As the database develops through different projects, it is hoped that coordinates can be assigned for many of these toponyms in the future.</p><p>A range of additional associated place-names were identified for 207 of the 232 disambiguated toponyms. These associated place names illustrate the complexity and potential of place name analysis. Some of the place names were similar, varying only due to transliteration. The associated names for Pedapalli, now the name of a district of northern Telangana, were clearly variations of the same root Petapouli, Peetapolee, Pettapoli, Pettepole and Peddapalli. Others showed far greater variation in nomenclature. The place located as Caliatur, for example, had six associated place-named: Krishnapatnam, Kistnapatnam, Caleture, Caletur, Calitore and Calletur. The Hill Fortress at Kondaveedu appeared on three maps and was associated with different names on each.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*dFPWRcuKfThsivCGWveHBw.png" /><figcaption>Kondaveedu Fort as it appears on three of the maps: ‘<a href="https://www.davidrumsey.com/luna/servlet/detail/RUMSEY~8~1~2911~300047:Malabar,-Coromandel,-costes-?sort=Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No&amp;qvq=q:image_no%3D4764085;sort:Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No;lc:RUMSEY~8~1&amp;mi=0&amp;trs=1">Condavera</a>’; ‘<a href="https://www.davidrumsey.com/luna/servlet/detail/RUMSEY~8~1~317083~90085859:Vol--I--Asia--Part-1--Plate-4?sort=Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No&amp;qvq=q:%3Dindia%20AND%20date%3D1700...1800%20;sort:Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No;lc:RUMSEY~8~1&amp;mi=146&amp;trs=309">Kondehuir</a>’; ‘<a href="https://www.davidrumsey.com/luna/servlet/detail/RUMSEY~8~1~253237~5518803:Prequ-ile-de-L-Inde-?sort=Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No&amp;qvq=q:image_no%3D%224697026%22;sort:Pub_List_No_InitialSort%2CPub_Date%2CPub_List_No%2CSeries_No;lc:RUMSEY~8~1&amp;mi=0&amp;trs=1">Condavir</a>’</figcaption></figure><p>This preliminary work indicates the importance for smaller-scale explorations of place names that will map nomenclatures at the local level and trace their relationship to changes in government, administrative, urban growth and environmental transformations.</p><p>The annotation and georeferencing of this small selection of maps has initiated what will hopefully begin a more comprehensive expansion of a historical gazetteer for colonial India. It raises issues about the assignment and slippages of toponyms between cartographic representations of territory in colonial contexts. Further research can use place-names to trace out the appearance, disappearance and movement of place-names between cartographies, between maps and textual materials and between place-points and regions.</p><blockquote>If you have any questions related to this project, please get in touch with <strong>Deborah Sutton</strong> (d.sutton[at]lancaster.ac.uk, <a href="https://twitter.com/DebsSutton">@DebsSutton</a>) or <strong>Katherine Bellamy </strong>(k.a.bellamy[at]lancaster.ac.uk, <a href="https://twitter.com/kbellamy_">@kbellamy_</a>)</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94fef92ad4a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pelagios/pelagios-in-the-indian-subcontinent-94fef92ad4a5">Pelagios in the Indian Subcontinent:</a> was originally published in <a href="https://medium.com/pelagios">Pelagios</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>