Stefano Costa bio photo

Stefano Costa

Email Twitter Github

A few months ago, we found out through Antiquist that DAI (Deutsches Archäologisches Institut, i.e. the German Archaeological Institute) has published a set of IT Guidelines for all its research projects. Even though it’s primarily intended for a German audience (German-speaking too, obviously) it is a very interesting piece of standards. You can get it from the DAI website in PDF. With some help from tools like Google Translate, one can even get an idea of what these guidelines say also without being a native speaker. We did, and here is a partial summary of the document. The DAI IT guidelines refer to other similar standards, among them the MINERVA EC Technical Guidelines, which are going to be addressed in another post. The main technical areas addressed in the DAI guidelines are those one would expect. For most data types, the base concept is that the most well-known standards should be used, even though there are some differences between the various fields (most notably DWG is an ugly proprietary format — even though recently some efforts have been done to support it with free/libre software).

  DAI guidelines
text data UTF-8 or UTF-16, XML (including ODT), PDF/A
raster graphics TIFF, DNG (JPEG to be avoided)
vector graphics DWG, DXF (de facto standard)
3D data U3D, VRML 2.0
databases (L)AMP (desktop databases to be avoided)
GIS GeoTIFF, ESRI Shapefiles
audio and video WAV, AIFF, MPEG-1, MPEG-2

One could say these recommendations aim to a lowest common point of interoperability and preservation, and it is probably so for a large part (but, see recent notes about Shapefile by QGIS’s Gary Sherman who doesn’t accept the definition of Shapefile as a dead format). However the DAI guidelines look good, not just in the details but also in the general requirements for procedures and prior planning and the clear remark that the adoption and use of open source software has to be the necessary aim of any project design.

There is no mention in this document of using software formats like those used by Microsoft Word or Microsoft Access, and there’s a good reason behind this of course. If you ever tried opening a .docx document with Microsoft Word 2003 you should already know why.

As stated by Olla Mulholland:

as the DAI is one of the biggest players in classical archaeological research, the guidelines may well come to have an influence beyond the institute's own projects.

We hope so.