Hi Jay,
I haven't worked with transforming EAD much, but ran in to the same kind of problem in transforming METS Profile documents to html. 
As far as I could tell the culprit was a namespace declaration. 

So with:
<METS_Profile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation=" http://www.loc.gov/METS_Profile/  http://www.loc.gov/standards/mets/profile_docs/mets.profile.v1-2.xsd"
    xmlns=" http://www.loc.gov/METS_Profile/">

The output I got was one giant line of text.


When I removed the last xmlns:
<METS_Profile xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/METS_Profile/  http://www.loc.gov/standards/mets/profile_docs/mets.profile.v1-2.xsd">

I got the nicely formatted html I wanted.

This worked fine for me (I was transforming very few documents), but it may be that changing the namespace declaration isn't a good option in other situations.  I also don't know why this worked (since it worked, I stopped investigating :) and so it could be that there is something inherently flawed in the approach. 
It is a dark art indeed.
Arwen
 
-----------
Arwen Hutt
Metadata Specialist
University of California, San Diego
[log in to unmask]
(858) 822-3876
-----------
 
On 8/24/07, Mike Ferrando <[log in to unmask]> wrote:
Jay,
I must admit that I do not use Relax NG nor Oxygen.

However, I remember that Michele Combs [log in to unmask] had the same problems with Oxygen on this list and resolved it successfully.

Hope this helps,
Mike Ferrando
Library Technician
Library of Congress
Washington, DC
(202) 707-4454

----- Original Message ----
From: Jay Moore < [log in to unmask]>
To: [log in to unmask]
Sent: Thursday, August 23, 2007 2:22:15 PM
Subject: Re: Transformation ead schema

Mike,

 

Thanks for the reply on this.  It would have been handy for me to include in my initial message the <ead> declaration, indeed.  Here's what I have:

 

 xsi:schemaLocation="urn:isbn:1-931666-22-9 http://www.loc.gov/ead/ead.xsd"

 xmlns="urn:isbn:1-931666-22-9"

 xmlns:xlink=" http://www.w3.org/1999/xlink">

 

I confess to believing that namespaces are a black art.

 

I had also read that Version 2 of the XSL/T style sheet should use Saxon 8B or 8SA or higher, but I hadn't acted on it yet.  Joseph Greene has been lending me a hand offline and told me where in the oXygen style sheet debugger where to set the parser.  I fixed it, and yet it has not fixed the html.

 

Thanks for any hints you can offer, Mike.

 

Jay Moore

NOAA Project Archivist

The Mariners' Museum Library and Archives

[log in to unmask]

 

-----Original Message-----
From: Encoded Archival Description List [mailto: [log in to unmask]] On Behalf Of Mike Ferrando
Sent: Wednesday, August 22, 2007 6:30 PM
To: [log in to unmask]
Subject: Re: Transformation ead schema

 

Jay,
I would suggest that you check to see if the schema namespace is declared in your ead document root node.

<ead xmlns="">

Also, I would update your SAXON to at least 6.5.5 or 8.X.

I know that SAXON 8.X is schema aware, I am not sure about 6.5.5.

Mike Ferrando
Library Technician
Library of Congress
Washington, DC
(202) 707-4454

----- Original Message ----
From: Jay Moore < [log in to unmask]>
To: [log in to unmask]
Sent: Wednesday, August 22, 2007 11:00:15 AM
Subject: Transformation ead schema

Dear all,

 

I am attempting to transform a finding aid that uses the EAD schema into html.  I'm using oXygen 8.2.  The transformation engine is, I gather, Saxon 6.5.2.  The XSL style sheet I am using from the EAD Cookbook 2002 edition (the combo, for anyone who knows, is eadcbs1.xsl and the include file dsc1.xsl that formats the <dsc>).  Oxygen tells me that I have valid EAD, and after I fixed a couple of apostrophe errors, that the style sheet parses. The finding aid itself is done up through the sub-series level, with no file-level information yet. When I tell oXygen to transform the document, it does so in a nice html document that has absolutely no formatting in it no paragraphs, no headings, no centering, no nothing.  Just a nice continuous line of text.  At least the EAD tags aren't also displaying I had that trouble earlier!

 

As you can see, I'm a pretty raw novice.  If anyone has seen this sort of thing before, please let me know how I might fix it!

 

Thanks!

 

Jay Moore

NOAA Project Archivist

The Mariners' Museum Library and Archives

[log in to unmask]

 

 


Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us.




Be a better Globetrotter. Get better travel answers from someone who knows.
Yahoo! Answers - Check it out.