Lists Home |
Date Index |
- From: "W. Eliot Kimber" <email@example.com>
- To: <firstname.lastname@example.org>
- Date: Fri, 04 Dec 1998 10:19:24 -0600
At 03:44 PM 12/4/98 -0000, Michael Kay wrote:
>> I'm helping a company ... make their policies and procedures manual
>> available as an online reference. I am thinking that it makes
>> sense to mark
>> it up as XML: it is 1000 pages and contains lots of chapters and
>> subheadings. Anyway, the question is, have people gone this route yet, of
>> marking up some text in XML and then streaming it to the client
>> (browser) as HTML?
>Author it in XML definitely. What I would do with it then, given that this
>is a static manual, is to generate HTML at publication time and store the
>generated HTML on the server in the normal way. That's heresy to many on
>this list, but to my mind it gives the best performance and the least system
>complexity. Of course if you're planning a fancy interactive experience for
>your readers the answer might be different.
It's a very effective technique. There are also commercial tools like
DynaWeb, Dual Prism, and SIM that will do it for you and provide
high-quality search and retrieval. See the "tools" section of Robin
Cover's SGML/XML Web site for pointers (<http://www.oasis-open.org/cover/>).
One downside with pregenerating the HTML is that you don't get the enhanced
search and retrieval that XML enables. A document like a policy and
procedures manual that is presumably supporting people in critical work is
an ideal candidate for highest-possible-quality search and retrieval.
W. Eliot Kimber, Senior Consulting SGML Engineer
ISOGEN International Corp.
2200 N. Lamar St., Suite 230, Dallas, TX 75202. 214.953.0004
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)