-1
Misunderstands what the div is for (ie a very elegant solution to a
difficult problem, with a maximum cost of 11 bytes to those that
solve the problem in other ways).
Graham
Graham wrote:
Misunderstands what the div is for (ie a very elegant solution
I totally disagree with elegant: it's a hack!
to a
difficult problem,
What's difficult?
Namespaces? The spec might add advices and/or examples (like in
PaceXhtmlDivSuggestedOnly). Namespaces don't seem to me like a
Thomas Broyer wrote:
I might have not be enough explicit in what I'm suggesting with this
Pace: I just want the XHTML div to be optional for people that don't
need it but still meeting other people's needs of a dummy container to
carry their XHTML namespace declarations.
That way, those two
On Saturday, May 14, 2005, at 10:36 AM, Kevin Marks wrote:
After seeing 'in the wild' what I consider badly-formed Atom feeds,
where both the atom:summary and atom:content contain identical
abbreviated entry text, I realised that the spec does not make this
clear.
On 14 May 2005, at 5:36 pm, Kevin Marks wrote:
After seeing 'in the wild' what I consider badly-formed Atom feeds,
where both the atom:summary and atom:content contain identical
abbreviated entry text, I realised that the spec does not make this
clear.
As this is a key advantage of Atom, I
