<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi everyone,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As I mentioned today, I recently was at a talk by Monika (not Anna!) from Tracing Networks. I made lots of (very rough) notes, unfortunately none of which I now understand! However to those with an interest in semantic web I have emailed them in the hope they may be of value to you, otherwise please ignore this.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cheers,<o:p></o:p></p><p class=MsoNormal><br>Tom.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><o:p> </o:p></b></p><p class=MsoNormal><b>Monika Solanki: <o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Background in structural engineering/computer science<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Colleagues - Prof. Jose Fiadeiro, Yi Hong, Prof. Lin Foxhall, Katherina Rebay-Salisbury.<br><br><o:p></o:p></p><p class=MsoNormal>Tracing networks - dealing with huge amounts of data (Monika started in 2009)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Interested in the Chaine operatoire<o:p></o:p></p><p class=MsoNormal><br>Monika wants to utilise the paradigm of Chaine operatoire to trace links through the data, and trace the links between people. The aim of her work is to investigate a network of contacts across and beyond the Mediterranean region between 1500 - 200 BC.<o:p></o:p></p><p class=MsoNormal><br>There are seven archaeological data sets incoporated into the tracing networks project, which hopes to set these in their wider social, economic and social contexts. Archaeologists study material artefacts, and by tracking these at every stage of their production, distribution, use and consumption across a large geographic region, it is hoped that they can trace the links between the people who made, used and taught others to make them.<o:p></o:p></p><p class=MsoNormal><br>Questions<o:p></o:p></p><p class=MsoNormal>How does technical knowledge move from one person to another?<o:p></o:p></p><p class=MsoNormal>How do people choose which particular knowledge to apply from their repertoire?<o:p></o:p></p><p class=MsoNormal>In what context does innovation appear?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Within semantic web there has been little work in the archaeological domain. Lots however has been done in the domains of cultural heritage and museum studies).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Data is placed into the TN-LOD cloud (Tracing Networks - Linked Open Data)<o:p></o:p></p><p class=MsoNormal><br>The aim is to find common aspects of the data sets and to link them. They also plan to link these datasets to the outside world by connecting to the CKAN-LOD (look this up). Also plan to link to closed community networks of archaeological data.<o:p></o:p></p><p class=MsoNormal><br>The vocabulary is based on the CIDOC-CRM. It is an ontology of 86 classes and 137 properties. It has been an international standard since 2006. The data is encoded in OWL 2.0, OWLDL and RDFS.<o:p></o:p></p><p class=MsoNormal><br>In order to input the data, they needed to translate excel and access files. The team looked at existing mapping frameworks, but they were not able to use these for mapping as they were too simplistic and could only do a one-to-one mapping. The relationships in the archaeological data were far more complicated than this.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Instead the team created their own transformation frameworks that they could input access and excel files into. These were ORM reverse engineered, created ELA rule-based transformations and allowed instance generation of the ontology. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Once they had created this framework, the question was waht do you do with it? And how do you motivate archaeologists to use it?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Therefore the team created SEA - the semantic explorer for archaeology<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The team recognised that the majority of time using this data was during the post-excavation phase. Therefore they designed their explorer to focus on archiving, querying and analysing the data within the framework.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>SEA is a web application. It uses a RESTful API for accessing the TN-LOD cloud. Archaeolgists can query the data then choose exactly how they want to visualise it. <o:p></o:p></p><p class=MsoNormal><br>One interesting part of the overall architecture of SEA was a natural language summariser to help archaeologists use the system if they don't have a detailed knowledge of semantic web. However some experience of semantic web is required to use it. The system also has an AJAX style autocomplete to assist with navigating the various relationships. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The explorer can visualise your query as a graph before searching, and also search for a specific node. The results of a query can be visualised as linked data or with Google Maps/Earth. It can also present statistics of the query in the form of bar charts, pie charts etc.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Each of your queries has to be specified in the form of RDF triples.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Some closely related work was identified to Tracing Networks:<o:p></o:p></p><p class=MsoNormal>D2RQ: Berlin (Transformation framework)<o:p></o:p></p><p class=MsoNormal>Virtuoso: Open link software (Transformation framework)<o:p></o:p></p><p class=MsoNormal>STAR: English Heritage<o:p></o:p></p><p class=MsoNormal>STELLAR: English Heritage<o:p></o:p></p><p class=MsoNormal>TRANSLATION: Southampton (Leif)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Monika's future work includes working with the transformation language to create a user friendly environment for editing the rules. She also plans to allow archaeologists to change the hierarchy of search results and wants to augment the support for inference making.<o:p></o:p></p></div></body></html>