A Better Location for Forum Gallorum?

René Voorburg has raised concerns over the Pleiades location for Forum Gallorum (http://pleiades.stoa.org/places/246395/), given relevant evidence from the Antonine Itineraries. You can see his comment, and my initial response, at http://pleiades.stoa.org/places/246395/darmc-location-7291.

I'd be grateful if some interested party, who has local access to TIR Caesaraugusta*, can check pages 117-118 to see on what grounds it locates Forum Gallorum at Cerro de San Mitiel (Ayerbe) and whether it addresses the anomalous distance measures René noticed. Neither René nor I have immediate access to the volume.

Please provide your response by appending a comment to the above discussion thread. All you need to submit comments to Pleiades is an OpenID. Many thanks!

* TIR Caesaraugusta = Tabula Imperii Romani K-30, Madrid: Caesaraugusta, Clunia (Madrid: 1993).

NEH Project Directors' Meeting

John Muccigrosso and I had a good time at the NEH Project Directors' Meeting in Washington yesterday (#SUG2011 was the twitter hash tag). Here are the slides that Sebastian Heath whipped up for our 2-minute lightning talk about the forthcoming Linked Ancient World Data Institutes (spring 2012 at ISAW; spring 2013 at Drew U.). I blogged my notes on Linked Open Data yesterday.

Linked. Open. Data.

As we get spun up for our Linked Ancient World Data Institute (LAWDI) and move toward more interlinkedness between Pleiades, Papyri.info, the Ancient World Image Bank and other resources, I've been refreshing my thinking on Linked Open Data (LOD). Among the fodder for this thinking is Tim Berners-Lee's "Linked Data - Design Issues." Today's Digital Humanities Project Directors meeting at NEH has John Muccigrosso and myself channeling Sebastian Heath in a lightning talk, so I thought I'd better get my thoughts in order. It falls to me to briefly define linked open data so John can talk about the institute.

Berners-Lee's piece presents two lists of criteria/considerations/characteristics of linked open data in a way that doesn't entirely reconcile the two. They're overlapping and complementary, but they clearly represent two different stages in the promotion of the idea. I think those lists can be remixed into a single list with three clear rubrics that are easy to remember.

Linked

• Put your content on the web (not under or inside or over it)
• Assign (stable) Uniform Resource Identifiers (URIs) as names to discrete entities and ideas in your content
• Use HTTP URIs to enable lookup of the names and hide implementation detail
• Provide useful information about named entities on lookup
• Link to other URIs to facilitate discovery
  • Typed links define relationships between named entities both within and beyond your content
  • Typed links facilitate assertion and inference
• Bottom line: my data is your metadata

Open

• Publish under open licenses (e.g., Creative Commons Attribution, GNU Public License)
• Publish in non-proprietary formats
• Publish machine-readable content
• Facilitate discovery via browsing and crawling (i.e., don't require searching/guessing)
• Bottom line: my data is your data

Data

• Publish structured data, not just documents
• Treat both content and links as data
• Express internal and external links in well-defined forms like RDF
• Bottom line: our machines can help

Describing Pleiades

Matt Knutzen recently sent me a draft description of the Pleiades project and asked for my thoughts on it. Here's what resulted:

The Pleiades Project (http://pleiades.stoa.org) is a consortially developed, open-source, web-based platform for using, creating, improving and sharing historical geographic information about the ancient world. It employs a unique data model that adapts best-practice and standards in GIS and spatial computing to deal with the unique challenges of sparse, damaged and contested information about ancient places, spaces and names. The project began by adapting and publishing all the data gathered for the Barrington Atlas of the Greek and Roman World, but is now working with partners to expand temporally and spatially into Late Antiquity, the Byzantine Empire, the ancient Near East, Egypt and beyond.

Feeds of Flickr Photos Depicting Pleiades Places

Some months ago, ISAW started adding Pleiades machine tags to the Ancient World Image Bank (AWIB) photos we've been uploading to Flickr. This post will explain what that means, how it might be useful to you and how you can add Pleiades machine tags to your own photos so we can find out about them.

Updated: 8:45pm EDT, 10 September 2011 (changes highlighted in orange).
Updated: 10:43am EST, 20 December 2011 (some of what's here is now superseded by recent developments; see further this new post: Pleiades, Flickr, and the Ancient World Image Bank)

Pleiades Machine Tags

Pleiades is a collaborative, open-access digital gazetteer for the ancient world. AWIB is an open-access publication that uses the Flickr photo-sharing site to publish free, reusable photos of ancient sites and artifacts. Machine tags are an extension to Flickr's basic tag-this-photo functionality that "use a special syntax to define extra information about a tag" (Aaron Straup Cope, "Ladies and Gentlemen: Machine Tags," 24 January 2007).

A Pleiades machine tag looks like this:

pleiades:place=795868

where 795868 is the stable identifier portion of a Pleiades Uniform Resource Identifier (URI).  In this example, the URI corresponding to the machine tag above is:

http://pleiades.stoa.org/places/795868

Note what's in common between the machine tag and the URI (highlighted in yellow).

What Pleiades Machine Tags Are Good For

The Flickr API makes it possible to request lists of machine-tagged photos in the RSS webfeed format. So, to get a list of all photos in Flickr that are tagged with the example machine tag above, pop this into your feed reader:

http://api.flickr.com/services/feeds/photos_public.gne?tags=pleiades%3Aplace=795868&lang=en-us&format=rss_200

The same results can be viewed in HTML in a browser by resolving the following:

http://www.flickr.com/photos/tags/pleiades:place=795868

To get a list of all photos in Flickr that are tagged with any Pleiades machine tag, try this (the API syntax supports wildcards!):

http://api.flickr.com/services/feeds/photos_public.gne?tags=pleiades%3Aplace%3D&lang=en-us&format=rss_200

The same results, viewed in HTML on the Flickr site:

http://www.flickr.com/photos/tags/pleiades:place

Feeds like these aren't just for feed readers anymore. You can add user-interface widgets to your blog or website to summarize the latest content for your readers (check out the right-hand column in this blog). You can hook up services like Networked Blogs or Twitterfeed to pass on the latest changes to your Facebook friends or Twitter followers. If you've got a web-facing numismatic database that you've already linked up with Pleiades for the mint locations, you could write custom code to pull a corresponding picture of the ancient site into your web interface (say, alongside the map you've already got).

Add Pleiades Machine Tags to Your Own Photos on Flickr

Many of you have been taking amazing photos of ancient sites and artifacts for years. Many of you have posted some of them to Flickr and shared them with great groups like Chiron, Visibile Parlare - Greek Inscriptions and Visibile Parlare - Latin Inscriptions. If you'd like these photos to appear in queries and feeds (like those described above), right alongside the photos that we're publishing via AWIB, all you have to do is add the appropriate Pleiades machine tags in Flickr. Just look up your site on Pleiades, copy the numeric ID from the URI in your browser's location bar, append it to the string "pleiades:place=" and tag your Flickr photos with it. In this way, you can help us improve findability of good photos of ancient sites and the artifacts found there for everyone on the web. Who knows ... maybe enough people will join us in this effort that we can someday get the Flickr development team to give Pleiades machine tags some extra love.

Kudos to:

• Aaron Straup Cope for his blog post "Wildcard Machine Tag URLs" (18 July 2008) that showed me how to construct the API queries necessary to get the RSS feeds described above. That, and the Flickr API documentation on feeds.
• Nate Nagy, Managing Editor of AWIB, who applies the tags and keeps AWIB rolling.
• Dan Pet, from the Portable Antiquities Scheme, and Ryan Baumann, from the Center for Visualization and Virtual Environments at the University of Kentucky, who put me onto machine tags in the first place and helped me get up to speed.