More deep explanation :
Yes, you can use nesting tasks but how to manage the difference
between real nested tasks (a task that needs to be composed of a
series of different tasks) and real stepgroups ?
This leads to the question of what is the real need ?
The best sample is what I often find in the layout of many
documentation : a two columns table with, for each row :
- first cell : an image plus warnings
- second cell : a serie of steps all relates to the image.
I've no reason to define this as non respecting minimalist
technical writing.
Pierre
Le 05/12/2019 à 17:21, Michael
Priestley a écrit :
Have you
considered
nesting tasks? Once each group of steps has its own title and
introductory
context, it may make sense to think of them as subtasks, rather
than substeps.
Michael Priestley, Senior Technical Staff Member (STSM)
Taxonomy Specialist, Marketing Analytics
mpriestl@ca.ibm.com
From:
Pierre
Attar <attar@tireme.fr>
To:
dita-comment@lists.oasis-open.org
Date:
2019/12/05
08:12 AM
Subject:
[EXTERNAL]
[dita-comment] <stepsection> useless
Hi,
I've a request on the way steps are made for now : the
<stepsection>
element is useless in most of the cases while it is not a
container per
se.
In fact, many different cases, the way TW are working is
something like
:
<stepgroup>
<title>
<image>, <note>, <etc.
<step>
<step>
...
</stepgroup>
<stepgroup>
<title>
<image>, <note>, <etc.
<step>
<step>
...
</stepgroup>
In the current DITA version, it is impossible to reproduce
this
meachnism because the <stepsection> is only a
specialization of <li>.
So the only way to do that is to use step and substeps.
But as semantics is implied, a step/cmd is not the same as a
stepgroup/title.
Any thoughts on the way to solve that I understand the
difficulty
as
<steps> derives from <ol> but there is may be an
other derivation
way to
solve that.
Regards Pierre
--
Pierre Attar (attar àt tireme point/dot fr)
Expert in Structured Document engineering
Expert en informatique documentaire
Tirème SARL (http://www.tireme.fr)
# : +33 1 43 41 12 13
--
This publicly archived list offers a means to provide input to
the
OASIS Darwin Information Typing Architecture (DITA) TC.
In order to verify user consent to the Feedback License terms
and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: dita-comment-subscribe@lists.oasis-open.org
Unsubscribe: dita-comment-unsubscribe@lists.oasis-open.org
List help: dita-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/dita-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita
Join OASIS: http://www.oasis-open.org/join/
--
Pierre Attar (attar àt tireme point/dot fr)
Expert in Structured Document engineering
Expert en informatique documentaire
Tirème SARL (http://www.tireme.fr)
# : +33 1 43 41 12 13