Depending on the version of MSXML you may need to have a slightly
different reference in the stylesheet. The w3c recommendation was
released in November 1999 and IE5.5 was released before that. The
transformaion was based on a draft version of the recommendation and has
quite limited functionality and used the working draft t namespace.
<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl"> You proabably
don't want to limit your functionality in this way however,
It is better to upgrade the MSXML to at least 3.0 so that you can use
stylesheets into the future. If you have Internet Explorer 5.5 you
will have to upgrade the MSXML parser to 3.0. The URL at
www.msdn.microsoft.com always changes but if you search for XML Parser
3.0 or the like you will be able to find the upgrade.
The BEST option is to upgrade to Internet Explorer 6.0 which has the
While you are at the microsoft site there are a few other things you
might want to check out
1)XSLT fAQ page
2)XSLT Utilities and Samples You Can Download
3) Internet Explorer Tools for Validating XML and Viewing XSLT Output
The third is a great little tool that gives you menu options when you
right click the mouse on the page that allow you to validate a document
and view the HTML outout.
Of course in a few days these URLS will change :)
Mozilla is another browser that does a pretty good job these days with
Of course there are limits to what you can do in the browser - you can
not use the XSLT 1.1 extensions that produce multiple documents (thus
frames are problematic) and you have to make sure your stylesheets that
use saxon are not using any of the extensions that are saxon specific.
And you want the version number to be 1.0 not 1.1
Another option altogether, if you want to display your finding aid in
reading order (ie you don't have to move things around), is to use CSS.
You can apply styles to element names just as you would in HTML. You can
use visibility:hidden to make elements invisible.
Do remember that whether you used XSLT or CSS you are revealing your
source document to the world. That means that you should not use these
methods if there is information in your documents that is sensitive or
that you would rather the world didn't know about.
Anyone can use "view source" to see your document in its entirely.
And obviously, using native XML really limits your audience to those who
have the newest browsers.
Aziza Technology Associates
Colleen Goldsworthy wrote:
>I wonder if anyone knows how to solve this problem
>I have many EAD files which when I run them through SAXON render very nicely into HTML files and are then posted on the web. However I have had a directive to render these files directly on the browser in xml - i.e. the stylesheet reference is included in the EAD file and the address in the internet bar shows Blah.xml instead of Blah.html.
>I have tried many things but am unable to get this to happen - it seems that the links to the individual files just will not render. Is this something to do with MSXML and SAXON differences. I have done the same thing with TEI Lite and Dublin Core files and have had no problem.
>Any assistance would be gratefully received
>University of Natal
>[log in to unmask]