Paul Hoffman wrote:
At 8:32 PM +0200 5/12/05, Julian Reschke wrote:
Bare with me here; I'm not an implementer. What kind of pseudocode are you envisioning on the receiver side? My picture (which could easily be wrong is):
# Atom 1.0 RFC says entries MUST have exactly one atom:foo1 # Atom 1.0 RFC says entries SHOULD have one atom:foo2 # Atom 1.0 RFC says entries MAY have one atom:foo3
Scan the entry.
If you don't find an atom:foo1, fail. If you find more than one atom:foo1, fail. Process the atom:foo1.
If you find more than one atom:foo2, fail. Process the atom:foo2.
If you find more than one atom:foo3, fail. Process the atom:foo3.
I agree with the analysis.
So if our charter says that we should support title-only feeds, we can't make the presence of summary or content a SHOULD, right???
Why not? If the text says something to the effect of, for example, "SHOULD include an atom:summary element unless there really is no summary", then title-only feeds are fine.
:-)
Adding "unless there really is no summary" of course changes the meaning in a way that *is* compatible with title-only feeds. So can we change the spec to say that?
Best regards, Julian
