Interesting (and a bit annoying!) about the dates.  Wonder if that's another glitch in the schema that needs to be addressed.  I'd encourage you submit this to the EAD Help Pages -- this would be a great start for a page on the DTD-to-Schema process.

Do you by chance have a comparable list of changes that had to be made to the style sheet and/or your output processing (other than the obvious ones to accommodate the changes to the EAD) ?  For example, we use Saxon as our XSLT processor and not all versions of Saxon are schema-aware (, so for us it would mean upgrading to a different version, or to something else.

-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Karen Miller
Sent: Thursday, April 28, 2011 12:26 PM
To: [log in to unmask]
Subject: Re: @mainagencycode question - schema vs DTD

We converted our finding aids to use a schema about a year ago at
Northwestern University Library. We're using a local schema, but it just has
some very minor changes to the schema that LC maintains. Here's a list of
the changes we found we had to make to accommodate the schema instead of a
DTD. Most of these changes can be done with search-and-replace, but I've
noted a few places where you'll need to be a bit careful with it.  There may
be more changes than these, but this should help.

Changes from using a DTD to using an XSD:

1. Replace the DOCTYPE statement with the XSD namespace declaration.

2. Remove the <ead> element, as it appears in the declaration above and is

3. Replace the attribute value 




4. Replace the mainagency attribute (you already know about this one - it
gave me fits, too).

5. The following attributes in the <extpr> or <dao> elements must have the
"xlink:" prepended to them:

		 href  [make sure to use search & replace on "href=" because
otherwise a valid  
			<archref@href> may be broken]
		 linktype [this becomes xlink:type, not xlink:linktype, so
it's not as easy as just adding the prefix]

like this: 



6. Also for <extptr> and <dao>, the attribute value "onrequest" for @actuate
must be changed to "onRequest"; similarly "onload" must change to "onLoad".

7. The subject attribute is no longer available in the <title> element.

8. Normal attributes in date fields can no longer be 6 digits - they must be
of one of these formats:



The "day" portion cannot be "00". I.e., 20090200 is not valid but 20090201
[possible logic: if a date is four digits, add 00 to the end. If the date is
4digits/4digits, add 00 to the end of the first four, 28, 30 or 31 to the
second four depending on month. Or just add 30.]

Karen D. Miller
Monographic/Digital Projects Cataloger
Bibliographic Services Dept.
Northwestern University Library
Evanston, IL 
[log in to unmask]

-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On
Behalf Of Terry Catapano
Sent: Thursday, April 28, 2011 10:19 AM
To: [log in to unmask]
Subject: Re: @mainagencycode question - schema vs DTD


Looks like you're right.

The mainagencycode attribute in the schema version uses the locally 
defined data.repositorycode datatype, the pattern of which does start with 
two letter country codes (apparently in conformance to ISO 15511 (ISIL)):


This does contradict the tag library which states that the country code 
portion should be placed in the countrycode attribute -- a co-ocurrence 
constraint not expressible in DTD, BTW. It's probably something which 
should be addressed in the next version of EAD.

In the meantime, while the current dtd2schema.xsl stylesheet does not 
address the issue, a template which concatenates the countrycode attribute 
value (if present) with the mainagencycode attribute (if it does not begin 
with a country code) could probably be added.


Wed, 27 Apr 2011, Mark A. Matienzo wrote:

> A colleague is looking at migrating some DTD-compliant EAD finding
> aids to be schema-compliant, and the @mainagencycode  within the eadid
> is set to not have a country code prefix. As far as I can tell, the
> @mainagencycode values within schema-compliant EAD are constrained to
> ISO 15511 values *with* country codes, but this constraint is not
> there for DTD-compliant EAD.
> I'd like to verify this is correct, as the tag library for EAD 2002
> <> specifies the following:
> [quote]
> MAINAGENCYCODE -- A code in <eadid> compliant with ISO/DIS 15511
> Information and Documentation International Standard Identifier for
> Libraries and Related Organizations (ISIL). Values should be supplied
> without the country code, which should be placed instead in the
> COUNTRYCODE attribute.
> [/quote]
> However, my colleague is unable to get @mainagencycode values without
> the country code prefix to validate, leading the validation engine to
> state that codes such as "US-CtY" are invalid.
> Mark A. Matienzo
> Digital Archivist, Manuscripts and Archives
> Yale University Library

Terry Catapano
Special Collections Analyst/Librarian
Columbia University Libraries Digital Program
[log in to unmask]