OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [dita] foreign element description issue (non-XML?)

> -----Original Message-----
> From: Kristen James Eberlein [mailto:kris@eberleinconsulting.com]
> Sent: Monday, December 28, 2009 1:40 PM
> To: dita
> Subject: Re: [dita] foreign element description issue (non-XML?)
> 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.


That's not clear enough.  Anything that you add to a DITA file must preserve the validity of the file. 

If you add non-DITA XML markup, you must do so using namespaces and the namespace must be declared in the file. Otherwise, the DITA file becomes invalid from XML point of view. Notice that, you cannot declare a standard DTD in your DITA file, you have to use an XML Schema instead.

Also, in order to use elements from a foreign namespace, DITA schemas have to provide the necessary extension points. If the official schemas don't allow foreign elements inside <foreign>, then the content model is restricted to text, CDATA sections, XML comments and XML Processing Instruction.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]