#27 Enforce summery content type

[Bjarke Viksøe]

I would really like to see a validation (probe, if true
validation is not possible) of the content @type element.

As I understood it, if not specifically included the default
type of the summery/content elements are "text/plain",
but even Sam Ruby's blog puts HTML in the "summery"
element without adding a "type" attribute to indicate
this.

Consumer's will benefit from having valid content types.
With more "content" elements with different types, this
becomes obvious. Not all viewers run in a fancy web-
browser, so picking entries that are plain text is
important.

bjarke

[Sam Ruby]

Logged In: YES
user_id=141556

I need more information on the types of "probe" you have in
mind.

The validator already validates xml, base64, and html for
atom:title, atom:summary, and atom:content. But how do you
validate that something is NOT text/plain?

[Bjarke Viksøe]

Logged In: YES
user_id=942046

I realize that true validation would probably not be possible,
so by probe I mean to display at least a warning that possible
HTML (such as <p>, <a href> and <div> tags) are found in
the contents of the tag while no @type attribute is given.

Sure for an item actually describing a HTML related issue this
could give a false positive, so flagging the item with a warning
seems appropriate.

[Sam Ruby]

Logged In: YES
user_id=141556

See test cases:

http://feeds01.archive.org/validator/testcases/atom/must/entry_summary_not_text_plain.xml
http://feeds01.archive.org/validator/testcases/atom/must/entry_summary_not_text_plain2.xml
http://feeds01.archive.org/validator/testcases/atom/must/entry_summary_not_text_plain3.xml