OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook] How to model complex procedures, Stepalternatives

Hi Thomas,

On Friday 21 October 2005 15:13, Thomas, Ludger wrote:
> Dear all,
> I wonder how to model complex procedures with alternatvies e.g. "Create
> a new Document in MS WORD"? From my point of view, in such a case there
> ought to be several alternative procedures or steps at the highest
> level (Icon, Menu, Explorer, ...).

I am not sure, if I understand you correct. Could you explain it a bit 
more, please?

> <procedure>
> 	<stepalternatives>
> 		<step><title>Icon</title>
> 			<procedure>
> 			<step><para>...
> 		</step>
> 		<step><title>File Menu</title>
> 			<procedure>
> 				<step><para>Click on File Menu ...
> 				<step>...
> 		...
> 	</stepalternatives>
> 	<step><para> ...
> 	<stepalternatives>
> 		...
> </procedure>

What about this solution:

   <title>Create a new Document in MS WORD</title>

> The example doesnīt work because <stepalternatives> isnīt allowed to be
> a direct child of <procedure>. Any hints how to model these kind of
> procedures?

Probably you should rethink your procedure on a textual basis. Could you 
simplify your text? This would lead to a simpler procedure which is 
better anyway.

> Are there any examples of complex(!) procedures available 
> on the web?

I don't know of any, but probably they are anywhere. On the other hand: In 
my experience as a technical writer, complex procedures aren't really 
useful. Do you think a reader will read, for example, a 15 step procedure 
with some step alternatives intermixed? :)

> Furthermore I wonder how to model long procedures which are 
> interrupted by sections. Any hints how to model interrupted and
> continued procedures?

In my opinion, your problem is more text related than a technical problem. 
Maybe I am wrong and misunderstand your problem. :)


Thomas Schraitle

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]