This is really a neat implementation; thanks for sharing this.  

I'm also curious about very useful context window at the bottom of the
screen.  Presumably it's a javascript function; from what I can see each
c0# in the finding aid html has the correct string of ancestor id's
which it then passes to the function; does it then use the DOM to find
the things with those IDs and generate the nice indented tree?  Has this
part been checked with all browsers as well?

Thanks!

Michele C.


-=--=--=--=--=--=--=--=--=--=--=--=--=--=-
Michele R. Combs
Manuscripts Processor
Special Collections Research Center
Syracuse University Library
222 Waverly Avenue
Syracuse, NY 13244
(315) 443-2697
-=--=--=--=--=--=--=--=--=--=--=--=--=--=-

>>> [log in to unmask] 11/1/2006 12:08 PM >>>
We actually took a similar approach by using CSS to mimic the 
navigational features of frames since we wanted to reap the benefits of

frames but didn't still wanted to be able to transform the document to

HTML on-the-fly (and couldn't use Saxon with our current XML delivery 
software).  I wrote a paper about this several months ago but got 
stumped on the convoluted javascript required to detect the various 
browsers accurately.  The script currently supports all of the major 
browsers, but not all of them (like Mac's Safari which I haven't been 
able to build in support for at this time). But I think it's worth 
publishing as it stands now.  If anyone is interested, the document is
here:

http://staff.washington.edu/carlsonm/beyondframesets.pdf 

http://staff.washington.edu/carlsonm/