We have an almost identical challenge, with the added qualifications that
a) all our pages are customized and generated on the fly, out of the
repository;
b) we need to generate HTML, so that pages can be viewed and navigated with
today's HTML browsers.
This means that at the time of serving up the documents our code needs to
compose HTML <A HREF="...">content</A> tags from the symbolic link
identifiers. I.e., for outputting just HTML there seems to be no reason to
generate an intermediary XML document, with entity definitions and entity
refs, which then gets translated to HTML. However, the XML doc makes sense
if we want to anticipate supporting both XML and HTML browsers (by
switching on the browser type, and if it's HTML, generating HTML).
I see no reason why your approach wouldn't work with XML browsers.
- Mark
___________________________________
Mark Szpakowski
WorldNav Learning Systems Inc.
Halifax, Nova Scotia, Canada
mark.szpakowski@learningengine.com
Voice 902/422-1577 Fax 902/422-4964
___________________________________