Aha.  Additional discovery:

If you change this 

to this

that also fixes the problem.  

Namespaces (that's what xmlns stands for is XML namespace) have always given me a headache so I'm not positive, but I think the problem is this:

The :xx (or whatever) is called a prefix.  The other xmlns attributes listed in your document have prefixes (xmlns:xlink, xmlns:xsi) but this one doesn't.  If the root element (in this case <ead>) has an "unprefixed" xmlns -- in this case xmlns="urn:isbn:1-931666-22-9" -- then the processor assumes that all unprefixed elements in the rest of the document are part of THAT namespace.  In this case, the unprefixed elements in the ead document are NOT part of the URN namespace, they're part of the EAD namespace, so this causes a problem.  By adding a prefix, you remove this conflict.

Hope this helps!


-----Original Message-----
From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Dunn, Kathryn M.
Sent: Monday, December 06, 2010 9:44 AM
To: [log in to unmask]
Subject: XSLT for HTML display of schema-compliant EAD?

Hello EAD folks,

I'm wondering if anyone has a stylesheet that works with
schema-compliant EAD documents for in-browser transformation to HTML, or
advice on converting a stylesheet for DTD-compliant EAD to one for
schema-compliant EAD. 

I found this blog post while searching for information on stylesheets
for schema-valid EAD. 

Is everyone who is using schema-valid EAD using Archivists' Toolkit to
convert their finding aids to HTML?  I was surprised that I wasn't able
to readily locate a stylesheet that works with schema-valid EAD, but
maybe it's a more complicated issue than I realize.

Here are the DTD- and schema-valid versions of the EAD I'm working with: 

The main stylesheet is here:

It also uses a dsc stylesheet adapted from a stylesheet provided by
Michele Combs at her awesome workshop in Albany: 

Thanks very much in advance for any advice you can offer!


Katie Dunn
Technology & Metadata Librarian
Rensselaer Polytechnic Institute
[log in to unmask]