W3C home > Mailing lists > Public > public-tt@w3.org > April 2009

Re: Spec question. xml:space

From: Glenn A. Adams <gadams@xfsi.com>
Date: Thu, 16 Apr 2009 23:17:21 +0800
To: Sean Hayes <Sean.Hayes@microsoft.com>, Public TTWG List <public-tt@w3.org>
Message-ID: <C60D6D01.A391%gadams@xfsi.com>

well, the same information is also obtained from the XML Representation ­
Element Information Item of div and p, in sections 7.1.4 and 7.1.5,
respectively, which, under the Content definition includes Block.class for
the former and Inline.class for the latter, where these latter two are
defined in Table 4 in Section 5.3.1, where you can see that only
Inline.class includes #PCDATA, i.e., having a mixed content model

On 4/16/09 11:05 PM, "Sean Hayes" <Sean.Hayes@microsoft.com> wrote:

> Perhaps a note in the Section 4 abstract document type, or under xml:space
> would clarify this?
>  
> 
> Sean Hayes
> Media Accessibility Strategist
> Accessibility Business Unit
> Microsoft
>  
> Office:  +44 118 909 5867,
> Mobile: +44 7875 091385
>  
> 
> From: Glenn A. Adams [mailto:gadams@xfsi.com]
> Sent: 16 April 2009 3:28 PM
> To: Sean Hayes; Public TTWG List
> Subject: Re: Spec question. xml:space
>  
> 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 15:18:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 November 2009 22:41:42 GMT