LISTSERV mailing list manager LISTSERV 16.0

Help for EAD Archives


EAD Archives

EAD Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

EAD Home

EAD Home

EAD  September 2003

EAD September 2003

Subject:

Re: alternate container markup in EAD 2002

From:

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

Reply-To:

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

Date:

Wed, 3 Sep 2003 09:44:30 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (115 lines)

Amy,
   You are correct on the content model.  My recollection, perhaps faulty,
is that NMTOKEN was chosen for technical reasons to support locally defined
entities that could, in this case for example, prescribe a locally defined
set of possible values for a given attribute even when the EAD DTD is more
permissive.

   For example, in Sweden the national archives could create a list of
possible valid values for the type attribute and the French could do the
same.   Both would limit national practice while still being valid EAD since
they would be, in effect, subsets of the range of possible values for TYPE.
The way to do this is described in the file eadlocal.ent.   My sense is that
this a fairly complex technical matter and my advice is that if one does not
know enough SGML/XML to understand what's happening in this file that it's
best to stay away from it.

   The following description from the file eadlocal.ent may clarify the
difference between CDATA and NMTOKEN.

 "Attribute declarations (as literal entity values in the following
          parameter entities) have three components: name, type, and
default.
          In the following example, "rules" is the name of the attribute,
          "NMTOKEN" is the attribute type, and "#IMPLIED" is the attribute
          default.

            'rules
              NMTOKEN
              #IMPLIED'

          The following two attribute types are used:

            NMTOKEN: an XML key word meaning that the value of the attribute
              must be a NAME TOKEN.

            CDATA: an XML key word meaning that value of the attribute may
              be virtually any Unicode character, including a whitespace.

          Both NMTOKEN and CDATA may be replaced by one or more values (an
          enumerated list) that conform to the XML rules specifying the
          composition of a NMTOKEN. A NMTOKEN may include any combination of
          the following: Letter, digit, '.', '-', '_', or ':'.

          NOTE: A NMTOKEN MAY NOT contain a space. Thus while CDATA allows
          virtually any combination of characters (including whitespaces),
          constraining the values in the DTD will necessarily requiring
          conforming to the XML rules for NMTOKEN."

The bottom line, however, is that you can include any value in TYPE that
contains letters, digits, periods, hyphens, underscores, or colons.

Michael



-----Original Message-----
From: Amy McCrory [mailto:[log in to unmask]]
Sent: Wednesday, September 03, 2003 8:55 AM
To: [log in to unmask]
Subject: Re: alternate container markup in EAD 2002


Thanks to both Michael and Kris for the replies.  My next question: where
can I look at the content model?  The 2002 Tag Library still says "NMTOKEN"
for the type attribute in <container>.  My ability to interpret the
information in the DTD itself is limited, to put it mildly, though
improving.

Amy


At 08:02 AM 9/3/2003 -0500, you wrote:
>Amy,
>    If you look at the new content model in EAD 2002 for the type attribute
>in <container>, you will see that the restricted list of possible values,
>e.g., box, folder, reel, othertype, etc. is no longer there.   The type
>attribute can now contain any form of character data (CDATA).  As a result
>there is no longer a need for the othertype attribute as any value may be
>found directly in type.  This change was made because the former
semi-closed
>list was felt to be too restrictive and U.S. or at least English-centric.
>
>Michael
>
>-----Original Message-----
>From: Amy McCrory [mailto:[log in to unmask]]
>Sent: Wednesday, September 03, 2003 7:38 AM
>To: [log in to unmask]
>Subject: alternate container markup in EAD 2002
>
>
>Up till now, I've been using the @othertype attribute in the <container>
>element in order to accommodate finding aids that assign "box-folder-item"
>markup to individual items in collections.  Looking through the 2002 DTD, I
>see that this attribute has been discontinued.  What avenues are available
>for doing this sort of markup?  In the 2002 Tab Library there is an example
>of a finding aid with some item-level description; however, it assumes one
>item per folder, so only box-folder numbers are used.  Some of our finding
>aids describe multiple items in a single container, so each item is
>numbered separately.  For instance: Folder 1--Item 1, Folder 1--Item 2,
etc.
>
>Has anyone found a way to handle this, in the absence of the othertype
>attribute?
>
>Amy McCrory
>Archivist, Cartoon Research Library
>023L Wexner Center
>(614) 292-0538
>EAD Specialist, Special Collections Cataloging
>036 Main Library
>(614) 292-8114
>The Ohio State University Libraries
>Columbus, OH 43210

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

March 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
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