Agreed to remove them – their use is likely not interoperable (kind of attributes use in many ways).
Although there may be people using them but the DITA standard is not currently in the business of processing.
I have always had the idea however, that the OT should define “preprocessing” validity using DTDs. If this could be handled as a valid modification to the DITA DTDs that would be great.
This would mean that a DITA repository could store and validate OT preprocessed DITA using DITA specializations such as the debug attributes.
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Eliot Kimber
Sent: June-14-16 11:35 AM
To: DITA TC
Subject: Re: [dita] DITA 2.0: suggest removing @xtrf, @xtrc
I agree with Robert and Chris: remove them.
I agree. Unlike copy-to, I have used these in my implementations, both for debugging and for traceability from output HTML elements to source XML elements. But they’re not to be used by authors, and so probably shouldn’t be there (but as Robert says, they can still be added by processors for whatever purposes).
For DITA 2.0, I'd like to suggest removing @xtrf and @xtrc, also known as the "debug attribute group":
Sort of like with last week's discussion of copy-to, these attributes were really defined based on a specific processing model (the step-by-step toolkit style processing), with the idea that debug information can be carried through that sort of process while keeping the DITA itself valid according to the original schema.
I don't think that's appropriate for the core DITA specification itself. Applications like DITA-OT can continue to operate in exactly that way, using those exact attributes, without the two of them being part of the specification. I think that would be true of any attribute defined as "intended to store xxxx during intermediate processing", although I'm not aware of any others defined in that way.