<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>EAD3 and the consequences of the new version</title>
		<description>Discuss EAD3 and the consequences of the new version</description>
		<link>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version</link>
		<lastBuildDate>Fri, 17 Apr 2026 00:49:27 +0200</lastBuildDate>
		<generator>JComments</generator>
		<atom:link href="http://apex-project.eu/index.php/en/component/jcomments/feed/com_content/149" rel="self" type="application/rss+xml" />
		<item>
			<title>Kerstin Arnold says:</title>
			<link>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-635</link>
			<description><![CDATA[Dear Xavier, thanks very much. Your project sounds great - looking forward to hearing more about it. As you've seen, EAD3 has been officially adopted now by the Society of American Archivists and will become available, when SAA has their annual meeting next week. This will also include a default XSLT for transforming EAD 2002 to EAD3, which we at the Archives Portal Europe are very interested in. Our mapping guide for apeEAD also includes a chapter with some first mapping ideas in our context for moving to EAD3. You can access the document here: http://www.apex-project.eu/images/docs/D2.6D4.8_mapping-guide_apeEAD.pdf. With regard to LOD and EAD3, I think the Technical Subcommittee will be glad to get some examples from the community for this, but there don't exist any official recommendations yet. You might however want to have a look at what our colleagues at the Archives Hub have done with EAD 2002 and LOD: http://locah.archiveshub.ac.uk/. Best wishes, Kerstin]]></description>
			<dc:creator>Kerstin Arnold</dc:creator>
			<pubDate>Thu, 13 Aug 2015 14:47:15 +0200</pubDate>
			<guid>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-635</guid>
		</item>
		<item>
			<title>Xavier Agenjo says:</title>
			<link>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-555</link>
			<description><![CDATA[I think it is a very interesting article and I like to congratulate you for the effort to bring clarity to this issue, which it really needs. This year Digibís is going to undertake a project with the historical archives of Galicia in the northwest of Spain. We have planned to used DIGIHUB (which is the software used by Hispana) and to harvest the Galician archives. They use (or they are going to use) EAD3 and EAC as well, but we have planned to implement EAD3 in our software DIGIARCH. I wonder if there is available some detailed information about the use of Linked Open Data techniques related to EAD3 I have just read this: http://www.dlib.org/dlib/march15/park/03park.html but I feel I need some more features. Greetings]]></description>
			<dc:creator>Xavier Agenjo</dc:creator>
			<pubDate>Wed, 18 Mar 2015 17:39:04 +0100</pubDate>
			<guid>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-555</guid>
		</item>
		<item>
			<title>Karsten Kühnel says:</title>
			<link>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-5</link>
			<description><![CDATA[Hi Kelcy and Kerstin, thank you for this information! Best, Karsten ]]></description>
			<dc:creator>Karsten Kühnel</dc:creator>
			<pubDate>Fri, 07 Mar 2014 13:06:54 +0100</pubDate>
			<guid>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-5</guid>
		</item>
		<item>
			<title>Kerstin Arnold says:</title>
			<link>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-4</link>
			<description><![CDATA[Hi, thanks very much, Kelcy, for your feedback. Good to know that the Tag Library team already is working on this improvement of the documentation for EAD3. I can imagine, there's a lot to keep up with. So, to answer Karsten's question: in EAD3 the attribute @relator is supposed to be used for describing the role of a function. Best, Kerstin]]></description>
			<dc:creator>Kerstin Arnold</dc:creator>
			<pubDate>Fri, 07 Mar 2014 10:26:00 +0100</pubDate>
			<guid>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-4</guid>
		</item>
		<item>
			<title>Kelcy Shepherd says:</title>
			<link>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-3</link>
			<description><![CDATA[Hi Karsten and Kerstin, Yes, unfortunately the controlled access elements were among those that were not updated in time for the gamma release, so they reflected the beta schema. There is actually an attribute that is intended to be used for the same kind of information formerly in role. The new attribute is relator, and the Editorial Team will work to make that change clear in the Tag Library. Cheers, Kelcy]]></description>
			<dc:creator>Kelcy Shepherd</dc:creator>
			<pubDate>Thu, 06 Mar 2014 23:17:25 +0100</pubDate>
			<guid>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-3</guid>
		</item>
		<item>
			<title>Kerstin Arnold says:</title>
			<link>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-2</link>
			<description><![CDATA[Dear Karsten, thanks very much for your question. It's true, that the EAD Tag Library (as still being work in progress) does for now not include the description of attributes. With regard to the element function it also - unfortunately - only displays the status from the EAD3 beta. With the EAD3 gamma some more attributes have been added to all the controlled access elements, among others the attribute @localtype. It's a rather general option, but it could be an option to identify roles of functions. However, I am sure, the colleagues from the Tag Library Team will be grateful for this hint and if you'd want to propose a more distinctive attribute for this use, the TS-EAD will be happy to include your suggestion in the final revision. Please use the form at the SAA website to provide your feedback directly: http://www2.archivists.org/groups/technical-subcommittee-on-encoded-archival-description-ead/ead-revision-comments. Best wishes, Kerstin]]></description>
			<dc:creator>Kerstin Arnold</dc:creator>
			<pubDate>Mon, 24 Feb 2014 11:40:09 +0100</pubDate>
			<guid>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-2</guid>
		</item>
		<item>
			<title>Karsten Kühnel says:</title>
			<link>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-1</link>
			<description><![CDATA[My question refers to the EAD3 tag library. I miss the attribute @role at in the EAD3 tag library. I don't know how I could describe which role the function performs, like e.g. [sc. records ...] "created by performing" or as "re-used for" and so on. Is there any possibility to describe the quality or roles of functions (similar as it is already done in ). Emphasising the description of such kind of relationships between records and entities like functions or agents could support searching tools based on conceptual reference models, similar to CIDOC CRM etc.; that's my opinion. May be, a (still missing) catalogue of such function roles should be linked as a related authority record.]]></description>
			<dc:creator>Karsten Kühnel</dc:creator>
			<pubDate>Wed, 19 Feb 2014 16:35:49 +0100</pubDate>
			<guid>http://apex-project.eu/index.php/en/articles/149-ead3-and-the-consequences-of-the-new-version#comment-1</guid>
		</item>
	</channel>
</rss>
