Hi Amber,
We did consider this and decided that the mechanism was far too complex for this proposal. I think Eliot mentioned something about using <data-about> for this purpose in the text. Tom will be able to give you more information.
JoAnn
JoAnn T. Hackos, PhD
President
Comtech Services Inc.
710 Kipling Street, Suite 400
Denver, CO 80215
303-232-7586
CIDM will be hosting the Best Practices Conference in Savannah, Georgia September 16-18. More information at: http://www.infomanagementcenter.com/bestpractices/2013/index.htm
From: Amber Swope <>
Organization: DITA Strategies, Inc.
Reply-To: "" <>
Date: Friday, August 30, 2013 3:06 PM
To: 'Tom Cihak' <>, DITA TC <>
Cc: Seraphim Larsen <>
Subject: RE: [dita] Groups - Proposal 13102, Stage 2 Release Management (PDF) uploaded
Of course, with more thought, I realize that one of the possible changes could be deletion/removal of an element and in this case referencing the
changed element would not work. But I’m sure you’ve already considered this…
Have a great day,
A
From: Amber Swope [mailto:]
Sent: Friday, August 30, 2013 1:53 PM
To: 'Tom Cihak'; ''
Cc: Seraphim Larsen ()
Subject: RE: [dita] Groups - Proposal 13102, Stage 2 Release Management (PDF) uploaded
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
From: [mailto:]
On Behalf Of Tom Cihak
Sent: Friday, August 23, 2013 1:34 PM
To:
Subject: [dita] Groups - Proposal 13102, Stage 2 Release Management (PDF) uploaded
Submitter's message
PDF version of release management stage 2 proposal
-- Tom Cihak
Document Name:
Proposal 13102, Stage 2 Release Management (PDF)
Description
Proposal 13102, Stage 2 Release Management PDF
Download Latest Revision
Public Download Link
Submitter: Tom Cihak
Group: OASIS Darwin Information Typing Architecture (DITA) TC
Folder: Drafts
Date submitted: 2013-08-23 13:33:50
