This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: A straw proposal for help topics in DocBook
- To: DocBook List <docbook at lists dot oasis-open dot org>
- Subject: Re: DOCBOOK: A straw proposal for help topics in DocBook
- From: Michael Smith <smith at xml-doc dot org>
- Date: Fri, 19 Oct 2001 11:40:10 +0900
- List-Id: <docbook.lists.oasis-open.org>
- References: <Pine.WNT.4.33.0110181954100.1080-100000@gershon-lt>
Gershon L Joseph <gershon@mainsoft.com> writes:
> On Thu, 18 Oct 2001, Michael Smith wrote:
>
> [...]
> > Also, does it make sense to model a help topic as a recursive element?
> > What I mean is, in most (or maybe all) current online help systems,
> > each help "topic" is actually a single HTML page/webpage (though that
> > HTML page might of course be multiple physical pages if you were to
> > print it out).
> >
> > So to model it accurately, it seems like the help-topic element
> > actually shouldn't be recursive. I think it'd be like making Chapter
> > or Article recursive -- just as real chapters can't contain other
> > chapters, real help pages can't contain other help pages.
>
> I don't think this is so for large help projects. Many winhelp and
> HtmlHelp projects come to mind, e.g. MSDN or WordPerfect 9's online
> help. There seems to be no limit to how far down the topic tree you
> can go. [...]
Of course you're right. The containment is expressed in the TOC tree,
so it doesn't really matter that the pages are separate files.
So I can see that yes it's correct to model it as a recursive element.
I actually had it that way --
<!ELEMENT topic "(title;, topicinfo?, (text, topic?)+)">
-- in the simple standalone help module I put together:
http://www.logopoeia.com/xml/helpset/helpset.mod
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>