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  May 1999

EAD May 1999

Subject:

Re: Necessary files

From:

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

Reply-To:

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

Date:

Fri, 14 May 1999 08:55:59 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (148 lines)

Panorama needs access to all these files. The Panorama documentation
describes the ways in which its entityrc and catalog files need to be
configured to access these DTD files (or at least it did in previous
versions of the accompanying manual).

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: Bill Landis[SMTP:[log in to unmask]]
> Sent: Thursday, May 13, 1999 10:39 PM
> To: Multiple recipients of list EAD
> Subject: Re: Necessary files
>
> In response to Charles Cofone's message earlier this week regarding the
> EAD DTD and its associated files, I'm appending below the chunk from the
> "EAD v1.0 Application Guidelines" (forthcoming from SAA this summer) that
> deals with the DTD. This won't address Charles' specific question about
> Panorama, but it may help in figuring out the role of the various files
> associated with the DTD.
>
> Bill [log in to unmask]
> Manuscripts Librarian | The UCI Libraries
> Department of Special Collections | University of California
> 949 824.3113 | P.O. Box 19557
> 949 824.2472 FAX | Irvine, CA 92623-9557
>
> <begin excerpt>
>
> 4.3. Technical Issues in Authoring
>
> This section provides discussions of the following technical issues as
> they relate to the authoring of EAD documents:
>
> The structure of the EAD DTD and its associated files
> EAD as both an SGML and an XML DTD
> Parsing EAD instances to verify conformance with the DTD
> Data interchange between MARC records and EAD finding aids
> Effects of encoding features on output
>
> 4.3.1. Structure of the EAD DTD
>
> The EAD Document Type Definition (DTD) is an essential component of the
> authoring process. As a document, the DTD is constructed according to a
> strict syntax specified by the SGML standard. For file management
> purposes, components of the DTD have been divided in a modular fashion
> into the ead.dtd file and four other associated files that function
> together as a unit. Two of these (see below) are not required if the
> finding aid is encoded using EAD in XML mode. All five files are simple
> text documents in ASCII format that can be viewed and edited in text or
> word processing software. The five files are:
>
> ead.dtd
> eadbase.ent
> eadnotat.ent
> eadchars.ent
> eadsgml.dcl
>
> ead.dtd: This is the core EAD Document Type Definition file. It is brief,
> containing a version history of the DTD plus entity references that invoke
> the other files in the EAD suite. It also contains three conditional
> sections that enable or disable the following features: XML
> compatibility, XLink functionality and the specialized features of EAD's
> array of tabular elements. The use of these features is described in
> Sections 4.3.2.1 (XML compatibility), 4.3.5.4 (tabular layout), and 7.2.4
> (XLink functionality).
>
> eadbase.ent: This is the largest file of the group and contains the SGML
> rules for EAD.
>
> eadnotat.ent: This file contains references to the various types of
> notational (non-text) files that might be used within an EAD document.
> These include common image file formats such as GIF, JPEG, TIFF, and MPEG
> (see Section 6.5.2.4.2 for more information on notational files).
>
> eadchars.ent: This file contains references to the various character sets
> that might be used in an EAD document. All character sets are referenced
> by their standard ISO identifiers. This file is not required if the
> document is created in XML, which uses the Unicode character set (or some
> subset thereof) by default (see Section 6.5.2.1 for more information on
> character sets).
>
> eadsgml.dcl: This is the SGML declaration file, which specifies various
> features of the DTD that a processing application may need to know. While
> many DTDs utilize a standard SGML reference declaration, EAD employs its
> own version. Some software applications incorporate the text of the
> declaration at the beginning of each SGML instance. All XML documents,
> however, employ a default declaration and so do not require the use of
> this file.
>
> 4.3.2. SGML versus XML
>
> EAD is written so that it can be made to conform to the specifications of
> either SGML or XML. The form of the DTD and its associated files that is
> available from the EAD home page at the Library of Congress is SGML
> compliant. While XML may, in general, be thought of as a subset of SGML,
> there are five differences in XML that must be accommodated to make an EAD
> document XML-compliant. You must be particularly aware of these
> differences when converting existing SGML versions of documents into XML.
>
> 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 explicitly declared as an
> entity in the prolog of each EAD instance that contains links to
> notational (non-textual) data such as graphics files (see Section 6.2.3
> for a general discussion of the document prolog). 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 link to notational data such as
> graphics files, it is probably simplest to add it in all cases as a
> default. Note that the Uniform Resource Identifiers (URIs), in this case
> simple file names that refer to the "ead.dtd" and the "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 in
> accordance with your local storage practices for the DTD and its
> associated files.
>

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

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