On 2008-01-31 05:51, you wrote:
> On 31/1/08 10:54 AM, "Daniel Aleksandersen"
>
> <[EMAIL PROTECTED]> wrote:
> >> <summary type="xhtml">
> >>   <div xmlns="http://www.w3.org/1999/xhtml";>
> >>     <p>
> >>       This is a <em>summary</em> paragraph.
> >>     </p>
> >>   </div>
> >> </summary>
> >
> > Are there any downsides to defining the namespace in the atom:feed
> > element instead of repeating it troughout the document?
>
> the downside is that you have to repeat the xht:ns prefix on all the
> child elements:
>
> <feed Š xmlns:xht="http://www.w3.org/1999/xhtml";>
>    Š
>     <summary type="xhtml">
>       <xht:div>
>         <xht:p>This is a <xht:em>summary</xht:em> paragraph.</xht:p>
>       </xht:div>
>     </summary>
>   Š
> </feed>
>
> Any content not much more complicated than that very simple example and
> it would actually be more bytes than repeating the declaration inside
> each summary.
>
> That, plus the hassle of you adding the prefix, and the receiver
> removing the prefix .. much simpler all round to repeat the ns
> declaration on the <div /> wrapper each time.

One can easily add and remove the prefixes using any XML parser. (Which is 
required to work with Atom feeds anyways.)

I m really left with no choice but to use both <summary> and <div>, and 
with no predeclared namespace. I wonder why the specification even 
mentions other approaches then.

Regarding application/xhtml+xml in <content>.… Must I include a full 
document type and all? Or is it only the full <html> tree construct (from 
that element) that is required?

I think I will stick with representing a simple text‐type and a link!! :-P
-- 
Daniel Aleksandersen <[EMAIL PROTECTED]>

Reply via email to