I will caution you that if you are doing client side processing of your 
XML, there is not wide support for version 2.0 yet.  You'll want to 
stick with 1.0 unless you are processing your files locally with 
something like Saxon or your server has the capability to use Saxon on 
server side transformations.

Mark

On 3/31/2010 11:40 AM, Amy McCrory wrote:
> The style sheet in questions is one that I uploaded to the
> user-contributed stylesheets section of the EAD help pages,
> http://www.archivists.org/saagroups/ead/stylesheets.html
>
> I've changed job responsibilities since I last edited that file, and am
> too out of touch with XSLT at this point to bring it into compliance
> with XSLT 2.0. If someone else would like to edit it and re-post it,
> that would be great! But if not, it would be best to remove it from the
> help pages, as it will continue to cause people problems.
>
> If I don't hear from anyone about fixing it up, I'll request to have it
> removed.
>
> Amy
>
>
> At 12:02 PM 3/31/2010, you wrote:
>> Looks like your XSL code is designed to write multiple output HTML
>> files to the file system, i.e. it's set up to produce static HTML
>> files using saxon or oxygen or something. The way the browser works is
>> to render the HTML dynamically, in its memory; it doesn't write files
>> to the file system.
>>
>> Your best bet may be to go back to the earlier suggestion of producing
>> static HTML rather than serving up the EAD directly, since it looks
>> your style sheet is designed to do that. Another option is to pick a
>> different style sheet, one that doesn't rely on multiple named output
>> files.
>>
>> It might also be important to note that xsl:document exists only in
>> XSLT 1.1 (the syntax in XSLT2.0 is <xsl:result-document>) and XSLT 1.1
>> is not a supported standard. It was abandoned in favor of XSLT 2.0
>> (see http://www.w3.org/TR/xslt11/ , "Status of this document"). This
>> means you may run into additional issues, so again, choosing a
>> different style sheet might be the wisest course.
>>
>> Michele
>>
>>
>> -----Original Message-----
>> From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf
>> Of Anna Kresmer
>> Sent: Wednesday, March 31, 2010 11:06 AM
>> To: [log in to unmask]
>> Subject: Re: again, problem with a reference to an xsl stylesheet i do
>> not have
>>
>> Thanks a lot! I moved the doctype-public attribute to the xsl:output
>> element and that has made that error message go away. I also removed the
>> reference to the Saxon name space, which does not appear to have caused a
>> problem. The bit of code now reads like this:
>>
>> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>> version="1.1">
>> <xsl:strip-space elements="*"/>
>> <xsl:output encoding="ISO-8859-1" doctype-public="-//W3C//DTD HTML 4.0
>> Transitional//EN" method="html"/>
>>
>>
>> However, fix one error and another one makes itself known. I now have a
>> pair of errors linked to 2 xsl:document attributes. The lines of code
>> look
>> like this:
>>
>> <xsl:document method="html" href="{$file}.html">
>>
>> <xsl:document method="html" href="{$file}recordgrp{$recordgrp}.html">
>>
>> In both cases, there is a jagged red line under the tml">. Each of these
>> lines of code are part of sections that instruct the stylesheet to create
>> a new page (either for the collection-level description or for each
>> series
>> of the finding aid).
>>
>> The error codes linked to each of them look like this:
>>
>> Description: Attribute @method is not allowed on element <xsl:document>
>>
>> Description: Attribute @href is not allowed on element <xsl:document>
>>
>> I do not have a clue what to do with this one. Any ideas?
>>
>> Sorry to take up so much time,
>> Anna
>
> ----------------------------------------------------------------------
> Amy McCrory
> Digital Imaging Specialist, Preservation Department
> Room 6044 Ackerman Library
> 610 Ackerman Road
> The Ohio State University Libraries
> Columbus, OH 43202
> (614) 292-8647