SyntaxHighlighter

Showing posts with label concordia. Show all posts
Showing posts with label concordia. Show all posts

Thursday, April 18, 2013

Citing Sources in Digital Annotations

I'm collaborating with other folks both in and outside ISAW on a variety of digital scholarly projects in which Linked Open Data is playing a big role. We're using the Resource Description Framework (RDF) to provide descriptive information for, and make cross-project assertions about, a variety of entities of interest and the data associated with them (places, people, themes/subjects, creative works, bibliographic items, and manuscripts and other text-bearing objects). So, for example, I can produce the following assertions in RDF (using the Terse RDF Triple Language, or TuRTLe):

<http://syriaca.org/place/45> a <http://geovocab.org/spatial#Feature> ;
  rdfs:label "Serugh" ;
  rdfs:comment "An ancient city where Jacob of Serugh was bishop."@en ;
  foaf:primaryTopicOf <http://en.wikipedia.org/wiki/Suruç> ;
  owl:sameAs <http://pleiades.stoa.org/places/658405#this> .

This means: 'There's a resource identified with the Uniform Resource Identifier (URI) "http://syriaca.org/place/45" about which the following is asserted:
(Folks familiar with what Sean Gillies has done for the Pleiades RDF will recognize my debt to him in the what proceeds.)

But there are plenty of cases in which just issuing a couple of triples to encode an assertion about something isn't sufficient; we need to be able to assign responsibility/origin for those assertions and to link them to supporting argument and evidence (i.e., standard scholarly citation practice). For this purpose, we're very pleased by the Open Annotation Collaboration, whose Open Annotation Data Model was recently updated and expanded in the form of a W3C Community Draft (8 February 2013) (the participants in Pelagios use basic OAC annotations to assert geographic relationships between their data and Pleiades places).


A basic OADM annotation uses a series of RDF triples to link together a "target" (the thing you want to make an assertion about) and a "body" (the content of your assertion). You can think of them as footnotes. The "target" is the range of text after which you put your footnote number (only in OADM you can add a footnote to any real, conceptual, or digital thing you can identify) and the "body" is the content of the footnote itself. The OADM draft formally explains this structure in section 2.1. This lets me add an annotation to the resource from our example above (the ancient city of Serugh) by using the URI "http://syriaca.org/place/45" as the target of an annotation) thus:
<http://syriaca.org/place/45/anno/desc6> a oa:Annotation ;
  oa:hasBody <http://syriaca.org/place/45/anno/desc6/body> ;
  oa:hasTarget <http://syriaca.org/place/45> ;
  oa:motivatedBy oa:describing ;
  oa:annotatedBy <http://syriaca.org/editors.xml#tcarlson> ;
  oa:annotatedAt "2013-04-03T00:00:01Z" ;
  oa:serializedBy <https://github.com/paregorios/srpdemo1/blob/master/xsl/place2ttl.xsl> ;
  oa:serializedAt "2013-04-17T13:35:05.771-05:00" .

<http://syriaca.org/place/45/anno/desc6/body> a cnt:ContentAsText, dctypes:Text ;
  cnt:chars "an ancient town, formerly located near Sarug."@en ;
  dc:format "text/plain" ;

