But the *content* of the <foreign> element is not XML, meaning that it
cannot, itself, be parsed as XML, which is the intended meaning of the
statement you cite.
The <foreign> element itself is of course XML. It's content may or may not
be XML.
Cheers,
Eliot
On 12/17/09 10:22 AM, "Grosso, Paul" <> wrote:
>
>
>> -----Original Message-----
>> From: Eliot Kimber [mailto:]
>> Sent: Thursday, 2009 December 17 10:04
>> To: Grosso, Paul; dita
>> Subject: Re: [dita] foreign element description issue (non-XML?)
>>
>> On 12/17/09 9:59 AM, "Grosso, Paul" <> wrote:
>>
>>> In reviewing DITA 1.2, I came across something that is more
>>> than just editorial, so I thought I'd take it to the list.
>>>
>>> The shortdesc for the foreign element says (excerpted):
>>>
>>> The <foreign> element allows content.... The content may be XML
>>> or non-XML, such as MathML, SVG, or some non-XML data format....
>>>
>>> I don't believe "non-XML" is correct. I don't see how one
>>> can put non-XML inside an XML document. In fact, I don't
>>> know what is meant by "non-XML" in this case.
>>>
>>> My review comment is suggesting we delete any reference
>>> to non-XML in this description. Any objections?
>>
>> <gml class="+ topic/foreign my-foreign-d/gml ">
>> <![CDATA[
>> .df foo
>> .ef bar
>> This is GML formatted text
>> .ex another macro
>> ]]>
>> </gml>
>>
>> Non-XML is perfectly sensible within <foreign>.
>
> I disagree. That's not non-XML. It's a <gml>
> element with CDATA content.
>
> paul
>
>
> ---------------------------------------------------------------------
> 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:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
--
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 610.631.6770
www.reallysi.com
www.rsuitecms.com
