Presentation (PDF) - Digital Classicist

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
.
The Lexicon of Greek Personal Names and
classical web services
. .
.
Elaine Matthews and Sebastian Rahtz
. . . . . .
.
.

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Summary
Elaine Matthews, Editor, Lexicon of Greek Personal Names,
Classics Faculty, Oxford
Sebastian Rahtz, Information Manager, Oxford University
Computing Services
What is the Lexicon?
How do we record data?
Moving to XML and semantic markup
Web services from the Lexicon
Interaction with other classical projects
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
What is the LGPN?
The Lexicon of Greek Personal Names was established in 1972 as a
Major Research Project of the British Academy.
.
The overall objective of the LGPN project is to create a
comprehensive and authoritative record of the names of all
individuals attested in Greek (or with Greek names attested in
Latin) in the ancient Greek-speaking world, and so provide the
classical research community world-wide with a unique and
fundamental resource for the study of all aspects of the ancient
. Greek world.
. .
.
The papers from LGPN’s two international conferences have
been published: Greek Personal Names: their Value as Evidence,
eds. S. Hornblower, E. Matthews (2000); — Old and New Worlds
in Greek Onomastics, ed. E. Matthews (2007).
. . . . . .
.
.

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Lexicon as research tool
The conference papers provide a pointer to the range of
research questions which LGPN can illuminate, and, in some
instances, makes possible for the first time. They cover
linguistics,
the history of religion,
historiography and literary history,
demographic studies and above all,
cultural interaction.
In practice, of course, there is no limit, nor should there be, to
the uses researchers will make of LGPN’s material. Making the
data available online provides direct, unmediated access to the
material and supports exploitation of the data for further
research both individual and collaborative.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Publications
LGPN is internationally recognised as a unique resource which
has transformed the basis on which names may be studied and
used. It has done so to date primarily through its publications;
so far, 249,289 individuals sharing over 32,000 names have been
published in five regional volumes:
.
. .1 I, Aegean Islands, Cyprus, Cyrenaica (1987);
. . .2 II, Attica (1994);
. . .3 IIIA, Peloponnese, W. Greece, Sicily, Magna Graecia (1997);
. . .4 IIIB, Central Greece (2000);
. . .5 IV, Macedonia, Thrace, Northern Regions of the Black Sea
(2005).
In preparation,
VA: Coastal Asia Minor from Pontos to Ionia (due 2009);
VB. Coastal Asia Minor from Caria to Cilicia (due 2011).
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Lexicon data categories
The LGPN records
.
. .1 Normalized primary name form
. . .2 Sex of person named
. . .3 Place of attestation
. . .4 Date of the attestation (which can vary wildly in precision)
. . .5 Bibliographical references
. . .6 Assorted other data:
placename variations e.g. alternative places of birth or
citizenship
name variants (orthography, dialect), corrections etc
parent/child relationships to other people)
status or profession
editorial corrections/alterations to the record
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
The original records
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
… and what comes out
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Example data
In the compact text form of the Lexicon data, a record looks like
this:
Nani1s (f) @ Athens? @ F4B @ +IG II 12229 @ (%_Na!nei1s!)
Which says that there is a record of someone called Νανίς, a
woman, probably from Athens, in the first half of the 4th
century BC, with a bibliographical reference (publication of an
inscription). The name is normalized from the attested form
which has the syllable νείς.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Caveats
.
. .1 This is not guaranteed to be different from the person in
another record with the name Νανίς, but the Lexicon
believes it is a distinct individual. Any other inscriptions
which mention the same person will be conflated with this
record.
.
. .2 The bibliographical reference is usually, but not always,
exhaustive. If the person is very well attested, another
reference work, such as an encyclopaedia, will be cited,
where the full references can be found.
.
. .3 The relationship to the place name is almost always place
of birth, usually an ancient city or region, though the name
of the modern find-spot may be given, where the ancient
site cannot be identified.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
The Lexicon's IT history
The Lexicon has lived through all the generations of humanities
computing:
1970s trial input and storage using Famulus
no method of retrieval
planning to typeset using pen plotter
1980s input to text files
network database (IDMS)
retrieval programs in FORTRAN
typesetting using Lasercomp
1990s input to text files
relational database (Ingres)
retrieval programs in Pascal and C
typesetting using TeX
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Database
The most significant landmark in the project's IT history was the
design and implementation, in the mid-1980s, of a database
structured to reflect and provide access to all the research
components of an LGPN record, which in the books are
subsumed under name-headings: e.g. chronological and
topographical data, and socially relevant data such as statuses
and relationships.
The database has been crucial in imposing consistency of
format on complex evidence, and the published volumes are
generated from it in photo-ready copy, but its full research
potential remains to be fully realised.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Database first schematic
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Database second schematic
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
The Lexicon's IT present
2000s input to text files
serialization from relational database in XML
online searching using XML database
data model emphasizing collaboration
See
http://www.lgpn.ox.ac.uk/online/computerization
for many more details of the Lexicon's IT development.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
The online project
To transfer LGPN electronic resources to systems based on
TEI-conformant XML, and achieve:
.
. .1 an IT infrastructure to support the future maintenance and
preservation of its irreplaceable research data.
.
. .2 direct online access to all the data, thus opening up the full
research potential of LGPN data to researchers. This
includes the integration of data from all published (and to
be published) volumes into one resource.
.
. .3 the LGPN playing as significant a part in the e-Research
environment as it has played in traditional scholarship.
.
. .4 the LGPN playing a central role in determining standards
for encoding names in documents, using TEI/XML, and
achieving interoperability with online material worldwide.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Archival XML-based format
The technical components of the XML phase of the LGPN help
the Lexicon enhance its publishing and interchange capability:
.
. .1 definition of a XML schema, as a customization of the TEI,
for an archival form of the Lexicon data suitable for
repositories
.
. .2 converting existing database retrieval routines to output
XML conformant to the agreed schema
.
. .3 provision of a new simple forms-based interface for
searching the database or public subsets of it
.
. .4 delivery of results in XML against the TEI schema, with the
option of transforming that to other web delivery formats
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
TEI parallel developments
The LGPN XML work coincided with, and stimulated, a major
revision of the TEI module relating to names and dates in
2006/2007. This now models persons, places and organisations
as first class objects, which allows the Lexicon schema to be a
conformant pure subset of the TEI.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Mapping LGPN to TEI
The major data categories present in the Lexicon map cleanly to
TEI elements as follows:
Lexicon TEI
Name
Person
Name form
Sex
Date Formally, @notBefore and @notAfter attributes on ;
informally in
Status
Reference
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
The TEI customization — people
The TEI format designed for the Lexicon makes use mainly of
the element to contain a Lexicon record.
Long-form XML record for the Lexicon data example:
.
.
Νανίς
Athens
f.iv BC
Να

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Names
Names themselves are stored in a set of records,
providing for the name as a first class object distinct from the
. For example:
.
.
Εὐείδης
Eueidhs
E'uei1dhs
Eu)ei/dhs
.
. .
.
We store variants of the main name in different encodings, in
order to make searching easier.
. . . . . .
.

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
A longer example, short form
The Athenian general Themistocles, about whom a fair amount
is attested, in short form:
Qemistoklh3s (m) @ Phrearrhioi
@ C524-459BC @ +Ag. XXV 664-1049; +AM 106 (1991) p. 151;
+IG II 1035;= +SEG XXVI 121, 33, 45;& +PA/APF 6669;
+RE (1) @ (%_Qemi!sqokle3s!, %_Qemi!sqokle1e8s!,
%_Qemi!ssqokle3s!, %_Qemisto!kle3s! - ostraka:
I s. %Neoklh3s I, f. (nat.) %Dioklh3s
(Alopeke), f. %Neoklh3s II, %Arce1ptolis, %Polu1euktos,
%Kleo1fantos, %Mnhsiptole1ma, %Nikoma1ch, %Itali1a,
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
A longer example, XML form
.
.
Θεμιστοκλῆς
Phrearrhioi
c.524-459BC
Θεμιστοκλε3ς
— ostraka
s.Νεοκλῆς I
f. (nat.)Διοκλῆς (Alopeke)
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Places
Places are modelled using the TEI element, pointed
to by the @key attribute on . This allows us to
maintain a single hierarchical containing all
place names used by the Lexicon. Thus
.
.
Achaia
Aiga
Aigeira
Aigeira (Hyperesia)
.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Data interchange
The Lexicon has defined five levels of data interchange:
1. Character interchange ASCII text version of data separately
from the binary format used by any database
system. This was the minimal form of interchange
supported in the initial stages of the project.
2. Character encoding The Lexicon defined its own
transliteration for Greek, independly of e.g. TLG
betacode, and continues to use it for internal
purposes. Converted to Unicode UTF-8 for
interchange.
3. Standardized structural markup Data relationships follow the
schema defined in 1983. We have reimplemented
this hierarchical and network structure using XML
records to represent the relationships.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Data interchange (continued)
4. Standardized semantic markup The XML representation of
the Lexicon is aligned with the vocabulary and
semantics for XML elements of the Text Encoding
Initiative. The TEI elements are themselves in the
process of alignment with the CIDOC CRM,
allowing even wider understanding and a serious
ontology within this field.
5. Information linking For most categories of data (name, sex,
data, bibliography), the Lexicon can be fully linked
to comparable data. Places are work in progress
… see later.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
The Lexicon online, delivered from XML using
eXist database
With a conversion to XML available, we can load all 250,000
published records into a single new database:
experiment with delivery as XML
combine all volumes together
use XQuery to join together name, place and person data
Caveat: the data conversion and the interfaces are still
experimental. They are not yet ready for serious research.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Conventional interface
search form to enter name, or partial name (regular
expression)
results interlinked by place, date, name etc
browseable list of places and statuses
display mimicking typeset books
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
search example 1
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
search example 2
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
search example 3
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
search example 4
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Moving on, delivering Lexicon data as a web
service
Some people would like to see the raw XML data:
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Why stop at TEI XML?
What about other formats? Some people would like to retrieve
the data as
KML (Keyhole Markup Language), for display in Google
Maps or Earth
Atom, for distribution as RSS
JSON, for consumption by Javascript
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
KML output
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
KML in Google Maps
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Atom RSS
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Packaging it up: consistent cool URLs
Queries can take the form http://claslgpn2.classics.ox.ac.uk/type/query/format,
where
type is one of
. . .1 name: transliterated name with accents
.
. .2 lexname: transliterated name without accents (can
include regular expressions in query)
. . .3 greekname: name in UTF-8 Greek
.
. .4 status: status from Lexicon list (visible at
http://clas-lgpn2.classics.ox.ac.uk/status)
. . .5 date: date in the form yeartoyear
.
. .6 place: place name from Lexicon authority list (visible at
http://clas-lgpn2.classics.ox.ac.uk/place)
. . .7 summary: any name, but returns a summary record not a
full list
. .
. . . . . .
.8 batlas: reference to grid square in Barrington Atlas

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Consistent URLs (2)
…and format is one of
.
. .1 html: human-readable page
. . .2 xml: TEI XML
. . .3 kml: KML for display in Google Earth or Maps (This will not
work for most records until we add more geo locations).
. . .4 timeline: JSON code suitable for consuming by Simile
Timeline
.
. .5 exhibit: JSON code suitable for consuming by Simile
Exhibit
. . .6 atom: Atom RSS
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Examples of consistent URLs
Search by name, return HTML /lexname/Paramonos
Search by name, return XML /lexname/Paramonos/xml
Search by name, return KML /lexname/Paramonos/kml
Search by status, return timeline JSON
/status/potter/timeline
Search by date, return Atom RSS /date/250to265/atom
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Javascript display technologies
From MIT's Semantic Interoperability of Metadata and
Information in unLike Environments (SIMILE,
http://simile.mit.edu/) project, we have used
Timeline (timeline display); enhanced by Nick Rabinowitz's
timemap (http://code.google.com/p/timemap/)
Exhibit (data exploration)
as well as Google Maps and Google Earth.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Timemap
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Exhibit
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Geolocating
How do we find the latitude and longitude of the 3000 places
referenced in the Lexicon?
Looking them up in Wikipedia? No, not really …
Visiting all the sites with a GPS? Nice idea, but impractical
Finding them in Google Earth and reading off figures? In
theory, but how do you find the place?
Finding them in the Barrington Atlas
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
The Barrington Atlas
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Pleiades and Concordia
The Pleiades project (http://pleiades.stoa.org/) is
gradually digitizing all the material from Barrington.
Thanks to Tom Elliott, we were able to make a trial digitization of
c.60 places ourselves, ahead of Pleiades schedule.
That's an awful lot of places yet to geolocate …
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
The Barrington URL
But what if we simply mark all our places with the name, page
number and grid reference in the Atlas?
.
.
Boiotia
Akraiphia
akraiphiai-55-e4
23.216 38.453
.
. .
.
. . . . . .
.

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
The Barrington URL (2)
Now we can offer Lexicon data to other services who have done
a similar job of annotating places.
Credit for this brilliant notion to the Concordia project!
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
And where do all these formats come from?
… simply a series of XSL transformations of the TEI XML file …
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
The Lexicon microformat
Can we do the Lexicon lookup behind the screens and enhance
an HTML page?
.
Greek Unicode
.
names:Θεόδοτος
and᾿Ανθύλος
.
. .
.
. . . . . .
.

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
What does that Javascript do?
go over the document looking for elements.
take the name and send it off to LGPN as a summary
request
get back (eg)
.
lexnames({"names" : [ {"query": "Paramonos", "id": .
"Paramonos", "greek": "Παράμονος", "notBefore":
. "-0999", "notAfter":
. .
"0999", "number": "732" }] });
.
insert extra information in the web page using that data
set the data to display when you move the mouse over the
relevant place
. . . . . .
.

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
A simple test
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Interoperability with Aphrodisias
Aphrodisias TEI XML source:
.
Ζαχαρίας
μονο
πώλης
.
.
. .
can be rendered as
.
.
. Ζαχαρίαςμονοπώλης
. .
.
.
. . . . . .
.
.

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Aphrodisias example
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
What makes that possible?
shared semantic XML markup
common encoding system (Unicode)
powerful browser-based processing
Not anything clever, but appropriate use of standards
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Linking on bibliography
For interaction with the Beazley Archive in Oxford, they support
linking via bibliography:
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
The future
We are still at a very early stage, and these demonstrations are
still only proof of concept. Work to be done includes:
Checking data integrity of XML, and output formats
Establishing a production service
Linking places to Barrington Atlas
Geolocating all the places mentioned in LGPN
Establishing usage and copyright guidelines
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Thanks to …
Tom Elliott, for essential assistance with locating places and
ideas about URLs
Janet McKnight, for Javascript programming and
geolocating
Gabriel Bodard, for forcing us to complete this work by
giving us a deadline
Donna Kurtz and the Beazley Archive for stimulating
interchange ideas
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Conclusions
We believe that this story of the Lexicon illustrates four points:
. . .1 the conceptual data model of the 1970s has survived the
test of time; it has survived many completely unseen
changes and challenges, but has required no serious
change
.
. .2 the modern web techniques of machine/machine
interchange, and rich exploratory tools, can be retrofitted
effectively to older projects
. . .3 interoperability is a key technique, not just going online
with fancy displays
.
. .4 there are academic questions waiting to be answered by
this version of the Lexicon data, as well as uses we have not
yet imagined.
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Links for demonstrations
Searching for a name
http://clas-lgpn2.classics.ox.ac.uk/LGPN/se
Browsing places
http://clas-lgpn2.classics.ox.ac.uk/place
Browsing by status
http://clas-lgpn2.classics.ox.ac.uk/status
Directly to a name
http://clas-lgpn2.classics.ox.ac.uk/lexname
Directly to a partial name
http://clas-lgpn2.classics.ox.ac.uk/lexname
Directly to a status
http://clas-lgpn2.classics.ox.ac.uk/status/
Directly to a date
http://clas-lgpn2.classics.ox.ac.uk/date/25
Directly to a place
http://clas-lgpn2.classics.ox.ac.uk/place/A
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
More links
Retrieving XML
http://clas-lgpn2.classics.ox.ac.uk/lexname
Retrieving KML
http://clas-lgpn2.classics.ox.ac.uk/lexname
Using KML in Google maps
http://maps.google.co.uk?q=http://clas-lgpn
Generating Atom
http://clas-lgpn2.classics.ox.ac.uk/lexname
Retrieving summary of name
http://clas-lgpn2.classics.ox.ac.uk/summary
Timeline for name Polugnwtos
http://clas-lgpn2.classics.ox.ac.uk/Demo/ti
Timeline for name Paramonos
http://clas-lgpn2.classics.ox.ac.uk/Demo/ti
Timeline for status "potter"
http://clas-lgpn2.classics.ox.ac.uk/Demo/ti
. . . . . .

The Lexicon of
Greek Personal
Names and
classical web
services
Elaine
Matthews and
Sebastian
Rahtz
Yet more links
Timemap for name Panis
http://clas-lgpn2.classics.ox.ac.uk/Demo/ti
Timemap for name Paramonos
http://clas-lgpn2.classics.ox.ac.uk/Demo/ti
Timemap for status "potter"
http://clas-lgpn2.classics.ox.ac.uk/Demo/ti
Timemap for place Aloros
http://clas-lgpn2.classics.ox.ac.uk/Demo/ti
Exploring painters
http://clas-lgpn2.classics.ox.ac.uk/Demo/ex
Dynamically annotate page with summary Lexicon data
http://clas-lgpn2.classics.ox.ac.uk/Demo/te
Extended example of annotating page with summary
Lexicon data
http://clas-lgpn2.classics.ox.ac.uk/Demo/iA
Extracting data according to Barrington Atlas identifier
. . . . . .