I hope you'll forgive me for not spelling that all out in plain text, as all the syntax and terms are explained in the OADM. What I'm concerned about in this blog post is really what the OADM doesn't explicitly tell me how to do, namely: show that the annotation body is actually a quotation from a published book. The verb oa:annotatedBy lets me indicate that the annotation itself was made (i.e., the footnote was written) by a resource identified by the URI "http://syriaca.org/editors.xml#tcarlson". If I'd given you a few more triples, you could have figured out that that resource is a real person named Thomas Carlson, who is one of the editors working on the Syriac Reference Portal project. But how do I indicate (as he very much wants to do because he's a responsible scholar and has no interest in plagiarizing anyone) that he's deliberately quoting a book called The Scattered Pearls: A History of Syriac Literature and Sciences? Here's what I came up with (using terms from Citation Typing Ontology and the DCMI Metadata Terms):
<http://syriaca.org/place/45/anno/desc7/body> a cnt:ContentAsText, dctypes:Text ;
  cnt:chars "a small town in the Mudar territory, between Ḥarran and Jarabulus. [Modern name, Suruç (tr.)]"@en ;
  dc:format "text/plain" ;
  cito:citesAsSourceDocument <http://www.worldcat.org/oclc/255043315> ;
  dcterms:biblographicCitation  "The Scattered Pearls: A History of Syriac Literature and Sciences, p. 558"@en .

The addition of the triple containing cito:citesAsSourceDocument lets me make a machine-actionable link to the additional structured bibliographic data about the book that's available at Worldcat (but it doesn't say anything about page numbers!). The addition of the triple containing dcterms:bibliographicCitation lets me provide a human-readable citation.

I'd love to have feedback on this approach from folks in the OAC, CITO, DCTERMS, and general linked data communities. Could I do better? Should I do something differently?


The SRP team is currently evaluating a sample batch of such annotations, which you're also welcome to view. The RDF can be found here. These files are generated from the TEI XML here using the XSLT here.

Friday, June 1, 2012

Ancient Studies Needs Open Bibliographic Data and Associated URIs

Update 1:  links throughout, minor formatting changes, proper Creative Commons Public Domain tools, parenthetical about import path from Endnote and such, fixing a few typos.

The NEH-funded Linked Ancient World Data Institute, still in progress at ISAW, has got me thinking about a number of things. One of them is bibliography and linked data. Here's a brain dump, intended to spark conversation and collaboration.

What We Need

  • As much bibliographic data as possible, for both primary and secondary sources (print and digital), publicly released to third parties under either a public domain declaration or an unrestrictive open license.
  • Stable HTTP URIs for every work and author included in those datasets.

Why

Bibliographic and citation collection and management are integral to every research and publication in project in ancient studies. We could save each other a lot of time, and get more substantive work done in the field, if it was simpler and easier to do. We could more easily and effectively tie together disparate work published on the web (and appearing on the web through retrospective digitization) if we had a common infrastructure and shared point of reference. There's already a lot of digital data in various hands that could support such an effort, but a good chunk of it is not out where anybody with good will and talent can get at it to improve it, build tools around it, etc.

What I Want You (and Me) To Do If You Have Bibliographic Data
  1. Release it to the world through a third party. No matter what format it's in, give a copy to someone else whose function is hosting free data on the web. Dump it into a public repository at github.com or sourceforge.net. Put it into a shared library at Zotero, Bibsonomy, Mendeley, or another bibliographic content website (most have easy upload/import paths from Endnote, and other citation management applications). Hosting a copy yourself is fine, but giving it to a third party demonstrates your bona fides, gets it out of your nifty but restrictive search engine or database, and increments your bus number.
  2. Release it under a Creative Commons Public Domain Mark or Public Domain Dedication (CC0).  Or if you can't do that, find as open a Creative Commons or similar license as you can. Don't try to control it. If there's some aspect of the data that you can't (because of rights encumberance) or don't want to (why?) give away to make the world a better place, find a quick way to extract, filter, or excerpt that aspect and get the rest out.
  3. Alert the world to your philanthropy. Blog or tweet about it. Post a link to the data on your institutional website. Above all, alert Chuck Jones and Phoebe Acheson so it gets announced via Ancient World Online and/or Ancient World Open Bibliographies.
  4. Do the same if you have other useful data, like identifiers for modern or ancient works or authors.
  5. Get in touch with me and/or anyone else to talk about the next step: setting up stable HTTP URIs corresponding to this stuff.
Who I'm Talking To

First of all, I'm talking to myself, my collaborators, and my team-mates at ISAW. I intend to eat my own dogfood.

