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?
This package appears to introduce artificial constructs in the RSS data structure for the purpose of grouping extensions.
For example, the
RssFeed
object contains aRssItunes
child and aRssPodcastIndex
child. These names don't exist in the spec. The properties within these objects should technically be supported directly withinRssFeed
(FYI:RssFeed
seems to meanchannel
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?