LISTSERV mailing list manager LISTSERV 16.0

Help for EAD Archives


EAD Archives

EAD Archives


EAD@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

EAD Home

EAD Home

EAD  March 1999

EAD March 1999

Subject:

Re: IE5.0 - XML

From:

"Fox, Michael" <[log in to unmask]>

Reply-To:

Encoded Archival Description List <[log in to unmask]>

Date:

Wed, 24 Mar 1999 12:10:04 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (208 lines)

It is good to see early examples of EAD finding aids being delivered on the
Web. Thanks to Paul and others who are sharing these.

However, I would like to suggest that perspective users try a different
approach than that listed below for getting your EAD files XML aware.

The following text is taken from the forthcoming EAD Application Guidelines
and describe the changes that need to be made to the ead.dtd file and the
proper DOCTYPE declaration for xml.

Note, for example, that eadchars.ent is no longer required or reference to
any characters as XML is Unicode based.

From the Application Guidelines:

4.3.2.1 Changes in the DTD Files

If the DTD is to be used with XML applications such as validating
processors, one change must first be made to the "ead.dtd" file. There is a
section towards the end of the file headed "SGML EADNOTAT AND EADCHARS
INCLUSION/EXCLUSION." At the end of this section, there is an entity
reference that reads "<!ENTITY % sgml 'INCLUDE' >". To "switch off" SGML
compatibility and "switch on" XML compatibility, change 'INCLUDE' to
'IGNORE'.

When you make this change, observe that the explanatory note in this section
of the DTD file points out that "for XML, the eadnotat.ent file should be
invoked in the declaration subset of [the] individual instance." This means
that the file "eadnotat.ent" must be declared explicitly as an entity in
each EAD instance that contains links to notational (non-textual) data such
as graphics files. For XML instances, the prolog of EAD-encoded finding
aids should therefore read:

                <!DOCTYPE ead PUBLIC "-//Society of American Archivists//DTD
ead.dtd (Encoded Archival Description (EAD) Version 1.0)//EN" "ead.dtd"
                [
                <!ENTITY % eadnotat PUBLIC "-//Society of American
Archivists//DTD eadnotat.ent (Encoded Archival Description (EAD) Notation
Declarations Version 1.0)//EN" "eadnotat.ent">
                %eadnotat;
                ]>

While it is not necessary to declare the notation file eadnotat.ent if the
finding aid does not contain a graphic file, it is probably simplest to add
it in all cases as a default. Note that the Uniform Resource Identifiers
(URI), in this case simple file names that point to the ead.dtd and
eadnotat.ent files, must point to the exact physical location of these two
files on your system. Their content may therefore vary from the above
examples according to local file storage practices.

4.3.2.2. Case Sensitivity

Markup in SGML is not case sensitive for element or attribute names. For
compatibility with the Unicode character set specifications, XML markup is
case sensitive for this data; EAD element and attribute names must therefore
be in lower case for XML compliance. Some SGML authoring or parsing
software automatically writes out such names in upper case; the resulting
files must be edited to change all attribute and element names to lower
case. A conversion macro written for Microsoft Word is available via the
EAD Help Pages.

4.3.2.3. Processing Instructions

Processing instructions (PIs) are an SGML device for inserting into a
document information that is intended for processing by a proprietary
software application rather than a parser. While PIs may be used for a
variety of purposes and may appear anywhere within an SGML instance, a PI
declaring that the file is in the XML format must come at the very beginning
of the file, preceding the DOCTYPE declaration. All XML instances must
begin with a PI that contains three elements: the XML version employed;
whether the document uses an external DTD such as EAD; and optionally, the
Unicode character encoding scheme utilized (such as UTF-8). A typical EAD
PI might read:

                <?xml version="1.0" standalone="no" encoding="UTF-8"?>


4.3.2.4. Empty Elements

Finally, SGML and XML differ in the markup syntax for elements declared to
be "empty" in the DTD; that is, elements that contain neither other elements
nor PCDATA. The relevant EAD elements are <lb>, <extptr>, <extptrloc>,
<ptr>, and <ptrloc>. Except for <lb>, which is a formatting device, these
are all linking elements that utilize attribute values to point to other
locations or files. In SGML, "empty" elements require only a start-tag
(e.g., <lb>). XML adds an additional form called the "empty-element tag"
which has the syntax <lb/>. While both formats are technically valid in
XML, the XML standard declares that the "empty-element tag" form must be
employed "for interoperability." While the meaning of this statement is
admittedly vague, it is easiest simply to use the empty-element-tag syntax
(<lb/>) as your default in XML documents.

If you have IE 5, you can retrieve another example of an EAD finding aid,
encoded in xml, that uses an xsl stylesheet to generate a display in your
browser in real time, at

http://www.mnhs.org/library/findaids/00020s.xml

