I am also running into the issue brought up in #48. Speciically, I am working with a partner whose rss feed contains

    <item>
      [...]
      <itunes:episodeType>full</itunes:episodeType>
      [...]
    </item>

This causes parse validation to fail. @kou has advised to disable validation in this case; is this possible to do on just this attribute, or is validation all-or-nothing? Suggesting clients disable all validation because of a common casing issue present in RSS feeds of well-known publishers is a bit impractical and opens the door to many validation bugs.

My ask is that:

• How to disable validation is documented (please forgive me if it is, but I was unable to find it and simply looked in the method signatures and have landed on RSS::Parser.parse(content, validate: false))
• Discuss the approach disabling validation of specific attributes vs global validation
• Reconsider if casing should be considered a validation error. As @liberlanco points out, existing validators do not seem to consider this a validation error, and it is a common occurrence in publishers' feeds. I am also unable to find a technical document stating that this should be a case sensitive value; I would happily take a link to a document that does as ammo to push back on the publisher.