Should in Atom binding have Content tag prio over Summary?

from the mailing list discussion:

Section 4.2. in Part II mentions in 5. b) about Atom entries:
"Other (Content-less document, Folder, Relationship, Type, etc): Best efforts at generating HTML text that represents the object. That text would normally go into the summary tag, but since there is no content, goes in the content tag. "

I wonder whether this is a useful strategy. Isn't it that most Atom readers evaluate the summary tag and not the content? How useful is it to model something as content that is not real content but more a description of an object? Do we dilute in this way the concept of content as it is modeled in the rest of the spec?

Do others feel that this is an issue that is worth creating a JIRA?

Jens

-------------------------
I agree - I would create a JIRA issue for this and only have content element with a src= attribute. Generating something inside the content element proved to be an issue in prototyping for us with round-tripping the atom entry.

-Al