rcade wrote:
>
> When an issue like this arises, there ought to be some means to answer
> it with authority, so developers can follow that lead.
>
> There are three potential entities that could do this.
>
> Dave, the lead author of RSS 2.0, could tell people his
> interpretation. By nature of his role in the format, it would be
> widely adopted.
>
> Sam and the other authors of the Feed Validator could validate RSS 2.0
> feeds according to their interpretation. Most RSS publishers use that
> validator and follow its dictates.
>
> The RSS Advisory Board, because it has published the RSS 2.0 spec
> since 2003 and reaches a sizable audience, could offer its interpretation.
These options are not mutually exclusive.
The RSS Advisory Board's profile has largely followed Dave's lead. The
Feed Validator has closely followed the RSS Advisory Board profile's lead.
RFC 2398 was issued in 1998 and describes the syntax of URIs. In 2005,
this RFC was obsoleted by RFC 3986. Closer to home, RFC 822 was later
obsoleted by RFC 2822. But others prefer RFC 3339.
RSS 2.0 is what it is.
= = =
Are multiple enclosures in an item permitted? This is an equivalently
binary question that one could argue that "there ought to be some means
to answer it with authority", but here's how the profile handles that
particular question:
Support for the enclosure element in RSS software varies
significantly because of disagreement over whether the specification
permits more than one enclosure per item. Although the author
intended to permit no more than one enclosure in each item, this
limit is not explicit in the specification.
Why is the question regarding namespace qualified attribute names on
core elements different?
I spent some time reading and thinking before responding, and have an idea. There are just a few people who are dug in on positions that actually are quite...
Dave, If I said something absolutely untrue, then why don't you reply to that comment and tell us what the truth is. That's the dangerous part. You keep...
I think this is a great proposal by Dave. We've been asking for clarifications on some of these things for years, and now he's offering a way for us to get...
... The nearest IETF equivalent to the RSS-Profile is a document called a "Best Current Practice". By virtue of its name, it is not a gospel. For starters, it...
... does ... I think it is safe to assume, given the last 16 months, that nothing the RSS Advisory Board does will ever go unchallenged. This is a good thing....
... These options are not mutually exclusive. The RSS Advisory Board's profile has largely followed Dave's lead. The Feed Validator has closely followed the...
... Sam, If you were concerned about my answer, then you should've said something at that time, not save it for later flamebait. The problem is people like you...
Ya, that's possible. But ask yourself if it's true. It also explains this [http://tech.groups.yahoo.com/group/rss-public/message/1370], which I thought was...
The other concern is that unchallenged advice might be considered official. If the group dislaims any official status, as the Advisory Board did, then there is...
Attacking me by saying what I said was absolutely not true and than refusing to tell me what is untrue about it. WOW! Let me re-iterate. You state, "You keep...
Okay, I'm going to avoid the invitations to defend myself. James, thanks for investigating the item ordering issue. Apparently it is as I suspected, the spec...
Dave, Let me start by thanking you for at least bringing some sanity to your argument. Compromise is defined as "A settlement of differences in which each side...
Folks, I don't wish to stick my nose in this exchange but to only say that as a "new comer" with an interest to participate and contribute to RSS future, what...
Hector Santos
hsantos@...
May 28, 2007 7:38 pm
... +1 ... We talked about a more formal process when the profile project began last year, but settled into one where we take suggestions and test reports here...
My apologies. You are, of course, 100% correct and I have egg on my face. I'm calling a ceasefire to see if we can make Dave's idea of a compromise work. ...
... Dave, I come to this discussion with no preconceptions and no bones to pick. I *am* a professional developer, but I have not been active in the RSS space....
Alan, the spec itself, in the Roadmap section, explains why it is frozen. http://cyber.law.harvard.edu/rss/rss.html#roadmap "Having a settled spec is something...
... Dave, I can accept the "no new features" part of the roadmap. One could argue that this facilitated the development of the Atom spec instead of trying to...
Alan, I addressed this in the root message in this thread. To everyone else, I don't relish these circular debates about debates. Been dragged into them for...
... I assume that you refer to the following statement in the root message: "1. Recognize that the RSS 2.0 spec is on the Harvard server, and it is not going...