Re: [syndication] RSS 1.0 Module draft: Administrative
- Julian Bond writes:
> Ken MacLeod writesDoh! My bad. Disregard the proposal for <errorReportsTo> for 0.93.
> >This module defines <admin:errorReportsTo> and <admin:generatorAgent>
> >properties for channels, corresponding to the <errorReportsTo> and
> ><rssProviderAgent> properties proposed for RSS 0.93.
> Regarding <admin:errorReportsTo> and <errorReportsTo>, what's wrong with
> using <webMaster> which is already in
> the 0.9x specs? Quoting http://backend.userland.com/rss091
> "<webMaster> -- The email address of the webmaster for the channel,
> the person to contact if there are technical problems. Maximum
> length is 100."
All of the 0.91 fields were not incorporated directly into 1.0, but
rather were intended to be reorganized into modules, so I missed that.
<admin:errorReportsTo> is still a good candidate for 1.0 because it is
also being reused for any RDF, so it may not be a "webMaster" who is
making the RSS/RDF available.
> As for <rssProviderAgent> and <admin:generatorAgent>. This is like:-) and not that knowing that the sender's agent is Outlook would help
> the X-Mailer: email header convention. In email it's useful for
> discovering that the sender is using MS Outlook Express but not a
> lot else. I mean, who cares? I code all my rss by hand anyway ;-)
in forwarding notes of conformance issues to Microsoft, as we all know
by the number of emails that come with 1200-line replies to 1199-line
messages, saying "me too".
But for the other 95% of agents, knowing that a particular agent is
misbehaving, rather than its user, is really useful and their authors
very responsive. In particular, there have recently been several new
RSS generator packages that have come on line, starting a good trend
early makes it easier to adopt.