Hi Robert,
Yes, I mean remove from the spec. As far as I know, the items to be removed from the spec are <anchor>, <anchorref>, and the anchorref attribute. I’m not aware of anything else that’s related.
Cheers,
Gershon
Gershon Joseph | Senior Information Architect | Precision Content
Direct: +972 (54) 658-3887| Email: gershon@precisioncontent.com |
www.precisioncontent.com
Unlock the Knowledge in Your Enterprise™
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Please
notify us by return email if you have received this email in error. ©2021,
Precision Content Authoring Solutions Inc, Toronto,
Ontario, Canada
From:
Robert Anderson <robert.dan.anderson@oracle.com>
Date: Wednesday, 24 November 2021 at 19:20
To: Gershon Joseph <gershon@precisioncontent.com>, dita <dita@lists.oasis-open.org>
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
Direct: +972 (54) 658-3887| Email: gershon@precisioncontent.com |
www.precisioncontent.com
Unlock the Knowledge in Your Enterprise™
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Please
notify us by return email if you have received this email in error. ©2021,
Precision Content Authoring Solutions Inc, Toronto,
Ontario, Canada