[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Deprecate <anchor> and related attributes
Hi Gershon,
I just want to clarify - when you say deprecate, you mean remove entirely from 2.0, is that correct? Otherwise "deprecate" for the TC has always meant "keep it in but announce that it will be removed later".
Also, before discussing we need to be explicit about what related markup would be included - otherwise we cannot even ask whether others beyond IBM use the markup proposed for removal. I'm pretty sure that both the @anchorref attribute on maps and the <anchorref>
element in the map group domain would be included as related markup. Is that correct, and/or did you have anything else in mind as related markup?
Thanks,
Robert
From: dita@lists.oasis-open.org <dita@lists.oasis-open.org> on behalf of Gershon Joseph <gershon@precisioncontent.com>
Sent: Wednesday, November 24, 2021 10:01 AM To: dita <dita@lists.oasis-open.org> Subject: [External] : [dita] Deprecate <anchor> and related attributes Hi all,
Following up on our discussion at yesterday’s TC meeting, I would like to propose that we deprecate <anchor> and related markup from the DITA 2.0 spec. This functionality does not appear to be used by anyone except IBM. I propose we deprecate it now while we still can deprecate things in DITA 2.0. IBM can continue to use this functionality by specializing this stuff back into their shells.
This proposal will simplify the DITA content model and spec by removing esoteric stuff that’s not used, or even needed, by the vast majority of DITA implementations.
Any objections? Other thought? Please raise them on the email list or be prepared to discuss them at a future TC meeting when this topic is on the agenda.
Cheers, Gershon
Gershon Joseph | Senior Information Architect | Precision Content
Unlock the Knowledge in Your Enterprise™
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]