Re-visit modeling practices

[matthew-carroll]

This package appears to introduce artificial constructs in the RSS data structure for the purpose of grouping extensions.

For example, the RssFeed object contains a RssItunes child and a RssPodcastIndex child. These names don't exist in the spec. The properties within these objects should technically be supported directly within RssFeed (FYI: RssFeed seems to mean channel from an XML perspective).

Why was this modeling approach chosen? Why not name all classes and properties to reflect the XML names in the spec?

[matthew-carroll]

@sudame Do you happen to know the answer to the question above in this ticket?

[sudame]

@matthew-carroll Sorry for my late response, and I have no idea.