OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Questions about updated stage 2 proposal 33: Remove copy-to

Eliot, I don't see any changes to the "Example" section. Where is the updated content located? Maybe you attached a back-level PDF, since the shortdesc still reads "Deprecate or remove @copy-to" ...


Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
+1 919 622-1501; kriseberlein (skype)

On 10/14/2019 12:52 PM, Eliot Kimber wrote:
I have updated the proposal to include a short discussion of the general requirements for processors to manage the generation of anchors in deliverables, stressing that it is inherently processor dependent.

DITA source is updated in SVN.



Eliot Kimber

ïOn 10/5/19, 10:04 AM, "Eliot Kimber" <ekimber@contrext.com> wrote:

    Proposal 33 is ready for TC consideration for promotion to stage 3:
    PDF is attached.
    DITA source (SVN): https://tools.oasis-open.org/version-control/browse/wsvn/dita/trunk/DITA-2.0/stage-2/Issue33-DeprecateOrRemoveCopyTo.dita
    Tl;dr: Remove @copy-to, don't replace it with anything. Remove language from @chunk attribute related to implications of use of @copy-to on topic head topicrefs.
    The consensus of myself, Robert, and Chris was that everything having to do with @copy-to and the larger issues around the construction of "anchors" in deliverables is entirely processor specific and therefore not something we can or should be trying to standardize or even define conventions for in the DITA specification.
    Eliot Kimber

To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]