The RSS 2.0 specification is ambiguous. The specification [1] clearly states
how to represent the values but fails to indicate how to delineate a
collection of values. Commas? Spaces? Other?

The skipDays verbiage also mentions Sunday as the last day of the week. Does
the order of days in the collection matter to those parsing the channel and
again what is the preferred delineator if any?

Finally, as a point of discussion which ahs probably been argued in the past
the specification fails to indicate how the channel for a restaurant or deli
for example may or may not indicate skipped hours on such and such a day(s)
while skipping other hours on this day and that day instead while skipping
days entirely on this day and that day. Clear as mud ;-)

I'll be posting this inquiry to several lists hoping to attract the
attention and comments of those who may have insight regarding how
aggregators and readers are responding to these issues. Perhaps a general
consensus will emerge as I haven't found any FAQs or "Best Practice"
documents yet...

<%= Clinton Gallagher

[1] http://blogs.law.harvard.edu/tech/skipHoursDays#skiphours