MS Reveals Info On New RSS Extensions
dizzy_p writes "Microsoft released yesterday more information on their earlier announced extensions to the RSS format(s). The specifications can be found on MSDN. The question is, will the mainstream developer adopt these specifications, or will they only live in the Microsoft "Blogosphere" (To quote MSDN). The specifications in question are named Microsoft Simple Sharing Extensions Specification and Microsoft Simple List Extensions Specification"
More proprietary extensions from Microsoft. Now the question is, how useful are they really?
We'll start seeing ,These RSS feeds work only with MS RSS Reader. or some such shit. Which will piss me off almost as much as This website is best viewed with Internet Explorer.
So take note, I hate all of you developers that insist on using MS extensions for any web development. Burn in Hell!
Fuckers!
In all honesty I'd be more impressed if I saw them adhering to standards with even half the zeal that they want to "enhance" them.
I'm not very familiar with this topic, and of course Microsoft-bashing is easy in this forum, but still: What kind of attitude is that? Making extensions to a specification and publishing them for everybody else to use? So that's the way standards are defined in the Microsoft universe? I thought "making a standard" meant getting together with everybody else (or at least some approximation of that) and work things out together?
Can we learn from the lesson of Java that M$ is not the company that should be setting the standard for anything industry based. They always come out with their own modified version of XYZ and make everybody else play with them.
RTFA. Specially at the end. The text of the specification is under a Creative Commons license. Also, MS explicitly states that they have no intention of burdening implementations of the standard with patents.
Embrace and extend will not work as well as Microsoft think. Why? Because it's not the user that decides what feeds are available - it's the webmaster.
Webmaster's want to maximise the number of people who can productively use their site. Given the choice of Microsoft's custom format or a format submitted to the IETF for an RFC number I know which one I'd rather use.
Simon.
FTFA: Microsoft's copyrights in this specification are licensed under the Creative Commons Attribution-ShareAlike License.
This license is more simple, but the same in principle, to the GPL.
As to software implementations, Microsoft is not aware of any patent claims it owns or controls that would be necessarily infringed by a software implementation that conforms to the specification's extensions. If Microsoft later becomes aware of any such necessary patent claims, Microsoft also agrees to offer a royalty-free patent license on reasonable and non-discriminatory terms and conditions to any such patent claims for the purpose of publishing and consuming the extensions set out in the specification. ( http://msdn.microsoft.com/xml/rss/sse/ )
What?
He who knows best knows how little he knows. - Thomas Jefferson
ROFL!
Indeed. Is it just history repeating or the kids didn't pay attention to the last couple of decades?
That's why there aren't any IE-only sites out there anymore... Sorry to break this to you, but most "webmasters" will either slap something together that works in their browser (IE that is. "Why change something for the minority of users?" they ask) or that some "t00lz" creates for them (Hint: I've yet to see a CMS that produces, better yet, forces W3C valid output). It's a shame, yes, but I don't see why RSS should differ from HTML in that respect :-(
Funny, I don't ever recall reading that Microsoft was responsible for the development and evolution of RSS. And now they want to set their own development standards? Seems to me that we had this same problem with HTML circa 1998/9.
401 - Attention span not found
You really don't understand the 'embrace/extend/extinguish' cycle, do you?
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
Yup, Embrace, Extend, sue anyone who disagrees. We love you M$, for all the bullshit and over priced bugware
The great thing about standards in the computer industry is that there are so many to choose from.
"Is it just history repeating or the kids didn't pay attention to the last couple of decades?"
Yes because we've all seen what a failure Bill Gates and Microsoft have been over the last 20 years.
-Rick
"Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
The Simple Sharing Extension sounds pretty useful. It defines extra fields to help make one feed dependent on another feed, which will be useful when you're creating RSS aggregators.
The List Extension sounds less useful to me; it basically sets up fields to define ways to sort and group RSS feeds (like you can do with a SQL query). This one strikes me as less well thought-out and partially redundant with an RSS reader which could sort on any field. That's especially true for your basic blog-like RSS feed, where the set of fields in use is limited. It looks like this is a piece of a much larger generalized query mechanism using RDF.
I'm not an RSS expert so I can't say how necessary these extensions are. But I'll remind everybody that most new standards come out as somebody initially saying, "Here, try this!" and the ones that like stick and are eventually blessed by a standards committee. HTML predates the W3C, and HTML got a good bit of bashing around trying to find the Right Thing in practice rather than having a standards committee guess what was right.
So I'd recommend that people developing RSS readers consider adding these features and see if their users like them.
My brain is having problems with "Microsoft" and "sharing" being in the same sentence without "against" or "forbids" being involved.
"Trademarks are the heraldry of the new feudalism."
I have to wonder about the mentality of someone who looks at the RSS specification and thinks "What Really Simple Syndication needs is to be less simple".
"Hey! Do the Bender! This move is called the Bender!"[1]
This is a forum for freedom of expression, not fascist moves.
I only quickly browsed MS's site, but I don't think they implemented something similar to georss.org.
From slashgisrs: A team is working on Geographically Encoded Objects for RSS feeds. From the overview: "GeoRSS is simple proposal for RSS feeds to also be described by location or Geotagged. We standardize the way in which "where" is encoded with enough simplicity and descriptive power to satisfy most needs to describe the location of Web content. [...] it should serve as an easy-to-use geotagging language that is brief and simple with useful defaults but extensible and upwardly-compatible with more sophisticated formats like the OGC (Open Geospatial Consortium) GML (Geography Markup Language)".
GeoRSS is really an interesting innovation from the actual concept of RSS.
Animoog.org
Okay so lets take a step back and have a look at MS's past wonderful contributions to computing standards ..
Standard: HTML
Contribution:
enough said...
Okay so lets take a step back and have a look at MS's past wonderful contributions to computing standards ..
Standard: HTML
Contribution: <marquee>
enough said...
The question is, will the mainstream developer adopt these specifications No.
I kill harmless processes for sport
..This is the second phase in their usual plan of Embrace, Extend, Extinguish.
It's easier to fight for one's principles than to live up to them.
There's nothing standard about the lack of support for the beloved tag.
How do you define "mainstream" as it applies to developers? Is a developer who does SQL code for a web app used by millions of people more or less mainstream than someone who writes a straight Win32 app for 5 customers?
My guess is that developers who are writing RSS applications who see value in adding features based on these extensions will use it. Whether or not they are mainstream is a vague question that begs a pointless answer.
And today, this article appears on Developer.com: "RSS: So Simple with Wisual Basic 2005".
4 1
http://www.developer.com/net/vb/article.php/35671
"In no time, you can build a simple RSS viewer that takes a user-entered RSS feed URL and retrieves the title, description, and link for that channel."
And so now we can expect a rapid proliferation of readers that don't work with every other RSS feed in the world; they will require the 'Microsoft Extensions' (I am assuming this of the VB implementation, either now or in the future). RSS feeds and readers alike will eventually have to implement it one way or the other.
I don't know what the plan for World Domination here is, but it goes something like this:
1) Wedge yourself in the middle where no one wants or needs you
2) ???
3) Profit!
Yup. Great. Sigh.
and do yourself a favor: http://www.atomenabled.org/
The Borg Collective always "proposes" some set of "alternate" standards which they then implement in their own products, attempting to make them the de facto standard by sheer force. This just sounds like more of the same from them.
2 cents,
Queen B
HDGary secures my bank
Stage 1: Embrace
Granted that MS is also mentioned in some of such efforts, but still I think there is a place for Cisco to be offended from such a comparison as you used.
RSS was one of the few WWW things that didn't easily allow for an exploit on IE. With these extensions, this much-needed functionality will finally be available to IE users, everywhere!
Coming Soon to a Win32 box near you... ActiveRSS.NET(SP9)
help me i've cloned myself and can't remember which one I am
He's referring to Microsoft's tendency to snuff out open standards by adding proprietary extensions to them, not whatever you seem to think he's talking about.
Yes because we've all seen what a failure Bill Gates and Microsoft have been over the last 20 years.
Is a successful monopoly for Microsoft success for you as their customer/client?
People are all screaming "embrace and extend" and such but they're missing the whole picture...
/. and somehow we just HAVE to bash MS no matter what. Obviously the RSS feed format was modified 8 times already without too making too much noise, but now, because it's MS basing a new format on it then it's Evil! They're not allowed to create some new extended/better format - even if it's Open and free/Free - for the benefit of anyone. They're innovating for once, so quit the whining and thank them for sharing it with everybody. I bet soon those all the whiners will be using it and liking it - and then conveniently "forget" it was a Microsoft innovation. That's the slashdot mentality...
Not compatible? I haven't looked at the actual specs yet, but it's based off RSS, so it's most likely very similar (perhaps even backwards compatible - just that the old clients won't get the extra infos; I'll check in a few minutes).
Either ways, it doesn't matter. It's TOTALLY OPEN! GPL-like licensed, and it's just plain XML. Easy to parse and everything. It'll be easy to implement and use.
And whoever is complaining about compatibility... How convenient you're forgetting there's 9 different versions of RSS, plus there's also ATOM feeds - several versions again, and other formats like klip, opml, myst and others (I've even seen things like data feeds as JSON or such).
What's the problem with one newer, possibly better format, that's free/Free and easy to implement?
I guess this is
If you want your extensions to common protocols to succeed, I suggest you leave your corporations name out of the protocol name. And also leave out anything that resembles a copyright claim or license agreement. Web professionals are still dealing with the mess you made of HTML, Java and JavaScript.
... Microsoft has added the ability to define scrollbar colors in RSS!
RSS has been lucky so far. While the available tags has remained small, every company is defining their own namespace and pulling it in its own direction. Aside from that, I just don't see how "giving away snippets of information for free" can be a viable business option.
I like the overall idea, and I commend Microsoft for releasing the idea under a CC license, but my problem with SSE is that it requires RSS as the underlying grammar. Shoe-horning arbitrary XML data into RSS just to take advantage of SSE is seriously short-sighted.
c dc97850-c187-41e2-aaba-2875e457bcb1
SSE should be an aspect-oriented namespace that can be used to synchronize any XML data without regard to the underlying semantics, not one that requires bludgeoning XML data into a channel/item/headline/story format to take advantage of it.
More:
http://www.tallent.us/blog/CommentView.aspx?guid=
Otherwise, this undos everything, i.e. takes the simple out of RSS
Ack! I can't stand MS doing their thing again (HTML, Java, etc.)
Now some MS grunt will learn making RSS "the Microsoft way" and we will all be dealing with these "features." I just hope it doesn't become a standard.
Need a color? Try 100 random colors
Hmmmm... MSSE Specification to be pronounced "Messy" Spec, and MSLES to pronounced MS Less. Works for me.
--- Asking inconvenient questions for over 30 years...
I don't really see a problem with MS embrace and extend.... usually it is an accepted development decision to use MS- specific technologies. What I consider to be more interesting though is the fact that embrace and extend is moreso a commercial action, to differentiate themselves from competitors with similar products. And sometimes it works so incredibly well:
- the AJAX hype is all due to the MS XMLHTTP ActiveX object which IE5 (!) had, and now has only gotten to the point where there is so much hype because finally other browsers can support the same app design.
- IFRAME was originally an MS extension to HTML, I believe.
- HTML textareas MS originated.
And of course there are lot's of failures (rather dead ends). SO this is just another way for MS to compete, and you'll know if they've won this when you're using their technology, either through the MS way, or a way copied (adopted?) from MS.