[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] inline elements in dita maps
Hi, Paul:
Regarding:
> Did we know we were doing this, or was this an unintended consequence of other decisions.
As Robert pointed out, the TC did discuss the potential for tag abuse with the <foreign> element. We decided that the benefits of extensible inclusion of standard vocabularies like LOM, MathML, SVG, XForms, ChemML, ebXML, and so on outweighed the risks.
Ideally, we would constrain the <foreign> element to exclude every DITA element (and specialization) except fallbacks like <desc>, <object>, <image>, and <foreign> while allowing any non-DITA element. The write-up:
http://www.oasis-open.org/apps/org/workgroup/dita/download.php/19115/IssueNumber35.htm
For that reason, it would seem a waste of investment for an editor tool to support practices that the scheme would exclude if possible -- for instance, editing of structured text within <foreign>. Instead, I would think that an editor tool might do better to concentrate on functions like:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]