On 4/26/05, Sam Ruby <[EMAIL PROTECTED]> wrote: > If you attempt to syndicate a contentless and summaryless entry, there > will be people who drop it on the floor. It doesn't matter how many > people write software that behaves otherwise, it is a reality that some > will behave this way.
Do you have an example? > > From RFC 2119: > > SHOULD This word, or the adjective "RECOMMENDED", mean that there > may exist valid reasons in particular circumstances to ignore a > particular item, but the full implications must be understood and > carefully weighed before choosing a different course. > > I am willing to concede that there are valid reasons in particular > circumstances to ignore the requirement for a summary. Are you willing > to concede that there are implications to such a decision that must be > understood and carefully weighed before chosing to omit a summary? What are the interoperability considerations that must be carefully weighed? I think the "full implications" you're worried about are non-technical. Robert Sayre
