<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Data Portability in Paleoanthropology</title>
	<atom:link href="http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/feed/" rel="self" type="application/rss+xml" />
	<link>http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/</link>
	<description>Beyond bones &#38; stones</description>
	<lastBuildDate>Wed, 30 May 2012 15:52:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Lugal</title>
		<link>http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/#comment-9171</link>
		<dc:creator><![CDATA[Lugal]]></dc:creator>
		<pubDate>Fri, 11 Jan 2008 19:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/#comment-9171</guid>
		<description><![CDATA[Since archaeological data sets are so frequently tied to national surveys, CRM, and other such projects with legal implications, there has been a lot of ink spilled discussing data interchange between projects. But the underlying problem, that each project has its own highly customized database schema, is the same in archy as it seems to be in paleoanthro. An increasing number of projects are now putting their databases online, which facilitates data dissemination, but there aren’t any good systems that I know of for broadly applicable database schemas or other methods of data sharing between projects.

One site that’s been getting a lot of buzz lately, hosting multiple high-profile projects’ databases is Open Context (http://www.opencontext.org/)--so the answer to your second question is “yes.” But I don’t know whether anyone is using them yet for actual research.

Also, there’s been at least one serious attempt at general XML schema for archaeology, ArchaeoML (http://ochre.lib.uchicago.edu/index_files/ArchaeoML_Schema.htm). I haven’t had the chance to dig into it, and I don’t know if it’s still being developed, but it would be a good place for an interested archaeologist to start.

And as for Atom/RSS, in concert with a specialized XML interchange format, it might make a lot of sense for announcing changes. That is, let each project use its own database but create the tools (as Paul suggests) for exporting the data into a common XML schema, and use RSS to announce the availability of new data to all interested parties. That way, we could use best-of-breed solutions for data storage, data dissemination, and data sharing, without diluting the quality of any single component by mashing it all together.

Unfortunately, I doubt that a schema for the interchange of paleoanthro data would be useful for archy, or vice-versa.]]></description>
		<content:encoded><![CDATA[<p>Since archaeological data sets are so frequently tied to national surveys, CRM, and other such projects with legal implications, there has been a lot of ink spilled discussing data interchange between projects. But the underlying problem, that each project has its own highly customized database schema, is the same in archy as it seems to be in paleoanthro. An increasing number of projects are now putting their databases online, which facilitates data dissemination, but there aren’t any good systems that I know of for broadly applicable database schemas or other methods of data sharing between projects.</p>
<p>One site that’s been getting a lot of buzz lately, hosting multiple high-profile projects’ databases is Open Context (<a href="http://www.opencontext.org/" rel="nofollow">http://www.opencontext.org/</a>)&#8211;so the answer to your second question is “yes.” But I don’t know whether anyone is using them yet for actual research.</p>
<p>Also, there’s been at least one serious attempt at general XML schema for archaeology, ArchaeoML (<a href="http://ochre.lib.uchicago.edu/index_files/ArchaeoML_Schema.htm" rel="nofollow">http://ochre.lib.uchicago.edu/index_files/ArchaeoML_Schema.htm</a>). I haven’t had the chance to dig into it, and I don’t know if it’s still being developed, but it would be a good place for an interested archaeologist to start.</p>
<p>And as for Atom/RSS, in concert with a specialized XML interchange format, it might make a lot of sense for announcing changes. That is, let each project use its own database but create the tools (as Paul suggests) for exporting the data into a common XML schema, and use RSS to announce the availability of new data to all interested parties. That way, we could use best-of-breed solutions for data storage, data dissemination, and data sharing, without diluting the quality of any single component by mashing it all together.</p>
<p>Unfortunately, I doubt that a schema for the interchange of paleoanthro data would be useful for archy, or vice-versa.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kambiz</title>
		<link>http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/#comment-9168</link>
		<dc:creator><![CDATA[Kambiz]]></dc:creator>
		<pubDate>Fri, 11 Jan 2008 18:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/#comment-9168</guid>
		<description><![CDATA[Hey Paul,

Yeah, I think I didn&#039;t clarify in the post that I&#039;m not saying RSS is the format to do this. Rather, I think the way RSS is distributed and aggregated is the way paleoanthropological data needs to be shared. This has to be done with a new XML schema. The paleoanthropolgical community needs to sit down and agree upon a predetermined set of fields. Then people will need to just have their databases be exported and then published. Anyways, thanks for catching that!

I hope that paleoanthropologists will think about this way of executing their data sharing because having to reformat databases is a big pain in my opinion. Or also, if the big data portability initiative in the technology sector finds a better way, which I have faith they do, that they&#039;ll use that model as a way of sharing paleoanthropological data.

Kambiz]]></description>
		<content:encoded><![CDATA[<p>Hey Paul,</p>
<p>Yeah, I think I didn&#8217;t clarify in the post that I&#8217;m not saying RSS is the format to do this. Rather, I think the way RSS is distributed and aggregated is the way paleoanthropological data needs to be shared. This has to be done with a new XML schema. The paleoanthropolgical community needs to sit down and agree upon a predetermined set of fields. Then people will need to just have their databases be exported and then published. Anyways, thanks for catching that!</p>
<p>I hope that paleoanthropologists will think about this way of executing their data sharing because having to reformat databases is a big pain in my opinion. Or also, if the big data portability initiative in the technology sector finds a better way, which I have faith they do, that they&#8217;ll use that model as a way of sharing paleoanthropological data.</p>
<p>Kambiz</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kambiz</title>
		<link>http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/#comment-9166</link>
		<dc:creator><![CDATA[Kambiz]]></dc:creator>
		<pubDate>Fri, 11 Jan 2008 18:20:17 +0000</pubDate>
		<guid isPermaLink="false">http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/#comment-9166</guid>
		<description><![CDATA[lugal, yeah I think making some sort of XML method, published and aggregated similar to RSS is the way to go. Aside from that, are you facing similar problems with archaeological data sets? Are people willing to have their data be shared and even hosted on other databases?]]></description>
		<content:encoded><![CDATA[<p>lugal, yeah I think making some sort of XML method, published and aggregated similar to RSS is the way to go. Aside from that, are you facing similar problems with archaeological data sets? Are people willing to have their data be shared and even hosted on other databases?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Wren</title>
		<link>http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/#comment-9125</link>
		<dc:creator><![CDATA[Paul Wren]]></dc:creator>
		<pubDate>Fri, 11 Jan 2008 04:39:27 +0000</pubDate>
		<guid isPermaLink="false">http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/#comment-9125</guid>
		<description><![CDATA[You are on the correct path-- everyone can store their data in whatever database formats they want, and then make that information available to colleagues in XML.

Unfortunately, the definitions (schema) for RSS and Atom are far too simplistic and restricted to adequately represent all of the information paleoanthropologists would desire, so a custom XML schema should be developed.

Simple tools would also be needed to dump the contents of each specific database into the common formal XML files, but this is not a show-stopper.  It could be managed as an open-source software effort.

There are a lot of anthropologists who are self-taught programmers, and a lot of programmers who are self-taught anthropologists... I&#039;m sure there will be people available to do this.]]></description>
		<content:encoded><![CDATA[<p>You are on the correct path&#8211; everyone can store their data in whatever database formats they want, and then make that information available to colleagues in XML.</p>
<p>Unfortunately, the definitions (schema) for RSS and Atom are far too simplistic and restricted to adequately represent all of the information paleoanthropologists would desire, so a custom XML schema should be developed.</p>
<p>Simple tools would also be needed to dump the contents of each specific database into the common formal XML files, but this is not a show-stopper.  It could be managed as an open-source software effort.</p>
<p>There are a lot of anthropologists who are self-taught programmers, and a lot of programmers who are self-taught anthropologists&#8230; I&#8217;m sure there will be people available to do this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lugal</title>
		<link>http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/#comment-9114</link>
		<dc:creator><![CDATA[lugal]]></dc:creator>
		<pubDate>Fri, 11 Jan 2008 02:05:49 +0000</pubDate>
		<guid isPermaLink="false">http://anthropology.net/2008/01/10/data-portability-in-paleoanthropology/#comment-9114</guid>
		<description><![CDATA[I’ve been struggling with the same problems w/ archaeological datasets, and think that you might be onto something. I’m not sure about using RSS per se, but the idea of using a common interchange format (and especially an XML one like Atom or RSS) makes a lot of sense. Such solutions, in my experience, are rarely discussed—but probably, for the reasons you state, the path of least resistance.]]></description>
		<content:encoded><![CDATA[<p>I’ve been struggling with the same problems w/ archaeological datasets, and think that you might be onto something. I’m not sure about using RSS per se, but the idea of using a common interchange format (and especially an XML one like Atom or RSS) makes a lot of sense. Such solutions, in my experience, are rarely discussed—but probably, for the reasons you state, the path of least resistance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

