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:

Proportional Font

LISTSERV Archives

LISTSERV Archives

EAD Home

EAD Home

EAD  February 2004

EAD February 2004

Subject:

Re: entityref verses href

From:

Alvin Pollock <[log in to unmask]>

Reply-To:

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

Date:

Thu, 26 Feb 2004 10:09:31 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (87 lines)

I'll add another advantage to Richard's: with entities you also
have a NOTATION to tell you the type of resource being linked
to. NDATA JPEG, NDATA GIF tells your stylesheets that the
resource is an image and may be rendered in HTML with <img>.
NDATA METS might tell your stylesheet to render as <a>. NDATA
WAV might prompt your stylesheet to display information about
appropriate sound players. And so on. Encoding institutions
which are beginning to move beyond embedding just images may
find themselves wishing for some kind of type attribute, e.g.,
type="image", type="sound", type="tei document", etc. In those
cases they should really begin investigating entities instead.

Entities provide a very useful indirection mechanism. Your
actual hypertext links can be stored in a single XML Catalog
file. When URLs change there is no need to update hundreds
of EAD files. Simply change the catalog file entries or a
single rewriteSystem or rewriteURI entry. See:
http://www.oasis-open.org/committees/entity/spec-2001-08-06.html

We have found entities to be critical especially for creating
links to related EAD finding aids in <archref>. We completely avoid
hardcoding URLs to a particular presentation system du jour and
refer instead to the formal public identifier of the target
finding aid as encoded in its <eadid>. So as out presentation
or indexing system changes there's no need to worry about anything
encoded in our hundreds of finding aids. We simply alter the
single catalog file and everything automatically works.

People seem to prefer @href because they are familiar with it
from HTML. But they seem to forget all of the headaches associated
with broken links and changing URIs that continue to plague
the web.

As Richard points out, the Application Guidelines were written
in 1998. Many people do not realize that since that time XSLT
supports unparsed-entity-uri and other related functions for
obtaining information about entities.

Alvin Pollock
Digital Publishing Group
UC Berkeley Library

 >Hi Bill
 >
 >I think it's horses for courses, and very much depends on the nature of
 >your system.
 >
 >The advantage of the entityref approach is that a finding aid encoder
 >can assert a link betwen *logical* entities without knowing about how
 >the system is being implemented. In theory, URLs can be associated with
 >the entities at runtime by whatever software (web server, XML editor...)
 >is handling the delivery.
 >
 >As the 1998 Application Guidelines say, it is a "technically elegant"
 >approach, that leaves the assignment of physical locations to separate
 >catalogue files or other resource brokers. However, as they also say,
 >
 >> There are technical disadvantages to this approach. Web browsers that
 >>  support XML and the use of XSL or CSS stylesheets are unable to
 >> access and resolve such entity names into explicit resource addresses
 >>  such as URLs. It would require specialized programming to create
 >> workarounds for this problem. In addition, the overhead of supplying
 >> a well-formed FPI (as specified by the ISO 9070 standard) for each
 >> digital resource is not insignificant.
 >
 >On our NDAD system (http://ndad.ulcc.ac.uk/), we have stuck with href
 >for the time being, since our internal references double as URLs (within
 >our domain) - and everything is transformed into HTML anyway. If the
 >tide were to change, it doesn't seem like it would be terribly difficult
 >to harvest all the hrefs and substitute entityrefs.
 >
 >HTH
 >
 >Richard
 >
 >
 >--
 >/
 >\ Richard M Davis
 >/ Digital Archives
 >\ University of London Computer Centre
 >/ Tel: +44 (0) 20 7692 1350
 >\ mailto: [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

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