Hi Jenn:  According to the specification, the ROLE attribute is supposed
to contain a URI.  I would recommend against specifying a particular
player but would rather suggest that you specify a more generic
directive such as the MIME type and allow the client machine to render
the link with whatever player is set as the default for that MIME type.
  You can put it in ALTRENDER which wouldn't violate any standards.
You'll also want to set the SHOW attribute to "EMBED" and then set the
"ACTUATE" attribute to "ONLOAD".


Here is a list of MIME types:

I hope this helps.

Mark Carlson
Special Collections
University of Washington Libraries

On 7/29/2010 11:21 AM, Riley, Jenn wrote:
> Dear EAD folks,
> I'm looking for some clearer guidance than what I've been able to find
> online regarding the usage of xlink:role in EAD. In our finding aids, we use
> <dao>  to link to digitized versions of components in our collections. We're
> now facing a situation where we can potentially be embedding players/viewers
> inside our finding aid display instead of linking out to external systems,
> which has got us pretty excited. But what this means for us is our<dao>  now
> needs to be able to indicate what "player" should be used for a given link.
> Whether it's a paged digital object that needs a page turner to view, a
> sound recording that needs an audio player, etc.
> We're using the EAD2002 W3C XML Schema, and I'm thinking one of the xlink
> attributes on<dao>  would probably be best for encoding information about
> what system should render a digitized archival object. Based on a review of
> the brief information on linking elements in the EAD Tag Library, the old
> Application Guidelines, and the W3C XLink specifications (which I'd never
> really looked at before and was sorry after I tried to), I'm thinking
> xlink:role is the most appropriate of the xlink attributes included in EAD.
> Do other folks agree this is the right direction to go? Or should I be
> looking at other options?
> If xlink:role is the appropriate place, I'm still uncertain as to exactly
> what the right usage should be. I see implementations and documentation that
> treat xlink:role as requiring a QName (basically a string but can't start
> with a number), in which case we could just use standardized terminology for
> our different display options. But I also see implementations and
> documentation which suggests these values should be full URIs. Is there a
> clear best practice between these two options?
> Would the semantics of xlink:role suggest the value be more appropriate as a
> property of the object ('pageturned', 'audio', etc.) or more appropriate as
> the name of the delivery system in which it should be rendered?
> I'm not finding the W3C XLink documentation to be much help to me in
> answering these questions. Does anyone know of other XLink resources that I
> might find more useful as I learn about this?
> Thanks for any thoughts you can provide,
> Jenn
> ========================
> Jenn Riley
> Metadata Librarian
> Digital Library Program
> Indiana University - Bloomington
> Wells Library W501
> (812) 856-5759
> Inquiring Librarian blog: