-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I did some checks with EAD 2002 DTD, XML Schema, and Relax NG and found,
that the schemas declare the "urn:isbn:1-931666-22-9" namespace for all
elements, but the DTD does not. Is this right? Is there a rationale for
this behaviour?
Thanks,
Stefan
Am 08.12.2010 17:18, schrieb Custer, Mark:
> As a follow-up (since I've just now read the rest of the messages on the listserv that I hadn't yet received in my inbox):
>
> Just follow the examples that you'll see in the AT stylesheets. Also, don't use stylesheet version 1.1 (you should be fine using version 1.0; I just took a quick look at your stylesheet, but didn't see anything 2.0 related). So, your XSLT header would be more like:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <xsl:stylesheet xmlns="http://www.w3.org/1999/xhtml"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
> xmlns:ead="urn:isbn:1-931666-22-9"
> xmlns:xlink="http://www.w3.org/1999/xlink"
>
> Not:
>
> <xsl:stylesheet version="1.1">
>
>
> And then just make sure to add those namespace prefixes ("ead:", "xlink:", etc., when appropriate) within your stylesheet(s), and then everything should work fine.
>
>
> Mark Custer
> [log in to unmask]
> 252-328-5389
>
>
>
> -----Original Message-----
> From: Custer, Mark
> Sent: Wednesday, December 08, 2010 10:55 AM
> To: [log in to unmask]
> Subject: RE: XSLT for HTML display of schema-compliant EAD?
>
> Kathryn,
>
> There's no need to delete the xmlns declaration within the file. You'll just need to update your current stylesheet to include the EAD namespace. So, wherever you've got something like select="//scopecontent", or match="scopecontent", you'd change that to:
>
> Select="//ead:scopecontent, and match="ead:scopecontent".
>
> Also, I'm not sure what you're asking about with the Archivists' Toolkit (as any EAD file that the AT creates will be schema-valid), but the AT does contain a few stylesheets (such as "at_eadToHtml.xsl" and "at_eadToPDF.xsl") which will work with most any EAD file (and which already include the "ead" namespace). In fact, if you've installed the AT on your desktop, those files will be located at Archivists Toolkit/reports/Resources/eadToPdf.
>
> Let us know if that works out for you,
>
>
> Mark Custer
> [log in to unmask]
> 252-328-5389
>
>
>
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Michele R Combs
> Sent: Wednesday, December 08, 2010 10:04 AM
> To: [log in to unmask]
> Subject: Re: XSLT for HTML display of schema-compliant EAD?
>
> Hi Kathryn --
>
> I haven't worked much with the schema, but I don't think the problem lies in the style sheet. The problem appears to be this line in the root element (<ead>) :
>
> xmlns="urn:isbn:1-931666-22-9"
>
> If you take that out, the document renders fine. Is that line absolutely necessary?
>
> Michele
>
> -----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.
> http://woodsonresearch.wordpress.com/2009/01/07/a-humbling-discovery/
>
> 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:
> http://www.rpi.edu/~dunnk2/ead/q/AC_27_DTD.xml
> http://www.rpi.edu/~dunnk2/ead/q/AC_27_XSDschema.xml
>
> The main stylesheet is here:
> http://www.rpi.edu/~dunnk2/ead/q/test_for_display.xsl
>
> It also uses a dsc stylesheet adapted from a stylesheet provided by
> Michele Combs at her awesome workshop in Albany:
> http://www.rpi.edu/~dunnk2/ead/q/su1_modified_kd.xsl
>
>
> Thanks very much in advance for any advice you can offer!
>
> Katie
>
> -------
> Katie Dunn
> Technology & Metadata Librarian
> Rensselaer Polytechnic Institute
> 518-276-8353
> [log in to unmask]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkz/zeYACgkQ6m+l2LO+BGyfdgCglBjE458ygMzmAMcBB/F7tsF9
zf0Anjo6KPuHCmAVKWOpW5xHX6gYAWll
=rh+g
-----END PGP SIGNATURE-----
|