I would appreciate advice from anyone who can tell me why the hyperlinks
from the <organization> section to the individual <c01>s don't work. The
other internal links are ok. But I can't get the stylesheet to generate an
attribute value containing the number of a child element relative to its
parent, i.e that this is the first item in a list, the second item in a
list, etc.



Michael

Michael Fox
Head of Processing
Minnesota Historical Society
345 Kellogg Blvd West
St. Paul MN 55102-1906
phone: 651-296-1014
fax: 651-296-9961
[log in to unmask]
**NOTE NEW AREA CODE EFFECTIVE JULY 12, 1998**

> ----------
> From: Paul Kiel[SMTP:[log in to unmask]]
> Sent: Wednesday, March 24, 1999 9:23 AM
> To: Multiple recipients of list EAD
> Subject: IE5.0 - XML sans plugin
>
> Mail*Link(r) SMTP IE5.0 - XML sans plugin
>
> Greetings,
>
> I am interested to see if people have been successful getting their EAD
> documents to display in the new Internet Explorer 5.0. With some
> machinations I have had success. While there was a bit of effort, it was
> simpler than the plugin problems. Being able to serve up directly to the
> browser was the fulfillment of the promise for so long.
>
> My testing included no stylesheet for this (CSS or XSL) so IE displays the
> tags basically like Explorer displays directories. You can click on the
> directory with a "+" and expand to see the tags within it or click on "-"
> to
> shrink the subtags. Finally, I must admit to some sloppiness. I used the
> EAD1.0 dtd with beta documents, so please overlook the testing
> compromises.
>
> Using IE5.0 look at:
>
> http://www.lib.ncsu.edu/libraries/archives/collections/test/
>
> (brown.xml and kamphoef.xml are full length documents and take a second to
> load, the others are collection level only and illustrate the effect a bit
> faster)
>
> Here is what I had to do to make it work:
>
> 1) have your server configured for the xml mime-type (text/xml xml)
>
> 2) make sure the DOCTYPE tag includes the filename reference "ead.dtd" (be
> careful of case) ex:
> <!DOCTYPE EAD PUBLIC "-//Society of American Archivists//DTD ead.dtd
> (Encoded
> Archival Description (EAD))//EN" "ead.dtd">
>
> 3) rename files with extension ".xml"
>
> 4) do the same with the EADID tag
>
> 5) include in the public identifiers the actual filename as follows:
>
> <!ENTITY % eadbase PUBLIC
> "-//Society of American Archivists//DTD eadbase.ent (Encoded Archival
> Description (EAD) Basic Declarations Version 1.0)//EN" "eadbase.ent" >
>
> <!ENTITY % eadchars PUBLIC
> "-//Society of American Archivists//DTD eadchars.ent (Encoded Archival
> Description (EAD) Special Characters Version 1.0)//EN" "eadchars.ent" >
>
> <!ENTITY % eadnotat PUBLIC
> "-//Society of American Archivists//DTD eadnotat.ent (Encoded Archival
> Description (EAD) Notation Declarations Version 1.0)//EN" "eadnotat.ent" >
>
> 6) you will need to do the same with the SPECIAL CHARACTER ISO ENTITY
> SETS.
> For testing, I simply commented these references out - which means I
> couldn't
> display the copyright symbol and changed it in the documents to say
> "copyright" instead. Adding direct references would correct this I am
> sure.
>
> Notes: For a review of IE5.0 look at www.xml.com. Also, XML did not make
> it
> into the help files of IE, so don't even try and look at documention.
>
> I would love to hear other experiences with this,
>
> Paul Kiel
> -------------------------------------------
> W. Paul Kiel
> Interim Head
> NCSU Libraries Special Collections
> http://www.lib.ncsu.edu/libraries/archives/
> Box 7111
> North Carolina State University
> Raleigh, NC 27695-7111
> voice: 919.515.8119
> fax: 919.515.3628
> Internet: [log in to unmask]
> ------------------------------
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996
February 1996
December 1995

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager
https://listserv.loc.gov/cgi-bin/wa?A2=ind9903&L=EAD&F=P&P=26459
listserv.loc.gov
crawl=CC-MAIN-2022-49
71101
application/http; msgtype=response
sha1:UGXNG7HX3SN3O5TY3DQLRKF3YYAFHVR6
<urn:uuid:e3488547-2fda-463e-8b0d-828a6d90f45b>
2022-12-02T09:37:02Z
140.147.239.86
text/html
sha1:LYYBW2NKEJNW6SR3YGME656I3TGHDOXK
<urn:uuid:be4e6809-037e-4114-bdab-da8fd09d9110>
https://listserv.loc.gov/cgi-bin/wa?A2=ind9903&L=EAD&F=P&P=26459
response
<urn:uuid:514bfc6b-5671-4d6d-8a30-9fe75e5557bd>
isPartOf: CC-MAIN-2022-49
publisher: Common Crawl
description: Wide crawl of the web for November/December 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-16
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/