Search the web
Sign In
New User? Sign Up
rss-public
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Want to share photos of your group with the world? Add a group photo to Flickr.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
Clarification v. changes   Message List  
Reply | Forward Message #360 of 1975 |
Multiple Enclosures (was Re: Clarification v. changes)

Close, but no cigar.

It's not that I want it to remain ambiguous, it *has* to remain
ambiguous, because the roadmap says so.

It takes the decision out of everyone's hands, no one can change the
spec, because the SPEC SAYS IT CAN'T BE CHANGED.

That's been the key to the growth of the format, guys. If it could
have been broken, the format would be nothing.

Dave


--- In rss-public@yahoogroups.com, "James Holderness" <j4_james@...>
wrote:
>
> A. Pagaltzis wrote:
> > Dave Winer insists that his interpretation of the spec is only
> > one of multiple valid ones. Which seems to mean that the spec
> > effectively provides no guidance and anyone should make up their
> > own mind. So I tried to formulate something that gives guidance
> > without removing this ambiguity which Dave seems to consider very
> > important â€" clarification, not change.
>
> I tend to agree. I wish he would just come out and state it
unequivocally,
> but reading between the lines, it seems to me that Dave wants the
spec to
> remain ambiguous if that's how it has always been. Any clarification
that
> made it unambiguous would be considered a change to someone. He's
trying to
> avoid having to tell all these companies that have invested
"billions of
> dollars" in RSS that their products are now broken as a result of a
> clarification in the spec.
>
> Take Microsoft for example. Their IE7 aggregator treats titles as plain
> text. Angle brackets and ampersands are just WYSIWYG - there's no
markup
> interpretation going on. However, their blogs at MSDN treat titles as
> escaped HTML. They double escape ampersands and angle brackets to
prevent
> them being interpreted as markup. Any clarification in the spec that
> unambiguously stated how titles were supposed to be interpreted
would break
> one of these two products.
>
> Of course we're now left with the situation in which we have two RSS
> products, produced by the same company, that won't actually
interoperate
> with each other. But at least they can both still claim to be valid
> interpretations of the spec. Everyone's right. Nothing really works.
But's
> it's all cool.
>
> Regards
> James
>








Thu Feb 23, 2006 6:04 pm

dwiner
Offline Offline
Send Email Send Email

Forward
Message #360 of 1975 |
Expand Messages Author Sort by Date

... I tend to agree. I wish he would just come out and state it unequivocally, but reading between the lines, it seems to me that Dave wants the spec to remain...
James Holderness
james_holder...
Offline Send Email
Feb 23, 2006
5:41 pm

Close, but no cigar. It's not that I want it to remain ambiguous, it *has* to remain ambiguous, because the roadmap says so. It takes the decision out of...
Dave Winer
dwiner
Offline Send Email
Feb 23, 2006
6:05 pm

Being Ambiguous that way is a bug, not a feature. Here's a question: I'm an aggregator implementor. Based on the spec being ambiguous in this area, I might...
jarober61
Offline Send Email
Feb 23, 2006
6:17 pm
 First  |  |  Next > Last 
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help