W3C home > Mailing lists > Public > public-appformats@w3.org > January 2007

Re: [XBL] Conformance

From: Ian Hickson <ian@hixie.ch>
Date: Sat, 13 Jan 2007 06:02:08 +0000 (UTC)
To: Cameron McCormack <cam@mcc.id.au>
Cc: public-appformats@w3.org
Message-ID: <Pine.LNX.4.62.0701130600220.22379@dhalsim.dreamhost.com>

On Sat, 13 Jan 2007, Cameron McCormack wrote:
> Ian Hickson:
> > Oh, I see what you're saying.
> > 
> > That's covered by DOM3 Core, which says "When an EntityReference node 
> > represents a reference to an unknown entity, the node has no children and 
> > its replacement value, when used by Attr.value for example, is empty".
> > 
> > See:
> > 
> >    http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-11C98490
> 
> Ok.  But does that not contradict with the statement
> 
>   If user agents do include entity reference nodes in the DOM, then user
>   agents must handle them as if they were fully expanded when
>   implementing this specification.
> 
> because if they were fully expanded, then it could have some text, and
> the xbl:attr="def=xbl:text" would behave differently?

Oh, I see the confusion. I'm reading "fully expanded" to mean "replaced by 
its DOM replacement value" and you're reading it to mean "replaced by its 
XML replacement value".

I've fixed the text accordingly.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 13 January 2007 06:02:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:10:21 GMT