Scott, While I am not completely familiar with all of Panorama's specific needs, I am assuming it can deal with well constructed SGML. If this is the case, then your Entity Declaration is where you are going wrong. <!ENTITY accessuse PUBLIC "-//(..text snipped...)//TEXT (URL of HTML document)//EN" NDATA HTML> Where you have the string "URL of HTML document", you should have a name unique in the server environment in which you are working for the document. For example: <!ENTITY accessuse PUBLIC "-//(..text snipped...)//TEXT (The Blah-blah-blah document)//EN" NDATA HTML> And then following the ..//EN" and before the "NDATA HTML" You should have the URL for the document to which you are providing a link: <!ENTITY accessuse PUBLIC "-//(..text snipped...)//TEXT (The Blah-blah-blah document)//EN" "URL://myserver.edu/blah3.htm" NDATA HTML> It is this latter piece of information that will supply the information Panorama needs to find the specified file. (There are a couple of other ways of doing it, but I would try to make this work before using more complex, more robust approaches. I hope this helps. Daniel At 04:36 PM 5/19/97 -0400, you wrote: >I'm still working on getting links to HTML documents from EAD. I've >followed Daniel Pitti's advice and looked at his EAD Retrospective >Conversion Guidelines (http://sunsite.berkeley.edu/amher/upguide.html; >thanks Stephen). I'm not sure what I'm doing wrong, but the EAD document >doesn't create a link from the text to the HTML document. This is what >I'm doing: >[(...text snipped...) ><!NOTATION html PUBLIC "-//IETF//DTD HTML/EN"> ><!ENTITY accessuse PUBLIC "-//(..text snipped...)//TEXT >(URL of HTML document)//EN" NDATA HTML> >] >(...text snipped...) >... see <extref displaytype="present" entityref="accessuse"> Policy on >Access and Use</extref>. > >When Panorama loads the SGML document, before the words "Policy on Access >and Use" there appears a box with the NOTATION and ENTITY declarations in >it (this box is similar to the box that I saw when I discovered that >PanoramaFree 1.0 doesn't read JPEG images). The text "Policy on Access and >Use" is the text that I want to link from to the URL of the HTML document. > >The Coversion Guidelines seem rather vague about external pointers. The >section on the <dao> element was clear to me, but the rest of the >information feels more like a lesson on how to tag using the given >elements. (The information on the <ref> element is clearer, but appears >to belong in the internal pointers section.) > >The Panorama manual talks about linking to URLs, using <?ATTLINK tagname >attname URI> elements (this causes Panorama to treat the value of >attribute "attname" of the element "tagname" as a URL), but this doesn't >work much better. I attempted to go this way before, but it lead to a >deadend where it brought up part of the text from the HTML document within >the SGML browser. > >Has anyone linked to HTML documents from within the EAD? If so, please >let me know where I can look at an example. LC's "Visual Materials of the >NAACP" implies a future link to the Prints and Photographs home page, but >the link is still under construction. > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~ >Scott A. Leonard ><> >e-mail: [log in to unmask] >Scott's Page on the Web: http://www.wam.umd.edu/~sleonard/ > > "I cannot speak for the way God deals with others; I know only how He deals >with me personally." > C. S. Lewis, _God in the Dock_ (p. 262) > > Daniel V. Pitti Project Director Institute for Advanced Technology in the Humanities Alderman Library University of Virginia Charlottesville, Virginia 22903 phone: 804 924-6594 fax: 804 982-2363 email: [log in to unmask]