Here are other institutions and entities I know about who have potentially useful data.
  • The Open Library : data about books is already out there and available, and there are ways to add more
  • Perseus Project : a huge, FRBR-ized collection of MODS records for Greek and Latin authors, works, and modern editions thereof.
  • Center for Hellenic Studies: identifiers for Greek and Latin authors and works
  • L'Année Philologique and its institutional partners like the American Philological Association: the big collection of analytic secondary bibliography for classics (journal articles)
  • TOCS-IN: a collaboratively collected batch of analytic secondary bibliography for classics
  • Papyri.info and its contributing project partners: TEI bibliographic records for  much of the bibliography produced for or cited by Greek and Latin papyrologists (plus other ancient language/script traditions in papyrology)
  • Gnomon Bibliographische Datenbank: masses of bibliographic data for books and articles for classics
  • Any and every university library system that has a dedicated or easily extracted set of associated catalog records. Especially any with unique collections (e.g., Cincinnati) or those with databases of analytical bibliography down to the level of articles in journals and collections.
  • Ditto any and every ancient studies digital project that has bibliographic data in a database.
Comments, Reactions, Suggestions

Welcome, encouraged, and essential. By comment here or otherwise (but not private email please!).

Monday, February 6, 2012

Playing with PELAGIOS: The GAWD is Live

The is the lastest in an on-going series chronicling my dalliances with data published by the PELAGIOS project partners.

I think it's safe to say that, thanks to the PELAGIOS partner institutions, that we do have a Graph of Ancient World Data (GAWD) on the web. It's still in early stages, and one has to do some downloading, unzipping, and so forth to engage with it at the moment, but indeed the long-awaited day has dawned.

Here's the perspective, as of last Friday, from the vantage point of Pleiades. I've used SPARQL to query the GAWD for all information resources that the partners claim (via their RDF data dumps) are related to Pleiades information resources. I.e., I'm pulling out a list of information resources about texts, pictures, objects, grouped by their relationships to what Pleiades knows about ancient places (findspot, original location, etc.). I've sorted that view of the graph by the titles Pleiades gives to its place-related information resources and generated an HTML view of the result. It's here for your browsing pleasure.

Next Steps and Desiderata

For various technical reasons, I'm not yet touching the data of a couple of PELAGIOS partners (CLAROS and SPQR), but the will hopefully be resolved soon. I still need to dig into figuring out what Open Context is doing on this front. Other key resources -- especially those emanating from ISAW -- are not yet ready to produce RDF (but we're working on it).

There are a few things I'd like the PELAGIOS partners to consider/discuss adding to their data:

  • Titles/labels for the information resources (using rdfs:label?). This would make it possible for me to produce more intuitive/helpful labels for users of my HTML index. Descriptions would be cool too. As would some indication of the type of thing(s) a given resource addresses (e.g., place, statue, inscription, text)
  • Categorization of the relationships between their information resources and Pleaides information resources. Perhaps some variation of the terms originally explored by Concordia (whence the GAWD moniker), as someone on the PELAGIOS list has already suggested.
What would you like to see added to the GAWD? What would you do with it?

Friday, January 29, 2010

A new Concordia term: "where" (needed for linking papyri to Pleiades resources)

In discussions this week with Sean and Hugh, we explored what would be minimally necessary for web feeds describing the papyrological documents now being surfaced via http://papyri.info.

In the long term, we'd like to link not only to descriptive resources (at Pleiades or elsewhere) for their modern places of finding but also any ancient places attested in the texts themselves (having done named-entity analysis on all 50,000+ documents, the first steps in which are now underway by Mark Depauw and the Trismegistos team in Leiden).

In the near term, we can express geographic linkages on the basis of the nome attributions recorded for the papyri by the editors of the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens whose records are incorporated into the papyri.info contents.

But none of the terms we had previously defined in our Concordia link-type thesaurus precisely fit this information. We did have several geographic terms (findSpot, origin, observedAt and attestsTo), but we needed to add a more generic one: "where". The nomes as indicated by HGV are geographical classifications, based on the ancient regions, made primarily for facilitating reference and review by modern scholars. They don't necessarily constitute "find spot" or "place of origin" in every case. This "where" term idea followed naturally from Sean's earlier efforts to advocate for a "where" link relation type. A link in a feed entry using this term will simply indicate that the described resource should be treated as being located, in a general way, at the place described by the linked resource.

