Print

Print


Provided you are not assuming any of the default values in the DTD,  
there is no reason to invoke the DTD. Just serve the EAD as well- 
formed. This will speed processing on the client-side. Once this is  
done, if the finding aid still does not render, then the problem will  
be isolated to the URL of the stylesheet, or perhaps security issues  
associated with a remote client requesting files.

Of course one way to get around all of these possible problems is to  
do as Michael at first reasonably assumed was being done, convert the  
ead-encoded finding aid to html in Oxygen and serve the resulting  
html. There will be (or should not be) any URL or security issues  
associated with that technique. And unless I am overlooking something,  
there is no advantage to client-side rendering of the XML. In fact,  
one gets around the inconsistencies in the different browsers'  
handling of XSLT even if one then has to deal with inconsistencies in  
how browsers render html and css.

On Mar 31, 2010, at 6:20 AM, Fox, Michael wrote:

> I would also be interested to hear the experiences of institutions  
> that choose to point to external web locations for the source of  
> their dtd, schema and stylesheet files rather than relying on local  
> versions of these files.
>
> Michael Fox
>
>
>
> ________________________________________
> From: Encoded Archival Description List [[log in to unmask]] On Behalf Of  
> Michele R Combs [[log in to unmask]]
> Sent: Tuesday, March 30, 2010 11:57 AM
> To: [log in to unmask]
> Subject: Re: problem with a reference to an xsl stylesheet i do not  
> have
>
> Wouldn't that just be for transformation on your local PC using  
> Oxygen?  Once you have the file online with a callout to an XSL  
> style sheet, doesn't the browser do all the work?
>
> Michele
>
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]] On  
> Behalf Of Fox, Michael
> Sent: Tuesday, March 30, 2010 11:56 AM
> To: [log in to unmask]
> Subject: Re: problem with a reference to an xsl stylesheet i do not  
> have
>
> I believe that you have to create a transformation scenario in  
> Oxygen that directs the XSLT engine to use the stylesheet  
> instruction that you reference at the beginning of the document.
>
> Michael
>
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]] On  
> Behalf Of Anna Kresmer
> Sent: Tuesday, March 30, 2010 7:49 AM
> To: [log in to unmask]
> Subject: problem with a reference to an xsl stylesheet i do not have
>
> Hello All,
>
>        I'm a new archivist working with my IT department to get our  
> very
> first EAD finding aid online. This is a new experience to all of us  
> and we
> have run into a problem. We set up a directory on our web server  
> with all
> the proper files (EAD DTD, the EAD file, an XSL stylesheet, and a CSS
> file) all linked together as they should be. It all appears to work  
> fine,
> until you try to visit the URL.
>        The IT department identified a problem with one line of code in
> the EAD XML file. It references an XSL stylesheet we do not have. This
> stylesheet reference was left in the EAD template that came with  
> Oxygen
> Editor and was presumable used by the archivist who created/donated  
> the
> EAD template to Oxygen (see the middle line, please):
>
> <?xml version="1.0" encoding="utf-8"?>
> <?xml-stylesheet type="text/xsl" href="http://nwda-
> db.wsulibs.wsu.edu/xsl/project.xsl"?>
> <!DOCTYPE ead PUBLIC "+//ISBN 1-931666-00-8//DTD ead.dtd (Encoded  
> Archival
> Description (EAD) Version 2002)//EN" "ead.dtd">
>
>
> We removed this reference and got a white page of the finding aid text
> with no formatting at all. I then replaced it with the references to  
> the
> correct XSL and CSS stylesheet, like so:
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <!DOCTYPE ead PUBLIC "+//ISBN 1-931666-00-8//DTD ead.dtd (Encoded  
> Archival
> Description (EAD) Version 2002)//EN" "ead.dtd">
> <?xml-stylesheet type="text/xsl" href="ead_divs.xsl"?>
> <?xml-stylesheet type="text/css" href="ead_divs.css"?>
>
> But this does not fix the problem. Loading the URL just gets an error
> message:
> The page cannot be found
> The page you are looking for might have been removed, had its name
> changed, or is temporarily unavailable.
> ________________________________________
> Please try the following:
> *       Make sure that the Web site address displayed in the address  
> bar
> of your browser is spelled and formatted correctly.
> *       If you reached this page by clicking a link, contact the Web  
> site
> administrator to alert them that the link is incorrectly formatted.
> *       Click the Back button to try another link.
> HTTP Error 404 - File or directory not found.
> Internet Information Services (IIS)
> ________________________________________
> Technical Information (for support personnel)
> *       Go to Microsoft Product Support Services and perform a title
> search for the words HTTP and 404.
> *       Open IIS Help, which is accessible in IIS Manager (inetmgr),  
> and
> search for topics titled Web Site Setup, Common Administrative  
> Tasks, and
> About Custom Error Messages.
>
>
> Is there anyone out there who can shed some light on what I am doing
> wrong? According to Oxygen, my EAD file is valid, well-formed, and the
> transformation scenario loads properly when I test it on my  
> computer. Am I
> missing some all important line of code?
>
> Any help would be greatly appreciated.
> Thank you,