How about the following wording:
The <foreign> element allows the introduction of non-DITA content, for example, MathML, SVG, or Rich Text Format (RTF). If the <foreign> element contains more than one type of non-DITA content, processors /should/ render all the content types. Specialization of the <foreign> element generally is implemented as a domain, but architects looking for more control over the content can implement foreign vocabularies as structural specializations.
Kris
Grosso, Paul wrote:
> See my suggested wording at the bottom of this email.
>
> <snipped>
<kje>a lot of content snipped</kje>
>
>>
>> The <foreign> element allows the introduction of non-DITA content such
>> as MathML, SVG, or some textual data format. If <foreign> contains more than one alternative content element, they should all be processed.
>> Specialization of <foreign> should be implemented as a domain, but
>> architects looking for more control over the content may implement
>> foreign vocabularies as structural specializations.
>>
>>
>>
>
>
