From: "Houghton,Andrew" <houghtoa@oclc.org>
Date: July 9, 2004 10:57:54 AM EST
To: Eric Lease Morgan <emorgan@nd.edu>
Subject: RE: using xml::libxml to find & replace in xml documents

Dear Email Recipient:

This message was changed by the Notre Dame central email system 
administered by the OIT in the following way:

WARNING!  POSSIBLE VIRUS FILE ATTACHMENT RENAMED FOR YOUR PROTECTION!

The attachment "results.zip" was renamed to "results.zip.unknown" 
because the file is of a type that could contain malicious code or 
because the email system was unable to scan it for viruses because it 
was password protected.

IT IS LIKELY THAT THIS ATTACHMENT IS A VIRUS!

If you were not specifically expecting this attachment, DO NOT OPEN IT! 
Delete it immediately!  Opening a virus infected attachment will infect 
your computer and may result in network access being terminated, as 
well as costly computer repair.

If you are CERTAIN this attachment is safe, you will need to rename the 
file by removing the .unknown from the file name in order to open it.

If you have questions about this, please contact the Notre Dame OIT 
Help Desk at 574-631-8111.


-------- Original Message --------



OK, attached is a Windows command script, XSLT, and your original and
converted files.  I even pretty formatted the converted files for easier
"human" reading.  If you have any questions that the comments don't 
answer,
feel free to ask.


Enjoy, Andy.

Andrew Houghton, OCLC Online Computer Library Center, Inc.
http://www.oclc.org/about/
http://www.oclc.org/research/staff/houghton.htm


> -----Original Message-----
> From: Eric Lease Morgan [mailto:emorgan@nd.edu]
> Sent: 09 July, 2004 09:32
> To: Houghton,Andrew
> Subject: Re: using xml::libxml to find & replace in xml documents
>
>
> On Jul 9, 2004, at 8:16 AM, Houghton,Andrew wrote:
>
>>> On the other hand do you have an XSLT stylesheet file that
> does this
>>> sort of thing?
>>
>> The XSLT would depend upon your data, but it doesn't sound
> like it's
>> beyond the capability of XSLT.  If you send me a couple of sample
>> records and exactly what wrong and what you want the result
> to be, I
>> could probably whip something up.
>
> Okay. I'll take you up on this. Think of it as an academic exercise.
> :-)
>
> Attached should be three well-formed EAD files (dlc.xml,
> zeh.xml, and zcx.xml). Each file needs to be modified similarly:
>
>    1. Change the href in the xml-stylesheet processing
> instruction to "ead2html.xsl".
>    2. Change eadheader's langencoding attribute to "ISO639-2".
>    3. Remove the langmaterial and legalstatus attributes from
> the archdesc element.
>    3. Remove the admininfo element and all of its children.
>
> 'Sound fun?
>
> --
> Eric Morgan
> (574) 631-8604
>
>

  