Tom,
I
reviewed the proposal in light of my clients’ requirements
and really liked the way you propose to handle the
multiple-product/concurrent release challenge. Overall, I
think that the strategy of using the topic <prolog>
and the structure of the domain are sound.
However,
the one item I didn’t see addressed is the requirement to
visually indicate the exact location of the change in the
content of the topic. It seems to me that the
<change-item> needs to reference the modified element
and it comes down to the selection of the appropriate DITA
referencing mechanism. Has the subcommittee considered the
options for providing this support?
The
challenge for many teams is the they need to visually
indicate changes between releases of a deliverable, but the
track changes features in most tools don’t work for the
following reasons:
· author
may want to identify a subset of content changes based on
specific criteria, such as importance or relevance
· changes
may not correspond cleanly to the workflow
versions/revisions of the topic file and the releases of the
deliverable
Thanks
and have a great weekend,
Amber
Amber Swope
dita specialist
<dita strategies>
503.922.3038
amber@ditastrategies.com
From:
dita@lists.oasis-open.org [mailto:dita@lists.oasis-open.org]
On Behalf Of Tom Cihak
Sent: Friday, August 23, 2013 1:34 PM
To: dita@lists.oasis-open.org
Subject: [dita] Groups - Proposal 13102, Stage 2
Release Management (PDF) uploaded
Submitter's message
PDF version of release management stage 2 proposal
-- Tom Cihak