Martin Duerst wrote:
>This is how I generate my Atom 0.3 feed, using the popular Movable Type program:
>
><content type="text/html"
> mode="escaped"
> xml:lang="en"
> xml:base="<$MTBlogURL encode_xml="1"$>">
> <$MTEntryBody encode_xml="1"$>
></content>
Not a single namespace declaration here, so it's rather unclear to me what's going on (except if this is an explicitly wrong example, in which case I don't understand why it is here, because we know people get things wrong without needing examples.
Martin,
Rob probably has a feed root element as follows
<feed version="0.3" xmlns="http://purl.org/atom/ns#"; xmlns:dc="http://purl.org/dc/elements/1.1/"; xml:lang="en">
ie the feed is served using a default ns (I'm not sure whether you can alter this in MT without altering MT).
As long as it's XML and otherwise conformant, I think it's fine.
>Probably not. Do you and Julian and Anne and Henri approve?
I don't see how I would want to complain about how you generate your stuff, as long as the result is following the specs.
The point I'm seeing here is that creating markup using string concats is inherently fragile. No surpise there. Wrt namespaces, fragility is eliminated when you stop using defaults (but there are other considerations which keep string concat fragile). Use of div covers off the XHTML case.
cheers Bill
