- From: Glenn A. Adams <gadams@xfsi.com>
- Date: Thu, 16 Apr 2009 22:27:59 +0800
- To: Sean Hayes <Sean.Hayes@microsoft.com>, Public TTWG List <public-tt@w3.org>
Received on Thursday, 16 April 2009 14:28:42 UTC
Itıs not straightforward to extract this information from the text of the spec. From the RNG schemaıs Content Module (C.1.2.3), the definition of TTAF.Inline.class includes the keyword ³text², which is referenced by TTAF.p.content, but not by TTAF.div.content. TTAF.div.content includes TTAF.Block.class which does not include ³text². A similar logic applies for the XSD schema. On 4/16/09 10:20 PM, "Sean Hayes" <Sean.Hayes@microsoft.com> wrote: > Thanks, thatıs kind of what I thought, but I donıt see what combination of > spec references provides that answer. > > From: Glenn A. Adams [mailto:gadams@xfsi.com] > Sent: 16 April 2009 2:53 PM > To: Sean Hayes; Public TTWG List > Subject: Re: Spec question. xml:space > > > On 4/16/09 8:57 PM, "Sean Hayes" <Sean.Hayes@microsoft.com> wrote: > Iım trying to determine the proper handling of xml:space in the following > example fragment: > > My question is, what if anything should happen to preserved space between the > div and first and last p and between the p elements. Inline text is not legal > here, so should anonymous <p> elements be inserted, or is the space ignored? > [GA] It (the whitespace) is ignored since the content type for <tt:div> is not > MIXED.
Received on Thursday, 16 April 2009 14:28:42 UTC