Hopefully, this term will be useful not only for papyri.info, but also for other pre-existing datasets where the location information recorded about ancient artifacts is similarly less precise than the born-digital epigraphic corpora that guided the minting of our initial thesaurus terms. Hopefully it will also prove useful in contexts such as those that Sebastian has recently been blogging about.

Thursday, December 17, 2009

Interoperation with Pleiades

I've had a few questions lately about how other web-based publications could be designed to support interoperation with Pleiades. Here's my working advice:

Any project that wants to lay the groundwork for geographic interoperability on the basis of Pleiades should:

1. Capture and manage Pleiades identifiers (stable URLs like http://pleiades.stoa.org/places/638753/) for each place one might want to cite.

2. Request membership in the Pleiades community and add/modify content therein as necessary in order to create new resources (and new URLs) for places that Pleiades doesn't yet document, but which are provably historical and relevant to content controlled by the external project.

3. Capture and manage stable URLs from Wikipedia or GeoNames that correspond to modern geographic entities that are relevant to the content controlled by the external project. Don't conflate modern and ancient locations, as this will eventually lead to heartbreak.

4. Emit paged web feeds in the Atom Syndication Format (RFC 4287) that also conform to the guidance documented (with in-the-wild, third-party examples) at:

http://www.atlantides.org/trac/concordia/wiki/ConcordiaAtomFeeds

and make use of the terms defined at

http://www.atlantides.org/trac/concordia/wiki/ConcordiaThesaurus

to indicate publicly relationships such as "findspot" and "original location" between the content controlled by the external project, Pleiades resources, Wikipedia resources, GeoNames resources and resources published by other third parties.

5. Alert us so we can include the entry-point URL for the feeds in the seeded search horizon list for the web crawler and search index service we are developing.

You can see how the Epigraphic Databank Heidelberg team has been thinking about how to accomplish this at:

http://www.atlantides.org/trac/concordia/wiki/PleiadesMoI

and

http://www.atlantides.org/trac/concordia/wiki/EDHgeographyTable

Tuesday, June 9, 2009

Determining BAtlas IDs for future Pleiades interoperation

For those who are working with datasets they'd like eventually to link up with Pleiades, we created the Barrington Atlas ID scheme. I've just posted some more tools for helping you determine the BAtlas IDs to go with your existing geographic names or other information.

There's now a draft "Barrington Atlas Index with Identifiers". In PDF (watch out: 7.2 MB) it looks like:


It's also available in a 1.0 MB zip-compressed HTML version, with somewhat semantic class attributes on spans that could be used to parse out different themes ahead of an attempt to match it to a names list:

And of course there is already the home-brewed XML format we distributed the original IDs in (last release tar-gzipped archive):

Share and enjoy!

Wednesday, January 28, 2009

The Concordia Graph

In yesterday's post, I should also have linked directly to the working copy of the Concordia Graph ... persons, places, names, objects and some basic, history-oriented relationships between them ... a subset of what hopefully GAWD will eventually address (as non-idiosyncratically as possible).

Tuesday, January 27, 2009

Semantic Web, Scholarly Resources for Antiquity and the Museum

Our on-going work on geographically functional, cross-resource, machine-actionable citation(!) with the Web continues to get more interesting.

The kickoff was, of course, the joint NEH/JISC grant that is (under the rubric of the Concordia project) funding our look at this in collaboration with the Centre for Computing in the Humanities at King's College, London. Our two workshops (and lots of discussion with other parties in between) have led us through KML, Atom+GeoRSS, citation vocabularies and OAI/ORE on to Cool URIs, Linked Data, CIDOC CRM and more.

Traffic is now building on the Graph of Ancient World Data discussion group (e.g., Sebastian Heath's post on coin hoard data at nomisma.org). Yesterday, Sean Gillies rolled out some changes to the Pleiades interface that provide #this endpoints for Pleiades places, so that Sebastian and others can make explicit reference either to the historical places themselves (non-information resources cited like http://pleiades.stoa.org/places/639166#this) or our descriptions of them on the web (information resources, cited like http://pleiades.stoa.org/places/639166/).

And then this afternoon I came across the latest Talis Semantic Web podcast, featuring Koven Smith on Semantic Web initiatives at the Metropolitan Museum of Art. 38 minutes well-spent. They're thinking about and exploring a number of the approaches and technologies we're interested in, but from a museum perspective. It would be interesting to discuss how these methods could be used to better bridge gaps between museums, field archaeologists, epigraphers, numismatists, papyrologists, prosopographers, historical geographers, librarians, archivists and the rest!

Friday, January 16, 2009

Digital Projects (ISAW Newsletter January 2008)

Since the ISAW Newsletter is only available online as a monolithic PDF, I thought I'd make the text of my contribution (about our "digital programs") available here in HTML form:
ISAW’s digital programs are fundamental to the Institute’s mission. Convinced that the transformation of the media and information landscape now underway offers scholars unparalleled opportunities to make new discoveries, collaborate with distant colleagues, engage public interests, and tackle previously intractable problems, we have committed ourselves to an ambitious slate of digital initiatives that extend far beyond the walls of the Institute. As the examples below illustrate, we emphasize the creation and delivery of core resources such as primary and secondary texts and images, as well as geographic and archaeological reference information. We seek to serve the entire field of ancient studies by working for the durability of digital publications–and the sustainability of the projects that create and maintain them–through promotion of standards, creation of reusable free software, use of open-access licenses, and decentralization of authorial, editorial, and peer-review activities.

In early 2008, ISAW became a partner in the Pleiades Project. Together with the Ancient World Mapping Center (AWMC), we are digitizing the most comprehensive register of geographical data for the ancient Greek and Roman world, collected by the American Philological Association’s Classical Atlas Project to support the preparation of the Barrington Atlas of the Greek and Roman World (R. Talbert, ed., Princeton 2000). All of the coordinates, historical names, and other information in this rich collection are being placed online so scholars, students, and enthusiasts worldwide can browse, search, and map it, as well as offer suggestions for updates and additions. The Pleiades effort has recently expanded with funding from a Transatlantic Digitization Grant, awarded to ISAW and King’s College London, by the National Endowment for the Humanities (NEH) and the U.K. Joint Information Systems Committee. It supports the prototyping of mechanisms to tie Pleiades into important digital collections of epigraphic and papyrological texts from Egypt and coastal North Africa (see further: the Concordia Project and the Graph of Ancient World Data group). This effort will lay the foundation for extensive, automated cross-linking between Pleiades and other web-based scholarly resources for the entire Greek and Roman world. We are currently seeking funding for a second, two-year development period for Pleiades/Concordia that will accelerate the digitization of content and bring users together for a series of workshops to identify needed improvements to the system and to facilitate more effective collaboration.

Over the past year ISAW has also assumed a leadership role in a group of interrelated digital papyrology projects (see http://idp.atlantides.org). One of these, funded by a grant to Duke University from the Andrew W. Mellon Foundation, has successfully upgraded and effectively integrated two of the key digital resources for study of ancient documents on papyrus: the Duke Databank of Documentary Papyri (DDbDP) and the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV). Both resources will soon be provided to users via a search and display environment prototyped by the digital libraries team at Columbia University. This system, dubbed the Papyrological Navigator, combines DDbDP and HGV content with images and database records drawn from the 22 museum and university papyrus collections that constitute the Advanced Papyrological Information System (APIS). It also links them to the extensive Trismegistos databases in Leuven. Under new funding provided to APIS by the NEH, work on this interface will move to the Digital Libraries team at NYU where, with collaboration from ISAW and APIS team members at Columbia, it will see extensive improvements. ISAW is currently working with partners to secure funding for a second major upgrade to the DDbDP and HGV: a collaborative, online editing environment that will speed the addition and revision of content by granting papyrologists worldwide direct authorial capabilities under a distributed system of editorial oversight.

A number of other exciting projects are in work for 2009 and beyond. We hope to expand the utility of Pleiades by linking it to a number of other systems and digital gazetteers under development at a variety of institutions around the world. Plans are being formulated for a collaborative digital encyclopedia of Coptic archaeology, an extensive database of digital images, an online calendar of museum exhibitions, a major book and journal digitization program, and a multi-institutional publication series comprising open-access primary texts and research data.

Thursday, September 4, 2008

BAtlas IDs: first full release (all maps)

Grab the whole thing here: http://atlantides.org/batlas/2008-09-04/baids-2008-09-04.tgz

Let me know what problems you find.

README file for Barrington Atlas Identifiers, version published 2008-09-04
This is the first complete release.
Reference URL: http://atlantides.org/batlas

Background: http://horothesia.blogspot.com/search/label/batlasids
New maps covered in this release: 100, 101, 102
List of all maps presently covered: 1-102 (complete)

Major classes of change from prior versions are listed below. Consult individual files named like map22-diff.txt for output files differencing from prior version to this version.
  • No changes to previously released IDs.

Wednesday, September 3, 2008

BAtlas ID update: Maps 1-6 and 65

README file for Barrington Atlas Identifiers, version published 2008-09-03
Reference URL: http://atlantides.org/batlas

Background: http://horothesia.blogspot.com/search/label/batlasids
New maps covered in this release: 1, 1a, 2, 3, 4, 5, 6, 64
List of all maps presently covered: 1-99

Major classes of change from prior versions are listed below. Consult individual files named like map22-diff.txt for output files differencing from prior version to this version.

  • No changes to previously released IDs.
  • Note that map 64 was erroneously listed as included in previous releases, but was not present. This difficiency is corrected with this release.

Thursday, August 28, 2008

Barrington Atlas ID update: maps 89-99

README file for Barrington Atlas Identifiers, version published 2008-08-28
Reference URL: http://atlantides.org/batlas

Background: http://horothesia.blogspot.com/search/label/batlasids
New maps covered in this release: 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99
List of all maps presently covered: 7-99

Major classes of change from prior versions are listed below. Consult individual files named like map22-diff.txt for output files differencing from prior version to this version.
  • No changes to previously released IDs.

Wednesday, August 20, 2008

BAtlas ID Update: Maps 28-34, 67-71, 81-83

README file for Barrington Atlas Identifiers, version published 2008-08-20
Reference URL: http://atlantides.org/batlas

Background: http://horothesia.blogspot.com/search/label/batlasids
New maps covered in this release: 28, 29, 30, 31, 32, 33, 34, 67, 68, 69, 70, 71, 81, 82, 83
List of all maps presently covered: 7-88

Major classes of change from prior versions are listed below. Consult individual files named like map22-diff.txt for output files differencing from prior version to this version.

* No changes to previously released IDs.

Tuesday, August 19, 2008

BAtlas ID update: Maps 7-9, 26-27

README file for Barrington Atlas Identifiers, version published 2008-08-19
Reference URL: http://atlantides.org/batlas

Background: http://horothesia.blogspot.com/search/label/batlasids
New maps covered in this release: 7, 8, 9, 26, 27
List of all maps presently covered: 7-27, 35-66, 72-80, 84-88

Major classes of change from prior versions are listed below. Consult individual files named like map22-diff.txt for output files differencing from prior version to this version.
  • No changes to previously released IDs.

Monday, August 18, 2008

BAtlas ID update: Maps 19, 41-48

README file for Barrington Atlas Identifiers, version published 2008-08-15
Reference URL: http://atlantides.org/batlas

Background: http://horothesia.blogspot.com/search/label/batlasids
New maps covered in this release: 19, 41, 42, 43, 44, 45, 46, 47, 48
List of all maps presently covered: 10-25, 35-66, 72-80, 84-88

Major classes of change from prior versions are listed below. Consult individual files named like map22-diff.txt for output files differencing from prior version to this version.
  • No changes to previously released IDs.

Friday, August 8, 2008

BAtlas ID update: Maps 14-18, 24, 25, 39, 40

README file for Barrington Atlas Identifiers, version published 2008-08-08
Reference URL: http://atlantides.org/batlas

Background: http://horothesia.blogspot.com/search/label/batlasids
New maps covered in this release: 14, 15, 16, 17, 18, 24, 25, 39, 40
List of all maps presently covered: 10-18, 20-25, 35-40, 49-65, 72-80, 84-88

Major classes of change from prior versions are listed below. Consult individual files named like map22-diff.txt for output files differencing from prior version to this version.

* No changes to previously released IDs.

Tuesday, August 5, 2008

BAtlas IDs: Maps 10-13, 20-21, 49

README file for Barrington Atlas Identifiers, version published 2008-08-05
Reference URL: http://atlantides.org/batlas

Background: http://horothesia.blogspot.com/search/label/batlasids
New maps covered in this release: 10, 11, 12, 13, 20, 21, 49
List of all maps presently covered: 10, 11, 12, 13, 20, 21, 22, 23, 35, 36, 37, 38, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 65, 72, 73, 74, 75, 76, 77, 78, 79, 80, 84, 85, 86, 87, 87 inset, 88

Major classes of change from prior versions are listed below. Consult individual files named like map22-diff.txt for output files differencing from prior version to this version.

* No changes to previously released IDs.

Monday, August 4, 2008

BAtlas ID update: maps 23, 84, 85, 87, 87 inset, 88 and fixed dates

README file for Barrington Atlas Identifiers, version published 2008-08-04
Reference URL: http://atlantides.org/batlas

Background: http://horothesia.blogspot.com/search/label/batlasids
New maps covered in this release: 23, 84, 85, 87, 87 inset, 88
List of all maps presently covered: 22, 23, 35, 36, 37, 38, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 65, 72, 73, 74, 75, 76, 77, 78, 79, 80, 84, 85, 86, 87, 87 inset, 88

Major classes of change from prior versions are listed below. Consult individual files named like map22-diff.txt for output files differencing from prior version to this version.
  • All readme files, dated folders and compressed tar files have been modified and renamed as necessary to redress the erroneous substitution of 2007 for 2008. No changes to IDs have occurred.

Saturday, July 26, 2008

BAtlas IDs: 4 more sets in Asia Minor, plus Cyprus

README file for Barrington Atlas Identifiers, version published 2007-07-26
Reference URL: http://atlantides.org/batlas

Background: http://horothesia.blogspot.com/search/label/batlasids
New maps covered in this release: 62, 63, 66, 72, 86
List of all maps presently covered: 22, 35, 36, 37, 38, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 65, 72, 73, 74, 75, 76, 77, 78, 79, 80, 86

Major classes of change from prior versions are listed below. Consult individual files named like map22-diff.txt for output files differencing from prior version to this version.

* No changes to previously issued files in this release

Tuesday, July 22, 2008

BAtlas IDs: 10 more maps

README file for Barrington Atlas Identifiers, version published 2007-07-22
Reference URL: http://atlantides.org/batlas

Background: http://horothesia.blogspot.com/search/label/batlasids
New maps covered in this release: 50, 51, 52, 53, 54, 56, 57, 58, 59, 60
List of all maps presently covered: 22, 35, 36, 37, 38, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 65, 73, 74, 75, 76, 77, 78, 79, 80

Major classes of change from prior versions are listed below. Consult individual files named like map22-diff.txt for output files differencing from prior version to this version.

* Still suppressing ID creation for roads; have also added suppression for "coastal change" (so far only seen in Map 53)
* No changes to previously issued files in this release