[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] Question about include element and existing specializations
I assumed it was oversight for coderef, because it's more or less required there for some cases.
For svgref / mathmlref I think I'd prefer to add it and stay in sync with the base. It's not going to hurt anything and there's no requirement to use it, but it could be useful in cases where you're doing something odd, just as with any reference to an XML file from the base <include> element.
For <fallback> -- I think it probably makes sense to add it, unless someone has an objection.
Robert D. Anderson DITA-OT lead and Co-editor DITA 1.3 specification Marketing Services Center |
E-mail: robander@us.ibm.com 11501 BURNET RD,, TX, 78758-3400, AUSTIN, USA |
Proposal #8 to add the <include> element also covered an update to coderef, svgref, and mathmlref so that they are based on <include>.
I've been working on integrating that change into the technical content specification this evening and ran into a question.
The proposal mentioned adding @parse to those three (with default values), but overlooked adding the other new attribute @encoding from the new base element. This pretty clearly seems to be an oversight (no reason to exclude it), so I've put that onto the three existing elements.
One question I'm wondering about -- with these three currently-empty elements now based on <include>, they could also allow the nested <fallback> element for cases where backup behavior is needed.
Should that element be added as a child to those three, or should they be left as they are today? I'm not sure if this was an oversight in the proposal, or was explicitly left out.
Thanks,
Robert D. Anderson DITA-OT lead and Co-editor DITA 1.3 specification Marketing Services Center |
E-mail: robander@us.ibm.com 11501 BURNET RD,, TX, 78758-3400, AUSTIN, USA |
The content of this email and any attached files are intended for the recipient specified in this message only. It may contain information that is confidential, proprietary, privileged, and/or exempt from disclosure under applicable law. It is strictly forbidden to share any part of this message with any third party or rely on any of its contents, without the written consent of the sender. If you received this message by mistake, please reply to this message and follow with deletion of the original message, any copies and all attachments, so that Oberon Technologies can ensure such a mistake does not occur in the future.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]